Auto generate tutorial data

@garrettmflynn Need your help integrating this with front-end
In the meantime, I'll continue debugging and extend it to multi-subject, multi-session, and multi-probe

@garrettmflynn Might also need some help getting the test to trigger the endpoint properly, I keep getting a 415 error locally

Getting an error about ModuleNotFoundError: No module named 'sklearn'. Are there additional dependencies here that weren't in the repo before?

Ahhhh, yes sorry - I should have added them to the conda environment files
Through trial and error it will be whatever is needed to succeed with these imports: https://github.com/NeurodataWithoutBorders/nwb-guide/pull/530/files#diff-bfe22e422f7a3669b04d7ddfc8b73491eda63907f0a4da680bb6494f98f15d69R771-R773

Alright, I've updated this PR so that you can generate test data (and, at the same time, a dataset that replicates this data) on the Settings page. I've pre-emptively removed the Tutorial page since this replaces the data generation features there—though we don't currently have any textual material that replaces the original tutorial.
@CodyCBakerPhD Any suggestions before we can merge this in?

@CodyCBakerPhD Any suggestions before we merge this in?

Only to have a navigation popup button next to the 'delete' one that leads the user to the generated dataset so that they can see what it looks like after it completes

Also, this PR removes autogeneration of the 'tutorial pipeline' in anticipation of the step-by-step screenshot approach approach, right?

Did you run through a full pipeline using the generated data?
I have an issue with the Phy folders specifically; they formed invalid symlinks for me

Specifically leading to
Uncaught (in promise) Error: ENOENT: no such file or directory, stat '~\NWB_GUIDE\test-data\data\phy\phy_example_0'
    at statSync (node:fs:1615:3)
    at Object.<anonymous> (node:electron/js2c/asar_bundle:2:4557)
    at Object.statSync (D:\GitHub\nwb-guide\node_modules\graceful-fs\polyfills.js:319:16)
    at #checkType (FileSystemSelector.js:134:38)
    at Array.forEach (<anonymous>)
    at #handleFiles (FileSystemSelector.js:142:53)
    at FilesystemSelector.selectFormat (FileSystemSelector.js:168:30)

in the folder selector

That symlink issue should be fixed. My bad!
I've added that extra interaction as well. The "show in folder" command actually completely stalls my Finder on Mac, which is super weird. I'll see if I can find a way to avoid that

The delete command triggers a non-meaningful error when it tries to delete the target of the symlinks after the first time it was deleted (I assume that's what's going on); is there a way to 'safely' do that?
I also pushed a fix to the channel lengths on SpikeGLX, can you also run through a full test of a pipeline that uses these data?

Can't get past the SourceData page with this error:

The delete command triggers a non-meaningful error when it tries to delete the target of the symlinks after the first time it was deleted (I assume that's what's going on); is there a way to 'safely' do that?

Can you clarify what's triggering this error? Are you generating the dataset, deleting, regenerating, then deleting again? This is just removing the dataset output folder and shouldn't let you press the button without that folder existing.

I've also found a fix for the lack of responsiveness when opening the folder location on Mac. Does this make things faster on your side as well?

Can't get past the SourceData page with this error:

Fixed this. Turns out that if I don't delete the data (only the dataset), the previously generated files will not be overwritten?

I've also found a fix for the lack of responsiveness when opening the folder location on Mac. Does this make things faster on your side as well?

Mine no longer even opens at all; if possible, could you use the previous method if its Windows and your current method if its Mac?

Can you clarify what's triggering this error?

It was the kind of windows JS popup message that I can't copy/paste; said something about not being able to remove the resources because it didn't exist; I haven't seen it as of the last few commits

Got it. I've ensured that the directories are only deleted if they exist, so that should solve the latter problem.
As for it not working on Windows, that's quite weird. Can you confirm that starting GUIDE again from the command line doesn't fix the issue? Since the changes were partially implemented on the main Electron process, the app needs to be restarted (which I also didn't notice and thought the system was broken after the initial implementation).

As for it not working on Windows, that's quite weird. Can you confirm that starting GUIDE again from the command line doesn't fix the issue? Since the changes were partially implemented on the main Electron process, the app needs to be restarted (which I also didn't notice and thought the system was broken after the initial implementation).

That was it; fully restarting the app fixed the issue

@garrettmflynn This is now working well for me; can you review, try it completely, and approve if happy with it?


docker machine

It would be neat to have a one-line local test docker machine.

Yeah this is definitely something that I want to add once the foundation has been set. Shouldn't be very difficult to get that done.

Found this article which may be helpful.

This has been added through the new repo maproulette/maproulette2-docker


Fix comparetion

       $res = BC::parse('0 | 0');         var_dump($res);
Old version:
Replacing 0|0 with  in the (0|0) section of (0|0)
Replacing (0|0) with  in (0|0)
string(0) ""
New version:
Replacing 0|0 with 0 in the (0|0) section of (0|0)
Replacing (0|0) with 0 in (0|0)
string(1) "0"
if i add some logic to parse:
 $isPlayed = BC::parse('{totalMoney} <= {playedMoney} | {balance} <= 1' , [             'totalMoney'  => $bonusUser->totalMoney,             'playedMoney' => $bonusUser->playedMoney,             'balance' => $financeClient->balance         ], 2, true);         var_dump($res);

Codecov Report

Merging #3 into master will decrease coverage by 0.71%.
The diff coverage is 90.9%.

@@             Coverage Diff              @@
##             master       #3      +/-   ##
============================================
- Coverage       100%   99.28%   -0.72%
- Complexity       70       79       +9
============================================
  Files             1        1
  Lines           138      140       +2
============================================
+ Hits            138      139       +1
- Misses            0        1       +1

Impacted Files
Coverage Δ
Complexity Δ

src/BC.php
99.28% <90.9%> (-0.72%)
79 <45> (+9)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cd8c759...a641350. Read the comment docs.

andru@developer-a ~/Web/www/bcmath $  phpunit -v --color -c .travis-phpunit.xml
PHPUnit 5.3.5 by Sebastian Bergmann and contributors.
Runtime:       PHP 5.6.30-11+deb.sury.org~trusty+3 with Xdebug 2.5.1
Configuration: /home/andru/Web/www/bcmath/.travis-phpunit.xml
.......................                                           23 / 23 (100%)
Time: 8.48 seconds, Memory: 6.00MB
OK (23 tests, 72 assertions)
Generating code coverage report in Clover XML format ... done
https://www.dropbox.com/s/bm7stcnli109k9p/снимок50.png?dl=0
https://www.dropbox.com/s/aq4avopo3tmkzi6/снимок51.png?dl=0

Please check coverage parser because if i run PHPUnit coverage in local machine i see 100%

I actually want to do this a slightly different way; I just haven't had a moment to sit down and do it.
I was originally a bit worried about how boolean operations would be processed if there were more than one in an expression, but I figured it wouldn't be a feature used very often, so I didn't bother improving the implementation at the time. This PR reminded me I still hadn't addressed that, and apparently it's a useful feature after all, so I'm gonna sit down and make it happen soon. Just haven't gotten there, yet. I'll leave this open to remind me to follow through.
Should have said something sooner, actually. Sorry about that. :frowning_face:

Can i use this logic in my project? After you make the logic in your own, will I be able to use your code without changes in my project?

I don't see why not. It will output the same way. The only differences will be in exactly how the parser handles booleans, that's all.

Up. This fix is actual now.


virt-launcher: fix guestOS info reporting in VMI status

The guestOS info in the VMI resource would stop getting populated
after 5 minutes (--qemu-agent-version-interval default) and until
a new Domain notification would get delivered to virt-handler because
the code which does the periodic resyncing uses the GetDomain()
virt-launcher API which does not populate guestOS info when retrieving a
Domain leading to virt-handler updating the VMI status with a blank guestOS info.
This commit makes ListAllDomains() (which is used by GetDomain())
populate GuestOS info (when available).
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1924479
Signed-off-by: Antonio Cardace<EMAIL_ADDRESS>
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

virt-launcher now populates domain's guestOS info also when doing periodic resyncs.

This looks very similar to https://github.com/kubevirt/kubevirt/pull/5428

This looks very similar to #5428

Indeed! race condition alert :)
Well since it's fixed I'm just going to close this.

/close

This looks very similar to #5428

Indeed! race condition alert :)
Well since it's fixed I'm just going to close this.

I'm not sure if it is fixed or not, that one was done for the network interfaces.
Just make sure it is indeed fixed.

OSinfo fix is included there as well
Thanks for raising it

Should we add release notes to #5428
as you did here?

FYI
PR #5428 handles handleResync periodic, which is determined by virt-handler defaultDomainResyncPeriodSeconds
In case this PR meant to handle other periodic flow which PR #5428 doesn't
then it might worth to recheck it
I did see that with #5428 there are no flakes for 20 minutes plus
nor for the interfaces nor for the OSinfo, on the other hand

@oshoval I've already looked at it and indeed your PR fixes the same issue, it's the same exact fix, just a different flavor :) Thank you!

Should we add release notes to #5428
as you did here?

Yes, I'd add a release note as it actually fixes a reported bug https://bugzilla.redhat.com/show_bug.cgi?id=1924479.


This fixes two errors SNMPV3 des3 privacy support.

Key localization is now done as specified in https://tools.ietf.org/html/draft-reeder-snmpv3-usm-3desede-00
and not as in https://tools.ietf.org/html/draft-blumenthal-aes-usm-04 which is only for AES.
Crypt/Decrypt functions were broken; they were doing unnecessary extra work. All they needed to do is use the encrypt/decrypt methods provided by the 3DES object from Pycrypto.

