qa_crowbarsetup: add hybrid/ldap test

:+1:

:+1 for code (have you tested the connection to ldap?)

we tested it by manually pasting snippets during development
and are doing a full fresh run with it atm

Looks good. After the want_ldap=1 mkcloud finished, I can do on the dashboard node
keystone user-get bwiedemann
keystone user-get 82608

to get details


FeedbackPrompt test (snapshot)

@ethanbb : If I don't get a chance and you have some free time, can you take a look at what's failing?

Looks like the support/netlify directory doesn't exist - probably just needs another pull from dev.

@Butterwell : Could you update to be in sync with the latest dev changes?

Done. That looks better.


Implement API to retrieve compiler command-line

Fixes #212

That was fast, thanks! The code looks great, so assuming the build check passes I'll merge this in an get a release out. I also need to run some integration tests locally before releasing, but that rarely fails if the CI build passes.

Thank you very much for merging this so fast. I just updated my project and it works like a charm.

Awesome, glad to hear it!


[flutter_auth] Listen to email verification

Is your feature request related to a problem? Please describe.
I'm logging in with flutter_auth well enough and when a new user signs up I'm fine with them being immediately logged in. But I would really like my user to verify the email address. To that end I use sendEmailVerification. But what I would just love is that, when the user actually verifies their email, I could listen to that event.
Describe the solution you'd like
Something in line with the onAuthStateChanged stream would be great. Or perhaps the user property isEmailVerified should be a Stream<bool> instead of a simple bool.
Perhaps there's another method to achieve what I want and I'm just missing it?

Same for me...
For now, I had a waiting page after signin where the user can say that he has checked the verification email (and ask to resend verification email). When he says that he has checked the verification link in the email sent by firebase, my app check for flag isEmailVerified thanks a firebase function (the only way for me to check this flag without asking the user to sign out and sign in again...)... A little boring isn't it compared to a isEmailVerified stream directly in the app....

The new version of the library has a stream for this, check it out.


The page you were looking for doesn't exist (404)

I guess there is another issue with version 0.11 during upload:
https://ci.appveyor.com/project/OpenRA/openra/build/1.0.5590#L528

Unfortunately, thats not me, and is still broken in 0.10.0.  Something changed on coverity's side 2 days ago. I'm investigating the problem and looking for a solution now.
Working build with 0.10.0
https://ci.appveyor.com/project/MarkClearwater/bclextensions/build/1.2.0-unstable.56 (Build 349)
Failing build on the same commit a day later:
https://ci.appveyor.com/project/MarkClearwater/bclextensions/build/1.2.0-unstable.56 (Build 350)

Update: the UI upload works. It seems to just be the "https://scan.coverity.com/builds"  endpoint that has started failing. Even using it from curl at the command line gives me the same 404 response. Trying to sign up to the forum to raise the issue, waiting for the manual verification step.
Looks like most other scripts use http://scan5.coverity.com/cgi-bin/upload.py. This is only http but has been the way scripts have been doing it for several years now.  not sure if https://scan.coverity.com/builds is newer and better or if i should change. Pretty simple change to make though. And the scan5 one does work from command line.

This all seems to be working again for me today the scan5 api seems slower so I wan't be switching to it. Ill close the ticket for now. Re-open if the issue comes back.

Yay, the https://scan.coverity.com/projects/3650 passed again. Thanks!


Feature request: soft and hard link support in object storage interface

Is your feature request related to a problem? Please describe.
ChubaoFS is a distributed fusion storage that provides both POSIX-compatible file system interface and S3-compatible object storage interface.
The object storage interface is designed on the basis of POSIX compatibility, the object storage semantics will be escaped to POSIX semantics on ChubaoFS.
The object storage interface is compatible with S3, so that file system operations cannot be performed which not defined in Amazon S3 .
For example, user cannot make soft or hard link through the object storage interface.
Describe the solution you'd like
Users want to make soft and hard links through the object storage interface like using ln command through POSIX-compatible file system interface.
This feature reuqest comes from Yuhao Zhang of the Recommended Search Platform Division in the JD Retail.
Describe alternatives you've considered
None.
Additional context
None.

The copy or part copy of existing object interface is  based on data streams and does not implement hard link, because the custom metadata of different objects may be different, and the same inode cannot save the custom metadata of different objects.


Improve search integration with the documentation panel

Previously, if you hit the input timeout while searching the documentation panel would close as input into the search buffer would be taken into consideration for the documentation to be shown. This PR does two things:

Ensures that the documentation panel only considers the prompt's input for show documentation
Will conditionally apply the search criteria against the prompt or documentation buffer based on which was previously focused before the search as activated

Trying to write tests for this by leveraging the internal interfaces will be quite challenging.
There's a vt100 terminal emulator called pyte that we could leverage to have the output of the shell go to an in memory string representation of the current terminal screen. Though, that only solves one problem and would likely also require a custom event loop that would allow us to provide input, inspect the current screen state, then provide more input, etc. I think it would be quite an effort to wire the prompt toolkit internals up in this way.
I also found hecate which is a testing framework designed for testing ncurses like terminal applications. It leverages tmux as a terminal emulator and interfaces with a tmux session to send input and determine the current screen state. It's relatively simple to write tests with it and I have one in this PR to test these changes. Unfortunately, actually running an instance of the shell to run tests against it currently is being blocked by having the documentation generate in the background. It would be better to have all the documentation already generated then run these kind of integration tests against them for consistency.

I got a proof of concept done for the pyte version. It currently side steps the event loop issue by spawning it in another thread while retaining a reference to the input stream and pyte screen. Might need to do some more interface shuffling on the AWSShell class to ensure all environment sensitive things can be injected rather than assumed (such as history).
This approach has some pretty significant advantages over hecate:

No dependencies outside of python
A lot faster
Not as sensitive to timing issues
We control the AWSShell instance being run.


Update changelog about upgrade to spring-boot-dependencies:2.4.5 and spring-cloud-dependencies:2020.0.2

Update changelog about upgrade to spring-boot-dependencies:2.4.5 and spring-cloud-dependencies:2020.0.2

Related PR: https://github.com/Azure/azure-sdk-for-java/pull/20721

Hi, @saragluna , @yiliuTo , please help to review this PR. 🙏


Moving this to /zalando-incubator

Hi @slavaschmidt: Looks like you're the maintainer of this repo now. Can I move it to our other GitHub org, as we don't have anyone from our team involved in this project and most attention is on the API First Hand repo?

Hi! Sure, this project is actually not maintained anymore.
By the way, i'm not sure who is maintaining API First Hand repo, but if you like me to continue to do so, could you please check why I have all my rights revoked?

Wow, that's strange. I just added you back as an admin -- you weren't listed. I don't get it but it's fixed now.

Cool, thank you so much!


what's the update in New version ?

what features or assistance will get through this new updated version??

Just keep updated is recommended.
Add /update command , using this will update the EdgeGPT to the newest. ( only update EdgeGPT, not PyroEdgeGPTBot)

Okays Thanks


ci: remove sematic-release job

Codecov Report

Merging #164 (4dd9ea5) into main (517f450) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff            @@
##              main      #164   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         1    -1
  Lines           93        27   -66
  Branches         4         3    -1
=========================================
- Hits            93        27   -66

Flag
Coverage Δ

linux-clang-14
?

linux-gcc-12
?

macos-clang
100.00% <ø> (ø)

windows-cl
?

windows-clang
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 2 files with indirect coverage changes


Crash report + request for install instructions

Hi! So I cloned your extension to<EMAIL_ADDRESS>and restarted GNOME.
Was about to start configuring the extension but was greeted by a crash report in extension manager:
The settings of extension<EMAIL_ADDRESS>had an error:
GLib.FileError: Failed to open file<EMAIL_ADDRESS>open() failed: No such file or directory

Stack trace:
getSettings@resource:///org/gnome/Shell/Extensions/js/misc/extensionUtils.js:200:31
fillPreferencesWindow@/home/aadil/.local/share/gnome-shell/extensions/kimai@benediktmagnus.de/prefs.js:20:37
_init@resource:///org/gnome/Shell/Extensions/js/extensionPrefsDialog.js:27:29
ExtensionPrefsDialog@resource:///org/gnome/Shell/Extensions/js/extensionPrefsDialog.js:10:4
OpenExtensionPrefsAsync/<@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:129:33
asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:115:22
run@resource:///org/gnome/Shell/Extensions/js/dbusService.js:186:20
main@resource:///org/gnome/Shell/Extensions/js/main.js:22:13
run@resource:///org/gnome/gjs/modules/script/package.js:206:19
start@resource:///org/gnome/gjs/modules/script/package.js:190:8
@/usr/share/gnome-shell/org.gnome.Shell.Extensions:1:17

Is there something I did wrong? I'm running the extension on Pop!_OS 22.04, which uses GNOME 42.

Hi aadilayub!
Thank you for the report.
For an installation from source, you need to compile the schemas: glib-compile-schemas schemas/ (inside the cloned extension folder). I have added an installation instruction to the readme to clarify this in the future.
Let me know whether this solves your issue or not.


vs code extension is not working

I am getting this error after installing the vs code extension even  though i installed phpactor and added it to my path
[Error - 3:21:39 AM] Starting client failed
Launching server using command php failed.

The latest version of vscode-phpactor comes bundeled with phpactor phar. It tries to run php (path to extension data)/phpactor.phar.
The error indicates that perhaps vscode was not able to find PHP in the path. These are the steps that the extension makes to resolve path to php

setting phpactor.executablePath
setting php.executablePath
setting php.validate.executablePath
php

First one set is used. If you have php in a special location and not in path, add the setting phpactor.execuablePath.
Try to also set verbose logging via setting phpactor.trace.server to see if there is any other logs available.

I encountered this issue on Pop!_OS, and it wasn't just this particular problem. PHP CS Fixer didn't work either, and every time I opened a PHP file, VS Code would prompt me to set php.validate.executablePath, which was quite strange. So, I decided to delete Pop!_OS and installed Debian instead, and now everything works fine.


Hashable eqx.Module

