ctrld ignores config file location (--config) on reboot

I want ctrld to keep the config file in its own folder instead of the user folder.
I used this command to achieve this:
sudo ./ctrld start --cd $DID --config /path/to/ctrld/folder/ctrld.toml
It successfully created the file in the desired folder.
However, upon reboot, ctrld still looks for the config file in the user folder instead of the folder designated above.
ctrld ignores the config file that is already in its own folder.
To fix this, I have to do the following:
sudo ./ctrld service status
Service is running

sudo ./ctrld service stop
Feb 13 07:12:28.280 ERR resetDNS failed error="exit status 4" prefix=main
Feb 13 07:12:28.280 ERR could not reset DNS error="exit status 4" iface=en7 prefix=main
Feb 13 07:12:28.280 INF Service stopped prefix=main

sudo ./ctrld service uninstall
Feb 13 07:12:53.111 ERR resetDNS failed error="exit status 4" prefix=main
Feb 13 07:12:53.112 ERR could not reset DNS error="exit status 4" iface=en7 prefix=main
Feb 13 07:12:53.112 INF Service uninstalled prefix=main

I could do the command to repeat the creation of the config file in the desired folder, but it will be ignored by ctrld in the next reboot.
So, I'll use this command until this issue is resolved:
sudo ./ctrld start --cd $DID
loading config file from: /Users/USER/ctrld.toml
Feb 13 07:13:11.799 INF fetching Controld-D configuration mode=cd prefix=main
Feb 13 07:13:12.771 INF generating ctrld config from Controld-D configuration mode=cd prefix=main
Feb 13 07:13:12.775 INF writing config file to: /Users/USER/ctrld.toml mode=cd prefix=main
Feb 13 07:13:12.846 ERR setDNS failed, ips = ["<IP_ADDRESS>"] error="exit status 4" prefix=main
Feb 13 07:13:12.846 ERR could not set DNS for interface error="exit status 4" iface=en7 prefix=main
Feb 13 07:13:12.846 INF Service started prefix=main

Hi @pmcarrion, thanks for reporting.
How do you know the config file was ignored? What does ignore mean:

ctrld did not read the config?
ctrld read the config but the content was overwritten?

Hi @cuonglm,
None of the above, the config file was in the same folder as the ctrld binary, but ctrld kept looking for the config file on the /Users/USER folder instead of the folder specified when using this command:
sudo ./ctrld start --cd $DID --config /path/to/ctrld/folder/ctrld.toml
I rebooted the machine twice to confirm this issue. I was unable to get an Internet connection, and both times I had to do the following:
sudo ./ctrld service status
sudo ./ctrld service stop
sudo ./ctrld service uninstall
sudo ./ctrld start --cd $DID --config /path/to/ctrld/folder/ctrld.toml

Then I stopped/uninstalled the service and deleted the ctrld.toml file from /path/to/ctrld/folder/.
Finally, I reinstalled the service with this command:
sudo ./ctrld start --cd $DID
Since then, ctrld works as expected, reading the config file from its standard location (Users/USER).

@pmcarrion It seems to me that the problem is ctrld does not take --config into account when --cd is specified. To clarify, when you use --cd, ctrld will always fetch the config and overwrite the content of old config file. It does not attempt to use your old config, even though it does read it.
I'm not sure while you don't get the internet connection after rebooting, would you mind taking a look at the log when this happen? (You can do --log /path/to/your/log/file when starting ctrld).

So, instead of using
sudo ./ctrld start --cd $DID
I should use
sudo ./ctrld service start --config /path/to/ctrld/folder/ctrld.toml
What is the default config file if --cd is not used to fetch it?

@pmcarrion Whatever config file you use, ctrld --cd $DID will fetch the resolver config, then overwrite the old config content if the config existed, or writing new one if the config is not existed.
The bug here is ctrld start does not honor the --config file flag, but always find config file in user's home directory. This will be fixed in next release, so when you pass --config, ctrld will write the configuration to specified file.

This issue is resolved in the latest release.


using 'disabled' as a binding name in component causes problems in form in IE 11

A Bug in IE 11, apologies if this has been raised before
If  'disabled' is used as a binding name it causes issues in IE 11.Cant tab, placeholder does not work
The following example shows 3 input buttons, 2 of which are in the parent component form and 1 is in the child component. The first example shows with binding 'disabled'. tab on the input boxes does not work and place holder does not work correctly.
The second example is with binding called 'isdisabled'. Everything works correctly in IE 11
DEMO:
with binding 'disabled' = https://plnkr.co/edit/3KRHdmj7Y93L8qaD9Ziv?p=preview
with binding 'isdisabled' = https://plnkr.co/edit/fQuxhW14TcrkfvqS9Umo?p=preview

This is a IE11 issue. It isn't related to Angular or directive bindings.
The funny behavior happens when using a disabled attribute on a container (regardless if it is related to a binding or not - in fact regardless of Angular). This demo shows the same bug without Angular at all.
While there is not anything we can do to fix this (IE should fix this), you can prefix your attributes with data- or x- to work arounf the issue. Angular denoralizes the attribute names, so it will interpret data-disabled or x-disabled the same as disabled, but IE11 won't act funny on <prefix>-disabled attributes.


[Key Vault] Fix pipeline test resource deployment issues

Description
This aligns Python's KV test resource deployment setup to align more with Java's, since Java has been able to successfully deploy HSMs in test pipelines while Python's consistently fail.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


Improve load performance

Based off work from https://github.com/GoogleCloudPlatform/require-so-slow

defer loading of css-modules-loader-core
defer loading of chokidar

These were our two worst offenders in terms of load time performance impact.

What kind of perf improvements did this yield?

Should have included in the OP:

The flamegraph implied that this was a 50% startup saving, but my quick manual test of the changes only saw a speedup from .27 sec -> .21 sec (~25% speedup).

I wonder if we swapped got out for something simpler like bent would decrease the load time for that?
got ~28kb
bent ~1kb
https://github.com/mikeal/bent

+1, we only use got for our experimental webDependencies support, could be worth checking out.


implement stack-based interpreter to improve performance

currently sval is a tree-walking interpreter and has a ordinary performance. compile the code into some kinds of intermediate representation based on stack to improve performance.
I have a demo as followed. it may be difficult and take some time to migrate.
const { parse } = require('acorn')
const { simple } = require('acorn-walk')

const ast = parse('1 + 8 * 2 / 2 + 1')

const stack = []

simple(ast, {
  Literal(node) {
    stack.push(node.value)
  },
  BinaryExpression(node) {
    const right = stack.pop()
    const left = stack.pop()
    const binaryOps = {
      '+': () => left + right,
      '-': () => left - right,
      '*': () => left * right,
      '/': () => left / right
    }
    const handler = binaryOps[node.operator]
    if (handler) {
      stack.push(handler())
    } else {
      throw new SyntaxError(`Unexpected token ${node.operator}`)
    }
  }
})

console.log(stack[0])

I just found an available register-based js vm, continuum. it did a great work, but unbelievable, its performance is even worse than sval. it makes me reconsider the performance of stack-based interperter written in js.
test case:
<!DOCTYPE html>
<html>
<body>
  <script src="https://unpkg.com/sval"></script>
  <script<EMAIL_ADDRESS>  <script>
    const code = 'for(var i=0;i<100000;i++){}'
    for (let i = 0; i < 5; i++) {
      const interpreter = new Sval()
      console.time(`sval      ${i + 1}`)
      interpreter.run(code)
      console.timeEnd(`sval      ${i + 1}`)
      const realm = continuum.createRealm()
      console.time(`continuum ${i + 1}`)
      realm.evaluate(code)
      console.timeEnd(`continuum ${i + 1}`)
      console.log('')
    }
  </script>
</body>
</html>

result in chrome:
sval      1:<PHONE_NUMBER>6875ms
continuum 1: 1341.805908203125ms

sval      2: 83.824951171875ms
continuum 2: 1551.010986328125ms

sval      3: 79.5869140625ms
continuum 3: 1698.853759765625ms

sval      4: 82.9951171875ms
continuum 4: 1470.83984375ms

sval      5: 83.164794921875ms
continuum 5: 1300.2099609375ms

I don't think it's a good idea to create a VM with javascript. It just emits more code, needs more allocations and results in more GC.
Sval is great and easy.  Firstly, we should try regular optimization ways such as cache critical paths, instead of rewriting the whole solution.
Take below case for example, it takes about 145ms on my Chrome 74.:
    const interpreter = new Sval();

    interpreter.run(`
    var x = 0;
    function functionOne() {
      x++;
    }

    var iterations = 100000;
    console.time('Function #1');
    for(var i = 0; i < iterations; i++ ){
      functionOne()
    };
    console.timeEnd('Function #1')

    console.log(x);
    `);

When optimizing with inline function, the time cost cuts down half to 75ms, one time faster!
  const interpreter = new Sval();

    interpreter.run(`
    var x = 0;
    function functionOne() {
      x++;
    }

    var iterations = 100000;
    console.time('Function #1');
    for(var i = 0; i < iterations; i++ ){
      functionOne()
    };
    console.timeEnd('Function #1')

    console.log(x);
    `);

agree. I will think it over.
actually I don't mean to implement an entire vm. just to flatten the ast by compiling into ir, in order to decrease the performance reduction caused by maintaining scopes.

Top cost of the above for loop test case:

check property exists on object

get and set property to obj

get property from object

set property and create object

the updater cost a lot

get property from object

5/6 are about property setter/setter, it seems V8 doesn't have good property accessing performance,  it should be faster, right?  Let's take a look at below test case:
Accessing property with  String key vs. number key:
const map = {};

const strKeys = new Array(100000);
const numKeys = new Array(100000);

for(var i=0; i< 100000; i++) {
  var key = 'Key' + i;
  strKeys[i] = key;
  numKeys[i] = i;
  map[key] = i;
  map[i] = i;
}

console.time('StrKey Lookup #1');

for(var i=0; i< 100000; i++) {
  var key = strKeys[i];
  var v = map[key];
  v = v + 1;
}
console.timeEnd('StrKey Lookup #1');

console.time('NumKey Lookup #1');

for(var i=0; i< 100000; i++) {
  var key = numKeys[i];
  var v = map[key];
  v = v + 1;
}
console.timeEnd('NumKey Lookup #1');

And here's the test result:

Surprise? Of course not, V8 blog gives us the explanation: named properties and indexed elements are different in V8.

