Correct indexing bugs due to incorrect refactor in robustIteration()

Fixes the indexing bug discussed today with @weefuzzy.
It could probably do with a quick check over to see that this looks similar to the code here:
https://github.com/flucoma/flucoma-core/blob/2011fc0b21d4ec597d973bc64657542768269452/include/algorithms/ARModel.hpp
Which I think is the last good version.

Impossible for me to tell if the tests should fail given the change or not. The tests that fail are all to do with checking the output of transient processes, but if they are based on old results then it would make sense for them to now be different.

Yes, those are all unsurprising test failures – we'll have to quite literally play it by ear.

This feels qualitatively easier to use with the real-time slicer and extractor.

Thanks - I had no doubt it would be better as all my original audio testing was done on code that was functional. The question for me is how far the improvements go. Is it still missing obvious transients (as per your tests sent separately last month with graphical accompaniment)?

Here's the windowed forward and backward error, plotted against their source material

To my mind that's vastly improved from the previous plots and for good reason as most of the previous ARModel would have been almost entirely based on the raw data, which means that it is likely that if there's enough transient in the window, or it's a bit softer that it likely won't detect (as it did not before).
Levels of noisiness are about what I'd expect - I presume they are about the same on both (it's just that the spikes are higher for backwards), but it's a bit hard to tell due to the scaling differences on display. but it seems to be mostly just under 1, which for a normalised error (assuming the factor is around 3) would be correct/expected.
I see nothing here that points to anything other than merging this and then considering other improvements either to the variance estimate or possibly the manner of prediction (although I still have reservations about whether that route should be taken, or at least how to validate that it is really an improvement from either an empirical or theoretical standpoint) as future enhancements. As far as I can tell this represents what I intended the code to do and performs better so I would vote merge and then we can look at the block edge effects discussed and then leave you to make whatever further changes you wish after that.
It might be a good time to update the tests and pull in the updated autocorrelation code and possibly way of calculating the AR parameters here as there would then be a good basis for checking those changes. That can also be done without me, but I'd be happy to be involved in reviewing that as it removes some other non-optimal aspects of the code to date. Likewise the safety changes to ARModel.hpp

I've adjusted the slicer tests and will run them by @tremblap in supercollider form before fixing up here.
Bafflingly, however, the transients decomposition objects no longer null sum when using the reported latency. I'm going to go and sit in a dark cave to try and figure out why  this single change should / could do that (yes, I've been back to the dev branch and rebuilt / rechecked 😉 )

Hmmmm. If this were an FFT process I'd agree and consider that acceptable. However, given that the output is literally formed from subtraction then the question is what bit depth is the null sum test performed at - I'm guessing given that it's SC we are down to 32 bit? (my thinking is that even if the interpolated output was formed of generated noise, it should still null sum with the input given how the transient output is formed). On the other hand, floating point dB limits are complex to reason about (because floating and also potential catastrophic subtraction relative error). -100dB seems a bit high for me, even for a single sample, but I'd have to look at the whole of the processing chain in the test to have any decent thoughts about what acceptable performance would be. It would also be worth having a relative error test to indicate what that -100dB equates to (more like how many ULP is that?).

Wait - are you checking on this branch directly, or did you merge the changes in? I didn't pull updates (so this is 74 behind your main). Let me update.

Well, yes, being SC there's quite a lot of gubbins in the the way between language, server buffers, process, and back again.
Probably worth checking this as close to source as possible before getting too excited.
ULPs are new things for me, but with some hasty googling, the answer would be appear to be 'many ULPs':
The peak difference between the sum of the transients + residual and the source (done in sclang) is
-0.015426635742188 - -0.015437006950378 = 1.0371208e-05
Now, SC doesn't have the facilities for working out the ULP (as far as can see), but with numpy
(np.float32(-0.015426635742188) - np.float32(-0.015437006950378)) / np.spacing(np.float32(-0.015426635742188))

comes out at a chunky 11136. Did I do that right though?

Well - we don't need to get as technical as ULP probably, although over a small number of simple calculations you are looking for a few ULP at most lost accuracy, unless there is some significant reason that accuracy is lost somewhere.
If the numbers above are correct that is at the 4th significant figures or about the 10th significant bit. That seems far too much - something funky is going on, but it is hard to see how it could be in the transient separator given the way it forms it output.
I suspect this might be an investigation of the testing system, rather than the algo - but I would need to see the whole of the test process to really understand it. For now the next step is to see what the two components are for the step that has that "large" error.

So, for the afflicted area, it seems like something goes batshit. Here is the source waveform over 1000 samples around the glitch

Looks innocent enough. But here is the transient channel output. -250 seems excessive as a value.

Here is the residual

Source and residual together, on a sensible scale,

and some detritus when we do (trans + residual) - source

Well - that explains the null summing error perfectly - so this is definitely something to do with what is coming out of the transient separator and the lack of null summing accuracy is the fact that one component has gone well about 0dB and we are losing accuracy in the bit we care about (so the -250 is cancelled but not perfectly because it obliterates some of the low bits in sum).
Next thing to investigate is why this is the output and what this means for the transient separator. I'd very much hope that that section is a detected transient (not that it necessarily should be) and thus the interpolator is going a bit haywire - then we need to figure out why.

Source is Tremblay-AaS-SynthTwoVoices-M.wav
Params are default:

order
20

blockSize
256

padSize
128

threshFwd
2

threshBack
1.1

windowSize
14

clumpLength
25

OK. See (original code from 2018):
https://github.com/flucoma/flucoma-core/blob/2011fc0b21d4ec597d973bc64657542768269452/include/algorithms/ARModel.hpp#L151
And now see (code now):
https://github.com/flucoma/flucoma-core/blob/e01e237ecd687d190cb3e3ffa34a0921d8536088/include/algorithms/util/ARModel.hpp#L166
Which are not the same loop size/points.
I see why that's been done (to avoid reading from input that is prior to the pointer), but as far as I can see the first part of the vector isn't explicitly initialised (it may default to zeros - not sure) and in fact this pre-reading was intentional (it's another example of the sort of issue already discussed about the prediction methods and should probably be addressed similarly). This may be unrelated to the issues of accuracy, but it should be addressed.
I didn't make that change.

Good find. That fixes it, thanks. I can see you didn't make the change 😉

Good. I hoped it might, but I wasn't sure. Happy to discuss why I do this, but it relates to the vagueness in the Kleiner/Martin/Thomson paper about how to deal with the start of time series (they don't tell you if I recall).
It's also important in the context of the transient code (if I recall correctly) that the input that gets passed in as you move through time is the residual (in other words because the beginning of the estimates array never updates, it's important that we feed it something that has a high probility of already being "correct" - which in this case means that the transients/outliers have already been removed.
It's all coming back to me now...


Font issue

I installed Myanmar text font but i can not type it in Burmese or Karen it just appear in Eng so what is the issue? i try to reinstall it and the Keyboard still does not work. Is keyboard needed for the font as well? most of other font i installed, they all work for the language.

The Myanmar Text font uses standard Unicode encoding of Myanmar characters. If you are getting English characters when typing, that means that your keyboard is inputing the ANSI 8-bit subset of Unicode, not correct Unicode Myanmar characters.
You will need to install and activate a Unicode Myanmar keyboard driver. There are a number of options for this, including third-party keyboard layouts, but I suggest starting with the Windows language pack for Burmese. This web page has good general information on adding language support in Windows 10:
https://www.digitalcitizen.life/change-display-language-windows-10-english-another-language/
Note that you can either add a new language to be your default input and display language (which will localise the user interface), or just add a new keyboard driver, spelling dictionary, etc.

Information for managing the input and display language settings in Windows 10 is posted here.

I assume the issue was not having a Myanmar keyboard installed. Closing.


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 1998 ms

Resolved: Bofrost.de performance has improved in 39ddff9.


Elasticsearch URL command-line option should actually be a URL

Currently --logstash.elasticsearch-url accepts a domain:port, but it should accept a full URL

@sadovnikov You might want to pay attention to this. --logstash.elasticsearch-url should now be --logstash.elasticsearch-url=http://{host}:{port}


Document how to add new node to public federation

After neurobagel/planning#104 we may have more people try out our tools and maybe also try a local deployment. We should tell them how they can make the federation API aware of their new node in that case:

[ ] add to the docs how to add my new node
[ ] discuss / decide a process by which the federation API checks if nodes are still alive

We are not going to focus on this right now because we have yet to see a demand for adding public nodes from users. Once that's confirmed we will address the issue


AWS V4 Signature with AWS4-HMAC-SHA256 algorithm

Wrong Issue

wrong issue

Hi @vnarendrareddy ,
what exactly is the issue? Appear you're opening for SigV4, which is different from SigV4A signature.

Closing for inactivity. Please reopen if there is something unresolved left.


Fix file upload for API v2

API call "2/files/upload_session/finish" needs to go to content.dropboxapi.com, not api.dropboxapi.com

Thats correct thank you


UnboundLocalError in get_remote_item

Error in Maestral
UnboundLocalError in venv/maestral/lib/python3.8/site-packages/maestral/sync.py:2044
local variable 'res' referenced before assignment
View on Bugsnag
Stacktrace
venv/maestral/lib/python3.8/site-packages/maestral/sync.py:2044 - get_remote_item
venv/maestral/lib/python3.8/site-packages/maestral/sync.py:2793 - startup_worker

View full stacktrace
Created by Sam Schott via Bugsnag

When get_remote_item is called with an invalid Dropbox path, an UnboundLocalError is raised when trying to process the download result.

Fixed in v1.1.0.


Pin markupsafe at version 2.0.1

Temporary fix due to breaking changes in the dependency.
The 2.2 branch of aiohttp-apispec requires Jinja2 < 3, while its 3.0 (beta) branch supports newer Jinja2 versions which would likely also bypass this issue. We can either test out the current beta or wait for a new release there.

Shouldn't I be able to replicate the AATH issue with ./run_docker --version in the scripts folder of the current main?  I couldn't.  Happy to accept this, but just wondering about that.

Confirmed that this fixed the AATH. Issue -- all good.


Create option should be selectable without use of mouse

The major blocker that I have with this library is that I cannot select the "create" (item) selection without using my mouse. Nor is it selectable in the tab sequence.
It would be 100% amazing if there was an easy way to select the create option. Arrow keys would be great, but the "create" option should probably be near the top of the list in that case. As an alternative, pressing a certain key to create a new option would be nice, like tab perhaps. I considered comma, but it is unfortunate in cases where a comma is needed in the text of the selection. Maybe an even further future consideration, but this sort of configuration could be exposed via the api.

@MegaKeegMan good catch, will see if I can fix this sometimes, also PR is welcome as well :)

Actually @harshzalavadiya  do you have an idea of how you expect to implement #529 ? My intuition for an MVP is to implement the arrow key functionality for the "create" option. Any thoughts or preferences before I get started?

@harshzalavadiya I am having some complications unfortunately. So I cloned this repo, and set up a fresh react project. Then I did:

npm link from the library repo
npm link react-multi-select-component from the project repo
npm run dev from the library repo
and started up the app
Unfortunately when I do all of this, my React app stops working and I get these errors:

Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app

Uncaught TypeError: dispatcher is null
    useState React
    MultiSelectProvider index.js:75
    ...

The above error occurred in the <MultiSelectProvider> component:

MultiSelectProvider@http://localhost:3000/static/js/bundle.js:474:7
MultiSelect@http://localhost:3000/static/js/bundle.js:1097:22
div
Component@http://localhost:3000/static/js/bundle.js:150:82
div
App@http://localhost:3000/static/js/bundle.js:45:82