Thank you for this fantastic library -- I love the transparency of the systems you can build when everything is just a python datastructure.
As it stands, eqx.Modules do not have a way of being hashed. This makes decorating methods with @jax.jit impossible, and it complains:
ValueError: Non-hashable static arguments are not supported. An error occured while trying to hash an object of type <class '__main__.SimpleModule'>, SimpleModule(layers=[NeuronLayer(lagrangian=<function SimpleModule.__init__.<locals>.<lambda> at 0x7f818447b160>, shape=(32,), tau=1.0), NeuronLayer(lagrangian=Softmax(beta=1), shape=(500,), tau=0.0)], synapses=[DenseSynapse(W=DeviceArray([[ 1.1177216 , -0.85337347,  0.62181216, ...,  0.47079483,
               2.1223438 ,  0.11009306],
             [-0.19882406, -0.58834153,  0.27299452, ...,  0.3560427 ,
              -1.3553874 , -0.64876467],
             [-0.27144387, -0.24926849,  1.7452046 , ...,  0.90979475,
              -0.37605172, -0.30193415],
             ...,
             [ 0.25044632, -0.96083486,  0.18758047, ...,  0.82221097,
               0.73630685, -0.7022106 ],
             [-1.0072463 , -0.30353332,  1.412912  , ..., -1.0664191 ,
              -1.1468811 ,  0.5145061 ],
             [-0.7490296 ,  2.1055915 , -1.5650765 , ...,  1.9068209 ,
               0.04990109,  0.2296551 ]], dtype=float32))], connections=[(0, 1, 0)]). The error was:
TypeError: unhashable type: 'SimpleModule'

I was curious if there is anything preventing eqx.Modules from providing a default hash function. They are, after all, just data containers with a few methods attached to them.

Thank you for the positive review!
So judging from your error message, I don't think it'll be possible to hash eqx.Modules for your use case. The reason is that you have a JAX array as part of the PyTree, and JAX arrays aren't hashable.
(Theoretically I think it should be fine to define hashing eqx.Modules that feature no JAX arrays, but that's a very uninteresting/unusual edge case for obvious reasons.)
It should be fine to JIT methods (indeed I do it all the time); you just need to make sure that the self parameter handles static vs tracing appropriately, typically via a filtered transformation.
import functools as ft
import equinox as eqx

class MyModule(eqx.Module):
    @ft.partial(eqx.jitf, filter_fn=eqx.is_array)
    def __call__(self, x):
        ...

Substituting filter_fn for whatever criterion you need, of course. (Or a filter_tree if you need really fine-grained control.) I find that is_array is usually the desired behaviour though.
(It sounds like you're doing @ft.partial(jax.jit, static_argnums=0) instead? This would produce the error message you've given.)

(Good eye -- yes, I did the @ft.partial(jax.jit, static_argnums=0) command you mention, thanks for filling in that gap in my request)
Sweet yes, this is what I was looking for. I had a misconception about how JIT was supposed to work regarding static arguments. Thanks for clearing it up!


PyISY 1.0.8 upgrade gives initialization errors with ISY 4.6.2

Home Assistant release (hass --version):  0.53.0
Python release (python3 --version): Hass.io supervisor 0.61  I can't/don't how login to it enough to see the python version in use.
Component/platform: ISY994
Description of problem:
Since the upgrade to v0.53, ISY initialization returns several instances of:
2017-09-11 08:21:21 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.6/asyncio/tasks.py", line 179, in _step
    result = coro.send(None)
  File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity_component.py", line 381, in async_process_entity
    new_entity, self, update_before_add=update_before_add
  File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity_component.py", line 238, in async_add_entity
    yield from entity.async_update_ha_state()
  File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 246, in async_update_ha_state
    attr = self.state_attributes or {}
  File "/usr/lib/python3.6/site-packages/homeassistant/components/cover/__init__.py", line 245, in state_attributes
    current = self.current_cover_position
  File "/usr/lib/python3.6/site-packages/homeassistant/components/cover/isy994.py", line 62, in current_cover_position
    return sorted((0, self.value, 100))[1]
TypeError: '<' not supported between instances of 'NoneType' and 'int'

In my case, I get that nine times.  For covers, I have 3 fans.
This is running on a non-prod Hass.io that is virgin, with the exception of adding in just the base ISY connection and letting it discover.  Prior to this upgrade, on HA v0.52.1 there were no exceptions at startup.
I see that #9182 bumped the PyISY version to resolve #7601.  Those were all issues aroud the alpha release of ISY 5.0.x.  Did anyone test the upgrade against the current stable relase, 4.6.2?
If I take my prod HA v0.52.1 and modify just the home-assistant/homeassistant/components/isy994.py line 20 to REQUIREMENTS = ['PyISY==1.0.8'] to force an upgrade of just that library, it causes these same errors on start up/
The ISY portion will continue to run, but when updating a fan (which also still works), logs the following...   Others have seen this second error on 0.52.1 and this may not be related. see #9223.  I'm including it for completeness.
2017-09-11 13:29:43 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.4/asyncio/tasks.py", line 233, in _step
    result = coro.throw(exc)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/core.py", line 1025, in _event_to_service_call
    yield from service_handler.func(service_call)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/fan/__init__.py", line 219, in async_handle_fan_service
    yield from getattr(fan, method['method'])(**params)
  File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/fan/isy994.py", line 88, in set_speed
    self.speed = self.state
AttributeError: can't set attribute

Any one else seeing this?  Or am I the lone holdout not running the alpha v5 ISY software?  I'd love to, I just don't have the time to play with it if or when they break it.
Additional info:
First noticed in Hass.io, non-production (0.53.0)
Duplicated in prod 0.52.1 with modification of updating PyISY to 1.0.8.

I see the same thing.  Everything I have in ISY is replicated as every type...Switch, Light, Fan, Cover...
I'm on 5.0.2.

I'm seeing the same error.

I was using 4.6.2 w/ HASS 0.53 w/ no issues. Python version is 3.6. I did upgrade to 5.0.10; however now no entities show up and there are no errors in the logs ;(

Here's the errors I'm still getting.
HASS 0.56.2
Python 3.6.3
2017-11-02 09:47:58 INFO (MainThread) [homeassistant.components.cover] Setting up cover.isy994
2017-11-02 09:47:58 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 180, in _step
    result = coro.send(None)
  File "/home/hass/hass/lib/python3.6/site-packages/homeassistant/helpers/entity_component.py", line 398, in async_process_entity
    new_entity, self, update_before_add=update_before_add
  File "/home/hass/hass/lib/python3.6/site-packages/homeassistant/helpers/entity_component.py", line 246, in async_add_entity
    yield from entity.async_update_ha_state()
  File "/home/hass/hass/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 222, in async_update_ha_state
    attr = self.state_attributes or {}
  File "/home/hass/hass/lib/python3.6/site-packages/homeassistant/components/cover/__init__.py", line 236, in state_attributes
    current = self.current_cover_position
  File "/home/hass/hass/lib/python3.6/site-packages/homeassistant/components/cover/isy994.py", line 62, in current_cover_position
    return sorted((0, self.value, 100))[1]
TypeError: '<' not supported between instances of 'NoneType' and 'int'
2017-11-02 09:47:58 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 180, in _step
    result = coro.send(None)
  File "/home/hass/hass/lib/python3.6/site-packages/homeassistant/helpers/entity_component.py", line 398, in async_process_entity
    new_entity, self, update_before_add=update_before_add
  File "/home/hass/hass/lib/python3.6/site-packages/homeassistant/helpers/entity_component.py", line 246, in async_add_entity
    yield from entity.async_update_ha_state()
  File "/home/hass/hass/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 222, in async_update_ha_state
    attr = self.state_attributes or {}
  File "/home/hass/hass/lib/python3.6/site-packages/homeassistant/components/cover/__init__.py", line 236, in state_attributes
    current = self.current_cover_position
  File "/home/hass/hass/lib/python3.6/site-packages/homeassistant/components/cover/isy994.py", line 62, in current_cover_position
    return sorted((0, self.value, 100))[1]
TypeError: '<' not supported between instances of 'NoneType' and 'int'
2017-11-02 09:47:58 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 180, in _step
    result = coro.send(None)
  File "/home/hass/hass/lib/python3.6/site-packages/homeassistant/helpers/entity_component.py", line 398, in async_process_entity
    new_entity, self, update_before_add=update_before_add
  File "/home/hass/hass/lib/python3.6/site-packages/homeassistant/helpers/entity_component.py", line 246, in async_add_entity
    yield from entity.async_update_ha_state()
  File "/home/hass/hass/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 222, in async_update_ha_state
    attr = self.state_attributes or {}
  File "/home/hass/hass/lib/python3.6/site-packages/homeassistant/components/cover/__init__.py", line 236, in state_attributes
    current = self.current_cover_position
  File "/home/hass/hass/lib/python3.6/site-packages/homeassistant/components/cover/isy994.py", line 62, in current_cover_position
    return sorted((0, self.value, 100))[1]
TypeError: '<' not supported between instances of 'NoneType' and 'int'

Hey everyone,
I just found this issue. I don't experience it myself, but I'd like to get it fixed. It looks like the update of PyISY to 1.0.8 caused the issue from what I'm reading here.
Could you please post or send me the output of your http://isy/rest/nodes/ endpoint? (check for personal info in there before posting)

<node flag="0" nodeDefId="UZW000E">
  <address>ZW008_104</address>
  <name>ZW 008 Binary Sensor</name>
  <family>4</family>
  <parent type="1">ZW008_1</parent>
  <type><IP_ADDRESS></type>
  <enabled>true</enabled>
  <deviceClass>0</deviceClass>
  <wattage>0</wattage>
  <dcPeriod>0</dcPeriod>
  <startDelay>0</startDelay>
  <endDelay>0</endDelay>
  <pnode>ZW008_1</pnode>
  <sgid>104</sgid>
  <devtype>
    <gen>4.16.0</gen>
    <mfg>132.1107.273</mfg>
    <cat>104</cat>
    <model>11</model>
  </devtype>
  <ELK_ID>A13</ELK_ID>
  <property id="ST" value="100" formatted="On" uom="78" />
</node>

Here's a full nodes dump.  The error seems to occur once per Insteon fan, of which I have three in there.  But the full file for context.
Nothing PII in there that I can find.
I appreciate you looking at this.
nodes.txt

Hey @dethpickle, I just opened https://github.com/home-assistant/home-assistant/pull/16812 which should fix these issues. Can you confirm a few things for me?

You would get log spam, but all of the device functionality still worked, correct?
You haven't gotten the fan/isy994.py error (AttributeError: can't set attribute) for quite some time now, correct?

If I am correct about both of those things, then I am pretty sure I fully understand what these errors were and have them fixed appropriately

I've been experiencing this very issue and just found this thread!
Thanks for getting it fixed, @OverloadUT!

Just updated my HA to the latest 0.80 release but I still face the issue. Wondering whether the issue I face is different from the one described here. Here is what I get after restarting HA:
Error during setup of component isy994
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/setup.py", line 148, in _async_setup_component
    component.setup, hass, processed_config)  # type: ignore
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/isy994.py", line 379, in setup
    use_https=https, tls_ver=tls_version, log=_LOGGER)
  File "/usr/local/lib/python3.6/site-packages/PyISY/ISY.py", line 84, in __init__
    self.nodes = Nodes(self, xml=self.conn.getNodes())
  File "/usr/local/lib/python3.6/site-packages/PyISY/Nodes/__init__.py", line 52, in __init__
    self.parse(xml)
  File "/usr/local/lib/python3.6/site-packages/PyISY/Nodes/__init__.py", line 238, in parse
    Group(self, nid, nname, members, controllers), ntype)
  File "/usr/local/lib/python3.6/site-packages/PyISY/Nodes/group.py", line 43, in __init__
    self.update()
  File "/usr/local/lib/python3.6/site-packages/PyISY/Nodes/group.py", line 83, in update
    if self.parent[m].status > 0:
  File "/usr/local/lib/python3.6/site-packages/VarEvents/__init__.py", line 255, in __gt__
    return self._val > other