cool
linear int keys allow us to malloc a linear continuous mem to store, and we can access the item by offsetting the pointer. but string keys need a hashtable to store the relationship between keys and indexes, in order to access the mem block by indexes to get the item. that's why int keys have a better performance.
so, to store a dict, we need a hashtable and an array actually. if we store the data in a array, we still need a map/hashtable/object to maintain the mapping relationship between keys and indexes, which takes the same time as we directly store at a object. to avoid this problem and just use a array to store data, we need a stack-based interpreter instead of register-based or tree-walking interpreter.
as you say, the predefinition of dynamic property has a similar meaning of hoisting variable and function. I am working on it now.

fengari did a great job of running lua over js. mark for reference - Fengari
<script src="./fengari-web.js"></script>
<script type="application/lua">
  local start = os.time()
  for i=1, 10000000 do
  end
  print(os.time() - start) -- 0~1s cool :)
</script>
<script src="https://unpkg.com/sval"></script>
<script>
  const interpreter = new Sval()
  interpreter.run(`
    var start = Date.now()
    for (var i = 0; i < 10000000; i++) {}
    console.log((Date.now() - start) / 1000) // around 6s :(
  `)
</script>

currently a stack-based interpreter has been roughly accomplished. a brenchmark demo can be found in #3b660d4, and the interpreter has a great performance promotion lol.
const interpreter = new Sval()
interpreter.run(`
  var start = Date.now()
  for (var i = 0; i < 10000000; i++) {}
  console.log((Date.now() - start) / 1000) // 3.45s now :D
`)

When will this performance improvements reach master branch?

When will this performance improvements reach master branch? Any ETA? I'm looking into moving from Interpreter-JS to Sval.
PD: Quite a nice job.

I will try to complete in August

Hi :) sorry for the double post, I would love to use Sval too! Do you confirm end of August as a possible release date for the performance improvements? :)
Thank you and great job!!!

Hi :) sorry for the double post, I would love to use Sval too! Do you confirm end of August as a possible release date for the performance improvements? :)
Thank you and great job!!!

Nope. I don't have time to handle it this month, and I'm not sure when I can finish. :(

That's fine anyway, thank you! :) Looking forward to seeing it completed!

currently a stack-based interpreter has been roughly accomplished. a brenchmark demo can be found in #3b660d4, and the interpreter has a great performance promotion lol.
const interpreter = new Sval()
interpreter.run(`
  var start = Date.now()
  for (var i = 0; i < 10000000; i++) {}
  console.log((Date.now() - start) / 1000) // 3.45s now :D
`)

Nice job. Is there a lot left to finish it?

Any update? What's left to do? :)


Adding tab view for config vs CLI based arguments in tutorials

Currently our tutorial have the explanation of configuration file in tutorials where the option of a.) editing the config file to update parameters  and b.) passing arguments via CLI both are merged with each other. This breaks the flow of following the steps to replicate the results.
What we have so far:
An example see the snapshot attached from here:

What would be useful:
It would be nice to have some way to keep the steps for both the available options yet keeping them separate from each other. I looked and it seems Sphinx Tabs could serve our purpose.
What is the solution:
I tested two versions that could look good and it would be nice to discuss if we can adopt them for all tutorials. For example purpose, I will show the design of 'Uncertainty Estimation' tutorial. All tabs are clickable!
Version 1
Explaining the parameters that need to be edited in config file in a text editor first

and then one whole tab section (each for editing config file and via CLI) for other parameters, where tab 1 can be for editing config file

and tab 2 can be for arguments via CLI

Version 2
Keeping the same sequence of arguments explained in current tutorial and make tabs where there exist two options (i.e. both with config edit file and via CLI) as shown below:

while the other half have to manually toggle multiple times to see the other Approach's content.

To fix this problem, what about Version 2, but using the Group tabs feature to synchronize the choice between tabs?

That's a good suggestion @joshuacwnewton . It we do this, it will also help follow steps in the other they appear in config file : e.g. train and then data path and then output path etc.

From out meeting, we want to minimise usage of CLI, therefore we’re gonna get rid of CLI syntax in the tutorials, and once #941  is implemented we can add a single usage page before the tutorials to instruct that everything can also be done via CLI.

and once #941 is implemented we can add a single usage page before the tutorials to instruct that everything can also be done via CLI.

can you pls open an issue on that @copperwiring

Fully resolved in PR1039 and other upcoming PRs that revamp the tutorials with improved tab organization.


uninitialized constant Tumblr

Here is my error:
build.rb:5:in `<main>': uninitialized constant Tumblr (NameError)

Here is the file I am using:
require 'rubygems'
require 'bundler/setup'

# Authenticate via OAuth
client = Tumblr::Client.new({
  :consumer_key => 'xxx',
  :consumer_secret => 'xxx',
  :oauth_token => 'xxx',
  :oauth_token_secret => 'xxx'
})

binding.pry

# Make the request
client.info

The xxx are replaced with values from Tumblr, and this is a straight ruby app.
Thoughts?

Ok, I fixed that first error by adding:
require 'tumblr/client'

but now I am getting:
/Users/chrishough/GrokTrunkLive/NoConformity/OpenSourceSoftware/my-projects/archive-tumblr/.bundle/ruby/2.2.0/gems/tumblr_client-0.8.5/lib/tumblr/client.rb:27:in `initialize': undefined method `options' for Tumblr:Module (NoMethodError)
	from build.rb:6:in `new'
	from build.rb:6:in `<main>'

Fixed this issue with the following, meant to post this late last night:
require 'rubygems'
require 'pry'
require 'tumblr_client'

hacked acct

@cathleen5 confused?

