Passing parameter to script through call_service failing

hass --version
0.105.3
Description:
I have the following testing script:
fanspeed:
  sequence:
  - service: system_log.write
    data_template:
      level: info
      message: 'Setting fan speed to: ({{speed}})'

From within HomeAssistant Developer Tools SERVICES I can run the following:
Service:  script.fanspeed
Service Data (YAML, optional)
1 "speed": "off"
CALL SERVICE

Which results in the expected log message:
[homeassistant.components.system_log.external] Setting fan speed to: (off)
Although I am trying to get this to work with IFTTT, the problem can more easily be reproduced with curl.  Using the following:
curl -s -H "Content-Type: application/json" -d '{ "action": "call_service", "service": "script.fanspeed", "speed": "off" }' https://mydomain.com/api/webhook/da2c13...

Which results in:
[homeassistant.components.system_log.external] Setting fan speed to: ()
Note the "speed" parameter is null.
I have tried all of the following payloads without success:
-d '{ "action": "call_service", "service": "script.fanspeed", "speed": "off" }'
-d '{ "action": "call_service", "service": "script.fanspeed", { "speed": "off" } }'
-d '{"action": "call_service",  "service": "script.fanspeed", "data": { "speed": "off"}  }'
-d '{"action": "call_service",  "service": "script.fanspeed", "variables": {"speed": "off" } }'
-d '{"action": "call_service",  "service": "script.fanspeed", "fields": {"speed": "off" } }'

It was working in 0.100.3 using the OLD IFTTT method with the REST interface and api_password.  Since upgrading to 0.105.3 deprecated the old method I have not been able to get the NEW IFTTT integration using "call_service" to work in this case.  I have a dozen other integrations which do all work, but this is the only one trying to pass a parameter to a script through call_service.
The use of the constant text "off" is only for testing.  Once working, I will change it to <<<{{TextField}}>>>.
Operating Environment:
Home Assistant Core on Gentoo Linux installed with pip.
Integration/Platform:
https://www.home-assistant.io/integrations/script/
Traceback:
No traceback results.  Log shows either 'null' parameter or no message at all (meaning the script is not called).
My Email address:
<EMAIL_ADDRESS>

Can someone at least confirm that this is a bug?

Open dev tools -> events. In "Listen to events" card, add ifttt_webhook_received and start listening, now trigger your curl. You can now see all the data that is available in the event and create an automation that triggers on that event.

Thank you!  What a great troubleshooting tool!  It displayed this:
Event 1 fired 4:32 AM:
{
    "event_type": "ifttt_webhook_received",
    "data": {
        "action": "call_service",
        "service": "script.fanspeed",
        "speed": "off",
        "webhook_id": "da2c1308b200f32b47b0cc91e980d1aad0e901be1133ebf12a56a607b28cd166"
    },
    "origin": "LOCAL",
    "time_fired": "2020-02-17T11:32:16.684731+00:00",
    "context": {
        "id": "aa9636dce7c04dc2b16a84a5c3795c28",
        "parent_id": null,
        "user_id": null
    }
}

So I changed the value_template in my script to:
message: 'Setting fan speed to: ({{ data.speed }})'
Now it says:
Error rendering data template: UndefinedError: 'data' is undefined
I am still lost... :(

Please help!  I am unable to find the solution despite many hours of searches.


feat(metadata): add ability to update metadata manually

functionality to allow updating of the metadata of a track for streams

I'd love to see this feature in react-native-track-player.
Is there any reason you've stopped work on it?


Unable to compile Hello World. Build did NOT complete successfully. Have tried almost all solutions already posted

Hello! I just recently installed mediapipe using the instructions on https://g3doc.corp.google.com/third_party/mediapipe/g3doc/getting_started/install.md?cl=head
I ran Hello World using: bazel run --copt -DMESA_EGL_NO_X11_HEADERS --copt -DEGL_NO_X11
mediapipe/examples/desktop/hello_world:hello_world
However, when running "Hello World" and any other model, I get the following error:
/usr/local/google/home/adiljmalik/mediapipe/mediapipe/calculators/core/BUILD:583:11: C++ compilation of rule '//mediapipe/calculators/core:pass_through_calculator' failed (Exit 1): gcc failed: error executing command /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer '-std=c++0x' -MD -MF ... (remaining 51 argument(s) skipped)
Use --sandbox_debug to see verbose messages from the sandbox gcc failed: error executing command /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer '-std=c++0x' -MD -MF ... (remaining 51 argument(s) skipped)
Use --sandbox_debug to see verbose messages from the sandbox
In file included from :
/usr/include/stdc-predef.h: In substitution of 'template<class _Functor, class, class> std::function<std::unique_ptrmediapipe::internal::CalculatorBaseFactory()>::function(_Functor) [with _Functor = ;  = ;  = ]':
mediapipe/calculators/core/pass_through_calculator.cc:96:1:   required from here
/usr/include/stdc-predef.h:32:94: internal compiler error: Segmentation fault
32 |    whether the overall intent is to support these features; otherwise,
|                                                                                ^
0x7f5dc5067d5f ???
./signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0x7f5dc5052d09 __libc_start_main
../csu/libc-start.c:308
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <file:///usr/share/doc/gcc-10/README.Bugs> for instructions.
Target //mediapipe/examples/desktop/hello_world:hello_world failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 4.817s, Critical Path: 4.68s
INFO: 6 processes: 6 internal.
FAILED: Build did NOT complete successfully
FAILED: Build did NOT complete successfully
If someone could guide me, I would appreciate it!

Hi @ajm133, Could you please provide the steps to reproduce the above error and which platform are you trying the above. Thanks!

Running on gcc (Debian 10.2.1-6+build2) 10.2.1
cd $HOME
git clone https://github.com/google/mediapipe.git
cd mediapipe
sh ./ setup_opencv.sh
sudo apt-get install mesa-common-dev libegl1-mesa-dev libgles2-mesa-dev
export GLOG_logtostderr=1
bazelisk run --copt -DMESA_EGL_NO_X11_HEADERS --copt -DEGL_NO_X11
mediapipe/examples/desktop/hello_world:hello_world

Hi @ajm133, Could you please confirm you are trying to install on GPU support Linux machine  (via mesa drivers). Thanks!

I am. Also, i tried running it on the CPU but was getting the same error. Thus, I think it is not the cpu/gpu support problem, but rather something else.

The error message tells us that's an internal compiler error. You probably can try some other version of gcc such as gcc9. See instructions at https://linuxconfig.org/how-to-switch-between-multiple-gcc-and-g-compiler-versions-on-ubuntu-20-04-lts-focal-fossa.


Force quantile tensors to be float; prevents accidents

In particular, sometimes this was failing with:
RuntimeError: quantile() input tensor must be either float or double dtype

Fixes https://github.com/pytorch/pytorch/issues/103054
Signed-off-by: Edward Z. Yang<EMAIL_ADDRESS>

perf test is flaky. force-merging


Add option for client with custom http client

This PR adds the option to use a custom http client to use for example oauth2.

This also could be use Basic Auth


Problem with transition

Vue.js version
1.0.17
Reproduction Link
http://worldofwarships.com/en/community/accounts/teams/
Steps to reproduce
Press the button "load more" fast as possible
What is Expected?
In one time this button can be blocked
What is actually happening?
I have overlay layer for table and button
overlay:

transtion:
.v-simple-opacity
  &-transition
    transition: opacity .2s ease-out
    opacity: 1

  &-enter,
  &-leave
    opacity: 0

and then i do async query,  i change stateOfLayer at true,
after response i set stateOfLayer = false
and some times overlay layer not receive the property display: none,
only class .v-simple-opacity-leave
What I have noticed from experimentation:
if response is faster than the duration of the animation, then sometimes  a bug occurs
and if after response i set stateOfLayer = false with delay more than 200ms, bug not accurs
I think there is problem with vue transition system.
P.S. This bug can live maximum about 2-3 days, after we release patch, where i add delay for change stateOfLayer and Sorry for my english.

The live link seems to be down, do you have a simpler repro, e.g. a jsfiddle?

ok, i try repeat it at jsfiddle

I couldn't repeat this at jsfiddle.
Сan a Transition Directive have some difficulty in components with a large number of reactive variables, or this has nothing to do?

Unfortunately I can't really triage this without a testable repro - but feel free to open a new issue when you run into it later (and hopefully reproducible)

Okay)
пн, 14 марта 2016 г., 21:10 Evan You<EMAIL_ADDRESS>
Closed #2425 https://github.com/vuejs/vue/issues/2425.
—
Reply to this email directly or view it on GitHub
https://github.com/vuejs/vue/issues/2425#event-589138682.


allow JsonWebKeys that contain an asymmetric key

Allow a JsonWebKey as SigningCredentials when it contains an asymmetric key.
As proposed in #768

Hi @igarciaolaizola, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

Could you add a test please?

Could you add a test please?

I've added 2 test cases, JWK with asymmetric key (successful case) and JWK with symmetric key (failure case).

thanks!


Incorrect code coverage reported in Svelte example

Describe the bug
When running the tests of the Svelte example, the test coverage is incorrectly reported with an uncovered line while simultaneously reporting 100% coverage an all statements, functions and lines:
$ yarn coverage
yarn run v1.22.19
$ vitest run --coverage

 RUN  v0.29.3 /home/oskar/git/vitest/examples/svelte
      Coverage enabled with c8

 ✓ test/basic.test.ts (1)
 ✓ test/hello.test.ts (2)

 Test Files  2 passed (2)
      Tests  3 passed (3)
   Start at  17:17:52
   Duration  1.13s (transform 88ms, setup 0ms, collect 342ms, tests 88ms)

 % Coverage report from c8
--------------|---------|----------|---------|---------|-------------------
File          | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
--------------|---------|----------|---------|---------|-------------------
All files     |     100 |        0 |     100 |     100 |
 Hello.svelte |     100 |        0 |     100 |     100 | 6
--------------|---------|----------|---------|---------|-------------------
Done in 1.71s.

Related to #1893
Reproduction
$ cd examples/svelte
$ yarn coverage

System Info
System:
    OS: Linux 6.2 Arch Linux
    CPU: (12) x64 Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
    Memory: 24.70 GB / 31.28 GB
    Container: Yes
    Shell: 3.6.0 - /usr/bin/fish
  Binaries:
    Node: 19.7.0 - /usr/bin/node
    Yarn: 1.22.19 - /usr/bin/yarn
    npm: 8.19.2 - /usr/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Firefox: 110.0.1
  npmPackages:
    @vitest/coverage-c8: ^0.29.3 => 0.29.3
    @vitest/ui: latest => 0.29.3
    vite: latest => 4.2.0
    vitest: latest => 0.29.3

Used Package Manager
yarn
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Svelte will not work properly with code coverage tools.
When Svelte code is transpiled it includes generated code in the source maps. This generated code is not part of your source codes and causes incorrect code coverage results. c8 and istanbul both rely on source maps.
This is not an issue of Vitest but Svelte itself:  https://github.com/sveltejs/svelte/issues/7824


net-mgmt/zabbix-agent: upgrade to 4.0 release series

With the release of Zabbix 4.0, the previous version 3.4 is now unsupported.
Our Zabbix Agent plugin should be moved to the current release.
This change is targeted for the upcoming OPNsense 19.1 release.
Refs #859