TypeError: '>' not supported between instances of 'NoneType' and 'int'


use_node_name  breaks datafile import

running muninflux import doesn't succeed processing /var/lib/munin/datafile. The offending line reads like example.com;host:use_node_name 0 - opposed to the other, plugin-related lines, there is only one string after the host specification, instead of multiple .-separated ones.

this happens too on the following lines:
domain;host:port 4949
domain;host:update 1
fixed it meanwhile locally doing a check on the plugin_parts length (will add a PR as soon as possible here)


Index name definition on many to many relation possible??

Hello every one. Is there any way to define the index name for a many to many relation?
Regards.

No, this isn't supported at the moment.

Is there any plan to implement this functionality?

Not currently: a manual SQL migration is generally sufficient for this.


Added arg in run function, removed multiple breaks

Added an argument in the run function if the user wants to return the message object to possible add more reactions, etc. Rremoved breaks after return statements as the code would no longer be reachable.

Instead if an arg i made it always return the message object


docs: Derived signals - Clarified derived signals

I love these docs .. they are well work the read...
This is just a minor thing that broke my concentration
The double use of the word "per" in a sentence made no sense to me
It read like the units of acceleration meters per second per second...

Fair enough, thanks :-)


Better Support for Source Breakpoints when output is in different folders

VSCode Version: 1.1.1
OS Version: Windows 10

Steps to Reproduce:
Given:
./dist/foo.js
./dist/foo.map
./dist/folder/bar.js
./dist/folder/bar.map

./spec/foo.spec.js
./spec/foo.spec.map

./src/foo.ts
./src/foo.spec.ts
./src/folder/bar.ts

In node launch config...
set "outDir": "${workspaceRoot}/dist"
set breakpoint in bar.ts
set breakpoint in foo.spec.ts
Run f5 (node debug)

then:
neither break-point will resolve within nodejs and execution will pass over them.
use-case:
I'm outputting source code to both a "dist" and "spec" folder; based on whether the file is *.spec.ts or not. As a result I have two locations for source mappings. In order to be able to assign breakpoints in both the .ts and .spec.ts files I must specify an outDir for VS Code's launch.json. Unfortunately, it does not support multiple directories so I can only pick one at the moment.
Secondly, any vscode can only successfully map the breakpoints for files within /outDir if you have map/js in sub-folders it also fails to match them up.

actually, could this be globbed please?
If my TS file is in a sub-directory, it doesn't seem to be able to find the breakpoints either.

+1
I have source maps in some modules in the node_modules folder, and VSCode is unable to find them. If I place a breakpoint in a .ts file in a node_modules module, the vscode-node-debug debugger is unable to automatically resolve the source map location. However, if I instead place the breakpoint in the corresponding .js file, the source map resolves based on the sourceMappingURL, and the breakpoint is hit in the .ts file. This is a somewhat counterintuitive workaround. Being able to specify multiple outDirs looks like it might fix the problem.

I've had to solve this by compiling ts->js/map in the same folder, you can then entirely hide the js/map files that have a corresponding ts file next to them.
.vscode/settings.json:
{
  "files.exclude": {
    "**/*.js": {"when": "$(basename).ts"},
   "**/*.map": {"when": "$(basename).map"}
  }
}

This seems like the only way to reliably have VSCode map from js to ts, when execution moves over multiple folders, and make your project tree look sane.

I think this is related to a similar problem I am having.
My projects file structure is as follows:
project

build

routes

nestedFile.js

app.js

maps

routes

nestedFile.js.map

app.js.map

source

routes

nestedFile.ts

app.ts

With my setup I can add breakpoints to the app.ts and everything works as expected however if i add a breakpoint to nestedFile.js.map i get the dreaded "Breakpoint ignored because..." error.
I'm assuming that until outDir can take an array of directories as a value this is going to be a problem and the only realistic work around for larger project is as @MeirionHughes suggests?

I've updated the issue so its a bit more clear.

I think that while being able to pass outDir an Array is a solution, its probably not the best solution.
Glad you changed the title of the issue. :)

@kineticfaction  your structure should work (and I even have an automatic test for exactly that case). Set outDir to ${workspaceRoot}/build and make sure that the source maps are correct. The source maps don't need to be under outDir.

I agree, we need a way to specify more than one 'outDir' in the launch.json or use a different mechanism, e.g. scanning the whole project structure upfront to locate all source that is referenced by the generated JavaScript (but this can be expensive for large projects).
Both options would solve the issue described in the initial comment.
However, in the discussions/comments that are following I see some speculation and misconceptions about how things work. So here are some clarifications:
Source mapping always involves two directions: mapping source to generated code and mapping generated code back to source. JavaScript source maps only cover the second case: "mapping generated code back to source". The other direction must be either derived from the first direction (exhaustive search), or by explicitly configuring it in the launch.json.
Let's start with how the "mapping source to generated code" is configured with the 'outDir' attribute in the launch.json:
The 'outDir' is only used to map a breakpoint in source to the generated file (because there is no other direct reference in the source that would help VS Code to find the generated code where the real breakpoint has to be registered). If setting a breakpoint in source fails in an active debug session (breakpoint is a grey donut), this indicates that VS Code cannot map the source breakpoint to the corresponding line in the generated code. Typically you can fix this by supplying the 'outDir' and by making sure that the folder structure in source matches the structure in the generated code. If your build process generates a different structure for the generated code than the source structure, setting breakpoints will most likely fail.
Now let's look into the other direction "mapping generated code back to source":
For this the VS Code debugger needs a way to find the originating source if a breakpoint has been hit in some generated JavaScript file. By convention there is a URL at the end of the generated code file that points to the source map (*.js.map) or contains the source map inlined as a data url:
console.log("end of code");
//# sourceMappingURL=./app.js.map

The URL can either point to a location on disk (an absolute or relative file URL), or it can be an http URL that points to some remote file. This means that VS Code makes no assumption about where the source map is located but just follows the URL in the generated code (so the statement from some comment above "VS Code fails to match up map/js in sub-folders" is not correct). Just make sure that the URL is correct and VS Code will be able to find the source map. I recommend either to keep the source maps side by side with the generated code which results in a very simple (relative) URL or to use inlined source maps.
With inlined source maps the URL is a data URL that contains the map. This is less error prone, but since the data URL uses base64 encoding, it is more difficult to see what's in the source map.
The next step in "mapping generated code back to source" is in the source map itself. Here the entries in the "sources" array should point to the source files. If they are absolute paths it is easy to verify that they are valid. However it is good practice to keep them short by making them relative. But this makes verification a bit more difficult because you have to understand to what reference point they are relative. The source map spec says: "If the sources are not absolute URLs after prepending of the “sourceRoot”, the sources are resolved relative to the SourceMap (like resolving script src in a html document)."
So in @kineticfaction's structure from above the entry in the 'sources' array in "nestedFile.js.map" would be "../../maps/source/routes/nestedFile.ts" and for "app.js.map" it would be "../maps/source/app.ts".

Typically you can fix this by supplying the 'outDir' and by making sure that the folder structure in source matches the structure in the generated code.

Doesn't appear to work properly for me when I have subfolders. I have some code in ./src/rules/... that don't match up with ./dist/rules/...when I useoutDir: "./src/"

@MeirionHughes you have to set outDir to the generated code, not the source.

sorry yes... typo. it is set to dist

@MeirionHughes and it must be an absolute path, e.g. ${workspaceRoot}/dist

Yes sorry; its exactly that. :P

ahh I may know why... I think my sourceRoot is wrong in the output.

Can you please add "trace": "sm" to your launch config and then set a breakpoint. In the debug console you should see a trace of what's going on. That could help investigating this.