Tested with Cisco IOS 15.1 (cisco 890 services router) and Cisco Modeling Labs Router (Cisco IOS 15.4).

Thank you for your work on this! I'm eager to merge it, however I want to understand why it works with Extreme networks switch despite seeming difference in algorithm used compared to that described in RFC. Could it be some other draft standard? %-\

My last commit updated the code as per your comments, thanks. Feel free to do any editing that you want to do on the code.
I believe that  this code faithfully implements the key localization specified in the  https://tools.ietf.org/html/draft-reeder-snmpv3-usm-3desede-00 draft standard for 3DES, which is why it is no surprise that it works with Extreme Networks and also Cisco.
I want to point out that all third party tools I used (SnmpGet SnmpSoft, SNMP++) worked fine with 3DES for both Cisco and Extreme networks because they implemented the reeder draft standard. It is only in AES192/AES256 encryption that problems arise because Cisco did not follow the bluementhal draft standard (instead, used the key localization from the 3DES draft standard).


rename app to match other app-templates naming conventions

It should be called "acme-apptemplatecs"

fixed


autofocus only works if Editor is created with a mobiledoc

This currently will not autofocus, because there is no document, therefore nowhere to place the cursor:
const editor = new Mobiledoc.Editor({
  placeholder: 'Write here...',
  autofocus: true
})

This works:
const editor = new Mobiledoc.Editor({
  placeholder: 'Write here...',
  autofocus: true,
  mobiledoc: {
    version: '0.3.0',
    markups: [],
    atoms: [],
    cards: [],
    sections: [[1, "p", [[0, [], 0, ""]]]]
  }
})

Auto-creating a blank mobiledoc if not provided may have some unwanted side effects.
Perhaps offering a public constant to a blank doc could be a compromise:
const editor = new Mobiledoc.Editor({
  placeholder: 'Write here...',
  autofocus: true,
  mobiledoc: Mobiledoc.BlankMobiledoc
})

Agreed, added this to the draft features 1.0 doc, will make a milestone or something today.

Also ran into this issue.

Minor nit: autofocus only works if Editor is created with a mobiledoc with sections. That is to say, the EMPTY_MOBILEDOC in ember-mobiledoc-editor will not suffice.

FWIW, seems like this fix doesn't work in Safari. It's unclear if it's due to something specific in our implementation or a more general problem.


Add private types. Fixes #2950

This adds private types to the language. #2950 had an RFC for it, but this PR defines the final semantics, which I'll explain now.
Basic example:
class Foo
  # private means: it can be accessed as Bar while inside Foo,
  # can never be accessed as Foo::Bar
  private class Bar
  end

  Bar.new # OK
  Foo::Bar # Error: private constant Foo::Bar referenced
end

Foo::Bar   # Error: private constant Foo::Bar referenced
::Foo::Bar # Error: private constant Foo::Bar referenced

We can start using private types where we previously could only use :nodoc: to only hide them from docs, but they could still be found and used with code. Some places where we could use them: Hash::Entry, the many iterator types, some constants in Base64, and many more places.
One can apply private to all of these: class, module, lib, enum, alias, and constants too:
class Foo
  private ONE = 1

  puts ONE # OK
end

Foo::ONE # Error: private constant Foo::ONE referenced

Like methods, private types can be seen in subclasses. For example:
class Foo
  private class Nested
  end
end

class Bar < Foo
  puts Nested # OK
end

Finally, private types can be marked at the top level: this makes them file-private, just like what using private with methods and macros at the top-level does. For example:
# foo.cr
private class Foo
end

puts Foo.new # OK

# bar.cr
require "./foo.cr"

puts Foo.new # Error

This feature is probably only useful to define types in specs that we don't want to pollute or conflict in the global namespace. For example we could use them here, here, here and many other specs.
I can understand that this last feature (file-private types) might not seem like needed, or strange, but the reason we introduced file-private methods in the first place was to define helper functions in specs without polluting the global namespace, and at least for me they have worked pretty well. I also sometimes use them in the compiler where I just want to define pure functions that don't really belong to any type, but I only need them in that file. For example here.
Private types can of course be returned from methods and used perfectly fine outside the namespace where they are defined. private only makes it impossible to reference them by name outside the namespace. For example this is valid:
class Foo
  private class Bar
  end

  def self.bar
    Bar
  end
end

p Foo.bar.new # => #<Foo::Bar:0x100393fd0>

One can't use protected with types. We could maybe think about it later, but I think just private is enough (for example Ruby has private_constant but no protected_constant).

Ohhhhh, it's a miracle. Thank you, thank you, thank you. I've been thinking about how to make a convincing RFC to implement exactly this.

I still have one concern about this PR. Why is there a difference between Foo::Bar and just Bar when inside Foo? Doesn't it make more sense to always allow full paths to any class, and simply check where you're referencing that from? I suspect that the reason ruby behaves like this is because it's implemented in the Module class which doesn't know where it's being referenced from.
I understand not being able to reference file-private types using ::Foo because they're in a "pseudo-namespace" under ::/path/to/file.cr, but it still feels a little confusing. I still think using namespaces + private modifier is a much nicer solution in almost every way than file-private types but I guess i'll just have to complain to myself.

Why is there a difference between Foo::Bar and just Bar when inside Foo?

@RX14, I'd like to note that this is consistent with the language: private methods can't be called through self (not that I necessarily like this)

@RX14 The algorithm for dealing with private types right now is pretty simple. When we have Foo::Bar::Baz, Foo is searched in the current type and all types (public and private are found). For names after then ::, they are not found if they are private. What you suggest is a big more complex, but we could consider it in the future.


nbdev_test fails with concurrent.futures.process.BrokenProcessPool exception

Similar to: https://github.com/fastai/nbdev/issues/673