@chrishough For future reference, you don't need the require 'rubygems'. It's actually not even a valid gem in the standard rubygems.org source. (Unless you've got another gem from elsewhere named rubygems, in which case ignore me.)

@ceykooo thanks :+1:


cwtv not working for "Pen & Teller Fool Us"

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

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

Checklist

[X] I'm reporting a broken site
[X] I've verified that I'm running yt-dlp version 2023.01.06 (update instructions) or later (specify commit)
[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 the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
US
Provide a description that is worded well enough to be understood
I tried downloading from cwtv which works perfectly from Firefox and other browsers but I can't get it to download with yt-dlp.
I am accessing the site via US site via vpn from Switzerland which works well in the browsers but I thought I mention it.
Thank you very much for your amazing work! Let me know if I can do anything else or anything else is needed.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', 'https://www.cwtv.com/shows/penn-teller-fool-us/that-bleeping-teller/?play=e10d4841-1db3-4750-8eca-c4b84be0ccff']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2023.01.06 [6becd25] (zip)
[debug] Python 3.10.8 (CPython x86_64 64bit) - Linux-5.15.0-57-generic-x86_64-with-glibc2.35 (OpenSSL 1.1.1s  1 Nov 2022, glibc 2.35)
[debug] exe versions: ffmpeg 5.1.2 (setts), ffprobe 5.1.2, rtmpdump 2.4
[debug] Optional libraries: Crypto-3.15.0, sqlite3-2.6.0
[debug] Proxy map: {}
[debug] Loaded 1760 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: 2023.01.06, Current version: 2023.01.06
yt-dlp is up to date (2023.01.06)
[CWTV] Extracting URL: https://www.cwtv.com/shows/penn-teller-fool-us/that-bleeping-teller/?play=e10d4841-1db3-4750-8eca-c4b84be0ccff
[CWTV] e10d4841-1db3-4750-8eca-c4b84be0ccff: Downloading JSON metadata
[ThePlatform] Extracting URL: http://link.theplatform.com/s/cwtv/media/guid/2703454149/e10d4841-1db3-4750-8eca-c4b84be0ccff?format=SMIL&formats=M3U&tracking=true&mbr=false#__youtubedl_smuggle=%7B%22force_smil_url%22%3A+true%7D
[ThePlatform] e10d4841-1db3-4750-8eca-c4b84be0ccff: Downloading SMIL data
ERROR: [ThePlatform] e10d4841-1db3-4750-8eca-c4b84be0ccff: Unable to download XML: Remote end closed connection without response (caused by RemoteDisconnected('Remote end closed connection without response')); please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
  File "/home/dom/.local/bin/yt-dlp/yt_dlp/extractor/common.py", line 680, in extract
    ie_result = self._real_extract(url)
  File "/home/dom/.local/bin/yt-dlp/yt_dlp/extractor/theplatform.py", line 298, in _real_extract
    formats, subtitles = self._extract_theplatform_smil(smil_url, video_id)
  File "/home/dom/.local/bin/yt-dlp/yt_dlp/extractor/theplatform.py", line 32, in _extract_theplatform_smil
    meta = self._download_xml(
  File "/home/dom/.local/bin/yt-dlp/yt_dlp/extractor/common.py", line 1034, in download_content
    res = getattr(self, download_handle.__name__)(url_or_request, video_id, **kwargs)
  File "/home/dom/.local/bin/yt-dlp/yt_dlp/extractor/common.py", line 998, in download_handle
    res = self._download_webpage_handle(
  File "/home/dom/.local/bin/yt-dlp/yt_dlp/extractor/adobepass.py", line 1366, in _download_webpage_handle
    return super(AdobePassIE, self)._download_webpage_handle(
  File "/home/dom/.local/bin/yt-dlp/yt_dlp/extractor/common.py", line 868, in _download_webpage_handle
    urlh = self._request_webpage(url_or_request, video_id, note, errnote, fatal, data=data, headers=headers, query=query, expected_status=expected_status)
  File "/home/dom/.local/bin/yt-dlp/yt_dlp/extractor/common.py", line 825, in _request_webpage
    raise ExtractorError(errmsg, cause=err)

  File "/home/dom/.local/bin/yt-dlp/yt_dlp/extractor/common.py", line 807, in _request_webpage
    return self._downloader.urlopen(self._create_request(url_or_request, data, headers, query))
  File "/home/dom/.local/bin/yt-dlp/yt_dlp/YoutubeDL.py", line 3730, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File<EMAIL_ADDRESS>line 519, in open
    response = self._open(req, data)
  File<EMAIL_ADDRESS>line 536, in _open
    result = self._call_chain(self.handle_open, protocol, protocol +
  File<EMAIL_ADDRESS>line 496, in _call_chain
    result = func(*args)
  File "/home/dom/.local/bin/yt-dlp/yt_dlp/utils.py", line 1371, in http_open
    return self.do_open(functools.partial(
  File<EMAIL_ADDRESS>line 1352, in do_open
    r = h.getresponse()
  File<EMAIL_ADDRESS>line 1374, in getresponse
    response.begin()
  File<EMAIL_ADDRESS>line 318, in begin
    version, status, reason = self._read_status()
  File<EMAIL_ADDRESS>line 287, in _read_status
    raise RemoteDisconnected("Remote end closed connection without"
http.client.RemoteDisconnected: Remote end closed connection without response

it works from US
[CWTV] Extracting URL: https://www.cwtv.com/shows/penn-teller-fool-us/that-bleeping-teller/?play=e10d4841-1db3-4750-8eca-c4b84be0ccff
[CWTV] e10d4841-1db3-4750-8eca-c4b84be0ccff: Downloading JSON metadata
[ThePlatform] Extracting URL: http://link.theplatform.com/s/cwtv/media/guid/2703454149/e10d4841-1db3-4750-8eca-c4b84be0ccff?format=SMIL&formats=M3U&tracking=true&mbr=false#__youtubedl_smuggle=%7B%22force_smil_url%22%3A+true%7D
[ThePlatform] e10d4841-1db3-4750-8eca-c4b84be0ccff: Downloading SMIL data
[ThePlatform] e10d4841-1db3-4750-8eca-c4b84be0ccff: Downloading m3u8 information
WARNING: [ThePlatform] Ignoring subtitle tracks found in the HLS manifest; if any subtitle tracks are missing, please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
[ThePlatform] e10d4841-1db3-4750-8eca-c4b84be0ccff: Downloading m3u8 information
[ThePlatform] e10d4841-1db3-4750-8eca-c4b84be0ccff: Downloading JSON metadata
[debug] Formats sorted by: hasvid, ie_pref, lang, quality, res, fps, hdr:12(7), vcodec:vp9.2(10), channels, acodec, filesize, fs_approx, tbr, vbr, abr, asr, proto, vext, aext, hasaud, source, id
[debug] Default format spec: bestvideo*+bestaudio/best
[info] e10d4841-1db3-4750-8eca-c4b84be0ccff: Downloading 1 format(s): hls-8333-3
[debug] Invoking hlsnative downloader on "https://stream-hls.cwtv.com/nosec/The_CW/155/853/155854917765/PennAndTeller-907-ThatBleepingTeller-P907-CW-SWAP1_155856453715_m3u8_video_1920x1080_8000000_primary_audio_eng_x32ad666491364cb6b727213f4ed7d47a_8.m3u8"
[hlsnative] Downloading m3u8 manifest
[hlsnative] Total fragments: 420
[download] Destination: 20221203_Sat_11_00_00_CWTV_e10d4841-1db3-4750-8eca-c4b84be0ccff_That_Bleeping_Teller.mp4
[download]   1.5% of ~   2.42GiB at    1.36MiB/s ETA 04:29 (frag 6/420)^C
ERROR: Interrupted by user

OK, thank you very much. Closing this.

@leancode maybe try passing --force-ipv4 ?


Will not play videos with most recent nightly (as of date of filing this)

I'm submitting a ...

[x] bug report
[ ] feature request
[ ] support request

General infomration
Older alpha (25/08/2018) works fine with 13.13 or 13.12, alpha from 19/09/2018 fails for netflix playback.
Youtube playback works fine.
Prerequisites

[x] Are you running the latest version?

Description
[Description of the bug or feature]
Steps to Reproduce
Play a video.
Actual behavior: [What actually happened]
Video timeline appears and progresses, but no video plays.
Context (Environment)
Win10 x64 1803
19/09/2018 kodi nightly
addon 13.13
Installation

[ ] I installed the plugin via zip from the Releases page
[ ] I´m using the Netflix Repo
[ ] I´m using a different source (Please tell which)

Operating System

[ ] Linux (x86/x64)
[ ] OSX (x86/x64)
[x] Windows (x86/x64)
[ ] Linux (ARM)
[ ] Android

Debug log
[Please include a link to your debug log (use something like http://sprunge.us/) or similar, please do not paste]
Other information
[e.g. detailed explanation, related issues, suggestions how to fix, links for us to have context, etc.]
Screenshots
[Please add a screenshot if that helps understanding your problem]
[You can erase any parts of this template not applicable to your Issue.]

Nothing we can do without a complete debug log.

You could install a nightly yourself.

Are you on Win x64 or linux?

I'm on Win10 x64, latest nightly. As I said, everything works fine on my end, so in order to help you I'll need a full debug log please.


AZ SQL not available as DataDestination?

[Hi-- I'm wondering why Azure SQL is not accepted as a Data Destination Source Type in this template? Would love to use the template for my team, but would need Azure SQL as the destination. Happy to do it by hand as well. Just thought I'd request in case others can leverage out-of-the-box.
keep up the good work!
Thanks,
r33d]

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

ID: b9f1c9ba-1c89-1ad0-32e6-71e1d0ec2b5f
Version Independent ID: 8d6f931c-49d3-52aa-9f47-463f0fbca0f1
Content: Delta copy from a database using a control table - Azure Data Factory
Content Source: articles/data-factory/solution-template-delta-copy-with-control-table.md
Service: data-factory
Sub-service: tutorials
GitHub Login: @dearandyxu
Microsoft Alias: yexu

@r33dz  Thanks for the question! We are investigating and will update you shortly.

Hi @r33dz ,
I tried to use my linked service pointing to Azure SQL database as the Source dataset in 'Delta copy from a database' template and it's working for me. Here is the detailed video :

If you have any further query on the implementation part,  I would recommend you to create a thread on the forums - Microsoft Q&A or Stack Overflow
Once you post your issue on forums, it will have visibility across the community which is a better suited audience for such types of issues.
As it doesn't seem to be a document feedback or document bug , I am closing this issue here. Please feel free to post further query related to the implementation part on the above mentioned platforms.

Hi @AnnuKumari-MSFT : The request is for Azure SQL DB as destination, not source as you show in your example. I am happy to try another forum, although I suppose the request is to update the template.
Thanks,
-Reed

Hi @r33dz ,
Templates are pre-defined pipelines which has some set of codes which can be re-used and customized according to the need and requirements. So, if your requirement is to have Azure SQL as sink datastore, you can easily create a new dataset pointing to Azure SQL table and use that in the Sink setting.
If you particularly want to have this feature in the template, I would recommend you to share the feedback on our Data factory feedback channel, which would be open for the user community to upvote & comment on. This allows our product team to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.
Lastly, as it doesn't seem to be a document feedback or document bug , I am closing this issue here. Please feel free to post further query related to the implementation part on the above mentioned platforms. Thankyou !


[Service Bus] ClaimCheck failing in nightly runs

Service Bus nightly test runs are failing with:

Error message
Azure.RequestFailedException : The value for one of the HTTP headers is not in the correct format.
RequestId:ca74310c-901e-00e0-16eb-7b75b8000000
Time:2022-06-09T10:29:58.0456994Z
Status: 400 (The value for one of the HTTP headers is not in the correct format.)
ErrorCode: InvalidHeaderValue
Additional Information:
HeaderName: x-ms-version
HeaderValue: 2021-08-06
Content:
InvalidHeaderValueThe value for one of the HTTP headers is not in the correct format.
RequestId:ca74310c-901e-00e0-16eb-7b75b8000000
Time:2022-06-09T10:29:58.0456994Zx-ms-version2021-08-06
Headers:
x-ms-request-id: ca74310c-901e-00e0-16eb-7b75b8000000
Content-Length: 329
Content-Type: application/xml
Date: Thu, 09 Jun 2022 10:29:57 GMT
Server: Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
Data:
HeaderName: x-ms-version
HeaderValue: 2021-08-06
Stack trace
at Azure.Storage.Blobs.ContainerRestClient.d__8.MoveNext() in D:\a_work\1\s\sdk\storage\Azure.Storage.Blobs\src\Generated\ContainerRestClient.cs:line 94
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1.ConfiguredTaskAwaiter.GetResult()    at Azure.Storage.Blobs.BlobContainerClient.<CreateInternal>d__53.MoveNext() in D:\a\_work\1\s\sdk\storage\Azure.Storage.Blobs\src\BlobContainerClient.cs:line 1192 --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1.ConfiguredTaskAwaiter.GetResult()
at Azure.Storage.Blobs.BlobContainerClient.d__52.MoveNext() in D:\a_work\1\s\sdk\storage\Azure.Storage.Blobs\src\BlobContainerClient.cs:line 1082
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1.ConfiguredTaskAwaiter.GetResult()    at Azure.Storage.Blobs.BlobContainerClient.<CreateIfNotExistsAsync>d__50.MoveNext() in D:\a\_work\1\s\sdk\storage\Azure.Storage.Blobs\src\BlobContainerClient.cs:line 938 --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()
at Azure.Messaging.ServiceBus.Tests.Samples.Sample10_ClaimCheck.d__0.MoveNext() in D:\a_work\1\s\sdk\servicebus\Azure.Messaging.ServiceBus\tests\Samples\Sample10_ClaimCheck.cs:line 25
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Azure.Messaging.ServiceBus.Tests.Samples.Sample10_ClaimCheck.d__0.MoveNext() in D:\a_work\1\s\sdk\servicebus\Azure.Messaging.ServiceBus\tests\Samples\Sample10_ClaimCheck.cs:line 87
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()    at NUnit.Framework.Internal.TaskAwaitAdapter.GenericAdapter1.BlockUntilCompleted()
at NUnit.Framework.Internal.MessagePumpStrategy.NoMessagePumpStrategy.WaitForCompletion(AwaitAdapter awaiter)
at NUnit.Framework.Internal.AsyncToSyncAdapter.Await(Func1 invoke)    at NUnit.Framework.Internal.Commands.TestMethodCommand.RunTestMethod(TestExecutionContext context)    at NUnit.Framework.Internal.Commands.TestMethodCommand.Execute(TestExecutionContext context)    at NUnit.Framework.Internal.Execution.SimpleWorkItem.<>c__DisplayClass4_0.<PerformWork>b__0()    at NUnit.Framework.Internal.ContextUtils.<>c__DisplayClass1_01.b__0(Object _)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

For more details check here:

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1630399&view=results

@jsquire for notification.

Seems to be related to the new service version for Storage that is not yet rolled out to all regions. This error should resolve itself once the service rolls out to all regions.

This is no longer occuring.


slack notifications

Description
Users designated as "Lead" are not tagged and notified in slack.
Related https://github.com/HyphaApp/hypha/pull/3433

@fourthletter Please specify the specific notification this is happening on. Pasting in the text works, we can use that to find it in the code base.

Also make sure the user in question have set a slack name in the user account.


Rust SDK

It would be great to have Rust SDK in order to create very high-performant yet safe pipelines.
Imported from Jira BEAM-12658. Original Jira may contain additional context.
Reported by: .

Thanks @bvolpato for pointing me to this https://github.com/apache/beam/issues/21089
This would be extremely useful for us at Discord. We use Rust heavily and we are using Beam (using python) for data processing. To reduce training serving skew this would be very beneficial.

Contributions welcome!  Do advise if need some resources to get started.  And, a related talk:  https://www.youtube.com/watch?v=VsGQ2LFeTHY

Hi, I would like to express interest in working on the Rust SDK, and I have begun drafting a possible design doc which I intend to share in the mailing list in the next few days. I will also create an incubator fork soon.

.take-issue

Great!  Will be happy to help, collab, and pull in those needed along the way.  Feel free to reachout to<EMAIL_ADDRESS>for collaboration via email

Work is underway here. Progress may be slow, and early code will look quite rough. I'll be really happy to receive any feedback or collaboration opportunities.

@nivaldoh iv been looking for a reason to learn rust. Happy to take on any house keeping work that will slow you down

@dofinn I really appreciate the offer. Currently we have a few TODOs with improvement ideas which I'd be happy to describe in more detail, and we could also try to coordinate effort on the larger tasks as well (which I'm also planning to organize in the main README file) if you're interested. Feel free to open a PR directly in the fork or reach out to me by email<EMAIL_ADDRESS>if you'd like.

@nivaldoh thanks for doing this!

@esadler-hbo thanks for the support!
There's still a lot of work to be done, and I try to keep an updated roadmap here if you or anyone else is interested in a quick overview of the current state of the implementation.
In particular, the user API is starting to take shape, and the snippet below (inspired by the new patterns set by the Typescript SDK) is now functional end-to-end:
let runner = DirectRunner::new();

// Impulse won't be exposed to the user, but it serves as a mock transform for now
let transform = Impulse::new();

runner.run(|root| root.apply(transform)).await;

To anyone interested, any early input on this format would be highly appreciated, as this is the current foundation that I'll be using for everything else. Any other contributions (including early code reviews, even if partial) would be awesome as well.

I also like to help! I have some experience with Rust but am pretty new to Beam or large-scale data processing framework

@nivaldoh I think reading the doc will only get me so far and I should probably start working on some implementation and see how it goes. Is there any coder/transform or other stuff you want my help with?

I just saw this, there's actually an effort to build a Rust SDK this week from the Dataflow team. What we have is at https://github.com/kennknowles/beam/tree/rust/sdks/rust ; it would be great to combine efforts.

@robertwb and @kennknowles -- I'm glad you're looking into this.  I have advised Nivaldo on strategies, with an eye on getting this to be something useful enough to warrant being merged into the proper project as another sdk.  Your experience/knowledge attending to this will go a long way!
Maybe you two can dig a little into https://github.com/nivaldoh/beam/tree/rust_sdk and @nivaldoh can look at https://github.com/kennknowles/beam/tree/rust/sdks/rust -- suggesting that we wind only working on one or the other.
I wonder if it'd be easier to keep @kennknowles 's eyes on progress if developed in his repo?  But, if the other is much further along might it better to jump into that [ @nivaldoh -- I assume you can give @kennknowles , @robertwb , and others relevant merge/commit permissions in your repo -- in things Beam they know their stuff and should absolutely be trusted ].  Else, it might then depend on the merge/migration path to get relevant bits into https://github.com/kennknowles/beam/tree/rust/sdks/rust, which I also imagine @nivaldoh might be open to taking on, as that could help solidify understandings, implementation.
I'll try to have a look to compare the repos over the weekend or sometime next week.
@nivaldoh - please advise on your thoughts/inclinations [ I've been sorta speaking for you, based on my read of you, motivation, inclinations when we've connected ]

IMHO, @nivaldoh's repo is further along, and better structured, so I think it makes sense to start there. In the next day or two we'll probably be pushing willy-nilly to the one at kennknowles, in the spirit of the hackathon to explore ideas, but next week I suggest we start creating pull requests to https://github.com/nivaldoh/beam/tree/rust_sdk to carry anything over that has value (and isn't already in the latter) and continue there.

Sounds like a plan!

@TommyCpp Besides some of the smaller TODOs spread out around the codebase, adding new coders such as DoubleCoder (mirroring from the Typescript SDK) could be a great way option since their structure is a bit more organized at the moment and they can be reliably tested in isolation. However, considering the current discussions, the Dataflow is going to implement a lot of things over the weekend and likely introduce different approaches, so it might be better to wait until then.
@brucearctor I agree with all your points. Additionally, @robertwb and @kennknowles need no introduction for me, so I've already sent both of them invites for collaborator access on my repo. What I really intend is to grant them owner permissions but I'm not completely familiar with this sort of thing on GitHub, so please let me know if any access is still missing after this (as well as anyone else who might require access).
I'm quite happy that we might be able to use what I've done so far as the base repo for the initial stages of the Rust SDK, but if it turns out to be a better idea to move the code there into https://github.com/kennknowles/beam/tree/rust/sdks/rust instead as @brucearctor mentioned, I'd be more than happy to make any adaptations necessary so that we may continue from there.
I'll also keep an eye on the progress there over the weekend to see if there's anything that could be changed in advance inside my repo. There are plenty of minor (such as the current module structure forcing me to import certain libraries in more than one Cargo file) and not so minor (such as downcasting coders from Any and using their literal TypeId as a key) things that need to be restructured soon over here, so I'll be looking for ideas to improve them and speed up the merge as well.
On a random bonus note, my work vacation starts soon, so progress should start moving a lot faster and I'll also be able to dedicate more time here for further collaboration.

@nivaldoh As promised on the dev thread I've just opened a PR at https://github.com/nivaldoh/beam/pull/20 with some worker code changes as well as a container and boot script based on the existing SDK containers.
I assumed that Rust pipelines would typically be statically compiled like Go pipelines, so the boot script only looks for a single artifact file at the moment. The binaries must match between the launcher and worker if we were to use serde_traitobject to serialize the DoFns, I've got some additional changes coming up to provide some scaffolding for that.
The user binary needs to be able to switch between pipeline construction and pipeline execution mode, so there's an init function much like the Go SDK requires to run soon after the binary is started. That init function needs to be in a different place, but that would require restructuring the crates a bit I think. Happy to sync on that at some point, I think most of the framework code could live in an apache-beam crate and optional features could live in separate crates e.g. apache-beam-io-gcp/aws/azure.
The worker code I had started on uses a concurrent cache, such that we don't need to lock on the worker to interact with the caches and such that we can expire entries in the cache like the Java SDK does.
Looking forward to continue working on this with you!

@sjvanrossum Thanks a lot, the PR is now merged.
I had other issues with the current module/crate structure as I mentioned in my previous comment, and with the point you brought up about the binaries I think this is a good time to change that. I think the crate structure you proposed makes a lot of sense, so that's what I'll be aiming for.
I'll start looking into this in a more general manner to join all current modules into a single crate, but please let me know if this would disrupt or heavily overlap with the upcoming changes you mentioned.
Looking forward to continue working with you as well!

I'm interested in helping, I'm still new to Rust, but I'm already making my first contributions to the java SDK, and I wanted to do the same in Go, but seeing that you're getting started in Rust I'd like to join you.

I'm also interested in using and contributing to https://github.com/nivaldoh/beam/tree/rust_sdk/sdks/rust.
I am the author of SpringQL, an in-memory and single-node streame processor mainly for IoT devices.
I'd like to support Beam as a programming model for newer versoin of SpringQL.
I will try to integrate the https://github.com/nivaldoh/beam/tree/rust_sdk/sdks/rust with our SpringQL and make some necessary changes to both repository.

@laysakura -- thanks for keeping this moving!

@nivaldoh - thanks for getting it started, and please continue to collaborate as makes sense

I'm interested in helping. I have some experience with Rust and the Beam Python SDK, along with previous experience with big data frameworks like Spark and Scalding.
It would be awesome with guidance as to how/where to get started contributing 🤔  Should one just grep for TODOs in the fork by @laysakura and submit prs for review? Or maintain one's own fork and submit prs to the fork by @nivaldoh?

@dahlbaek -- officially your questions are outside the scope of Beam project governance, since happening outside of the organization/official-repos.
To try to help keep things moving --> based on recent lack of activity from @nivaldoh , it seems more likely development to occur with @laysakura .  Probably TODOs there, and/or maybe @laysakura will add some GH Issues or have other suggestions for concrete things that are bite-size enough for individuals to take on.  In general, I believe the SDK will come together, so I would also imagine there is no shortage of things that could be accomplished around improved testing, automation, etc [ not to mention bug work, feature development, and more ].  I imagine PRs would be welcome by @laysakura ... but there could always be conversations in issues in https://github.com/laysakura/beam/tree/rust_sdk ...
All:  I'm far from much of a Rust developer, but am happy to do what I can to ensure smooth collaboration and that we can eventually get this merged and as a proper Beam Rust SDK!

I'm happy to receive help from @dahlbaek. I'll start the conversation on https://github.com/laysakura/beam/issues/1.
@brucearctor, I appreciate your assistance. We will report our progress here. I also hope to collaborate with @nivaldoh again. If @nivaldoh becomes interested in Rust SDK again, I would be happy if you contacted me.

Desafortunadamente, parece que@nivaldohEl repositorio de está inactivo desde el 1 de febrero de 2023. Hay 5 solicitudes de incorporación de cambios que no se han revisado ni fusionado.

Para solucionar este problema, he creado una bifurcación del repositorio. En mi tenedor, tengo:

fusión manual de una rama de tema de @robertwb
(wip) dejó de usar Anyy, en su lugar, usó genéricos para los parámetros de entrada y salida de PTransform
hizo muchas otras refactorizaciones para hacer que el código fuera más parecido a Rust

Doy la bienvenida a cualquier contribución a este repositorio.

Ok, I understand that it is all new from the main project no? there is nothing from @nivaldoh's branch ?

@Miuler

Ok, I understand that it is all new from the main project no? there is nothing from @nivaldoh's branch ?

laysakura/beam's rust_sdk branch is a fork from nivaldoh/beam's rust_sdk.
It manually merged the following PRs created in nivaldoh/beam.

https://github.com/nivaldoh/beam/pull/22
https://github.com/nivaldoh/beam/pull/23
https://github.com/nivaldoh/beam/pull/25
https://github.com/nivaldoh/beam/pull/26

I'm sorry for not merging your https://github.com/nivaldoh/beam/pull/24 because https://github.com/nivaldoh/beam/pull/25 might make FIXMEs in https://github.com/nivaldoh/beam/pull/24 unnecessary (also described in https://github.com/nivaldoh/beam/pull/25).
You may check the git history in laysakura/beam by yourself.

What is the most fluid conversation channel? Telegram? matrix/element? discord? slack?

https://github.com/laysakura/beam/issues/1 is.

Thank you @laysakura for rebooting this effort!

@robertwb Thank you for creating the basic mechanisms of Beam, such as ParDo and GBK.
@dahlbaek and I are now working on creating a more Rust-like, statically-typed pipeline based on your work. We would also appreciate your contribution to laysakura/beam based on your extensive experience with the TypeScript SDK.

Oh, I seem to have missed some traffic on this issue. I received collaborator access to @nivaldoh's fork yesterday, but I'll move development over to @laysakura's fork. :)
I've got some work in progress for data channels on DataSource and DataSink and I'm currently drafting a change to serialization as mentioned on https://github.com/nivaldoh/beam/pull/22.

@sjvanrossum Thank you so much! I sent an invitation to add you as a collaborator of laysakura/beam.

I think it would be helpful to create design documents in order to align our goals and understanding. To start, I have written an initial version of a document titled "Custom Coders for the Beam Rust SDK".
A portion of the proposal outlined in the document has already been implemented and tested, as can be seen here: https://github.com/laysakura/beam/pull/30/.
I would especially appreciate it if @sjvanrossum and @dahlbaek, who have recently collaborated with me on the laysakura/beam repository, could take a look and provide any comments or suggestions.
Of course, I welcome feedback from anyone.

@laysakura and all:  a little note to see whether interest has dwindled, or just other priorities, etc.  It seems this had been taking shape and would be great to eventually get it in a state where we can get this merged into Beam.

@brucearctor For me, I still has interests but cannot prioritize Beam-related work in my company for a while 😞
It would be great if others lead the Rust SDK's development.

@brucearctor For me, I still has interests but cannot prioritize Beam-related work in my company for a while 😞 It would be great if others lead the Rust SDK's development.

Makes sense -- our abilities to devote work time to various efforts does change over time.
Sounds like a call for Any/All that are interested to consider stepping in and helping/contribute!

From my side I'm still interested in contributing, but I do it on my own time, and haven't had much to spare lately.

From my side I'm still interested in contributing, but I do it on my own time, and haven't had much to spare lately.

@dahlbaek :  Totally understandable, and one of the nice things about Open Source!

@brucearctor I've had Coder/DoFn serialization and authoring functionality that I've been working on "on again and off again" and I would be happy to support contributors if they wish to contribute PRs (not sure if my remote branch is fully up to date, but I'll take a peek). My situation matches that of the other contributors, I've unfortunately had to prioritize my core role over this for the past few months.

Just found this --> https://github.com/swiftdiaries/beam-rust hadn't dug deep, unclear whether much is usable.

Seems like it didn't progress beyond "Hello, world!" unfortunately.


Add support for early/late mixins

Right now the build script doesn't have support for early/late mixins, forcing mods that use it (such as Hodgepodge and NotFine) to use a custom gitignore with this line removed:
https://github.com/GTNewHorizons/ExampleMod1.7.10/blob/c861c6b0486ca5dfd228e2f62c76e88b0dea47b4/.gitignore#L29

This should be updated to only exclude the autogenerated mixins.blah.json; and not the (currently not autogenerated) mixin.blah.(early|late).json.  Or updated to also generate the early/late.json if they're missing.  🤔

Maybe the autogenerated configs could reside in a different temp directory, which would be added as an extra dir to sourceSets.main.resources.srcDirs. That would remove the need to gitignore anything from src.

RFG provides a injectedTags sourceset in the build folder for generating the class with mod version/id/etc., which could also be used for adding resources to the built jar without putting them in the main source folders


Update excon instrumentation

The Ruby agent is known to support up to version 0.60.x of the excon gem. We would love your help in making sure our instrumentation works with the latest version.
For guidance on how to proceed, see our Guide to Updating Instrumentation, and please let us know if you have any questions not covered there.

We addressed this as part of our prepend instrumentation work


chore(master): release 0.76.0-alpha

:robot: I have created a release beep boop
0.76.0-alpha (2024-04-01)
Features

new (23fdadc)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/mafqla/yalis-blog/releases/tag/v0.76.0-alpha :sunflower:


Fix up timestamp helpers to match spec

Quick scan of the code seems to say the helpers added in timestamp.proto aren't correct.  The key part being: https://github.com/google/protobuf/blob/master/src/google/protobuf/timestamp.proto#L103-L106  nanos is always positive.
https://github.com/google/protobuf/blob/master/src/google/protobuf/util/time_util.cc#L68-L72 is some of the logic to steal.

I believe this was fixed with #253


"Refactoring: Extract to Page" command

Would cut the current selection (or if nothing is selected the current section based on header?), ask for a page name, replace it with a page reference and move the content to the new page.

also interesting, "merge with page"

Yes, that makes sense. You could also decide to not merge it into core, but create a separate plug repo: https://github.com/silverbulletmd/silverbullet-plug-template
But honestly, I think this will be useful enough to have in core, so yes — I'd put this functionality in plugs/core/refactor.ts or similar.


fix: use typesVersions to wire up deep imports

and explain that stuff in the docs
closes #9114
closes #9115
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[x] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

There's a bad link in the docs preventing the site deploy but other than that LGTM


Current stack is stuck being rebased

Description of the bug
I seem to have gotten my repository into a bit of a pickle with branchless and I'm not sure how to proceed, beyond trashing my repository.
The first problem is we primarily use git-flow, tho I've been trying to use branchless for local work, committing my stacks on the develop branch, things were working fine til I was trying to amend a stack, and ran git sync by accident rather than git restack, and everything went to hell.
It turns out I had legit installed, along with various legit aliases defined in my main ~/.gitconfig file which seems to have been used in favour of branchless (it would be good for the init process to check that maybe).

Actual behavior
I'm stuck in a rebase.
Version of rustc
No response
Automated bug report
Software version
git-branchless 0.8.0
Operating system
macOS 14.3 (Darwin 23.3.0)
Command-line
/Users/amrk/.cargo/bin/git-branchless bug-report

Environment variables
SHELL=/usr/local/bin/fish
EDITOR=<not set>

Git version
> git version
git version 2.43.0

Hooks

Show 7 hooks
Hook post-applypatch
#!/bin/sh
## START BRANCHLESS CONFIG

git branchless hook post-applypatch "$@"
## END BRANCHLESS CONFIG

Hook post-checkout
#!/bin/sh
## START BRANCHLESS CONFIG

git branchless hook post-checkout "$@"
## END BRANCHLESS CONFIG

Hook post-commit
#!/bin/sh
## START BRANCHLESS CONFIG

git branchless hook post-commit "$@"
## END BRANCHLESS CONFIG

Hook post-merge
#!/bin/sh
## START BRANCHLESS CONFIG

git branchless hook post-merge "$@"
## END BRANCHLESS CONFIG

Hook post-rewrite
#!/bin/sh
## START BRANCHLESS CONFIG

git branchless hook post-rewrite "$@"
## END BRANCHLESS CONFIG

Hook pre-auto-gc
#!/bin/sh
## START BRANCHLESS CONFIG

git branchless hook pre-auto-gc "$@"
## END BRANCHLESS CONFIG

Hook reference-transaction
#!/bin/sh
## START BRANCHLESS CONFIG

# Avoid canceling the reference transaction in the case that `branchless` fails
# for whatever reason.
git branchless hook reference-transaction "$@" || (
echo 'branchless: Failed to process reference transaction!'
echo 'branchless: Some events (e.g. branch updates) may have been lost.'
echo 'branchless: This is a bug. Please report it.'

The smartlog doesn't indicate the current rebase status (but maybe it should).
Generally speaking, if you're stuck in a rebase, then you should use git rebase --abort; it shouldn't be different when git-branchless is involved. (It's true that git-branchless initiates some rebases for you.)
I think git sync behaving poorly with rewritten commits, as you've done, is basically a footgun. It's also discussed at https://github.com/arxanas/git-branchless/issues/1137. I'll leave that issue open for that, and rename this issue to address smartlog rebase status.


Release a new version to RubyGems

@SudhagarS could you publish a new version to RubyGems?

@Ch4s3 Hello buddy, just published.

Awesome, thanks! Big fan of this gem BTW.


New version: Puppet.puppet-agent version 8.1.0

Pull request has been created with Komac v1.9.1 :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/116381&drop=dogfoodAlpha

/azp run


color calculations result in different values than configured in theme

I am running into a weird issue, likely caused by a potentially bad theme configuration:
brand1: {
    page: '#ffffff',
    section: '#f7f7f7',
    brand: {
        DEFAULT: '#0c4e19',
        '50': '#f0faeb',
        '100': '#dcf4d3',
        '200': '#bceaac',
        '300': '#92db7b',
        '400': '#6cca51',
        '500': '#4daf33',
        '600': '#388b25',
        '700': '#2d6b20',
        '800': '#0c4e19',
        '900': '#24491e',
        '950': '#0f270c',
    }
}

when using the brand1 theme and an element with bg-brand1 the effective color value used in the document is a few shades "dimmer":
expected value:
'#0c4e19

actual value:
#234c20

Any insight into what may be causing this would be much appreciated.

Hi @Jonnx
Please share your tailwind.config.js file, the theme config you shared does not generate a brand1 color, therefore bg-brand1 does not exist. You might have declared a brand1 color somewhere else in you config


add zn_cursor

Context
implement a part of #89
Summary
The cursor is just shown on center of the screen. Cannot move.
How to check behavior

start zen
appear the cursor on center of the screen

Thank you for review patiently~

How to Check behavior

build
run zen-desktop with one monitor.
add another monitor
disconnect the monitor where a cursor is shown

The cursor appears in the remaining monitor.


Interaction between AsyncDisplayKit and RealSwift breaks accors

Goals
Be able to use standard property accessors on Realm objects with RealmSwift in a project that also uses ASyncDisplayKit
Expected Results
Accessing a property of a Realm object should return the value of that property
Actual Results
All accessors return ether nil (for optionals) or whatever the default value is created by the object's constructor; setters have the same problem.  However accessing (or setting) the properties with KVO and all the values are returned (or set) as expected...
Steps to Reproduce

git clone https://github.com/realm/reach.git
git checkout dhms/rooms-work
cd reach/server
yarn to get all packages, etc updated
Run server in vscode or by hand with npm run build && node dist/index.js
Run Realm Studio, open the local server; then open the /RealmChat Realm; there will be 3 users (ios-user, electron-user and android-user) in the User table created by the server setup
cd ../ios
Update pods with pod update
Open Reach.xcworkspace
Pick a simulator; then build and run
Log in to the local server (users are ios-user, electron-user and android-user all with the password of password)
Swipe left to reveal the utility menu which should have 2 menu items: Settings… and Logout…
Tap Settings - a breakpoint should fire at line 71 in the file SettingsViewModel.swift. This is where the user’s profile is returned by a static method on the User class. You can examine the Realm object and see (as per the attached screen shot, below) that the object is populated… however attempting to access the properties yields the defaults for a new record rather than the values read in from the Realm into the myProfile object.
allowing the app to continue will show the Settings view but, of course, nothing is correctly populated (you can continue to step thru’ here too.. and the object itself will remain intact, but the properties are still inaccessible…).

As mentioned above accessing the properties with KVO and all the values are returned as expected...

@austinzheng  did some preliminary analysis on this issue -- here are the salient parts from our slack conversation: - in a nutshell it seems to be a problem with method swizzling affecting Realm objects:
Austin Zheng [2:33 PM]
as far as I can tell your object is correctly being created at the objective-C layer (and behaves accordingly), but somehow loses its swizzled methods when it gets unsafe bit casted to a Swift object.
David Spector [2:34 PM]
Yikes.  Sounds like AsyncDisplayKit must be the wildcard….
Austin Zheng [2:59 PM]
just to sum up: I investigated code that called into public func object<Element: Object, KeyType>(ofType type: Element.Type, forPrimaryKey key: KeyType) -> Element?. The object that is created behaves correctly at all points during the Objective-C phase of execution. Unfortunately it's not possible to inspect the object once it bubbles back up to the Swift layers because LLDB crashes.
Austin Zheng [1:23 PM]
I made a tiny, tiny bit of progress. Once the object gets back to Swift, if I cast it from Any? to AnyObject? and then use the universal member look-up to get the value of displayName, it seems to work. I think the unsafe downcast/bitcast we're doing might have something to do with the swizzled method impls disappearing? (edited)
Code Sample
See above
Version of Realm and Tooling

Realm framework version: ? 3.01 and 3.0.2
Realm Object Server version: ? 2.0.23
Xcode version: ? Xcode9.1, Xcode9.2
iOS/OSX version: ? iOS 11.1
Dependency manager + version: ? 1.3.1

You have not marked the properties as dynamic.

doh.

we really should catch that....

We've tried. There does not appear to be any way to.


[WFLY-6341] Testcase for basic use of BouncyCastleProvider

https://issues.jboss.org/browse/WFLY-6341

@ctomc, thanks for review, notes incorporated.


Fix ReqMgr2 validation and spec args definition

These are the changes:

Fix the validation code used by ReqMgr2 (for both spec creation and assignment)
Use the same validation used by ReqMgr2 in ReqMgr
Fix some spec arguments and their definition

Already rebased on https://github.com/dmwm/WMCore/pull/7130

Closing it because I made a mess of this branch


Cleaned up some compatibility shims for old Django versions.

Coverage increased (+0.0%) to 90.66% when pulling 4fa8e6db6b4e7e4c5eecad91b4f0134ffcbeec66 on timgraham:user-cleanup into 0dbb961f8427a74845dc9f226987b8f4a525bed8 on divio:develop.

Great job!
I'm setting this on hold to allow @ojii 's patch in first to avoid merge conflicts

Rebased and fixed test failure on develop.

Awesome, thanks!

The sane-add-plugin patch will require some time before merging, resuming merging


Updating and fixing parsers

Fixes #
Proposed Changes

Bugs in ZScaler,PA, Empty
Changes to schema data types

No, let's not wait since the table is already available. We will reformat all parser in a later merge

No, let's not wait since the table is already available. We will reformat all parser in a later merge


v19.0.11 add notes to the Game Initiation Request and it Tests

[Current coverage][cc-pull] is 100%

Merging [#482][cc-pull] into [master][cc-base-branch] will not change coverage

File ...RequestValidator.php was modified. more

Misses 0
Partials 0
Hits +16

@@           master   #482   diff @@
====================================
  Files          27     27
  Lines         418    436    +18
  Methods       103    112     +9
  Messages        0      0
  Branches        0      0
====================================
+ Hits          418    436    +18
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last updated by [3b98b75...08fb94f][cc-compare]
[cc-base-branch]: https://codecov.io/gh/eugene-matvejev/battleship-game-api/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/eugene-matvejev/battleship-game-api/compare/3b98b750a24e5a1afd2c8f7de8bdd7e2e6caf5b1...08fb94fd7662cb6c0934d7a498a86edd18738b03
[cc-pull]: https://codecov.io/gh/eugene-matvejev/battleship-game-api/pull/482?src=pr


Generate an sdist for PyPI

Closes #71
I don't understand all the context about the decision to remove sdists, but I found this: https://github.com/dbt-labs/dbt-extractor/pull/68#pullrequestreview-1540153858. The file is only 266 kb, and there's only one for all platforms, so I see zero risk of any "clogging".
Fixing this would really help people using conda-forge, Anaconda, and Linux distro packagers.
On the side I added __pycache__ to .gitignore.

Superseded by #73


readFile should not trigger error

Currently, using fs.readFile produces an error if the file cannot be statically linked.
babel-plugin-static-fs should not be invoked when fs.readFile is called if it does not support it.
This makes the plugin useless if you aren't only statically importing files.

Thanks! Seems like a duplicate of #15 so let's discuss it there.


Reset unneeded dump tools instead of just the dump-engine

This solves the issue on two tests failing the first time (and working on the second run).
Follow up of #15059

Snapshot stored with reference name:
refs/pull/15142/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15142/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15142/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/15142/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/15142/merge
https://gui.babylonjs.com/?snapshot=refs/pull/15142/merge
https://nme.babylonjs.com/?snapshot=refs/pull/15142/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/15142/merge#BCU1XR#0

WebGL2 visualization test reporter:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15142/merge/testResults/webgl2playwright/index.html

Visualization tests for WebGPU (Experimental)
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15142/merge/testResults/webgpuplaywright/index.html


getting exception on parser.Unseal

The code works well on my local machine, but when we put on our test server we are getting below exception. Please help identifying this issue.
Exception Message - One or more errors occurred. (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond).
Stack Trace
System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
at GooglePay.PaymentDataCryptography.SignatureVerification.VerifyMessage(PaymentData paymentData, String sender, String recipient, ISignatureKeyProvider keyProvider) in D:\Agents\a1_work\36\s\src\GooglePay.PaymentDataCryptography\SignatureVerification.cs:line 38
at GooglePay.PaymentDataCryptography.PaymentMethodTokenRecipient.Unseal(String sealedMessage) in D:\Agents\a1_work\36\s\src\GooglePay.PaymentDataCryptography\PaymentMethodTokenRecipient.cs:line 122

It seems your server is blocking external HTTP requests that are needed to fetch Google's signing keys.
You have two options:

Configure your test server to allow external traffic to https://payments.developers.google.com which is needed to fetch these keys.

Make Google's signing keys available on your test server through other means (e.g. locally) and then load them by extending ISignatureKeyProvider. For an example on how to do this, see how GoogleKeyProvider works.

I'm closing this since it's not an issue with the library.


How to replicate start file that accesses host environment variabels using ENTRYPOINT

I am trying to get a Dockerfile-based build working through pangeo's binder (original issue posted here), but am running into difficulty replicating the functionality of the start script they have in their cookie cutter recipe.
In a nutshell, that start script replaces some fields in a jupyterlab-workspace.json file by accessing the ${JUPYTERHUB_USER} environment variable on the host machine. However, when I set this start script up as an ENTRYPOINT at the end of my Dockerfile, when the docker image is built and run using pangeo's binder link, it is not accessing this environment variable, and the server is failing to launch because jupyter lab doesn't generate an appropriate workspace in the ENTRYPOINT script. I suspect this is because the pangeo binderhub setup doesn't specify an argument like -e JUPYTERHUB_USER when it calls docker run. Any idea how I can pull host environment variables into my ENTRYPOINT script if the host machine doesn't use this -e flag? It seems like this variable is picked up when the using the start file in the conda buildpack approach, just not when I'm trying to replicate it in a Dockerfile.

I think the underlying issue is https://github.com/jupyterlab/jupyterlab/issues/5977 - workspaces shouldn't rely on JUPYTERHUB_USER. JUPYTERHUB_USER is only set when running under a JupyterHub - so it's set on mybinder.org but not on repo2docker itself.

Seems like a good lead, but would that explain why this fails using a Docker build but but not with the conda buildpack that included a start file? If you follow the pangeo-binder link from this repo, it gets running fine. This is using a binder folder with files that trigger the conda build pack. The start file handles the JUPYTERHUB_USER substitution for workspace and in call to jupyter lab, and seems to work fine. I had expected that using ENTRYPOINT as a substitute for the start file would replicate the functionality of the start file under other buildpacks. I had assumed that the ENTRYPOINT script would have access to the host's environment variables, but that is apparently not the case (unless they're explicity provided with docker run -e ...).

@yuvipanda You've added the documentation label. Have you since figured out what the expected behaviour is, or where to find it?


Stub out a Dev Documentation section in the wiki

find out how to visualize the overall problem space
Stub out user personas to
https://github.com/trendscenter/coinstac/wiki/User-Personas
See how the problem space is solved either currently or ideally

Interview current user personas

researcher
computation author

I'd like to work towards the following pattern:
Concise, high level descriptions of the problem space and solutions that we can work backwards from. Starting with the most abstract, down to code implementation.

Ease-of-use is a big thing to optimize for in our software

Examples:

https://docs.openneuro.org/user_guide.html
https://bids-standard.github.io/pybids/


Question: is it possible to embed external .srt subtitles inside the output file?

So, I have many videos that have no embedded subtitles but only external, separate .srt subtitles. I was wondering if there is a way to bundle this subtitles to the output file of h265ize. I searched for this option but I found nothing so far.
Just to be clear: I do not want to hard sub the video with the subtitle, I just would like to bundle the srt file with the mkv file instead of having it as a separate file.

No. Sorry. Try https://mkvtoolnix.download/doc/mkvmerge.html.


Add more resources in Tools section

Please assign this issue under GSSOC'23 to me. I will add one resource in the Tools section -> JavaScript.

I've made the PR. @jayk-gupta please review it and accordingly merge it.


Configure reverse proxy and ssl certificate

URL: https://blog.metafacture.org

[x] change urls in gatsby-config
[x] remove pathPrefix
[ ] configure reverse proxy
[x] add ssl certificate

Added PR https://github.com/metafacture/metafacture-blog/pull/9 in which the url is changed in the gatsby-config to blog.metafacture.org and the path prefix is removed. After merging this will be published at https://metafacture.github.io/metafacture-blog/, so @dr0i can configure the reverse proxy.

Closed incidentially by #9, reopening.

Configured reverse proxy as in blog.skohub.io. Please check @katauber if things are working as expected.

The icons of github and twitter are a little bit bigger than they should 😄 I try to find out why.

There seems to be something wrong with the pathes of the links. If I click on a blockpost the url is e.g. https://blog.metafacture.org/new-beginnings/ but I stay on the main page. Maybe the reason of this problem is the same reason for the big icons?
In the skohub blog the icons are also very big on the github-io page but have the right size on blog.skohub.io, so maybe the problem is in the configuration of the reverse proxy @dr0i ?

Thx @katauber. Indeed I forgot an $1 doing a RewriteRule. Looks good now to me - can you confirm?

Commited apache configs. Closing.


Add Colaboratory

Addresses Issue #554 and adds CoLaboratory to the repository

Great - could you please add a reference image as well if you have time?


SimulateReflectivity has no way of passing in a random number generator for reproducibility

The SimulateReflectivity class should have some way of passing in a np.random.Generator instance so that simulation of reflectivity curves can become reproducible.

closed by #120


emacs: make a number of melpa packages work again

Motivation for this change
Fixes #44539
Things done

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

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

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

Cc: @chaoflow @lovek323 @peti @the-kenny @jwiegley

Sure

Thank you!


alt+key, ctrl+key, alt+shift+key don't work in terminal-in-editor (only ctrl+shift+key works)

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.91.0
OS Version: arch linux

Steps to Reproduce:

assign a keybinding to ctrl+key or alt+key
open a terminal-in-editor and focus it
press the keybind
nothing happens

this is the output of the keybind debugger panel while pressing ctrl+shift+e and alt+e
2024-07-04 13:44:30.916 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-07-04 13:44:30.916 [info] [KeybindingService]: \ Keyboard event cannot be dispatched
2024-07-04 13:44:30.917 [info] [KeybindingService]: + Ignoring single modifier ctrl due to it being pressed together with other keys.
2024-07-04 13:44:31.680 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-07-04 13:44:31.680 [info] [KeybindingService]: \ Keyboard event cannot be dispatched
2024-07-04 13:44:31.681 [info] [KeybindingService]: / Received  keydown event - modifiers: [ctrl], code: ControlLeft, keyCode: 17, key: Control
2024-07-04 13:44:31.681 [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl], code: ControlLeft, keyCode: 5 ('Ctrl')
2024-07-04 13:44:31.682 [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
2024-07-04 13:44:31.846 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-07-04 13:44:31.846 [info] [KeybindingService]: \ Keyboard event cannot be dispatched
2024-07-04 13:44:31.847 [info] [KeybindingService]: / Received  keydown event - modifiers: [ctrl,shift], code: ShiftLeft, keyCode: 16, key: Shift
2024-07-04 13:44:31.847 [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl,shift], code: ShiftLeft, keyCode: 4 ('Shift')
2024-07-04 13:44:31.848 [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
2024-07-04 13:44:32.092 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-07-04 13:44:32.092 [info] [KeybindingService]: | Resolving ctrl+shift+E
2024-07-04 13:44:32.093 [info] [KeybindingService]: \ From 3 keybinding entries, matched workbench.action.focusNextGroup, when: no when condition, source: user.
2024-07-04 13:44:32.093 [info] [KeybindingService]: / Received  keydown event - modifiers: [ctrl,shift], code: KeyE, keyCode: 69, key: E
2024-07-04 13:44:32.093 [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl,shift], code: KeyE, keyCode: 35 ('E')
2024-07-04 13:44:32.093 [info] [KeybindingService]: | Resolving ctrl+shift+E
2024-07-04 13:44:32.094 [info] [KeybindingService]: \ From 3 keybinding entries, matched workbench.action.focusNextGroup, when: no when condition, source: user.
2024-07-04 13:44:32.094 [info] [KeybindingService]: + Invoking command workbench.action.focusNextGroup.
2024-07-04 13:44:32.334 [info] [KeybindingService]: + Ignoring single modifier ctrl due to it being pressed together with other keys.
2024-07-04 13:44:32.611 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-07-04 13:44:32.612 [info] [KeybindingService]: \ Keyboard event cannot be dispatched
2024-07-04 13:44:32.612 [info] [KeybindingService]: / Received  keydown event - modifiers: [alt], code: AltLeft, keyCode: 18, key: Alt
2024-07-04 13:44:32.612 [info] [KeybindingService]: | Converted keydown event - modifiers: [alt], code: AltLeft, keyCode: 6 ('Alt')
2024-07-04 13:44:32.612 [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
2024-07-04 13:44:33.152 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-07-04 13:44:33.153 [info] [KeybindingService]: | Resolving alt+E
2024-07-04 13:44:33.153 [info] [KeybindingService]: \ From 1 keybinding entries, matched workbench.action.focusNextGroup, when: no when condition, source: user.
2024-07-04 13:44:33.153 [info] [KeybindingService]: / Received  keydown event - modifiers: [alt], code: KeyE, keyCode: 69, key: e
2024-07-04 13:44:33.154 [info] [KeybindingService]: | Converted keydown event - modifiers: [alt], code: KeyE, keyCode: 35 ('E')
2024-07-04 13:44:33.154 [info] [KeybindingService]: | Resolving alt+E
2024-07-04 13:44:33.154 [info] [KeybindingService]: \ From 1 keybinding entries, matched workbench.action.focusNextGroup, when: no when condition, source: user.
2024-07-04 13:44:33.155 [info] [KeybindingService]: + Invoking command workbench.action.focusNextGroup.
2024-07-04 13:44:33.264 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-07-04 13:44:33.264 [info] [KeybindingService]: | Resolving alt+E
2024-07-04 13:44:33.265 [info] [KeybindingService]: \ From 1 keybinding entries, matched workbench.action.focusNextGroup, when: no when condition, source: user.
2024-07-04 13:44:34.023 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-07-04 13:44:34.023 [info] [KeybindingService]: | Resolving alt+E
2024-07-04 13:44:34.023 [info] [KeybindingService]: \ From 1 keybinding entries, matched workbench.action.focusNextGroup, when: no when condition, source: user.
2024-07-04 13:44:34.178 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-07-04 13:44:34.178 [info] [KeybindingService]: | Resolving alt+E
2024-07-04 13:44:34.179 [info] [KeybindingService]: \ From 1 keybinding entries, matched workbench.action.focusNextGroup, when: no when condition, source: user.
2024-07-04 13:44:35.635 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-07-04 13:44:35.635 [info] [KeybindingService]: \ Keyboard event cannot be dispatched
2024-07-04 13:44:35.635 [info] [KeybindingService]: + Ignoring single modifier alt due to it being pressed together with other keys.
2024-07-04 13:45:00.446 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-07-04 13:45:00.520 [info] [KeybindingService]: \ Keyboard event cannot be dispatched
2024-07-04 13:45:00.520 [info] [KeybindingService]: / Received  keydown event - modifiers: [shift], code: ShiftLeft, keyCode: 16, key: Shift
2024-07-04 13:45:00.521 [info] [KeybindingService]: | Converted keydown event - modifiers: [shift], code: ShiftLeft, keyCode: 4 ('Shift')
2024-07-04 13:45:00.521 [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
2024-07-04 13:45:01.573 [info] [KeybindingService]: + Storing single modifier for possible chord shift.

I've figured out the issue, closing
https://code.visualstudio.com/docs/terminal/advanced#_keybinding-and-the-shell


VS 2022 support

Please would you consider adding support for VS2022? I've gotten so used to having your extension it's hard to live without it, thank you!
Here is a link to documentation:
https://docs.microsoft.com/en-us/visualstudio/extensibility/migration/update-visual-studio-extension?view=vs-2022

Hm. That was a fair bit of work. But I suppose I'm going to want it myself sooner or later. I'll put it on the mental backlog.

Much appreciated!
On Mon, 21 Jun 2021 at 17:24, Olle Westman @.***> wrote:

Hm. That was a fair bit of work. But I suppose I'm going to want it myself
sooner or later. I'll put it on the mental backlog.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ow--/vs-subword-navigation/issues/14#issuecomment-865173613,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABCY6YJMRCAP5D3VVXVXQUTTT5RTFANCNFSM47BGM27A
.

Good news! Because this extension is very simple, it doesn't need to be split into multiple projects to support Visual Studio 2022. 🎉
I've created PR #15 to add VS2022 support.


Stats VLR draft

As discussed in #19.

So did we scrap mean/median/variance then? I think those would future-proof the format and add very little overhead to the file

So did we scrap mean/median/variance then? I think those would future-proof the format and add very little overhead to the file

Much 🧇'ing.

To me, the mean/variance fields are a half-measure - aside from the extents which are quite useful, what you really probably want is bucketed counts, potentially histograms at various or adaptive bin sizes, maybe other stats, etc.  I think the mean and variance are not useful enough to require as part of the core spec and just add complication for writers (I just included them here because EPT had them), and rather that some optional VLR targeting rendering statistics could be specified in the future to capture these more sophisticated scenarios.

It's a tough balancing act, and this is why we've been 🧇'ing so much. First is how to provide enough simple metadata to a renderer to make some sliders for dimension rendering. We know from Potree and Plasio this is a very strong need. The second is to keep the writers as simple as possible so they don't have to do extra work to produce data that no one will use.
mean isn't that expensive to compute, but variance is a little bit expensive and can be challenging to do in a way that doesn't require all of the data at once. What could a client do with mean? I suppose they could easily adjust the rendering of a grouping of COPC files to normalize them in some way, but doing that probably requires a much more resolute histogram than mean/stddev provide. A renderer can't do much with variance without making assumptions about the shape of the histogram. In that case, I think you'd much rather have the histogram.
After hashing it out, we don't want to require a complicated VLR that only exists to support certain kinds of rendering tricks. If the COPC rendering community (if there ever is one) wants to come up with an optional EVLR that can be placed at the end of the file, I think that would serve the need in an unobtrusive way – people who wanted to "render optimize" their COPC files could write a bit of software to cumulate these stats and stick them on the end as a VLR. Then it could include fancy histograms, transformations, and many of the other things Markus might want to make pretty pictures.
The capability to provide dimension ranges that the currently proposed VLR provides is a simple extension of something that was missing in LAS. What can you do with just the ranges as we've proposed here?

Know if a field is actually populated with data (min != max)
Know if the Intensity field is using 8-bit or 16-bit range
Guestimate GPSTime situation based on range
Know if the data have any flagged points

We think this is enough, but we would like to hear concrete reasons why it isn't if you have them.

So we can do:
struct CopcInfo
{
  int64_t span;                 // Number of voxels in each spatial dimension (typically powers of 2)
  uint64_t root_hier_offset;    // File offset to the first hierarchy page
  uint64_t root_hier_size;      // Size of the first hierarchy page in bytes
  uint64_t laz_vlr_offset;      // File offset of the *data* of the LAZ VLR
  uint64_t laz_vlr_size;        // Size of the *data* of the LAZ VLR.
  uint64_t wkt_vlr_offset;      // File offset of the *data* of the WKT VLR if it exists, 0 otherwise
  uint64_t wkt_vlr_size;        // Size of the *data* of the WKT VLR if it exists, 0 otherwise
  uint64_t eb_vlr_offset;       // File offset of the *data* of the extra bytes VLR if it exists, 0 otherwise
  uint64_t eb_vlr_size;         // Size of the *data* of the extra bytes VLR if it exists, 0 otherwise
  uint64_t extent_vlr_offset;
  uint64_t extent_vlr_size;
  uint64_t reserved[9];        // Reserved for future use. Must be 0.
};

?
What else do we need to get it across the line?

What else do we need to get it across the line?

definition of the cube with a centerpoint and a distance needs to go in the info VLR as well.

@hobu What do you mean by "a distance"?

@hobu Sorry, reflecting on this:

What cube?
What centerpoint? The centerpoint of the cube?
What does "a distance" refer to?

Is there previous discussion of these in the issue queue? we aren't seeing them

See: https://github.com/copcio/copcio.github.io/issues/26#issuecomment-920318010

We should remove the extra bytes dims from this VLR as they're already in the EB VLR.

We should remove the extra bytes dims from this VLR as they're already in the EB VLR.

So if we were to fully normalize as suggested:

XYZ ranges from the header
ReturnNumber ranges from the header (current language doesn't do that)
PointSourceId-defined dimensions from this extents VLR
EB VLR ranges from EB VLR item headers

If we were to provide everything in the extents VLR:

Add range entries in order for all dimensions including XYZ, but not including bitfields.

At risk of the extents VLR data being out of sync with those other places, let's go with the latter. Not as much hopping around, not as much dimension checking logic when writing or reading it, and maybe it is an example going forward for LAS if there ever is another LAS version.

@abellgithub @hobu do you plan on adding a new VLR for extents in lazperf to go along lazperf::copc_vlr? Or just adding the offset and size in the current copc_vlr?

do you plan on adding a new VLR for extents in lazperf to go along

It is included in https://github.com/hobu/laz-perf/pull/102 but I was waiting on the dust to settle on the info VLR before merging. We will make a new laz-perf release when we are ready to go final with COPC 1.0

Ah great, thanks!


Sensitive Variable Support

Thinking out loud here.
I saw Django's sensitive_variables feature for the first time today. Seems like a great idea.
https://docs.djangoproject.com/en/dev/howto/error-reporting/#sensitive_variables
@mitsuhiko any thoughts on adding support for this into werkzeug?

Sensitive variable markup in Django seems to be for two things: debug output and error logging / emails. Given that the debugger should only be run in development, and it can evaluate code, I don't think the added complexity is needed. And we don't log any data with exceptions, that would be something handled specifically by a project, and I don't think that's something that falls enough into Werkzeug's scope.


Trinity handling of KeyboardInterrupt

What is wrong?
Currently, trinity is not correctly handling KeyboardInterrupt for asyncio loop based processes.
How can it be fixed
Fill this in if you know how to fix it.
We need to make use of the asyncio.loop.add_signal_handler API to do proper keyboard interrupt signal handling.

asyncio is very low-level
For KeyboardInterrupt, there are varied behaviours. Check this issue : https://github.com/python/asyncio/issues/341
It depends on how you trigger KeyboardInterrupt. When there is a callback that doesn't return - you need to use the signal to break through that, eg a loop like
while True:
    pass

Adding asyncio.loop.add_signal_handler might not work because it wouldn't stop such a loop.
Otoh, if there's an event loop or a queue running, and you do not want the signal to interrupt that routine, you can use asyncio.loop.add_signal_handler .
Another way to do it (naively), would be :
loop = asyncio.get_event_loop()

tasks = asyncio.gather(
        asyncio.async(some_task(second=5)),
        asyncio.async(some_task(seconds=10))
    )

try:
    loop.run_until_complete(tasks)
except KeyboardInterrupt as e:
    print("Caught keyboard interrupt..")
    tasks.cancel()
    loop.run_forever()
    tasks.exception()
finally:
    loop.close()


BYPhoneNumTF - 柏荧的博客 | BY Blog

https://dalangblog.github.io/2017/02/04/BYPhoneNumTF/
Every failure is leading towards success.

45


In Nuxt this.$gtag is undefined in actions of vuex store

Description
In Nuxt this.$gtag is undefined in actions of vuex store
Expected behavior
Be able to access gtag in actions of vuex store
Actual behavior
$gtag is undefined, work well in components
Environment
Run this command in the project folder and fill in their results:
npm ls vue-gtag<EMAIL_ADDRESS>Then, specify:

Operating system: Mac Os 10.14
Browser and version: Google chrome: Version 88.0.4324.182 (Official Build) (x86_64)

Reproducible Demo
async signupWithLocal ({ dispatch, rootState }, payload) {
    const { $auth, $axios, $gtag } = this

    ...

    await $auth.setUserToken(data.token)

    try {
      this.$gtag.set({
        'userId': $auth.user._id
      })
    } catch (e) {
      console.log(e)
    }
}

Use vm in nuxt
this._vm.$gtag

vue-gtag is not available in the vuex context, you should import it like this
import { set } from 'vue-gtag'

set({ userId: 'foo' })

check all methods here https://matteo-gabriele.gitbook.io/vue-gtag/api

Use vm in nuxt
this._vm.$gtag

undefined inside a nuxt 2 plugin


I need help piz

my music bot will not do play music join in the channel

it say
Traceback (most recent call last):
File "C:\Users\Robbie\Desktop\MUSIC bot\MusicBot-master\musicbot\bot.py", line 256, in get_voice_client
await asyncio.wait_for(voice_client.connect(), timeout=10, loop=self.loop)
File "C:\Users\Robbie\AppData\Local\Programs\Python\Python35-32\lib\asyncio\tasks.py", line 396, in wait_for
raise futures.TimeoutError()
concurrent.futures._base.TimeoutError

a


http://toblerity.github.com/shapely/ appears to be down

I haven't been able to open the docs in a few days. Is this a known issue?

This works fine for me at the moment.

Works for me now, too.


IE8 svg object constructor

Hi,
In IE8 , the constructor of  svg object is  [object HTMLGenericElement] . Maybe, you should judge svg with nodeName instead of constructor。

Hi there,
Well, I never considered to work on IE8 because SVG is not supported and this browser is no longer supported by Microsoft. Plus, I don't think I can use required methods like getTotalLength() on path elements. So I prefer to focus on bugs and new features.
Sorry


fix bug in checking playback type

Could you please make this change as a pull request to https://github.com/avalonmediasystem/mediaelement/tree/avalon ?

Woops, I mistakenly pushed straight into Avalon branch.
From: cjcolvar<EMAIL_ADDRESS>Sent: Thursday, October 08, 2015 2:25 PM
To: avalonmediasystem/mediaelement_rails
Cc: Keese, Brian W
Subject: Re: [mediaelement_rails] fix bug in checking playback type (#4)
Could you please make this change as a pull request to https://github.com/avalonmediasystem/mediaelement/tree/avalon ?
—
Reply to this email directly or view it on GitHubhttps://github.com/avalonmediasystem/mediaelement_rails/pull/4#issuecomment-146645178.

No problem.  I was thinking this could be done directly as well.


validation failed, will skip it: unit is not expected with channel instance

not can select channel

fix<EMAIL_ADDRESS>


Remove unused imports to fix style warnings

Motivation and Context
We have style warnings on develop:

I found some other used imports in the tests:
https://github.com/ls1intum/Artemis/blob/26c469be15665912614ea17f5664c4a82b0a86c9/src/test/javascript/spec/helpers/mocks/service/mock-auth-server-provider.service.ts#L2
https://github.com/ls1intum/Artemis/blob/develop/src/test/javascript/spec/helpers/mocks/service/mock-code-editor-build-log.service.ts#L4
https://github.com/ls1intum/Artemis/blob/develop/src/test/k6/ModelingExerciseAPIs.js#L14

@Strohgelaender thanks, I removed those as well.


fix(detect-scan): support input for .secrets.baseline path

Issue
When .secrets.baseline is provided, the file is only updated and not written to stdout.
Therefore, the pipe to baseline2rdf doesn't work as there is no JSON to parse.
Proposed solution

Add an input to specify a baseline path (usually .secrets.baseline).
If an input is provided, just update the current baseline file (rename to conventional name if different). If not, output the json from stdout to .secrets.baseline
Echo the content of .secrets.baseline and pipe it to baseline2rdf and reviewdog commands.

This was not tested, and it might contains errors, please don't hesitate to fix it or suggest any modification :)

This approach will create and store the artifact .secrets.baseline in the working directory. This is unexpected behavior for an optional feature.
I suggest moving the .secrets.baseline file to a temporary container directory /tmp/. And if stdout data needs access, then changing the path to the file as addition option.

Thanks for your suggestion.
I agree and have moved the .secrets.baseline to /tmp. I'm not sure this is all you suggested, detect-secrets doesn't write the baseline content to stdout if the baseline path is provided.

Hi, @SoaAlex! We merged your PR to reviewdog! 🐶
Thank you for your contribution! ✨
We just invited you to join the @reviewdog organization on GitHub.
Accept the invite by visiting https://github.com/orgs/reviewdog/invitation.
By joining the team, you'll be a part of reviewdog community and can help the maintenance of reviewdog.
Thanks again!


💢💢Suggestion problem💢💢

I'm not sure why this is happening but as far as I checked, this happens with all suggestion extensions.
An explanation of why it happens:

https://github.com/tailwindlabs/tailwindcss-intellisense/issues/458#issuecomment-1013118943

Video:
https://user-images.githubusercontent.com/101414008/160208711-73e7d0d3-922f-40e3-a66f-12a1bf39393b.mp4
My active class suggestion extension at the time that I was recording the video:

vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vsclayoutctrt:30451275
dsvsc009:30452663
pythonvsnew555:30457759
vscscmwlcmc:30438804
vscgsvid1:30447480
cppdebug:30451566
pynewfile477cf:30450039

Please disable "Snippets Prevent Quick Suggestions":
"editor.suggest.snippetsPreventQuickSuggestions": false

An alternative solution is manually triggering suggestion when in a snippet.

Please disable "Snippets Prevent Quick Suggestions":
"editor.suggest.snippetsPreventQuickSuggestions": false

Thank you so much @Lemmingh, this☝ works.

Is this going to get fixed eventually? It makes suggestion plugins limited/broken because you don't always get the suggestion...

Not sure what do you mean.
The snippetsPreventQuickSuggestions setting was introduced to solve the interference between snippet and quick suggestion: #50776
So, it depends on your workflow. If it's safe to always enable quick suggestion, turning snippetsPreventQuickSuggestions to false works best for you. Otherwise, manual triggering is the right choice.

In case you don't know why I talk about snippet:
The Emmet in VS Code is powered by snippet.


website improvements

Current dependencies on/for this PR:

main

PR #107   👈

This stack of pull requests is managed by Graphite.