Sorry @weinand, you are correct with the same folder structure plus correct sourceRoot; it does work.
Seems there is an issue with gulp-typescript or gulp-sourcemap with regard to setting the relative path see( https://github.com/ivogabe/gulp-typescript/issues/395 ).
So we're left with the original issue (support for multiple outDir folders).

@MeirionHughes great to hear that sourcemaps works for you for the one-outDir case.
I'm planning to add globbing support for outDir soon.

Thanks Andre I'll take a look this evening once i get out of the office

@weinand Yep works perfectly as expected.

@kineticfaction thanks a lot for verifying that your setup works.

How about debugging codes generated by ts-node?
I'm using mocha to run test.ts:
mocha --require ts-node/register test.ts --debug

ts-node will compile test.ts to test.js which locates in a temp folder.  The folder structure in source can never match the structure in the generated code.
I can't debug for test.ts if I set the sourceMap option enabled.


deselect_node event send a faulty selected nodes list ...

I created a three levels tree :
 Level 1
   Level 2
     Level 3 - 1
     Level 3 - 2
     Level 3 - 3

I binded to 'select_node' and 'deselect_node' events :
      .bind('select_node.jstree', function(event, selectedNodes) {
      })

      .bind('deselect_node.jstree', function(node, selectedNodes) {
      })

When I select a 'Level 2' node the selectedNodes parameter gives me a list including all 'Level 3' nodes; but when I deselect this same node, I get the same list ... but nodes are not any more selected in the tree.

 Please share your config next time you submit a bug. If you are this behavior is normal - when using the checkbox plugin with the three_state option enabled, selecting and deselecting nodes cascades up and down. Also keep in mind is better to used the changed.jstree event. If I misunderstood - please clarify and I will reopen the ticket.
Best regards,
Ivan

Hello,
I am using checkbox plugin, indeed ...
What is strange is that my leaf nodes are no more selected but are still in the selected nodes array.
I copy my configuration and a console log screen capture after I selected each one of the leaf nodes and then unselected their parent node. As you will see in the screen capture the tree is whole unselected but I still have a selected nodes array ... where as none are selected in the tree.
    var jsTreeData = new Array();
    jsTreeData.push( { "id" : 'entity_95', li_attr: { "entities_id" : 95 }, "parent" : "#", "text" : "Level 1" } );
    jsTreeData.push( { "id" : 'entity_96', li_attr: { "entities_id" : 96 }, "parent" : "entity_95", "text" : "Level 2" } );

    $('#hostsTreeTest')
      .jstree({
        "core" : {
          "check_callback" : true,
          "data" : jsTreeData
        }
        , "plugins" : [
          "checkbox",
          "sort"
        ]
        , "checkbox": {
            "three_state" : true
          , "whole_node": true
        }
      })

      .bind('ready.jstree', function(e, data) {
        var nodeID = $('#hostsTreeTest').jstree().create_node('entity_96', { "id": 'kiosk_1', "type": "host", "text": 'Level 3-1' }, "last", function (node) {
          $(node).attr("host_name", 'Level 3-1');
        });
        var nodeID = $('#hostsTreeTest').jstree().create_node('entity_96', { "id": 'kiosk_2', "type": "host", "text": 'Level 3-2' }, "last", function (node) {
          $(node).attr("host_name", 'Level 3-1');
        });
        var nodeID = $('#hostsTreeTest').jstree().create_node('entity_96', { "id": 'kiosk_3', "type": "host", "text": 'Level 3-3' }, "last", function (node) {
          $(node).attr("host_name", 'Level 3-1');
        });

        $('#hostsTreeTest').jstree().open_node('kiosk_1');
      })

      .bind('select_node.jstree', function(event, selectedNodes) {
        if (debugJs) console.debug('Selection :', selectedNodes.selected);
      })

      .bind('deselect_node.jstree', function(node, selectedNodes) {
        if (debugJs) console.debug('Deselection :', selectedNodes.selected);
      })

Hi, I see what you mean - this is why I suggested using the changed.jstree event.
Deselect is triggered whenever a single node is deselected, the checkbox plugin picks up that event and reacts on it to apply cascading, so when you process that same event the checkbox plugin has not yet made its changes (those changes however are available in the changed.jstree event).
Sorry for the inconvenience, I will try to make this clear in the docs.
Best regards,
Ivan

Thanks. When using changed.jstreeeverything is ok !


Add support for TypeScript

Add build system infrastructure to slowly migrate all code to
TypeScript.
This is the first PR for ThingTalk 2.0. Given the invasiveness of a lint & build system change, I would like to merge this quickly to the next branch. We can do small PRs targeting next, and then do a single merge to master when ready.

Pull Request Test Coverage Report for Build 1088

524 of 551 (95.1%)  changed or added relevant lines in 59 files are covered.
67 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.2%) to 80.307%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/ast/index.ts
11
12
91.67%

lib/compiler/jsir.js
6
7
85.71%

lib/grammar_api.js
10
11
90.91%

lib/date_utils.js
34
37
91.89%

lib/utils.js
22
27
81.48%

lib/builtin/primitive_ops.js
34
50
68.0%

Files with Coverage Reduction
New Missed Lines
%

lib/i18n.js
1
70.37%

lib/builtin/primitive_ops.js
7
72.73%

lib/nn-syntax/parser.js
59
67.97%

Totals

Change from base Build 1085:
0.2%

Covered Lines:
8996

Relevant Lines:
10774

💛  - Coveralls


Student U: Improve borrow link tooltip

[x] Align tooltip position to icon
[x] Include originating tripos AND part information

[ ] Tangential: We should really try to fix the scroll bar issue, as this example shows how sloppy is it to have a scrollbar there, apart from interfering with adding series and modules to the calendar.

Assigning to @Coenego who's been working in the area

Fixed in https://github.com/CUL-DigitalServices/grasshopper-ui/pull/322


Release Google.Cloud.Functions.V2Beta version 1.0.0-beta07

Changes in this release:
New features

Optional field for specifying a service account to use for the build. This helps navigate the change of historical default on new projects. For more details, see https://cloud.google.com/build/docs/cloud-build-service-account-updates (commit f6efb2e)
Optional fields for setting up automatic base image updates. (commit f6efb2e)
Optional field for specifying a revision on GetFunction. (commit f6efb2e)
Optional field for binary authorization policy. (commit f6efb2e)
Optional field for deploying a source from a GitHub repository. (commit f6efb2e)
Additional field on the output that specified whether the deployment supports Physical Zone Separation. (commit f6efb2e)
Generate upload URL now supports for specifying the GCF generation that the generated upload url will be used for. (commit f6efb2e)
ListRuntimes response now includes deprecation and decommissioning dates. (commit f6efb2e)

Documentation improvements

Refined description in several fields. (commit f6efb2e)

Created release for Google.Cloud.Functions.V2Beta-1.0.0-beta07


Fix coverage omit dirs

This PR fixes an issue identified by @gretelliz, in which the coverage report was including the tests directory.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-4.7%) to 78.503%

Totals

Change from base Build<PHONE_NUMBER>1:
-4.7%

Covered Lines:
493

Relevant Lines:
628

💛  - Coveralls


add support for dumping geojson and shapefiles!

not sure if this is a good idea considering how long it takes to generate a geojson.  It'll probably be more efficient to create a geojson from the downloaded CSV (which can happen outside this program).

It also seems we're limited to downloading up to 50k records in a GeoJSON whereas CSV is unliited.


[CTA Block] Using wrong top padding above heading-05

Detailed description
The CTA Block component is using the wrong top padding above the heading-05 title. It is currently using 48px on all breakpoints. Instead, it should be using a top padding of 64px on max, xlg,and lg and use 32px on md and sm breakpoints.
Steps to reproduce the issue
Storybook
Design specs
Additional information
What is currently on Storybook

Expected on max, xlg, and lg

Expected on md and sm

All good except CTA section is not mis-aligned. The top margin of CTA section's section heading should also be 64 in here.

When a Content section is used with Content block, the top spacing should follow the larger one like in this case:

Though there are quite a lot of spacing bugs in this component and I can open a more thorough issue later if that's better. Lemme know.

@emyarod I think this can be closed.  Is that correct?

@RobertaJHahn yes this should be resolved by #6907

closing,  based on comments above.


[FLINK-12683] Provide task manager location information for checkpoint coordinator specific log messages

What is the purpose of the change
This pull request provides task manager location information for checkpoint coordinator specific log messages
Brief change log

Added a new parameter TaskManagerLocation taskManagerLocation for method receiveAcknowledgeMessage and receiveDeclineMessage
Changed specific test case

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Hi @aljoscha what do you think about this PR? cc @tillrohrmann

cc @tillrohrmann reopened this PR.


runtime: add builtin proxy and shim capability

Add a new proxy type KataProxyBuiltinType and a new shim type KataBuiltinShimType. When they are specified, new proxy or shim processes will not be created. OTOH, the proxy and shim capabilities are provided by the kata runtime library directly.
For proxy, a yamux grpc dialer is used to create connections to the kata agent. And a goroutine is created to watch guest's console.
For shim, sandbox relay APIs will be provided. They are left to future PRs though.
Unfortunately due to limitation of the yamux library (at most one connection between client and server), this cannot be used with the kata runtime cli. So no cli change is included.
Depends-on: kata-containers/agent/pull/201

@devimc @jodh-intel @sboeuf PR updated. PTAL.

Jenkins failed on #193

Thx @bergwolf
LGTM

Jenkins failed on kata-containers/tests/issues/225

@bergwolf have you rebased on latest master version ? Just want to make sure you have kata-containers/runtime#193 included.

ping @kata-containers/runtime


tabmon wont install

Hi all.  I have run through the pre-requisites for installing Tableau. Am logged in as a local windows administrator.  I have right clicked on InstallRabMon and run as administrator.  I click on install (with the option to install and initialise Postgres selected) and it appears to try and install Postgres then comes up with an error saying one or more issues caused the setup to fail.  0x80070001 - incorrect function is the message. I have looked at the log but cannot determine what the issues is.
Can anyone help please?
tabmon install error log.txt

Hello,
I would suggest installing without Postgres. Once that is done you can manually install and configure postgres using the "Manually Installing and Configuring Postgres" section of the appendix here.
If you are still running into issues after this, please let me know.
Thanks,
Dan

Thanks will try that


Error on valid JIRA_URL without trailing slash

Steps to reproduce:

set your JIRA_URL to a url without a trailing slash, e.g. http://example.com
call book-time with otherwise valid parameters

Actual behavior:
book-time produces an error:
XXX-XXXX 2022-11-10T08:00:00.000+0200 0h 30m http://example.comrest/internal/3/issue/XXX-XXX/worklog
Traceback (most recent call last):
  File "urllib3/connection.py", line 169, in _new_conn
  File "urllib3/util/connection.py", line 73, in create_connection
  File "socket.py", line 955, in getaddrinfo
socket.gaierror: [Errno -2] Name or service not known

Expected behavior:
The time should be booked with no error.

Should now be fixed 👍


messages: Add spinner for messages sent on slow connections.

At times, it might get confusing for users who are on slow connections if their messages has not been sent even after 5s. Including a spinner that will only show up after 5 seconds has elapsed will keep user informed about their slow connection.
5s is set as minimum time because showing up a spinner before than might be distracting for users on normal connections.
Fixes: #19328.
zid has been used to identify the concerned message since it is unique to the message. Another approach we have is to pick the last element in the list. I think using zid is a better approach.

Screenshots and screen captures:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Thanks! Does this PR make changes to the buttons we currently have in locally echoed messages? We don't want to remove those.

No, It does not make changes to the buttons we currently have in locally echoed messages. These buttons pop up only when the message was not successfully sent, due to disconnectivity maybe. The new spinner appears only when the connection is slow and the message is still not sent after 5 seconds. I tested in main but I did not see anything spinning when the message is in the process of sending.

Got it. How did you pick the color for the spinner?

Time replaces the spinner after the message is sent, it is the same color as that time.

You can use the browser's dev tools > Network section and throttle your connection speed. The default profiles might be too fast for the spinner to show up and hence you might need to make a new profile. In my case, I made one with 1kbit/s upload and download speeds.

Ok, thanks! That looks reasonable to me, but I looks like we should make sure clicking on the spinner area doesn't do anything. While the timestamp is hidden, the link still seems to be there, but I think it's not actually valid.

The link is the URL of the message. I think the issue is unrelated to this PR since it is there in the main too. I can fix this in a separate commit.

