Daemon connectivity problems

after installing elvish on bash/windows subsystem for linux I am greeted with this warning:
warning: socket exists but not responding version RPC: dial unix /tmp/elvish-1000/sock: connect: connection refused

followed by this error:
Failed to initialize command history. Disabled.

this question is did I do something incorrectly, or does this stem from the wsl?

Originally I got this error:
warning: cannot start daemon: cannot find elvish: not found cannot connect to daemon after 1s: dial unix /tmp/elvish-1000/sock: connect: no such file or directory
After creating the directory sock in /tmp/elvish-1000 I got your error above.  When I exit I get the following, which may have nothing to do with anything--it's gibberish to me--but just in case:
`panic: runtime error: invalid memory address or nil pointer dereference [recovered]
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x74f586]
goroutine 37 [running]:
github.com/elves/elvish/eval.catch(0xc420041f80, 0xc420396500)
/home/travis/gopath/src/github.com/elves/elvish/eval/eval.go:312 +0x241
panic(0x92ee40, 0xdf6080)
/home/travis/.gimme/versions/go1.8.linux.amd64/src/runtime/panic.go:489 +0x2cf
net/rpc.(*Client).Close(0x0, 0x10, 0xc4203922e0)
/home/travis/.gimme/versions/go1.8.linux.amd64/src/net/rpc/client.go:280 +0x26
github.com/elves/elvish/daemon/api.(*Client).Close(0xc420121680, 0x7f5e64195e10, 0x0)
/home/travis/gopath/src/github.com/elves/elvish/daemon/api/client.go:44 +0x43
github.com/elves/elvish/eval.preExit(0xc420396500)
/home/travis/gopath/src/github.com/elves/elvish/eval/builtin_fn.go:1406 +0x36
github.com/elves/elvish/eval.exit.func1(0x0)
/home/travis/gopath/src/github.com/elves/elvish/eval/builtin_fn.go:1280 +0x2a
github.com/elves/elvish/eval.exit(0xc420396500, 0x0, 0x0, 0x0, 0xc420366300)
/home/travis/gopath/src/github.com/elves/elvish/eval/builtin_fn.go:1285 +0x14c
github.com/elves/elvish/eval.(*BuiltinFn).Call(0xc42012e660, 0xc420396500, 0x0, 0x0, 0x0, 0xc420366300)
/home/travis/gopath/src/github.com/elves/elvish/eval/builtin_fn.go:55 +0x5c
github.com/elves/elvish/eval.String.Call(0xc42016ba28, 0x4, 0xc420396500, 0x0, 0x0, 0x0, 0xc420366300)
/home/travis/gopath/src/github.com/elves/elvish/eval/string.go:60 +0x89
github.com/elves/elvish/eval.(*String).Call(0xc420390100, 0xc420396500, 0x0, 0x0, 0x0, 0xc420366300)
:34 +0x88
github.com/elves/elvish/eval.(*compiler).form.func3(0xc420396500)
/home/travis/gopath/src/github.com/elves/elvish/eval/compile_op.go:266 +0x8f5
github.com/elves/elvish/eval.Op.Exec(0xc4203a8000, 0x0, 0x4, 0xc420396500)
/home/travis/gopath/src/github.com/elves/elvish/eval/compile_op.go:23 +0x45
github.com/elves/elvish/eval.(*EvalCtx).PEval(0xc420396500, 0xc4203a8000, 0x0, 0x4, 0x0, 0x0)
/home/travis/gopath/src/github.com/elves/elvish/eval/eval.go:281 +0x98
github.com/elves/elvish/eval.(*compiler).pipeline.func1.1(0xc420396500, 0xc4203a8000, 0x0, 0x4, 0xc42039e030, 0xc420390120)
/home/travis/gopath/src/github.com/elves/elvish/eval/compile_op.go:85 +0x4d
created by github.com/elves/elvish/eval.(*compiler).pipeline.func1
/home/travis/gopath/src/github.com/elves/elvish/eval/compile_op.go:92 +0x2c7
`

Did you put elvish binary at your PATH, eg /usr/bin, /usr/local/bin
I think this common error should be addressed somewhere or let elvish to find its binary.  @xiaq

my path is correctly set up, and the shell works for me (at least, for the 10 min I had to play with at the time). I'm not entirely sure what the socket warning deals with, I haven't dealt in depth with sockets at all, but the command history definitely does not work for me right now. I have also installed elvish on my mac with homebrew and everything works fine there.

Maybe related, but I also got this error:
warning: cannot start daemon: cannot find elvish: not found cannot connect to daemon after 1s: dial unix /tmp/elvish-1000/sock: connect: no such file or directory
I took a look in the latest /tmp/elvish-1000/daemon.log and saw this:
[daemon] 2017/07/11 10:48:16 failed to create storage: failed to initialize command history table: database is locked
Then removed the following directory $HOME/.elvish/db.lock. That seemed to solve it for now.

I have encountered this a couple of times, it would seem like the daemon dies leaving behind the socket but with no process behind it. Usually removing the elvish tmp directory makes it work again.

This keeps happening to me whenever I don't use the shell for some time (at least several hours). Any way to permanently fix it rather than deleting the sock every time it happens?

@markkuit Related code has changed several times; can you update to HEAD and start from clean state (kill all elvish processes, remove temp directories) and see if this still happens?

More details: This bug is caused by either the daemon failing to start up, or the daemon crashing after startup. The former case is caused by #496 most of the time, which is now fixed.
In the latter case, the daemon may have left some logs in the temporary file: look at /tmp/elvish-(id -u) to see if there are files named daemon.log.* and paste the content here.

Okay , I'm able to easily replicate this on my phone running termux , boot elvish and then force remove termux from memory : this one is from normally exiting elvish before closing termux
[daemon] 2017/12/15 07:41:47 No active client, daemon exit
[daemon] 2017/12/15 07:41:47 listener closed, waiting to exit
[daemon] 2017/12/15 07:41:47 Failed to accept: &net.OpError{Op:"accept", Net:"unix", Source:net.Addr(nil), Addr:(*net.UnixAddr)(0x44201a0c00), Err:(*errors.errorString)(0x44200340f0)}
[daemon] 2017/12/15 07:41:47 exiting
This is how it looks like when I force close termux and don't exit elvish :
[daemon] 2017/12/15 18:49:47 pid is 4138
[daemon] 2017/12/15 18:49:47 going to listen /data/data/com.termux/files/usr/tmp/elvish-10201/sock
[store] 2017/12/15 18:49:47 initializing store
[store] 2017/12/15 18:49:47 initialized store
[daemon] 2017/12/15 18:49:47 starting to serve RPC calls
And then nothing . Hope this helps .

I think that the root cause is in the fact that when the parent process goes into a certain state or gets killed , the daemon fails to close the socket and then can't open it again .
From my 2nd termux instance I manually sent sigterm to the 1st termux process hosting and elvish that couldn't connect to the socket . Upon re-opening termux and starting elvish , apparently the socket got closed when sending manual sigterm even if it wasn't connected .

@xiaq The culprit seems to be the daemon getting killed before the elvish instances connected to it .The sock gets closed but the file remains there making it think that there is a daemon running, when a new elvish instance finds it , it can't connect . To easily reproduce : kill -s SIGKILL  . I'll try to come up with a fix but I think that there's a few things to take into consideration like when and where the sock should be handled . Any suggestions ? I was currently thinking of handling it at runtime .

Right, when the client tries to connect to the daemon, it only checks the existence of the socket file to determine a daemon should be spawned.
Normally, when the daemon gets terminated by SIGTERM or quits itself automatically, the socket file is removed; but if it is killed with SIGKILL the socket file is not, leaving the client thinking that a daemon is still running.
We can use a more sophisticated daemon status check; I can think of two ways:

Not only check the existence of the socket file but also attempt to connect to it: if connection fails, remove the socket and spawn a daemon. However, this may suffer from false negative where the daemon is running but unresponsive:
i. A code bug causes daemons to become unresponsive shortly after startup. Now each Elvish instance will now start a daemon. This is quite unlikely though, given that the daemon implementation is basically handleFlags(); for { client = accept(); go handle(client) }.
ii. The daemon has become overloaded. In this case, the newly spawned daemon will not have access to the database (boltdb does not support concurrent access from multiple processes). The new daemon won't quit, however; it just accepts connections and return errors for RPCs that need to access the database. The old daemon continues to serve Elvish instances that were talking to it but won't accept new connections. This is not exactly a good failure mode, but doesn't sound too problematic.

Write a PID file when daemon starts up. Instead of checking if the socket file exists, check if the process is running; if it is not, then remove the socket and PID file, and spawn a daemon. This, on the other hand, may have false positive as PIDs can be reused. It can be somewhat mitigated, however, by checking certain properties of the process (e.g. whether the command line contains elvish -daemon).

We can also use a combination of both techniques:
func autoSpawn() {
  if socket file does not exist {
    print to debug log "auto-spawned daemon"
    spawn()
    return
  }
  if connection to socket succeeds {
    return
  }
  if process with pid is running {
    if process looks elvish daemon {
      print to user "daemon is running but cannot be connected to"
      // don't spawn
      return
    }
    print to user "pid exists but does not look like elvish daemon, considering daemon dead"
  }
  print to user "daemon is dead, auto-spawning"
  remove socket and pid files
  spawn()
}

This eliminates the possibility of false negative of 1, although it has the same false positive problem of 2.

Hmm...I was thinking of making it simpler , I was looking at the runtime.go check where the os.Stat(sockpath) happens , the result of os.Stat(sockpath) seems to modify each time a new client opens on an active socket(os.Stat returns FileInfo , which has a Sys() component that seems to be the interface of the underlying data source ) , since anything we do results in a change in the output of os.Stat.Sys() while the daemon is active , but it is the same if it has no daemon attached to it. Ex :
Here is an active daemon :
&{sock 0 16777664 {641040709<PHONE_NUMBER>1 0xbbeaa0} {35 18648850 1 49600 0 0 0 0 0 4096 0 {1513609897 857707376} {1513609881 641040709} {1513609881 641040709} [0 0 0]}}
&{sock 0 16777664 {641040709<PHONE_NUMBER>1 0xbbeaa0} {35 18648850 1 49600 0 0 0 0 0 4096 0 {1513609917 941040709} {1513609881 641040709} {1513609881 641040709} [0 0 0]}}
For an inactive daemon , the socket remains unmodified so I was thinking we could use this to our advantage and "profile" the daemon's state that way ? Although , I think that we can just fix this by just adjusting the error handling . I already made a "fix" for just checking this case and it seems like even the initial elvish that had his daemon killed is able to reconnect :smile: . I'll make a pull request with my "sort-of" fix :) .