Do you have any tips on what I am doing wrong. This does not happen when I install the library regularly. I am doing this on a fresh npx create-react-app my-app --template typescript

@MegaKeegMan I'll recommend using vite instead of Create React App since it's not very actively updated,
also there's no need to seprately setup other repo to test this, you can use existing storybook dev environment to do the same thing easily

Excellent, okay I am set up to develop now. Thank you. I did run into an error that seemed to be related to using node v17, but found a quick solution here: https://stackoverflow.com/questions/69692842/error-message-error0308010cdigital-envelope-routinesunsupported.
Specifically, I followed option 2 in the most popular answer there.

@harshzalavadiya thanks very much for the responsiveness. Unfortunately, thought the code I submitted does seem to work on the storybook components, it does not quite work as I want while integrating the component into my app. I will poke around a bit to see if I can identify the differences. But mainly, I seem to be able to tab my way to the create option, which is good, but I cannot get to it using the arrow keys like I can in the storybook creatable.

I took a look at the rendered markup of the storybook vs my app.
Here is the creatable list item on my app:

Here is the creatable list item on the storybook:

Create "dfsafafa"

On my app, I have select all disabled, and that may be the reason. But the search also has a tab index of 0. I expect this is the cause of the failure... As I typed this I went to check, and indeed it does work on my app when select all is disabled. I wonder if tabIndex should just be equal to skipIndex. I will try to pull this storybook back up on local dev today.

@harshzalavadiya this is all set. One thing that is a bit funny, but is not anything new, is that you can continue setting the focus index for as many options are available. So if you press "down" twice from your search, despite there only being one visible item in the list (the create item), you will have to press "up" twice to get back to having the search in focus. Maybe that can be a new issue, but the new MR above at least resolves this one.

Released v4.3.2


On ECONNRESET, assert() calls undefined res.status which throws an error

When for some reason the remote server fails and the connection is reset, supertest cannot handle the error properly which is why the following error is thrown:
|"TypeError: Cannot read property 'status' of undefined",
|"    at Test.assert (/webapp/node_modules/supertest/lib/test.js:203:12)",
|"    at assert (/webapp/node_modules/supertest/lib/test.js:132:12)",
|"    at /webapp/node_modules/supertest/lib/test.js:129:5",
|"    at Test.Request.callback (/webapp/node_modules/superagent/lib/node/index.js:781:12)",
|"    at ClientRequest.<anonymous> (/webapp/node_modules/superagent/lib/node/index.js:736:10)",
|"    at ClientRequest.emit (events.js:95:17)",
|"    at Socket.socketOnEnd [as onend] (http.js:1569:9)",
|"    at Socket.g (events.js:180:16)",
|"    at Socket.emit (events.js:117:20)",
|"    at _stream_readable.js:944:16",
|"    at process._tickCallback (node.js:448:13)"

There is this code on line 202 in supertest/lib/test.js:
if (status) {
  if (res.status !== status) {
    var a = http.STATUS_CODES[status];
    var b = http.STATUS_CODES[res.status];
    return fn(new Error('expected ' + status + ' "' + a + '", got ' + res.status + ' "' + b + '"'), res);
  }

  // remove expected superagent error
  if (resError && resError instanceof Error && resError.status === status) {
    resError = null;
  }
}