we can already switch -devel to zabbix4-agent for 18.7.10 if you want?
with version 4 I'd not like to split agent and proxy between different minor versions so we should stay on the same LTS version.

we can already switch -devel to zabbix4-agent for 18.7.10 if you want?

Ayntime, to ensure it's in working condition for 19.1.

Done. Since stable/19.1 is branched from master it'll be automatically included in 19.1-RC1 and up.


Optimize usage of x registers

Also reduce stack usage a little bit when decoding. Impact on Sudoku benchmark is measurable but less than 1%.
These changes are made under both the "Apache 2.0" and the "GNU Lesser General
Public License 2.1 or later" license terms (dual license).
SPDX-License-Identifier: Apache-2.0 OR LGPL-2.1-or-later

So if I understand the gist of this change:

Write directly to xregs (which is already declared), instead of in directing through ctx
Don’t store the destination register type in a local variable, when decoding

That's what the title and the comment of this PR are about indeed.
There is an additional side optimization: WRITE_REGISTER and READ_REGISTER macros now use the pointer to the register directly instead of performing an indexed indirection.

Is there anything else of significance? I am not sure I fully understand the new *_UNSAFE macros. Can you explain their rationale?

UNSAFE macros are for y registers that can be moved by a GC. In the previous version, because the pointer was recomputed when calling WRITE_REGISTER, it was always safe. New macros should distinguish between cases where we don't need to compute the pointer (the non-UNSAFE variants) and cases where it's not safe to rely on it.

Maybe I have some kind of bias, but naming suggests me the opposite: UNSAFE tells me that it does something without additional care.
What about SAFE since it is safer than regular WRITE_REGISTER?
CC @fadushin

Looks good, I'm just unsure if another name would be better than UNSAFE.

Good catch, this was renamed GC_SAFE.


chore(layers): add release pipeline in GitHub Actions

Issue number: #1183
Summary
We have been using internal pipeline to release public layers for with powertools. Because of the initial design we could not ship public layers to all commercial regions. This PR introduces a CDK project and GitHub action workflow and we will integrate it into the release process in this repository. The goal is to deploy public layers after a release and update the documentation with the latest ARNs automatically.
Changes
The CDK project has two stacks LayerStack and CanaryStack. We use CDK customer resource capability to run a canary function after the layer deployment so we can verify that the layer works. We also need to track layer ARNs, powertools and the available region, so we can put this information into our documentation. To achieve that, there is dedicated version tracking application. After a successful deployment the canary functions sends an event with all the details. This application is maintained separately. The only information we need is the event bus ARN to send the data.
To deploy into an AWS account we assume a role by using GitHub OIDC configuration. We store the target account and the role name as secrets (though the target account will be public after the public layer is released). The OIDC configuration for target accounts will be provided, no additional work is required in this project.
Open tasks

[x] add secrets
[x] add python caching for workflow jobs

Checklist
If your change doesn't seem to apply, please leave them unchecked.

[ ] Meet tenets criteria
[ ] I have performed a self-review of my this change
[ ] Changes are tested
[ ] Changes are documented
[ ] PR title follows conventional commit semantics

Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

View rendered layer/README.md

This is so so so exciting. I can't believe we're finally at the stage we will have Layers with Extras, ARM, all commercial regions, except the special ones (yet), and more importantly tightly integrated with the release process now.
Can't thank you enough!

I have configured the GitHub OIDC connection to AWS accounts and added the secrets used in for layer deployments.


Introduction and Check-in

Summary
Provide context on the service and how to get access.
Provide description of the authentication options and how to authenticate into the providers.

Rebased and ready for review

handled in #4


Your requirements could not be resolved to an installable set of packages.

Flarum0.1.0-beta.15
PHP7.4.21
MySQL10.4.19-MariaDB
composer require justoverclock/og-meta-tag:"*"
./composer.json has been updated
Running composer update justoverclock/og-meta-tag
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires justoverclock/og-meta-tag * -> satisfiable by justoverclock/og-meta-tag[0.1.0].
- justoverclock/og-meta-tag 0.1.0 requires flarum/core ^1.0 -> found flarum/core[v1.0.0, ..., v1.0.4] but it conflicts with your root composer.json require (^0.1.0).
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.

can u post here your php flarum info output?


Automatic update of nested custom tags

Maybe I'm doing something wrong, but in the following example, whenever I change outer.foo, the inner component is not updated (i.e. the opts object is not updated after it has been mounted).
I was expecting the data={foo} "binding" to be updated each time foo is changed in outer.
<outer>

Outer

  <inner data={foo}></inner>

  this.foo = "test";
</outer>

<inner>

{data}

</inner>

I would have to listen on("update", ...) in the inner component, which couples the inner and outer component a lot more than I want to.

The child updates itself automatically, you just must write { opts.data }. Here's a working demo
http://jsfiddle.net/0hr6s5s6/

How to deal with async updates?
<inner>
  this.on('update', function() {
    asyncInner(this.opts.dataId, function(data) {
     this.opts.data = data
     this.update() // Endless loop incomming
   })
  })
</inner>

https://github.com/tipiirai: thanks a lot, this works perfectly!

koanda: for me, this issue is closed, do you want to open another one for your question?


Migrated ConfigurationManagementServiceImplTest to use new annotations issue#1165

@carlspring I believe this is completed.
Edit: Still WIP

@carlspring: I think this should be closed, because it has already been migrated,

@ptirador : Thanks for following up on this and for letting me know!


IllegalArgumentException during "lein run" while working fine in "lein repl"

I'm using clara-rules 0.11.1.
First the code:
(ns claratest.core
  (:gen-class)
  (:require [clara.rules :refer :all]))

(defrecord Fact [])

(defquery get-facts []
  [?facts <- Fact])

(defn- run []
  (-> (mk-session)
      (fire-rules)
      (query get-facts)))

(defn -main
  "I don't do a whole lot ... yet."
  [& args]
  (println "Hello, World!")
  (run)
  (println "Bye, World!"))

Running it in the REPL works fine:
claratest.core> (run)
()