Error
Was going through the tutorial using nbdev==2.0.4 on macOS.
$ nbdev_test
objc[29851]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called.
objc[29851]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
Traceback (most recent call last):
  File "/usr/local/bin/nbdev_test", line 8, in <module>
    sys.exit(nbdev_test())
  File "/usr/local/lib/python3.9/site-packages/fastcore/script.py", line 116, in _f
    return tfunc(**merge(args, args_from_prog(func, xtra)))
  File "/usr/local/lib/python3.9/site-packages/nbdev/test.py", line 86, in nbdev_test
    results = parallel(test_nb, files, skip_flags=skip_flags, force_flags=force_flags, n_workers=n_workers, pause=pause, do_print=do_print)
  File "/usr/local/lib/python3.9/site-packages/fastcore/parallel.py", line 117, in parallel
    return L(r)
  File "/usr/local/lib/python3.9/site-packages/fastcore/foundation.py", line 98, in __call__
    return super().__call__(x, *args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/fastcore/foundation.py", line 106, in __init__
    items = listify(items, *rest, use_list=use_list, match=match)
  File "/usr/local/lib/python3.9/site-packages/fastcore/basics.py", line 63, in listify
    elif is_iter(o): res = list(o)
  File<EMAIL_ADDRESS>line 559, in _chain_from_iterable_of_lists
    for element in iterable:
  File<EMAIL_ADDRESS>line 608, in result_iterator
    yield fs.pop().result()
  File<EMAIL_ADDRESS>line 445, in result
    return self.__get_result()
  File<EMAIL_ADDRESS>line 390, in __get_result
    raise self._exception
concurrent.futures.process.BrokenProcessPool: A process in the process pool was terminated abruptly while the future was running or pending.

Try 2.0.5, and also upgrade your fastcore to 1.5.11.

I was able to get the tests to run post the upgrades. Thank you @jph00
$ nbdev_test
Success.

The one change I had to make to make the tests pass was remove the following two lines which I use to get higher resolution matplotlib charts. The nbdev_test command failed with the following error when I had these two lines in the notebook.
%matplotlib inline
%config InlineBackend.figure_format = 'retina'

Error message of nbdev_test
While Executing Cell #6:
---------------------------------------------------------------------------
ModuleNotFoundError                       Traceback (most recent call last)
<ipython-input-1-0eb3525f3a9a> in <module>
----> 1 get_ipython().run_line_magic('matplotlib', 'inline')
      2 get_ipython().run_line_magic('config', "InlineBackend.figure_format = 'retina'")
      3
      4 import pandas as pd

~/Library/Python/3.7/lib/python/site-packages/IPython/core/interactiveshell.py in run_line_magic(self, magic_name, line, _stack_depth)
   2334                 kwargs['local_ns'] = self.get_local_scope(stack_depth)
   2335             with self.builtin_trap:
-> 2336                 result = fn(*args, **kwargs)
   2337             return result
   2338

<decorator-gen-101> in matplotlib(self, line)

~/Library/Python/3.7/lib/python/site-packages/IPython/core/magic.py in <lambda>(f, *a, **k)
    185     # but it's overkill for just that one bit of state.
    186     def magic_deco(arg):
--> 187         call = lambda f, *a, **k: f(*a, **k)
    188
    189         if callable(arg):

~/Library/Python/3.7/lib/python/site-packages/IPython/core/magics/pylab.py in matplotlib(self, line)
     97             print("Available matplotlib backends: %s" % backends_list)
     98         else:
---> 99             gui, backend = self.shell.enable_matplotlib(args.gui.lower() if isinstance(args.gui, str) else args.gui)
    100             self._show_matplotlib_backend(args.gui, backend)
    101

/usr/local/lib/python3.7/site-packages/execnb/shell.py in enable_matplotlib(self, gui)
     91     def enable_matplotlib(self, gui=None):
     92         "Enable `matplotlib` in a nested shell"
---> 93         from matplotlib_inline.backend_inline import configure_inline_support
     94         configure_inline_support.current_backend = 'unset'
     95         return super().enable_matplotlib(gui)

ModuleNotFoundError: No module named 'matplotlib_inline'

I looked at example notebooks on fastai to check if something else needs to be done. But, I did not see any.

Ref: https://github.com/fastai/fastai/blob/master/dev_nbs/course/lesson1-pets.ipynb

OK thanks for letting us know - tracking that in #702

@bkowshik have you tried pip install matplotlib_inline (or the conda equivalent if you're using that)?

Following the tutorial. I also get this issue on nbdev==2.1.2 and fastcore==1.5.15 on MacOS (M1) and Python 3.9.7:
objc[12963]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called.
objc[12963]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
Traceback (most recent call last):
  File "/Users/lars/.pyenv/versions/3.9.7/bin/nbdev_test", line 8, in <module>
    sys.exit(nbdev_test())
  File "/Users/lars/.pyenv/versions/3.9.7/lib/python3.9/site-packages/fastcore/script.py", line 116, in _f
    return tfunc(**merge(args, args_from_prog(func, xtra)))
  File "/Users/lars/.pyenv/versions/3.9.7/lib/python3.9/site-packages/nbdev/test.py", line 88, in nbdev_test
    results = parallel(test_nb, files, skip_flags=skip_flags, force_flags=force_flags, n_workers=n_workers,
  File "/Users/lars/.pyenv/versions/3.9.7/lib/python3.9/site-packages/fastcore/parallel.py", line 117, in parallel
    return L(r)
  File "/Users/lars/.pyenv/versions/3.9.7/lib/python3.9/site-packages/fastcore/foundation.py", line 98, in __call__
    return super().__call__(x, *args, **kwargs)
  File "/Users/lars/.pyenv/versions/3.9.7/lib/python3.9/site-packages/fastcore/foundation.py", line 106, in __init__
    items = listify(items, *rest, use_list=use_list, match=match)
  File "/Users/lars/.pyenv/versions/3.9.7/lib/python3.9/site-packages/fastcore/basics.py", line 66, in listify
    elif is_iter(o): res = list(o)
  File "/Users/lars/.pyenv/versions/3.9.7/lib/python3.9/concurrent/futures/process.py", line 559, in _chain_from_iterable_of_lists
    for element in iterable:
  File "/Users/lars/.pyenv/versions/3.9.7/lib/python3.9/concurrent/futures/_base.py", line 608, in result_iterator
    yield fs.pop().result()
  File "/Users/lars/.pyenv/versions/3.9.7/lib/python3.9/concurrent/futures/_base.py", line 445, in result
    return self.__get_result()
  File "/Users/lars/.pyenv/versions/3.9.7/lib/python3.9/concurrent/futures/_base.py", line 390, in __get_result
    raise self._exception
concurrent.futures.process.BrokenProcessPool: A process in the process pool was terminated abruptly while the future was running or pending.

I tried downgrading nbdev to 2.0.5 and downgrading fastcore to 1.5.11 as per the suggestion, but it doesn't seem to solve the issue.

@larsyencken could you please try upgrading to the latest Python 3.9 version? There’s a known macOS parallelism bug in earlier versions. Also try using latest versions of execnb, fastcore, and nbdev.

Thanks! Upgrading from Python 3.9.7 to 3.9.13 fixed it, works fine now.


Sslprofile support for lbvserver and csvserver

Added sslprofile support for lbvserver and csvserver.
Included ns_default_ssl_profile_secure_frontend sslprofile to examples.
Tested scenarios with both resource types:
[x] Set sslprofile
[x] Unset sslprofile
[x] Change sslprofile to another
Closes #13

@chiradeep can you review?
/cc @ranman166

ping @chiradeep

Can someone review and merge this PR?

@olljanat can you add a Signed-off-by

@chiradeep rebased to one signed commit now :smile:


Test gentime settings system

What

we currently have no coverage over the gentime settings system
check that config file errors, static OR runtime, are gracefully handled
check that files of correct name/place are read as expected
check that changing the settings actually has the intended effect

Why

lot of IO and state and logical branching around this, no obvious bugs here, but not obviously no bugs!

How

some kind of e2e test, multiple
we can reuse our TestProject class abstraction

The E2E tests seem to be failing. Once they are stable I can add E2E test for settings

They are passing https://github.com/prisma/nexus-prisma/runs/2614915354#step:9:65

Is it a false positive?
PASS tests/e2e/e2e.test.ts (57.338 s)
  ● Console

    console.log
      e2e test project at: /tmp/93c4a663d24ae05e8b37555bdd46f2f6

      at Object.<anonymous> (tests/e2e/e2e.test.ts:284:11)

    console.log
      e2e output:
       {
        runFirstBuild: Error: Command failed with exit code 2: npm run build
        npm WARN lifecycle The node binary used for scripts is /tmp/yarn--1621375462727-0.8140294797271534/node but npm is using /opt/hostedtoolcache/node/12.22.1/x64/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
        npm ERR! code ELIFECYCLE
        npm ERR! errno 2
        npm ERR<EMAIL_ADDRESS>build: `tsc`
        npm ERR! Exit status 2
        npm ERR!
        npm ERR! Failed at the<EMAIL_ADDRESS>build script.
        npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

        npm ERR! A complete log of this run can be found in:
        npm ERR!     /home/runner/.npm/_logs/2021-05-18T22_04_56_184Z-debug.log

        ><EMAIL_ADDRESS>build /tmp/93c4a663d24ae05e8b37555bdd46f2f6
        > tsc

        src/schema.ts(4,10): error TS2305: Module '"nexus-prisma"' has no exported member 'Bar'.
        src/schema.ts(4,15): error TS2305: Module '"nexus-prisma"' has no exported member 'Foo'.
        src/schema.ts(4,20): error TS2305: Module '"nexus-prisma"' has no exported member 'SomeEnumA'.
        src/schema.ts(33,9): error TS2339: Property 'json' does not exist on type 'ObjectDefinitionBlock<any>'.
        src/schema.ts(34,9): error TS2339: Property 'dateTime' does not exist on type 'ObjectDefinitionBlock<any>'.
            at makeError (/home/runner/work/nexus-prisma/nexus-prisma/node_modules/execa/lib/error.js:59:11)
            at Function.Object.<anonymous>.module.exports.sync (/home/runner/work/nexus-prisma/nexus-prisma/node_modules/execa/index.js:186:17)
            at Object.<anonymous>.module.exports.commandSync (/home/runner/work/nexus-prisma/nexus-prisma/node_modules/execa/index.js:225:15)
            at runTestProjectBuild (/home/runner/work/nexus-prisma/nexus-prisma/tests/e2e/e2e.test.ts:39:31)
            at Object.<anonymous> (/home/runner/work/nexus-prisma/nexus-prisma/tests/e2e/e2e.test.ts:286:19)
            at Object.asyncJestTest (/home/runner/work/nexus-prisma/nexus-prisma/node_modules/jest-jasmine2/build/jasmineAsyncInstall.js:106:37)
            at /home/runner/work/nexus-prisma/nexus-prisma/node_modules/jest-jasmine2/build/queueRunner.js:45:12
            at new Promise (<anonymous>)
            at mapper (/home/runner/work/nexus-prisma/nexus-prisma/node_modules/jest-jasmine2/build/queueRunner.js:28:19)
            at /home/runner/work/nexus-prisma/nexus-prisma/node_modules/jest-jasmine2/build/queueRunner.js:75:41 {
          shortMessage: 'Command failed with exit code 2: npm run build',
          command: 'npm run build',
          exitCode: 2,
          signal: undefined,
          signalDescription: undefined,
          stdout: '\n' +
            '><EMAIL_ADDRESS>build /tmp/93c4a663d24ae05e8b37555bdd46f2f6\n' +
            '> tsc\n' +
            '\n' +
            `src/schema.ts(4,10): error TS2305: Module '"nexus-prisma"' has no exported member 'Bar'.\n` +
            `src/schema.ts(4,15): error TS2305: Module '"nexus-prisma"' has no exported member 'Foo'.\n` +
            `src/schema.ts(4,20): error TS2305: Module '"nexus-prisma"' has no exported member 'SomeEnumA'.\n` +
            "src/schema.ts(33,9): error TS2339: Property 'json' does not exist on type 'ObjectDefinitionBlock<any>'.\n" +
            "src/schema.ts(34,9): error TS2339: Property 'dateTime' does not exist on type 'ObjectDefinitionBlock<any>'.",
          stderr: 'npm WARN lifecycle The node binary used for scripts is /tmp/yarn--1621375462727-0.8140294797271534/node but npm is using /opt/hostedtoolcache/node/12.22.1/x64/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.\n' +
            'npm ERR! code ELIFECYCLE\n' +
            'npm ERR! errno 2\n' +
            'npm ERR<EMAIL_ADDRESS>build: `tsc`\n' +
            'npm ERR! Exit status 2\n' +
            'npm ERR! \n' +
            'npm ERR! Failed at the<EMAIL_ADDRESS>build script.\n' +
            'npm ERR! This is probably not a problem with npm. There is likely additional logging output above.\n' +
            '\n' +
            'npm ERR! A complete log of this run can be found in:\n' +
            'npm ERR!     /home/runner/.npm/_logs/2021-05-18T22_04_56_184Z-debug.log',
          failed: true,
          timedOut: false,
          isCanceled: false,
          killed: false
        },
        runReflectPrisma: {
          command: 'npm run reflect:prisma',
          exitCode: 0,
          stdout: '\n' +
            '><EMAIL_ADDRESS>reflect:prisma /tmp/93c4a663d24ae05e8b37555bdd46f2f6\n' +
            '> prisma generate\n' +
            '\n' +
            'Environment variables loaded from .env\n' +
            'Prisma schema loaded from prisma/schema.prisma\n' +
            'You can now start using Nexus Prisma in your code. Reference: https://pris.ly/d/nexus-prisma\n' +
            '\n' +
            '✔ Generated Prisma Client (2.22.1) to ./node_modules/@prisma/client in 187ms\n' +
            '\n' +
            '✔ Generated Nexus Prisma to ./.yalc/nexus-prisma/dist/runtime in 298ms\n' +
            'You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client\n' +
            '```\n' +
            "import { PrismaClient } from '@prisma/client'\n" +
            'const prisma = new PrismaClient()\n' +
            '```',
          stderr: 'npm WARN lifecycle The node binary used for scripts is /tmp/yarn--1621375462727-0.8140294797271534/node but npm is using /opt/hostedtoolcache/node/12.22.1/x64/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.',
          failed: false,
          timedOut: false,
          isCanceled: false,
          killed: false
        },
        runReflectNexus: {
          command: 'npm run reflect:nexus',
          exitCode: 0,
          stdout: '\n' +
            '><EMAIL_ADDRESS>reflect:nexus /tmp/93c4a663d24ae05e8b37555bdd46f2f6\n' +
            '> cross-env REFLECT=true ts-node --transpile-only src/schema\n' +
            '\n' +
            'Generated Artifacts:\n' +
            '          TypeScript Types  ==> /tmp/93c4a663d24ae05e8b37555bdd46f2f6/src/typegen.ts\n' +
            '          GraphQL Schema    ==> /tmp/93c4a663d24ae05e8b37555bdd46f2f6/schema.graphql',
          stderr: 'npm WARN lifecycle The node binary used for scripts is /tmp/yarn--1621375462727-0.8140294797271534/node but npm is using /opt/hostedtoolcache/node/12.22.1/x64/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.',
          failed: false,
          timedOut: false,
          isCanceled: false,
          killed: false
        },
        runSecondBuild: {
          command: 'npm run build',
          exitCode: 0,
          stdout: '\n' +
            '><EMAIL_ADDRESS>build /tmp/93c4a663d24ae05e8b37555bdd46f2f6\n' +
            '> tsc\n',
          stderr: 'npm WARN lifecycle The node binary used for scripts is /tmp/yarn--1621375462727-0.8140294797271534/node but npm is using /opt/hostedtoolcache/node/12.22.1/x64/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.',
          failed: false,
          timedOut: false,
          isCanceled: false,
          killed: false
        },
        fileGraphqlSchema: '### This file was generated by Nexus Schema\n' +
          '### Do not make changes to this file directly\n' +
          '\n' +
          '\n' +
          'type Bar {\n' +
          '  foo: Foo\n' +
          '}\n' +
          '\n' +
          '"""\n' +
          'A date-time string at UTC, such as 2007-12-03T10:15:30Z, compliant with the `date-time` format outlined in section 5.6 of the RFC 3339 profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar.\n' +
          '"""\n' +
          'scalar DateTime\n' +
          '\n' +
          'type Foo {\n' +
          '  DateTimeManually: DateTime\n' +
          '  JsonManually: Json\n' +
          '  someDateTimeField: DateTime!\n' +
          '  someEnumA: SomeEnumA\n' +
          '  someJsonField: Json!\n' +
          '}\n' +
          '\n' +
          '"""\n' +
          'The `JSONObject` scalar type represents JSON objects as specified by [ECMA-404](http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf).\n' +
          '"""\n' +
          'scalar Json @specifiedBy(url: "http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf")\n' +
          '\n' +
          'type Query {\n' +
          '  bars: [Bar]\n' +
          '}\n' +
          '\n' +
          'enum SomeEnumA {\n' +
          '  alpha\n' +
          '  bravo\n' +
          '  charlie\n' +
          '}\n',
        fileTypegen: '/**\n' +
          ' * This file was generated by Nexus Schema\n' +
          ' * Do not make changes to this file directly\n' +
          ' */\n' +
          '\n' +
          'import * as PrismaClient from ".prisma/client"\n' +
          'import { core } from "nexus"\n' +
          'declare global {\n' +
          '  interface NexusGenCustomInputMethods<TypeName extends string> {\n' +
          '    /**\n' +
          '     * A date-time string at UTC, such as 2007-12-03T10:15:30Z, compliant with the `date-time` format outlined in section 5.6 of the RFC 3339 profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar.\n' +
          '     */\n' +
          '    dateTime<FieldName extends string>(fieldName: FieldName, opts?: core.CommonInputFieldConfig<TypeName, FieldName>): void // "DateTime";\n' +
          '    /**\n' +
          '     * The `JSONObject` scalar type represents JSON objects as specified by [ECMA-404](http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf).\n' +
          '     */\n' +
          '    json<FieldName extends string>(fieldName: FieldName, opts?: core.CommonInputFieldConfig<TypeName, FieldName>): void // "Json";\n' +
          '  }\n' +
          '}\n' +
          'declare global {\n' +
          '  interface NexusGenCustomOutputMethods<TypeName extends string> {\n' +
          '    /**\n' +
          '     * A date-time string at UTC, such as 2007-12-03T10:15:30Z, compliant with the `date-time` format outlined in section 5.6 of the RFC 3339 profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar.\n' +
          '     */\n' +
          '    dateTime<FieldName extends string>(fieldName: FieldName, ...opts: core.ScalarOutSpread<TypeName, FieldName>): void // "DateTime";\n' +
          '    /**\n' +
          '     * The `JSONObject` scalar type represents JSON objects as specified by [ECMA-404](http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf).\n' +
          '     */\n' +
          '    json<FieldName extends string>(fieldName: FieldName, ...opts: core.ScalarOutSpread<TypeName, FieldName>): void // "Json";\n' +
          '  }\n' +
          '}\n' +
          '\n' +
          '\n' +
          'declare global {\n' +
          '  interface NexusGen extends NexusGenTypes {}\n' +
          '}\n' +
          '\n' +
          'export interface NexusGenInputs {\n' +
          '}\n' +
          '\n' +
          'export interface NexusGenEnums {\n' +
          '  SomeEnumA: PrismaClient.SomeEnumA\n' +
          '}\n' +
          '\n' +
          'export interface NexusGenScalars {\n' +
          '  String: string\n' +
          '  Int: number\n' +
          '  Float: number\n' +
          '  Boolean: boolean\n' +
          '  ID: string\n' +
          '  DateTime: any\n' +
          '  Json: any\n' +
          '}\n' +
          '\n' +
          'export interface NexusGenObjects {\n' +
          '  Bar: PrismaClient.Bar;\n' +
          '  Foo: PrismaClient.Foo;\n' +
          '  Query: {};\n' +
          '}\n' +
          '\n' +
          'export interface NexusGenInterfaces {\n' +
          '}\n' +
          '\n' +
          'export interface NexusGenUnions {\n' +
          '}\n' +
          '\n' +
          'export type NexusGenRootTypes = NexusGenObjects\n' +
          '\n' +
          'export type NexusGenAllTypes = NexusGenRootTypes & NexusGenScalars & NexusGenEnums\n' +
          '\n' +
          'export interface NexusGenFieldTypes {\n' +
          '  Bar: { // field return type\n' +
          "    foo: NexusGenRootTypes['Foo'] | null; // Foo\n" +
          '  }\n' +
          '  Foo: { // field return type\n' +
          "    DateTimeManually: NexusGenScalars['DateTime'] | null; // DateTime\n" +
          "    JsonManually: NexusGenScalars['Json'] | null; // Json\n" +
          "    someDateTimeField: NexusGenScalars['DateTime']; // DateTime!\n" +
          "    someEnumA: NexusGenEnums['SomeEnumA'] | null; // SomeEnumA\n" +
          "    someJsonField: NexusGenScalars['Json']; // Json!\n" +
          '  }\n' +
          '  Query: { // field return type\n' +
          "    bars: Array<NexusGenRootTypes['Bar'] | null> | null; // [Bar]\n" +
          '  }\n' +
          '}\n' +
          '\n' +
          'export interface NexusGenFieldTypeNames {\n' +
          '  Bar: { // field return type name\n' +
          "    foo: 'Foo'\n" +
          '  }\n' +
          '  Foo: { // field return type name\n' +
          "    DateTimeManually: 'DateTime'\n" +
          "    JsonManually: 'Json'\n" +
          "    someDateTimeField: 'DateTime'\n" +
          "    someEnumA: 'SomeEnumA'\n" +
          "    someJsonField: 'Json'\n" +
          '  }\n' +
          '  Query: { // field return type name\n' +
          "    bars: 'Bar'\n" +
          '  }\n' +
          '}\n' +
          '\n' +
          'export interface NexusGenArgTypes {\n' +
          '}\n' +
          '\n' +
          'export interface NexusGenAbstractTypeMembers {\n' +
          '}\n' +
          '\n' +
          'export interface NexusGenTypeInterfaces {\n' +
          '}\n' +
          '\n' +
          'export type NexusGenObjectNames = keyof NexusGenObjects;\n' +
          '\n' +
          'export type NexusGenInputNames = never;\n' +
          '\n' +
          'export type NexusGenEnumNames = keyof NexusGenEnums;\n' +
          '\n' +
          'export type NexusGenInterfaceNames = never;\n' +
          '\n' +
          'export type NexusGenScalarNames = keyof NexusGenScalars;\n' +
          '\n' +
          'export type NexusGenUnionNames = never;\n' +
          '\n' +
          'export type NexusGenObjectsUsingAbstractStrategyIsTypeOf = never;\n' +
          '\n' +
          'export type NexusGenAbstractsUsingStrategyResolveType = never;\n' +
          '\n' +
          'export type NexusGenFeaturesConfig = {\n' +
          '  abstractTypeStrategies: {\n' +
          '    isTypeOf: false\n' +
          '    resolveType: true\n' +
          '    __typename: false\n' +
          '  }\n' +
          '}\n' +
          '\n' +
          'export interface NexusGenTypes {\n' +
          '  context: any;\n' +
          '  inputTypes: NexusGenInputs;\n' +
          '  rootTypes: NexusGenRootTypes;\n' +
          '  inputTypeShapes: NexusGenInputs & NexusGenEnums & NexusGenScalars;\n' +
          '  argTypes: NexusGenArgTypes;\n' +
          '  fieldTypes: NexusGenFieldTypes;\n' +
          '  fieldTypeNames: NexusGenFieldTypeNames;\n' +
          '  allTypes: NexusGenAllTypes;\n' +
          '  typeInterfaces: NexusGenTypeInterfaces;\n' +
          '  objectNames: NexusGenObjectNames;\n' +
          '  inputNames: NexusGenInputNames;\n' +
          '  enumNames: NexusGenEnumNames;\n' +
          '  interfaceNames: NexusGenInterfaceNames;\n' +
          '  scalarNames: NexusGenScalarNames;\n' +
          '  unionNames: NexusGenUnionNames;\n' +
          "  allInputTypes: NexusGenTypes['inputNames'] | NexusGenTypes['enumNames'] | NexusGenTypes['scalarNames'];\n" +
          "  allOutputTypes: NexusGenTypes['objectNames'] | NexusGenTypes['enumNames'] | NexusGenTypes['unionNames'] | NexusGenTypes['interfaceNames'] | NexusGenTypes['scalarNames'];\n" +
          "  allNamedTypes: NexusGenTypes['allInputTypes'] | NexusGenTypes['allOutputTypes']\n" +
          "  abstractTypes: NexusGenTypes['interfaceNames'] | NexusGenTypes['unionNames'];\n" +
          '  abstractTypeMembers: NexusGenAbstractTypeMembers;\n' +
          '  objectsUsingAbstractStrategyIsTypeOf: NexusGenObjectsUsingAbstractStrategyIsTypeOf;\n' +
          '  abstractsUsingStrategyResolveType: NexusGenAbstractsUsingStrategyResolveType;\n' +
          '  features: NexusGenFeaturesConfig;\n' +
          '}\n' +
          '\n' +
          '\n' +
          'declare global {\n' +
          '  interface NexusGenPluginTypeConfig<TypeName extends string> {\n' +
          '  }\n' +
          '  interface NexusGenPluginFieldConfig<TypeName extends string, FieldName extends string> {\n' +
          '  }\n' +
          '  interface NexusGenPluginInputFieldConfig<TypeName extends string, FieldName extends string> {\n' +
          '  }\n' +
          '  interface NexusGenPluginSchemaConfig {\n' +
          '  }\n' +
          '  interface NexusGenPluginArgConfig {\n' +
          '  }\n' +
          '}'
      }

      at Object.<anonymous> (tests/e2e/e2e.test.ts:289:11)

No, it tests that the first build fails, then after reflection passes

Thank you for explaining. I find it a little confusing but at least I know to ignore it now...


Revert "industrial_core: 0.7.2-1 in 'melodic/distribution.yaml' [bloom]"

As per subject.
Reverts ros/rosdistro#30043
Let's unblock Melodic, we'll fix it later.

@clalancette FYI

@clalancette: what's the window for getting a fixup release in?
I found an easy bw-compatible fix which doesn't require reverting 0.7.2 completely.
I'm waiting on some user feedback before creating a new release.

#30230


Failed to download ‘gnu’ archive behind proxy

Observed behavior
I do have a working proxy setup for other program(e.g. curl, browser, python). But doom-emacs failed to install.
INSECURE=1 make install wouldn't help.

stdout: click to expand
make --trace install
Makefile:87: target '.local/autoloads.el' does not exist
emacs --quick --batch --eval '(setq user-emacs-directory default-directory)' -l core/core.el -f doom-initialize-autoloads
Installing core packages
Importing package-keyring.gpg...
Importing package-keyring.gpg...done
Using a proxy for https...
Contacting host: localhost:3128
Failed to download ‘gnu’ archive.
Package refresh done
Failed to download ‘melpa’ archive.
Eager macro-expansion failure: (error "Package ‘persistent-soft-’ is unavailable")
Installing core packages
Importing package-keyring.gpg...
Importing package-keyring.gpg...done
Failed to download ‘gnu’ archive.
Package refresh done
Failed to download ‘melpa’ archive.
Eager macro-expansion failure: (error "Package ‘persistent-soft-’ is unavailable")
Installing core packages
Importing package-keyring.gpg...
Importing package-keyring.gpg...done
Contacting host: localhost:3128
Failed to download ‘gnu’ archive.
Package refresh done
Failed to download ‘melpa’ archive.
Package ‘persistent-soft-’ is unavailable
Makefile:87: recipe for target '.local/autoloads.el' failed
make: *** [.local/autoloads.el] Error 255

Steps to reproduce

export https_proxy=http://localhost:3128
git clone https://github.com/hlissner/doom-emacs ~/.emacs.d
cd ~/.emacs.d
cp init.example.el init.el  # maybe edit init.el
make install

System information

Click to expand
DOOM Doctor
Running Emacs v25.3.2, commit 5dacbb7cb1c6ac246a9ccd15e6c4290def67757c

shell: /bin/bash
Compiled with:
  XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND GPM DBUS GCONF GSETTINGS
  NOTIFY LIBSELINUX GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF XFT ZLIB
  TOOLKIT_SCROLL_BARS GTK3 X11 MODULES
uname -a:
  Linux cnbjlx23123 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19
  11:48:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Attempt to load DOOM: failed
  (Cannot open load file No such file or directory async-autoloads)

----

test-emacs
test-windows
test-fonts
test-gnutls
test-tls
Validated https://elpa.gnu.org
Validated https://melpa.org
Validated https://self-signed.badssl.com (this shouldn’t happen!)
Validated https://wrong.host.badssl.com/ (this shouldn’t happen!)
test-tar

====
Have some debug information:

  + byte-compiled files:
    n/a

  + exec-path:
    /home/CORPUSERS/288xxxxxx/bin
    /home/CORPUSERS/288xxxxxx/.local/bin
    /usr/local/sbin
    /usr/local/bin
    /usr/sbin
    /usr/bin
    /sbin
    /bin
    /usr/games
    /usr/local/games
    /usr/lib/x86_64-linux-gnu/emacs/25.3/x86_64-linux-gnu

  + PATH:
    /home/CORPUSERS/288xxxxxx/bin
    /home/CORPUSERS/288xxxxxx/.local/bin
    /usr/local/sbin
    /usr/local/bin
    /usr/sbin
    /usr/bin
    /sbin
    /bin
    /usr/games
    /usr/local/games

----
There were issues!

The install goes well if I forward tcp traffic to a local transparent proxy.
It can't go through the https_proxy for some reason.

I use proxychains ,It work fine.

Do the answers in https://stackoverflow.com/questions/1595418/emacs-behind-http-proxy#1595673 help you? I've never used Emacs behind a proxy, so I'm afraid I know little about it, but the link above looked promising.

Thanks for the suggestion.
Answer in the link above do not help. I feel like it is our cooperate proxy that causing this trouble. Emacs did picking up the proxy setting from environment.

So I've run into this issue but was able to solve it by adding in the proxy information at the top of early-init.el. The problem now is that if I want to pull the latest commits I need to remove then add this code back each time, and attempting to add it to my own config.el stops the doom script from using the proxy. Is there a preferred/better way to add user customizations to early-init @hlissner ?

@Vezill Will adding them to ~/.doom.d/init.el not work?

I originally had them in ~/.doom.d/config.el, but moving it into the top of ~/.doom.d/init.el looks like it worked, thanks for the tip. I originally didn't want to modify that file to make diffing it with the example one easier, but this works fine.


Cannot Add Normal Form

If we need to add a non modal Form  using  simply this:
Dim Form As New Form4
  Form.Show()

It would simply Show a non responding Form  if i add
Form.ShowDialog()
it works but it wont get all the features as  a non modal Form how can i make it work as normal  .Show() ?
To Be More Specific The issue is in the following in the file:
Form1.vb
When it receves the message from the client it wont open the any kind of not Modal Form it would just get stuck on Loading and not Responding so if i do:
 Private Sub S_Data(ByVal u As USER, ByVal b() As Byte) Handles S.Data
        Dim DATA As String() = Split(BS(b), RKEY)
        Try
            Select Case DATA(0)
Case "ANY"
        Dim Form As New Form4
              Form.Show()

Form.Show() would get stuck seems like if some loop is running so it blocks the form to run
Please look at your code and see what is wrong
Best Regards

Because there is a bug in class SK. however, it's too late fix it because I'm already doing a new update, I may release it in few days.


Set ID on checkbox input

Feature request
Simple feature request here. When supplying an ID to a checkbox root primitive the ID is set on the button and not the input. This raises errors like:

It'd be nice to be able to supply on the ID on the input component instead. Thanks.

This was a mistake on my end, disregard. Thanks.


Implement get for RTDB queries

go/rtdb-get

@schmidt-sebastian @paulb777 This PR was failing CI checks for two reasons:

The added tests interfered with other tests in the suite (goOnline/goOffline) is required (code)
The CI in firebase-ios-sdk was still using 4.7.2 (this was addressed in https://github.com/firebase/firebase-ios-sdk/pull/7250)
Per Paul's recommendation, I added scripts/run_database_emulator.sh to the github workflow paths so that emulator version bumps trigger CI checks (pr)

The only change here is the goOnline/goOffline handling. Sebastian, could you have a look and rubberstamp?

@schmidt-sebastian @paulb777 This PR was failing CI checks for two reasons:

The added tests interfered with other tests in the suite (goOnline/goOffline) is required (code)
The CI in firebase-ios-sdk was still using 4.7.2 (this was addressed in https://github.com/firebase/firebase-ios-sdk/pull/7250)
Per Paul's recommendation, I added scripts/run_database_emulator.sh to the github workflow paths so that emulator version bumps trigger CI checks (pr)

The only change here is the goOnline/goOffline handling. Sebastian, could you have a look and rubberstamp?


Misc: Revisit Version Requirements

I'm currently only requiring Python 3.6, but there is code in the package that will only work for 3.8 or higher. I need to decide if I want to refactor that code or bump the minimum Python version up to 3.8 (or perhaps higher). Currently leaning toward increasing the version requirement, in which case it'll be worth considering whether to increase requirements for mkdocs and/or mkdocstrings.

Decision:

Upgrade Python requirement: 3.6 -> 3.8
Upgrade mkdocs requirement: 1.4.0 -> 1.6
Upgrade mkdocstrings requirement: 0.19.0 -> 0.23.0


[Feature] soul create event

Hello, first of all, thanks for this splendid plugin!
I'd love it if there was a cancellable event fired before creating a soul. This would allow other developers to integrate support for the plugin in their own work.
A cancellable event along the lines of PreSoulCreateEvent, that exposes the Player, Location and perhaps the death reason would be awesome.
I'm also requesting that such API be published on maven central or jitpack.io, whichever one would be easier for you to setup. I would be willing to lend a hand if you run into trouble publishing to either repository.

Sure thing I'll take a look when I get a chance. I've never written an API before for a Minecraft plugin so I'll reach out if I need any help!

Sounds good 👍
My recommendation would be to just create a package like dev.faultyfunctions.soulgraves.api.event and put the new event class (or kotlin equivalent) in there.
(This is mostly just to make it obvious to other developers where to look for stuff they can use/interface with)
Figuring out publishing to a maven repository is pretty easy with jitpack: https://docs.jitpack.io/building/.


Can't integrate easily, lots of non sense errors

Please look at this question:
http://stackoverflow.com/questions/35200822/glossy-ios-doesnt-conform-to-protocol

hi @HamedMP - can you link me to a sample project where you're experiencing these issues?

As mentioned on StackOverflow - you're on Xcode 7.2 which comes with Swift 2.2. Gloss was last updated with Swift 2.1. I'll add a task for myself to update. If the functionality Gloss provides is needed before that happens, a different library should be used.

Hi hkellaway, first congratulations, its really nice library for json to object, but i am having issues when i convert object to Json with toJSON. The sample toJson is below. its creating ( brackets instead of { and has = sign instead of : in key value. So its not a valid json. Only URL are wrapped in double quotes other strings are not..  So could please help me clarify what setting needs to be set to get the correct json. Note: i ran your sample program i still got the same answer..
["products": (
{
"id_dt_ot_product" = 1;
"product_image" = "HTTPS://UPLOAD.WIKIMEDIA.ORG/WIKIPEDIA/COMMONS/7/7C/CAPPUCCINO_CHIANG_MAI.JPG";
"product_name" = CAPPUCCINO;
}
)]

@Pericharan thanks!
it sounds like what you're describing is simply what JSON looks like when printed out in Xcode's console. accessing that JSON in code would be as expected.

@HamedMP - so i ran the project with both Xcode 7.2 and 7.3, with no issues; so i'd say my theory is incorrect.
if you try what this user on StackOverflow suggests and have any luck let me know http://stackoverflow.com/a/35201355/3777116

closing due to 2+ weeks of inactivity. the next version, 0.7.0 was just released - if desired, give that a try and submit another issue if you run into errors.


OCPBUGS-31444: use dnsPolicy: Default for konnectivity-agent in data plane

What this PR does / why we need it:

Fix coreDNS interworking
With the change, konnectivity-agent in data plane will use the name resolution configuration from the node
This makes sure that the konnectivity-agent's proxy-server-url can be resolved even if coreDNS is down or mis-configured
konnectivity-agent control plane shall not change as it still needs to use coreDNS as in that case a ClusterIP Service is configured as proxy-server-url

Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes https://issues.redhat.com/browse/OCPBUGS-31444
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/ok-to-test

/jira refresh

/retest

/retest

This cannot be done and is needed in Satellite (this hooks into some of the configuration Satellite link provides in the base of a location for proxying connections through satellite link for Hypershift Satellite locations.
Can consider doing public cloud only but cannot be in Satellite

Thanks @relyt0925 . I understand that this would break that.
Any suggeston? Do you have any parameter which differentiate public cloud and satellite?
Thanks!

Thanks @relyt0925 . I understand that this would break that. Any suggeston? Do you have any parameter which differentiate public cloud and satellite?
Thanks!

@mihivagyok Yes, here are some code examples showing how we can determine if this is Satellite (i.e. UPI).
  platform:
    type: IBMCloud
    ibmcloud:
      providerType: "{{ hypershift_providertype_map[cluster_default_provider|default('softlayer')]}}"

hypershift_providertype_map:
  g2: "VPC"
  softlayer: "Classic"
  upi: "UPI"

	if hcp.Spec.Platform.IBMCloud != nil && hcp.Spec.Platform.IBMCloud.ProviderType == configv1.IBMCloudProviderTypeUPI {
		ibmCloudUPI = true
	}

@relyt0925 @hasueki @rtheis I have updated the code. Please take a look! Thank you very much!

@relyt0925 PTAL

/lgtm

/remove-hold

/approve

/cherry-pick release-4.15


BUG: Website is not access able on iPhone and Mac Safari! Only Chrome on macOS works

Hi!
The website is not access able on my iPhone.
On the Mac using Chrome no issues, but Safari doesn't work either! Only Chrome works.
Will this help?

Thanks
URBANsUNITED

Yes, it was very helpful.
I don't have a Mac or an iPhone, so I can't test it, but I think it should be working now, could you check

Not yet solved, new error:

Can you try again?

WORKS! 👍🏼
Great! Many thanks ☺
But the picture rendering is much slower then on Chrome. On the same machine.
iPhone Safari and Chrome = equal speed, but on macOS is Chrome much faster compared to Safari.
I am talking about the transform from blur to sharp picture to full sharp.
The dev console gave no error, maybe a general "problem"!?! iPhone is an 11'er, so power enough...
Cheers

Perhaps there is some issue with react-spring and safari, like here. I'll set up virtual machine with macOS next week and try to fix it


Color/opacity contrast (accessibility)

We're using the Coy theme — I noticed that some things (like .namespace) have opacities lowered, which brings the text below the contrast ratio. Also noticed many of the other themes have contrast issues, too.

Hi! Don't hesitate to override Prism's themes styles if they don't fit your requirements. Or provide a PR so that we can include this improvement in the project, if every maintainer agrees.


Indoor and outdoor temperature

Following what is shown in NetHome Plus for Midea it shoud be sothething like:
They count (d - 50) / 2 as double but put only integer of this.
So this is exactly what should be in decode_temp:
def decode_temp(d: int) -> Optional[float]:
    return (int((d - 50) / 2) if d != 0xFF else None)

Next we have to add part after dot but must depend on temperature value odd or even:
if self.indoor_temperature:
    if self.indoor_temperature < 0:
        self.indoor_temperature -= (payload[15] & 0xF) / 10
    else:
        self.indoor_temperature += (payload[15] & 0xF) / 10

if self.outdoor_temperature:
    if self.outdoor_temperature < 0:
        self.outdoor_temperature -= ((payload[15] & 0xF0) >> 4) / 10
    else:
        self.outdoor_temperature += ((payload[15] & 0xF0) >> 4) / 10

You can simplify if needed :)
After those changes we can see exactly what recomended NetHome Plus for Midea shows.
Perhaps they make a mistake taking only int part of temperature but to who we can believe?

        if self.indoor_temperature:
            #self.indoor_temperature += (payload[15] & 0xF) / 10
            self.indoor_temperature += ((payload[15] & 0b00001111) - 5) / 10
        if self.outdoor_temperature:
            #self.outdoor_temperature += (payload[15] >> 4) / 10
            self.outdoor_temperature += (((payload[15] & 0b11110000) >> 4) - 5) / 10

Thanks for the information. What's your reference for this change?

I updated earlier post.

I had to chanche again.
There was problem around -0.5 degrees.
Following what is shown in NetHome Plus for Midea it shoud be sothething like:
So now the code look like this:
if self.indoor_temperature:
    if self.indoor_temperature < 0:
        self.indoor_temperature = int(self.indoor_temperature) - (payload[15] & 0xF) / 10
    else:
        self.indoor_temperature = int(self.indoor_temperature) + (payload[15] & 0xF) / 10

if self.outdoor_temperature:
    if self.outdoor_temperature < 0:
        self.outdoor_temperature = int(self.outdoor_temperature) - ((payload[15] & 0xF0) >> 4) / 10
    else:
        self.outdoor_temperature = int(self.outdoor_temperature) + ((payload[15] & 0xF0) >> 4) / 10

It looks they take negative 0.5 degree and later int od this.


Fix thread leak in WMI sampler

What does this PR do?
Fixes #5655. There is a thread leak in the sampler class which means that transient instances leave a thread behind. This PR implements the python with construct to allow the check class to dispose of the sampler used by tag queries.
Motivation
The current code causes the agent to stop working, and can make the host server unstable
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached

@rlaveycal Thanks a ton for answering the feedback provided earlier.
In order to minimize the diff and associated QA work on our side, I reverted several changes on this PR that do not participate to strictly fixing the thread leak, in particular:

Refactor ._query() and .get_connection() by reusing the locator (it's actually not clear to me anymore that this is would bring much value - how heavy is it to create a locator each time?).
Log exceptions that occur when sampling. (Besides, the code was swallowing the exception, which is almost always not a good idea. If you'd like to log the exception because the Agent can't log exceptions occurring in threads, feel free to provide a new PR that also makes sure the exception is re-raised after being logged. :-))
"Paranoia" deletion of the connection object — in the current implementation the Python GC should take care of that automatically (since we don't store any reference to the return value of the .get_connection() method).

Feel free to provide tightly-scoped PRs for any of the following in the future — we greatly appreciate your contributions!

One other point that might be interesting to look at in the future here…
This check still uses the Agent 5 signature, which hints me to think that it was created (and designed) for when the Agent was able to run multiple instances for a given check. Since we now run on a 1 instance = 1 Check class instance basis, it's not clear to me that we need to multithreaded approach anymore. Indeed, it seems one WMISampler is created based on properties that depend on the instance only (needs to be confirmed though), so we will only ever have one WMISampler per check. This makes the execution mostly sequential now, since the query_loop blocks until we call .sample() from the outside. So my intuition tells me it should be possible to get rid of all the multithreading, and just make blocking calls to the WMI API from within the check code.

Note that CI is failing on some integrations here because CI secrets aren't set for @rlaveycal's fork (known issue). @AlexandreYang triggered a build in https://github.com/DataDog/integrations-core/pull/5810 as a workaround — CI is passing there. ✅


BLD: macosx_arm64 wheel build on GHA instead of cirrus

Reduces load on cirrus ($$) by building macosx_arm64 wheels on GHA instead.

Looks good to me, thanks Andrew. It's unclear to me from the Cirrus logs why the Linux aarch64 now failed. Probably a simple timeout on installing the uploader?

I think we're good to go now. The wheels are all building successfully and the docs are ok.

I kicked off wheel builds from main on GHA, so the nightlies get refreshed.


Proposal for responsive site design refresh

Several weeks ago, I began an effort to clean up the Git site's CSS. My hope of having a clean enough starting point to begin making the site more responsive (per #1084). The CSS was a complete mess – the great majority of it my fault – and I realized that even after making the new linter happy and fixing the overly deep nesting, etc., we'd still wouldn't be in a good place for introducing responsive rules.
I decided to take a step back and see how feasible it might be to start fresh with all new CSS. I took a sample documentation page and spiked a new layout with Tachyons.

Sample page design
👉  https://nugit.now.sh 👈

Screenshots

My original intention wasn't to do a true redesign, but I think a minor refresh is in order after 6 years.
A few updates:

Responsive (duh).
Use a more modern system font stack.
Use SVG icons from open source Feather project.
Move main nav to top.
Better text contrast.
SVG logo.

Things to figure out:

How and if to structure the IA. E.g. I feel like the Book should be a top level section, but we'll learn more once we begin collecting analytics again.
How to handle secondary navigation links. Current thought is to use the collapsing (and expandable on mobile) sidebar like in the page above.
Perhaps further minimize JS with <details> / <summary> for expandable sections.
Probably most importantly, getting some sort of staging site set up that we can deploy to and have the community test out.

If folks are ok with this general direction, I'd like to begin updating the site. Most of the work will be on the front end and a fellow GitHub designer has offered to help out. Minor Rails tweaks may be needed and I have a volunteer for that as well (plus anyone else that wants to lend a hand).

This looks awesome @jasonlong 🎉
For comparison, the current equivalent of the above design: https://git-scm.com/docs/git-shortlog

Screenshot of current page

At first sight it seems in the right direction.
One of the major problems was reported on #359, and it is fixed with the new design :)
Just 2 topics:

I've seen many articles criticising the burguer menu recently (I don't have any in specific, but google is full of those). But if you feel it's the right choice I'm happy with that.

The <pre> elements in mobile have an UX problem I hate personally: it's not easy to understand you can (and sometimes you need in order to see everything) scroll horizontally. What are your thoughts? Can we find a better solution?

I've seen many articles criticising the burguer menu recently

I feel like the initial backlash has fizzled out and now the metaphor (while not ideal) is so ubiquitous in a mobile context that it's perfectly fine to use.

The  elements in mobile have an UX problem I hate personally: it's not easy to understand you can (and sometimes you need in order to see everything) scroll horizontally.

Viewing code snippets on a small device isn't an ideal experience no matter what you do. You can choose to wrap long lines, but that breaks a lot of uses where the author was relying on specific whitespace.
On a more practical note, the <pre> tags and the rest of the documentation markup comes from the backend tooling (asciidoc?) and I've never had control over the output. I mean, I'm sure we could request changes, but it's possible to style the existing markup just fine.

I want to help with this, it's fantastic!

@jasonlong I agree that reading code snippets on mobile or other similar devices is never going to be great, but just like in the desktop/notebook browser you have the vertical scrollbar always visible, can't we have some horizontal scrollbar present in the snippets?
while not beautiful (maybe we can find a nice solution), at least the readers would know immediately that they should scroll because some info may be missing.
I know some of the content comes from the asciidoctor (at least the book content, and probably the man pages also?), and if needed maybe we should invest some time looking for important asciidoctor updates or other alternatives (never been through that part of the site, so can't really say if it would be too much work)
Nevertheless this seems an huge improvement, and I am available to help in anything you need of course (reviewing, testing, and coding)

One thing that would be pretty easy would be to add an ::after pseudo-element with a content attribute of Drag to scroll or something on those <pre> tags on smaller viewports.

This is awesome.
Happy to lend a hand here as I’ve been working with Tachyons for roughly a year now — would love to contribute and share ideas for enhancements, open items, etc.

@laurendorman Awesome. If you have any feedback on my Tachyon usage thus far, definitely let me know. The repo for this spike is https://github.com/jasonlong/nugit.

This is so pretty. Good work!

@jasonlong I think everyone is with you on this :) How can we help making this happen?

@pedrorijo91 I've begun working on this in a local branch. I think the most useful thing here will be to get a secondary testing/staging Heroku instance spun up (not sure if their Flow feature makes sense here?) . We'll also need to be careful about making sure updates in master find their way into the new branch.

I think only @peff has permissions to setup that

The heroku app is owned by a team account, so if there's anybody interested in setting up a pipeline with a staging instance, I can add you to the team (@pedrorijo91, I think you're already on the team, but let me know if you run into any permissions problems). It's something I think would be useful to have set up for reviewing all PRs, but I just haven't had time to look into it (and I doubt I will in the near future, either).

I will have a look then. I played with a simpler version of this feature 2 years ago, I supposed it should be as easy to setup as it was. just one thing before doing any action: how does the billing work @peff? Spinning up apps for every PR may affect the monthly bill.
we may also have to do some work to populate the DB when launching a new app (assuming it will launch a new app with a new DB), or having a staging DB that the app should connect to. Will try to have a look on that

how does the billing work

We have credits from Heroku that cover the regular billing. I don't know how high those credits would go if we add more services. Any uncovered bill goes to my personal credit card. So please don't add things that cost money. ;)
If we have an idea of what the costs might be, I can talk to the heroku folks about covering it with credits. But I assumed we would be able to spin up free hobby-level dynos for pipeline test-sites. They'd not have any real traffic hitting them.

we may also have to do some work to populate the DB when launching a new app

I think there's some facility to clone (maybe with copy-on-write?) the production database for test sites. But I've never actually tried it. Our needs are actually pretty simple; read-only access would be fine, since the regular site never writes to the database (it's only written during the scheduled rake tasks to suck in book/manpage content).

Since there were no objections to the new direction and with @tarebyte and I working on the updates, I think it's safe to close this. We can take up further logistics discussions separately.

New project board here: https://github.com/git/git-scm.com/projects/2

@jasonlong I really like what you did there. Would you be game to do the same responsive work for Git for Windows (https://github.com/git-for-windows/git-for-windows.github.io)? (The current version was made "responsive" by myself, and my level "Inept" at web design shows...)

@dscho Doing this responsive work has meant starting from scratch with all new CSS. My focus is going to be on this side project for a while, so I can't guarantee if/when I'll have cycles to help on the Windows site. If nothing else, maybe someone else in the community can take what we end up with here as a foundation for that site.


Cannot render route's component when the page was translated to other language

Uncaught DOMException: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
Error when the page was translated to other language (chrome browser translate feature), when I click the Link and it should render the component route, but it's not render the component of the route.

The browser is manipulating the DOM outside of React's control, and React doesn't like that. This doesn't have anything to do with React Router.


How can I change tooltip structure ?

is there any way to change tooltip structure ?
I have multiple lines in single chart it shows long list on mouse hover.
If I have 16 lines then it creates 16 rows for tooltip.

Yes, you can use the tooltip.content setting to override the tooltip and completely customize it so that it will look any way you want.
http://c3js.org/reference.html#tooltip-contents

Thank You!


Pod Lifecycle - Completed

Should we also add the lifecycle state of "Completed"? I created a pod that prints a random number and then completes. RestartPolicy is set to Never, and now the POD state is "Completed"

/language en
/kind support

Hi @tushartgupta, can you elaborate your issue in detail.
Do you want some change in Kubernetes docs, if yes, then can you provide link to the doc?

/remove-kind support
Maybe there is room to improve a page in the documentation.


Harmonize the aws profile option

Description
I would like the --awsProfile to change to --profile to match the AWS CLI.
Use Case
To make it easier to switch between various AWS CLIs
Proposed Solution
Change this line I believe: https://github.com/aws/amazon-genomics-cli/blob/884308fc2b7e00d918c57e8a912957076309dde2/packages/cli/internal/pkg/cli/flag.go#L33
Other information
NA

Seems reasonable. To retain backward compatibility we would probably retain --awsProfile and call the same logic from --profile.
We use Cobra for command line parsing which in turn uses PFlag for flags. PFlag allows flag aliasing

I can try to make a PR, a first for me for Go.


TEST: Mongo image updates

Overview
The mongo:latest image, which at the time of authoring this PR is MongoDB v6.0, is not compatible with Ruby 2.4 and below. Ruby 2.4 and below were testing fine using mongo:5.0.11.
This PR runs the multiverse database group using all tested Ruby versions to ensure a condition for the installed Mongo image does not create any problems.
This is a test PR to evaluate the validity of #1450
Relates to: #1351
Submitter Checklist:

[ ] Include a link to the related GitHub issue, if applicable
[ ] Include a security review link, if applicable

Testing
The agent includes a suite of unit and functional tests which should be used to
verify your changes don't break existing functionality. These tests will run with
Github Actions when a pull request is made. More details on running the tests locally can be found
here for our unit tests,
and here for our functional tests.
For most contributions it is strongly recommended to add additional tests which
exercise your changes.
Reviewer Checklist

[ ] Perform code review
[ ] Add performance label
[ ] Perform appropriate level of performance testing
[ ] Confirm all checks passed
[ ] Add version label prior to acceptance

Closing, as all multiverse DB test groups are passing and the logs show the correct version is being downloaded.


[Feature Request]: In Python how to assign types to multi-output tags?

What would you like to happen?
I have a multi-output DoFn:
    class DoFn1:
        def process(self, row) -> Iterable[Union[Dict[str, Any], pvalue.TaggedOutput]]:
            if something:
                yield some_dict(...)
            else:
                yield pvalue.TaggedOutput("bad", ...)

And another DoFn that consumes its outputs
    class DoFn2:
        def process(self, row: Dict[str, Any]) -> Iterable[...]:
            if something:
                yield some_dict(...)
            else:
                yield pvalue.TaggedOutput("bad", ...)

And then when I use it like this:
    pcoll = ...
    pcoll = pcoll | "dofn1" >> beam.ParDo(DoFn1()).with_outputs(
        "bad",
        main="good",
    )
    pcoll["good"] | "dofn2" >> beam.ParDo(DoFn2())

I get an error that looks like this:
apache_beam.typehints.decorators.TypeCheckError: Type hint violation for 'dofn2': requires Dict[str, Any]
but got Union[Dict[str, Any], TaggedOutput] for row

How can I tell Beam type checking that the good tag gives Dict[str, Any], and bad gives TaggedOutput? Am I forced to propagate the tagged output type hints?
Also asked in SO here if not appropriate for Github: https://stackoverflow.com/questions/76151787/in-apache-beam-dataflow-multi-output-dofns-how-do-you-assign-type-hints-to-spec
I found a related discussion here: https://github.com/apache/beam/pull/9810
Issue Priority
Priority: 3 (nice-to-have improvement)
Issue Components

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

Have you tried using .with_input_types ? https://github.com/apache/beam/blob/c31243ece6a78e46ea2a25147643143d0ab20d93/sdks/python/apache_beam/transforms/ptransform.py#L871

@tvalentyn I'm not quite understanding what you mean. I think this issue is more referring to the fact that it doesn't really seam possible to set the return type of a expand to be either a Tuple or a TaggedPCollection so that you get typed outputs for each of the keys/indexes.
I'm stuck on this as well breaking both static typing with a warning
WARNING  | apache_beam.typehints.decorators:strip_pcoll_helper:381 - This output type hint will be ignored and not used for type-checking purposes. Typically, output type hints for a PTransform are single (or nested) types wrapped by a PCollection, PDone, or None. Got: Tuple[apache_beam.pvalue.PCollection[XXX], apache_beam.pvalue.PCollection[YYY]] instead.

Nor can I perform runtime type-checking correctly

In the context of example in the description, I am asking whether we tried to replace
    pcoll["good"] | "dofn2" >> beam.ParDo(DoFn2())

to
    pcoll["good"] | "dofn2" >> beam.ParDo(DoFn2()).with_input_types(<correct typehint for elements belonging to good pcoll, which seems to be Dict[str, Any]>)

also cc: @jrmccluskey who is an expert on this topic.

Any updates on this?  I am having trouble with the same thing as the OP.

@lazarillo have you tried using with_input_types on transforms that consume tagged output?

Yes, I have.  I think you are correct and it will solve the issue.  Unfortunately, I have multiple issues going on, so for the moment, I cannot fully confirm that it worked.

I tried this approach with beam.io.WriteToCsv without success.

@robmoore could you elaborate please?

Certainly. I tried using beam.io.WriteToCsv(...).with_input_types(...) for one of my tagged outputs passing in my named tuple subclass as the type. The typing hint apparently was ignored.

Hmm, did you get a type hint violation error? Is there a minimal example that you can provide by chance?


Update columnar stats tracker API to pass file path for new batches

This updates the columnar stats tracker newBatch API to pass the output file path the batch will be written to.  It's essentially the columnar form of the row-based task stats change as part of SPARK-26164.
This also fixes some potential leaks that could occur if the newBatch callback on a stats tracker were to throw.

build

Retargeted to 22.12, as this is a prerequisite for Delta Lake write support which is desired in 22.12 per @sameerz.

build


Update VMBoxes.php

Add VMBoxes messages() method corresponding to API feature.

Perhaps this should be getMessages() ?


BADGE REQUEST [LossLofi#3109]

What is your Discord Tag?
LossLofi#3109
What is your UID (User ID)?
842526957697630258
What is the image for the badge that you want? Please make sure that the image is hosted on a trusted domain, such as i.imgur or cdn.discordapp.
https://cdn.discordapp.com/avatars/842526957697630258/6474dfb8e7357752b767d9ffd3c01c24.png?size=1024
Additional Confirmation:

[x] My badge does not contain any NSFW material. (It does not.)
[x] My badge is not a badge that signifies that I am an official developer / staff for Discord or client mod communities. (It does not.)

image does not exist.


feat(payment): STRIPE-280 using addressFormSkeleton instead spinner for stripeLink components

What? STRIPE-280
The spinner is to be replaced by addressFormSkeleton in order to get the same UX
Why?
The Checkout team introduced new CSS loading skeletons to the checkout, replacing the loading spinners so that the checkout feels faster and more responsive.
Testing / Proof
Customer

Shipping

Demo (pending......)
@bigcommerce/checkout @bigcommerce/apex-integrations

💚 Tested!
QE Details:
PR is working as expected, spinning loaders is not displaying as per acceptance criteria.
Following scenarios have been validated:

Shopper login via stripe link.
Shopper edit shipping and bulling addresses.
Shopper logout
2nd shoppers is login and edit shipping address.

Note: Spinning loader animation is only available when shopper place the orders.
Please review attached recording videos with validation details.
https://user-images.githubusercontent.com/82106950/215625452-573436bb-3c44-4021-af3f-1d112b163420.mov
https://user-images.githubusercontent.com/82106950/215625502-b6f6d5d0-4cb2-4c9d-b819-c03f07a69eea.mov
https://user-images.githubusercontent.com/82106950/215625567-e7afbf00-f281-4451-b86b-6def3a315363.mov


adds github bounty account to known wallets

as can be seen here, a new bounty wallet has been created, especially for the github bounties. i am guessing all github bounties will be paid through that wallet from now on - @boldninja might be able to confirm?
i set the name to "ARK GH Bounty" to keep it short, i hope that's fine!

I would make it ARK GitHub Bounty, not everyone necessarily knows what GH stands for.

changed accordingly!


IMG src has no value, resulting in a blank canvas. Any idea what i am doing wrong?

An callback would be really nice. In the meantime I'm using SetTimeout(). Since a timeout for as little as 2ms was enough for rendering I'm using 100ms. Hopefully it is enough for all users and not to long for the impatient ones.


sin function

how to train the parameter in sin function. I don't find it in the project

how to train the parameter in sin function. I don't find it in the project

Is there any update about this issue?
I'm also wondering how the precomputed harmonic instance embeddings can be derived, since they are provided in the sample projects.


Theme Toggler

Describe the bug
The Theme Toggler is coming out of the navbar and not looking I can fix it and make some changes with the cards.
Reproduction
...
System Info
..

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

I guess that's related with this PR https://github.com/jellydn/dapp-starter/pull/1061/files Thanks.


Upgrade from Alpine 3.13.5 → 3.14.3

3.15.0 was just released today
https://alpinelinux.org/posts/Alpine-3.15.0-released.html

3.15.0 was just released today

I know, but I thought I would give it some time to mature... Maybe upgrade when we have 3.15.1?
Or is there anything in the 5.15 kernel that would be important to get right away?


How to access vars in included templates

P.S. I'm not sure if this is righ place to ask questions but not to report bugs.
My template is so big that I simply want to divide it into parts - like modules or units or files in programming.
The question is - how can I access (in my main template) variables that were defined with {% set %} by included template?

You can ask your question at users mailing group https://groups.google.com/forum/#!forum/twig-devs

You cannot do this. Including a template means that you render the template and put the output in this place. You don't have access to the structure of the included template.

So any {% set %} called in sub-template will be destroyed after renderint it, correct?

Koc, thanks, I joined mailing group

@meglio: that's correct.