@amanagr I haven't re-tested this PR, but perhaps you can review at this point?

Do we want to display a tooltip saying "Your message is taking longer than expected to be sent. Sending..."?

Sure, that might be helpful. I'll update it soon.

The alignment is not correct for /me messages.

@amanagr Thanks, I've addressed your feedback.

Pushed an update, to better represent the last commit. LGTM now.

@timabbott LGTM

I made the following changes:

I renamed the CSS class to use -s rather than _s in its separators.
Various changes to comments, including explaining how this state gets cleared once we've displayed it.

I opened https://github.com/zulip/zulip/issues/25069 for a pre-existing issues that still remains after this PR.
Thanks for the work on this @lakshaykananiya!


[Dask] Cannot perform reordered multidim slice of lazy cube

In cases where a slice of a cube will require transposing the intermediate result (that is, when the requested slice dims are not in the same order as they are on the cube), the following error will occur:
>>> cube = iris.load_cube(iris.sample_data_path('A1B_north_america.nc'))
>>> ht_slice = next(cube.slices(['latitude', 'time']))
Traceback (most recent call last):
  File "<input>", line 1, in <module>
  File "/.../git/iris/lib/iris/cube.py", line 3965, in __next__
    cube.transpose(self._mod_requested_dims)
  File "/.../git/iris/lib/iris/cube.py", line 2793, in transpose
    data = dm.core_data().transpose(new_order)
  File "/.../python2.7/site-packages/dask/array/core.py", line 1266, in transpose
    return transpose(self, axes=axes)
  File "/.../python2.7/site-packages/dask/array/core.py", line 2362, in transpose
    if axes:
ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()

This is because iris.cube._SliceIterator passes a NumPy array of reordering dims to cube.transpose, which dask cannot handle. This case was missed when cube.transpose was originally daskified, as was a test for this case that would have picked up on the error.

Closed now #2580 is merged.


Make an installation procedure.

Do an installation procedure to get Bitcluster run on your own machine.

+1
After installation dependencies:
C:\Users\test\Downloads\Bitcluster-master>start_webapi.py
Traceback (most recent call last):
File "C:\Users\test\Downloads\Bitcluster-master\start_webapi.py", line 1, in
from web.api import app
File "C:\Users\test\Downloads\Bitcluster-master\web\api.py", line 3, in
from web.dao import getNodeFromAddress, getNodeInformation, getTransations,
groupByAllDistribution, groupbyNode,
File "C:\Users\test\Downloads\Bitcluster-master\web\web.py", line 2, in
from web.dao import getNodeFromAddress, getNodeInformation, getTransations,
groupByAllDistribution, groupbyNode,
ImportError: No module named dao
I'm developer, but not familiar with python

@pshenmic You need Python 3 to run the projet. I will add it in the requirements. I did got the exact same issue as you when I did run it with Python 2.7.

C:\Users\test\Downloads\Bitcluster-master>py start_website.py

Running on http://<IP_ADDRESS>:5000/ (Press CTRL+C to quit)
<IP_ADDRESS> - - [26/Jul/2016 13:44:47] "GET / HTTP/1.1" 200 -
<IP_ADDRESS> - - [26/Jul/2016 13:45:31] "GET / HTTP/1.1" 200 -
[2016-07-26 13:45:50,936] ERROR in app: Exception on / [POST]
Traceback (most recent call last):
File "C:\Users\test\AppData\Local\Programs\Python\Python35-32\lib\site-packages
\flask\app.py", line 1988, in wsgi_app
response = self.full_dispatch_request()
File "C:\Users\test\AppData\Local\Programs\Python\Python35-32\lib\site-packages
\flask\app.py", line 1641, in full_dispatch_request
rv = self.handle_user_exception(e)
File "C:\Users\test\AppData\Local\Programs\Python\Python35-32\lib\site-packages
\flask\app.py", line 1544, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "C:\Users\test\AppData\Local\Programs\Python\Python35-32\lib\site-packages
\flask_compat.py", line 33, in reraise
raise value
File "C:\Users\test\AppData\Local\Programs\Python\Python35-32\lib\site-packages
\flask\app.py", line 1639, in full_dispatch_request
rv = self.dispatch_request()
File "C:\Users\test\AppData\Local\Programs\Python\Python35-32\lib\site-packages
\flask\app.py", line 1625, in dispatch_request
return self.view_functionsrule.endpoint
File "C:\Users\test\Downloads\Bitcluster-master\web\web.py", line 26, in web_ro
ot
node_id = getNodeFromAddress(address)
File "C:\Users\test\Downloads\Bitcluster-master\web\dao.py", line 10, in getNod
eFromAddress
cursor = db.addresses.find_one({"_id": address})
File "C:\Users\test\AppData\Local\Programs\Python\Python35-32\lib\site-packages
\pymongo\collection.py", line 1014, in find_one
for result in cursor.limit(-1):
File "C:\Users\test\AppData\Local\Programs\Python\Python35-32\lib\site-packages
\pymongo\cursor.py", line 1090, in next
if len(self.__data) or self._refresh():
File "C:\Users\test\AppData\Local\Programs\Python\Python35-32\lib\site-packages
\pymongo\cursor.py", line 1012, in _refresh
self.__read_concern))
File "C:\Users\test\AppData\Local\Programs\Python\Python35-32\lib\site-packages
\pymongo\cursor.py", line 850, in __send_message
**kwargs)
File "C:\Users\test\AppData\Local\Programs\Python\Python35-32\lib\site-packages
\pymongo\mongo_client.py", line 827, in _send_message_with_response
server = topology.select_server(selector)
File "C:\Users\test\AppData\Local\Programs\Python\Python35-32\lib\site-packages
\pymongo\topology.py", line 210, in select_server
address))
File "C:\Users\test\AppData\Local\Programs\Python\Python35-32\lib\site-packages
\pymongo\topology.py", line 186, in select_servers
self._error_message(selector))

Where should i place the database? Why there isnt any documentation for this tool? That's confusing

yes, python3 is necessary. and as far as I understand you need mongodb and bitcoind with full node data on the machine.
then you may start build_cluster.py and it will crawl data from bitcoind to mongo.
then you may start start_website.py and open http://<IP_ADDRESS>:5000 (or another ip address if it is remote machine, you need to change app.run for that) in the browser.
however, process of crawling failed in my case and web interface says "Invalid or inexistant address" when I checked several addresses.

@pshenmic: see https://github.com/mathieulavoie/Bitcluster/wiki/Installation-Procedure
@anton48: Building the database from scratch is a bit more complex. I did add a section into the installation procedure. Let me know if you have any question or if something doesn't work,

@mathieulavoie: this is exactly what I did and build_cluster.py script (step 5 of procedure "Creating the database from scratch") failed:
[/home/a48/Bitcluster]# python3.4 ./build_cluster.py 1
Block 1 crawled
Block 2 crawled
Block 3 crawled
[...]
Block 117501 crawled
Nb addr :  34076
Nb nodes :  24595
Waiting for insertion thread to complete...
DB Sync Finished
An exception will rise DB Sync Finished
nothing happens after this message for a long time and I pressed ctrl-c. At this point I stopped and was going to investigate the problem later.

The message shoud be "An exception will rise, press any key to see the Stacktrace". It used to be for debugging purpose during the tool development. I will remove it in the next commit.

Getting his while restoring database:
$ mongorestore bitcluser_2016-07-19/
connected to: <IP_ADDRESS>
Sat Jul 30 20:00:12.663 ERROR: don't know what to do with file [bitcluser_2016-07-19/bitcoin/addresses.metadata.json.gz]
Sat Jul 30 20:00:12.664 ERROR: don't know what to do with file [bitcluser_2016-07-19/bitcoin/addresses.bson.gz]
Sat Jul 30 20:00:12.664 ERROR: don't know what to do with file [bitcluser_2016-07-19/bitcoin/system.profile.metadata.json.gz]
Sat Jul 30 20:00:12.664 ERROR: don't know what to do with file [bitcluser_2016-07-19/bitcoin/transactions.metadata.json.gz]
Sat Jul 30 20:00:12.664 ERROR: don't know what to do with file [bitcluser_2016-07-19/bitcoin/system.profile.bson.gz]
Sat Jul 30 20:00:12.664 ERROR: don't know what to do with file [bitcluser_2016-07-19/bitcoin/transactions.bson.gz]

@maciekit The dump is is compressed using gzip. Use the --gzip command line option.
See https://docs.mongodb.com/manual/reference/program/mongorestore/#cmdoption--gzip

@mathieulavoie: tought so, but I don't have it:
ERROR: unrecognised option '--gzip'
mongorestore version 2.4.10

Ok, just answered myself, need version > 3.2.

After reaching to last block it says
Block 423534 crawled
Block 423535 crawled
Block 423536 crawled
Block 423537 crawled
Block not found
and you have to wait for timeout to have it inserted into db. This could be avoided by checking via rpc how many blocks are there.
And maybe you should consider adding second parameter here:
$ ./build_cluster.py
Usage: python ./build_cluster.py
so user can choose how big range would like to have.


fix: (v0.33.3) updated Goodreads status update rendering NaN

This PR fixes an issue where the Goodreads widget is rendering "NaN" for a recent status update that is missing the "created" field from the Goodreads API response, but does have an "updated" field. I do remember updating the status to status after the original review.

Screenshot: before this change

Screenshot: after this change

The deploy preview looks great. I'm going to merge this. 🚀


Adding Prompt Engineering Hindi course to the courses section

Dear Repository Owner,
I hope you're well. I'm a beginner participating in Hacktoberfest 2024 and came across your project. I’ve added a link to the Hindi version of the Prompt Engineering course to make it more accessible for Hindi-speaking users.
I’d appreciate it if you could review and consider merging my changes.
Thank you for your time and support!
Best regards,
Aayush Kolte.
What does this PR do?
This PR adds the Prompt engineering course in hindi for beginners under artifical intelligence subsection of courses section.
Why is this valuable ?
This prompt engineering course is valuable because it teaches how to effectively communicate with AI models whose use is growing drastically everyday, optimizing outputs for specific tasks. It enhances problem-solving by crafting precise, clear, and efficient prompts. Mastering this skill improves productivity and accuracy in AI-driven solutions. Additionally, it fosters a deeper understanding of model behavior, helping to leverage AI more effectively.
How do we know it's really free?
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Please approve my request

Don't invent titles! Use the title given by the resource.

@eshellman I have updated course name as per resource...so please do consider and merge my request as soon as possible

@eshellman I had committed the changes as said by you again after removing spaces pls approve and merge my request