On the line 203, which says if (res.status !== status) {, res is undefined. Because resError = { [Error: socket hang up] code: 'ECONNRESET', response: undefined }.

Same here. During a stress test mongoose connection limit is reached and node is sending an empty result. So i get same exception.
My temporary Solution:
Test.prototype.assert = function(resError, res, fn){
if(!res) {
res = {
status: 'FOOO'
};
}

This is a duplicate of #237. There is PR #258 to address this.

#260 doesn't fix this issue. Need to reopen.

I'm having this issue as well on Windows 7. I've described my experiences with this issue here https://github.com/visionmedia/supertest/issues/230

@kadishmal , @mleanos  - any resolution to this?
https://github.com/visionmedia/supertest/issues/298
if you could help me with 298 . thanks !

No, this particular issue is still present. res.status is not handled properly because res is undefined.

@kadishmal  - thanks for the update. Do you know ETA for this fix; or know if supertest is working towards a fix?

@mikelax  - Do you know ETA for this fix; or know if supertest is working towards a fix?

It's quite an old thread and it is closed, but I still encounter this issue. It is reproduced on Windows only and when I send a PUT with binary content with content-type set to a different value.
After googling this is still the most relevant place, so maybe someone knows how to address this problem?


Posters for event list

[ ] Update the event list with posters

Branches assigned

Branch
Assigned

management
@suneel87

technical 1
Content from cell 2

technical2
Content from cell 2

cultural1
@Subaharish

cultural2
@PriyaaIyer


Sidebar mobile view and add container storage informations.

The sidebar doesn't fit well using my smartphone, Why didn't you pick the sidebar example from twitter bootstrap website ?
Is there a chance that in later release you display the storage (used/available) of each container ?
Is there a chance that in a later release you display also the hostname ?

Hi @kopax,
We don't currently target mobile browsers as a priority. Maybe you could tell us a bit about how you use Marathon from your mobile phone? I'd be fascinated to hear more. We also welcome PRs against the UI if you'd like to have a stab yourself.
On the matter of storage, it's not something Marathon monitors at present, I'd suggest raising an issue with the enhancement flag to stimulate some discussion on the matter. It should be possible to script a health check for disk usage using cadvisor or similar though.

I have no usage on mobile view but It was just a remark, I understand it is not a priority.
I have added a third question about the hostname.

host is shown in the UI in the task detail view since v0.13.0.

I meant on the list view.
It is in the UI since way before 0.13.0

A specific feature request is a good way to get a discussion going on this, as other members of the community will wish to offer their opinions on new functionality.
Of course, a PR which implements this functionality is even better!

Could you create it for me ?
I can't see how to create a special feature request :/

Here you can see how it looks portrait and in landscape mode on iphone.
It would work if the name would be printed instead of icon beside the name.
How do I use marathon with my phone ?
Sometimes I do scale and app over the phone, but since version 0.13 I have to use search to find the right one.

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-2896. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-2896. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.


added yaml files for running vllm on tpu

Description

This PR adds yaml files needed for vLLM on TPU GKE user guide
Tasks

[X] The contributing guide has been read and followed.
[X] The samples added / modified have been fully tested.
[X] Workflow files have been added / modified, if applicable.
[X] Region tags have been properly added, if new samples.
[X] All dependencies are set to up-to-date versions, as applicable.
[X] Merge this pull-request for me once it is approved.

@NimJay does using upper case mean it functions as a variable in the userguide like it does in the yaml files in this one https://cloud.google.com/kubernetes-engine/docs/how-to/persistent-volumes/hyperdisk-ml#create-from-hd?

@Edwinhr716, good question.
Unfortunately, I believe those variables (like the ones in the image below) are only possible with in-line samples (not samples embedded by referencing files on GitHub):

I recommend just adding a comment in the sample itself similar to # Replace with your value.


Exception while setting custom ja3 parameter on requests.get() for certain cipher suite integer values

Please check the following items before reporting a bug, otherwise it may be closed immediately.

[x] This is NOT a site-related "bugs", e.g. some site blocks me when using curl_cffi,
UNLESS it has been verified that the reason is missing pieces in the impersonation.
[x] A code snippet that can reproduce this bug is provided, even if it's a one-liner.
[x] Version information will be pasted as below.

Describe the bug
Cipher Exception:
Exception while setting custom ja3 parameter on requests.get() for certain cipher suite integer values
The exception observed is:
[2024-11-26 11:25:42,203] ERROR in curl_cffi_script: 49324
[2024-11-26 11:25:42,209] ERROR in curl_cffi_script:   File "/Users/Documents/scripts/curl_cffi_script.py", line 258, in crawl_url
    response = await s.get(
  File "/Users/python_virtual_env/python3/lib/python3.9/site-packages/curl_cffi/requests/session.py", line 1253, in request
    req, buffer, header_buffer, q, header_recved, quit_now = self._set_curl_options(
  File "/Users/python_virtual_env/python3/lib/python3.9/site-packages/curl_cffi/requests/session.py", line 654, in _set_curl_options
    self._set_ja3_options(c, ja3, permute=permute)
  File "/Users/python_virtual_env/python3/lib/python3.9/site-packages/curl_cffi/requests/session.py", line 304, in _set_ja3_options
    cipher_name = TLS_CIPHER_NAME_MAP[cipher_id]

Cipher 49324 translates to a Hex value: 0xC0,0xAC which is the cipher TLS_ECDHE_ECDSA_WITH_AES_128_CCM as per https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-parameters-4
Similar issue observed with Cipher values: 65, 64, 49202, 49167, 49194, 106 and a few more.
To Reproduce
async with AsyncSession() as s:
    # This is the ja3n text for Safari v18 on a Mac obtained from: https://tls.browserleaks.com/json
    ja3n_str = "771,49199-49171-49191-49200-49172-49192-156-47-60-157-53-61-65-132-49195-49324-49326-49161-49187-49196-49325-49327-49162-49188-158-51-103-159-57-107-69-136-4865-4866-255,0-10-11-13-23-43-51,23-29-24-256-257-258,0"
    # Another ja3n string that fails
    # ja3n_str = "771,4866-4865-4867-49196-49195-52393-49200-52392-49199-159-52394-163-158-162-49188-49192-49187-49191-107-106-103-64-49198-49202-49197-49201-49190-49194-49189-49193-49162-49172-49161-49171-57-56-51-50-49157-49167-49156-49166-157-156-61-60-53-47-255,0-5-10-11-13-17-23-43-45-50-51,29-23-24-25-30-256-257-258-259-260,0"
    response = await s.get(
        url,
        timeout=30,
        ja3=ja3n_str
    )

Expected behavior
The valid custom ja3n fingerprint string must be used upon requests.get().
Versions

OS: Mac Sonoma
curl_cffi version 0.7.3

Additional context

Which session are you using? async or sync? Async

These values are not available in boringssl, thus there is no way to use them unless we patch boringssl, which requires a significant amount of investigation. Please expect an extend time to fix.

These values are not available in boringssl, thus there is no way to use them unless we patch boringssl, which requires a significant amount of investigation. Please expect an extend time to fix.

Thank you. I shall keep this ticket open as a reference.


TPLink Archer C5400 router doesn't work well with Matter over IPv6

Problem
When commissioning an Rpi with IPv6 enabled, it doesn't complete commissioning successfully. Specifically, the REPL acting as a commissioner is unable to connect operationally over CASE to the Rpi:
2022-02-07 13:25:10 johnsj-macbookpro1.roam.corp.google.com chip.DL[59137] DEBUG Mdns: OnGetAddrInfo hostname:EEAABADABAD0DDCA.local.
2022-02-07 13:25:10 johnsj-macbookpro1.roam.corp.google.com chip.DIS[59137] INFO Node ID resolved for 0x0000000000000002
2022-02-07 13:25:10 johnsj-macbookpro1.roam.corp.google.com chip.DIS[59137] INFO     Addr 0: [::e65f:1ff:fe82:f926]:5540
2022-02-07 13:25:10 johnsj-macbookpro1.roam.corp.google.com chip.CTL[59137] INFO F0000000000000001: OperationalDiscoveryComplete for device ID N0000000000000002
…
…
2022-02-07 13:25:10 johnsj-macbookpro1.roam.corp.google.com chip.IN[59137] INFO Prepared unauthenticated message 0x7f86138df868 to 0x0000000000000000 (0)  of type 0x30 and protocolId (0, 0) on exchange 61170i with MessageCounter:1597295096.
2022-02-07 13:25:10 johnsj-macbookpro1.roam.corp.google.com chip.IN[59137] INFO Sending unauthenticated msg 0x7f86138df868 with MessageCounter:1597295096 to 0x0000000000000000 at monotonic time: 959560209 msec
2022-02-07 13:25:10 johnsj-macbookpro1.roam.corp.google.com chip.CTL[59137] INFO Device connection failed. Error ../../src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000041: No route to host

The key failure is the inability to get a route to the Rpi.
Cause
The Router attempts to do prefix delegation, but has insufficient bits granted by my ISP to assign a prefix. So it grants the device a completely bogus global IPv6 address: ::e65f:1ff:fe82:f926
This is picked up commissioner during mDNS discovery and it attempts to send a message to that address, but clearly fails.
Proposed Solution
While we were able to prevent the router from doing this by switching the mode on the router from "SLAAC + Stateless DHCP" to "DHCPv6", we can add a heuristic to de-prioritize such an address in the IsIpLess function.

FYI @andreilitvin @tcarmelveilleux

Many thanks to @tcarmelveilleux for helping me debug this.

So, we only seem to resolve to 1 IP address in the logs above.
However, calling dns-sd on my Mac seems to show multiple addresses that are returned:
(python_env) ➜  connectedhomeip git:(ipv6/zero-prefix-addrs) ✗ dns-sd -Gv4v6  EEAABADABAD0DDCA.local.
DATE: ---Tue 08 Feb 2022---
12:08:12.938  ...STARTING...
Timestamp     A/R    Flags if Hostname                               Address                                      TTL
12:08:12.940  Add 40000003  6 EEAABADABAD0DDCA.local.                0000:0000:0000:0000:0000:0000:0000:1000%<0>  120
12:08:12.940  Add 40000003  6 EEAABADABAD0DDCA.local.                FE80:0000:0000:0000:E65F:01FF:FE82:F926%en0  120
12:08:12.940  Add 40000002  6 EEAABADABAD0DDCA.local.                <IP_ADDRESS>                                120

@mrjerryjohns  - Andrei put up a PR a few days ago to preferentially select addresses. Can you re-test and see if this PR has fixed this issue?
https://github.com/project-chip/connectedhomeip/pull/15200/files

Will try it out. However, it doesn't look like multiple entries were even returned to begin with in the logs above?

I will update the code to use the new resolver, however for now the final code is not in. However could you verify if it 'would work'?
Use:
./scripts/build/build_examples.py --target linux-x64-address-resolve-tool build

./out/linux-x64-address-resolve-tool/address-resolve-tool node 0x000000000001E1B9 0x116362B9D227A22A

and subsitute your fabricid and nodeid in there, see if the result is good. Specifically you should have a line like:
CHIP:DIS: Resolve completed: UDP:[2607:fea8:1fdf:1001:ea68:e7ff:fe31:1684%enp58s0]:5540
CHIP:DIS:    Supports TCP:                  YES
CHIP:DIS:    MRP IDLE retransmit timeout:   5000 ms
CHIP:DIS:    MRP ACTIVE retransmit timeout: 300 ms
CHIP:DIS: Discovery does not require any more timeouts

which will tell you the final result

I also have a pending PR in #15580 to only attach an interface to link local addresses that is not yet in master, so interface may not be final .But address selection should be (it should not pick the bogus 0/64 prefix I hope)

@mrjerryjohns is this still an issue with the latest SDK? We have heavily updated address resolve code now.


[Question] Certificate authentication and cert issuing via Certificate API. Have these features been removed?

I would like to authenticate users via client certificate, but I've got stuck.
I've tried to find information about setting up user authentication, but only found in the apiserver commandline arguments and the kubeconfig that it uses HTTP basic auth by default.
Is the content of the htpasswd file managed by k3s? If so, how can we add new entries?
I've also tried to issue a new client certificate via the Certifcates API as k3s kubectl api-versions show it's supported. (This is how I tried: https://kubernetes.io/docs/tasks/tls/managing-tls-in-a-cluster and it works on other clusters)
But after approving the CSR with k3s kubectl certificate approve ... the CSR only goes to "Approved" state and not "Approved,Issued", and there is no .status.certificate field.
Without these I've tried to sign my CSR directly using the CA cert, and I wasn't able to authenticate (I'm not sure I've used correct cert files).
Are these the expected behaviors and it's better to forget cert auth to integrate with, or should I report it as bug?
I'm using k3s v0.2.0 (amd64)

I've found the server authentication code meanwhile, and as I see it uses the upstream k8s authenticator so I guess certificate authentication should work. Maybe I've created a wrong client certificate without the Certificate API.

Does this work? I am using the stable/cockroachdb helm chart on k8s installed via kubeadm, and this system with k3s - only the kubeadm based system issues the approved CSRs.

How's it going?

@zsolt-keseru-epam

@huapox I didn't have the chance to investigate this deeper as we decided to move with other solution for a start.
Although now I have checked that certificate issuing is still not working in 0.5.0

I've tested the version 0.7.0-rc2 , it seems works after #359

Tested Okay, via #684

Closing due to age.


feat: Add to_pubsub streaming method

Also add script that simply creates a pubsub topic named "penguins"

Add to sphinx documentation (toc.yaml and something.rst) Thanks

This will be added in a follow-up.


Symbols aren't callable in maths mode

Description
$hat(a)$ #sym.hat("a") #(sym.hat)("a")

error: expected function, found symbol
    ┌─ mmn15.typ:148:10
    │
148 │ $hat(a)$ #sym.hat("a") #(sym.hat)("a")
    │           ^^^^^^^

Reproduction URL
No response
Operating system
No response
Typst version

[X] I am using the latest version of Typst

Symbols themselves are different from the callable symbol functions. We define for a certain set of symbols (accents) a function with their name, which is made available in the math scope. They aren't related at all to the sym module.
The behaviour you show is to be expected, as it should be accessed as #math.hat("a") instead, I think.

I see, I suppose we would want to fix the name overloading problems then. I really don't get why sym items are even available under math in code mode to be honest

Maybe I should clarify that they aren't quite "in scope" in the usual sense. The sym items are made available by simply defining them in math as well (https://github.com/typst/typst/tree/main/crates/typst/src/math/mod.rs#L208-210). So they are still accessible under math in code mode as they are defined there.
We could probably change it so that the sym items aren't redefined in math, and instead perform a lookup inside the sym module when evaluating identifiers in math mode.

That makes more sense to me

Could you please try to compile your code with the main branch code? AFAIK, symbol hat is now callable since #4299
https://github.com/typst/typst/blob/92ec56601831b9c454dbeaf28dba84e2769c7726/crates/typst/src/symbols/sym.rs#L158

Could you please try to compile your code with the main branch code? AFAIK, symbol hat is now callable since #4299

I hadn't realised this change had been implemented on main, sorry I gave a very wrong description of the current behaviour!
I also thought there might still be overlapping definition problems when using #math.hat (or something similar) with those changes, but I just checked and it isn't a problem.


Allow synonyms to improve location filtering on /galleries

Fixes an issue that currently affects several of our geocoded cities, e.g…

The geocoded name "Saint Ives" doesn't match the user input "st ives"
The geocoded name "St. Louis" doesn't match the user input "saint louis"

Let's allow synonym-matching so that both of the above  typeahead queries will succeed:

          1 Warning

:warning:
Please assign someone to your PR

  Generated by :no_entry_sign: danger

Looks 👍 !


[DNM pending #493] xfail flaky prep tests

Fixes #480, pending #493

Codecov Report

Merging #495 (35c6591) into main (e83baa9) will increase coverage by 0.01%.
The diff coverage is 100.00%.

Additional details and impacted files

Closing in favour of #493


What is the correct way to create a droplet and then get its public v4 and v6 ips?

thanks!

Please see the examples on the readme. They detail both these tasks.


Fix integration tests

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: ryandawsonuk:white_check_mark: mteodori:x: alfresco-buildYou have signed the CLA already but the status is still pending? Let us recheck it.


feat: convert to @dhis2/cli format

BREAKING CHANGE: removes the binaries for code-style.js and
commit-style.js and instead exposes a binary named d2-style which is
the subcommand which the d2 cli will use.

Looks good to me, except I think we should take this oportunity to make the final command an operative verb like "apply" or "check", depending on the context.  That way we can also have destructive and non-destructive versions of the same style, i.e. d2 style js check just prints warnings, d2 style js apply actually edits files so they conform to the style rules.
Not sure about those particular verbs, but I think they make sense.

Cool, good input. I'll do that.

For JS:
d2 style js check
// checks if staged files needs fixing

d2 style js check --all
// checks if all files needs fixing

d2 style js apply
// applies to staged

d2 style js apply -all
// applies to all files

For Git commit:
d2 style commit apply
// reads from ./.git/COMMIT_EDITMSG

d2 style commit apply "broken msg"
// ignores [msg] when applying

d2 style commit check "foobar: check this msg"
// checks if [msg] is valid

d2 style commit check
// logs error when no [msg] is passed to check

[x] Refactored the structure to use command directories
[x] check/apply are now commands, not arguments, which avoids bugs with yargs positional arguments

The command hierarchy is now more as described in the yargs docs:
src/cmds
├── commit_cmds
│   ├── apply.js
│   └── check.js
├── git-commit.js
├── javascript.js
└── js_cmds
    ├── apply.js
    └── check.js

src/cmds.js sets up all the commands in src/cmds => javascript.js and git-commit.js
each of those commands sets up all the commands in their respective *_cmds/ directory => check.js and apply.js.

Resolved the comments.

Looks great @varl!
One final comment - I know it's a bit uglier, but would it be alright to update the path.join(__dirname, ...) calls to each have only two arguments?  So i.e. path.join(__dirname, '../config/prettier.config.js') instead of path.join(__dirname, '..', 'config', 'prettier.config.js')?  The former support automatic asset detection with pkg, the latter doesn't unfortunately.

Sure, no problem. Wasn't clear that it only worked with path.join(__dirname, '../config/prettier.config.js').


Summon Night 6: Lost borders [PCSH00225]

App summary

App name: Summon Night 6: Lost borders
App serial: PCSH00225
App version: 1.00

Vita3K summary

Version: v0.1.6
Build number: 3123
Commit hash: https://github.com/vita3k/vita3k/commit/be55aa3a
CPU backend: Dynarmic
GPU backend: Vulkan

Test environment summary

Tested by: Dystnine
OS: Windows 10
CPU: INTEL I3 4100U
GPU: AMD HD 8500M
RAM: 8 GB

Issues
Game is ingame+ and crash after video.
Screenshots

Log
vita3k.log
Recommended labels

Menu

is not ingame if crash after intro video before get ingame ?

is not ingame if crash after intro video before get ingame ?
Well, it crashes after the intro video, but it doesn't go to the title page, so I think it's ingame+

is not ingame if crash after intro video before get ingame ?

Well, it crashes after the intro video, but it doesn't go to the title page, so I think it's ingame+

what ? if crash  before ingame how you want is ingame +, is no sense, Ingame want said you can PLAY
here is menu  that all

is not ingame if crash after intro video before get ingame ?

Well, it crashes after the intro video, but it doesn't go to the title page, so I think it's ingame+

what ? if crash before get ingame how you want is ingame +, is no sense, Ingame want said you can PLAY here is menu that all

OK, I changed the label to Menu.

as of https://github.com/Vita3K/Vita3K/commit/8d345f002187fb9e619fc386bd7a73ea64a393dc, the game got ingame in Vulkan. Before getting this scene (see in 4th screenshot) it crashed with a out of memory error. However, in OpenGL, the game is normal and get past the scene. Audio is low quality.
Screenshots

Logs
vita3k (OpenGL).log
vita3k (Vulkan).log
Recommended Labels

Playable
audio quality
vulkan issue


Error starting CamelContext (camel-1) due to exception thrown: Failed to start route idscpServer because of null

I have just installed a real certificate I got from Gerd and made all the necessary configuration on the dataspace connector.
The 6.0.0 connector launches and at the very end presents the error:
Error starting CamelContext (camel-1) due to exception thrown: Failed to start route idscpServer because of null
..... (see the attachment)
Any help would be very much appreciated.
error.log

Hi,
the error seems to be related to IDSCP2 not being able to read the certificate correctly.
do you want the connector to communicate via IDSCP2? If not, the property idscp2.enabled should be set to false. Then, the IDSCP2 server does not try to start. If you do want to use IDSCP2 for communication, the path to the IDS certificate also has to be set in the property idscp2.keystore, as IDSCP2 requires a valid IDS certificate to start.

thank you, I disabled the IDSCP2, I don't need  to use the IDSCP2.


Adding template style memdb file for Stanford private DC instance

Note: the corresponding "template" style csv, tmcf and manifest.json file is here: https://console.cloud.google.com/storage/browser/datcom-stanford-resources/stanford?project=datcom-stanford&pageState=("StorageObjectListTable":("f":"%255B%255D"))&prefix=&forceOnObjectsSortingFiltering=false

Can remove "manifest.json" in gcs now. Also can you update the instruction here as well: https://github.com/datacommonsorg/website/blob/master/docs/new_deployment.md#private-instance-adding-data.
I am thinking maybe to check in the tmcf and csv file in the repo and the instruction can refer to them?


git-checkout-pr: removed fork results in git remote add This repository has been deleted

Please ensure:

[X] The bug is caused by Refined GitHub. It doesn't happen if I disable the extension.
[X] The bug happens after clearing extension cache. The "Clear cache" button can be found at the bottom of the options page.

Example URLs
https://github.com/void-linux/void-packages/pull/35150
Extension version
22.1.18
Browser(s) used
Firefox
Description
GitHub doesn't close a PR when the fork was removed, then it's not possible to checkout the PR with git, but Checkout with git
Code -> Checkout with Git shows:
Run in your project repository, pick either one

HTTPS

git remote add This repository has been deleted https://github.com/This repository has been deleted.git
git fetch This repository has been deleted
git switch --track This repository has been deleted/

SSH

git remote add This repository has been deleted git@github.com:This repository has been deleted.git
git fetch This repository has been deleted
git switch --track This repository has been deleted/

Include in this issue:

[ ] Screenshots/video/gif demonstrating the bug, if it’s visual
[ ] Console errors, if any

We have two options:

avoid adding the content when the fork was deleted
change the commands to fetch the commit from the current repo (I think that's how it works)

I don't see git-checkout-pr on the example PR at all. Is this related to the Codespaces tab?

Because the PR was closed. He made the issue before he closed it.

Well, it's back to #4701

Closing in favor of #4701.


Create a Sign in page

create an initial start page with app logo and a sign in button
navigate to the home page when logged in
add new users to the database

https://github.com/392-f24/CommonCart/pull/2

https://github.com/392-f24/CommonCart/pull/3


chore: bump ape core 0.4.0

ape 0.4.0
Needs tests

Merging with failing tests to setup secret env vars for future test runs


Add tests

Currently this repository has literally no unit or integration tests.
That should be fixed.

I will do that! For now I will integrate with travis-ci and codecov.


[Archive.org] Index out of range

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting that yt-dlp is broken on a supported site
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[ ] I've read about sharing account credentials and I'm willing to share it if required

Region
U.S.A.
Provide a description that is worded well enough to be understood
After Archive.org is down for more than a week, when you attempt to download a video, it throws a "list index out of range" error and therefore cannot be downloaded.
EDIT: It was caused by JSPlayer failing to load.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-o', 'd:\\Google Drive & YouTube Video Downloads and more\\%(title)s.%(ext)s', 'https://archive.org/details/dvd-transfer-27', '-v']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-master-builds [5bc5fb283] (win_exe)
[debug] Python 3.10.11 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 1.1.1t  7 Feb 2023)
[debug] exe versions: ffmpeg 6.1-full_build-www.gyan.dev (setts), ffprobe 6.1-full_build-www.gyan.dev, phantomjs 2.1.1
[debug] Optional libraries: Cryptodome-3.21.0, brotli-1.1.0, certifi-2024.08.30, curl_cffi-0.5.10, mutagen-1.47.0, requests-2.32.3, sqlite3-3.40.1, urllib3-2.2.3, websockets-13.1
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets, curl_cffi
[debug] Loaded 1837 extractors
[archive.org] Extracting URL: https://archive.org/details/dvd-transfer-27
[archive.org] dvd-transfer-27: Downloading webpage
ERROR: list index out of range
Traceback (most recent call last):
  File "yt_dlp\YoutubeDL.py", line 1625, in wrapper
  File "yt_dlp\YoutubeDL.py", line 1760, in __extract_info
  File "yt_dlp\extractor\common.py", line 742, in extract
  File "yt_dlp\extractor\archiveorg.py", line 229, in _real_extract
  File "yt_dlp\extractor\archiveorg.py", line 212, in _playlist_data
IndexError: list index out of range

EDIT: It was caused by JSPlayer failing to load.

The media doesn't load in browser either?

EDIT: It was caused by JSPlayer failing to load.

The media doesn't load in browser either?

Yes. It does not load for me.

If it won't load in browser, then it's expected that yt-dlp can't load it either. Ideally our error handling would be better here, but I don't see a reliably way to distinguish between a site-side problem and an extractor bug


Repeating line in render_callback.py example

Hi,
In lines 105 and 106 'render_callback.py' in folder 'special callbacks' , the line set_render_callback(render) is repeated. Deleting one of these two lines seems to work as well.

its removed now, thanks for catching that!


Change JavaScriptConverter to JsonConvert.DeserializeObject

Subject: Request for Enhancements in CokyGrabber: .NET Core Support and Librewolf Integration
Hello,
I am reaching out regarding the functionality of CockyGrabber for extracting bookmarks from Librewolf (Gecko). I have encountered an issue with the current project's lack of support for .NET Core, as I intend to utilize it with .NET 6 or a higher version. Upon using your NuGet package, an error was triggered due to the absence of the file containing "System.Web.Script.Serialization;". To overcome this obstacle, I resorted to manually copying your source code and change it for my usage.
I am kindly requesting the following enhancements to enhance compatibility and functionality:

Replace the JavascriptConverter with JsonConvert.DeserializeObject to facilitate support for dynamic JSON objects in .NET Core:

using Newtonsoft.Json;
dynamic json = JsonConvert.DeserializeObject(File.ReadAllText(profile + BookmarkPath));

Incorporate Librewolf support in the UniversalGrabber feature of CockyGrabber:

public class LibrefoxGrabber : GeckoGrabber
{
    public override string ProfileDirPath => Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData) + "\\librewolf\\Profiles";
}

I believe there may be an error in the documentation regarding the implementation of your own GeckoGrabber, where the base class should not be the BlinkGrabber:
Link to documentation correction

Thank you for considering these requests.

Can I refactor the code myself instead? This way, you won't have to do it. I prefer not to fork your project but to create a new branch where I can make the changes. Ultimately, I need a NugetPackage for grabbing, as I automate my project builds with GitHub actions. It seems that you don't publish your packages with GitHub actions. I would like to update your NugetPackage, giving credit to you for the project. Could you please add a GitHub secret named "NUGET_API_KEY" that contains an API key to push new CockyGrabber packages to Nuget?
I plan to update the project to .NET 6 for long-term support and compatibility. I believe that many features in .NET 8 (C# 12) are unnecessary. I'm unsure about which tasks from your ToDo list I can tackle, but I'm willing to try if you're open to me refactoring the code. GitHub is great for version control, so I believe it should work smoothly.


No zero grad for min gpt

I noticed that the min gpt example is does not have any call to zero_grad(). This leads to the gradients accumulating with each iteration instead of being computed fresh each time.

Just made a pull request.

Sounds a bit strange, is it something that you actually noticed experimentally? The intent of the backward_step... methods is to perform the full step (gradient zeroing, backward pass, weights update) e.g. in the case of the min gpt example this should happen here.

Oh, does tch's backward functions do the zeroing automatically? PyTorch itself accumulates the gradients with each pass and requires manual zeroing.


Migrate primary branch from master to main

See https://github.com/Senzing/stream-loader/issues/283

Pull requests:

https://github.com/Senzing/images/pull/11


mesheryctl: adding new command restart

this commit creates new command restart
which will first stop meshery and then
start meshery again.

mesheryctl system restart *

Signed-off-by: subhamkrai<EMAIL_ADDRESS>Description
This PR fixes #878
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

I would like to know if we can do it any other easier way because we are just writing whole stop and start meshery logic inside this.

There is too much duplication in here, assuming we already have start & stop command why to write the whole boilerplate logic in here?

Yes, I tried to find better solution and also tried to call stopcmd and startcmd inside restartcmd but that didn't work. Can we do this, calling startcmd  inside restartcmd ?

Yes, I tried to find better solution and also tried to call stopcmd and startcmd inside restartcmd but that didn't work. Can we do this, calling startcmd inside restartcmd ?

Can you share the error logs or what was the issue when you tried the above approach? IMO ,this should be the ideal approach considering we have to implement start & stop with flags to observe reset & skip-update, we should just observe the flags & use exec.Command to call the commands.

Yes, I tried to find better solution and also tried to call stopcmd and startcmd inside restartcmd but that didn't work. Can we do this, calling startcmd inside restartcmd ?

Can you share the error logs or what was the issue when you tried the above approach? IMO ,this should be the ideal approach considering we have to implement start & stop with flags to observe reset & skip-update, we should just observe the flags & use exec.Command to call the commands.

@kushthedude thanks, earlier I was not using exec(I thought it is not the conventional way to create a new command). but using exec works.

Ideally, we not exec'ing commands like an external script might be. What's preventing this program (mesheryctl) from calling other functions in the same program?

Ideally, we're not exec'ing commands like an external script might be. What's preventing this program (mesheryctl) from calling other functions in the same program?

My latest commit is working fine using exec. And Earlier I was not using  exec.

@subhamkrai, I understand. I'm asking, what the issue is with invoking the other commands internally to stop and start. One area logic in an application (reset) should not need to externally call itself to invoke another area of logic (stop and start). It's the same application, let's keep the invocations internal to the application. Let's work through whatever issues that you're are facing in doing this.

@subhamkrai, I understand. I'm asking, what the issue is with invoking the other commands internally to stop and start. One area logic in an application (reset) should not need to externally call itself to invoke another area of logic (stop and start). It's the same application. Let's keep the invocations internal to the application. Let's work through whatever issues that you're are facing in doing this.
Okay, let me it another try( I have something to similar) or else we'll see the error

@subhamkrai the changes in restart.go and system.go look good. It's not clear to me why changes are needed in start.go and stop.go. I might be missing something, though. @kumarabd, @kushthedude, could you help clarify, if changes in those two files are necessary?

@leecalcote no major changes in start.go and stop.go just keeping them inside the function so that we can call it outside but within the same package for restart.go.

I dont think moving out the cobra runE is good option. It will also reduce
the error handlers which had been invoked utilising the cobras' handlers.
Also, I think we should maintain consistency in all of our commands, moving
forward isn't there anyway to call the cobra sub-commands without making
this functional changes in the code?
On Mon, 3 Aug, 2020, 12:58 abishek<EMAIL_ADDRESS>wrote:

@kumarabd approved this pull request.
@subhamkrai https://github.com/subhamkrai This looks good, given that
the start and stop handlers been moved outside RunE and they have been
reused. Looks great! // @leecalcote https://github.com/leecalcote
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/layer5io/meshery/pull/1317#pullrequestreview-459804290,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKQMTLQFVLSXO3Y2ZQTBDILR6ZRKTANCNFSM4PIOMT5Q
.

See the answer over here https://github.com/spf13/cobra/issues/379
On Mon, 3 Aug, 2020, 13:03 Kush Trivedi<EMAIL_ADDRESS>wrote:

I dont think moving out the cobra runE is good option. It will also reduce
the error handlers which had been invoked utilising the cobras' handlers.
Also, I think we should maintain consistency in all of our commands, moving
forward isn't there anyway to call the cobra sub-commands without making
this functional changes in the code?
On Mon, 3 Aug, 2020, 12:58 abishek<EMAIL_ADDRESS>wrote:

@kumarabd approved this pull request.
@subhamkrai https://github.com/subhamkrai This looks good, given that
the start and stop handlers been moved outside RunE and they have been
reused. Looks great! // @leecalcote https://github.com/leecalcote
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/layer5io/meshery/pull/1317#pullrequestreview-459804290,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKQMTLQFVLSXO3Y2ZQTBDILR6ZRKTANCNFSM4PIOMT5Q
.

I dont think moving out the cobra runE is good option. It will also reduce the error handlers which had been invoked utilising the cobras' handlers. Also, I think we should maintain consistency in all of our commands, moving forward isn't there anyway to call the cobra sub-commands without making this functional changes in the code?
…
On Mon, 3 Aug, 2020, 12:58 abishek, @.> wrote: @.* approved this pull request. @subhamkrai https://github.com/subhamkrai This looks good, given that the start and stop handlers been moved outside RunE and they have been reused. Looks great! // @leecalcote https://github.com/leecalcote — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1317 (review)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKQMTLQFVLSXO3Y2ZQTBDILR6ZRKTANCNFSM4PIOMT5Q .

@kushthedude He has just moved the body of RunE into a separate function and ultimately returning the control to RunE. I think this should work and will not affect cobra's error handling as the control is returned. @leecalcote  You thoughts?


April 5th 2022, Community Meeting Agenda

Dapr Community Meetings
Every two weeks we host a community meeting to showcase new features, review upcoming milestones, and engage in Q&A with the Dapr community - all are welcome, and we encourage participation.
The purpose of this thread is to form a discussion amongst the Dapr community on potential topics to highlight during the meeting. If you have a topic you wish to present or learn more about, please comment and be sure to include your name and a short description of the topic.
The conversations in this thread will directly influence the meeting agenda for the community call on April 5th, 2022, at 10:00am PST. The meeting agenda will be finalized by a Community Call Host days prior to the meeting.
Thank you and we look forward to hearing your input.

Title: Dapr on Kyma - What to consider and how to start
Abstract:  In this talk and demo we will show how to get started with Dapr on Kyma, how to avoid installation pitfalls and how to use it in combination with the Kyma Stack. Sneak peek available at https://blogs.sap.com/2022/02/25/whats-new-with-kyma-2.0-installing-your-own-components/
CC @yaron2 : as discussed

@paulgyro will present a production use case of Dapr done by enChoice for a public sector agency.

@lechnerc77 - Thanks for the title and agenda
@paulgyro - Can you suggest a title, agenda and how long you would need?

@msfussell : My talk with demo would be something like 20 minutes. Let me know if that's okay

@paulgyro - Can you suggest a title, agenda and how long you would need?
Title: How enChoice built a Conversion System with Dapr
Abstract: Paul Widner, Director of Solution Engineering at enChoice discusses a recent success story where his team built a Conversion System for a large public sector retirement agency using Dapr, gRPC, MongoDB, and Azure Service Bus.

@paulgyro - Thanks.How long will you need? Keeping this to under 20 mins would be best.

@paulgyro - Thanks.How long will you need? Keeping this to under 20 mins would be best.

Plan on me taking 15 minutes.

@paulgyro - 15 minutes works well, thank you.
@lechnerc77 - confirming that you're still available to present?
Please plan on joining the community meeting 10 minutes prior to the scheduled call. That will allow time for a quick tech check. Thanks!.

@greenie-msft I confirm that I am available to present - all ready to go :-)
How shall we join the call - is there a meeting request/link?

@greenie-msft I have an issue: I cannot sign into the meeting - it wants me to have a commercial account that I do not have

hmm, that should not be necessary. Have you tried the instructions listed here: https://github.com/dapr/community#community-meetings

This is the meeting link right?
https://us02web.zoom.us/j/85305980190

Yes, that's the correct link.
@paulgyro - was able to sign in with his google account and then provided the passcode. Is that an option for you?

Zoom Call: https://us02web.zoom.us/j/85305980190
Password: eWRhSklVTjJjSnhTaURDcFZaU2ZzQT09

Note you might need to go to Zoom.com and sign up for a free Zoom account and associate it with your personal Google account (or other supported accounts).

@paulgyro That did the trick .. heart rate was rising a bit :-)

Delivered and recorded.


Add support for DigitalOcean Driver

Issue Type

Feature request

Molecule and Ansible details
ansible 2.7.6
molecule, version 2.19.1.dev121

Molecule installation method (one of):

source

Ansible installation method (one of):

pip

Desired Behavior
Add driver to support for DigitalOcean.

Added PR: https://github.com/ansible/molecule/pull/1736
ofc feel free to make recommendations / requests

Oh yes, solid stuff! Digital ocean automation with Molecule is going to be really awesome.

@bmildren I see you've created a PR for this. Excellent thank you. No need to issue first, so I'll close this


Cannot build hostpath provisionner

Hi,
An error appears while I try to build hostPath provisionner:
CGO_ENABLED=0 go build -a -ldflags '-extldflags "-static"' -o hostpath-provisioner .
hostpath-provisioner.go:27:2: cannot find package "github.com/kubernetes-incubator/external-storage/lib/controller" in any of:
	/home/pafer/go/src/github.com/kubernetes-incubator/external-storage/lib/controller (from $GOROOT)
	/home/pafer/Projects/goprojects/src/github.com/kubernetes-incubator/external-storage/lib/controller (from $GOPATH)
hostpath-provisioner.go:28:2: cannot find package "k8s.io/apimachinery/pkg/apis/meta/v1" in any of:
	/home/pafer/go/src/k8s.io/apimachinery/pkg/apis/meta/v1 (from $GOROOT)
	/home/pafer/Projects/goprojects/src/k8s.io/apimachinery/pkg/apis/meta/v1 (from $GOPATH)
hostpath-provisioner.go:29:2: cannot find package "k8s.io/apimachinery/pkg/util/wait" in any of:
	/home/pafer/go/src/k8s.io/apimachinery/pkg/util/wait (from $GOROOT)
	/home/pafer/Projects/goprojects/src/k8s.io/apimachinery/pkg/util/wait (from $GOPATH)
hostpath-provisioner.go:30:2: cannot find package "k8s.io/client-go/kubernetes" in any of:
	/home/pafer/go/src/k8s.io/client-go/kubernetes (from $GOROOT)
	/home/pafer/Projects/goprojects/src/k8s.io/client-go/kubernetes (from $GOPATH)
hostpath-provisioner.go:31:2: cannot find package "k8s.io/client-go/pkg/api/v1" in any of:
	/home/pafer/go/src/k8s.io/client-go/pkg/api/v1 (from $GOROOT)
	/home/pafer/Projects/goprojects/src/k8s.io/client-go/pkg/api/v1 (from $GOPATH)
hostpath-provisioner.go:32:2: cannot find package "k8s.io/client-go/rest" in any of:
	/home/pafer/go/src/k8s.io/client-go/rest (from $GOROOT)
	/home/pafer/Projects/goprojects/src/k8s.io/client-go/rest (from $GOPATH)
Makefile:23: recipe for target 'hostpath-provisioner' failed
make: *** [hostpath-provisioner] Error 1

Tried with go 1.7.5 and go 1.8.3, same result.
Any help can be appreciated

Did you run glide install -v in the hostpath-provisioner directory first? client-go and apimachinery are quite unstable so we use glide to fix our dependency on specific older versions

Yes I did it.
What I cannot understand is why I doesn't see any reference of vendor directory while go is searching libraries.
Here are the full logs:
~/Projects/Lab/external-storage  cd docs/demo/hostpath-provisioner/
 ~/Projects/Lab/external-storage/docs/demo/hostpath-provisioner  glide install -v

[WARN]	The name listed in the config file (github.com/kubernetes-incubator/external-storage/docs/demo/hostpath-provisioner) does not match the current location (.)
[INFO]	Downloading dependencies. Please wait...
[INFO]	--> Found desired version locally github.com/davecgh/go-spew 5215b55f46b2b919f50a1df0eaa5886afe4e3b3d!
[INFO]	--> Found desired version locally github.com/docker/distribution cd27f179f2c10c5d300e6d09025b538c475b0d51!
[INFO]	--> Found desired version locally github.com/emicklei/go-restful 09691a3b6378b740595c1002f40c34dd5f218a22!
[INFO]	--> Found desired version locally github.com/ghodss/yaml 73d445a93680fa1a78ae23a5839bad48f32ba1ee!
[INFO]	--> Found desired version locally github.com/go-openapi/jsonpointer 46af16f9f7b149af66e5d1bd010e3574dc06de98!
[INFO]	--> Found desired version locally github.com/go-openapi/jsonreference 13c6e3589ad90f49bd3e3bbe2c2cb3d7a4142272!
[INFO]	--> Found desired version locally github.com/go-openapi/spec 6aced65f8501fe1217321abf0749d354824ba2ff!
[INFO]	--> Found desired version locally github.com/go-openapi/swag 1d0bd113de87027671077d3c71eb3ac5d7dbba72!
[INFO]	--> Found desired version locally github.com/gogo/protobuf e18d7aa8f8c624c915db340349aad4c49b10d173!
[INFO]	--> Found desired version locally github.com/golang/glog 44145f04b68cf362d9c4df2182967c2275eaefed!
[INFO]	--> Found desired version locally github.com/golang/groupcache 02826c3e79038b59d737d3b1c0a1d937f71a4433!
[INFO]	--> Found desired version locally github.com/google/gofuzz 44d81051d367757e1c7c6a5a86423ece9afcf63c!
[INFO]	--> Found desired version locally github.com/juju/ratelimit 77ed1c8a01217656d2080ad51981f6e99adaa177!
[INFO]	--> Found desired version locally github.com/kubernetes-incubator/external-storage c5e69a02cc1f9db5171efbac7284ee6f3cc0c49f!
[INFO]	--> Found desired version locally github.com/mailru/easyjson d5b7844b561a7bc640052f1b935f7b800330d7e0!
[INFO]	--> Found desired version locally github.com/pborman/uuid ca53cad383cad2479bbba7f7a1a05797ec1386e4!
[INFO]	--> Found desired version locally github.com/PuerkitoBio/purell 8a290539e2e8629dbc4e6bad948158f790ec31f4!
[INFO]	--> Found desired version locally github.com/PuerkitoBio/urlesc 5bd2802263f21d8788851d5305584c82a5c75d7e!
[INFO]	--> Found desired version locally github.com/spf13/pflag 9ff6c6923cfffbcd502984b8e0c80539a94968b7!
[INFO]	--> Found desired version locally github.com/ugorji/go ded73eae5db7e7a0ef6f55aace87a2873c5d2b74!
[INFO]	--> Found desired version locally golang.org/x/net e90d6d0afc4c315a0d87a568ae68577cc15149a0!
[INFO]	--> Found desired version locally golang.org/x/text 2910a502d2bf9e43193af9d68ca516529614eed3!
[INFO]	--> Found desired version locally gopkg.in/inf.v0 3887ee99ecf07df5b447e9b00d9c0b2adaa9f3e4!
[INFO]	--> Found desired version locally gopkg.in/yaml.v2 53feefa2559fb8dfa8d81baad31be332c97d6c77!
[INFO]	--> Found desired version locally k8s.io/apimachinery c1c4a7fe832857c75cc1d79c8e40d71d5da15fc6!
[INFO]	--> Found desired version locally k8s.io/client-go 76153773eaa3a268131d3d993290a194a1370585!
[INFO]	--> Found desired version locally k8s.io/kubernetes fff5156092b56e6bd60fff75aad4dc9de6b6ef37!
[INFO]	Setting references.
[INFO]	--> Setting version for github.com/PuerkitoBio/purell to 8a290539e2e8629dbc4e6bad948158f790ec31f4.
[INFO]	--> Setting version for github.com/ugorji/go to ded73eae5db7e7a0ef6f55aace87a2873c5d2b74.
[INFO]	--> Setting version for github.com/kubernetes-incubator/external-storage to c5e69a02cc1f9db5171efbac7284ee6f3cc0c49f.
[INFO]	--> Setting version for github.com/gogo/protobuf to e18d7aa8f8c624c915db340349aad4c49b10d173.
[INFO]	--> Setting version for github.com/davecgh/go-spew to 5215b55f46b2b919f50a1df0eaa5886afe4e3b3d.
[INFO]	--> Setting version for github.com/PuerkitoBio/urlesc to 5bd2802263f21d8788851d5305584c82a5c75d7e.
[INFO]	--> Setting version for github.com/go-openapi/swag to 1d0bd113de87027671077d3c71eb3ac5d7dbba72.
[INFO]	--> Setting version for github.com/pborman/uuid to ca53cad383cad2479bbba7f7a1a05797ec1386e4.
[INFO]	--> Setting version for github.com/spf13/pflag to 9ff6c6923cfffbcd502984b8e0c80539a94968b7.
[INFO]	--> Setting version for github.com/emicklei/go-restful to 09691a3b6378b740595c1002f40c34dd5f218a22.
[INFO]	--> Setting version for github.com/mailru/easyjson to d5b7844b561a7bc640052f1b935f7b800330d7e0.
[INFO]	--> Setting version for github.com/juju/ratelimit to 77ed1c8a01217656d2080ad51981f6e99adaa177.
[INFO]	--> Setting version for github.com/google/gofuzz to 44d81051d367757e1c7c6a5a86423ece9afcf63c.
[INFO]	--> Setting version for github.com/go-openapi/jsonpointer to 46af16f9f7b149af66e5d1bd010e3574dc06de98.
[INFO]	--> Setting version for github.com/go-openapi/jsonreference to 13c6e3589ad90f49bd3e3bbe2c2cb3d7a4142272.
[INFO]	--> Setting version for github.com/ghodss/yaml to 73d445a93680fa1a78ae23a5839bad48f32ba1ee.
[INFO]	--> Setting version for github.com/golang/groupcache to 02826c3e79038b59d737d3b1c0a1d937f71a4433.
[INFO]	--> Setting version for github.com/docker/distribution to cd27f179f2c10c5d300e6d09025b538c475b0d51.
[INFO]	--> Setting version for github.com/golang/glog to 44145f04b68cf362d9c4df2182967c2275eaefed.
[INFO]	--> Setting version for github.com/go-openapi/spec to 6aced65f8501fe1217321abf0749d354824ba2ff.
[INFO]	--> Setting version for golang.org/x/net to e90d6d0afc4c315a0d87a568ae68577cc15149a0.
[INFO]	--> Setting version for golang.org/x/text to 2910a502d2bf9e43193af9d68ca516529614eed3.
[INFO]	--> Setting version for gopkg.in/inf.v0 to 3887ee99ecf07df5b447e9b00d9c0b2adaa9f3e4.
[INFO]	--> Setting version for gopkg.in/yaml.v2 to 53feefa2559fb8dfa8d81baad31be332c97d6c77.
[INFO]	--> Setting version for k8s.io/apimachinery to c1c4a7fe832857c75cc1d79c8e40d71d5da15fc6.
[INFO]	--> Setting version for k8s.io/client-go to 76153773eaa3a268131d3d993290a194a1370585.
[INFO]	--> Setting version for k8s.io/kubernetes to fff5156092b56e6bd60fff75aad4dc9de6b6ef37.
[INFO]	Exporting resolved dependencies...

[INFO]	Removing: /home/pafer/Projects/Lab/external-storage/docs/demo/hostpath-provisioner/vendor/github.com/docker/distribution/vendor
[INFO]	Removing: /home/pafer/Projects/Lab/external-storage/docs/demo/hostpath-provisioner/vendor/github.com/kubernetes-incubator/external-storage/vendor
[INFO]	Removing: /home/pafer/Projects/Lab/external-storage/docs/demo/hostpath-provisioner/vendor/k8s.io/apimachinery/vendor
[INFO]	Removing: /home/pafer/Projects/Lab/external-storage/docs/demo/hostpath-provisioner/vendor/k8s.io/client-go/vendor
[INFO]	Removing: /home/pafer/Projects/Lab/external-storage/docs/demo/hostpath-provisioner/vendor/k8s.io/kubernetes/vendor

 ~/Projects/Lab/external-storage/docs/demo/hostpath-provisioner  make
glide install -v --strip-vcs
[WARN]	The --strip-vcs flag is deprecated. This now works by default.
[WARN]	The name listed in the config file (github.com/kubernetes-incubator/external-storage/docs/demo/hostpath-provisioner) does not match the current location (.)
[INFO]	Downloading dependencies. Please wait...
[INFO]	--> Found desired version locally github.com/davecgh/go-spew 5215b55f46b2b919f50a1df0eaa5886afe4e3b3d!
[INFO]	--> Found desired version locally github.com/docker/distribution cd27f179f2c10c5d300e6d09025b538c475b0d51!
[INFO]	--> Found desired version locally github.com/emicklei/go-restful 09691a3b6378b740595c1002f40c34dd5f218a22!
[INFO]	--> Found desired version locally github.com/ghodss/yaml 73d445a93680fa1a78ae23a5839bad48f32ba1ee!
[INFO]	--> Found desired version locally github.com/go-openapi/jsonpointer 46af16f9f7b149af66e5d1bd010e3574dc06de98!
[INFO]	--> Found desired version locally github.com/go-openapi/jsonreference 13c6e3589ad90f49bd3e3bbe2c2cb3d7a4142272!
[INFO]	--> Found desired version locally github.com/go-openapi/spec 6aced65f8501fe1217321abf0749d354824ba2ff!
[INFO]	--> Found desired version locally github.com/go-openapi/swag 1d0bd113de87027671077d3c71eb3ac5d7dbba72!
[INFO]	--> Found desired version locally github.com/gogo/protobuf e18d7aa8f8c624c915db340349aad4c49b10d173!
[INFO]	--> Found desired version locally github.com/golang/glog 44145f04b68cf362d9c4df2182967c2275eaefed!
[INFO]	--> Found desired version locally github.com/golang/groupcache 02826c3e79038b59d737d3b1c0a1d937f71a4433!
[INFO]	--> Found desired version locally github.com/google/gofuzz 44d81051d367757e1c7c6a5a86423ece9afcf63c!
[INFO]	--> Found desired version locally github.com/juju/ratelimit 77ed1c8a01217656d2080ad51981f6e99adaa177!
[INFO]	--> Found desired version locally github.com/kubernetes-incubator/external-storage c5e69a02cc1f9db5171efbac7284ee6f3cc0c49f!
[INFO]	--> Found desired version locally github.com/mailru/easyjson d5b7844b561a7bc640052f1b935f7b800330d7e0!
[INFO]	--> Found desired version locally github.com/pborman/uuid ca53cad383cad2479bbba7f7a1a05797ec1386e4!
[INFO]	--> Found desired version locally github.com/PuerkitoBio/purell 8a290539e2e8629dbc4e6bad948158f790ec31f4!
[INFO]	--> Found desired version locally github.com/PuerkitoBio/urlesc 5bd2802263f21d8788851d5305584c82a5c75d7e!
[INFO]	--> Found desired version locally github.com/spf13/pflag 9ff6c6923cfffbcd502984b8e0c80539a94968b7!
[INFO]	--> Found desired version locally github.com/ugorji/go ded73eae5db7e7a0ef6f55aace87a2873c5d2b74!
[INFO]	--> Found desired version locally golang.org/x/net e90d6d0afc4c315a0d87a568ae68577cc15149a0!
[INFO]	--> Found desired version locally golang.org/x/text 2910a502d2bf9e43193af9d68ca516529614eed3!
[INFO]	--> Found desired version locally gopkg.in/inf.v0 3887ee99ecf07df5b447e9b00d9c0b2adaa9f3e4!
[INFO]	--> Found desired version locally gopkg.in/yaml.v2 53feefa2559fb8dfa8d81baad31be332c97d6c77!
[INFO]	--> Found desired version locally k8s.io/apimachinery c1c4a7fe832857c75cc1d79c8e40d71d5da15fc6!
[INFO]	--> Found desired version locally k8s.io/client-go 76153773eaa3a268131d3d993290a194a1370585!
[INFO]	--> Found desired version locally k8s.io/kubernetes fff5156092b56e6bd60fff75aad4dc9de6b6ef37!
[INFO]	Setting references.
[INFO]	--> Setting version for github.com/golang/glog to 44145f04b68cf362d9c4df2182967c2275eaefed.
[INFO]	--> Setting version for github.com/ugorji/go to ded73eae5db7e7a0ef6f55aace87a2873c5d2b74.
[INFO]	--> Setting version for github.com/spf13/pflag to 9ff6c6923cfffbcd502984b8e0c80539a94968b7.
[INFO]	--> Setting version for github.com/go-openapi/swag to 1d0bd113de87027671077d3c71eb3ac5d7dbba72.
[INFO]	--> Setting version for github.com/PuerkitoBio/purell to 8a290539e2e8629dbc4e6bad948158f790ec31f4.
[INFO]	--> Setting version for github.com/docker/distribution to cd27f179f2c10c5d300e6d09025b538c475b0d51.
[INFO]	--> Setting version for github.com/go-openapi/jsonpointer to 46af16f9f7b149af66e5d1bd010e3574dc06de98.
[INFO]	--> Setting version for github.com/PuerkitoBio/urlesc to 5bd2802263f21d8788851d5305584c82a5c75d7e.
[INFO]	--> Setting version for github.com/go-openapi/jsonreference to 13c6e3589ad90f49bd3e3bbe2c2cb3d7a4142272.
[INFO]	--> Setting version for github.com/juju/ratelimit to 77ed1c8a01217656d2080ad51981f6e99adaa177.
[INFO]	--> Setting version for github.com/gogo/protobuf to e18d7aa8f8c624c915db340349aad4c49b10d173.
[INFO]	--> Setting version for github.com/mailru/easyjson to d5b7844b561a7bc640052f1b935f7b800330d7e0.
[INFO]	--> Setting version for github.com/google/gofuzz to 44d81051d367757e1c7c6a5a86423ece9afcf63c.
[INFO]	--> Setting version for github.com/emicklei/go-restful to 09691a3b6378b740595c1002f40c34dd5f218a22.
[INFO]	--> Setting version for github.com/davecgh/go-spew to 5215b55f46b2b919f50a1df0eaa5886afe4e3b3d.
[INFO]	--> Setting version for github.com/golang/groupcache to 02826c3e79038b59d737d3b1c0a1d937f71a4433.
[INFO]	--> Setting version for github.com/pborman/uuid to ca53cad383cad2479bbba7f7a1a05797ec1386e4.
[INFO]	--> Setting version for github.com/ghodss/yaml to 73d445a93680fa1a78ae23a5839bad48f32ba1ee.
[INFO]	--> Setting version for github.com/go-openapi/spec to 6aced65f8501fe1217321abf0749d354824ba2ff.
[INFO]	--> Setting version for github.com/kubernetes-incubator/external-storage to c5e69a02cc1f9db5171efbac7284ee6f3cc0c49f.
[INFO]	--> Setting version for golang.org/x/net to e90d6d0afc4c315a0d87a568ae68577cc15149a0.
[INFO]	--> Setting version for golang.org/x/text to 2910a502d2bf9e43193af9d68ca516529614eed3.
[INFO]	--> Setting version for gopkg.in/inf.v0 to 3887ee99ecf07df5b447e9b00d9c0b2adaa9f3e4.
[INFO]	--> Setting version for k8s.io/apimachinery to c1c4a7fe832857c75cc1d79c8e40d71d5da15fc6.
[INFO]	--> Setting version for gopkg.in/yaml.v2 to 53feefa2559fb8dfa8d81baad31be332c97d6c77.
[INFO]	--> Setting version for k8s.io/client-go to 76153773eaa3a268131d3d993290a194a1370585.
[INFO]	--> Setting version for k8s.io/kubernetes to fff5156092b56e6bd60fff75aad4dc9de6b6ef37.
[INFO]	Exporting resolved dependencies...

[INFO]	Removing: /home/pafer/Projects/Lab/external-storage/docs/demo/hostpath-provisioner/vendor/github.com/docker/distribution/vendor
[INFO]	Removing: /home/pafer/Projects/Lab/external-storage/docs/demo/hostpath-provisioner/vendor/github.com/kubernetes-incubator/external-storage/vendor
[INFO]	Removing: /home/pafer/Projects/Lab/external-storage/docs/demo/hostpath-provisioner/vendor/k8s.io/apimachinery/vendor
[INFO]	Removing: /home/pafer/Projects/Lab/external-storage/docs/demo/hostpath-provisioner/vendor/k8s.io/client-go/vendor
[INFO]	Removing: /home/pafer/Projects/Lab/external-storage/docs/demo/hostpath-provisioner/vendor/k8s.io/kubernetes/vendor
CGO_ENABLED=0 go build -a -ldflags '-extldflags "-static"' -o hostpath-provisioner .
hostpath-provisioner.go:26:2: cannot find package "github.com/golang/glog" in any of:
	/home/pafer/go/src/github.com/golang/glog (from $GOROOT)
	/home/pafer/Projects/goprojects/src/github.com/golang/glog (from $GOPATH)
hostpath-provisioner.go:27:2: cannot find package "github.com/kubernetes-incubator/external-storage/lib/controller" in any of:
	/home/pafer/go/src/github.com/kubernetes-incubator/external-storage/lib/controller (from $GOROOT)
	/home/pafer/Projects/goprojects/src/github.com/kubernetes-incubator/external-storage/lib/controller (from $GOPATH)
hostpath-provisioner.go:28:2: cannot find package "k8s.io/apimachinery/pkg/apis/meta/v1" in any of:
	/home/pafer/go/src/k8s.io/apimachinery/pkg/apis/meta/v1 (from $GOROOT)
	/home/pafer/Projects/goprojects/src/k8s.io/apimachinery/pkg/apis/meta/v1 (from $GOPATH)
hostpath-provisioner.go:29:2: cannot find package "k8s.io/apimachinery/pkg/util/wait" in any of:
	/home/pafer/go/src/k8s.io/apimachinery/pkg/util/wait (from $GOROOT)
	/home/pafer/Projects/goprojects/src/k8s.io/apimachinery/pkg/util/wait (from $GOPATH)
hostpath-provisioner.go:30:2: cannot find package "k8s.io/client-go/kubernetes" in any of:
	/home/pafer/go/src/k8s.io/client-go/kubernetes (from $GOROOT)
	/home/pafer/Projects/goprojects/src/k8s.io/client-go/kubernetes (from $GOPATH)
hostpath-provisioner.go:31:2: cannot find package "k8s.io/client-go/pkg/api/v1" in any of:
	/home/pafer/go/src/k8s.io/client-go/pkg/api/v1 (from $GOROOT)
	/home/pafer/Projects/goprojects/src/k8s.io/client-go/pkg/api/v1 (from $GOPATH)
hostpath-provisioner.go:32:2: cannot find package "k8s.io/client-go/rest" in any of:
	/home/pafer/go/src/k8s.io/client-go/rest (from $GOROOT)
	/home/pafer/Projects/goprojects/src/k8s.io/client-go/rest (from $GOPATH)
Makefile:23 : la recette pour la cible « hostpath-provisioner » a échouée
make: *** [hostpath-provisioner] Erreur 1

Anyway, I'm wondering if I should use docs/demo/hostpath-provisioner or the local-volume...

BTW:
glide get github.com/golang/glog
[WARN]	The name listed in the config file (github.com/kubernetes-incubator/external-storage) does not match the current location (.)
[INFO]	Preparing to install 1 package.
[INFO]	Attempting to get package github.com/golang/glog
[WARN]	--> Package "github.com/golang/glog" is already in glide.yaml. Skipping
[WARN]	Nothing to do

ll vendor/github.com/golang/glog
total 76
drwxr-xr-x. 2 pafer pafer  4096 26 juin  17:21 .
drwxr-xr-x. 4 pafer pafer  4096 26 juin  17:21 ..
-rw-rw-r--. 1 pafer pafer  3323 26 juin  17:21 glog_file.go
-rw-rw-r--. 1 pafer pafer 36277 26 juin  17:21 glog.go
-rw-rw-r--. 1 pafer pafer 11439 26 juin  17:21 glog_test.go
-rw-rw-r--. 1 pafer pafer 10273 26 juin  17:21 LICENSE

My god... forget my bug... the "glide get" command gave me the problem, I wasn't at the right place. I needed to get project in GOPATH/src
My apologies

Ah it is because external-storage must be in your GOPATH for the "vendor" stuff to work. Go won't bother to look for ./vendor unless you're working in a descendent of GOPATH. (Dumb I know).
The hostpath provisioner is intended to be a barebones toy demo (hence forcing people to build it to use it, etc.) that will only work properly on single-node clusters. Local-volume will be the way to go for local storage but is alpha in 1.7 only.

yeah, I realized that it can only work on a single node installation later ;)
And that's very ennoying that local-volume only works on 1.7 only, I'm using openshift 1.5.1 that incluse k8s 1.5 :\
So, that means that I will not be able to have Galera with hostpath on our cluster :(


OLED Dark Version of Theme

It would be fantastic if there was an OLED Dark version of the theme (full black background with darker panel background elements).
Any thoughts on adding a preconfigured theme for that?

Hi!
I'm not actively developing this project, so don't expect this feature from me. However, I'm happy to take contributions, and can answer some questions, if one want to tackle this.
I'm not sure how much this would reduce energy consumption, but it would certainly have an impact. Generally speaking, though, pure black is something that is mostly avoided on user interface elements because it creates too much contrast and thus increases eye strain.

I could take a stab at it, got any resources to point me in the right direction?


Responsive Article Component

Article section details:

[ ]  Layout (@owendodd what kind of minimum margins should we have?)
[ ]  Embed (change to mobile height at 400px)
[ ]  Callouts (push to inline with body instead of floating at 400px)
[ ]  Artworks and Images (stack artworks at 400px)
[ ]  Images (mostly stay the same, except adjust for screen width )
[ ]  Text (use mobile font size at 400px)
[ ]  Image Set (mostly stay the same, except adjust for screen width)
[ ]  TOC (switch from 3 columns to 2 at 400px)
[ ]  Video (mostly stay the same, except adjust for screen width)
[ ]  Fullscreen header (use mobile font size and margin at 400px)

More details TK!

Other places to be considerate about when working on this:

Fair pages
Partner articles


Horizontal Mouse wheel support and Topic++ group export fix

Adds feature Horizontal Mouse Wheel support in CtrlCore for POSIX and Win32.
Fixes touch/pen detection for Win32 to allow touch screen gestures to pass through as normal mouse ops.
Fixes cross linking of files in Topic++ group export result files (PDFs and HTMLs).

Hello Tom,
Thanks for creating this PR! Optimally it should be divided into four separate PR's (on your fork you can have multiple branches):

dedicated to horizontal mouse wheel support
dedicated to touch screen gestures
dedicated to topic++ improvemenets
dedicated to zip64 support

Right now we have a problem everything or nothing. With separation of PR's some of things might be merged sooner than later. So, please reconsider dividing your PR's. Of course Mirek will have last word, but from my point of view it is the best approach. I added Mirek to the review.
Klugier

Hi Klugier,
I proceeded while learning from the github docs and ended up in this unfavorable situation. When I discovered the problem of them all being bundled together, it was too late (or early if you look at the clock) to figure out how to fix it.
Anyway, I will try to learn about managing branches and get better results next time. (In any case, I have to say that this seems like a lot of work to get a few files transferred.)
Thanks for your attention and guidance.
Best regards,
Tom
Sent from Proton Mail mobile
-------- Original Message --------
On 11. helmik. 2024 klo 10.56, Zbigniew Rębacz wrote:

Hello Tom,
Thanks for creating this PR! Optimally it should be divided into four separate PR's (on your fork you can have multiple branches):

dedicated to horizontal mouse wheel support
dedicated to touch screen gestures
dedicated to topic++ improvemenets
dedicated to zip64 support

Right now we have a problem everything or nothing. With separation of PR's some of things might be merged sooner than later. So, please reconsider dividing your PR's. Of course Mirek will have last word, but from my point of view it is the best approach. I added Mirek to the review.
Klugier
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Hello Tom,
Sure. Thanks for reflection! I think Mirek will be able to modify your patches to integrate them with master branch.
Klugier

Hi, I just completed splitting them to separate branches. Should I now create PRs for each of them and cancel the original multi feature PR?
Tom
Sent from Proton Mail mobile
-------- Original Message --------
On 11. helmik. 2024 klo 13.10, Zbigniew Rębacz wrote:

Hello Tom,
Sure. Thanks for reflection! I think Mirek will be able to modify your patches to integrate them with master branch.
Klugier
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Hello Tom,
If you can, please do that. Separate PR's with dedicated changes is optimal approach.
Klugier

Hi Klugier,
I think this PR is now redundant. All four categories here are now covered in separate PRs pointing to specific branches.
Tom


Don't store OAuth token in ~/.config

Like most developer UNIX users, I like to keep configuration files in a 'dotfiles' repo. Because of things like GTK config, I include the ~/.config folder in that repo, as I'm sure many people do as well. However, since hub stores the oauth token in ~/.config/hub I have to add an explicit entry to my .gitignore to prevent that file from getting committed to my public dotfiles repo.  It seems to me like hub should make this sort of silliness less easy to do accidentally.

I believe git is already capable of reading credentials out of ~/.netrc.gpg using git-credential-netrc, which would make a lot more sense than storing extremely sensitive credential data in plaintext. Would it be possible to make hub use whatever credential helper git is already configured to use?

@technomancy Yes I'm interested in adding a feature to hub to support a credential helper. Any advice about the exact protocol used for talking to a credential helper would be welcome.

As a temporary workaround, I'm using this wrapper around hub:
#!/bin/bash

HUB_CONFIG_GPG=$HOME/.config/hub.toml.gpg
export HUB_CONFIG=$(mktemp -t tmp.XXXXXXXX.hub)

function finish {
  rm -rf "$HUB_CONFIG"
}

trap finish EXIT

gpg -q -d "${HUB_CONFIG_GPG}" > "${HUB_CONFIG}"

exec "${HOME}/src/hub/bin/hub" $@

@mislav Thanks; I will do some digging and see if there's a way for non-git programs to tap into the methods it uses for resolving credentials. Too bad this isn't done in Ruby any more, since I already implemented support for this there. =)

@mislav See here. Basically, you run git credential with an argument of either fill, approve, or reject:

fill retrieves credentials
approve stores credentials
reject removes stored credentials

Then, on stdin, you feed it something in this format, followed by an empty line. The format is basically key=value, with the following keys:

protocol is the protocol (e.g. https, ssh, git)
host is the remote hostname (e.g. github.com)
path is the path to the remote repository (e.g. github/hub.git)
username is the username (e.g. mislav)
password is the password (or, in our case, the personal OAuth token)
url is the full clone URL

Which of these must be provided will depend on what command you're using. For fill and reject, you only need to specify protocol and host, though path and username may optionally be provided if available. For approve, protocol, host, username, and password should be provided, though path can also be provided if you want to provide credentials specific to a particular repository. If you provide a value for url, any other values that are present in it will be parsed out (e.g<EMAIL_ADDRESS>has values for protocol, host, path, username, and password).
If you're performing a fill operation, the command will then spit out something like this:
protocol=https
host=github.com
username=elyscape
password=oauth-token

You can also call the credential helpers directly. They work the same as git credential, except that their commands are get, store, and erase instead of fill, approve, and reject. Still, it's probably better to use git credential and let it worry about paths and which helper to use.

As a side note, calls to git credential will, by default, filter out the repo path if the protocol is HTTP(S) before passing the parameters to the credential helper.

Thanks for the research. That seems reasonable. The tricky part of implementing this is going to be deciding what to do with existing credentials that might be stored for https://github.com/, but which are a Personal Access Token that someone generated for git cloning purposes only and which wouldn't work with a bunch of operations that hub needs to utilize the API for.


Condiitional insert types

I have a rust binary where I want to conditionally make the inserts "async inserts" depending on a specific environment variable. Wondering whats the best way to do this.
Thanks!

We have the example for async insertions, so you can read that specific environment variable and configure the client depending on it.

Thanks @loyd - i missed seeing that in the docs.


Auto-Exposure Not Consistently Working at System Init on D435

Running v2.0.2 of this package with v2.10.0 of librealsense and camera firmware <IP_ADDRESS>. Ubuntu 16.04 with 4.10.0-28 kernel.
I noticed quite poor depth performance when viewing the Point Cloud in RVIZ after power cycling the D435 camera but no issue when using realsense-viewer. This caused the data in RVIZ to appear splotchy and inconsistent.
I then launched rosrun rqt_reconfigure rqt_reconfigure and noticed that the auto-exposure for the depth stream (first checkbox at the top of the realsense config menu) was indeed turned on (as indicated by the box being checked). However, unchecking this box and then re-checking it consistently fixed the issue indicating that auto-exposure at nodelet boot is not working. This might be an issue on the librealsense side, but I'm not too sure since it looked OK in realsense-viewer.

I am experiencing the same thing.

@Mitchell-Hampton, @dpipemazo, please post the output of the RealSense ROS node.

I managed to reproduce this issue and it looks like a firmware bug.
As a workaround you can physically replug the camera or call to Hardware Reset method.

@icarpis Thanks for looking into it! Sorry I didn't post the output of the node; got pulled away from working on it for a few days. Is there an issue filed on the firmware that I can follow for it? I am happy to file it if you'd like.

I just ran into this issue as well. The auto exposure works well after toggling it off & on in rqt_reconfigure. I am going to try calling hardware_reset and see if that helps.
@icarpis I would be really interested in a firmware fix for this as well.

Can you confirm that you are only seeing this on Linux AND ROS? I dont see this issue on Windows, but maybe I am not doing the right thing to reproduce. We need to figure out whether it is FW or SW.

We have experienced the same issue, this is the script we use to solve it now (as a workaround):
#!/bin/bash
rosrun dynamic_reconfigure dynparam set realsense2_camera_manager rs435_depth_enable_auto_exposure 0
rosrun dynamic_reconfigure dynparam set realsense2_camera_manager rs435_depth_enable_auto_exposure 1

This script can be put in the launch file where you start the node and nodelet manager.

@agrunnet : Yep, I am seeing it only on Linux & ROS. In the Realsense viewer on Windows it launches fine with depth auto exposure enabled.

Any updates on this issue?

@reinzor, I'm on the latest version for the librealense, SDK, and so on. Your script doesn't seem to work, I still have to toggle it in rqt_reconfigure. Any suggestions?

@fiorano10 , this script performs exactly the same service calls than you are doing with the gui. Please check whether your node argument is correct:
Usage: dynparam set [options] node parameter value

Yes, re-check your nodelet manager name. The first argument (args attribute) has to point to the nodelet manager that is running your camera driver nodelet.
You can use the rosnode cli to obtain the names of the running nodes:
rosnode list

I have had the same issue with the d415. I believe it is caused as setting the manual exposure causes the system to drop out of auto exposure mode, and the manual exposure is set on startup.
I fixed the issue on my system by adding
if(config.rs415_depth_enable_auto_exposure){     BaseD400Node::setParam(config, base_depth_enable_auto_exposure); }
After this line https://github.com/intel-ros/realsense/blob/development/realsense2_camera/src/rs415_node.cpp#L93. I expect the same fix would work for the d435 node

Thanks @ZacharyTaylor ! I can confirm it works for the d435.

Thanks @ZacharyTaylor. I opened PR #392 implementing the proposed fix.

Hope to see this fixed soon!

Running the procedure that @dpipemazo mentioned in his original post, with the latest RealSense updates (that is librealsense version 2.16, Real Sense firmware version 05.10.03 and latest realsense2_camera [31a0e4d] ), it would seem that auto exposure is working on start up.
It would be interesting if others could conform this as well.

fixed in the latest commit. Will be available in the upcoming release, hopefully by tomorrow.


Cookie is not being set in production with express and graphql-yoga

Describe the bug
I'm trying to set a cookie from a graphql authentication mutation. I have tried using the Response object express provides in the context which doesn't set the cookie in the Set-Cookie header at all in production. I also tried using the cookieStore plugin that comes from @whatwg-node/server-plugin-cookies which sends the correct Set-Cookie header but the cookie is never set in production also.
My frontend domain is xxx.baraa.app, and the backend is on api.xxx.baraa.app.
    await ctx.request?.cookieStore?.set({
      name: 'access',
      value: token,
      domain: accessTokenCookieDomain,
      path: '/',
      sameSite: 'lax',
      secure: !isDev,
      expires: new Date(Date.now() + 1000 * 60 * 60 * 24 * 7),
    })

With express res:
  ctx.res.cookie('access', token, {
      httpOnly: true,
      domain: accessTokenCookieDomain,
      maxAge: 1000 * 60 * 60 * 24 * 7,
    })

Response header:
Access-Control-Allow-Credentials:
true
Access-Control-Allow-Origin:
https://xxx.baraa.app
Cache-Control:
public, max-age=0, must-revalidate
Content-Length:
39
Content-Type:
application/json; charset=utf-8
Date:
Thu, 18 May 2023 09:53:42 GMT
Server:
Vercel
Set-Cookie:
_ga=GA1.1.223434950.1674928901; _ga_H3TPKGYL58=GS1.1.16841794<IP_ADDRESS>41794<IP_ADDRESS>; access=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImNsaGwzNWZvdTAwMDBsMjA4cHBhbDA1MmEiLCJpYXQiOjE2ODQ0MDM2MjEsImV4cCI6MTY4NTAwODQyMX0.YpjTVzV4Emy6VUHAQRlTnb1x_Os_DQCJhFJRJuiSVhw; Domain=xxx.baraa.app; Path=/; Secure; SameSite=Lax

Your Example Website or App
I can't provide an example.
Steps to Reproduce the Bug or Issue

Initialize an express app and add a createYoga object
Install @whatwg-node/server-plugin-cookies and add it to the plugins
Add the following snippet to your mutation

await ctx.request?.cookieStore?.set({
      name: 'access',
      value: token,
      domain: accessTokenCookieDomain,
      path: '/',
      sameSite: 'lax',
      secure: !isDev,
      expires: new Date(Date.now() + 1000 * 60 * 60 * 24 * 7),
    })

Expected behavior
I'm expecting to get the cookie set.
Screenshots or Videos
No response
Platform

OS: macOS
NodeJS: 18.1.0
@graphql-yoga/* version(s): ^3.9.1

Additional context
No response

I can't provide an example.
We need a reproduction in order to help you.

We can reopen the issue when you provide a reproduction. Closing it for now.


Person's title translations giving confusing choices in other languages

The same translations of the English terms in address book's dropdown list of titles are causing confusion in other languages.
The original choices in English:
https://github.com/django-oscar/django-oscar/blob/1a3372e1728d7b464693da6c78525ef4f13176a1/src/oscar/apps/address/abstract_models.py#L22
are being translated to a same term:  Miss/Mrs/Ms turns Frau/Frau/Frau in German or Mlle/Mme/Mme in French or Panna/Pani/Pani in Polish. It's impossible to differentiate the title chosen.
https://github.com/django-oscar/django-oscar/blob/1a3372e1728d7b464693da6c78525ef4f13176a1/src/oscar/locale/de/LC_MESSAGES/django.po#L45-L55

One can try it out with different languages in the address book in the sandbox.
I'd propose, instead of searching for direct translations, that could be difficult or awkward to use ("panna" in Polish or "Fräulein" in German for Miss are rather old-fashioned and not being used often), we leave just one term for a woman, hopefully it's sensible and inclusive to all in question.

Hah, that's a fun one.
I am inclined to suggest we go even further and remove the title field from the address forms entirely (we'd have to leave the field in the models in case projects want to use it). I agree with the UK Government Design System advice on this:

Avoid asking users for their title.
It’s extra work for them and you’re asking them to potentially reveal their gender and marital status, which they may not want to do.
It’s also hard to predict the range of titles your users will have. If you have to ask for someone’s title, use an optional text input not a select.

I don't think the title is really a useful/necessary field and a delivery address is perfectly usable without it.

I think you're right. The current choices are also a little limited (for example I'd need also a 'company'), so it's better to remove it entirely.

@solarissmoke May I work on this issue?
Also, I came across this property called salutation:
https://github.com/django-oscar/django-oscar/blob/27fe44a177b52aaa2299767ac7d879d3c130352d/src/oscar/apps/address/abstract_models.py#L319-L326
If title is removed from salutation, it becomes redundant as name property is serving the same purpose:
https://github.com/django-oscar/django-oscar/blob/27fe44a177b52aaa2299767ac7d879d3c130352d/src/oscar/apps/address/abstract_models.py#L328-L330
So, should all references to salutation be removed as well?

@SakshiUppoor yes, please do.
The only change required here is to remove the title from the address forms. We're not modifying the model itself - so that if projects still want to use the title they can. Thus properties such as salutation will also need to remain.