Experiencing exact same issue as OP as of v0.12-508-g14121baa a.k.a. 14121baa. Running rm -r /tmp/elvish-* works as a workaround, but it seems like the issue is not really fixed, after all.

I'm on HEAD and see this message still when I launch my first elvish shell, even after a reboot and no /tmp/elvish-*
Cannot connect to daemon: daemon unreachable after waiting for 1s
Daemon-related functions will likely not work.

@dangerousHobo It's been my experience this only happens if you launch two elvish instances more or less simultaneously. For example, I use a shell script to setup multiple tmux sessions to all the systems I use for development. This involves starting six interactive shells on each system as quickly as possible. This would frequently result in the failure discussed in this issue on at least one system (typically my Windows+MSYS platform). After I modified that script to sleep one second after starting the first elvish instance on each platform I stopped seeing this failure.
Rather than fix this race condition in the long term I'd like to see the daemon eliminated. It appears to exist solely due to the database that is used for storing interactive history. If it were replaced with a database that allowed concurrent access from multiple clients the daemon wouldn't be necessary.

I saw this or a similar problem on Windows.
Cannot connect to daemon: unexpected RPC error on socket C:\Users\John\AppData\Local\Temp\elvish-John\sock: dial .
Daemon-related functions will likely not work.

Deleting the C:\Users\John\AppData\Local\Temp\elvish-John directory resolved my daemon connectivity issues.


[FEATURE] : Dynamic Search Results Update in Search Bar on homepage

Issue Template
Description
The search bar on the homepage of the website does not filter results until the search button is clicked. I propose that the search results should be updated dynamically as the user types, allowing for a more efficient and user-friendly experience.
Steps to Reproduce

Go to the homepage of the website.
Locate the search bar.
3 .Start typing in the search bar.
Notice that the results do not filter until the search button is clicked.

Expected Behavior
I expected the search results to update in real-time as I type in the search bar, providing immediate feedback and making it easier to find notes.
Actual Behavior
Currently, the search results remain unchanged until the search button is clicked, requiring additional steps to view filtered results. This can be cumbersome and slows down the search process.
Screenshots
Additional Context

Hello !!!! It would be great if you assign this issue to me under GSSoC extd and hactoberfest accepted label

Thanks for raising this issue . Assigned @DevanshS9881

Can you assign it to me


Home screen: Alignment issue.

Alignment does not look right.

Verified this issue on keeper app v 1.1.11(295)


Minor documentation improvements

Fixes #2424

Merged as f66e12ac4de43f5b31c31abf035a2c954e9d4691 (made a small tweak to the commit message style).  Thanks @zbenjamin!


Want to integrate in my project.

Am I allowed to integrate same demo as yours, into my project?
Will there be any Policy that will broken if I integrate the same in future?

Hi @Rashesh-Bosamiya,
Yes, you can integrate this demo into your project. This project is distributed under the MIT license so you are free to copy, modify and use it as you see fit.
This demo is just a side project so I can make no promises to breaking things in the future. I may add or change functionality. So, it is best to fork this project because master may change drastically.


No template for "Subscription requests (requiring approval)"

There is no template for the e-mail that is send to the administrator when a new subscription requests is made. The current template still points to the old Administrator portal, which cannot be used anymore.
I want to alter the template so it links to the subscriptions page on the Azure portal.

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

ID: a55c0a23-de53-df95-fcc9-70cebebf3d0c
Version Independent ID: 51f1b3fc-aa47-110b-6de9-e4fec8c5b269
Content: Configure notifications and email templates in Azure API Management
Content Source: articles/api-management/api-management-howto-configure-notifications.md
Service: api-management
GitHub Login: @vladvino
Microsoft Alias: apimpm

Hi @rverschuur - Thank you for your feedback! We will review and update as appropriate.

Please assign this to @mikebudzynski

@rverschuur Thank you for raising this Issue; we're aware of the current limitation. At this moment, you can't modify administrator templates. I took a note of your requirement and we will keep it in mind once we get down to the feature implementation work.
#please-close

Thank you!


look for tools for code documentation and build the documentation with CI

Maybe this could be a start? https://guide.esciencecenter.nl/#/best_practices/language_guides/ccpp?id=documentation

All the configuration and instructions are added in #122. The code documentation is automatically built by readthedocs.


Methods should have a consistent I/O

I'm new to Dart (looking at this package for numerical analysis)
It looks like some of the methods (eg. reshape)  accept and return a List whereas others (slice) require a List<List> so that the output of one method can't be passed to another

I'm not certain I'm doing this correctly :-), but this will reproduce
 var list = [
      [1, 2],
      [1, 2],
      [8, 5]
    ];
    var list2 = [
      [9, 2],
      [9, 2]
    ];
    var concat = m2d.concatenate(list,list2);
    print('concatenated: $res');

    concat.reshape(3, 4);
    //    List<List> ress = m2d.reshape(res,3, 4);  // consistency with other methods would suggest this approach
    print('reshaped: $concat');
    print('res shape: ${concat.shape}');

    var sliceOfConcat = m2d.slice(concat, [2], [3]); // wrong input type
    print('slice: $sliceOfConcat');


Condition to Match Array (set ) intersection

Example : Key : [1,2,3,4]
Value = [4,7,8]
Result TRUE
Also Counter condition ( NOT ) should also be there

This is also done. Opening a new issue which makes this a part of the current range operator itself.


Deprecate MNE-Binder in favour of MNE-Docker

As discussed in #9
All efforts are now focused on MNE-Docker and this works well with Binder

@agramfort maybe also archive the repository if you're inclined.


docs: add screen shot to quickly view how the app looks like

@mikaoelitiana Thanks for the idea! I'm sorry I didn't get time to review it before you closed it.
I think you're right: we should add some image or gif or even video to show what the app looks like, and how it works.
For now, how about something like this:


Project action

Summary of changes

Changes introduced in this pull request:
Reference issue to close (if applicable)

Closes #2503
Other information and links

Change checklist

[x] I have performed a self-review of my own code,
[x] I have made corresponding changes to the documentation,
[x] I have added tests that prove my fix is effective or that my feature works (if possible),
[x] I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

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

@lerajk Here's the PR for the action

@tyshko5 could you please show an example of how it works and how it populates the board? E.g, by creating a separate repository with this workflow (or forking Forest I guess)

@tyshko5 could you please show an example of how it works and how it populates the board? E.g, by creating a separate repository with this workflow (or forking Forest I guess)

I tested it here https://github.com/tyshko5/test_actions @LesnyRumcajs

@tyshko5 could you please show an example of how it works and how it populates the board? E.g, by creating a separate repository with this workflow (or forking Forest I guess)

I tested it here https://github.com/tyshko5/test_actions @LesnyRumcajs

Can you provide the link to the filled board?

@tyshko5 could you please show an example of how it works and how it populates the board? E.g, by creating a separate repository with this workflow (or forking Forest I guess)

I tested it here https://github.com/tyshko5/test_actions @LesnyRumcajs

Can you provide the link to the filled board?

https://github.com/users/tyshko5/projects/1

@tyshko5 the board may be private, I get 404.

@tyshko5 the board may be private, I get 404.

made it public

@tyshko5 what about the dates we talked about? The issue should have a date on the board when it was closed.

@LesnyRumcajs Looks like there is no way to fill the columns of any kind. The action can just add to the board based of an event and labels and that's it. https://github.com/tyshko5/test_actions/actions/runs/4127203186/jobs/7130118472#step:2:1

If @lerajk is okay with this and filling the dates manually, then I'm fine. Otherwise, there's a way, but it's a bit more complex to implement. See the example here. Most likely we could snatch it and customize it to our needs.


Logging command updatebuildnumber fails and then succeeds

...but it fails the build...
So I have this:
Write-Host "##vso[build.updatebuildnumber]$newBuildNumber"
in a powershell step at the start of my build.
I get the most peculiar behaviour. The step registers a failure, but it still updates
However, because of the failure, the build does not continue.
Here's the log section:

@TheBeardedLlama i think something more is going on. the agent intercepts the command from STDOUT, and performs the update build number action. the agent - separate process simply reading STDOUT from your script - doesn't know anything about the powershell variable you used to construct the command. the error message contains $newBuildNumber") and indicates to me that your command is malformed. to get a better idea of what is actually being written over STDOUT, either:

