Second rails push with ruby-2.2.2 fails

With an empty Rails app and ruby "2.2.2" specified in the Gemfile, the second push fails with this error:
-----> Building cranes-cuddle-belleville...
-----> Ruby app detected
remote: cp: failed to access 'vendor/heroku': Permission denied
-----> Compiling Ruby/Rails
remote: /usr/lib/ruby/1.9.1/fileutils.rb:247:in `mkdir': Permission denied - vendor/ruby-2.2.2 (Errno::EACCES)
remote: 	from /usr/lib/ruby/1.9.1/fileutils.rb:247:in `fu_mkdir'
remote: 	from /usr/lib/ruby/1.9.1/fileutils.rb:221:in `block (2 levels) in mkdir_p'
remote: 	from /usr/lib/ruby/1.9.1/fileutils.rb:219:in `reverse_each'
remote: 	from /usr/lib/ruby/1.9.1/fileutils.rb:219:in `block in mkdir_p'
remote: 	from /usr/lib/ruby/1.9.1/fileutils.rb:205:in `each'
remote: 	from /usr/lib/ruby/1.9.1/fileutils.rb:205:in `mkdir_p'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/ruby.rb:318:in `block in install_ruby'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:18:in `block (2 levels) in instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:40:in `yield_with_block_depth'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:17:in `block in instrument'
remote: 	from /usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:16:in `instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/base.rb:48:in `instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/base.rb:44:in `instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/ruby.rb:305:in `install_ruby'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/ruby.rb:85:in `block in compile'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:18:in `block (2 levels) in instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:40:in `yield_with_block_depth'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:17:in `block in instrument'
remote: 	from /usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:16:in `instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/base.rb:48:in `instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/base.rb:44:in `instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/ruby.rb:80:in `compile'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/rails2.rb:49:in `block in compile'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:18:in `block (2 levels) in instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:40:in `yield_with_block_depth'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:17:in `block in instrument'
remote: 	from /usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:16:in `instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/base.rb:48:in `instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/base.rb:44:in `instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/rails2.rb:47:in `compile'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/rails3.rb:38:in `block in compile'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:18:in `block (2 levels) in instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:40:in `yield_with_block_depth'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:17:in `block in instrument'
remote: 	from /usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:16:in `instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/base.rb:48:in `instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/base.rb:44:in `instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/rails3.rb:37:in `compile'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/rails4.rb:41:in `block in compile'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:18:in `block (2 levels) in instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:40:in `yield_with_block_depth'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:17:in `block in instrument'
remote: 	from /usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:16:in `instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/base.rb:48:in `instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/base.rb:44:in `instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/rails4.rb:40:in `compile'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/bin/compile:16:in `block (2 levels) in <main>'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/base.rb:125:in `log'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/bin/compile:15:in `block in <main>'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:35:in `call'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:35:in `block in trace'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:18:in `block (2 levels) in instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:40:in `yield_with_block_depth'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:17:in `block in instrument'
remote: 	from /usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:16:in `instrument'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/lib/language_pack/instrument.rb:35:in `trace'
remote: 	from /tmp/buildpacks/000003_heroku-buildpack-ruby/bin/compile:11:in `<main>'
       !
       !     Permission denied - vendor/ruby-2.2.2
       !
remote: Build failed: exec: job exited with status 1
To ssh://git@dev.localflynn.com:2222/cranes-cuddle-belleville.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'ssh://git@dev.localflynn.com:2222/cranes-cuddle-belleville.git'

Reported by @josephglanville on IRC.

This appears to have been caused by #1617, but I haven't sorted out why yet.


Add top level package godoc comment

When you look at https://pkg.go.dev/github.com/ethersphere/bee  , not all packages that should have a synopsis have a synopsis. Add this.

Documentation: we might want to consider linking to https://pkg.go.dev/github.com/ethersphere/bee in the advanced section of our docs

done in #1152


Parallel tests slower than regular phpunit

I'm running paratest in vagrant and they take longer than regular phpunit. I've tried 2, 4, 8, 16 processes. I also tried using -f with no avail.
Any suggestions?

How many CPUs are you allowing the Vagrant VM to use? If using the default (1) you likely won't gain anything since only 1 process will truly be running at the same time. In general, the p parameter for paratest should match the number of CPU cores you have available.
What are your result timings? Are we talking about a difference of 1 second vs 8 seconds or 1 minute vs 8 minutes? The reason I ask is since paratest will not always be faster than regular phpunit in 1 process, depending on what your tests are doing and how many there are. There is some overhead in bootstrapping & cleaning up paratest processes.
Have you tried the --runner=WrapperRunner option, it super charges running tests in parallel. This works best with well written tests that have proper setUp and tearDown, and not a lot of static/global/side effects in the code.

Thanks --runner=WrapperRunner fixed the issue
BTW, I had 2 cpus and the difference was from 9 minutes to 9:30 minutes


haskellPackages.taffybar: Compilation with newer ghcs is now unbroken…

… in version 4.0.0
@rvl you are listed as a taffybar maintainer in nix I believe. This issue was fixed in https://github.com/taffybar/taffybar/pull/541 , which is now included in the latest official taffybar release. I'm not up to date on how exactly hackage-packages.nix is generated these days. Will this latest change get picked up?
Also cc @cumber

This will be taken care of in the next hackage bump, thanks for the heads up!

@sternenseemann any idea when that will be?

Hopefully next week, we are currently struggling with a lack of time and CI issues.

Done in 37e9e677d6366ef97d9d0753f403e001f47a3f90.


scripts: drop -f from hostname, openbsd does not support it

:+1: as we're only interested in some identifier, and it should be the same on most systems anyway.


Update Jenkins configuration [phab:D509]

Created by schroederc at 2015-09-15 20:37:18:

schroederc wrote at 2015-09-15 20:39:25:
Fix comment

zarko accepted this revision at 2015-09-15 20:43:16

schroederc closed via commit 4ca2f136640c777df8f1a9ef87ce3c1f0d760bb2 at 2015-09-15 20:50:10


Return largest numbers in array - Portuguese

added solution

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

Closes #XXXXX

This one and the others (#34563 #34564 #34580) all need to include the invocation in the solution, just like in the challenge seed and the English versions. If you don't want to do that, the PRs can also be closed, as they'll be superseded by #34955, which will solve it for all challenges of all languages. Thanks!

Thanks!


HOTFIX: reduce streams benchmark input records to 10 million

We are occasionally hitting some timeouts due to processing not finishing. So rather than failing the build for these reasons it would be better to reduce the runtime.

@guozhangwang

LGTM. Feel free to merge.


Mob hats lag

Mobs picking up items as hats naturally don't despawn. If some common item is allowed as a hat there might be a lot of persistent mobs.

Suggestion: make separate list for items allowed for mob hats or make mobs equip items as hats only via dispenser.

This is a vanilla issue, unfortunately. Mobs only equip items as hats after they pick them up first. If they can't equip it, they'd just hold an item in their hand, which would still prevent them from despawning.
Note that since 1.17.1 zombies/drowned/etc can't pick up glow ink sacks at all, which also prevents them from equipping them.
I just tested this - mob does not pick up the glow ink sack, and doesn't equip it either.
Mojang are looking into a more permanent solution (see https://twitter.com/kingbdogz/status/1460241959503736833), but it likely won't be implemented at least until 1.19.
As a side note, if you use at least mod version 0.7 and set "mobsCanEquipHats" to false, mobs will no longer attempt to equip items on their heads (but you can still use a dispenser to equip them manually, similarly to your suggestion).


First try to fix sleeping barber.

This is a fix for the supposed sleeping barber in 3.6. This is 3.6 only. We do have manual tests to try to understand if the problem is solved. We do have a TLA+ model which should describe this version relatively accurately.

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/10886/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/10893/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/10919/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/10944/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/10945/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/10946/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/10953/

Another test run with normal idle timeout. When this is good, the PR is good to go from my perspective. Jan might still want to do some more tests.

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/10954/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/

I have added very thorough comments (I believe) to explain the reasoning behind _leased. Please verify carefully that the arguments are OK.

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/10973/ New run. I expect no trouble since the only change was the missing initializer.

Tests blue.


The 'Git' symbol is not normal

Hello,developer,I used this theme in the process of finding a problem, Git symbols show garbled, how can this solution? My system is MacOS. Thanks.

The specific setting is “Format for git_prompt_info()”  “ZSH_THEME_GIT_PROMPT_PREFIX”

would you mind showing us a screenshot which reveals the actual problem of this theme? :)

￼Yes, The location of the box is the wrong place, shown as garbled。

do you have font-awesome installed?

No, I don't installed it, I have just looked at the font-awesome, But I don't know how to used it on lambda-mod-zsh-theme.   Can you tell me something?  Thanks.

I didn't use font-awesome, so can't help you issues with that. @Ma27 is more knowledgeable here.
You can try out other fonts (for example, fonts mentioned here).

@halfo well, after installing font-awesome globally the branch icon was shown properly, so I assume it might be a fix for this sort of issue
@gmle I'm unfortunately not a MacOS user, but each system installs its fonts somewhere to be used by userland applications. This support thread from the apple forum might help you with that: https://discussions.apple.com/thread/4944214?tstart=0

@Ma27 Thanks, I installed font-awesome fonts , but not solved this ploblem. I try to use other ways to solve it.


Use voluptuous for ZigBee

Description:
Migration of the configuration check to voluptuous.
Related issue (if applicable): fixes 127528299
Example entry for configuration.yaml (if applicable):
zigbee:
  device: /dev/ttyUSB0
  baud: 115200

sensor:
  - platform: zigbee
    name: My Analog ZigBee Input
    type: analog
    pin: 0
    address: 0013A2004233D138

@flyte, would be nice if you could take a look at the changes and run a quick test. Thanks.

LGTM - second set of eyes?


feat: implement fast-follow placeholder website for firebase

Implements #64
Using the image described in https://github.com/GoogleCloudPlatform/avocano/pull/231, create a Cloud Run job that deploys a placeholder website. This will execute midway through the terraform processing, giving a "Your application is still deploying..." page.
Once the client deployment job runs, this placeholder is overwritten. The placeholder autofreshes through JavaScript every 5 seconds, so automatically updates when the avocano site is deployed.
This is faster than splitting the existing client/setup jobs into separate instances, as the client job depends on the cloud run API service, which depends on the database, which makes it low in the order of deployments. Deploying a placeholder without this dependency makes it higher in the order of operations, observed to be midway through the sql instance deployment, but definitely mid terraform deployment, which means it's ready before the window where Terraform is done but async metadata startup scripts haven't completed.

It's non-obvious, but tests are failing because the "plan after apply should have non-empty diff".

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # module.dynamic-python-webapp.google_compute_instance.placeholder_init[0] will be updated in-place
  ~ resource "google_compute_instance" "placeholder_init" {
      ~ desired_status            = "TERMINATED" -> "RUNNING"
        id                        = "projects/ci-dynamic-python-webapp-44c8/zones/us-central1-c/instances/placeholder-initialize-4ac0"
        name                      = "placeholder-initialize-4ac0"
        tags                      = []
        # (19 unchanged attributes hidden)

        # (5 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so Terraform can't
guarantee to take exactly these actions if you run "terraform apply" now.
    terraform.go:359:
...
        	Error:      	Should not be: 2
        	Test:       	TestSimpleExample
        	Messages:   	plan after apply should have non-empty diff

This is because the placeholder GCE instance copied the desired_status from the "run migrations again if you run terraform" config from #46. The placeholder instance was long stopped, and should only be run once, so the desired_status can be removed.
It's presumed this instance stays running for a short time after terraform apply finishes, as it's running the jobs, so the state will still be running by the time this check is made. If this compute instance ends up synchronous, resulting in a plan diff by the time this check is run, this may need to be readdressed.

@grayside merged the two PRs together, can I get your re-approval?

Merging blocked pending https://github.com/GoogleCloudPlatform/cloud-foundation-toolkit/pull/1575


enable-root-server as config option

Has there been any discussion on moving the compile time option --enable-root-server to a runtime configuration option? Where I understand why measures should be taken to protect users from using NSD as a root server, requiring a custom build seems a bit to complicated. Having this as a runtime configuration option would help a lot running of the shelf binary packages.

Hi @jschlyter! You're right in that the compile-time option is there to prevent people from unknowingly serving some version of the root zone. I asked around internally and people are fine with turning this into a runtime option (it was added before NSD supported configuration files). I'll have a look to determine the amount of work involved.

I would go further and say that this option should be dropped altogether. Other name servers, such as BIND, Knot DNS and PowerDNS, do not require enabling anything special to run as a root name server, and I haven't heard of any cases of folk misconfiguring things. This whole enable-root-server option, whether as a compile-time or run-time, is unnecessary.


added product 902 (8x8 bicolor led)

The adafruit website links to this library but this library doesn't link to the adafruit website. Just wanted to reduce confusion

This looks good to me! Can someone with repository access review?

This looks good to me! Can someone with repository access review?


Change Capybara.default_wait_time to Capybara.default_max_wait_time to fix deprecation warnings

The warning appears whilst running Cucumber with recent versions of Capybara. Also added some tidying up via Rubocop

Thanks :)


advice for npm errors after following steps in readme

After following the setup-instructions in the README I'm getting a bunch of errors from npm.
How should one handle the missing peer dependencies to webpack 4 and 3, and also an older version of less (2.3.1)?
I'm not sure what impact this has, but I'm concerned with starting a new project based on this cookiecutter with all these errors I don't understand popping up.
Warnings shown during install
(myflaskapp)$ npm install
npm WARN deprecated<EMAIL_ADDRESS>Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 1051 packages from 667 contributors and audited 8898 packages in 20.528s
found 1 moderate severity vulnerability
  run `npm audit fix` to fix them, or `npm audit` for details

Errors shown when running npm ls (all the errors except from missing peer dependencies actually go away after a npm dedup)
(myflaskapp)$ npm ls
npm ERR! peer dep missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! peer dep missing<EMAIL_ADDRESS>|| ^4.0.0, required by<EMAIL_ADDRESS>npm ERR! peer dep missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>
My npm and node versions
(myflaskapp)$ npm --version
6.4.1
(myflaskapp)$ node --version
v10.11.0

I had that problem on windows. nodejs on ubuntu worked fine.

A number of outdated packages have been recently updated, which addresses many of these warnings. If you happen to be running into Windows-related issues, I'd recommend you check out the new instructions for creating a project using docker!


Expected not to find a document already present for an add

Hi Arunoda,

When server sends an object that is already present on client via fast-render, the client throws this error. The issue doesn't manifest on localhost, only on production servers (both Modulus and Galaxy). You can see it in https://pintask.me/: just log in and reload the page.
Also, it's evident that the number of errors (236 on screenshot) is correlated to number of fastrendered objects. Here's a simple test:

Open one board in Pintask
Reload the page.
Note the number of errors
Execute Cards.find({boardId: Router.current().params.boardId, isArchived: false}).count() + Lists.find({boardId: Router.current().params.boardId}).count()
Open another board
/* Do the same */

It's clear that difference between error counts is equal to difference between fastrendered cards+lists sums.
This error is present on both projects I'm involved in, and both projects use latest Meteor <IP_ADDRESS> + latest fast-render 0.2.5

Hope we are good here.


dubious makeRequest function

What does it do? Why does a connect to http://www.umei.cc/p/gaoqing/cn/ ? It will at least make my Windows Firewall open up for that remote URL, and make that site register my IP.
Does not seem to be needed for the plugin. Better to remove it, or document its purpose.
Found at
https://github.com/Wscats/compile-hero/blob/master/vscode-extension/src/extension.ts#L234

This is a code snippet that has not been used. @BananaAcid

I too was wondering about this.

@b1m1nd Because I originally planned to provide a postman-like function before, but due to time constraints, I have left this unused code.


Update language-support.md

Adding newly added options and services where we extended support

@tylerthedeveloper : Thanks for your contribution! The author(s) have been notified to review your proposed change. @metanMSFT

#sign-off

@erhopf: I'm sorry - only the author of this article, @metanMSFT, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@erhopf - we are blocked on this as the original approver, metanMSFT, has left the company.
@dylankil has taken over his position, can we update that in the backend?

@ktoliver - Can we approve this PR, as the author listed has left the company. I can go ahead and update the author in azure-docs-pr once this is merged. Thanks!

Thanks all!


Cannot compile sass with imports

If a sass file uses a relative @import from another file, it won't be inlines
Reproduction: https://stackblitz.com/edit/node-hutoco?file=src%2Fstyle.sass
(run npm test)
Context: https://github.com/unjs/mkdist/pull/27 > https://github.com/nuxt/module-builder/issues/87

see https://github.com/unjs/mkdist/pull/109

Since it got fixed: When can we expect the next release of mkdist (and unbuild)?


Add dockerless-calico docs and systemd services

Lookin' good to me.  I think we'll still want to pin those versions once we have a release which includes this, but we can update the doc then.


Fix: missing vars in disabled models fail compilation (#434)

Fixes #434
When a var is missing during parsing, just always return None. Wait until runtime (compilation, etc) to actually fail about it.
This avoids requiring a var to be set even when a model is disabled, but still fails as appropriate when a var isn't set for an enabled model at compile time.
I've based this on PR #1426 as they touch basically the same stuff.

Well, first: I think if anything it's actually more correct to let the errors ride at parse time and catch them at runtime. The only goal of parse-time should be to find refs, sources,  and docs and to evaluate config() calls. Anything else that we can catch that early is nice, but we should throw away any of those niceties if it means we can do a better job at having understandable behavior.
That said I think we can figure that problem regarding the variable being set (I don't think _VAR_NOTSET comes into this!) and the model being disabled out, but it hinges on how we handle #1149. Currently that stuff is not going to work like it should.


dotenv / ports configuration

Description
Hey guys, found it a bit difficult to setup with a custom configuration, so made this. It's tested both with docker and development.
Reference issue
Fixes #75

split js/flutter to some new repo


[TDD] Create a TDD to add Application Note to CSV export

Is your feature request related to a problem? Please describe.
For the issue #7366, please create a TDD.
Describe the solution you'd like.
Adding the application note is not a trivial solution since the data is stored in the application_events table and for every application to be exported, we would do a lookup of the latest application note event to extract the note raising the time complexity to O(n^2) queries which would eventually fail the export and cause SQL timeout error. We need a better design on how to implement this.
What priority is this?
P2
Done when:
TDD is ready for development.

Not proceeding with a TDD at this time. I have provided a detailed explanation of approach in the PR.

Work is done.


Ensure all spo list webhook commands have all available list options

Noticed some sort of inconsistency regarding list options. To reference a list, you could use 3 ways: title, id or URL.
Below is a summary of all commands with their missing option(s).

Command
Options to add

spo list webhook add
--listUrl

spo list webhook get
--listUrl

spo list webhook list
--listUrl

spo list webhook remove
--listUrl

@milanholemans I could work on this!

Awesome @MathijsVerbeeck thank you!

Wups wrong assignment 😄


Use unique typeface for post titles

Would you like to use the Sans-Serif typeface for this? The site already has Open Sans in use in many other places anyway.

If you think that's best, it's okay with me. But I was thinking it'd be
nice to have a unique and distinctive typeface for our titles, such as the
New Yorker does.
On Sun, Mar 22, 2015 at 4:23 PM, Dylan Kinnett<EMAIL_ADDRESS>wrote:

Would you like to use the Sans-Serif typeface for this? The site already
has Open Sans http://www.google.com/fonts/specimen/Open+Sans in use in
many other places anyway.
—
Reply to this email directly or view it on GitHub
https://github.com/real-pants/Real-Pants/issues/50#issuecomment-84693086
.

The New Yorker's latest design on the web has a custom-made typeface that was cut especially for them and they also use Neutraface, for which they have a custom license for use on the web. Nobody else can use it on the web, so far as I can tell.
I imagine you don't have the budget for something like a custom typeface or a license like that but could you elaborate on what you mean by "unique and distinctive"? There might be something readily available, for free or for sale, something that would give the kind of typographic impression that you want to make. I imagine that uniqueness is important but new-yorker-ness maybe not so much, since they have that whole New Yorker vibe going on. This is about the Real Pants vibe, which is different.
You probably already know this stuff but if it helps to have some vocabulary for talking about the various qualities that typefaces have, so you can say what you like and dislike, I think that this guide is a useful one.

At some point I had selected a type family for serif and san serif, but I can't find it anywhere. You're right that it wasn't a totally custom face. What I found was free (limited to a small part of the family) and web-ready. I'll find something else ... they abound.

I was looking for that too. I remember it. Where did that post go? I'll look for it too.

I found it! Questa Sans Regular. I forwarded it to you separately.
On Mon, Mar 23, 2015 at 10:45 PM, Dylan Kinnett<EMAIL_ADDRESS>wrote:

I was looking for that too. I remember it. Where did that post go? I'll
look for it too.
—
Reply to this email directly or view it on GitHub
https://github.com/real-pants/Real-Pants/issues/50#issuecomment-85311819
.


Inquiry: using MQTT-WS transport in azure-sdk-for-c-arduino

Query/Question
I was wondering whether the MQTT-WS(S) transport is available in the azure-sdk-for-c-arduino library
Disclaimer: I'm asking here because the https://github.com/Azure/azure-sdk-for-c-arduino repo doesn't have an Issues section.
A tangential question was raised before: https://github.com/Azure/azure-sdk-for-c/issues/2313
There @danewalton stated that "[...] the transport is up to the user with this library, so you may swap in any MQTT or MQTT/WS library that you'd like."
I'm using azure-sdk-for-c-arduino lib on the ESP32 based on the Azure_IoT_Central_ESP32 example. The sample uses the esp_mqtt client and mqtts transport. But esp_mqtt also supports mqtt-ws (based on this esp_mqtt WSS sample).
If azure-sdk-for-c-arduino is fully transport-agnostic, it should be straightforward to switch to websockets (mqtt-ws or mqtt-wss). All that's required is a modified mqtt_client_config. I haven't had the time to try it out yet. Can anybody confirm my assumptions?

Hi @meta-space, you are correct. The transport layer is up to the user, you can refer to the esp_mqtt documentation to learn more about how to enable websockets.
By modifying the uri in mqtt_client_config you can connect via websockets. You need to change mqtt:// to wss:// as a prefix and add :443/$iothub/websocket as a suffix.

@RLeclair Thank you for the confirmation. I'll try it out.
Won't I have to configure TLS Certificates in the esp_mqtt client when I switch to wss ?

No need, you should still be able to use the SAS tokens in the sample (I assume that is what you were using)

@RLeclair Thank you! I've switched the protocol scheme from "mqtts://" to "wss://" and port number from 8883 to 443. But I haven't found a parameter or hook to change suffix. Nonetheless, the device connects to DPS and IoT Hub and is responsive via Azure IoT Explorer.
I'm connecting through DPS using this configuration. Is it possible that DPS will automatically redirect the device to "$iothub/websocket" ? Or asked differently, I've found the

#define AZ_IOT_HUB_CLIENT_WEB_SOCKET_PATH "/$iothub/websocket"

in the az_iot_hub_client.h header, but I don't understand whether this is supposed to be a url suffix or a mqtt-topic suffix... At the moment it seems to be working without it, or may be automatically used when the websocket transport is active.

@meta-space, great to hear! For your first question, DPS will provide the domain name for the IoT Hub, from there you can add the suffix and prefix to it.
With regard to the AZ_IOT_HUB_CLIENT_WEB_SOCKET_PATH, we don't have a sample on how to use it, but for our arduino samples you can edit our central sample (inside mqtt_client_init_function) you could add something like (look at last line below):
az_span mqtt_broker_uri_span = AZ_SPAN_FROM_BUFFER(mqtt_broker_uri);
mqtt_broker_uri_span = az_span_copy(mqtt_broker_uri_span, AZ_SPAN_FROM_STR(MQTT_PROTOCOL_PREFIX));
mqtt_broker_uri_span = az_span_copy(mqtt_broker_uri_span, mqtt_client_config->address);
mqtt_broker_uri_span = az_span_copy(mqtt_broker_uri_span, AZ_SPAN_FROM_STR(":443/$iothub/websocket"));

@RLeclair Thank you again. I used your snippet in the mqtt_client_init_function function and it appears to be working.


Can anyone give me the new miner for the V1.0

Can anyone give me the new miner for the sia v1.0 ????
By the way ,now ,can i also use the old (sia v0.6 ) to mining ???

Sia 1.0 compatible binaries for Windows will be available in about 3 or 4 hours, I think.


Add zsh completion for 'docker import -m --message'

Ref. #15711
ping @albers for bash
Signed-off-by: Steve Durrheimer<EMAIL_ADDRESS>

ping @vincentbernat :+1:
(thanks @sdurrheimer !)

Added this to 1.9.0 milestone (as the command is in there).

LGTM

LGTM, thanks @sdurrheimer and thanks for reviewing @vincentbernat


Chore: docs updates

adds a "Performance" section
improves docs for "Mutation" and "Prefetching"
fixes the missing style bug
adds cssnano to remove duplicated tailwind styles

~⚠ DON'T MERGE: I need to investigate why the sidebar is missing~

📝Changed routes:

/advanced/meta
/advanced/performance

(view full size)
(view full size)

/docs/mutation
/docs/prefetching

(view full size)
(view full size)

/meta

(view full size)

Commit 43f0f0def5e2d7d9810c96a224a560be2216ca22 (https://swr-site-git-chore-updates.vercel.now.sh).


It is not going any further

Describe the bug
VirtualBox:~/RasaTalk$ yarn
yarn install v1.13.0
$ npm run npmcheckversion
npm WARN lifecycle The node binary used for scripts is /tmp/yarn--1550479431722-0.303340767008462/node but npm is using /usr/local/bin/node itself. Use the --scripts-prepend-node-path option to include the path for the node binary npm was executed with.

<EMAIL_ADDRESS>npmcheckversion /home/ajinkz/RasaTalk
node ./internals/scripts/npmcheckversion.js

[1/5] Validating package.json...
[2/5] Resolving packages...
⢀<EMAIL_ADDRESS>Screenshots

Desktop (please complete the following information):

OS: 16.04
Browser Firefox
Version 65.0

What version of NPM are you running?
Can you try running yarn install instead?

It looks like yarn in not properly installed.
Maybe just use NPM instead.
So npm install

Hey @Ajinkz Please reopen this if the error reoccurs.


OAuth: Handle intermittent internet connectivity

For the longest time, poor @JohnONolan has reported constantly being logged out of Ghost. Something myself and other devs have never been able to reproduce.
Today, after another report, I thought I'd check in to see if something had changed in Ember Simple Auth that might cause the session to not refresh, and I stumbled across this issue about disconnects.
This is by far and away the best theory I've ever had for why some people can't stay connected - after all John lives somewhere where the internet connectivity is unstable and the rest of the devs all have awesome WiFi. It makes perfect sense that token refresh requests are frequently failing, and if there is no handling or retries this would result in re-auth dialogs popping up on a regular basis.
The issue on ESA outlines some application-level solutions, and apparently there is also a discussion on the slack channel.
I'd really like to see retries after connection drops handled in Ghost in lieu of support perhaps being added to ESA. This would fix one of the most gnarly and annoying issues we have!

Hi, Eris. I created the issue you're referencing. Just a caveat on my current working solution which you mention: I am essentially overriding the private method _refreshAccessToken by copying the original implementation into my own authenticator. This was necessary because, currently, _refreshAccessToken does not reject with the xhr object which you need in order to determine the cause of the failure.
Maybe this is something that could change in ESA at a later time. Good luck.

@rhyek thanks for the info 👍

Note here: we also need to check if poor internet connectivity could be interfering with signing in at all - e.g. does the User model hide away connectivity errors and make them look like bad passwords?

Eris, I have a created a gist with my complete oauth2 authenticator. Maybe it will help you. Features are:

Ensure only one tab/window is handling token refreshes to avoid 400/401 errors due to concurrent requests and lowering bandwidth used.
If a token refresh is rejected with 400/401 http status codes, invalidate the session.
Attempt token refreshes when 90% of the access token's lifetime has transpired, leaving the remaining 10% as an opportunity to retry the refresh in case of connection failures.
If a token refresh failes due to a connection error, keep trying every 5 seconds until the current access token's lifetime has expired, in which case, the session will be invalidated.


which php is required by this extension

I got this error when install omnipay 3, please tell me which version of php is required.
Thank you.
composer require league/omnipay:^3 omnipay/paypal
[InvalidArgumentException]
Package league/omnipay at version 3 has a PHP requirement incompatible with your PHP version (5.6.38)
require [--dev] [--prefer-source] [--prefer-dist] [--no-progress] [--no-suggest] [--no-update] [--no-scripts] [--update-no-dev] [--update-with-dependencies] [--update-with-all-dependencies] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [--sort-packages] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--] []...

Try version 3.0.1. 5.6 was removed in version 3.0.0 and readded in 3.0.1.


Let users view how other set Challenges

For novice users it would be tremendous help if they could see how other users set their challenges. There is no better way to learn but from working examples.

Thanks for bringing this up, @yt9tp. We can definitely do a lot more to make challenge creation easier. Are there specific aspects or settings that you're interested in?

Actualy I had few issues to understand.

I wanted to create challenge that selects some highway way objects for naming. Ways did not show up in chalenge until I included nodes too. I ended up with challenge with frightening number of tasks as all nodes were counted too althrough those are not meant to be edited at all.

Resolving tasks did not show up in challenge until I updated tasks with option to delete. That messed up with perspective what was included in challenge at start and what has been done, as, after each refresh only unresolved tasks were left.

I have to run tasks update manually to see what has been done so far, as already resolved objects kept coming up.

For number of highways there were several sections to edit. Each section is represented with tasks, actually number of task because task is created for each node on way. But, tasks were not offered in logical order (for example all tasks related to a single way i na row) but almost completely random across al ways. ti makes things harder to do as each next task ends up on a totally new way. It is much easier to edit road by road (all tasks in one road and then move to all tasks in other road).

It might be I did not understand how all this works. I tried to find and read all instructions available.

Hi @yt9tp -- I do understand it could be  easier, and documentation easier to find. This is probably the most comprehensive guide out there to help with Challenge creation.
A couple of points to your questions:

To avoid getting way-nodes as separate tasks, use [out geom] instead of recurse down in your Overpass query. This will get you the way geometry without the nodes as separate objects. See here for an example of how to not do it and here for a fixed example.
MapRoulette is designed to have randomly assigned tasks by default, but users can override it to receive 'nearby' tasks instead. As a Challenge owner, you could encourage mappers to use that, if it's relevant to your challenge. You could also try pre-processing the task GeoJSON to group tasks that you think belong together logically.

We're always happy to help, so let us know if you have any trouble.

Thanks.
I followed your suggestion abutusing [out geom]. Change in GeoJSNO is visible and it is now more logical - nodes are part of ways. However. Maproulette still counts nodes as tasks and for each way I have to go through each node.
It is now even more obvious when I use option to get next task in near. Getting near tasks works fine, except that most near tasks are nodes that do not need editing at all.

I got it. I had to remove clause
(._;>;);
Without it i could not get any task before. Now, after I set [out geom] just selecting ways works fine and result contains only ways, without nodes. Excellent!
Thanks a lot!
As I cannot edit Overpass query it seems I have to create new chalenges and delete those that I used so far.

Yes, you need to delete the old challenge and start a new one, sorry.

I am going to close this because the OP's specific questions were answered, and we have #96 to cover documentation.


Issue with deployment (Vercel)

Hi,
I'm running into the following issue and haven't been able to resolve it. When deploying, I'm receiving the following error in the Vercel log:
undefined
--
16:24:56.539 | [error] Could not load raw:./dist/vue3-picture-swipe.css (imported by node_modules/vue3-picture-swipe/index.js): ENOENT: no such file or directory, open './dist/vue3-picture-swipe.css'

Has anyone run across this before?

Same issue.


[runtime/onnx] fix the bug of OrtEnv singleton lifetime.

The OrtEnv singleton will be release, When the Env object destruct. So need use static mark Env live in whole process.

Why should we keep Env alive? It seems Env is only used when constructing sessions.


Support bs-platform@7

The problem
Is<EMAIL_ADDRESS>on the roadmap?
Considered solution
I started the conversion here: https://github.com/idkjs/reason-react-native/tree/bs_platform_701
Tested on the template here: https://github.com/idkjs/reason-react-native-bs701
Of note, I have not completed VirtualizedList.re yet since there is some trickery with section in that file.
I also have not converted the .md's yet. I wanted to get some feedback before continuing.
All of the changes are to implement the new syntax. A few examples are:

How do you test this repo? Is there a way to find out if I have broken anything?
Should I make a pull request?

Yeah sure bs 7 should be handled :) On all repos!
That said, this will be a breaking change release, a huge one.
We shouldn't probably rush on releasing that, as most people won't be ready to upgrade all there projects. Not sure if we can easily provide a upgrade script (most of the changes will be "## => ." but how to know what is RN & what is normal "js/json" from the user?)
For now the best way to test is to use unreleased branch in real world projects.
We could do an app + auto testing (via detox) but to cover entire react native apis, that will be a lot of work & a lot of maintenance... :)
@cknitt @sgny any idea/comment on how to handle such a breaking change?

We already have a fairly complete release that does not seem to have any major issues at the moment., if any such issues arise, we can make a branch of the repo before the breaking changes, so that users on v5 and v6 do not have to immediately move to v7.
I think not having to deal with Js.t objects is a huge QOL improvement and in comparison the move to v7 itself is quite painless and can be dealt with a simple script as you said. We can add a disclaimer that If users had their own Js.t objects, they will break, so that there is no surprise when the compiler throws that error.

I guess we could do a branch & keep maybe 2 version aside for a while until bs 7 is commonly used. like<EMAIL_ADDRESS><EMAIL_ADDRESS>something like that.
Indeed I didn't think about a script that just totally remove Js.t() for good :D

I agree with you all. bsp7 is huge. Simplifies things a whole lot and we should support it as soon as possible because every single time someone runs npm -D bs-platform they will be getting version 7. And presumably writing code in the style of bsp7. I don't mind testing it. Can we suggest any good, fairly complex examples out there that I could install 7 on and see what happens? I was going to try on @cem2ran's https://github.com/cem2ran/InstaClone but I could not get it run properly.

I'm going to backtrack a little.
@idkjs Since Js.t objects seem to work without issues with v7 (in my limited testing), there shouldn't be any issues with users transitioning to v7 even now. I'm not aware of that syntax getting deprecated or removed on any schedule, but I may be mistaken., so please correct me if I have missed the notice.
On the other hand, even though I don't much like Js.t objects, I should avoid being biased. Having to use the ## accessor, as is our convention, does remind one that one is dealing with an external object. That could justify keeping them.
While we are discussing these changes, we should also consider object creation. As BS records are JS objects now, do we want to keep constructors defined with the bs.obj decorator? Again, the current convention seems to work quite alright and could be kept.
TBH, the tangible benefit I'm aware of is the cleaner output when we have submodules and functors. We could take advantage of that even now.

Since Js.t objects seem to work without issues with v7 (in my limited testing), there shouldn't be any issues with users transitioning to v7 even now. I'm not aware of that syntax getting deprecated or removed on any schedule, but I may be mistaken., so please correct me if I have missed the notice.

Probably not getting deprecated. If you start using the new syntax, you will be accessing you keys with . to access your js objects. In my experience running through this and other repos, I did find myself having to think about whether an entity was a proper reason record or some value that came from js since we are accessing both with .. Compiler will keep you inline though. It's better than ever. The reminder point is a good one. Worth noting that since most of the code is behind an .rie, the end use shouldn't see any changes, right? I am asking. I don't have enough experience. I know that when I toss the bs7 version into an old reason-react-native project, it runs, whatever that means.

While we are discussing these changes, we should also consider object creation. As BS records are JS objects now, do we want to keep constructors defined with the bs.obj decorator? Again, the current convention seems to work quite alright and could be kept.

In the bs_platform_701 branch I changed every<EMAIL_ADDRESS>that didn't have a<EMAIL_ADDRESS>special type into a reason object as bs.string variants aren't supported in the new syntax. So mixing them doesn't hurt and the files are cleaner. Just for fun, though, I might go try turning some into inline values modules though, if @yawaramin says its not zero-cost.

TBH, the tangible benefit I'm aware of is the cleaner output when we have submodules and functors. We could take advantage of that even now.

If you show me an example of this, I will go do it.
At any rate, I do not need this to happen for any reason. I thought maybe it would be a thing we wanted to do and it I learned a whole lot going over your code line by line. So, If there is no interest we can go ahead and close this issue.

Since Js.t objects seem to work without issues with v7 (in my limited testing), there shouldn't be any issues with users transitioning to v7 even now. I'm not aware of that syntax getting deprecated or removed on any schedule, but I may be mistaken., so please correct me if I have missed the notice.

Probably not getting deprecated. If you start using the new syntax, you will be accessing you keys with . to access your js objects. In my experience running through this and other repos, I did find myself having to think about whether an entity was a proper reason record or some value that came from js since we are accessing both with .. Compiler will keep you inline though. It's better than ever. The reminder point is a good one. Worth noting that since most of the code is behind an .rei, the end user shouldn't see any changes, right? I am asking. I don't have enough experience. I know that when I toss the bs7 version into an old reason-react-native project, it runs, whatever that means.

Even for components without interface files, very little would need to change. We would not need to change names of any types (in case anyone else types everything explicitly like I do!). What would matter are the valid keys. As you observed, once a type is redefined as a BS record, then the compiler will enforce the . accessor (and the ## accessor if the type remains Js.t). Basically, at least for the replacement of Js.t types with BS records, the users would only need to replace ## with ..

While we are discussing these changes, we should also consider object creation. As BS records are JS objects now, do we want to keep constructors defined with the bs.obj decorator? Again, the current convention seems to work quite alright and could be kept.

In the bs_platform_701 branch I changed every<EMAIL_ADDRESS>that didn't have a<EMAIL_ADDRESS>special type into a reason object as bs.string variants aren't supported in the new syntax. So mixing them doesn't hurt and the files are cleaner. Just for fun, though, I might go try turning some into inline values modules though, if @yawaramin says its not zero-cost.

Actually, he says the cost is incurred only when used. For example, the decelerationRate prop for the ReactNativeWebView bindings accepts floats or string literals, so I used (after @cknitt with the version in this repo) bs.inline for the string literals and a function to cast floats as the appropriate type. When you pass such a value to this prop as below
decelerationRate=ReactNativeWebView.DecelerationRate.fast

the output is simply
decelerationRate: "fast",

So there is no additional cost.
We usually have to resort to bs.inline for string literals with Js.t objects passed to callback functions (so the above is an exception). They are verbose and we also have to define interfaces for them to prevent arbitrary new values to be created, etc. They also would have to be either defined multiple times for when the sets of allowed values are not quite the same. so we would have to have different scopes, etc.
The clear advantage with polymorphic variants is that they are identical no matter where you use them, you do not have to have them in scope. I think that matches very well with string literals. We cannot define a type made up of polymorphic variants, but we probably could not reuse them in practice anyway. Greatest opportunity for reuse would probably be with Style props, and there the sets of aligned values are not identical so we'd have to define multiple types.

TBH, the tangible benefit I'm aware of is the cleaner output when we have submodules and functors. We could take advantage of that even now.

If you show me an example of this, I will go do it.

Nothing is needed, the output is nicer with v7 for the same syntax.  With v7, Animated.bs.js has
var Value = {
  Decay: Decay,
  Spring: Spring,
  Timing: Timing,
  interpolate: interpolate
};

instead of
var Value = /* module */[
  /* Decay */Decay,
  /* Spring */Spring,
  /* Timing */Timing,
  /* interpolate */interpolate
];

The latter is easier to read and closer to JS code written by a human.

At any rate, I do not need this to happen for any reason. I thought maybe it would be a thing we wanted to do and it I learned a whole lot going over your code line by line. So, If there is no interest we can go ahead and close this issue. Thank you,sirs, for taking the time to give considered responses.

I do appreciate that you have brought this up and that these design choices are considered. It's just as valid to keep Js.t types as to change to BS records; the former allows a useful differentiation, the latter is more idiomatic now. Admittedly, I'm not too keen on bs.string for bs.inline and would prefer to keep the constructors, but the discussion is still open.

To make this short: I propose we start a branch on this & keep for a few months 2 version of the bindings (should be hard to back port fixes/changes now that we cover most of RN on 2 branches).
I find the . compared to ## clearly better for new comers & the bs7 record thing is especially nice for interop when you want to use Reason code from JS (yeah that can be a thing, which make sense if you integrate reason in a JS app & want to use your new reason component from old js code).
So @idkjs I am adding you to the org so you can create a branch in the repo to directly put things here so we might work on this together as a team :)

Cool. I will get on that. Should we close this?

Ok. First time being added to an org. Again, thank you. I have cloned this repo, created a branch with the branch code, then tried to git push origin branch-name. The password is a github token, though I tried with my regular password as well. I get the following error:
reason-react-native-org [bs-platform-7.0.1]git push origin bs-platform-7.0.1
Username for 'https://github.com': idkjs
Password for<EMAIL_ADDRESS>remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com/reason-react-native/reason-react-native.git/'

Any guidance would be appreciated. Thank you.

@idkjs You need to turn on two-factor authentication, if you have not already done so.

Already did that.

We should close this when a release is made, not before :)
The org doesn't change a thing, let me check that the rights are correct.
It seems ok.

You might need to check your git config, maybe setup ssh?

Don't think I have my git ssh setup. Was using the http instructions on git. Will get on it. Thank you, sir.

Finally got it to go. New branch is here:https://github.com/reason-react-native/reason-react-native/tree/bs-platform-7.0.1

I opened your branch as a PR so we can track progress :) Thanks for starting this initiative!

I am late to the party. 😉 Not using bs7 yet because of some minor Reason parser issues affecting our codebase that are still being ironed out. Should be good with the next BS release though.
In any case, I would love to have records instead of Js.t  objects, too. I left some comments in the PR.


Need for Dynamic Navbar

Currently, the navbar on the homepage is not dynamic; decreasing the size of the window causes the navbar to disappear. The expected outcome is that decreasing the size of the window should collapse all the navbar elements into a hamburger symbol.

@shubhrad1, you can check this issue as well.

Sure, I'd like to work on this.

@shubhrad1 assigning this to you. You can start working in that direction

I have made the PR which resolves this issue


KeyBoard manager does not use the remapped keys while casting

Microsoft PowerToys version
0.72.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
Keyboard Manager
Steps to reproduce
While using the windows Cast to Wireless Device feature to extend screen, KeyBoard Manager does not supply the remapped keys to the second screen.
✔ Expected Behavior
I swapped Control and Caps Lock keys, on second screen (while casting), the re-mapping was ineffective.
❌ Actual Behavior
No response
Other Software
No response

What do you mean with "Cast to Wireless Device"? /needinfo

I also encountered a similar problem:
I set the shortcut key mapping through the Keyboard Manager, Win (Left)+R=>Win (left)+Ctrl (left)+R, but it did not take effect. It was fine yesterday, but it failed when I started today.


refactor!: simplify subnet configuration

BREAKING CHANGE: remove subnet object properties network_security_group, route_table and nat_gateway. Add subnet object properties security_group_id, route_table_id and nat_gateway_id.

Depends on hashicorp/terraform-provider-azurerm#27199


DIN Lookalike potential issue

Hello @jimmylao,
I was wondering that whether doing operations on negative and positive sampling would exclude some of the device IDs out from training data ?
If it does then we might get an error at the time of ctr generation for those DIDs which were not present during the training.
Wanted to know your opinion on this.

@sanjaynirmal There is a placeholder in model.py for userID (or device ID) at the beginning of model.py, however, it was not used afterwards, i.e. userID is not used in the model.
While CTR generation, the input data does need to provide DID information to follow the format of input data, however, it may not require the DID exists in training data.
In summary, the potential issue may not happen in reality.


[To rel/1.2] Fix rel/1.2 branch CI issues

Description
This PR cherry pick these CI-issue-fix commits from master branch to rel/1.2.

Python client IT issue
Windows CPP IT issue
Sonar check issue

coverage: 47.953% (+0.001%) from 47.952% when pulling 186bfbd913e9bb19ba9c75e446558ebbc3d30129 on fix_1_2_ci_issues into 12d09e0e17e9aa8208293c6334acaeed403831c6 on rel/1.2.


[Clearing gallery] Applying Foundation's Fix#3410 "the image shift"

Good evening,
I'm currently trying to apply Foundation's fix for image shifting:
https://github.com/zurb/foundation/issues/3410
I'm having troubles with building app.js based on customized foundation.clearing.js. All the time it's rewritten with foundation's default file and then build into app.js
Could you assist me in applying that fix?
Have a nice evening,
versedi

I'll apply the fix as soon as a new foundation version gets shipped.


⚠ ClamAV has degraded performance

In 7e7b9be, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 423 ms

Resolved: ClamAV performance has improved in 4d2c2b5.


Move from geerlingguy.mas to own version

geerlingguy.mas has a number of default packages that are being installed
Run a clone of this and configure defaults
https://github.com/geerlingguy/ansible-role-mas

done


Implement hybrid thread/warp parallel kernel for get_json_object

Instead of selecting either a thread-parallel or warp-parallel kernel depending on the input row size, this approach implements a different hybrid kernel such that:

Each warp always processes at max one input row.
The number of active threads in a warp depends on the number of JSON paths. The number of warps processing one row is computed as ceil(num_path / warp_size).

Tested thread-parallel vs warp parallel vs hybrid kernel, with a small (fingerprint) dataset:
thread par, max path size:
2: 40s
4: 17s
6: 15s
8: 11.8s
10: 9.3s
16: 7.6s
32: 5.9s

warp par, max path size:
2: 19s
4: 13s
6: 13s
8: 12s
10: 11.5s
16: 10.6s
32: 10.2s

hybrid thread/warp par, max path size:
2: 17.2s
4: 11s
6: 10s
8: 8s
10: 7.6s
16: 6.4s
32: 5.6s

build

To be clear the chart is comparing against https://github.com/NVIDIA/spark-rapids-jni/pull/2256#pullrequestreview-2199808677 and I still want to run some more tests, but I think this is good to go.


Add deprecation notice to standalone-cluster plugin

Feature Request
Add a notice at plugin invocation that standalone-cluster is deprecated in this release, pointing to the doc for static-cluster (if #2704 is implemented too)
Describe alternatives you've considered

If we don't crack the release open, it could judst silently disappear in 0.11, but this would be better.
Additional context

Deprecation message should read. something like:
NOTICE: the standalone-cluster plugin and feature are deprecated in this release, and will be remove in v0.11.0. Please see  for the replacement static-cluster feature and how to install it in this release.

This was done as part of https://github.com/vmware-tanzu/community-edition/pull/2504
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Warning - Standalone clusters will be deprecated in a future release of Tanzu Community Edition
                                  Use at your own Risk
                   Checkout the proposal for the standalone cluster replacement:
                   https://github.com/vmware-tanzu/community-edition/issues/2266
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Is that good enough? Or do we want to change that before it goes out? Just let me know @qnetter!

Let's be explicit that it is deprecated in this release (0.10) and will be removed and replaced with the new one in 0.11.

Given how much we've gone back and forth with thing, i wonder if not coding exactly when it will be replaced would be sensible? How about something like:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Warning - Standalone clusters are deprecated and will be removed in a future release
                                  Use at your own Risk
                   Visit the following proposal to learn about the planned replacement:
                   https://github.com/vmware-tanzu/community-edition/issues/2266
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Let’s go with “near-future” - I want  to create a sense of urgency.
Sent from my iPhone
On Dec 10, 2021, at 10:23 AM, joshrosso @.***> wrote:

Given how much we've gone back and forth with thing, i wonder if not coding exactly when it will be replaced would be sensible? How about something like:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Warning - Standalone clusters are deprecated and will be removed in a future release
Use at your own Risk
Visit the following proposal to learn about the planned replacement:
https://github.com/vmware-tanzu/community-edition/issues/2266
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fvmware-tanzu%2Fcommunity-edition%2Fissues%2F2705%23issuecomment-991195130&data=04|01|rklorese%40vmware.com|a0b87b8740a249b6235b08d9bc0a32fa|b39138ca3cee4b4aa4d6cd83d9dd62f0|0|0|637747574263972758|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=lZR%2Ft2bat1x2OO9q3ChP%2BuICTBlvhQNKp9qp6kvXb1U%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACZWVL5JON3JFCLJTOIGG2LUQJAS7ANCNFSM5JXZOOCA&data=04|01|rklorese%40vmware.com|a0b87b8740a249b6235b08d9bc0a32fa|b39138ca3cee4b4aa4d6cd83d9dd62f0|0|0|637747574263982712|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=dFbRwKdkcSz06HEjWtoMpZueSEh35xApCy1dZ%2FBjZ5M%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|rklorese%40vmware.com|a0b87b8740a249b6235b08d9bc0a32fa|b39138ca3cee4b4aa4d6cd83d9dd62f0|0|0|637747574263982712|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=LUmtIgOq75GMDJfoeHZTxJnCb2iZxm9ioJytJqXhD%2Fc%3D&reserved=0 or Androidhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|rklorese%40vmware.com|a0b87b8740a249b6235b08d9bc0a32fa|b39138ca3cee4b4aa4d6cd83d9dd62f0|0|0|637747574263992666|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=H1tLlMPRWcxVvw91cm%2BpkNGzRteiiw31xs%2F6%2FrV6%2FxU%3D&reserved=0.

Cool! So, something like?
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Warning - Standalone clusters are deprecated as of 0.10.0 and will be removed in a near-future release
                                        Use at your own Risk
                         Visit the following proposal to learn about the planned replacement:
                         https://github.com/vmware-tanzu/community-edition/issues/2266
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Exactly.

This has been addressed.


Update configure command menu label

The most common label used for accessing command settings is Configure Command, not Command Preferences.

Thanks, @Palanikannan1437! 🏀

Thanks, @Palanikannan1437! 🏀

Thank you @gtsiolis for the PR 🙌

@Palanikannan1437 I realized we merged this into main instead of develop. This is a good example how https://github.com/gitpod-samples/Gitpod-Raycast-Extension/issues/78 and https://github.com/gitpod-samples/Gitpod-Raycast-Extension/issues/77 could help. 💡


Introduce abstraction for subobjects

This allows for reading / passing-around arbitrary subobjects.

Oh, I like this SubObject idea. I use a different approach which extends the KubeObject to be a sub component of the KRM resource and extend the GVKNN GetXXX() and SetXXX() to support bothmetadata.namespace and namespace (same for metadata.name ) so it can be directly used by sub component like RoleBinding's subject GetNamespace. But I'm struggled on this additional assumptions since it adds additional handling to the existing GVKNN GetXXX and SetXXX. I'll abandon mine.


Option to not generate fields as Optional

Feature Description
Optionals are pain to work with in Java and we already suffer enough on our daily life's.
We should have a option to enable/disable this behaviour.
Proposed Generated Code (Optional)
No response

@esfomeado what would you prefer instead? Leaving them nullable ?

Yes.


Save alert state

Alerts are currently sent directly to HA and always returns none regardless of the actual state. Save a received state to the config or to memory for future retrieval.

That is not true it actually looks for any active effect from HASS state.

That is not true it actually looks for any active effect from HASS state.

I mean the "alert" item, not effects. It's calling "flash" in HA. I don't believe that's something that HA returns when you call effects, so I think the only way to do this is by saving it ourselves.

I mean the "alert" item, not effects. It's calling "flash" in HA. I don't believe that's something that HA returns when you call effects, so I think the only way to do this is by saving it ourselves.

You're right. Got to have some more coffee :-)
Does HA return an attribute containing the state of the "flash" if you set it ?
Actually now that I think of it. This is always a one-off thing.

You're right. Got to have some more coffee :-)
Does HA return an attribute containing the state of the "flash" if you set it ?
Actually now that I think of it. This is always a one-off thing.

It is supposed to return the value of the last alert that was called, even if the alert has already passed. Perhaps a config entry?

It is supposed to return the value of the last alert that was called, even if the alert has already passed. Perhaps a config entry?

I'd say save it to the light config entry indeed.

I'd say save it to the light config entry indeed.


Make predictions with nicaea

I have run nicaea with the cosmology and the n(z) for these 5 bins, I have uploaded a tarball for all results (xip_bin1_bin1.dat, xip_bin1_bin2.dat ... xip_bin5_bin5.dat, then xim, then P_kappa.) Note that P_kappa is really 'ell*(ell+1)C_ell/(2*pi)'
nicaea.zip
No IA were included in these predictions, but we could possibly compare these with the CCL results (again with no IA) once they are available?

Nicaea worked pretty well, and matches CCL over most scales, so I will close this issue as we're moving towards CCL.


fix bug in GetAllAccessibleDatabases where a failed query triggers a panic

If tx.Query fails and returns a non nil error, rows will be nil and the deferred func will panic because rows is nil.
#640

/ready-to-test

/ok-to-merge


Unit testing with karma and jasmine

Hello,
i'm trying to test my application with karma and jasmine but i always get this error:

I think the problem is about its dependecies, in particular zone.js , i tried for hours to solve it without success...
TEST FILE
import 'zone.js';
import 'reflect-metadata';

import {
	inject,
	async
} from '@angular/core/testing';

import { MapService } from '../../common/map.service';

declare var beforeEach: any;
declare var describe: any;
declare var expect: any;
declare var it: any;

describe("MAP SERVICE", function () {

  beforeEach(function () {
  })

  it('should construct', async(inject(
	[MapService], (service) => {
		expect(service).toBeDefined();
  })));

  it("Be sure the latidute and longitude to equal 0 on init", async(inject(
	[MapService], (service) => {
		expect(service.myLocation).toBeDefined();
		expect(service.myLocation.latitude).toBe(0);
		expect(service.myLocation.longitude).toBe(0);
  })));

  it("setMyLocation", async(inject(
	[MapService], (service) => {
		service.setMyLocation(1, 1);
		expect(service.myLocation.latitude).toBe(1);
		expect(service.myLocation.longitude).toBe(1);
  })));

});

KARMA CONFIG
module.exports = function (config) {
  config.set({
    basePath: '',
    frameworks: ['jasmine'],
    files: [
      'app/**/*.js'
    ],
    exclude: [
    ],
    preprocessors: {
    },
    reporters: ['progress', 'live-html'],
    htmlLiveReporter: {
      colorScheme: 'jasmine',
      defaultTab: 'summary',
      focusMode: true
    },
    port: 9876,
    colors: true,
    logLevel: config.LOG_INFO,
    autoWatch: true,
    browsers: [],
    customLaunchers: {
      android: {
        base: 'NS',
        platform: 'android',
        arguments: ['--reporters html,dots']
      },
      ios: {
        base: 'NS',
        platform: 'ios'
      },
      ios_simulator: {
        base: 'NS',
        platform: 'ios',
        arguments: ['--emulator']
      }
    },
    singleRun: false
  })
}

PACKAGE JSON
{
  "description": "NativeScript Application",
  "license": "SEE LICENSE IN <your-license-filename>",
  "readme": "NativeScript Application",
  "repository": "<fill-your-repository-here>",
  "nativescript": {
    "id": "org.nativescript.eventsfinder",
    "tns-android": {
      "version": "2.5.0"
    }
  },
  "dependencies": {
    "@angular/common": "2.4.3",
    "@angular/compiler": "2.4.3",
    "@angular/core": "2.4.3",
    "@angular/forms": "2.4.3",
    "@angular/http": "2.4.3",
    "@angular/platform-browser": "2.4.3",
    "@angular/platform-browser-dynamic": "2.4.3",
    "@angular/router": "3.4.3",
    "nativescript-angular": "1.4.0",
    "nativescript-floatingactionbutton": "^2.2.7",
    "nativescript-geolocation": "0.0.18",
    "nativescript-google-maps-sdk": "^1.4.3",
    "nativescript-oauth": "^1.2.1",
    "nativescript-telerik-ui": "^1.6.0",
    "nativescript-theme-core": "~1.0.2",
    "nativescript-unit-test-runner": "^0.3.4",
    "reflect-metadata": "~0.1.8",
    "rxjs": "~5.0.1",
    "tns-core-modules": "2.5.0"
  },
  "devDependencies": {
    "babel-traverse": "6.4.5",
    "babel-types": "6.4.5",
    "babylon": "6.4.5",
    "jasmine": "^2.5.3",
    "karma": "^1.5.0",
    "karma-html-live-reporter": "^0.1.5",
    "karma-jasmine": "^1.1.0",
    "karma-nativescript-launcher": "^0.4.0",
    "lazy": "1.0.11",
    "nativescript-dev-android-snapshot": "^0.*.*",
    "nativescript-dev-typescript": "~0.3.5",
    "typescript": "~2.1.0",
    "zone.js": "~0.7.2"
  }
}

+1

Hi @mrcesc0,
Thank you for reporting this issue.
I reviewed your case, however, was unable to reproduce this behavior on my side.
On my further research, I found that this could be related to an issue with the socket.io, which makes the communication between the Karma server and the mobile app, more about this you could find here.
Another option could be an issue with the device, which you are using to run the tests. In this case, you could verify, whether you will have the same behavior while using android emulator.
Regarding that to be able to help you further and to verify what is causing this issue, could you send us sample project, which could be debugged locally.

Hi @tsonevn ,
thank you for answering me.
OK, i'll get you back as soon as possible!!!

Hey @mrcesc0,
I've been struggling with zone.js as well. Placing it in dependencies instead of devDependencies fixed it for me.
Besides that, these imports are also important:
import 'reflect-metadata';
import 'nativescript-angular/zone-js/dist/zone-nativescript';
import 'zone.js/dist/long-stack-trace-zone';
import 'zone.js/dist/async-test';
import 'zone.js/dist/fake-async-test';
import 'zone.js/dist/sync-test';
import 'zone.js/dist/proxy';
import 'zone.js/dist/jasmine-patch';

Hopefully this solves your issue as well!

Hey @mrcesc0 I am closing this issue due to  inactivity but please contact us if you have sample project for tests or any additional information  that might help us investigate further

I have the same error and from my examination it has something to do with Nativescript not playing nicely with angular code such as inject.
I think that Nativescript officially does not support Angular testing framework yet and you are expected to find workarounds such as creating your angular object. e.g: myService = new MyService();
@NickIliev , correct me if I'm wrong...

Sorry, I have the function which call RouterExtensions library to navigate. I spy it as the below spyOn(router, "navigate") but It show error properties: Object({ originalStack: 'Error:  : navigate() method does not exist
Please can help me!


python311Packages.aio-geojson-nsw-rfs-incidents: 0.6 -> 0.7

Diff: https://github.com/exxamalte/python-aio-geojson-nsw-rfs-incidents/compare/refs/tags/v0.6...v0.7
Changelog: https://github.com/exxamalte/python-aio-geojson-geonetnz-quakes/blob/v0.7/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 283960 run on x86_64-linux 1

2 packages built:

python311Packages.aio-geojson-nsw-rfs-incidents
python311Packages.aio-geojson-nsw-rfs-incidents.dist


Typo in Documentation ?

Hi,
thanks for this project.
Shouldn't  storedQueries be replaced by storedStatements in stored-statements documentation (or added)?
With storedQueries, I get :
{
  "reqIdx": 0,
  "error": "a stored statement is required, but did not find it"
}

and no   With 2 stored statements at startup.

Thanks for catching this! It was renamed recently, and I totally forgot to update that part of the docs. Should be ok now.


Update gdx-basis-universal to v1.0.0

Here's a little update for gdx-basis-univeral to the latest version.
There's one thing though, I recently found, that most of the modern texture compression formats are not accessible on iOS devices when using the classic robovm  backend. Switching on to robovm-metalangle solves it. So this is a strong recommendation from the library, to couple it only with the latter. In my experience, it's hard to find downsides in migrating to robovm-metalangle. So it would be lovely if there was an option to somehow let users know about the preferred iOS backend when they opt in for this library.

I see no problem with merging this. I don't know anything about the MetalANGLE backend, though, since I've never built any iOS app. Do you think MetalANGLE should be the default for iOS? Are there incompatibilities to be aware of?

 I just spent the whole day trying to figure out why OpenGL on robovm backend doesn't allow specific features on the device where it's clearly supported (HW support for compressed textures to be exact). I didn't dig too deep, it's probably related to the whole OpenGL depreciation thing, so the API in a way stuck somewhere between 2.0 and 3.0 and (intentionally?) hides away some features. So using Metal should be the way to go. However, I know very little about it besides this little case. It's relatively fresh and probably has some little overhead, hard to tell yet. Unless libGDX itself won't promote it as the default backend, I wouldn't recommend that move. But looks very promising for sure.
But the question still stands, unless the users are specifically told to switch backend, they won't know they are in trouble until it's too late. Best to just solve the problem for them from the start. robovm-metalangle may not be the mainstream backend yet, but it's for sure a stable official one, should be totally safe to propose it as an alternative.

I'll ask in the contributing channel on the Discord, see what other people think. I don't even know if robovm-metalangle is something you depend on in addition to RoboVM, or its own complete backend, or what...


Support for HyperGAI/HPT1_5-Air-Llama-3-8B-Instruct-multimodal

Hello team,
It would be so great so have this new multimodal based llama3 model supported with ollama! thanks!
https://huggingface.co/HyperGAI/HPT1_5-Air-Llama-3-8B-Instruct-multimodal
https://github.com/HyperGAI/HPT?tab=readme-ov-file#installation

+1


Neutron driver: convert all boxed comments to normal open source style

Anyone care to review this?

I've also now added PEP8 compliance to this PR.

:+1:


Question: How to create a bullet list?

Goal
I am trying to create a bullet list in my GenericStyledArea, that would look like this:

line 1
line 2

I have read Support for numbered and unnumbered Lists #384.  So until that feature is implemented, I am trying to work with the existing version of RichTextFX.  All my attempts have produced unsatisfactory results.
Attempts
I have tried the following approaches so far.  I present these to perhaps stimulate any thoughts or variations:

I used CSS to style the paragraph with "-fx-padding: 0 0 0 40;"  (successful), and then place a bullet (just an asterisk at present) as the first Text segment in the paragraph, and to style that with "-fx-translate-x: -20".  That almost works - the bullet is properly positioned, but when the list item itself requires multiple lines, the first line is incorrectly indented at <40 + width of bullet>, while the other lines are correctly indented at 40.  e.g.,

  this is an example of a multiline list item, demonstrating that the first line is incorrectly indented a bit further than successive lines.  xxx xxxxx xx xxxx xxx xxxxxxxx xxx xxxxx xx xxxx xxx xxxxxxxx xxx xxxxx xx xxxx xxx xxxxxxxx xxx xxxxx xx xxxx xxx xxxxxxxx.

I have created a new SEGMENT class to hold the bullet, whose charAt() and getText() return an asterisk, but whose length() returns 0 (to try to remove that bullet-width indent) - no luck
I have searched for JavaFX CSS styling for a hanging indent
Also searched for overlays
And just lots of Googling

Note that I am a beginner at CSS. :)
Does anyone know a way I could achieve this?  THANKS!
Environment info:
RichTextFX Version: 0.10.1
Flowless 0.6.1
ReactFX 2.0-M5
UndoFX 2.1.0
WellBehavedFX 0.3.3
Operating System: Windows 10
Java version: 8u181

Sorry for the delay it took me a while to experiment and figure this out.
You could try using a paragraph graphic factory like I've done here to create the bullets and add that to the text area (see here in this prototype RichTextDemo).
I've added icons to RichTextDemo courtesy of @afester from #824 (as well as using code from his playground) and also modified ParStyle to use a new Indent pojo.
Doing it this way will give you complete control of the bullet code without depending on RichTextFx "internals".

wonderful, I will try that!  no problem, about the time you needed; I am just grateful for your efforts.  I am coming to understand RichTextFX slowly and surely, and I really like it.

Jugen,
Sorry for my delay (family emergency, holiday).  And thanks again for your work on my question!
Your demo works perfectly, until I add a call to area.setWrapText(true) - then, for a list of bulleted items, where one list item wraps into multiple lines, the bullet is centered vertically on the N lines of text.  I was hoping for the bullet to be aligned with the just first line of those N lines.  I have looked at the LineIndicator demo from RichTextFX, and when setWrapText(true) is added there, it gives similar behavior.  I have googled for any solutions for this, but found none.
Also, the comment on get/setParagraphGraphicFactory() says the node "is positioned to the left of the first character in a paragraph's text.",  but I cannot find a way to force that, with wraptext on.

Is there a way to position the bullet on the first line of the N lines?

I've updated the paragraph graphic factory example to wrap the bullet node in a VBox so that the bullet remains on the top line when wrapping occurs.

That works perfectly.  Thank you so much!


12 words mnemonic

any wallet out there using a 12 words mnemonic?
Does MnemonicKey accepts 12 words?

And an hex raw privateKey?

@hanjukim I noticed that this works with 12 words:
const mk2 = new MnemonicKey({
  mnemonic:
    '< 12 words >',
});

any drawback using it?

Oh I did not know it. I am not 100% sure but I guess it is fine then?


Add Navbar to About Us and Login Pages

Describe the feature
Currently, the "About Us" and "Login" pages do not have a navbar, making it difficult for users to navigate to other sections of the site from these pages. Adding a navbar to these pages will enhance the user experience by providing easy access to other parts of the website.
Expected Behavior:
Both the "About Us" and "Login" pages should have a navbar similar to the rest of the site or a new navbar , allowing users to easily navigate to other pages such as Home, Contact, etc.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I have checked the existing issues
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@srivastav2006 fine you can work on it.

I kindly request to be assigned to this issue. As a Technical Executive at the IEEE CUIET Organization, I am well-positioned to address this matter. I am committed to delivering optimal results and have prior experience with similar projects, which I believe will enable me to make a meaningful contribution.
reference for prior work / projects :-|
https://www.linkedin.com/in/akshit-verma-596a0824b/


how to use the python version of chrome for testing?

how to use the python version of chrome for testing?
I downloaded it, specified it in path (I had to rename it to chromedriver to make the system understand what I wanted), run the code in pycharm, the chrome for testing window opens, and that's it. even the link doesn't go through.
The error indicates that the Chrome driver cannot connect to the service. Windows platform

Chrome for Testing is the infrastructure that makes the binaries available. This repository specifically hosts the dashboard and the API endpoints.
There might be various tools that consume the CfT JSON endpoints and make it easy to download the various binaries (see https://developer.chrome.com/blog/chrome-for-testing/#how-can-i-get-chrome-for-testing-binaries) but any issues with those tools are outside the scope of this repository.


Some Schedules Direct missing station improvements.

It turns out that sometimes some airings actually do end up being found using the method we added to the Wizard and this prevents the station from being invalidated and re-downloaded. I changed it to just check for an airing at this exact time and if it doesn't exist or is a No Data airing, we invalidate the station. This is also based more strongly on data we need now instead of data we have now.
I also added some methods I added for Seeker2 to create timed/manual recordings because I really didn't like the idea of creating an airing outside of the Wizard within Seeker. It just feels like the wrong place to do this. I'm not ready to commit the Seeker2 core changes yet since I'm still slowly working out a few small, but known issues.

I also fixed a null pointer exception that results from the fact that we sometimes have aliases without a normal person associated.


[Feature Request]: Evaluate MLTransform implementation without CoGroupByKey step

What would you like to happen?
MLTransform currently each row into columnts that has to be preprocessed by TFT and columns that should not, due to TFT requiring a schema for all colmunts. This creates a GBK step and requires adding a unique key per each element.
We can try out different implementations that don't require a GBK, for example by encoding not-to-be processed columns as bytes and passing them through TFT, then decoding. It might reduce the total cost or  improve performance.
Issue Priority
Priority: 2 (default / most feature requests should be filed as P2)
Issue Components

[X] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam YAML
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

not-to-be processed columns as bytes and passing them through TFT

I heard that TFT might allow supplying a key with each record, we could encode and pass columns without schema in  key portion of the record if it is unused now. in this case, keys don't have to be unique.


ARROW-4324: [Python] Triage broken type inference logic in presence of a mix of NumPy dtype-having objects and other scalar values

In investigating the innocuous bug report from ARROW-4324 I stumbled on a pile of hacks and flawed design around type inference
test_list = [np.dtype('int32').type(10), np.dtype('float32').type(0.5)]
test_array = pa.array(test_list)

# Expected
# test_array
# <pyarrow.lib.DoubleArray object at 0x7f009963bf48>
# [
#   10,
#   0.5
# ]

# Got
# test_array
# <pyarrow.lib.Int32Array object at 0x7f009963bf48>
# [
#   10,
#   0
# ]

It turns out there are several issues:

There was a kludge around handling the numpy.nan value which is a PyFloat, not a NumPy float64 scalar
Type inference assumed "NaN is null", which should not be hard coded, so I added a flag to switch between pandas semantics and non-pandas
Mixing NumPy scalar values and non-NumPy scalars (like our evil friend numpy.nan) caused the output type to be simply incorrect. For example [np.float16(1.5), 2.5] would yield pa.float16() output type. Yuck

In inserted some hacks to force what I believe to be the correct behavior and fixed a couple unit tests that actually exhibited buggy behavior before (see within). I don't have time to do the "right thing" right now which is to more or less rewrite the hot path of arrow/python/inference.cc, so at least this gets the unit tests asserting what is correct so that refactoring will be more productive later.

+1