@eshellman please merge my request I had made necessary changes. Please merge it as soon as possible.

Thanks, and welcome to free-programming-books!


Support inputFormat and inputSource for sampler

Description
This PR is to add support of the new interfaces (InputSource and InputFormat) introduced in https://github.com/apache/incubator-druid/pull/8823 for sampler. The key changes are:

Renamed FirehoseSampler -> InputSourceSampler.
IndexTaskSamplerSpec now supports both old (parser and firehose) and new (inputFormat and inputSource) APIs. You cannot mix them though.
SeekableStreamSamplerSpec now supports both parser and inputFormat.
To give the same experience with both sampler and Kafka/Kinesis indexing service, KIS now supports both parser and inputFormat. The supervisor will always internally fill parser if it was set in the supervisor spec to create sub tasks. Since the sub task understands both new and old APIs, it should work during the rolling update.
SamplerCache is removed now. This is because it caches the raw byte array of each row which makes sense for row-oriented file formats.
SamplerResponse now contains a Map of raw data instead of byte[]. This map will be serialized into JSON and sent to the caller like UI.
The behavior of SeekableStreamSamplerFirehose has changed. It returned an InputRow of null if it couldn't fetch any data within POLL_TIMEOUT_MS. Now it waits until it fetches any data.

This PR has:

[x] been self-reviewed.

[x] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[x] added documentation for new or modified features or behaviors.
[x] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[x] added unit tests or modified existing tests to cover new code paths.
[x] added integration tests.
[x] been tested in a test Druid cluster.

[x] Been tested during rolling update by running 1) old overlord + new middleManager and 2) new overlord + old middleManager.

This change is

Travis is failing because of https://github.com/apache/incubator-druid/pull/8779.

@jihoonson this has conflicts

@fjy thanks, resolved conflicts now.


Using generic method in expression does not work

Hello, i wrote a small demo project where i defined rule as follows :
{
"ErrorMessage": "There is no forecast with temperature > 100C.",
"ErrorType": "Error",
"Expression": "dataStore.GetObjects("temperatureC > 100").Count > 0",
"RuleExpressionType": "LambdaExpression",
"RuleName": "ForecastAbove100",
"SuccessEvent": "There is at least one forecast with temperature > 100C"
}
After rule's execution and investigation of the RuleResultTree i see an exception : "Exception while parsing expression dataStore.GetObjects<WeatherForecast>(\"temperatureC > 100\").Count > 0 - No property or field 'GetObjects' exists in type 'RedisObjectsManager'"
dataStore - i provide programmatically the instance of RedisObjectsManager  as a RuleParameter and the type  RedisObjectsManager  i provided to the RuleEngine through custom types of ReSettings .
I tried to use regular method of the RedisObjectsManager  (not generic one) and it works fine.
Are generic methods not available in the expressions? or there is a bug?
Thank you.
@abbasc52

Generic methods are not currently supported in expression. You can create a utils class and wrap the generic method call inside it.

Thank you. @abbasc52


Release 3.19.0

Features