consult the worker log in the _diag folder under the agent. i think it contains the full unparsed ## command
or 2) change your script to instead print something like Write-Host "vso[build.updatebuildnumber]$newBuildNumber" (removed leading ##) so you can verify the structure of the command you are writing.

also i just noticed you are using the powershell++ task, so i dont know if that is causing any interference (not a task in this repo). if you can repro with the regular powershell task then that would rule that out.

@ericsciple you hit the nail on the head with your closing remark
I was told to use that task type and I didn't parse that in my head
switched to standard powershell task and it's all happy
many thanks for the assistance


[FEATURE REQUEST] AWS Kinesis streaming source for HoodieStreamer

HoodieStreamer have a KafkaSource, but didn't find KinesisSource. Requesting to create this source.

There are couple of JIRA open for the same. Feel free to contribute in case you are interested. I can help you if needed.
https://issues.apache.org/jira/browse/HUDI-310
https://issues.apache.org/jira/browse/HUDI-1595

I love it

@ad1happy2go  I can take this up. Can you connect once and help me to start.

That's Great @manishgaurav84 . I will connect on slack.


Somerville, MA (/somerville)

closes #1252

Why is this being tagged as a "new email pr"??
https://github.com/defund12/defund12.org/blob/master/_emails/us/massachusetts/somerville.md
Somerville already exists here.

Ah you removed the label.

Ah you removed the label. Why are you adding whitespace to line breaks in these PRs? @rpalakkal

Ah you removed the label. Why are you adding whitespace to line breaks in these PRs? @rpalakkal

Yeah - thought it was a new email at first but then saw that it already existed. I've always added a line between paragraphs, as I thought it was required to parse correctly, but now I think the gatsby transformer outputs the same thing from both. Is adding an empty line between paragraphs ok?


Digest proxy example

Proxy digest to sign a hash, but use another hashing algorithm for deterministic nonce generation.

For some reason
#[test]
    fn recover_signature_from_message()

is broken (and it was in the original I suppose), but I didn't dig into it.
Also, I didn't check for any test vector for nonce generation compared to libsecp256k1 (C library), but from high level those should immediately match.

Fixed the test, refactored and cherry-picked on https://github.com/gakonst/ethers-rs/pull/72. Thanks a lot @shamatar!!


Clean up PP module and library skeleton

Attempt to clean up and address some of the issues in our modules for the upcoming release. Please comment here if you find other problems.

Require Python 3 in create_library_skeleton.py. This is because it uses format strings. Since this is only for internal use, I think it's fine to require 3 here.
Rename hpx.pp to hpx_preprocessor for consistency (the underscore) and understanding (full name). I haven't changed the names of the header directories, but will do so if we agree on that.
Use rst for all READMEs and clean up some of the markup (to be consistent with the main docs).
Put generated headers and symlinks to libs headers under include/generated and include/libs to have a common place for them.
Maybe fix source groups for the preprocessor module? This is still to do, if necessary.

This hopefully includes all the fixes from #3809 without the config modules. Also probably replaces #3806.

@hkaiser I tried to do something for the source groups. Could you give it a try when you have time?

@msimberg also, should we add #3813 to this as well?

I tried to do something for the source groups. Could you give it a try when you have time?

@msimberg A quick try shows that whatever you did has not had any positive effect on the source group issue. I will have a closer look later.

I moved the generated headers back to where they were. The only thing that now still doesn't work is APEX integration. We a few options, none of which are good, but we'll just have to pick one.

Add back the collected symlinked headers for modules and add a global include_directories to point to there (as in #3806).
Add global include_directories only for the parts that APEX needs as a special case. This is least disruptive in both HPX and APEX.
Add hpx_preprocessor as a dependency to APEX. This sounds bad at first glance, but considering APEX depends on a small subset of HPX (I think) the list of modules it'd have to depend on shouldn't grow very large.

@msimberg I think we should go with option 3 (add dependencies to APEX). That is the least intrusive and most cmake-like variant.

@msimberg do you still plan to rename the files (pp -> preprocessor)?

@msimberg I think we should go with option 3 (add dependencies to APEX). That is the least intrusive and most cmake-like variant.

Yeah, that's fair enough. It's not 100% right because APEX should depend on the hpx target which would give hpx_preprocessor for free, but it doesn't because of the circular dependency. Let's go with this though.

@msimberg do you still plan to rename the files (pp -> preprocessor)?

Yeah, I'll do it. We've already broken compatibility by moving them so I think it makes sense. The last thing I'm not going to change though is the macro names.

It's not 100% right because APEX should depend on the hpx target which would give hpx_preprocessor for free, but it doesn't because of the circular dependency. Let's go with this though.

I rather see at as APEX being one of the modules we will create in the future.

The last thing I'm not going to change though is the macro names.

Fair enough!

It's not 100% right because APEX should depend on the hpx target which would give hpx_preprocessor for free, but it doesn't because of the circular dependency. Let's go with this though.

I rather see at as APEX being one of the modules we will create in the future.

I think we agree! I meant "should" more in the sense that it should right now but, yes, ideally in the future it wouldn't.


Discovering multiple matching branches at one time breaks generation task

If there are multiple branches that it deems ready to spin up new pipelines for, the job breaks as it is not properly generating the yaml. Here is an example output from the branch-manager job:
jobs:
- name: Unit Test (feature-concourse-pipeline-generator)
  plan:
  - get: Contracts(feature-concourse-pipeline-generator) #TODO: change to your source repo
    resource: Contracts(feature-concourse-pipeline-generator)
    trigger: true
    params: {depth: 20}
  - task: Test
    config:
      platform: linux
      image_resource:
        type: docker-image
        source: {repository: docker.artifactory.homedepot.com/flow/rubymysql, tag: latest }
      inputs:
        - name: Contracts(feature-concourse-pipeline-generator)
      run:
        dir: Contracts(feature-concourse-pipeline-generator)
        path: ./ci/build-branch.sh
      params:
        TARGET_ENV: acceptance
        ENVIRONMENT: acceptance
        CF_API_ENDPOINT: api.run-np.homedepot.com
        GITHUB_PRIVATE_KEY: {{github-private-key}}
        GITHUB_TOKEN: {{github-token}}
        DEPLOYMENT_USER: {{deployment-user}}
---> DEPLOYMENT_PWD: {{deployment-pwd}}- name: Unit Test (feature-test-pipeline-generator) <---
  plan:
  - get: Contracts(feature-test-pipeline-generator) #TODO: change to your source repo
    resource: Contracts(feature-test-pipeline-generator)
    trigger: true
    params: {depth: 20}
  - task: Test
    config:
      platform: linux
      image_resource:
        type: docker-image
        source: {repository: docker.artifactory.homedepot.com/flow/rubymysql, tag: latest }
      inputs:
        - name: Contracts(feature-test-pipeline-generator)
      run:
        dir: Contracts(feature-test-pipeline-generator)
        path: ./ci/build-branch.sh
      params:
        TARGET_ENV: acceptance
        ENVIRONMENT: acceptance
        CF_API_ENDPOINT: api.run-np.homedepot.com
        GITHUB_PRIVATE_KEY: {{github-private-key}}
        GITHUB_TOKEN: {{github-token}}
        DEPLOYMENT_USER: {{deployment-user}}
        DEPLOYMENT_PWD: {{deployment-pwd}}
resource_types:

As you can see in the highlighted line, the next job was printed on the same line as the previous param. This is causing the following error:
target saved
Updating pipeline...
failed to unmarshal configStructure: yaml: line 19: mapping values are not allowed in this context
/usr/lib/ruby/gems/2.2.0/gems/process_helper-0.0.3/lib/process_helper.rb:117:in `handle_exit_status': Command failed, pid 28 exit 1. Command: `/tmp/d20170324-7-8eboiv/fly --target=concourse set-pipeline --config=/tmp/d20170324-7-1xlmyt4/pipeline.yml --pipeline=cbm-contracts --load-vars-from=credentials-repo/secrets.yml`. Command Output: "failed to unmarshal configStructure: yaml: line 19: mapping values are not allowed in this context (ProcessHelper::UnexpectedExitStatusError)
"
	from /usr/lib/ruby/gems/2.2.0/gems/process_helper-0.0.3/lib/process_helper.rb:22:in `block in process'
	from /usr/lib/ruby/2.2.0/open3.rb:199:in `popen_run'
	from /usr/lib/ruby/2.2.0/open3.rb:188:in `popen2e'
	from /usr/lib/ruby/gems/2.2.0/gems/process_helper-0.0.3/lib/process_helper.rb:12:in `process'
	from /tmp/build/0e9e5171/concourse-branch-manager/tasks/lib/cbm/pipeline_updater.rb:38:in `set_pipeline'
	from /tmp/build/0e9e5171/concourse-branch-manager/tasks/lib/cbm/branch_manager.rb:49:in `run'
	from concourse-branch-manager/tasks/manage_branches.rb:7:in `<main>'

I just tried adding more new lines at the bottom of my template yml and it is now on a different line, however I still get the same error.

It is also happening in the resource template as well. Adding the new line to my resource template fixed the problem completely. I think the solution is more resiliency to add a new line before writing out the next resource or job.

Hi @crstamps2,
Thanks for the feedback.
However, we aren't using concourse branch manager anymore and won't be maintaining it.
I'd be happy to turn it over to someone who would like to maintain it, or, in the meantime, to accept (but not validate or test) any PRs.

bummer. Are you using an alternative? I may be willing to take this over.

We are moving to a different tool.  If you are interested in taking over,
you can email me directly and we can discuss it further.
El El vie, mar. 24, 2017 a la(s) 10:21 AM, crstamps2 <
<EMAIL_ADDRESS>escribió:

bummer. Are you using an alternative? I may be willing to take this over.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pivotaltracker/concourse-branch-manager/issues/9#issuecomment-289087225,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAAnuV650QCqN5AjxnjIrCOlHvPnLp9ks5ro_usgaJpZM4MoW5i
.


Recent Upgrade results in HASS integration not functioning

Version of the custom_component
v3.0.0
-->
Configuration
Frigate itself is running perfectly, it's just the HACS integration for home assistant that I can't get to run.
My configuration is working great,  all camera streams are working.
Describe the bug
Frigate itself is running perfectly, it's just the HACS integration for home assistant that I can't get to run. (despite installing in the order described in the documents on the Frigate website).   I would just like to expose the cameras and motion within home assistant to get my automations working correctly again.   I'm not sure how to log items that are installed in HACs.

Frigate itself is running perfectly, it's just the HACS integration for home assistant that I can't get to run.

Can you explain what error you are seeing, what difficult you are having and the steps you are trying? As-is, I'm afraid there is no information provided in the issue report from which to help you.

Thanks for your quick feedback @dermotduffy .  You can probably sense the awkwardness in my attempt to put this to words.   Let me try again:

Before the recent Frigate upgrade, I had Frigate running within home assistant, alongside the HASS integration.   My problem is with the HASS integration -- as the "value add" it provides is the generation of entities for important items as boolean_sensors for the cameras, MotionDetected, etc. etc.
My problem statement is:  Since the upgrade last week,  no matter how many times i install the base Frigate addon AND the HACS HASS integration function, I can't seem to find a way for the two to expose those integration "Sensors".

I guess my first ask - is "is there a suggestion you have for troubleshooting that the HASS integration in HACS is working? "
Ie.,  When does it go into the Frigate configuration and identify all the cameras and create all of the unique motion and binary sensors?   Is there a way i can review that and send you the logs?   As i mentioned earlier, the logs from the primary Frigate add-on dont yield anything-- because the Frigate Add on itself is working just fine.  It's the "exposing" of Frigate functions within Home assistant that I'm trying to do--- and it's hard to troubleshoot the "absence" of them.   Thanks in advance for bearing with me.

What happens on each step of these installation instructions:
https://docs.frigate.video/integrations/home-assistant/#integration-installation
Can you complete these successfully? Can you see the Frigate integration installed if you go to the HA settings, under Device & Services?

Ahhhh,  Thank you. I went through it one more time and I figured it out.     Line for line I confirmed somehow another character was added to the "ccab4aaf" prefix for the add-on.   After reinstalling the HAC's integration, I'm good to go.   Thanks for walking it through with me!  TGIF.


Update name of the repository in README and package.json, and deprecate the old one

This repository is now named witnet-solidity-bridge.
We now need to update the README title, as well as the package name on package.json.
Then we need to deprecate the old witnet-ethereum-bridge NPM package with npm deprecate, which allows for a chosing custom message that can instruct the users to replace the old package for the new one.
After that, we will also need to update the name of the packages inside all our ecosystem's repos.

Hey team! Please add your planning poker estimate with ZenHub @aesedepece @aeweda @gabaldon @guidiaz

Everything is already done


Baseline PPO doesn't work

@taochenshh
Thanks for your great work!
When I try the command python scripts/train_baselines.py algo=ppo_algo task=AllegroHand isaac_param=True, Terminal doesn't output any meaningful information and Wandb doesn't init :(
Thanks for any advice!
Best,
Charlie

Sorry，there's something wrong with my conda environment.


Azure YAML Pipelines - Using template expression variables at non-global scope

Using the template expression variable syntax for a job-scoped variable is resulting in it being resolved to empty string. It seems that the compiler is not able to find a replacement value:

Template variables silently coalesce to empty strings when a replacement value isn't found.

Is this expected behavior? I could not find any mention of this in the documentation. Code example:
# Global variables are correctly replaced
variables:
  globalVar1: hello

extends:
  template: template.yml
    stages:
    - stage: stage1
      jobs:
      - job: job1
        variables:
          localVar1: world
        steps:
        - task: DisplayString
          inputs:
            stringToDisplay: ${{ variables.globalVar1}} ${{ variables.localVar1}}
            # This shows "hello "

Furthermore I have not been able to use the ${{ var }} syntax with variable templates either.

Hi @puya-ms thanks for reporting! We are working on more prioritized issues at the moment, but will get back to this one soon.

Still relevant...


Create Spread the Word page

Drafted by Katharine; pending stakeholder review as of Feb. 5, 2023.
Chris to do:

Share info from Heat Smart Alliance re: local legislation support/Spread the Word page
Chris to ask Heat Smart Alliance about flyers re: heat pumps for Spread the Word – they should have some already

Summary of edits/questions I see remaining:
For Chris
Homepage: Share testimonial photos + text ** blocker for homepage
“Spread the Word” page: share info from Heat Smart Alliance
DISCUSS on 2/21 - General review: look at top navigation and comment
DISCUSS what google drive the ‘social sharing’ copy should live on – current drive is not publicly viewable; should this be in Katharine’s GDrive?? Urban League?
For frontend team
Update images to edited versions on homepage
Create the “Spread the Word” page
Katharine to do
For the “Spread the Word” page:
Create flyer for local business
Create social sharing copy (TBD on where this should live; should it be a webpage or Gdoc)


Async Task intellitrace events

If I create a async task in controller and hook up intellitrace standalone collector which just uses HttpClient to call a web service then would trace be collected? I tried and it didn't result in any trace file.

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

ID: 995e3a2f-5674-63c4-5899-ba9a6b0e5da6
Version Independent ID: b93833ad-9195-96b4-6fac-8893836cde4e
Content: Using the IntelliTrace stand-alone collector - Visual Studio
Content Source: docs/debugger/using-the-intellitrace-stand-alone-collector.md
Product: visual-studio-dev15
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

@andysterland Andy, who might best answer this question?

HomeController.zip
HomeController WebService.zip
The web application (MVC Application controller code snippet shared as HomeController.zip)- "WEBUI" calls Web Service "WEBSERVICE"(Again MVC application and controller code snippet shared as HomeController WebService.zip) whose code snippet I have attached.
I am able to get trace files for "WebService" app however I am unable to get trace files for "WebUI" app.
Although the trace file for WebService doesn't have any informations probably because there are no intellitrace events for the method - GetEmpDetails().
Please note I am testing WebUI application - (method in HomeController.zip - Index() method) to check for trace files which is not getting generated.

@anantharamakrishnans  Thanks for your feedback; we appreciate it. To make sure that this is logged in the right place, please use the Report a Problem tool to report the issue. When you do this, your report becomes part of the work items that are listed in the in the Visual Studio Developer Community, which allows you to engage directly with the engineering team while they address and fix the problem.


Double checked locking for thread safe initialization of InternalLoggerFactor…

…y (default factory).
Motivation:
Current implementation of getDefaultFactory is not thread safe.
Modifications:
Implement holder pattern for lazy initialization of default factory.
Result:
Thread safe InternalLoggerFactory.

@jasontedor ptal

Might need to rework this a little bit as invoking io.netty.util.internal.logging.InternalLoggerFactory#setDefaultFactory will invoke io.netty.util.internal.logging.InternalLoggerFactory#newDefaultFactory.

Double checked locking might be the way to go.

Sounds good

Am 04.12.2016 um 15:36 schrieb Johno Crawford<EMAIL_ADDRESS>Double checked locking might be the way to go.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Replaced holder with double checked locking, unfortunately it is mutable and this seemed like the simplest approach.

LGTM...

Is there really a problem with two threads racing to initialize defaultFactory, they are just going to initialize it to the same instance? Also, this change does not protect against two threads racing via getDefaultFactory/setDefaultFactory, one initializing defaultFactory via getDefaultFactory when defaultFactory is null, and the other initializing the default factory via setDefaultFactory.
Taking a step back though, is it really necessary that defaultFactory be mutable after it is initialized? I wonder if it would be better to just rule that out:
diff --git a/common/src/main/java/io/netty/util/internal/logging/InternalLoggerFactory.java b/common/src/main/java/io/netty/util/internal/logging/InternalLoggerFactory.java
index 9f85e3646..32b143d3d 100644
--- a/common/src/main/java/io/netty/util/internal/logging/InternalLoggerFactory.java
+++ b/common/src/main/java/io/netty/util/internal/logging/InternalLoggerFactory.java
@@ -16,6 +16,8 @@

 package io.netty.util.internal.logging;

+import java.util.concurrent.atomic.AtomicBoolean;
+
 /**
  * Creates an {@link InternalLogger} or changes the default factory
  * implementation.  This factory allows you to choose what logging framework
@@ -33,6 +35,7 @@ package io.netty.util.internal.logging;
  */
 public abstract class InternalLoggerFactory {

+    private static AtomicBoolean set = new AtomicBoolean();
     private static volatile InternalLoggerFactory defaultFactory;

     @SuppressWarnings("UnusedCatchParameter")
@@ -54,24 +57,31 @@ public abstract class InternalLoggerFactory {
     }

     /**
-     * Returns the default factory.  The initial default factory is
-     * {@link JdkLoggerFactory}.
+     * Get the default factory that was either initialized automatically based on logging implementations on the
+     * classpath, or set explicitly via {@link #setDefaultFactory(InternalLoggerFactory)}.
      */
     public static InternalLoggerFactory getDefaultFactory() {
-        if (defaultFactory == null) {
+        if (set.compareAndSet(false, true)) {
             defaultFactory = newDefaultFactory(InternalLoggerFactory.class.getName());
         }
         return defaultFactory;
     }

     /**
-     * Changes the default factory.
+     * Set the default factory. This method must be invoked before the default factory is initialized via
+     * {@link #getDefaultFactory()}, and can not be invoked multiple times.
+     *
+     * @param defaultFactory a non-null implementation of {@link InternalLoggerFactory}
      */
     public static void setDefaultFactory(InternalLoggerFactory defaultFactory) {
         if (defaultFactory == null) {
             throw new NullPointerException("defaultFactory");
         }
-        InternalLoggerFactory.defaultFactory = defaultFactory;
+        if (set.compareAndSet(false, true)) {
+            InternalLoggerFactory.defaultFactory = defaultFactory;
+        } else {
+            throw new IllegalStateException("default factory is already set");
+        }
     }

     /**

@jasontedor we can do this as it will be a breaking change.

without the double checked locking wouldn't it be possible for getDefaultFactory to return null on one thread while the other is still constructing the factory? I did see the race between defaultFactory and getDefaultFactory but left that as there is a disclaimer [1] on the class.
[1] " * Please note that the new default factory is effective only for the classes

which were loaded after the default factory is changed.  Therefore,
{@link #setDefaultFactory(InternalLoggerFactory)} should be called as early
as possible and shouldn't be called more than once."

@normanmaurer Did you mean to say "can not"?

without the double checked locking wouldn't it be possible for getDefaultFactory to return null on one thread while the other is still constructing the factory?

@johnou You can also protect against with a CAS on an atomic reference but you're absolutely right, without some form of protection this can happen.

@jasontedor yes can not... sorry for the confusion

yes can not... sorry for the confusion

That's fine, I don't want to distract from this pull request but when can breaking changes be made, especially breaking changes for questionable use-cases (i.e., applications that set the default factory multiple times)?

@jasontedor in the next major release aka 5.0

in the next major release aka 5.0

I'm assuming this is very far off since there is not a branch for it?

Since the logger factories are essentially singletons I think using AtomicReference would be OK (doesn't matter if newDefaultFactory is invoked multiple times.

@jasontedor yes we have not start with 5.0 yet.

I still prefer the double checked locking for this specific use case but I think of others where cas would be appropriate. As I mentioned in a comment update above I think it's safer like this (code might be refactored or copied). That said I think Jason's proposal would be nice for next major release.

@johnou yes I think double looking is "ok" for this use-case and good enough. Let me merge this one

There is no risk of a dangerous race between two invocations of getDefaultFactory. If no protection is going to be added against races between 'getDefaultFactoryandsetDefaultFactory` (where there is risk of a dangerous race), nor my desire to just protect against multiple sets period, I don't think unnecessary locking should be added. If it's going to be added, I think a code comment remarking that it's unneeded but deliberate should be added.

And, to be clear, I do think protection against the getDefaultFactory/setDefaultFactory race should be added. Then I'm okay with adding locking here.

@jasontedor something like this?

@johnou Yes, that works, unless I can convince @normanmaurer permitting setting the factory twice is a bug to begin with in which case I think something stronger (like I proposed) should be the path.

yes we have not start with 5.0 yet.

@normanmaurer The more I think about this, the more I think it's a bug that Netty allows the InternalLoggerFactory to be set twice. Today it means that some objects will be class-level loggers using loggers from one factory (and they never reset because these are static fields), and some other objects will be using loggers from another factory. This already arose on our side where ThreadLocalRandom had its logger initialized with one of the built-in factories instead of the factory that we want it to be using (because of that premature optimization). I think you should disallow this, and I think it's a bug that today you do allow it (and, I certainly can't think of a valid use case for it).
So, I'm going to try again. 😇
I think is a bug, it should be fixed sooner rather than later, and I'm happy to open a PR with my proposed change above.

@jasontedor I am on a fence here... I agree with you that there should be no use-cases. Its just that netty is used everywhere and I am a bit afraid of breaking some app that uses it ... Let me think about it.

@normanmaurer fwiw it is mentioned in the javadoc.. "Therefore,

{@link #setDefaultFactory(InternalLoggerFactory)} should be called as early
as possible and shouldn't be called more than once."

@johnou Thank you, that's great. :smile:
@normanmaurer Are you more convinced it's a bug now? The Javadocs say do not call it more than once, the code just does not enforce it. Enforcing would do two things:

help users that do not realize they are not calling it early enough call it early enough (so that all loggers are created with their desired logger factory)
enforce what the Javadocs say regarding not calling setDefaultFactory it more than once

@johnou @jasontedor ok you convinced me... go for it

Why netty should support many logger factories? It create problems and overheads..
Usually java libraries provide logs only by slf4j api, and the target application uses one logger that wants. slf4j have bridges to logback, jul, log4j and others.

@fenik17 netty aims for being zero dependency for its core... Thats why.

@normanmaurer Ok! I will know.

Thanks @johnou for opening this PR as it triggered a conversation about just enforcing only allowing this to be set once. I opened #6106 to take that approach.

👍 thanks for taking the ball!


Export Android: Godot fails to build an APK file but then it builds successfully.

Tested versions
Godot 4.3 official release.
System information
Windows 11, Godot 4.3.
Issue description
Here is my projeect:
capybara_math_test.zip
I've recorded a video about the bug (export to android):
BugVideo.zip
Problem Description:
I've found that if I build an APK file with UseGradle=off the APK file will be corrupted/damaged and failed to build. Then if I set UseGradle=on and build again the APK file still will be corrupted. Then if I set back UseGradle=off and build again the APK file will be built successfully! A very strange bug.
My setup:
Java SDK 23.0.1
Android Studio 2024
Steps to reproduce
1 Download Java SDK 23 https://download.oracle.com/java/23/latest/jdk-23_windows-x64_bin.zip
2 Install Android Studio 2024 https://developer.android.com/studio
3 Install Android Packages. Tools ->SDKManager.

4 Open my Godot project
capybara_math_test.zip
5 Fix paths of AndroidSDK and JavaSDK

6 Build a project with Gradle=off

You will see this notification. The build fails and The APK file will be corrupted/broken.

7 Install Build Temlate:

8 Try to build again with Gradle=on

The build fails. You will see this notification.

9 Try to build again with Gradle=off.

The build will succeed and there will be no any warnings!!!
The build will succeed and there will be no any warnings!!!
The build will succeed and there will be no any warnings!!!
Minimal reproduction project (MRP)
Here is my projeect:
capybara_math_test.zip

unsupported class file major version 67 would imply you are trying to build in JDK 23 (reference).
Can you confirm your Java SDK Path is pointing to an Open JDK 17 distribution:

This can be found in the Godot editor at Editor -> Editor Settings -> (Export) Android.

@goldy1992 thanks. I've tried Java 17. I've got still the same issue on my machine.

Hm, I set Gradle=on and the project was built.

I've recorded a new video using Java 17:
2024-11-10 11-36-44.zip
Basically a behaviour looks like this with Java 17:

Gradle=off. Building fails.
Gradle=on. Building succeeds.
Gradle=off. Building succeeds.

It blows my mind )


RFC : Quick addition for thumbsticks support

Greetings,
Since I need to use my Valve Knuckles thumbsticks on a recent Godot OpenXR project of mine, I quickly hacked Knuckles thumbsticks support into this project.
There's clearly a need to build an UI for mapping OpenXR actions to Godot inputs, but that does the trick for the moment.
The thumbsticks are mapped to the Left Joystick on the Left hand and on the Right Joystick on the Right hand... I don't know if that's a good idea, since it's kind of confusing.
People might map the Right Joystick of peripheral 0 (Left hand), instead of peripheral 1 (Right hand) in the Godot editor and start wondering why it's not working correctly.
However, physically, the right hand thumbstick is on the right side of the controller, and left hand thumbstick is on the left side of the controller so, it's "visually correct".
All the mappings have been tested using the Godot Controls editor, meaning :

creation actions;
mapping them to joysticks;
calling Input.get_action_strength("action_name") and  Input.is_action_just_released("action_name");
using the Valve thumbsticks in-game, through SteamVR on Windows.

Thanks, I'm hoping to start working on a first version of a UI for mapping actions this month. As an intermediate solution hardcoding this way seems to be ok. @ChristophHaag what do you think?

Thanks, I'm hoping to start working on a first version of a UI for mapping actions this month. As an intermediate solution hardcoding this way seems to be ok. @ChristophHaag what do you think?

Going to start working on proper mappings soon but did some experimenting with this on stream tonight. There is actually a vector input type which is better suited for this.

Going to start working on proper mappings soon but did some experimenting with this on stream tonight. There is actually a vector input type which is better suited for this.

Indeed, XR_TYPE_ACTION_STATE_VECTOR2F and XrActionStateVector2f appear more relevant for sampling joysticks, instead of sampling each vector individually.
It's just that I went into "Monkey see, Monkey copy" way, using some Blender extension code as a basis.

Indeed, XR_TYPE_ACTION_STATE_VECTOR2F and XrActionStateVector2f appear more relevant for sampling joysticks, instead of sampling each vector individually.
It's just that I went into "Monkey see, Monkey copy" way, using some Blender extension code as a basis.

@Miouyouyou I spend time to finally implement the action system into the plugin so all inputs should now be supported. Let me know if you're happy with how things work now and if it covers everything. We can then close this PR.

Alright, I'll give it a shot this week-end ! Thanks for the heads up !

So, at the moment, on Windows, I tested the latest main branch and the demo worked fine.
My valve knuckles joysticks, A and B button, Trigger and Grab worked without issues !
Nice work !

Since the controls are now working fine, and this pull request code is no longer relevant, I'm closing the pull request.
I'll open a new one if I have new things to add !


fix: columnHelper not fit with Column type

Closes: https://github.com/TanStack/table/issues/4241

Fixing this a different way. Thanks!


It appears to be possible to sign up to a URL which is an invalid API endpoint

On 14 Feb 2017, 18:00, a GET request was issued to our email.openprescribing.net domain which redirects to https://openprescribing.net/api/1.0/measure_by_practice/, which gives a 500 error.
As the only place email.openprescribing.net URLs is generated is in Mailgun emails, it seems possible this is somehow in the content of a signup email.
https://rpm.newrelic.com/accounts/1550585/applications/45170403/filterable_errors#/show/77b63068-f2df-11e6-b863-f8bc124250a8_0_5350/stack_trace?top_facet=transactionUiName&primary_facet=error.class&barchart=barchart&_k=paxb7c

This only happened in two emails as far as I can see - have asked the team to search out for the likely culprit for further investigation

The magic string thing is a red herring; it's mailgun rewriting URLs in error messages.
From grepping the log files, these requests come from only two IP addresses, both of which are cloudflare.
I guess these are probes to an API endpoint to check it's up.
Stopping 500 errors for requests without parameters would therefore probably prevent some of the cloudflare-based downtime we've been seeing.


Build xinput1_3.dll failed

Durazno.cpp(215): error C2733: “XInputGetBatteryInformation
Durazno.cpp(227): error C2733: “XInputGetKeystroke
Find the reason for adding DirectX sdk to cause an error

Do not include unnecessary SDKs.

thanks

Excellent! I'll mark this closed then.


Startup freeze on macOS

"zig build run" consistently displays magenta-colored window and freezes machine completely. Reboot is necessary.
Tested on M3 Max with a fresh clone of the repo and downloaded zig binaries.
➜  aftersun git:(main) git log -1 | tee
commit e6b86155bc31f6736b712b8bb85e2dc0c9e9b908
Author: foxnne<EMAIL_ADDRESS>Date:   Mon Apr 8 11:16:25 2024 -0500

    settings: Play around with some of the camera settings.
➜  aftersun git:(main) sw_vers; zig cc -v
ProductName:		macOS
ProductVersion:		14.4.1
BuildVersion:		23E224
Homebrew clang version 17.0.6
Target: arm64-apple-darwin23.4.0
Thread model: posix
InstalledDir: /usr/bin
➜  aftersun git:(main) which mzig
mzig: aliased to /Users/jonas/src/zig/zig-macos-aarch64-0.12.0-dev.3180+83e578a18/zig
➜  aftersun git:(main) mzig version
0.12.0-dev.3180+83e578a18

This is the same Dawn bug as previous. I recently updated all my projects to latest mach nominated versions, which also means all of these projects can be built either with Dawn (zig build run) or sysgpu (zig build run -Duse_sysgpu=true).
Building with Dawn is going to cause these magenta screens and freezes on apple silicon, but sysgpu does not.
In the coming months, mach intends to begin ripping out Dawn as well as GLFW to attempt to replace these with sysgpu and a custom windowing library and from what Stephen has told me, he intends aftersun and pixi to be test beds for these, and would like me to adopt the changes as soon as possible, which I intend to, as soon as the needed features are there.
Just so you're aware, the reason these projects currently can build with either Dawn or sysgpu is that Dawn works fine on Windows/Linux, but sysgpu is needed for macOS. I felt this was the best way to leave things until more becomes resolved as I get crashes trying to run sysgpu on Windows right now.
So thanks for the report and I appreciate you always staying on top of latest! Hopefully soon these issues will be removed as Dawn gets removed and sysgpu gets stable on all platforms.

Thank you! That is really good to know. BTW, I'll be at Stephens workshop at SYCL in Milan in May. So this is one more good reason to stay on top of the latest. Keep up the good work!

Functionality is fine, but there is a reported memory leak from queue allocation. I can file a separate issue if you don't get that on Windows or Linux.

Functionality is fine, but using "zig build run -Duse_sysgpu=true" there is a memory leak from queue allocation. I can file a separate issue if you don't get that on Windows or Linux.

Feel free to, this leak is being reported on all my projects. I mentioned it to Stephen, because I can't seem to figure out what is going on here. As far as I know, the queue should be freed by mach, but it must be something I have wrong on all my projects.

BTW, I'll be at Stephens Mach workshop at SYCL 2024 in Milan next month. So this is another good reason to stay on top of the latest. Keep up the good work!

Jealous of this! I wish I could attend!


Solution cleanup

Use single solution file and project references instead of including individual files
Fix sample project: was referencing non-existent nuget version, and using removed+obsolete methods
Include assets/* files in Test project

Thanks for cleaning up :) 👍
Can you also fix the travis build before I merge? (Just remove the - xbuild /p:Configuration=Release test/Test.sln line in .travis.yml )


pdfjsLib not defined, simple question

Apologies for what might be a simple question, but I've been scouring the docs and the issues and I'm not seeing this very basic issue come up.
I include pdfjs.js as a script in my website:

But when I try to access pdfjsLib via console, or in a script, it says it's not defined:

I tried this line from the examples:
var pdfjsLib = window['pdfjs-dist/build/pdf'];
but it didn't do anything.
Am I missing something? I'm not particularly familiar with webpack.
Configuration:

Chrome, 91.0.4472.101:
Big Sur 11.1:
Rails 5.2.6, Sprockets 3.7.2 (though I'm bypassing sprockets currently)

Thank you.

I include pdfjs.js as a script in my website:

Please use official releases, see https://mozilla.github.io/pdf.js/getting_started/#download, rather than linking directly to this GitHub repository in your code (since it's not meant to be used as a CDN, and its code changes very frequently).

I tried this line from the examples:
var pdfjsLib = window['pdfjs-dist/build/pdf'];

Please see https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md (emphasis mine):

If you are developing a custom solution, first check the examples at https://github.com/mozilla/pdf.js#learning and search existing issues. If this does not help, please prepare a short well-documented example that demonstrates the problem and make it accessible online on your website, JS Bin, GitHub, etc. before opening a new issue or contacting us in the Matrix room -- keep in mind that just code snippets won't help us troubleshoot the problem.


[test] test

Affected hardware version
Bangle 2
Your firmware version
2v16.51
The bug
testtesttest
Installed apps
Apps

kbmulti (0.05)
widbthide (0.01)
widram (0.03)
calculator (0.07)
activityreminder (0.10)
pomoplus (0.05)
widanclk (0.02)
kbtouch (0.02)
run (0.14)
heartzone (0.01)
wohrm (0.09)
sevenmin (0.01)
banglexercise (0.03)
sleeplog (0.12)
swp2clk (0.04)
torch (0.11)
hrm (0.11)
lightswitch (0.06)
boot (0.55)
recorder (0.20)
spotrem (0.07)
podadrem (0.07)
sleepphasealarm (0.12)
annoy (0.01)
messages (0.58)
widmsggrid (0.04)
messageicons (0.03)
messagesmusic (0.05)
slopeclock (0.04)
tetris (0.01)
smpltmr (0.07)
weather (0.23)
circlesclock (0.23)
alarm (0.37)
android (0.20)
setting (0.56)
dragboard (0.07)
aiclock (0.07)
widminbat (0.02)
notify (0.12)
quicklaunch (0.08)
taglaunch (0.02)
altimeter (0.02)
messagelist (0.02)
dtlaunch (0.22)
sched (0.19)
swscroll (0.02)
fastload (0.03)
health (0.21)
bwclk (0.29)
calibration (0.03)

Nice! :D


Download link at top is old module?

New module appears to be available in PowerShell gallery?
https://www.powershellgallery.com/packages/O365CentralizedAddInDeployment/<IP_ADDRESS>

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

ID: 680b165b-5c8b-66c4-f9f4-0e20b8666f19
Version Independent ID: cb17922d-a250-90d8-79d9-ee4662208eec
Content: Use the Centralized Deployment PowerShell cmdlets to manage add-ins
Content Source: Enterprise/use-the-centralized-deployment-powershell-cmdlets-to-manage-add-ins.md
Service: o365-administration
GitHub Login: @twernermsft
Microsoft Alias: twerner

Yes...please update link and remove old docs...was stuck until I saw @marklitwin's feedback. Thanks marklitwin!

@officedocsbot assign @mypil

@marklitwin - From our understanding, the issue has been resolved but it may take a few days for the merged content to appear in the article. If you feel it hasn't been resolved, please re-open this issue.
Thank you for your contribution to make the docs better! Much appreciated!

@officedocsbot close


Cosign requires Go 1.19

I am trying to do 2 things, both of which end up unsuccessful (I have Golang 1.17.13 installed):

clone the cosign repo and run some of the tests locally
install the cosign binary according to documentation:

In both cases I get errors that the project requires at least Golang 1.18 or 1.19:

Suggestions:
Could you update the documentation to reflect that the project requires Golang 1.18 or 1.19?
Or, if the project could be run under Golang 1.17 could you update the instructions to specify how?

thanks for the issue @stefan-zh
Yep cosign requires go 1.19 as marked here https://github.com/sigstore/cosign/blob/main/go.mod#L3
go1.17 is archived and not supported anymore, go1.18 will soon be deprecated as well.
are you willing to update the doc to add this mention?

Thanks @cpanato
Given your clarification about Golang 1.19 being required, I will open a PR to update the docs.


inverter returns l1_voltage instead of p1_voltage

Discussed in https://github.com/addiejanssen/domoticz-solaredge-modbustcp-plugin/discussions/29
A breaking change in the solaredge_modbus causes an error in the plugin:
https://github.com/nmakel/solaredge_modbus/releases/tag/0.7.0
Registers were renamed and the plugin doesn't recognize them anymore.

Fixed by pull request #38
This is a breaking change. Any previous devices in Domoticz refering the P registers will not be updated anymore.
To fix this: remove all devices whos name start with "P" and restart Domoticz or in the hardware section stop and start the inverter.
This will result in loss of historical data for these devices.


Support --write-html flag

Checklist

[X] I'm reporting a feature request
[X] I've verified that I'm running yt-dlp version 2022.01.21. (update instructions)
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Description
I would like to save html page related to video. It may contain info which yt-dlp doesn't parse. For example, Coub items contains tags and also link to source video.
Yt-dlp downloads specified web page for video. Just write it as html, if --write-html specified.

If you just want the initial webpage, just use curl. If you want all pages that yt-dlp downloads use --write-pages

I use yt-dlp for downloading channels with option --output "%(uploader)s/%(uploader)s - %(upload_date)s - %(title)s/%(uploader)s - %(upload_date)s - %(title)s [%(id)s].%(ext)s" (seeing the script). So, I can't obtain html in corresponded place easily (moreover, any complex solution may be broken by some yt-dlp update).

These metadata are extracted from the downloaded pages and are hence not known not at the time of downloading the page. So this is impossible

There are way I see to use --write-url-link and then parse all *.url files, wgetting corresponded *.html.

If you just want the initial webpage, use curl/wget etc.

can this be handled/called by yt-dlp via a parameter ?
It would be nice if yt-dlp could be set to download the initial webpage automatically for every video and place it into the -o description: directory.

There is a workaround in write_html script. Requires  --write-url-link option (seeing example save script).


refactor load balance client so that users can add their custom implementation

Is your feature request related to a problem? Please describe.
My application needs to add a custom Client like FeignBlockingLoadBalancerClient, e.g.
public class CustomFeignBlockingLoadBalancerClient implements Client {
  ...
}

CustomFeignBlockingLoadBalancerClient  will add some extensions to FeignBlockingLoadBalancerClient, like tracing.
This works pretty well when using load-balanced clients. But when mixed with load-balanced and non-load-balanced clients, FeignClientFactoryBean hard coded to work with FeignBlockingLoadBalancerClient to get the delegate
		if (client != null) {
			if (client instanceof FeignBlockingLoadBalancerClient) {
				// not load balancing because we have a url,
				// but Spring Cloud LoadBalancer is on the classpath, so unwrap
				client = ((FeignBlockingLoadBalancerClient) client).getDelegate();
			}
			if (client instanceof RetryableFeignBlockingLoadBalancerClient) {
				// not load balancing because we have a url,
				// but Spring Cloud LoadBalancer is on the classpath, so unwrap
				client = ((RetryableFeignBlockingLoadBalancerClient) client).getDelegate();
			}
			builder.client(client);
		}

see https://github.com/spring-cloud/spring-cloud-openfeign/pull/776
Describe the solution you'd like
see https://github.com/spring-cloud/spring-cloud-openfeign/pull/776
Describe alternatives you've considered
see https://github.com/spring-cloud/spring-cloud-openfeign/pull/776
Additional context
NA
This issue is created for future enhancement to loadbalancer client customization.

Hello, @liubao68 - we actually provide tracing solutions. Have you checked that out? In any case, I think it'd be ok to allow for custom FeignLoadBalancerClient solutions. This is not going to be a team priority, but feel free to submit a PR similar to the one you've created before, but against the main branch instead. Please make sure to add tests.


1.6.0-alpha.11 on Mac M2 OSX 13.4 comictagger startup error

I get the following error if i try to start the gui.

Error message
```
Unhandled exception in app:
Traceback (most recent call last):
File "comictaggerlib/gui.py", line 136, in open_tagger_window
File "comictaggerlib/taggerwindow.py" line 90. in init
File "PyQt5/uic/__init__py", line 241, in loadUi
File "PyQt5/uic/Loader/loader.py", line 66, in loadui
File "PyQt5/uic/uiparser.py", line 1037, in parse
File "PyQt5/uic/uiparser.py", line 828, in createUserinterface
File "PyQt5/uic/uiparser.py", line 806, in traverseWidgetTree
File "PyQt5/uic/uiparser.py", line 273, in createWidget
File "PyQt5/uic/uparser.py", line 806, in traverseWidgetTree
File "PyQt5/uic/uiparser.py", line 503, in createLayout
File "PyQt5/uic/uiparser.py", line 806, in traverseWidgetTree
File "PyQt5/uic/uiparser.py", line 546, in handleItem
File "PyQt5/uic/uiparser.py", line 806, in traverseWidgetTree
File "PyQt5/uic/uiparser.py", line 273, in createWidget
File "PyQt5/uic/uiparser.py", line 806, in traverseWidgetTree
File "PyQt5/uic/uiparser.py", line 273, in createWidget
File "PyQt5/uic/uparser.py", line 806, in traverseWidgetTree
File "PyQt5/uic/uiparser.py", line 503, in createLayout
File "PyQt5/uic/uiparser.py", line 806, in traverseWidgetTree
File "pvQt5/uic/uiparser.py", line 546, in handleItem
File "PyQt5/uic/uiparser.py", line 806, in traverseWidgetTree
File "PyQt5/uic/uiparser.py", line 503, in createLavout
File "PyQt5/uic/uiparser.py", line 806, in traverseWidgetTree
File "PyQt5/uic/uiparser.py", line 546, in
handleltem
File "PyQt5/uic/uparser.py", line 806, in traverseWidgetTree
File "PyQt5/uic/uiparser.py", line 503, in createLavout
File "PyQt5/uic/uiparser.py", line 806, in traverseWidgetTree
File "PyQt5/uic/uiparser.py", line 546, in handleItem
File "PyQt5/uic/uiparser.py", line 806, in traverseWidgetTree
File "PyQt5/uic/uiparser.py", line 264, in createWidget
File "PyQt5/uic/uiparser.py", line 228, in setupObject
File "PyQt5/uic/objcreator.py", line 100, in createQObject
File "PvQt5/uic/obicreator.py", line 125, in findQObjectType
File "PyQt5/uic/Loader/gobjectcreator.py" line 113, in search
ModuleNotFoundError: No module named
'comictaggerlib.ui.customwidgets'
```

I am experiencing the same error on Windows

For now, if you wish to use alpha 11 rather than going back to alpha 10: Copy https://github.com/comictagger/comictagger/blob/develop/comictaggerlib/ui/customwidgets.py to the expected location (_internal/comictaggerlib/ui/ in the linux package for example) and it should run.

@mizaki thanks for the hint.
I copied [customwidgets.py] (https://github.com/comictagger/comictagger/blob/develop/comictaggerlib/ui/customwidgets.py) to /Applications/ComicTagger.app/Contents/Resources/comictaggerlib/ui/.
Now i get the following error.
Unhandled exception in app:
Traceback (most recent call last):
File "comictaggerlib/gui.py", line 137, in open_tagger_window
File "comictaggerlib/taggerwindow.py" line 220, in init
TypeError: unhashable type: 'list'

This is fixed by 4a33dbde465a35ef215fb095518eb0edd8d9f2de

Fixed in 1.6.0-alpha.12


ps__thumb-y disappear and won't come back

ps__thumb-y disappear after child elements reached to a certain height.

https://jsfiddle.net/dyvL31r6/6077/

this issue encountered when you need a long list like vue-virtual-scroll-list

I made a mistake


Adds test for /server resource

Initial stab at adding basic integration tests. Currently this only tests the /api/server* route by checking for a 200 ok response from thoth-api and that the response object from thoth-index is flattened.
{ response: { numFound: 0, start: 0, docs: [] }

would be
{ numFound: 0, start: 0, docs: [] }

Let me know if my assumption of the thoth-index response handling is correct.
The tests are generic enough that you could run against an actual running thoth-index and not change the port to 3002 as the readme suggest.
Convention
Integration tests would go under /tests/integration and naming the resource w/ the request type being tested.
So testing a GET request against the /api/server* resource would be /server-get.js.
Modules
Using tap for testing because it's super simple. Added request to simplify the request handling in tests, though it might be worth looking in to using request instead of http in the dispatcher modules.

+1


Annotation property with name starting with 'is' for Play/Scala model class not output properly

This annotation:
{code}
@ApiModel("VerifyCert")
case class VerifyCert(
@(ApiModelProperty @field)(position=1, required=true, value="Issuer Distinguished Name.") issuerDN: String,
{code}
is output as
{code}
"properties":{"suerDN":{"type":"string"}
{code}
Seems like a check is made for 'is' that is truncating the property name to 'suer'.

I believe this has been addressed in 1.3.13-SNAPSHOT.  Can you please retry that version?

This app is on play 2.2.2 that is why we are using 1.3.7. Is there a SNAPSHOT for play 2.2.2?

No, support for play 2.2.X has dropped since 1.3.9.

@maneeshsahu you might be able to force update it to use swagger-core 1.3.13-SNAPSHOT.  can you give that a shot?

@maneeshsahu - any update on this issue?

this has been fixed in 1.5.x, and will be picked up automatically with the scala support.


[Fix](inverted index) fix comparison for string after refactor compound #40338

cherry pick from #40338

run buildall


cnspec: 11.6.0 -> 11.6.3

Diff: https://github.com/mondoohq/cnspec/compare/refs/tags/v11.6.0...v11.6.3
Changelog: https://github.com/mondoohq/cnspec/releases/tag/v11.6.3
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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


Installation issue

Hi,
I m trying to use your library using pod.
During the compilation phase, I get 114 errors.
This is my pod file (it's an empty project)
#Uncomment the next line to define a global platform for your project
#platform :ios, '8.0'
target 'mirroir' do
# Comment the next line if you're not using Swift and don't want to use dynamic frameworks
use_frameworks!
pod 'SideMenuController'
end

The install version is 0.1.5
Sorry for my ignorance but I think it's due to my swift version (3.0).

Ok, I think I've found the solution.
I use pod 'SideMenuController',git:'https://github.com/teodorpatras/SideMenuController.git'

@Stan92 you may try to add next lines to your pod file:
post_install do |installer|
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings['ENABLE_BITCODE'] = 'NO'
config.build_settings['SWIFT_VERSION'] = '3.0'
end
end
end


New 4.3 icons missing in <IP_ADDRESS>?

Just updated to <IP_ADDRESS> and none of the new icons are loading manually or via the helpers.  The pre-4.3 icons work fine.
Installed and updated the gem and restarted the development server - I could be missing something but not sure what.

This is a common report with every new release, and I'd really like to
understand the most common reason.
Please read all the debugging steps in the contribution guidelines and let
me know which one does the trick:
https://github.com/bokmann/font-awesome-rails/blob/master/CONTRIBUTING.md
It's likely a caching issue with Sass or the asset pipeline or static
assets sitting in public/assets or another asset gem providing an old
version of the fonts.
On Friday, January 23, 2015, jasper502<EMAIL_ADDRESS>wrote:

Just updated to <IP_ADDRESS> and none of the new icons are loading manually or
via the helpers. The pre-4.3 icons work fine.
Installed and updated the gem and restarted the development server - I
could be missing something but not sure what.
—
Reply to this email directly or view it on GitHub
https://github.com/bokmann/font-awesome-rails/issues/127.

Thanks for the tip - it was a browser cache issue.  Opened in another browser to confirm.


removed .env, added .env to .gitignore, added docker setup environment variables to .env.example

Pull Request
Description
removed .env, added .env to .gitignore, added docker setup environment variables to .env.example to enhance security and privacy
Checklist:

[x] My code follows OCF's coding style guidelines
[x] I have performed a self-review of my own code
[x] I have checked my code and corrected any misspellings

Hi @aryanbhosale. Thanks for this. It would be great if you could use the values in the example that @roshnaeem originally: OPEN_METEO_MODELS=ncep_gfs013
OPEN_METEO_VARIABLES=temperature_2m,precipitation,cloud_cover
OPEN_METEO_MAX_AGE_DAYS=3
OPEN_METEO_REPEAT_INTERVAL=5
OPEN_METEO_CONCURRENT=4
Such that
OPEN_METEO_MODELS = models separated by commas
becomes
OPEN_METEO_MODELS = models separated by commas e.g: ncep_gfs013

Hi @aryanbhosale. Thanks for this. It would be great if you could use the values in the example that @roshnaeem originally: OPEN_METEO_MODELS=ncep_gfs013 OPEN_METEO_VARIABLES=temperature_2m,precipitation,cloud_cover OPEN_METEO_MAX_AGE_DAYS=3 OPEN_METEO_REPEAT_INTERVAL=5 OPEN_METEO_CONCURRENT=4
Such that OPEN_METEO_MODELS = models separated by commas
becomes OPEN_METEO_MODELS = models separated by commas e.g: ncep_gfs013

Hi @zakwatts , thank you for the review, I've updated the code in my latest commit

Also could you add some information about what the Open Meteo credentials are for? #84 as outlined in this PR? Just to avoid confusion from anyone looking at it thinking that it might be necessary to set these in order to create forecasts

Also could you add some information about what the Open Meteo credentials are for? #84 as outlined in this PR? Just to avoid confusion from anyone looking at it thinking that it might be necessary to set these in order to create forecasts

does the new commit cover it?

@all-contributors please add @aryanbhosale for code


Bump version to 1.0.1-SNAPSHOT

@sswguo A little confused for this version bump. Seems we don't have a formal 1.0 or 1.0.0 version release there, so why should we bump to 1.0.1-SNAPSHOT?

@sswguo A little confused for this version bump. Seems we don't have a formal 1.0 or 1.0.0 version release there, so why should we bump to 1.0.1-SNAPSHOT?

We had 1.0 image running on production for a while, but yeah no corresponding tag or release reflected on github, I will make a tag at least for it. So we may need to make a doc to address the process of microservice. ;-)


Error in Installation of Gulp bower-files

Sir,
When I Run (gulp bower-files) this library after the installation of bower files packages. its show me following Errors :
C:\Users\Honey\Desktop\php-plaid>gulp bower-files
Warning: gulp version mismatch:
Global gulp is 3.8.10
Local gulp is 3.6.2
Using gulpfile ~\Desktop\php-plaid\gulpfile.js
Starting 'bower-files'...
[gulp-bower-files] DEPRECATED  Please use main-bower-files (http://npmjs.org/package/main-bower-files)
'bower-files' errored after 4.87 ms
Error in plugin 'gulp-bower-files'
Bower components directory does not exist at ./bower_components

Archiving this project


How to work on the local machine

which file need edit?

You need cog and docker to run it in the local machine. And Nvidia GPU is required.

dont i need modify the config.ini file?

for example, i use blueboys-2d-v10 model, and convert the model dump into folder,
and i modify config.ini :
[generation]
model_id = ./blueboys-2d-v10

then i just run
cog predict -i prompt="1boy, blue" -i width=512  -i height=512
now im waiting for result

You need to run the scripts/download.py to get the model before use cog to run it.

ok i did it, thanks!!


scrollToItem doesn't work as expected when using StickyHeaders

Bug Report
Describe the Bug
scrollToItem doesn't work as expected when using StickyHeaders. When scrolling to an index, and align is 'start',  it should be scrolled to the top, but still be visible underneath any 'stuck' headers. Currently, it's scrolled to the absolute top, and thus, is obscured by sticky heads.
How to Reproduce
Create a a demo with sticky headers and try to scrollToItem to an index which is not a sticky header.

@ROTGP Thank you, I will investigate it soon.

@ROTGP Hey mate, I think it's the expected behavior because it's how a sticky item works. If you want an item to be scrolled on the top without be covered by the sticky item, maybe you can try this:
scrollToItem({ index: 10 - 1, align: "start" });

I don't really agree with you. And your approach will not work when scrolling to variable-sized rows/headers,  but thanks for your response.

@ROTGP For your case, you might can dynamically disable the position: sticky CSS property for the sticky item via the callback of scrollToItem


Please, re-add rss to your blog

Title

Looks like that was indeed whacked when we switched from Hugo.
What was the URL you were getting the RSS feed from? I want to make sure we get that correct when we re-add.

Let me know if #934 didn't fix this for you. I am going to assume it did.


Updated Logic Apps http trigger polling pattern details

@swylezol,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@swylezol : Thanks for your contribution to the Azure documentation! The author, @MandiOhlinger, has been notified to review your proposed change.

#sign-off


Utility classes

Is there a way to do utility classes? For instance, in Bootstrap I can do:
<button class='mt-0'>No margin on top</button>
To remove margin-top from the button, and there are others for padding, margin, etc. This makes it extremely quick to adjust spacing for components. I know I can pass classes to className, but how would I go about creating such utility classes while remaining encapsulated like styled-components prefers?

You can use the css utility. For example:
const mt0 = css`
  margin-top: 0;
`

// How to use this?
const Header = styled.div`
  ${mt0}
  // other styles
`

Hope this helps you ;)

Sure but what if only one element needs the margin or whatever? @k15a

Basically, I'd like these utility classes to not be tied to the components. For instance, this works but I'm not sure if it's correct:
import React from 'react';
import styled from 'styled-components';
import SidebarSectionHeader from './SidebarSectionHeader';

const StyledSidebarSection = styled.div`
  margin-top: 2rem;
`

const SidebarSection = props =>
  <StyledSidebarSection {...props}>
    <SidebarSectionHeader>{props.header}</SidebarSectionHeader>
    {React.Children.toArray(props.children)}
  </StyledSidebarSection>

SidebarSection.propTypes = {
  header: React.PropTypes.string
}

export default SidebarSection;

Then I can pass a className to the SidebarSection.

I don't understand exactly what you want to do with this code.
As a side note: You don't have to convert props.children to an array to render them.
{props.children} is working as well :)

In other words, what is the proper way to pass global utility classes to components using styled-components? It's much easier and more sanitary than defining per-component utility classes that other libraries reusing the components may not use (such as the margin/padding utilities I referred to above).
Also, for the toArray piece: http://stackoverflow.com/a/32705370/981177

If you have you're utility classes defined globally what's wrong with className then? If you want to inject styles globally with styled-components you can use the injectGlobal function from styled components. You can't encapsulate
Some examples which could help you:
function mt0(component) {
  return styled(component)`
    margin-top: 0;
  `
}

// Which could be used

const Header = styled.div`
  // styles
`

const HeaderWithoutMargin = mt0(Header)

const utility = css`
  ${props => props.mt0 && 'margin-top: 0;'}
  ${props => props.p0 && 'padding: 0;'}
`

// Which could be used

const Header = styled.div`
  ${utility}
  // more styles
`

<Header mt0 p0 />

Maybe someone else can help you more with this ;) Feel free to reopen this issue if you're question is still unanswered. :)

Using classNames (if they already exist) is perfectly fine @TrevorHinesley and will work exactly like you'd expect:
<StyledSidebarSection className="mt0" />

Also @TrevorHinesley, regarding children, I recommend you read this piece I wrote recently: https://mxstbr.blog/2017/02/react-children-deepdive/
There's no need to convert them to an array, React handles whatever data structure this.props.children is perfectly fine.

Thank you @mxstbr and @k15a!!

@TrevorHinesley I do something like this for working with utility classes, for lack of a better term I call them prop-receivers:
export const marginProps = props => css`
  ${props.marginBottom && `margin-bottom: ${typeof (props.marginBottom) === "string" ? props.marginBottom : "1em"};`}
  ${props.marginTop && `margin-top: ${typeof (props.marginTop) === "string" ? props.marginTop : "1em"};`}
  ${props.marginLeft && `margin-left: ${typeof (props.marginLeft) === "string" ? props.marginLeft : "1em"};`}
  ${props.marginRight && `margin-right: ${typeof (props.marginRight) === "string" ? props.marginRight : "1em"};`}
  ${props.margin && `margin: ${typeof (props.margin) === "string" ? props.margin : "1em"};`}
`;
`

Then we can use it in any component we want like so:
const SomeComponent = styled.div`
  ${marginProps}
`

So you can use this component in the following manner:
<SomeComponent margin /> // Will add a default margin to the component, in this case is 1em
<SomeComponent margin="2em" /> // Will add 2em padding
<SomeComponent marginLeft marginRight /> // Will add the default margin-left and margin-right

This pattern has proven to be very useful for us, as it leads to flexible components and also improves reusability of code as we don't need to hardcode margins or any other property directly in the component, making it more flexible for future reuse.
Hope this helps


⚠ Bofrost.de has degraded performance

In b66b834, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1732 ms

Resolved: Bofrost.de performance has improved in 974a706 after 7 minutes.


Move log files to a dedicated prefix

We currently have log files copied (from EMR or Data Pipeline) in logs folders under a prefix, such as development/logs. This doesn't allow a simple prefix filter for log ingestion. The effect is that the lambda for log processing gets called also when CSV files are created and many other instances.
Suggestion: Move log files into a toplevel _logs folder, so the example above would become _logs/development.
The effect is that we can have a prefix rule for lambdas on _logs. This also makes it easier to keep the log files while deleting a folder. So if there was an experiment poc, then removing files would previously delete poc/logs but now would leave _logs/poc

Done. https://github.com/harrystech/arthur-redshift-etl/tree/v1.8.0


gateway-api: set LastTransitionTime properly

Please provide a description of this PR:
We should not always set LastTransitionTime to now because it

unnessarily refreshes all routes' status to the api server when one service/route/gateway is updated. These status updates can trigger reconciliation again and we will end up with an infinite loop. In practice this process is usually fast enough that LastTransitionTime still keeps the same(the protobuf is accurate to a second IIRC) and breaks the loop, but it's still problematic and leads to pushing xDS at least 2x
does not conform the API semantics anyways

ref: https://github.com/kubernetes/kubernetes/blob/v1.26.3/staging/src/k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/helpers.go#L38-L39

@dddddai: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
4520cd5f96dd7ae82bd86c23ab5d7fb1228f1dd5
link
unknown
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@dddddai: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
587c4182ceeba382b077d91a06feec79093c6df0
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@dddddai: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
587c4182ceeba382b077d91a06feec79093c6df0
link
true
/test unit-tests-arm64

lint_istio
587c4182ceeba382b077d91a06feec79093c6df0
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@dddddai: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
587c4182ceeba382b077d91a06feec79093c6df0
link
true
/test unit-tests-arm64

lint_istio
587c4182ceeba382b077d91a06feec79093c6df0
link
true
/test lint

gencheck_istio
587c4182ceeba382b077d91a06feec79093c6df0
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


5 bar WiFi display crosses UI border line

There is not enough space in the "status" area of the UI to support a 15 pixel (5bars*3pixels per increment) 5 bar WiFi status icon. Possible solutions are to go to 2 pixels per increment or implement a new UI.
A new design might be needed because if you see a 1 bar display, it might not be obvious that the 1 bar is a WiFi signal strength indicator?

resolved


Add ability to set log level at startup

The ability to dynamically change the log level was added, but requires exec-ing into the container and changing it dynamically.
There should be a way to start the container with a given level as well.

This change only affects manager when running in dev mode.
Since this is purely a developer-centric change, closing as done.