but via lein run it throws an IllegalArgumentException, saying that "The query [...] is invalid or not included in the rule base." :
% lein run
Hello, World!
Exception in thread "main" java.lang.IllegalArgumentException: The query {:lhs [{:type claratest.core.Fact, :constraints [], :fact-binding :?facts}], :params #{}, :name "claratest.core/get-facts"} is invalid or not included in the rule base., compiling:(/private/var/folders/th/f2ks7qjn0g52279rdfnmjcsr0000gn/T/form-init5370267113791774844.clj:1:125)
	at clojure.lang.Compiler.load(Compiler.java:7391)
	at clojure.lang.Compiler.loadFile(Compiler.java:7317)
	at clojure.main$load_script.invokeStatic(main.clj:275)
	at clojure.main$init_opt.invokeStatic(main.clj:277)
	at clojure.main$init_opt.invoke(main.clj:277)
	at clojure.main$initialize.invokeStatic(main.clj:308)
	at clojure.main$null_opt.invokeStatic(main.clj:342)
	at clojure.main$null_opt.invoke(main.clj:339)
	at clojure.main$main.invokeStatic(main.clj:421)
	at clojure.main$main.doInvoke(main.clj:384)
	at clojure.lang.RestFn.invoke(RestFn.java:421)
	at clojure.lang.Var.invoke(Var.java:383)
	at clojure.lang.AFn.applyToHelper(AFn.java:156)
	at clojure.lang.Var.applyTo(Var.java:700)
	at clojure.main.main(main.java:37)
Caused by: java.lang.IllegalArgumentException: The query {:lhs [{:type claratest.core.Fact, :constraints [], :fact-binding :?facts}], :params #{}, :name "claratest.core/get-facts"} is invalid or not included in the rule base.
	at clara.rules.platform$throw_error.invokeStatic(platform.cljc:5)
	at clara.rules.platform$throw_error.invoke(platform.cljc:5)
	at clara.rules.engine.LocalSession.query(engine.cljc:1174)
	at clara.rules$query.invokeStatic(rules.cljc:48)
	at clara.rules$query.doInvoke(rules.cljc:38)
	at clojure.lang.RestFn.invoke(RestFn.java:425)
	at claratest.core$run.invokeStatic(core.clj:13)
	at claratest.core$run.invoke(core.clj:10)
	at claratest.core$_main.invokeStatic(core.clj:19)
	at claratest.core$_main.doInvoke(core.clj:15)
	at clojure.lang.RestFn.invoke(RestFn.java:397)
	at clojure.lang.Var.invoke(Var.java:375)
	at user$eval5.invokeStatic(form-init5370267113791774844.clj:1)
	at user$eval5.invoke(form-init5370267113791774844.clj:1)
	at clojure.lang.Compiler.eval(Compiler.java:6927)
	at clojure.lang.Compiler.eval(Compiler.java:6917)
	at clojure.lang.Compiler.load(Compiler.java:7379)
	... 14 more

After scratching my head a bit I found out that you can avoid this Exception by replacing (mk-session) with (mk-session 'claratest.core), thus stating the "rule namespace(s)" explicitly.
Not sure it's a bug as it might be the result of some AOT compilation stuff. However, I think most people would expect it to at least behave consistently during both lein repl & lein run (either both working or both failing).

Hey Oliver,
I agree this is surprising. I think the problem is that lein run doesn't set the current namespace to the that of the main program. Clara looks at Clojure's *ns* var to determine what rules to load if none are provided, and if you add this line to your -main function, I think you'll see the "user" namespace.
(println "In namespace: " (ns-name *ns*))

So Clara scans that namespace for rules, and of course they aren't there. I'm guessing when using the REPL you're running in your claratest.core namespace, so ns is set to the expected value.
An alternative would be either to explicitly state the namespace (as you found), or to statically define your ruleset, like so:
(def empty-session (mk-session))

(defn- run []
  (-> empty-session
      (fire-rules)
      (query get-facts)))

This works because (mk-session) is run when the claratest.core namespace is being loaded, so ns is pointing at it.
Thanks for bringing this up. I'm not sure there is a lot we can do in Clara for this case, but if nothing else we should be able to document this better. (When playing with this, I also noticed that the defsession macro isn't working quite like you might expect here, which is something we can fix.)

Hey Ryan,
first of all thanks for your quick answer.
Your assumption about this *ns* stuff seems to be correct. The namespace during lein run is indeed user.
Also, when switching to the user namespace in the REPL and then calling (claratest.core/run) (after making it public) raises the same exception.
I suppose this means that I was just lucky to not encounter this error in the REPL. I simply wasn't aware of that mk-session has to get hold of the specific namespace, which seems obvious when thinking about it.
Thus, making this behavior more explicit in the docs would for sure be of great help to new users and the workarounds provided seem sufficient (for me at least).
Thanks again. If I can be of any help then just let me know.

Alright, I clarified the ns behavior in the mk-session Clojure doc in the above commit. I don't think there's anything more to do here so I'm going to go ahead and close this, but we can reopen if you disagree, or create new issues  for further work.


PHOENIX-4900 Modify MAX_MUTATION_SIZE_EXCEEDED and MAX_MUTATION_SIZE_…

…BYTES_EXCEEDED exception message to recommend turning autocommit off for deletes

@twdsilva updated error msg

+1 , thanks @yanxinyi


Allow for removing the id attribute in Native.Graphics.Element.updateProps

There is some code here ...
https://github.com/elm-lang/core/blob/3.0.0/src/Native/Graphics/Element.js#L580-L583
... which updates the id of a DOM node if the tag of an Element has changed.
Now, if the new tag is an empty string, this code will set the id of the DOM node to an empty string, which probably isn't ideal -- it would probably be better to call removeAttribute in that case to remove the id.
This would correspond better to the setProps case here ...
https://github.com/elm-lang/core/blob/3.0.0/src/Native/Graphics/Element.js#L94-L97
... since, in the setProps case, the id attribute is not created at all if it is equal to an empty string.
Now, as far as I know, the existing behaviour does not cause any practical problems. So, I'm not suggesting that it is important to change this -- I just thought I'd mention it in case it was useful at some appropriate moment.

Sorry for the slow reply. It has been busy times. All the Graphics.* modules have moved to evancz/elm-graphics so it makes sense to retarget stuff like this.
Is it possible to say this in a clearer way? Problem is not clear to me.


Rename groupSortWith to groupSortBy

Haskell sorting functions have traditionally used 'By' rather than 'With' for the fully parameterised variants.

Fixed


Add Other Navigators from React Navigation (Drawer, Bottom Tab, Top Tab etc...)

Objective
We should have other React Navigation navigators integrated with proper typescript support on this template to aid faster development of common navigation patterns. At the very least, we should have the following navigators and use cases covered.
Navigators

[x] Drawer
[x] Material Bottom Tabs
[x] Material Top Tabs

Use Cases

[ ] Stack Inside Drawer
[x] Tab Inside Drawer
[ ] Stack inside Tab

There are lots of potential nesting use cases and we can't cover them all. for now only Tab inside Drawer is covered. We will consider other use cases if issues are raised in the future.


Update documentation to mention that preview does not work with windows

Hey there 👋 ,
I just added to the documentation that preview does work with windows.
Also modified the documentation of course: https://github.com/huggingface/course/pull/389

thanks a lot !


chore: add nohoist to site deps

Pull Request Checklist

[ ] Did you add new tests and confirm existing tests pass? (yarn test)
[ ] Did you update relevant docs? (docs are found in the site folder, and guidelines for updating/adding docs can be found in the contribution guide)
[ ] Do your commits follow the Conventional Commits standard?
[ ] Does your PR title also follow the Conventional Commits standard?
[ ] If you have a breaking change, is it correctly reflected in your commit message? (e.g. feat!: breaking change)
[ ] Did you run lint (yarn lint:check) and fix any issues? (yarn lint:write)
[ ] Did you follow the contribution guidelines?

PR-Codex overview
This PR focuses on adding the @tanstack/react-query library and updating tailwindcss version in package.json.
Detailed summary

Added @tanstack/react-query library version 5.28.9
Updated tailwindcss to version 3.4.3

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

fixed in vercel actually


Too many unexpected TcpConnect Event

Describe the bug
The log tells me that I have received a lot of unexpected connection events.
Was that a problem with my network or just a program mistake? Please give me some help
How to reproduce?
Set up kindling-agent and open tcpMetrics.
Screenshots

Environment (please complete the following information)
Both show on RHEL 7.9 kernel 3.10.0-1160-31 and Kylin 4.19.90-25 in EBPF mode

Could you enable the debug level logs of tcpconnectanalyzer? There should be some TCP connection events. It would be helpful If you could attach these events here.


Remove access_token from gist loading.

GitHub has deprecated use of access_token in query parameters and is email spamming us nonstop about it.  (dozens of emails a day)
Gists can be read anonymously with a rate-limit of 60 requests per hour per client IP address.
Since we stopped using gists for Sandcastle example code two years ago, the gist codepath is only for extremely old examples, so the rate limit is unlikely to be an issue in practice.
Also someone with the credentials for @Cesium-Sandcastle needs to revoke the old access_token and stop the endless deluge of emails.  Also note that account is still using an agi.com email address.
Fixes #8593

Thanks for the pull request @shunter!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

Would anyone mind if we use password-reset to gain access to the account and revoke the token?  It's driving us nuts.

Tested loading a gist without a token, it works when you're under the rate limit.  Since gists are deprecated anyway, this change shouldn't cause any harm.  Merging.


Create mocking and tests for external API calls

The API calls to both Typeform and to Seamless Docs should be able to deal with a variety of responses, and should log information where necessary.

This is closed with the merging of #40


ActionResult.CONSUME_PARTIAL is not documented

What, I didn't even know this thing exists! Definitely needs documentation on their usages and examples

It's only used for one scenario in vanilla, so I'm a bit confused on how it would be used as well. It is considered to be accepted just like ActionResult.SUCCESS and ActionResult.CONSUME, though.

Yeah, from the class we can see it probably simply doesn't swing hand and doesn't increase usage stats. Other side effects and use cases definitely worth exploring as well.


fix(android): remove jcenter repository

On February 3 2021, JFrog announced that they will be shutting down Bintray and JCenter
So remove jcenter() and replace it with mavenCentral().
Upgrade also some necessary tools for react native like Flipper to version 0.99.

Hi @zplata, jcenter repository is currently down. If you don't mind prioritizing this pull request, I'm sure others will appreciate it.

Thanks @chreck for adding this! I'll do some quick testing today and if all looks good, will get this merged and released in a next patch version


ReflectionException in Container.php line 736: Class LucaDegasperi\OAuth2Server\Middleware\OAuthMiddleware does not exist

Hey guys,
I get this error:
ReflectionException in Container.php line 736:
Class LucaDegasperi\OAuth2Server\Middleware\OAuthMiddleware does not exist

When trying to add the middleware to my controller via:
    public function __construct()
    {
        $this->middleware('oauth');
    }

Any ideas why this is happening and how to fix?
If I use the WithoutMiddleware trait in my unit tests it works though. But the normal endpoints return that error.

I'm getting a similar error when trying to use the check-authorization-params middleware.
Class LucaDegasperi\OAuth2Server\Middleware\CheckAuthCodeRequestMiddleware does not exist
Any ideas?

Which version of this package are you using?

Managed to fix it changed from 4.0 to 4.1@dev in my composer. json

I can't actually seem to use version 4.1? I can't see it tagged in the repo, and when I update I get
Problem 1
    - The requested package lucadegasperi/oauth2-server-laravel 4.1@dev could not be found.

Put either dev-master in the version or 4.1.*@dev, if you're unsure as to which version to use just check the page on packagist https://packagist.org/packages/lucadegasperi/oauth2-server-laravel.

Ahhh brilliant! Thanks, that sorted it.

When I run $ php artisan vendor:publish  now, it returns Nothing to publish for tag []. I raised a separate ticket but no one's responding...

I am using L5 and 4.1.*@dev and I am still getting this error.  When I went into the vendor folder for LucaDegasperi, I can't find a class with the name"OAuthMiddleware".  What should I do?

If using L5.0 use version 4.0 of the package. You won't have all the middlewares there though, and you should use filters instead.

will these eventually be moved to middleware?

Everything is moved to middleware if using L5.1 and 4.1@dev of this package. L5.0 didn't support middleware parameters so stuff had to be implemented with filters.


c11 line programs request

I meet some pdb include c11 line programs (attach below).
Since microsoft open source pdb symbol file format microsoft-pdb, it's feasible to support it now.
I'm wondering if anyone interest ?
c11-line-programs.zip

See #47


ref: Only send 100 sessions in one envelope

Test failures seem unrelated.

tracking testfailures in #671


Add the rendering::graphics-api category

That way gfx will show up here: https://crates.io/categories/rendering::graphics-api.

Note that at the moment you need to publish cargo nightly for the category to show up on crates.io.

Thanks!
@homu r+

:pushpin: Commit 359d258 has been approved by kvark

:zap: Test exempted - status


Allow access to DDEV_GITHUB_TOKEN

Allow ddev get to use a github token to prevent rate limiting by tests

Thanks!


Update google-cloud-nio to 0.127.24

About this PR
📦 Updates com.google.cloud:google-cloud-nio from 0.127.23 to 0.127.24
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.google.cloud", artifactId = "google-cloud-nio" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.google.cloud", artifactId = "google-cloud-nio" }
}]

labels: test-library-update, early-semver-minor, semver-spec-patch, commit-count:1

Superseded by #1184.


Added arrays.xml

arrays.xml With Russian translation

Could you rebase and add the translated strings to the Russian string.xml instead of creating a new arrays.xml file? Twckr has removed the localized arrays.xml file in 7577658cef12646e63b1c5d0e239cd249baf7098, that's probably a better way to do it.

ok


I got messages difference other broker (mosquitto, hivemq)

Testing Environment
docker-image: emqtt version: 2.3.8 with default configuration
mqtt-client: mqtt.js and mosquitto
Description
I tested publishing mqtt to a subscriber by Emq but I got difference result
Mosquitto and Hivemq broker is same but Emq difference
configuration of client 1 and client 2
connec

clean_session=false

publish

qos=1
retain=true

subscribe

qos=1

Testing timeline

There might be a behavior difference when handling the "duplicated subscription" between these brokers.
In EMQ, if a client tries to subscribe a topic to which it has already subscribed, the subscription request will be discarded, as it is treated as 'duplicated subscription'. In this case a warning level log will be printed:
[warning] Session(client1): Duplicated subscribe: test/777, qos = 1
And because you have set the clean session flag, the subscriptions of client1 (the 'test/777') have been stored in the broker. All the subsequent subscribes to 'test/777' will be regarded as 'duplicated', including the ones it sends after the connection has been established.

Thanks for the prompt reply

How should I have to do to get the same result (Mosquitto, Hivemq)
I think this difference should solve because most people set clean_session = false to get old messages that clients can't receive and retian=true to get the last message. so that, when developer set those flag It should express the ability of each flag. But now, EMQ can choose just one feature (clean_sessen or retain).
from 2. if there are some project wanna move to use your broker (EMQ), the code that they have should be compatible with every broker and your broker (EMQ)

Pay attention to this problem.

@DavidLiuXh @krittanon-w Hi, we're planing to fix this issue in 2.3.10.

This bug has been fixed in 2.3.11.

Hi, @Gilbert-Wong you said "This bug has been fixed in 2.3.11" but I see only 2.3.10 in release tab and for that release 2.3.10 It has no release note that reference or tag to any issue. is there something incorrect?

Sorry for my ambiguous state. The bug has been fixed bug  in develop branch but did not merge into release tab 2.3.10,  so  we would merge it into next version v2.3.11


Some more clang tidy "fixes"

Most of this is pretty run of the mill stuff. Lmk where I have done stupid stuff lol :sweat_smile:
~pure_evil.cpp won't compile with the __attribute__((noreturn)), but I remember you (@TrentHouliston) telling me something about how that required further fixes because it really should have that attribute (and there's a non-clang-tidy warning without it lol). What were those fixes?~
// It's this in `master`, but it won't compile with clang
static void (*const rethrow)(void*, void*, void (*)(void*)) __attribute__((noreturn)) = get_real_throw_func();

// This does compile, but generates a warning because the function `void __cxa_throw(..)` does return when it calls this
static void (*const rethrow)(void*, void*, void (*)(void*)) = get_real_throw_func();