Feature: display ENS name in connected wallet info (#3409)
[EPIC] Tx list and modals redesign (#3373)
Feature: historically estimate maxPriorityFeePerGas (#3450)
Add third party cookies banner warning (#3513)

Redesign fixes

fix: deal with nested arrays param values (#3469)
style: increase SpendingLimitDetail title font size (#3466)
fix: don't pass props to DOM (#3461)

General bug fixes

fix: Add form validation for max prio fee (#3482)
fix: getCode via readonly web3 object (#3477)
Fix: add OpenGraph meta tags (#3487)
fix: show user on stepper on immediate txs (#3478)
Fix: propose when creating or signing (#3455)
Fix: show non-owner execution warning only on tx creation (#3416)
fix: Disable tx execution for out of order nonce txs (#3467)
fix: only show safe sidebar on open Safes (#3463)
fix: reset safe info when URL changes (#3411)
style: remove on-chain rejection label (#3451)
Fix: show error msg when tx is not found (#3422)
fix: check that calculated gas price is a number (#3441)
fix: Disable queued Tx interaction while replacement Tx is pending (#3405)

Chores

docs: add info how to run prod version of the app
Chore: don't track 901 on Sentry (#3447)
chore: create codeql-analysis.yml; rm unused validator (#3485)
chore: update issue & PR templates (#3425)
fix: remove example address from env file (#3398)

The release looks good. The few issues found were solved. The issues with gas estimation in the GNO chain and the cancel status being shown as a contract interaction have been discussed outside of this ticket.
The tickets listed are fine and signing tx with different wallets in different networks work fine as well


Algorithm optimization of Pair methods create and update

Changes

No more Contact class (smaller source code)
Every vertex has a contact point (increasing memory footprint)
Pairs do not need to keep a map of current contacts (reducing memory footprint)
Contact ids do not need to be generated anymore
List of active contacts of a Pair are resized only when necessary
collision property added to Pair object at instantiation time to avoid future de-optimization.
Pair instantiation stripped of unnecessary parameter initialization that happen in the update method.
Some pair parameters are now only updated upon collision.

Result
Before the optimization:

After optimization:

We can see that the Pair.update method went from 7% of total used resources down to 0.13%.
That's a 50x improvement!
Overall, the profiling I performed on multiple tests seem to indicate a 6~7% boost to the engine.

Just tried implementing this and I'm seeing better results as well. My original performance was Pair.update at 13.9% and then V8 must have optimized it internally as I got a second entry at only 6.5%. After making the change the same very heavy test Pair.update used only 4.7% total. So well worth keeping in.

I am a bit surprised that you are only getting it down to 4.7%. All my tests suggest it is now well below 1% in every profile I make.

I've found a few issues here, at least when combined with #527, that I've been unable to resolve so far. While I much appreciate this work and potential improvements, unfortunately for the moment I've reverted this PR on master until we can find some way to fix.
It seems that combining the contacts into a single contact in this way appears to lower the quality of the result just a little too much. Maybe it can be solved, but it's not clear how.
I've completed some new work on tooling for comparing changes to the engine, discussed in PR #794, which I've used to confirm some stability and behaviour differences.
For those interested to see the issues I'm talking about, check out master on a commit before the revert that includes the comparison tool, e.g. fcdb4fa and run the dev server.
Go to http://localhost:8000/?compare#friction in the browser and wait for the box at the bottom to slide down and hit the wall.

The box bounces back a little in this version (shown in white), but not in the previous release version (overlayed here in gray). I know it seems like a minor detail, but the box should not bounce in this case as it has 0 restitution.
Also on http://localhost:8000/?compare#stress (and stress2), try collapse the stack by lifting a block on the top row up and left a little.

This version collapses much faster with a lot of bodies overlapping. The previous release version appears to hold up much better. This could just be resulting from a slight difference growing into a bigger one, but I can reproduce it every time in different ways. The testing tool also indicates this as an increase in average overlap.
I'm not sure whether #527 contributes more to this issue, but it appears that both need some review, hope that makes sense.


Non-reproducible build with scala_proto_library

Problem
Scalac sometimes embeds file path in compiled class (look for tmp514266449445771254 part):
javap -v $PWD/.../ErrorCode\$UNKNOWN_ERROR\$.class | grep bazel-out
   #40 = Utf8               Uninitialized field: bazel-out/k8-fastbuild/bin/schema-registry/proto/.../tmp514266449445771254/.../ErrorCode.scala: 22
   #41 = String             #40           // Uninitialized field: bazel-out/k8-fastbuild/bin/schema-registry/proto/.../tmp514266449445771254/.../ErrorCode.scala: 22
   #47 = Utf8               Uninitialized field: bazel-out/k8-fastbuild/bin/schema-registry/proto/.../tmp514266449445771254/.../ErrorCode.scala: 23
   #48 = String             #47           // Uninitialized field: bazel-out/k8-fastbuild/bin/schema-registry/proto/.../tmp514266449445771254/.../ErrorCode.scala: 23
        20: ldc           #41                 // String Uninitialized field: bazel-out/k8-fastbuild/bin/schema-registry/proto/.../tmp514266449445771254/.../ErrorCode.scala: 22
        20: ldc           #48                 // String Uninitialized field: bazel-out/k8-fastbuild/bin/schema-registry/proto/.../tmp514266449445771254/.../ErrorCode.scala: 23

ScalacWorker creates temporary directory if srcjar is given:
https://github.com/bazelbuild/rules_scala/blob/e21dd301e96e6f9146cfcbe820c37e2c9d194b93/src/java/io/bazel/rulesscala/scalac/ScalacWorker.java#L108
It's common to see scrjars in scalapb compilation.
Possible solution
Create temporary directory's name more predictably.
It can be hash of it's short_path or something similar.

Hi @darl, thanks for reporting this.
You mentioned

Scalac sometimes embeds file path in compiled class

Maybe you know under what circumstances it does that and why? I tried looking (with javap) at few compiled classes in rules_scala and couldn't find source paths being embedded.
Maybe you could provide repro?
I have a PR which addresses that but need to understand this issue fully and make sure this is right thing to do.

In my case its result of compilation of proto enums.
It compiles into case objects.
Minimal example taken from scalac tests (https://github.com/scala/scala/blob/8a2cf63ee5bad8c8c054f76464de0e10226516a0/test/files/run/checkinit.scala)
$ cat test.scala
trait U {
  val a = b
  def b: AnyRef
}

class U1 extends U { val b = "" }

$ scalac -Xcheckinit $PWD/test.scala && javap -v 'U1.class' | grep test.scala
  Compiled from "test.scala"
   #7 = Utf8               test.scala
  #24 = Utf8               Uninitialized field: /Users/darl/test.scala: 6
  #25 = String             #24            // Uninitialized field: /Users/darl/test.scala: 6
        22: ldc           #25                 // String Uninitialized field: /Users/darl/test.scala: 6
        22: ldc           #25                 // String Uninitialized field: /Users/darl/test.scala: 6
SourceFile: "test.scala"

Hi @darl
could you verify it's working for you and close this issue?
There was a regression https://github.com/bazelbuild/rules_scala/issues/1322 which was fixed in https://github.com/bazelbuild/rules_scala/pull/1323

I haven't tested for reproducibility yet.
But atleast it compiles fine.


[fr] Changed the command for Attaching to the shell container

https://github.com/kubernetes/website/pull/48267/files

/lgtm


Question reagrding spec.name for Grafana Dashboard CRD for Dashbord from URL

I have question regarding spec.name in Grafana Dashboard CRD for Dashbord from URL.
Is it mandatory to have .json suffix in spec.name? [1]
Reference:
[1] https://github.com/integr8ly/grafana-operator/blob/faceedabf2864402cc45767fe44ccd56e1b7955a/deploy/examples/dashboards/DashboardFromURL.yaml#L8

Good question, I don't think it is @pb82?

Good question, I don't think it is @pb82?

We are not using it indeed, and it appears that is not required consequently. Just wanted a confirmation from maintainers so that we can be more precise in the documentation.
Thank you very much! @HubertStefanski @pb82

@pacospace No, I believe the name is no longer used anywhere and we should remove it. For now, you can put any name in there.

@pacospace No, I believe the name is no longer used anywhere and we should remove it. For now, you can put any name in there.

I can open PR if you want :) I ll update out docs meanwhile to be more precise!

@pacospace Sure, We'll be happy to review and have it in :)


Add fill method to Arrays and PackedArrays

Closes godotengine/godot-proposals#2181
Based on the discussion on https://github.com/godotengine/godot/pull/46173
Adds a fill(value) method for Arrays and PackedArrays that allows filling the entire array with a single value.
Example usage:
var arr = Array()
arr.resize(4)
arr.fill(3.14)
print(arr) # [3.14, 3.14, 3.14, 3.14]

I would also like to thank @anberino. He ran all tests for me (since my gpu doesn't support vulkan) and this PR wouldnt be possible without his help.

I'm not sure about the extra logic for duplicating container types. Things like Array are passed by reference and is documented behavior, so I'd expect fill() to allocate needed elements to hold the same Array reference. Perhaps this can be made configurable. But I find it difficult to find a use case for filling an array elements with arrays/dictionaries, I think in most cases the method would be used by structures which are passed by value rather than reference.

While I agree it's a bit counter intuitive to duplicate, I though it would be a little weird to have an array where every position is the same object.
However, I can make it optional or simply remove the duplication, If requested.

Due to the reasons pointed by @Xrayez, I've removed the duplication on container types.
This should make the method more consistent and avoid future bugs related to duplicate(...).

I suggest refactoring the code this way:
// vector.h

template <class T>
void Vector<T>::fill(T p_elem) {
	T *p = ptrw();
	for (int i = 0; i < size(); i++) {
		p[i] = p_elem;
	}
}

// array.cpp

void Array::fill(const Variant &p_value) {
	ERR_FAIL_COND(!_p->typed.validate(p_value, "fill"));
	_p->array.fill(p_value);
}

Eliminates code duplication.
Improves performance. set() uses a write() proxy on each element access. Using ptrw() allows to modify the vector's contents directly. I've got x3 speed up on my machine on large arrays this way (at least on PackedByteArray).
Consistent with other Array method implementations.

Thanks for the feedback, @Xrayez.
I've updated the code and the documentation with your chances. I've also added the documentation for PackedVector2Array and PackedVector3Array, since I forgot to add them in the previous commits.

Thanks!

Can this get backported to 3.x?

Can this get backported to 3.x?

Yes, but this needs to be manually redone for 3.x.


media

I've created a new repo to host media files related to NodeOS, starting with a redraw of the NodeOS logo. I did it because I needed a good logo image for my thesis, so since there's no copy in vectorial format I did it. It follow the same proportions of the original logo in PNG format (or I think so), only fixed some minor adjustment on the lines. Also I've changed the colors to be someones from the basic VGA palette, so it can be correctly drawn on the console. Anyone is welcome to contribute with wallpapers or similar things based on the human interface guidelines colors and schemes... or not :-)
Comments? Questions? Suggestions?

Maybe this should be mentioned in the wiki or on the ReadMe?

Done in readme file ;-)


Drawer right padding in tvOS simulator

Describe the bug
While running the app on the tvOS simulator the drawer has a right side padding ( see the picture attached, it's the light blu padding on the right side of the drawer )
Screenshots

To Reproduce
Steps to reproduce the behavior:
Run the app on the tvOS simulator with npx expo run:ios
Expected behavior
The drawer should not have any white padding on the right side, like in Android TV, Fire TV and Web.
In the attached screenshot the right behavior

Hey @giolaq, can you assign this to me?

Assigned! Thank you!

Macbook is hating me, sorry for wasting your time.


about trainning set

Excuse me, can you share the hand keypoint detection dataset?

Sorry it's private dataset.


Security Attributes for DAPR Operator - Sentry - Sidecar Injector

Hi,
I want to close security recommendations for Kubernetes Cluster in Microsoft Defender for Cloud.
One of them is "Kubernetes clusters should disable automounting API credentials" and it can be solved by added "automountServiceAccountToken: false" for POD security "spec --> template --> spec"
spec:
  template:
    metadata:
    spec:
      automountServiceAccountToken: false

But when I am adding this value for the operator, sentry and sidecar injector, the pods give me CrashLoopBackOff status and that logs in below.
I try to add "volumes:" and "volumeMounts:" but there is nothing change for sentry and sidecar injector.
I try to add "env:" but there is nothing change for operator
How can I solve this?
DAPR Operator logs
level=info msg="log level set to: info" instance=dapr-operator-6f879fbff6-clhsr scope=dapr.operator type=log ver=1.10.8
level=info msg="metrics server started on :9090/" instance=dapr-operator-6f879fbff6-clhsr scope=dapr.metrics type=log ver=1.10.8
level=info msg="starting Dapr Operator -- version 1.10.8 -- commit e59b71de19bcb0625a3c7d1e8388c81742fdca42" instance=dapr-operator-6f879fbff6-clhsr scope=dapr.operator type=log ver=1.10.8
level=fatal msg="Unable to get controller runtime configuration, err: invalid configuration: no configuration has been provided, try setting KUBERNETES_MASTER environment variable" instance=dapr-operator-6f879fbff6-clhsr scope=dapr.operator type=log ver=1.10.8

DAPR Sentry logs
level=info msg="starting sentry certificate authority -- version 1.10.8 -- commit e59b71de19bcb0625a3c7d1e8388c81742fdca42" instance=dapr-sentry-67d6ff6d46-qqv56 scope=dapr.sentry type=log ver=1.10.8
level=info msg="log level set to: info" instance=dapr-sentry-67d6ff6d46-qqv56 scope=dapr.sentry type=log ver=1.10.8
level=info msg="metrics server started on :9090/" instance=dapr-sentry-67d6ff6d46-qqv56 scope=dapr.metrics type=log ver=1.10.8
panic: stat /home/nonroot/.kube/config: no such file or directory

goroutine 1 [running]:
github.com/dapr/dapr/utils.GetConfig()
        /home/runner/work/dapr/dapr/utils/utils.go:54 +0x85
github.com/dapr/dapr/pkg/sentry/config.getKubernetesConfig({0x1af7f28, 0xa})
        /home/runner/work/dapr/dapr/pkg/sentry/config/config.go:105 +0xc8
github.com/dapr/dapr/pkg/sentry/config.FromConfigName({0x1af7f28, 0xa})
        /home/runner/work/dapr/dapr/pkg/sentry/config/config.go:70 +0xf2
main.main()
        /home/runner/work/dapr/dapr/cmd/sentry/main.go:103 +0xacf

DAPR Sidecar Injector logs
level=info msg="log level set to: info" instance=dapr-sidecar-injector-76c494c55f-kmghh scope=dapr.injector type=log ver=1.10.8
level=info msg="metrics server started on :9090/" instance=dapr-sidecar-injector-76c494c55f-kmghh scope=dapr.metrics type=log ver=1.10.8
level=info msg="starting Dapr Sidecar Injector -- version 1.10.8 -- commit e59b71de19bcb0625a3c7d1e8388c81742fdca42" instance=dapr-sidecar-injector-76c494c55f-kmghh scope=dapr.injector type=log ver=1.10.8
panic: stat /home/nonroot/.kube/config: no such file or directory

goroutine 1 [running]:
github.com/dapr/dapr/utils.GetConfig()
        /home/runner/work/dapr/dapr/utils/utils.go:54 +0x85
github.com/dapr/dapr/utils.initKubeConfig()
        /home/runner/work/dapr/dapr/utils/utils.go:36 +0x1d
github.com/dapr/dapr/utils.GetKubeClient(...)
        /home/runner/work/dapr/dapr/utils/utils.go:64
main.main()
        /home/runner/work/dapr/dapr/cmd/injector/main.go:48 +0x296

The security policy automountServiceAccountToken: false is generally a great default to have for your deployments in Kubernetes as it means every workload won't have access to the Kubernetes API server by default, limiting blast radius due to a container file system leak or malicious access to a pod. However, this must be enabled on deployments which do intend to access the Kubernetes API server, because without it, they have no way to authenticate to the API server. This is why you are seeing the error you are.
The operator, sentry, and sidecar injector all require this setting to be true for this reason. It is also the case that the Dapr sidecars must also have this setting if you intend to use the Kubernetes API server as part of a component, like the Kubernetes Secret store for example https://docs.dapr.io/reference/components-reference/supported-secret-stores/kubernetes-secret-store/
I am going to close this as this is “working as expected”, but please feel free to reopen if you have any more questions 🙂


[Bug]: V8 coverage does not work with native ESM

Version
27.2.0
Steps to reproduce
As it was mentioned in https://github.com/facebook/jest/issues/9430#issuecomment-924826080, I was trying out V8 coverage with native ESM. Babel coverage works well, but for some reason there are issues with V8 coverage.
I was testing:

ESM without transforming, hence without source maps included
TypeScript modules transformed into ESM with source maps included

@SimenB thanks for quick response and hints. I started from creating failing tests inside a clone of Jest repo. The same result – coverage works well with Babel, but not with V8. So I will dig into the code and will try to find the reason.
Expected behavior
I also tried out coverage using c8 module directly on an ESM file (without involving Jest). All is good. Quick, nice and precise.
Similar result is expected.
Actual behavior
V8 coverage reports seems to be buggy.
Additional context
No response
Environment
System:
    OS: macOS 10.15.7
    CPU: (8) x64 Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz
  Binaries:
    Node: 16.9.1 - /usr/local/bin/node
    Yarn: 2.4.3 - /usr/local/bin/yarn
    npm: 7.21.1 - /usr/local/bin/npm

I'm also experiencing this on 27.2.1 with --coverage=true --coverageProvider=v8. I didn't check covered lines closely, but uncovered lines are off by ~3 lines it seems.
Running through c8 and using --coverage=false on jest, the uncovered line numbers are correct.

@SimenB The problem the clear. All works well with native ESM files, if the value of wrapperLength is 0 here. If I get it right, the wrapper here is the CJS module wrapper. In this case ~3 lines offset also makes sense.
Possible fix: check if the module wrapper will be used before assigning the value inside transformFile and transformFileAsync (here and here). Only question – what should be checked?

transformFile should only every be called with CJS and transformFileAsync should only ever be called with ESM.
Could you push your failing test case somewhere I can take a look?

Sure. I will send a PR tomorrow.

Found interesting case while cleaning up. I was trying to include empty-sourcemap test in the new coverage-provider-c8 test suite. A type is imported from types.ts to module.ts.
(1.) Babel transformer and Babel based coverage:

(2.) Any transformer and V8 based coverage (only types.ts line is in question, the rest is correct):

It is not ESM related, but still it made me curious. V8 checks if code was executed without inserting counters. types.ts is not executable and one should not expect coverage. Just exclude it manually from the coverage report and all is sorted out. But isn’t it too much manual work in the context of automated testing?
Just thinking out loud. There are two kinds of files – the ones which can be consumed directly and the others which have to be transpiled. If source file is transpiled, can V8 provide coverage without having a source map? It is not needed for directly consumed files, but what about the transpiled ones? Possible to try, but lines will not match in many cases.
What if V8 coverage would simply grey out transpiled files which do not have coverage (as in (1.))? ”Sorry, it is not possible to provide coverage for this file.”
In the other hand, if an executable file has no tests... It is much better idea to keep it red in the report instead of greying out. And might be worth to include a note on Babel / V8 coverage differences in documentation together with #11188.
@SimenB Could you confirm if this is expected behaviour? Looks so. I add it to tests like here, right?

If types.ts is not imported, we mark the entire file as uncovered. We should probably transform it and mark the transformed result as uncovered instead: https://github.com/facebook/jest/blob/da7c4a42840230ddaa7c101dbc86edb752787c64/packages/jest-reporters/src/generateEmptyCoverage.ts#L45-L67

Thanks for a hint. Now I see where '(empty-report)' was coming from. That one was a puzzle. Will play with the idea.


Move to D-guild's github org

Since the project is for the guild's use it shouldn't be @GitThisJoel's personal repo.

I totally agree. I would say that once we get both Swish and Zettle to work properly we can start moving this repo to D-sek.

@fnurkla have set this into motion again, will start to look into it again


Feature/implement orders

closes #17

Codecov Report

:exclamation: No coverage uploaded for pull request base (dev@0ba4b86). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff           @@
##             dev      #21   +/-   ##
======================================
  Coverage       ?   42.99%
======================================
  Files          ?       24
  Lines          ?     1107
  Branches       ?      187
======================================
  Hits           ?      476
  Misses         ?      622
  Partials       ?        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 0ba4b86...661ba68. Read the comment docs.


[Modal] Normalize the component & usage across all products.

This issue will serve as an umbrella for all issues (inconsistencies) found around the modal vs non-modal features noticed on all different products.

Material UI - we are missing a non-modal dialog demo. We technically have the hideBackdrop prop that makes this possible, but we are not educating people about this. The docs states "A Dialog is a type of modal window that appears in front of app content to provide critical information or ask for a decision. Dialogs disable all app functionality when they appear, and remain on screen until confirmed, dismissed, or a required action has been taken.", but there are also non-modal dialogs scenarios, that should likely support, for e.g. check https://accessuse.eu/en/non-modal-dialogs.html#:~:text=A non-modal dialog pops,partly covered by the dialog. This page has great examples of both use-cases https://www.nngroup.com/articles/modal-nonmodal-dialog/
Joy UI - we are missing a page for the Dialog, the only demo we have lives on the modal's page, it may not be straight forward to find it - https://mui.com/joy-ui/react-modal/#modal-dialog. The modal should be treated as a utility component, used in different components, we should not educate people to use it directly, but have components for the most common use-cases it is associated with, like dialogs, drawers etc.
Inconsistencies between using modal vs non-modal popups in some components. For e.g. on the Select component, Material UI uses a modal element for the options list - this means that when the select is open, users cannot directly take different action by clicking on an element outside of the list. For example try this demo - https://cml5vj.csb.app/ (open the select and try clicking on the button while it is opened). While this works great for mobile, the behavior is a bit odd on desktop, as you can likely find a spot to click in order to close the select without taking unintended action. On the contrast Base UI (and Joy UI) offer only the non-modal option, which works great on desktop, but could be problematic on mobile devices, where you may not have an available space to tab in order to close the select without taking an action. In my opinion we should support both of these scenarios in all libraries.

Joy UI - we are missing a page for the Dialog, the only demo we have lives on the modal's page, it may not be straight forward to find it - https://mui.com/joy-ui/react-modal/#modal-dialog. The modal should be treated as a utility component, used in different components, we should not educate people to use it directly, but have components for the most common use-cases it is associated with, like dialogs, drawers etc.

@siriwatknp for this one, I will start with moving the demos to a different page only. Long term, in my opinion we should have a Dialog component in Joy UI that should have both modal & non-modal version.


As part of PFWORKBIN-226, I'm removing potentially unsafe calls to me…

Removing potentially unsafe calls to memset() and using safer options.
A bit of tangential cleanup.

LGTM


Object spread error when collecting coverage with configured transform

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Tests fail to run and give the following error:
 FAIL  test\test.js
  ● Test suite failed to run

    jest-object-spread-bug/index.js: Unexpected token (7:2)
        5 | module.exports = {
        6 |   b: 2,
      > 7 |   ...obj,
          |   ^
        8 | };
        9 |

If the current behavior is a bug, please provide the steps to reproduce through a minimal
repository on GitHub that we can yarn install and yarn test.
Please see this demo repo: https://github.com/nwoltman/jest-object-spread-bug
What is the expected behavior?
Tests pass with 100% code coverage.
Please provide your exact Jest configuration and mention your Jest, node,
yarn/npm version and operating system.
Jest 21.2.1
Node 8.9.1 (which supports object spread syntax)
OS: Windows 10, Ubuntu 17.10
jest.config.js
module.exports = {
  collectCoverage: true,
  testEnvironment: 'node',
  transform: {},
};

The error only occurs while collecting coverage.
The error does not occur if transform is not set.

Related to issue #4248 which was partially fixed by PR #4519.
This issue is also sort of like reopening #5070 since you shouldn't have to use your own transformer to transform object spread syntax if it is natively supported by Node (especially since tests work just fine when not collecting coverage).

Fix upstream: https://github.com/istanbuljs/babel-plugin-istanbul/pull/141
If that is rejected, we can add the plugin on our side in here: https://github.com/facebook/jest/blob/df9234006a9c8592ede2539b0fb0832852272c77/packages/jest-runtime/src/script_transformer.js#L170-L180

Same issue here, hope this will be released soon :)
Is there a simple way to use your fix in jest/packages/jest-runtime/src/script_transformer.js while it is not released? (I can install jest package from df9234006a9c8592ede2539b0fb0832852272c77, but the fix is in jest-runtime...

If you use yarn, you can do
"resolutions": {
  "babel-plugin-istanbul": "SimenB/babel-plugin-istanbul#f467aee1e356f173ceb07f549894c597fae66311"
}

Thanks but we're using npm.
However, we noticed that when installing jest locally it works, but with jest installed globally it fails.
I don't understand yet the reason (maybe a version of a sub-dependency...).
This can do the trick in the meantime

Same issue:
"scripts": {
    "test": "jest",
...

"jest": {
    "coverageDirectory": "./coverage/",
    "collectCoverage": true
 }

"devDependencies": {
  "jest": "^22.0.4"

and node version if v8.9.1
npm test fails
      > 12 |     ...params,
           |     ^

Unexpected token

Without collectCoverage tests are green.
"jest": {
    "coverageDirectory": "./coverage/"
  }

👋 I just landed the upstream work @SimenB did on babel-plugin-istanbul, I've also given @SimenB commit access to the repo; sorry for blocking you for so long.

Since this has been fixed upstream you can now use this with yarn in package.json:
  "resolutions": {
    "babel-plugin-istanbul": "4.1.6"
  }

Awesome, thanks @bcoe! Bump in jest handled in #5799.
@rbong or just yarn upgrade or yarn remove jest && yarn add --dev jest. It's within semver range, so resolutions shouldn't be needed.

@SimenB I tried your solution, 4.1.6 is still tagged with "next" on npm so unfortunately resolutions are required in the short term until #5799 gets in or babel-plugin-istanbul tags 4.1.6 as "latest" (afaik)

Oh, good point.

@rbong @SimenB sorry for the slow turnaround, I just tagged 4.1.6 as latest on npm -- mind letting me know if this gets things working for you?

i am not sure what we are suppose to do i am using jest 24.9.0 and i still have the error


Review Dates pattern content

https://trello.com/c/NpCL3dpX/644-design-system-dates

Reviewed content; all is fine. Will progress with draft version.


fix: default env to master

This PR defaults the environment to master

I wonder whether it would be better to force the user to provide an environment id. I can see myself accidentally running a migration on master with this change, simply because I forgot to provide the environment id.

Hey @connor-baer some users might not have access to the environment feature and all of our other tools are defaulting to master for now, This might change when we reach the v1.0.0

To adress @connor-baer's doubt, I'd really like to have a Environment: <the-specified-environment>  in the plan output. As the called URLs are relative to the environment you don't see what you're executing against during runtime.

@connor-baer @zcei we now have the current environment displayed in the plan


Upgrade gatling version to 3.9.5

Description

Upgrade gatling version to 3.9.5
Upgrade java version to 17
Add rm option to use gatling.sh

I checked this change works correctly at my local by following commands.
$ make kind-create
$ kubectl config use-context kind-gatling-cluster
$ make build
$ make install-crd
$ make kind-deploy
$ make kind-sample-deploy

Also, I confirmed that Gatling 3.2.1 works fine with rm option. This means whether upgrading gatling version or not is up to gatling-operator users.
Checklist
Please check if applicable

[ ] Tests have been added (if applicable, ie. when operator codes are added or modified)
[ ] Relevant docs have been added or modified (if applicable, ie. when new features are added or current features are modified)

Relevant issue https://github.com/st-tech/gatling-operator/issues/84

@R-HNF
Thank you for all your comments.
I fixed them.
https://github.com/st-tech/gatling-operator/pull/96/commits/1bc64dfc92ab78a06dc5b93e57a4ba6fcd8b03a6

@R-HNF
I deleted unnecessary libc6-dev .
https://github.com/st-tech/gatling-operator/pull/96/commits/da6bc34fb826bd9ba377cfcf1cc2e44324262fa4


Upgrade Python dependencies for Dependabot alerts

Upgrade requests, Jinja2,  certifi and aiohttp.

Good point. I'll combine the pip install commands into one command.