(that was dealt with by #350)

@TrentHouliston could I grab a review on this bad boy pls?
Not being able to compile with clang is preventing us from having more sanitizers :(

@CMurtagh-LGTM u enabled auto-merge but still have requested changes?? looool

@CMurtagh-LGTM u enabled auto-merge but still have requested changes?? looool

Wrong button, too tired.


GKE - verify service account has permissions

When re-installing a few times I was getting 403 Forbidden in the logs of external-dns. This was because the service account, after exploration afterwards, appeared to be empty.
gcloud iam service-accounts get-iam-policy \
    test-external-dns@myproj-123456.iam.gserviceaccount.com@my-project-
    123.iam.gserviceaccount.com

etag: ACAB

It's working now (I had been deleting the service account and the kubeprod-autogen) although I can't spot exactly what was going wrong :-)
At any rate one possible improvement in the behaviour would be to:
On every install/upgrade

Delete the existing external-dns secret if it's there
Create a new key and secret
Verify the key works by using :

gcloud auth activate $SERVICE_ACCOUNT
gcloud dns managed-zones list```

Your external-dns issue is probably a duplicate of #64.  I've been caught by this before too and it's very confusing to debug. I agree we should add a workaround by recreating the Secret (and restarting the external-dns pods).  I suggest we followup that action item in #64.
Verifying the existing service accounts is a good suggestion, and it's easy enough to do.  I don't want to make it fatal however, since "just use the value I gave you" is an important feature for complex enterprise cases where the auto-installer is insufficient.  A "this failed a simple verification test" warning seems like an excellent improvement though.

thanks @anguslees , I'll close now and follow in 64.


Need AGP 8+ support

I'm getting the error:
1: Task failed with an exception.
-----------
* What went wrong:
A problem occurred configuring project ':gallery_saver'.
> Could not create an instance of type com.android.build.api.variant.impl.LibraryVariantBuilderImpl.
   > Namespace not specified. Specify a namespace in the module's build file. See https://d.android.com/r/tools/upgrade-assistant/set-namespace for information about setting the namespace.

As of AGP 8+ you must set the namespace in the android {} section of build.gradle. Is there an ETA for AGP 8+ support?

You can define common name space for all sub packages via added few lines in project level build.gradle file. Consider adding bold code mentioned below inside subprojects.
subprojects {     project.buildDir = "${rootProject.buildDir}/${project.name}"     **afterEvaluate { project ->         if (project.hasProperty('android')) {             project.android {                 if (namespace == null) {                     namespace project.group                 }             }         }     }**     tasks.withType(org.jetbrains.kotlin.gradle.tasks.KotlinCompile).configureEach {         kotlinOptions {             jvmTarget = "1.8"         }     } }
I'm also facing many issues nowadays with many packages which are not updated with latest flutter, dart and kotlin versions.

You can define common name space for all sub packages via adding few lines in project level build.gradle file. Consider adding below code inside subprojects block.
    afterEvaluate { project ->
        if (project.hasProperty('android')) {
            project.android {
                if (namespace == null) {
                    namespace project.group
                }
            }
        }
    }

I'm also facing many issues nowadays with many packages which are not updated with latest flutter, dart and kotlin versions.


Add EmailRegistrationGuard

The EmailRegistrationGuard is a guard that can be used to authenticate email registrations.
This guard is successful only if the provided signature is valid. The message that will be validated in the signature needs to follow the format:
email-register-${chainId}-${safe}-${emailAddress}-${account}-${timestamp}
The guard can be applied to any route that has:

the 'chainId' declared as a parameter
the 'safeAddress' declared as a parameter
the 'emailAddress' as part of the JSON body (top level)
the 'account' as part of the JSON body (top level)
the 'signature' as part of the JSON body (top level) - see message format to be signed
the 'timestamp' as part of the JSON body (top level)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

18 of 20 (90.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 90.461%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/routes/email/email-registration.guard.ts
18
20
90.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
5152

Relevant Lines:
5566

💛  - Coveralls


Merge prTesting_201909040819 branch to master branch

Docs Build status updates of commit 37a735b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
:bulb:Suggestion

Details

split/updateTestRef.md

[Suggestion] Missing attribute: author. Add the current author's GitHub ID. NOTE: This Suggestion will be elevated to a Warning on 9/1/2019.
[Suggestion] Missing attribute: title. Add a title string to show in search engine results. NOTE: This Suggestion will be elevated to a Warning on 9/1/2019.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


"AudioVisualizer" component doesn't work.

Problem:
Hello, I use the custom audio recorder component(the code will be given below) and the react-audio-visualizer package.
During the recording of the user's voice - everything is ok, the "LiveAudioVisualizer" component works well. But when I try to render a finished audio recording, the "AudioVisualizer" does not visualize anything, except the background color. In other words, the canvas with styles is rendered normally, but sound waves are not.
Project setup:
"react": "^18.2.0",
"react-audio-visualize": "^1.1.3";
What I tried:
I tried to create a simple project and visualize a song in "mp3" format. And it didn't work.
Code samples:
Custom useAudioRecorder hook:
import {useRef, useState} from "react";

export type IUseAudioRecorderReturnType = ReturnType<typeof useAudioRecorder>;

const mimeType = "audio/webm" as const;

const useAudioRecorder = () => {
   const mediaRecorder = useRef<MediaRecorder | null>(null);
   const [permission, setPermission] = useState<boolean>(false);
   const [isRecording, setIsRecording] = useState<boolean>(false);
   const [stream, setStream] = useState<MediaStream | null>(null);
   const [audio, setAudio] = useState<Blob | null>(null);
   const [audioChunks, setAudioChunks] = useState<Blob[]>([]);

   const getMicrophonePermission = async () => {
       console.log("get permission");
       if ("MediaRecorder" in window) {
           try {
               const streamData = await navigator.mediaDevices.getUserMedia({
                   audio: true,
                   video: false,
               });
               setPermission(true);
               setStream(streamData);
           } catch (err) {
               if (err instanceof Error) {
                   alert(err.message);
                   return;
               }
               console.warn(err);
           }
       } else {
           alert("The MediaRecorder API is not supported in your browser.");
       }
   };

   const startRecording = () => {
       console.log("start recording");
       if (!stream) {
           return;
       }

       setIsRecording(true);
       //create new Media recorder instance using the stream
       const media = new MediaRecorder(stream, { mimeType });
       //set the MediaRecorder instance to the mediaRecorder ref
       mediaRecorder.current = media;
       //invokes the start method to start the recording process
       mediaRecorder.current.start();
       const localAudioChunks: Blob[] = [];

       mediaRecorder.current.ondataavailable = (event) => {
           console.log("blobEvent: ", event);
           if (typeof event.data === "undefined") return;
           if (event.data.size === 0) return;
           localAudioChunks.push(event.data);
       };
       setAudioChunks(localAudioChunks);
   };

   const stopRecording = () => {
       console.log("stop recording");
       if (!mediaRecorder.current) {
           return;
       }
       setIsRecording(false);
       //stops the recording instance
       mediaRecorder.current.onstop = () => {
           //creates a blob file from the audiochunks data
           const audioBlob = new Blob(audioChunks, { type: mimeType });
           //creates a playable URL from the blob file.
           setAudio(audioBlob);
           setAudioChunks([]);
       };
       mediaRecorder.current.stop();
   };

   return {
       mediaRecorder,
       permission,
       isRecording,
       audio,
       getMicrophonePermission,
       startRecording,
       stopRecording
   };
};

export {useAudioRecorder};

The App component with the main logic(voice recording and rendering a finished audio recording):
import {AudioVisualizer, LiveAudioVisualizer} from "react-audio-visualize";
import {useAudioRecorder} from "./component/useAudioRecorder.hook.ts";

function App() {
    const {
        mediaRecorder,
        permission,
        isRecording,
        audio,
        getMicrophonePermission,
        startRecording,
        stopRecording
    } = useAudioRecorder();

    console.log("audio: ", audio);
    return (
        <div>
            { !permission && <button onClick={getMicrophonePermission}>Get permission</button> }
            { permission && !isRecording && <button onClick={startRecording}>Start</button> }
            { isRecording && <button onClick={stopRecording}>Stop</button> }

            {
                isRecording &&
                <LiveAudioVisualizer
                    mediaRecorder={mediaRecorder.current}
                    width="300px"
                    height="75px"
                />
            }

            {
                audio &&
                <AudioVisualizer
                    blob={audio}
                    width={"610px"}
                    height={"50px"}
                    barWidth={1}
                    gap={2}
                    barColor={"#f76565"}
                    backgroundColor={"black"}
                />
            }

        </div>
    )
}

export default App;

I would really appreciate your help

So, seems like my IDE glitched.
Anyway, thanks, if someone figured out this problem.


Bumblebee does not build on 17.03

Issue description
On the 17.03 branch, bumblee cannot be built.
Steps to reproduce
Use the following configuration.nix to nixos-rebuild build:
{
  imports = [];

  boot = {
    loader.grub = {
      version = 1;
      device = "/dev/sda";
    };
  };

  fileSystems."/" =
    { device = "/dev/sda1";
      fsType = "ext4";
    };

  hardware.bumblebee.enable = true;
  nixpkgs.config.allowUnfree = true;
}

Build log:
➜  nixpkgs git:(release-17.03) ✗ NIXOS_CONFIG=/home/ollie/nixpkgs/configuration.nix nixos-rebuild build                                                             ~/nixpkgs
building Nix...
building the system configuration...
these derivations will be built:
  /nix/store/r86cn30984i9mc5r3d3dq6qsrir6dzmj-bumblebee-3.2.1.drv
  /nix/store/18dvgz25d64z9hrj16ss64m13dk1i6pr-system-path.drv
  /nix/store/ahsv4yr5584a3myylb71w2fbid30qabl-dbus-1.drv
  /nix/store/mha32sb6bdivl932c7acwy5valxjiyp7-unit-dbus.service.drv
  /nix/store/gi5iyq32749hyadbdjckmw3fbgj7kzq1-user-units.drv
  /nix/store/gb5yr4m3wvs2zjrark64bg1v5gmaddaw-unit-polkit.service.drv
  /nix/store/q07gslxbh53mijdbxzk7dshigw9z4brq-unit-bumblebeed.service.drv
  /nix/store/yh80wgs7fymdyz5ynngv6b6ywz6pqsy7-system-units.drv
  /nix/store/042nl9prni3hhi0h3qaqhwg59d4i04h9-etc.drv
  /nix/store/v3njfa7j6vlx75b98nfw3hr33mmz9h5g-nixos-system-nixos-17.03beta320.ade5837.drv
building path(s) ‘/nix/store/mjhqlfilaqzknjy1kxc7mslrliyghqib-bumblebee-3.2.1’
unpacking sources
unpacking source archive /nix/store/3h76c30ipnchsz2d18wbmqn8mlpviwr6-bumblebee-3.2.1.tar.gz
source root is bumblebee-3.2.1
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file bumblebee-3.2.1/VERSION
patching sources
applying patch /nix/store/v45qbhln8rf90568jhmza58jvzhlb17w-nixos.patch
patching file conf/xorg.conf.nouveau
patching file conf/xorg.conf.nvidia
patching file src/bbsecondary.c
applying patch /nix/store/ss2ryfgmlriv96k4ag9i88bzspwfhanb-1ada79fe5916961fc4e4917f8c63bb184908d986.patch
patching file src/module.c
applying patch /nix/store/0rnayiv1da99iw3iysmfgh0rdl0mjv0d-deceb14cdf2c90ff64ebd1010a674305464587da.patch
patching file Makefile.am
patching file Makefile.am
patching file README.markdown
patching file configure.ac
patching file src/bbconfig.c
patching file src/bbconfig.h
patching file src/bblogger.c
Hunk #1 succeeded at 225 (offset -3 lines).
Hunk #2 succeeded at 254 (offset -3 lines).
patching file src/bumblebeed.c
patching file src/bumblebeed.c
patching file src/bumblebeed.c
patching file src/bumblebeed.c
patching file src/bumblebeed.c
patching file src/module.c
patching file src/module.c
patching file src/module.c
patching file src/module.c
patching file src/module.c
patching file src/optirun.c
configuring
configure flags: --disable-dependency-tracking --prefix=/nix/store/mjhqlfilaqzknjy1kxc7mslrliyghqib-bumblebee-3.2.1 --with-udev-rules=$out/lib/udev/rules.d CONF_LDPATH_NVIDIA=/nix/store/ljllkmy36znn28hb92p1gi41s285mnaj-nvidia-x11-375.26-4.9.13/lib:/nix/store/gwkpc014d8p8v8d8h4cgsa0kc4fanwyc-libglvnd-2016-12-22/lib:/nix/store/01nqn3rn5a9f35jyi8x485qjcfhikxxx-nvidia-x11-375.26/lib:/nix/store/pmvjgqpfahd9qbvynbb4mw2ln3n7sayr-libglvnd-2016-12-22/lib CONF_MODPATH_NVIDIA=/nix/store/sdqa3xdy5pywkar948vfa0x1f1kqiwv4-nvidia-x11-375.26-4.9.13-bin/lib/xorg/modules
checking for a BSD-compatible install... /nix/store/5lfwsx1nkrcqp7p24qr8z4wiwfxx5idv-coreutils-8.26/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /nix/store/5lfwsx1nkrcqp7p24qr8z4wiwfxx5idv-coreutils-8.26/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking how to create a pax tar archive... gnutar
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... none
checking whether gcc and cc understand -c and -o together... yes
checking for help2man... /nix/store/waa08hca7l1ia5wbj5wx1aqgsi4261vv-help2man-1.47.4/bin/help2man
checking for pkg-config... /nix/store/jcjkq069c3yj344clhkwfgvrgrpizmpy-pkg-config-0.29/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for x11... yes
checking for glib... yes
checking for libbsd... yes
configure: creating ./config.status
config.status: creating Makefile
./config.status: line 966: /nix/store/hkzcransq2fc2rd47rph5gifr06nw7lz-gawk-4.1.3/bin/gawk: cannot execute binary file: Exec format error
config.status: error: could not create Makefile
builder for ‘/nix/store/r86cn30984i9mc5r3d3dq6qsrir6dzmj-bumblebee-3.2.1.drv’ failed with exit code 1
cannot build derivation ‘/nix/store/18dvgz25d64z9hrj16ss64m13dk1i6pr-system-path.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/q07gslxbh53mijdbxzk7dshigw9z4brq-unit-bumblebeed.service.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/ahsv4yr5584a3myylb71w2fbid30qabl-dbus-1.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/gb5yr4m3wvs2zjrark64bg1v5gmaddaw-unit-polkit.service.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/mha32sb6bdivl932c7acwy5valxjiyp7-unit-dbus.service.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/yh80wgs7fymdyz5ynngv6b6ywz6pqsy7-system-units.drv’: 3 dependencies couldn't be built
cannot build derivation ‘/nix/store/gi5iyq32749hyadbdjckmw3fbgj7kzq1-user-units.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/042nl9prni3hhi0h3qaqhwg59d4i04h9-etc.drv’: 3 dependencies couldn't be built
cannot build derivation ‘/nix/store/v3njfa7j6vlx75b98nfw3hr33mmz9h5g-nixos-system-nixos-17.03beta320.ade5837.drv’: 2 dependencies couldn't be built
error: build of ‘/nix/store/v3njfa7j6vlx75b98nfw3hr33mmz9h5g-nixos-system-nixos-17.03beta320.ade5837.drv’ failed

Technical details

Nixpkgs version: 17.03beta320.ade5837

I can't reproduce that on ade5837 and the error suggests that something is wrong with your gawk binary. Perhaps an FS corruption? Could you run nix-store --verify-path /nix/store/hkzcransq2fc2rd47rph5gifr06nw7lz-gawk-4.1.3/?

Yea, I also noticed that, and am trying to get the path to repair (it is identified as corrupt), but - http://lists.science.uu.nl/pipermail/nix-dev/2017-March/023054.html


Add option to create local volumes instead of hostPath

resolve #85
Took the changes from #91 and added them to be enabled by a config value an annotation on the pvc. Default behavior is still to use hostPath volumes. By using an annotation, we can allow the user to create both hostPath and local volumes, instead of just locking down to one.
Made some small changes to the README, but will update the README and examples further if code changes are ok from maintainers.

@AnthonyEnr1quez Looks good. Can you solve the conflict, thank you.

Changed the status to Draft, will fix conflicts and add more docs/examples and tests

@derekbit Fixed the conflicts and added examples and an e2e test. Changed the mechanism to use local volume to annotations on the pvc.

If these changes are ok, I might refactor the e2e tests to be a bit cleaner and remove the dependency on testify suite

@AnthonyEnr1quez Do you need support here?
I already added support for PVC annotations into onechart - https://github.com/gimlet-io/onechart/pull/51
I'm really looking forward for this feature, since it's blocking my from creating an end-to-end backup strategy.
But it's always easy to say: "what's the status", instead maybe I can support you here?

As @Marcel-Lambacher, also waiting for this feature for better handling of backups.
I can also provide help if needed, any status @AnthonyEnr1quez?

@Marcel-Lambacher @maximeborges we should be good, just waiting for a response to https://github.com/rancher/local-path-provisioner/pull/260#discussion_r961817716

LGTM. Thanks for your contribution.

Hi, do we have a date when this will be released?

We will release the new version by the end of this week. I'm testing and fixing some issues.

v0.0.23 is released. Thank you and any feedback is appreciated.

@Marcel-Lambacher @maximeborges @fabioandreola if you need help converting volumes, see https://github.com/rancher/local-path-provisioner/issues/85#issuecomment-1292578697

@Marcel-Lambacher @maximeborges @fabioandreola if you need help converting volumes, see #85 (comment)

Thanks. I want to report that with this change Velero PVC backups are working as expected


Watching for file changes is broken in chomp v0.2.9

Upgrading to v0.2.9, chomp --watch no longer picks up file changes. Reverting back to chomp 0.2.6, then file changes trigger re-running chomp tasks again

//cc @Aslemammad this sounds related to the new pathing changes.


Static Groups and Control

This proposal follows up on https://github.com/cucapra/calyx/discussions/1334 to add static groups to the language to enable reasoning about timing. The core abstraction is using a "relative clock" to trigger actions. It additionally deprecates the @static syntax in favor of a static keyword.
Static groups
A static group is declared using the new static keyword:
static group foo {    // Starts at time `t`
    r.in = 10;
    r.write_en = %0;  // Asserted at `t+0`
    foo[done] = %1;   // Asserted at `t+1`
}

The %n syntax is a relative clock. The %0 is the current cycle, %1 is the next cycle, and so on. The %n syntax is only allowed in the static group.
The well-formedness constraint for a static group is that its done condition must be a relative clock and all actions within are assumed to complete before the done condition is asserted.
Chaining operations is straightforward:
static group two {
    r.in = 20;
    r.write_en = %0;
    d.in = 10;
    d.write_en = %1;
    two[done] = %2;     // Must be %n
}

This group looks suspiciously similar to a seq of two groups that write values into the registers r and d. This is intentional.
Static Control
Static control operators simply use the static keyword in front of the standard control operator. The well-formedness condition requires that they only contain other static control programs within them. Group enable of a static group is the smallest static control program. Furthermore, they obey all the constraints and guarantees from https://github.com/cucapra/calyx/discussions/1331. The composition principle for static control programs is that they can be compiled into static groups.
Sequences
static group one { r.in = 10; r.write_en = %0; one[done] = %1; }
static group two { a.in = 20; a.write_en = %0; two[done] = %1; }
control { static seq { one; two } /* Both groups must be `static` */ }

The semantics of static control operators are given in terms of a relative clock, i.e., one starts at %0 and two starts at %0 + %(one's delay). This means we can compile the static control program into a static group:
static group compiled {
    r.in = 10;
    r.write_en = %0;
    a.in = 20;
    a.write_en = %1;
    compiled[done] = %2;
}
control { compiled }

In general, the compiled group looks like:
static group compiled {
    one[go] = %[0:one's delay]; // This has concrete numbers in it
    two[go] = %[(one's delay):(one's delay + two's delay)];
    compiled[done] = %(one's delay + two's delay);
}

The special syntax %[n:m] is a signal that is asserted between n and m cycles. During compilation, one's delay etc. are going to be concrete numbers.
Parallel
static group one { r.in = 10; r.write_en = %0; one[done] = %1; }
static group two { a.in = 20; a.write_en = %0; two[done] = %2; }
control { static par { one; two } // Both groups must be `static` }

Semantics is provided the following group:
static group compiled {
    r.in = 10;
    r.write_en = %0;
    a.in = 20;
    a.write_en = %0;
    compiled[done] = %1;
}
control { compiled }

In general the compiled group looks like:
static group compiled {
    one[go] = %[0:one's delay];
    two[go] = %[0:two's delay];
    ...
    compiled[done] = %(max(one's delay, two's delay));
}

Conditional
static if port { tru } else { fal }

Conditionals execute their branches in the same cycle when they begin:
static group compiled {
    // Save the value from the port
    cond.in = port;
    cond.write_en = %0;
    // Use a wire to forward the right value
    w.in = %0 ? port : cond.out;
    // Execute the branches using the wire value
    tru[go] = w.out ? %0;
    fal[go] = !w.out ? %0;
    compiled[done] = %(max(tru's delay, fal's delay));
}

A couple of things are interesting about this encoding:

We need to save the value from the port in the first cycle because we don't if the branches will modify its value.

This can probably be relaxed when we know that neither branch modifies the port

The end time for the group is the max of the two branches which implicitly encodes the fact that we balance if branches before compiling them.
This encoding does not match how we lower @static if in https://github.com/cucapra/calyx/pull/1338 which allocates different states for each branch and transitions to one or the other path based on the condition. Perhaps this distinction doesn't matter?

Loops
Static loops need to necessaily be bounded. I'm going to define a new control operator repeat n to reflect the fact that static loop without a @bound is meaningless. Maybe we want to eventually actually define this as a control operator (in which case we'd need to handle the case where the body is not static):
@bound(n) static while port { body }

same as:
static repeat n { body }

This probably gets compiled to:
static group compiled {
    body[go] = %[0:n*body's delay];
    compiled[done] = %(n*body's delay);
}

I'm not quite sure if this is correct so would have to think harder.
Lowering to Dynamic Groups
In order to compile a Calyx program, we first lower all static groups to normal groups by reifing the relative clock. For example, the following static group:
static group foo {
    r.in = 10;
    r.write_en = %0;
    foo[done] = %1;
}

Compiles to:
cells {
    fsm = std_reg(4);
}
group foo {
    r.in = 10;
    r.write_en = fsm.out == 0;
    foo[done] = fsm.out == 1;
}
fsm.in = fsm.out == 1 ? 0;
fsm.out = fsm.out != 1 : fsm.out + 1;

The last two assignments are continuous since we need to be able to reset the FSM that provides the relative clock. In a fully static program, ideally we'd generate one static FSM per par thread.

Hell yes; this seems great. I really like the introduction of the explicit "relative time" bubble within each group; it is a great way to reflect the philosophy of group isolation while transposing it into a statically-timed domain.
To state something explicitly that is implicit in the above… since every static group has a line like this:
group[done] = %N;

…you can easily get the group's latency (what we currently call @static(N)): it's N, of course. :smiley:
One other obvious thing to make explicit: the time instant %4 is sugar for the time range %[4:4].
On static repeat n loops: maybe this was what you were getting at already, but it seems like we'd want to copy-n-paste the body's assignment n times? That is, keeping it active for longer doesn't seem the same as repeating its effects multiple times.

This is really interesting. I think it will certainly help accurately and precisely capture the kinds of pipelines we've Calyx for in CIRCT!
One question that wasn't immediately obvious:
The proposed <lhs> = %[n:m] construct says to assert <lhs> from relative cycle n through m, correct?
I was initially confused, because normally the right hand side of an assign can be constants, ports, etc. (I forget the exact rules). But this is a pretty specific case (a constant 1 at certain time steps).
Is the idea this special case is the only limited way this can be used? If so I guess there is a rule that the <lhs> must be a single bit? Are there other restrictions?
Also, what is the value of <lhs> outside the timesteps n:m? Is it 0/X? I guess if it is just this specific case, the compiler knows it is 0 outside the time steps where it is 1.

Good questions, @mikeurbach. @rachitnigam is of course the authority here, but I can give you my gut reactions and get corrected down the line:

Yep, the new %[n:m] construct would be a new kind of thing that can go on the RHS of assignments, adding to constants and ports. It is the new invention here to cope with static timing.
Yeah, I suppose the LHS would have to be a single bit. (In Calyx terms, %[n:m] expressions would have the type 1, which means they can only be assigned into 1-bit ports.)
Super good question about undefinedness. I would argue that we need it to be 1 for the range n–m and 0 otherwise to make most things make sense. (It would only be undefined when the entire group is inactive.)

Thanks for the explanation @sampsyo, that makes sense to me. The part about the type of %[n:m] expressions really clears it up. Looking forward to seeing where this goes, and getting CIRCT to support the new representation so we can target it from our all-static flow.

Misc syntax note from the meeting. The done assignment could possibly be folded into the declaration rather than the assignment syntax
static group foo {    // Starts at time `t`
    ...
    foo[done] = %1;   // Asserted at `t+1`
}

becomes something like (syntax entirely made up)
static group foo<1> {    // Starts at time `t`
    ...
}

Indeed; there is something nice about @EclecticGriffin's proposed syntax (or, like, static(1) group foo, which is very similar to our current annotation system) because it doesn't imply that there is an actual signal required to tell the group to stop executing (as there is in a "normal" group).
Two minor things struck me after our synchronous conversation yesterday:
Dynamic Within Static
v1.0 of this system will allow nesting static "islands" within dynamic control programs, which is definitely the most useful thing (it's an enactment of the "globally asynchronous, locally synchronous" (GALS) principle). We don't allow the other way around, for obvious reasons. But @andrewb1999's questions made me think about whether we could, in an extension, do something to allow the "backward" nesting.
Here is a very silly strawperson construct to achieve this. Introduce a limit control construct:
static seq {
  my_static_group;
  static limit(25) {
    my_dynamic_group;
  }
  my_other_static_group;
}

Here, my_dynamic_group can take any amount of time by itself. Wrapping it in limit(25) makes it take a deterministic 25 cycles. It does this by just aborting the execution altogether if it takes any longer than 25 cycles, and idling if it takes less than 25 cycles. Sort of a brute-force thing, but you can kinda imagine semi-contrived situations where you would want this: for example, when you know (but can't prove to the compiler) that accessing a memory takes either 3 or 25 cycles (on a cache hit or a cache miss).
Dynamic while Around Static Body
A thread that comes up often, again raised by @andrewb1999, is how we waste a cycle in traditional Calyx while loops:
while cond {
  body;
}

If body is a dynamic group that takes 5 cycles, then the overall loop takes 6 cycles per iteration. We waste one cycle to "realize" that the body has finished executing. This seems sad.
It should be a design goal for this proposal that we don't waste a cycle, i.e., the same loop takes only 5 cycles per iteration, when body is a static group. (Of course, while is always dynamic—the only kind of static loop that makes sense is a repeat loop.) This goal implies that we cannot compile the loop by first "wrapping" body in a dynamic interface and then compiling as normal (which is the normal/universal approach to compiling dynamic islands nested within dynamic control). Instead, we would want our dynamic control compilation pass to have a special case for while loops that wrap static bodies.

@sampsyo one note on a previous comment:

On static repeat n loops: maybe this was what you were getting at already, but it seems like we'd want to copy-n-paste the body's assignment n times? That is, keeping it active for longer doesn't seem the same as repeating its effects multiple times.

Not sure if we want to duplicate the body because that tends to blow up the FSM by a lot. The TDST implement (#1338) is explicitly designed to not duplicate the body for this reason

This occurred to me today during the CIRCT ODM, but have you looked at TL-X? CIRCT hosted a talk early last year. One thing that stuck out then is the "alignment" operator, which seems spiritually similar to the %[n:m] operator here. The syntax in TL-X has changed through revisions, but it's the >> and << in Section 16.4 here. I think the construct in TL-X is a more general way to access any value across pipeline stages, but seems spiritually similar in the notion of relative time offset. I guess I'm curious if you can draw any inspiration from TL-X as you are thinking about IR and languages for pipelining.

Thanks for the pointer; I had not seen this particular feature in TL-*!

This has been implemented in spirit.


glib: add bin output for gvfs executables

this fixes gvfs in caja (mate desktop)
Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Note that there is a related FIXME comment in someplace else: https://github.com/Mic92/nixpkgs/blob/ef73fa9c095eee8a337c172998e2fd6719100ff1/pkgs/desktops/gnome-3/core/gnome-session/default.nix#L32
Does this perhaps fix that issue as well? If so, the no longer correct ${glib.dev}/bin should be fixed in that file.

Good point. Maybe gvfs binaries also should be patched to always have gio in $PATH

@dezgeg IIRC, the comment refers to gsettings program.

To put the issue into context, glib has three types of binaries:

Ones needed during builds like glib-mkenums
Ones needed after installation like glib-compile-schemas
System utilities gio or gsettings

Optimally, they would be in separate packages but since glib is monolithic, we should use different outputs.

gapplication – used to start D-Bus-activatable applications, sometimes used in Exec keys in destktop files as a fallback (see description of DBusActivatable), maybe it should be always be in user environment?
gdbus – used for running some services (in my /nix/store I found it in xdg-utils which use it inside Flatpak and in gnome3.tracker, the latter should probably be patched), maybe some people may want to use it access D-Bus from shell scripts
gio – replaces gvfs-* commands, some users might want to install them either for scripts or manual usage
gdbus-codegen, glib-compile-resources, glib-genmarshal, glib-mkenums – used during build
glib-gettextize – developers use it for adding gettext support to autotools projects? is it even necessary with gettext 0.19, glib gettext m4 macros are definitely discouraged in favour of uptsream ones?
gtester, gtester-report – used for running tests (during build? by some autotools macro? meson has its own test runner)
gio-querymodules, glib-compile-schemas – usually run after installation to rebuild caches
gobject-query – no idea
gresource – debugging gresource files created glib-compile-resources?
gsettings – editing of GSettings from CLI, some users might want it even if it does not work very well with Nix

I think gapplication, gdbus, gio, gsettings and maybe gresource should go to bin, the rest to dev.

Success on x86_64-darwin (full log)
Attempted: glib
The following builds were skipped because they don't evaluate on x86_64-darwin: gtkd
Partial log (click to expand)
strip is /nix/store/0fzpxnsanc02i4jsb1yhchjp4p62b2n3-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/2w8qk31qzfzxf4fxjp055bf2x6vljpji-glib-2.56.0/lib
patching script interpreter paths in /nix/store/2w8qk31qzfzxf4fxjp055bf2x6vljpji-glib-2.56.0
strip is /nix/store/0fzpxnsanc02i4jsb1yhchjp4p62b2n3-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/04pjbj4hrq2r2f0ljypzy5r5is5azb4b-glib-2.56.0-dev/lib  /nix/store/04pjbj4hrq2r2f0ljypzy5r5is5azb4b-glib-2.56.0-dev/bin
patching script interpreter paths in /nix/store/04pjbj4hrq2r2f0ljypzy5r5is5azb4b-glib-2.56.0-dev
/nix/store/04pjbj4hrq2r2f0ljypzy5r5is5azb4b-glib-2.56.0-dev/bin/gdbus-codegen: interpreter directive changed from "/usr/bin/env /nix/store/fqsrb5whxc3w7cvvk4yw6z8pralx2q5l-python-2.7.14/bin/python" to "/nix/store/fqsrb5whxc3w7cvvk4yw6z8pralx2q5l-python-2.7.14/bin/python"
/nix/store/04pjbj4hrq2r2f0ljypzy5r5is5azb4b-glib-2.56.0-dev/bin/glib-gettextize: interpreter directive changed from " /bin/sh" to "/nix/store/x030a63qdilnv02pkivfjg44pdxsh5km-bash-4.4-p19/bin/sh"
strip is /nix/store/0fzpxnsanc02i4jsb1yhchjp4p62b2n3-cctools-binutils-darwin/bin/strip
patching script interpreter paths in /nix/store/i4s8ay3pgdkdmz7qdkjn6rjs5r3nid9k-glib-2.56.0-devdoc

Success on aarch64-linux (full log)
Attempted: glib
The following builds were skipped because they don't evaluate on aarch64-linux: gtkd
Partial log (click to expand)
stripping (with command strip and flags -S) in /nix/store/4x8lkdk5qg8hvm8q0s8c382517wv9pxq-glib-2.56.0-dev/lib  /nix/store/4x8lkdk5qg8hvm8q0s8c382517wv9pxq-glib-2.56.0-dev/bin
patching script interpreter paths in /nix/store/4x8lkdk5qg8hvm8q0s8c382517wv9pxq-glib-2.56.0-dev
/nix/store/4x8lkdk5qg8hvm8q0s8c382517wv9pxq-glib-2.56.0-dev/bin/glib-gettextize: interpreter directive changed from " /bin/sh" to "/nix/store/3gg2p6n4kv2f0lsxd41f5iz1ivkbzyzr-bash-4.4-p19/bin/sh"
/nix/store/4x8lkdk5qg8hvm8q0s8c382517wv9pxq-glib-2.56.0-dev/bin/gdbus-codegen: interpreter directive changed from "/usr/bin/env /nix/store/14z9xiiwdnks1pivrv2hml9cflwq2iw3-python-2.7.14/bin/python" to "/nix/store/14z9xiiwdnks1pivrv2hml9cflwq2iw3-python-2.7.14/bin/python"
checking for references to /build in /nix/store/4x8lkdk5qg8hvm8q0s8c382517wv9pxq-glib-2.56.0-dev...
shrinking RPATHs of ELF executables and libraries in /nix/store/1qqmiyq1kq9lfxn1q7c3r1iin51086pl-glib-2.56.0-devdoc
strip is /nix/store/3zq400fri5dv7d30lpxlqm2v9y1iis6j-binutils-2.28.1/bin/strip
patching script interpreter paths in /nix/store/1qqmiyq1kq9lfxn1q7c3r1iin51086pl-glib-2.56.0-devdoc
checking for references to /build in /nix/store/1qqmiyq1kq9lfxn1q7c3r1iin51086pl-glib-2.56.0-devdoc...
/nix/store/yr6hpdlksn9r1ga6j7zrjsn0axf03kxk-glib-2.56.0-bin

Success on x86_64-linux (full log)
Attempted: glib, gtkd
Partial log (click to expand)
peas/Engine.d
install -m 644 peasd-3.pc /nix/store/dyvjm17f7jsrvfgk4gvsyh69s974vbzw-gtkd-3.6.5/share/pkgconfig
install -m 644 libpeasd-3.a /nix/store/dyvjm17f7jsrvfgk4gvsyh69s974vbzw-gtkd-3.6.5/lib/
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/dyvjm17f7jsrvfgk4gvsyh69s974vbzw-gtkd-3.6.5
strip is /nix/store/fzcs0fn6bb04m82frhlb78nc03ny3w55-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/dyvjm17f7jsrvfgk4gvsyh69s974vbzw-gtkd-3.6.5/lib
patching script interpreter paths in /nix/store/dyvjm17f7jsrvfgk4gvsyh69s974vbzw-gtkd-3.6.5
checking for references to /build in /nix/store/dyvjm17f7jsrvfgk4gvsyh69s974vbzw-gtkd-3.6.5...

Success on aarch64-linux (full log)
Attempted: glib
The following builds were skipped because they don't evaluate on aarch64-linux: gtkd, tlaplus
Partial log (click to expand)
stripping (with command strip and flags -S) in /nix/store/ql79km8ciw5sa41vw33xkq0j8hlijah5-glib-2.56.0-dev/lib  /nix/store/ql79km8ciw5sa41vw33xkq0j8hlijah5-glib-2.56.0-dev/bin
patching script interpreter paths in /nix/store/ql79km8ciw5sa41vw33xkq0j8hlijah5-glib-2.56.0-dev
/nix/store/ql79km8ciw5sa41vw33xkq0j8hlijah5-glib-2.56.0-dev/bin/glib-gettextize: interpreter directive changed from " /bin/sh" to "/nix/store/fqm2x6kiay1q4vg7pqp4wp17bdijlyc3-bash-4.4-p23/bin/sh"
/nix/store/ql79km8ciw5sa41vw33xkq0j8hlijah5-glib-2.56.0-dev/bin/gdbus-codegen: interpreter directive changed from "/usr/bin/env /nix/store/imv54r70hay2sjrbjiw9l5hhmq3zdkkx-python-2.7.15/bin/python" to "/nix/store/imv54r70hay2sjrbjiw9l5hhmq3zdkkx-python-2.7.15/bin/python"
checking for references to /build in /nix/store/ql79km8ciw5sa41vw33xkq0j8hlijah5-glib-2.56.0-dev...
shrinking RPATHs of ELF executables and libraries in /nix/store/7bnjbgvw45p2rqb7li7ahdhbplw64ndx-glib-2.56.0-devdoc
strip is /nix/store/y4ymnvgxygpq05h03kyzbj572zmh6zla-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/7bnjbgvw45p2rqb7li7ahdhbplw64ndx-glib-2.56.0-devdoc
checking for references to /build in /nix/store/7bnjbgvw45p2rqb7li7ahdhbplw64ndx-glib-2.56.0-devdoc...
/nix/store/v9wslscl816142znahn4mvk4c30c3m8f-glib-2.56.0-bin

Timed out, unknown build status on x86_64-linux (full log)
Attempted: glib, gtkd, tlaplus
Partial log (click to expand)
stripping (with command strip and flags -S) in /nix/store/rdm2kvvgrz6pi4qvx5zmkny2njkgcgdn-libgit2-0.26.6/lib
patching script interpreter paths in /nix/store/rdm2kvvgrz6pi4qvx5zmkny2njkgcgdn-libgit2-0.26.6
checking for references to /build in /nix/store/rdm2kvvgrz6pi4qvx5zmkny2njkgcgdn-libgit2-0.26.6...
cannot build derivation '/nix/store/2hbpr45s6r423ks47fjavmqwrw0r5ldf-cargo-1.27.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/rz4sprk351yciw0yvrllrd55rpzhnabp-librsvg-2.42.4.drv': 8 dependencies couldn't be built
cannot build derivation '/nix/store/p3q5cv1fk7pb95izwbhg9i1rrgf7b05i-icon-naming-utils-0.8.90.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/5nn2zyrd7lwmyzfc9qx524ywcja90rqm-adwaita-icon-theme-3.28.0.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/42rdh9l5pykxn5n9j6hnnm0bv6mkflki-libpeas-1.22.0.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/9vql8msjxwsm3q874ma2f9n9slk3r7db-gtkd-3.8.3.drv': 13 dependencies couldn't be built
error: build of '/nix/store/9vql8msjxwsm3q874ma2f9n9slk3r7db-gtkd-3.8.3.drv', '/nix/store/gwdkrabvhl6ipayc64868bmj2mmjdy5s-tlaplus-1.5.6.drv' failed

Timed out, unknown build status on x86_64-darwin (full log)
Attempted: glib, tlaplus
The following builds were skipped because they don't evaluate on x86_64-darwin: gtkd
Partial log (click to expand)
cannot build derivation '/nix/store/grnmrx9w9036hg55yap667p3p7m1vq96-tlaplus-1.5.6.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/czb5hf8a3w65y6p60y7hkrpjb3ssqlzd-hook.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/3wzzyksiw064ybr4ywsppv341iyzvwjn-flex-2.6.4.drv': 6 dependencies couldn't be built
cannot build derivation '/nix/store/4ncnjraw61v3kh7vyz4z4vj0xrzydr09-bootstrap_cmds-dev-tools-7.0.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/1y4rlvpf7bfmhbrkhpq0ajbccqvld4kz-xnu-osx-10.11.6.drv': 8 dependencies couldn't be built
cannot build derivation '/nix/store/l8za43cgn4wci8qm2csd0p0rh5wak5ap-IOKit-osx-10.11.6.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/81vzs4w9r3xwf04v80lnq5lhw13lcsqh-configd-osx-10.8.5.drv': 8 dependencies couldn't be built
cannot build derivation '/nix/store/s98m4rvmhc88frr80ddmffjwafrbzldm-python-2.7.15.drv': 9 dependencies couldn't be built
cannot build derivation '/nix/store/3drb39sc88614yrkfr23fg6z4dha4k8x-glib-2.56.0.drv': 6 dependencies couldn't be built
error: build of '/nix/store/3drb39sc88614yrkfr23fg6z4dha4k8x-glib-2.56.0.drv', '/nix/store/grnmrx9w9036hg55yap667p3p7m1vq96-tlaplus-1.5.6.drv' failed

Thanks for finishing that!


Issue with integrating with Cordova iOS app

I've successfully implemented the Payment.js script on my website. The same codebase powers a "hybrid app", using Cordova to build an iOS native app.
I'm running into an issue with the script in the hybrid app. My payment form appears, and the iFrames for the individual fields/inputs loads, but the callback passed in to window.firstData.createPayementForm never gets called.
When debugging, the console is indicating the following error:
The string did not match the expected pattern.

The underlying code points to parent.postMessage where it takes two parameters -

a string (the message)
the parent's document referrer

In my case, the value for (2) is "" (an empty string).
Presumably this is because we're dealing with a hybrid/native app that doesn't have a typical URL structure (there is no URL like https://myapp).
At best, if the value passed in was "*", that might solve the issue, but I have no control over that. As far as I can tell, there's no way for me to set the referrer.
Have you encountered this issue before?
Please let me know if you need any more information to understand my issue.
Thank you.

We have encountered this issue 2-3 times before.
Unfortunately there's currently no workaround. The PaymentJS client library wasn't developed for non-browser applications.
Now while the client library may not be compatible at the moment, a direct api integration would be viable if you are interested in going that route.
As for the suggestion to use "*", that might work and the security implications may not be significant since the message is intended to be passed to the client library loaded under a domain external to us anyways. We'd need to discuss this suggestion internally though, I'm a bit concerned this could open a security hole I'm not yet aware of.
I'll keep this ticket open and will update it if we decide to include a fix in an upcoming release.


*: use pingcap/log (zap) for logging

What problem does this PR solve?
Switch to use the uniform log format.
What is changed and how it works?
The log library is changed from logrus to zap, a structured logger.
Due to how structured logging usually works, several interfaces are rewritten.

Child loggers are heavily used to abstract away contextual information in the log, e.g. the table name, engine UUID etc. Many types which originally compute these tagging information on-line are changed to storing a child logger instead.
The 3 functions QueryRowWithRetry/TransactWithRetry/ExecWithRetry originally writes log without any contextual information. These are modified to accept a logger. The common arguments are abstracted into an SQLWithRetry type.

All logging infrastructures (e.g. common.AppLogger) are moved from common into a new log package.

Like common.AppLogger, we need to define our own logger log.L() distinct from the true global one "github.com/pingcap/log".L() so we could control TiDB's logging level independently (though perhaps we could investigate whether merging the two is possible nowadays).
Stack traces of error level logs are entirely disabled, and stack traces of errors are by default inhibited by the log.ShortError function, to avoid flooding the log with noise.
A common pattern used in Lightning is:

Log that a task has started
Perform a task
Log that a task has ended, and display the total time taken.
This is codified into the log.Task type.

Several redundant error logs are eliminated (e.g. if f() calls g() calls h(), and h() logs an error, then g() and f() will not log the error again).
Following pingcap/tidb#10025's lead, when refactoring a function, if an error is known to be a custom error, errors.Trace will no longer be applied. This will be done more thoroughly in the future, after unit-test coverage is improved.
Check List
Tests

Unit test
Integration test

Side effects

Breaking backward compatibility

Log format is modified

Related changes

Need to update the documentation

/run-all-tests tidb=master tikv=master pd=master

Output looks like:

/run-all-tests

@july2993 @lonng PTAL

/run-all-tests


Set recording audio sesssion default to speaker

Related #314

this issue still persists in version 3.5.1.
after recording, the playback is not using the speaker.


Trying to implement an A-Buffer (Metal)

Hi,
currently I am trying to port my GLSL version of an A-Buffer for Per-Pixel-Linked-List Order Independent Transparency to bgfx.
Is there any way to do imageStore or imageLoad in a fragment shader compiled for Metal using the new version of shaderc (spirv)? My shader compiles fine using an IMAGE2D, but it seems like binding images is not supported in the bgfx Metal backend.
After realizing this, I tried to use DynamicBuffers (Index and Vertex) to achieve my goals. Like before: My shader compiles fine using a BUFFER_RW, but again, it seems like binding dynamic buffers is not supported in the bgfx Metal backend.
Generally writing to and reading from buffers is now supported in Metal's fragment shaders. See: What’s New in iOS 10, tvOS 10, and macOS 10.12
Function Buffer Read-Writes Available in: iOS_GPUFamily3_v2, OSX_GPUFamily1_v2 Fragment functions can now write to buffers. Writable buffers must be declared in the device address space and must not be const. Use dynamic indexing to write to a buffer.
Or is there someone who already did an A-Buffer implementation in bgfx who could help me or give me some hints?
I would use compute shaders to do that, but I don't see how an A-Buffer could be achieved without rasterization?!
Thanks you and best regards!
Gabriel

Metal doesn't support atomic RW for texture, only for buffers. See changes @attilaz made for 39-assao to make it work around this Metal limitation.

Yeah, I have already seen that. But doesn‘t this example use compute shader? I would need a buffer in a fragment shader.
Sent with GitHawk


Organizing research

I personally am not very good at organizing the research aspect of the mod, so if anyone has any lore input or wants to just help w/ sorting out the research altogether then it would be greatly appreciated! It saves me the time of going through it all and allows me to focus on the programming. With school being as extremely tight as is, I'm lucky to have even a little bit of time to work on Magistics.

I think I can help a little bit... What do you want me to do?

Well, if you head over to the post-init method in the main mod file here, you can add in research! To add the localizations, just head over to the lang file and add them under the research category. That's basically just how you add it all in! If you add in the lore and recipes it would be an enormous help!

Actually, this may take a while because I only know basic basics of programming, I'll search for the Thaumcraft API for research and then I'll contact you.

Well, that's the thing; my system makes it super simple for anyone to add in research! Yes, you will have to know how to add the basic parameters for a ResearchItem, etc., but that's really simple. I've added the Hungry Ender Chest's research and such, so you can use that as an example.

I can do lore if you want. I'm retarded at coding, but I can pastbin like a boss

That would be great, thanks! You just need to edit the en_US.lang file under the lang folder in the resources to add research localizations! Lore for the crystal blocks I've added, as well as the hungry ender chest and iron chests would be great, then I could ship out a release that can hold people over for a while whilst I work on the hardcore stuff

edit the en_US.lang file under the lang folder in the resources to add research localizations!

Will try... If I screw something up, than sorry :P

Nevermind, could I just give you a pastebin? I can barely even find the file and I dont want to screw it up

You can find the file here, though I'm fine w/ looking at your stuff through PasteBin. You can use the research that's there as a template if you'd like!

Yeah, I have the intelligence of a sea lard when it ocmes to these things.  I'll link it in a bit.

Any progress?

I did 2 so far, and got bogged with work. Going to get like 5 donw before i show it to ya


pytest and idapython

saved filedescriptor not valid anymore

this is an issue with pytest capturing output. fix described here: http://stackoverflow.com/a/26831328/87207
pytest.main("--capture=sys")

I'm curious, are you running pytest tests within IDA?
How do you usually test this code? By manually running it within an IDA instance?

yes, running pytest tests within IDA. you need to kick off the test as a standalone script.
i suppose you could invoke IDA in bulk/scripting mode, but since i'm really only deving on my local workstation, its probably overkill. wish i could integrate with a CI service, but obviously can't distribute the IDA install.

I'm not sure if this will interest you, but I'm planning to take another approach for IDAPython testing - I'm going to mock IDAPython. At least the parts of IDAPython I need, and will probably find a way to use code from the idapython repo instead of duplicating it myself.
I only just began, but you can find the repository here: https://github.com/nirizr/pytest-idapro

neat! i'll keep my eye on that project.


Pass upstream error message on failed unmarshal

simpleyaml now passes along the upstream error message
from go-yaml, when it fails to unmarshal data. This
provides better feedback to the end user on why the
unmarshal failed.

Any chance this could get merged?

:+1:

^ bump

thanks

Thanks!

On Jan 28, 2016, at 7:26 AM, 陈小玉<EMAIL_ADDRESS>wrote:
thanks
—
Reply to this email directly or view it on GitHub https://github.com/smallfish/simpleyaml/pull/1#issuecomment-176155008.


Recurrent Attention Model using Transformer?

Hi, @clvcooke @kevinzakka @malashinroman
Visual Recurrent Attention Model using Transformer is not yet?
That is possible?
I wonder ...
Thanks.
Best,
@bemoregt.

Hey @bemoregt, maybe not a great place to ask (and I don't think any of the people you pinged are collaborators), but it certainly is possible. The recent VIT paper shows how to use transformers for image classification, so you could probably put them in place of the RNN cell used in RAM.
https://openreview.net/forum?id=YicbFdNTTy


Problems with Stripe pod > 8.0.4

This module broke for me (it's annoyingly only broken using xcodebuild on the command line). Downgrading to 8.0.4 Stripe pod seems to fix it.
I see the is a libPods-StripeNative.a file I can link. But linking both lib-StripeNative.a and libPods-StripeNative.a causes build errors. Linking just libPods-StripeNative.a makes this module not work.
Anyone seen anything similar?
PhaseScriptExecution Copy\ Pods\ Resources /Users/richard/Library/Developer/Xcode/DerivedData/Expresso-gybfpknncoufkpcmhtfgeinmrhnm/Build/Intermediates/ArchiveIntermediates/Expresso/IntermediateBuildFilesPath/StripeNative.build/Release-iphoneos/StripeNative.build/Script-DD70DAC5CB39583C7B4B0442.sh
    cd /Users/richard/Workspace/expresso/expresso-customer-app/node_modules/react-native-stripe
    /bin/sh -c /Users/richard/Library/Developer/Xcode/DerivedData/Expresso-gybfpknncoufkpcmhtfgeinmrhnm/Build/Intermediates/ArchiveIntermediates/Expresso/IntermediateBuildFilesPath/StripeNative.build/Release-iphoneos/StripeNative.build/Script-DD70DAC5CB39583C7B4B0442.sh
/Users/richard/Library/Developer/Xcode/DerivedData/Expresso-gybfpknncoufkpcmhtfgeinmrhnm/Build/Intermediates/ArchiveIntermediates/Expresso/BuildProductsPath/Release-iphoneos/Stripe.bundle
building file list ... done
Stripe.bundle/
file has vanished: "/Users/richard/Library/Developer/Xcode/DerivedData/Expresso-gybfpknncoufkpcmhtfgeinmrhnm/Build/Intermediates/ArchiveIntermediates/Expresso/BuildProductsPath/Release-iphoneos/Stripe.bundle/Localizable.strings"

<more file has vanished lines>

sent 3383 bytes  received 3676 bytes  14118.00 bytes/sec
total size is 372910  speedup is 52.83
rsync warning: some files vanished before they could be transferred (code 24) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-47/rsync/main.c(992) [sender=2.6.9]
Command /bin/sh failed with exit code 24

** ARCHIVE FAILED **

Hi @richardgill -- I think you don't want to explicitly link the pods.a file. It's been a while but I did write this at https://github.com/lrettig/react-native-stripe#installation, as I think I ran into the same issue before. Does it work fine for you without this?

Please reopen if still an issue


Add haproxy release to bosh release version number and patched version

Change versioning in shipit script according to the "Versioning Guide"

I've reassigned to the approver group for review.

Just noticed this seems to be included in https://github.com/cloudfoundry/haproxy-boshrelease/pull/398/files?
Please request the review only after the proposal is finalized

@Mrizwanshaik, please remove the merge commits and rebase your changes on top of master


Error when starting Homebridge

When starting the Homebridge the following error appears from the plugin:
[homebridge-nb] This plugin threw an error from the characteristic 'Heartrate': Characteristic Property maxValue was set to 600, but for numeric format uint8 maximum possible is 255. See https://git.io/JtMGR for more info.

See #22.  Please re-install Homebridge NB.


Add Client#epic method

There's already a Client#story method for looking up stories without going through a Project. It would be nice to have the same capability for epics.
I'm happy to implement this myself and submit a PR if that's OK.

This is supported in Tracker's API v5 via the /epics/{epic_id} endpoint.


4.0.1: How to modify the initialization time zone?

I found that<EMAIL_ADDRESS>uses UTC0 (Universal Coordinated Time) for countdown by default. How do I initialize the time zone?
demo: https://123.1px.run/time/
发现<EMAIL_ADDRESS>默认使用的是 UTC0 （世界协调时）进行倒计时，请问我应该如何初始化时区？
案例：https://123.1px.run/time/

If I correct understand, you need to call timezz with the needed timezone.
For example:
const timer = timezz('.timer', {
  date: moment(YOUR_DATE).utc().valueOf(),
});


training dataloader issue

how to get the "projection_matrix" file?

Hi, projection_matrix (768*768) is the CLIP projection matrix, which should be weight.data of Linear layer defined in CLIP (out_dim, in_dim). We actually didn't use the image embedding, therefore, you can comment out this line. Let me know if you have further questions.

update: I have pushed the codes with this line cemented out, plz let me know if you meet other issues.

I review the decode processed data, and find the corresponding caption of every segmantion is empty, is it normal?

thanks for your answer, i used the coco dataset to process, and the key "is_det" in data is 0, so caption information in the decoded data can not be obtained.
I just wander waht the key "is_det" meaning? and the meaning of o365 in the corresponding comment "# if it is from detection (such as o365), then we will make a pseudo caption"

If is_det is 0, the model will use the generated instance captions. Otherwise, it will use the category name (from ground-truth or an object detection model) as the pseudo instance caption.


Create a contact info block

Add links to social networks (LinkedIn, Facebook, Instagram), phone number, email, Telegram username, etc.

Add links to social networks (LinkedIn, Facebook, Instagram), phone number, email, Telegram username, etc.

Done - https://github.com/ticial/homepage/pull/32/commits/7e7fc161d9e4083921eef634d32d0d616b0202c6


Cannot put focus on sidebar scrollbar

On the main screen (in grid view or list view) if the sidebar is enabled and the description is longer than the window a scrollbar shows up but is only accessible via the mouse. When using a controller there isn't actually a way to navigate over to the scrollbar and interact with it.
Desired behavior would be to allow use to input Circle/B to put focus on scroll bar and use up and down or right stick up and down to interact with it. left arrow input would put focus on filter presets.

Unfortunately I don't have that much control from themes. This would not be possible. Making the description area focusable causes issues elsewhere. Realistically you'd go to the Game Details page to read the full description, and the Main page just shows a snippet of the description, I wanted to have an ellipses (...) at the end of the description, but that is also not possible as the descriptions have to be in a HTML View which doesn't have that feature.


Organize 4.0.0 change list

Keeping all changes in a single list means users only have to look
in one place when they upgrade.
In this case, the "Removed" item was really obvious, but in general
a single list is a good practice, I think.
A single list is also recommended by http://keepachangelog.com/
which I'm a big fan of.
[ci skip]

Ben, just wanted to run this by you in case you had strong feelings about "Removed" vs. "Changed"

I don't actually have a strong preference one way or the other. I guess I just wanted to put the "Removed" piece in bold to help make it stand out in case any users ran into this.  Last time something was removed from PaperTrail there was a lot of questions filed in the issues tracker about what happened with it if I remember correctly. Then again, I didn't really start following good semantic versioning practices until prep for 4.0.0