Startup time is too long

It was mentioned in https://github.com/nortakales/vs-code-qalc/issues/32 that startup time for the extension can be upwards of 20 seconds. I'm personally seeing around 15 seconds. This is too long and should be investigated.

This is by far my slowest extension, but it's so useful that I don't want to disable it. Based on the linked issue above, if this is indeed due to the currency exchange rate API, I'm happy to just disable that if possible since I tend not to do anything with currencies.

At some point I had added some instrumentation to see where the time was being spent during startup, but I don't remember finding anything conclusive. That was quite a long time ago at this point though, so I definitely need to tackle that again. It can't be from fetching the exchange rates because the vast majority of the time it will grab them from a local cache. Especially if you just reload VSCode, it will definitely have cached values (but still takes a while for the extension to start).


Add default storage backend as etcd3

This PR adds parameter default storage backend to apiserver as etcd2. While launching k8s-cluster with kubernetes master branch (commit d82e51e) using kubernetes-anywhere. I found that kubernetes api-server fails with an error
E0111 03:00:53.829193   29597 status.go:62] apiserver received an error that is not an metav1.Status: rpc error: code = 13 desc = transport is closing
…
logging error output: "k8s\x00\n\f\n\x02v1\x12\x06Status\x12F\n\x04\n\x00\x12\x00\x12\aFailure\x1a0rpc error: code = 13 desc = transport is closing\"\x000\xf4\x03\x1a\x00\"\x00"

Currently, etcd3 is made as default storage backend for api-server and kubernetes-anywhere uses etcd2. Hence, this error occurs. This can be resolved by adding parameter storage-backend=etcd2 to apiserver manifest.
Refer this: https://github.com/kubernetes/kubernetes/issues/39710

I also changed parameter --config to --pod-manifest-path since it is no longer supported. Refer: https://github.com/kubernetes/kubernetes/pull/40048

@armstrongli I addressed your review comment. Can you please have a look?


Close mysql connection in TestXMySQL to prevent tests freezing

The unit tests freeze on my machine without this change because you can't drop a table until other connections that are using that table disconnect.

Thanks!
Can confirm this fixes it (have to admit I almost never ran those mysql tests locally ..)

Will just wait on travis to merge when green.

Do you have the same issue locally before this change?

yes, it specifically hangs on the test_execute_closed_connection test for me. But strange that it runs on travis OK. I almost never ran those old tests (TestXMySQL) locally, but relied on travis for these.
(BTW, we should clean this up once, remove that entire class, but check if there is still something tested there that is not tested in the other tests)


add pa11y

Starting to think how we build the a11y guidelines into our project.
I imagine it will be something similar to having docker container running an app and testing each one separately.
For now this uses devappy to give us an indication of what work we need to do to be passing.
The other idea would be to use pa11y-dash but I do wonder if it becomes something we then know about, but leave.
TODO

[ ] Get into CI

@davidpmccormick still in mega WIP - seeing if anyone wants to try add to it (get it in CI which is going to be tricky as you'll need to be running a version of the app in CI - potentially in docker)


self fetching the problemset every 3 days

can be solved with celery

temporarily built something to do this but better work with celery

playing around with firebase but saving datetime is weirdchamp


Add various usefull endpoints: get supported Architectures & Operating Systems

Hello,
Why not add some usefull endpoints to share more data with users.
Let's start with:

Supported Architectures
Support Operating Systems

What do you think?
Checklist

[X] You added tests to cover the change
[X] mvn clean install build and test completes
[ ] You changed or added to the documentation

My note from Slack: "In fact, we (the website) may use those endpoints instead of having lists hard coded in JS. That's why I started to write those endpoints"


PERF: Avoid using attribute access in inner event processing.

Reduce overhead of the attribute access of grabbing the process_event
and process_trade from both the algorithm object and the perf_tracekr or
blotter, by assigning those functions to a variable once per snapshot.

cc: @llllllllll

This looks correct, I had one comment about naming but functionally this looks good.

Fixed up and merged with 7059ba1e6a7c36f44226bbaed41d9e2f8a994d6d


is there supposed to be a ~/.rbenv/bin directory?

I have a server (OS X server) running several small rails applications. I had initially set it using brew to install ruby (could not get rvm to install!). I made some changes to one of the apps and ran into all kinds of problems with I updated the brew ruby version. I decided to try rbenv and set it up on the server. Lots of problems with clashes with the brew version that I eventually figured out.
I then tried to deploy and discovered that my bundle update loaded capistrano 3.1 and nothing worked. I started the conversion processes and I got stuck on:
set :rbenv_prefix, "RBENV_ROOT=#{fetch(:rbenv_path)} RBENV_VERSION=#{fetch(:rbenv_ruby)} #{fetch(:rbenv_path)}/bin/rbenv exec"

I have no bin directory on what brew installed for rbenv. I changed it to:
set :rbenv_prefix, "RBENV_ROOT=#{fetch(:rbenv_path)} RBENV_VERSION=#{fetch(:rbenv_ruby)} /usr/local/bin/rbenv exec"

and got it to work, but maybe I'm missing something.  I did get a basic deploy to work, but still have to get the rest of my 'railscast/recipes' to work, like writing plists for launchd etc.

Based on the settings listed in the Usage section of capistrano/rbenv, the following worked by changing the path to the actual rbenv executable (/usr/local/bin/rbenv).
set :rbenv_prefix, "RBENV_ROOT=#{fetch(:rbenv_path)} RBENV_VERSION=#{fetch(:rbenv_ruby)} /usr/local/bin/rbenv exec"

I had to set :rbenv_path, '/usr/local/opt/rbenv' in addition to @shawnpyle's solution to get rbenv to find the bundler executable.

@kirs, did you mean that this is already the default for rbenv_ruby and there's nothing to set?

If you use Homebrew, your rbenv_ruby path should be /usr/local/Cellar/rbenv/0.4.0

I'm wondering because you also said:

@mech rbenv_ruby should point to ruby version, not the directory with rbenv

Does this mean 'don't even set (rather than change) rbenv_prefix at all':

That means you don't need to change rbenv_prefix at all.

To avoid /Users/jason/.rbenv/bin/rbenv: No such file or directory, I had to:
ln -s /usr/local/Cellar/rbenv/1.1.1/bin ~/.rbenv/bin
Of course, this will break when rbenv is updated.
What's the proper way to set this up when installing with Homebrew? Thank you!
related: #52

In my case I installed the Ubuntu rbenv package. This seems to place the binary elsewhere (outside of the .rbenv path). To fix this you need to configure it explicitly:
set :rbenv_prefix, '/usr/bin/rbenv exec'

Use which rbenv on your server to find the correct location.
You can see the logic around this here::
https://github.com/capistrano/rbenv/blob/1fdb93a6dd4a4ab3fb786c995055cf6949daf7a4/lib/capistrano/tasks/rbenv.rake#L19
https://github.com/capistrano/rbenv/blob/1fdb93a6dd4a4ab3fb786c995055cf6949daf7a4/lib/capistrano/tasks/rbenv.rake#L35-L45


Redis backend, cannot release lock

Using a Redis backend, there is an error when the lock gets released:
AttributeError: type object 'Lock' has no attribute 'LUA_RELEASE_SCRIPT'
I can't find any other mention of this LUA_RELEASE_SCRIPT in the code.

LUA_RELEASE_SCRIPT is defined at here:
https://github.com/andymccurdy/redis-py/blob/e57daf554d6a4a66373de6605d13fb7a185852e9/redis/lock.py#L24
I have imported the Lock class of redis-py at line 251, I don't know why you got this error, you can check out if the Lock class here is reference to the redis.lock.Lock correctly.
Sorry for my poor English.


Reduce the number of threads for IngestionDelayTimerThread

while debugging some issue, we have observed that we create a lot of threads for IngestionDelayTimerThread. It would be better if we can cap this number.

According to https://stackoverflow.com/questions/1933520/java-timer-and-thread-it-creates, it recommends to use ScheduledExecutorService over Timer
IngestionDelayTracker:

    _timer.schedule(new TimerTask() {
        @Override
        public void run() {
          timeoutInactivePartitions();
        }
      }, INITIAL_TIMER_THREAD_DELAY_MS, _timerThreadTickIntervalMs);

cc: @jugomezv

Hey @snleee
Can I take this up?

Yes should be an easy change. I had this as follow up but have other tasks at work now.  @snleee we can let @cypherean take a stab? keep me in the loop for reviews


Remove JSON example campaign code and data

We've created a new /reset endpoint that generates an example campaign, and have removed the Playwright tests that relied on these JSON example campaigns. Removing these does mean that if we need to generate static/predictable campaign data again in the future, we'll need to develop a new way of doing it, but we'd prefer to do this with the factories directly instead of using an intermediary JSON file.

This also means that our review apps won't have example data loaded. Do we want add (in a later PR) a way to load up example data from a rake task?

This also means that our review apps won't have example data loaded. Do we want add (in a later PR) a way to load up example data from a rake task?

Once we fix the review apps, we'll worry about that 😂


Whylogs is getting blocked in Intel Dev Cloud

Code
for i in range(1):
self.logger.log_image(Image.fromarray(np.random.random((10,10))), feature_name="Random Image")
self.logger.log({'a': 'abcdef'})
self.logger.flush()
self.logger.close()
This code does not show any output. But if you comment out the log_image code line, and just log the dictionary, it gives the output.
Steps to replicate:
Platform:
Intel Dev Cloud

Thanks, IDC tested this for me.
https://community.intel.com/t5/Intel-DevCloud/In-Intel-Dev-Cloud-whylogs-package-is-not-working/m-p/1378455/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufEwyN0dSSU5PMlJIQVNPfDEzNzg0NTV8U1VCU0NSSVBUSU9OU3xoSw#M4669
There is no bug on this issue, may be its just a platform issue.

How did you create and configure the:
self.logger

You might want to modify the configuration around where the writers are saving whylogs profiles. The call to logger.flush() will call configured writers to write the output. The default uses a local file writer (like in this example: https://github.com/whylabs/whylogs-examples/blob/mainline/python/GettingStarted.ipynb), but you can pass in a config file to change the behavior: https://github.com/whylabs/whylogs/blob/mainline/examples/.whylogs_local.yaml like in this notebook: https://github.com/whylabs/whylogs-examples/blob/mainline/python/MLFlow Integration Example.ipynb or you can configure the writers in code like in our Whylabs examples https://github.com/whylabs/whylogs-examples/blob/mainline/python/WhyLabs_Platform.ipynb)

I set it same as example provided below:
https://github.com/whylabs/whylogs-examples/blob/mainline/python/MLFlow Integration Example.ipynb
from whylogs import get_or_create_session
assert whylogs.version >= "0.1.13" # we need 0.1.13 or later for MLflow integration
session = get_or_create_session(".whylogs_mlflow.yaml")
whylogs.enable_mlflow(session)
I'm also using MLFlow in my example. But coding it later.

Hi @aswinvk28 I wanted to follow up to see if you're still experiencing problems. We'd love to help get you enjoying whylogs! I'll be watching here, but we also have a wonderful slack community http://join.slack.whylabs.ai/

Thanks @TheMellyBee


Could the remote's microphone be utilized as well?

I would say no, for two main reasons:

It's not supported by Wouterdek/magic4pc
It's unclear if we could do it without a rooted TV

What would you do with it? Assuming you could, would you stream the audio from remote -> magic4linux and try to do some voice recognition on the stream? How would we expose that in a way that you can build around? As for magic4linux, I don't think we should add any voice recognition logic into the service itself.
I'll close this now, but if you feel there is more to discuss around this topic, feel free.


Fixes nfs-server security issue in image

@jsafrane and I found this issue while debugging the e2e test for recycling.  The pod couldn't write/delete from the NFS volume.
2 of 5 PRs created from #8334
@thockin

@saad-ali would you please build/push this new image like you did for @jsafrane in #7435?

Will do

Done.
Pushing tag for rev [50c2f96d4105] on {https://gcr.io/v1/repositories/google_containers/volume-nfs/tags/0.2}

@saad-ali thank you!


RGB exposure settings takes 'forever' until active

Required Info

Camera Model
D435i

Firmware Version
<IP_ADDRESS>

Operating System & Version
{Win 10

Kernel Version (Linux Only)

Platform
PC

SDK Version
2.53.1

Language
python

Segment
Robot

Issue Description
Setting:

RGB @ 30 FPS with 1920 x 1080 (auto-exposure off)
IR1/2 @ 30  FPS with 1280 x 720 (auto-exposure on, dark environement: typical IR exposure times: 10.000 to 20.000 us)
depth @ 30 FPS with 1280 x 720

Setting RGB exposure values of 5000 or 10000 using set_option() and retrieving the resulting frame via wait_for_frames() often does not result in a frame where the settings is applied (checked via frame_metadata_value.actual_exposure).
It takes up to several hundred frames, until the new setting is active (I set it again if the actual value does not match the desired value).
The setting is applied faster, if I deactivate IR1 and IR2. But I would like to use IR1 and IR2 as well.
Is this a known issue?

Hi @Siegel20  The RGB exposure uses a different scale to depth exposure.  RGB exposure uses small values such as 156, whilst depth exposure uses large values such as 33000.  So in most cases RGB exposure should not be set to 5000 or 10000, even though doing so is supported.
In a test that I performed in the RealSense Viewer with RGB exposure of 156 and 10000, at 156 it had an FPS of 30 whilst at 10000 exposure it had an FPS of 0 and a 'No Frames Received' error.

I will try to have enough light so I can avoid getting into these problems. Thank you.

You are very welcome.  Thanks very much for the update!


Initial unit tests

Part of #33

@streeve @pzhanggit
I understand that something in the code need to be changed. But given the current structure of the code, I think all the model pass the tests with a random data generated from scratch.
New changes can be suggested in a new pull request after this one has been merged.

@streeve @jychoi-hpc
I think that everything that has to do with creation, modification from raw data to .pkl data, and destruction of folders/data has to be safeguarded by barriers and per performed only by the master process.


Add 3rd party dependencies wget file

We depend on some 3rd party jars, which we pick up from external sites.  We can add the file that contains the links to the TestConfig/lib folder, so that a user can run wget -f dependencies.txt to pick them up and have them in TestConfig/lib (where we expect them to be found).
We will also need to update README to indicate these dependencies (will be done as part of issue 1).

@smlambert We've tended to use Ansible or a set of shell scripts to pull those down.  Might be worth a chat to @gdams and @neomatrix369 to see if we can merge some of those efforts?

Actually, I guess we do have a shell script that does this https://github.com/AdoptOpenJDK/openjdk-tests/blob/master/get.sh, which we should edit, so that the fetch of the adoptopenjdk binary is optional if you want to run tests with your own SDK.

With #12 people could do following to wget third party jars:
cd openjdk-test
get.sh


Min Pickaxe Tier

Updated my mod to version 1.0.3 and suddenly I was unable to mine black metal veins due to being "too hard".
I checked the config and changed all pickaxe tier requirements from:
3 → 2
2 → 1
This fixed the issue.
And from that I gather it goes as follows:
Antler Pickaxe = Tier 0
Bronze Pickaxe = Tier 1
Iron Pickaxe = Tier 2

Base game has no tier 3 pickaxe.

default config fixed


Fixes for a few errors being thrown

Allow 'stroke' to be a gradient or pattern in __applyStyleToCurrentElement. Before an error would be thrown as it would attempt to run indexOf on the gradient or pattern.
Fix issue with mixing transforms with path commands #44. Before the following error would be thrown "Attempted to apply path command to node g".
Fix thrown error when using ctx.closePath without creating a path

@webspinner Sorry, I am not seeing the statement you are referring to. Could you provide a snippet or the line number where you're seeing the issue?

@canavandl Thanks for explaining. This has been sorted out.

I've tested this locally and it works for me. What else needs to happen to get this merged/released?

@canavandl the last commit merged to this project was more than a year ago. I think it is likely that we will need to fork this repo into the our org and make the changes we need there.

Sorry, yes I no longer work for Gliffy or manage this project. You can find there contact data at gliffy.com

Thanks, I've emailed<EMAIL_ADDRESS>though I expect we will just have to maintain a fork.

We're discussing our open source projects internally so we don't just abandon people! Thanks for your patience.

@spanktar thanks for the update, we've gone ahead and forked for the time being in order to make a release schedule next week, but will look forward to getting back on an official releases in the future!

Thanks for your patience!  Took awhile since we use this internally and didn't really have the testing mechanism behind it to merge without some legwork.  We've tagged master before this merge for reference.


unable to start or create Service for component with "odo push --build-command"

/kind bug

What versions of software are you using?

Running test on travis CI.
Actual behavior
Running odo with args [odo preference set Experimental true]
[odo] I0724 07:25:04.478713    1559 preference.go:196] The path for preference file is /tmp/537875377/config.yaml
[odo] Global preference was successfully updated
[odo] I0724 07:25:04.479071    1559 odo.go:72] Could not get the latest release information in time. Never mind, exiting gracefully :)
Setting KUBECONFIG=/tmp/537875377/config
Creating a new project: nbdkxklnsr
Running odo with args [odo project create nbdkxklnsr -w -v4]
[...]
Running odo with args [odo create java-openliberty dehkdp --project nbdkxklnsr]
[odo] Experimental mode is enabled, use at your own risk
[...]
Running odo with args [odo push --project nbdkxklnsr]
[odo] I0724 07:25:22.131092    1805 preference.go:196] The path for preference file is /tmp/537875377/config.yaml
[odo] I0724 07:25:22.131212    1805 context.go:69] absolute devfile path: '/tmp/537875377/devfile.yaml'
[...]
[odo]  ✓  Changes successfully pushed to component
Running odo with args [odo push --build-command devbuild -f --project nbdkxklnsr]
[odo] I0724 07:26:00.081421    3556 preference.go:196] The path for preference file is /tmp/537875377/config.yaml
[odo] I0724 07:26:00.082282    3556 context.go:69] absolute devfile path: '/tmp/537875377/devfile.yaml'
[odo] I0724 07:26:00.088271    3556 content.go:33] converted devfile YAML to JSON
[odo] I0724 07:26:00.088367    3556 apiVersion.go:50] devfile apiVersion: '2.0.0'
[odo] I0724 07:26:00.088402    3556 helper.go:35] devfile apiVersion '2.0.0' is supported in odo
[odo] I0724 07:26:00.094409    3556 schema.go:47] validated devfile schema
[odo] I0724 07:26:00.336537    3556 content.go:33] converted devfile YAML to JSON
[odo] I0724 07:26:00.336609    3556 apiVersion.go:50] devfile apiVersion: '2.0.0'
[odo] I0724 07:26:00.336626    3556 helper.go:35] devfile apiVersion '2.0.0' is supported in odo
[odo] I0724 07:26:00.343428    3556 schema.go:47] validated devfile schema
[odo] I0724 07:26:00.394435    3556 content.go:33] converted devfile YAML to JSON
[odo] I0724 07:26:00.394539    3556 apiVersion.go:50] devfile apiVersion: '2.0.0'
[odo] I0724 07:26:00.394556    3556 helper.go:35] devfile apiVersion '2.0.0' is supported in odo
[odo] I0724 07:26:00.399259    3556 schema.go:47] validated devfile schema
[odo] I0724 07:26:00.402781    3556 parse.go:83] overriding data of devfile with URI: https://raw.githubusercontent.com/odo-devfiles/registry/f56180b89556ee2945a355ac0dcf3428d3ab35c7/devfiles/java-openliberty/devfile.yaml
[odo] I0724 07:26:00.402998    3556 parse.go:106] adding data of devfile with URI: https://raw.githubusercontent.com/odo-devfiles/registry/f56180b89556ee2945a355ac0dcf3428d3ab35c7/devfiles/java-openliberty/devfile.yaml
[odo] I0724 07:26:00.403020    3556 parse.go:83] overriding data of devfile with URI: https://gist.githubusercontent.com/mik-dass/6f88d133b73e90bc52ffcda92833b625/raw/cc46d1ba348cd085855f163b269c0f1be87226c4/devfile-middle.yaml
[odo] I0724 07:26:00.403200    3556 parse.go:106] adding data of devfile with URI: https://gist.githubusercontent.com/mik-dass/6f88d133b73e90bc52ffcda92833b625/raw/cc46d1ba348cd085855f163b269c0f1be87226c4/devfile-middle.yaml
[odo] I0724 07:26:00.403219    3556 validate.go:32] Successfully validated devfile sections
[odo] I0724 07:26:00.403435    3556 preference.go:196] The path for preference file is /tmp/537875377/config.yaml
[odo] I0724 07:26:04.007138    3556 preference.go:196] The path for preference file is /tmp/537875377/config.yaml
[odo] I0724 07:26:04.007265    3556 preference.go:196] The path for preference file is /tmp/537875377/config.yaml
[odo] I0724 07:26:04.007333    3556 preference.go:196] The path for preference file is /tmp/537875377/config.yaml
[odo] I0724 07:26:04.007396    3556 context.go:69] absolute devfile path: '/tmp/537875377/devfile.yaml'
[odo] I0724 07:26:04.007621    3556 content.go:33] converted devfile YAML to JSON
[odo] I0724 07:26:04.007666    3556 apiVersion.go:50] devfile apiVersion: '2.0.0'
[odo] I0724 07:26:04.007673    3556 helper.go:35] devfile apiVersion '2.0.0' is supported in odo
[odo] I0724 07:26:04.011758    3556 schema.go:47] validated devfile schema
[odo] I0724 07:26:04.061397    3556 content.go:33] converted devfile YAML to JSON
[odo] I0724 07:26:04.061534    3556 apiVersion.go:50] devfile apiVersion: '2.0.0'
[odo] I0724 07:26:04.061596    3556 helper.go:35] devfile apiVersion '2.0.0' is supported in odo
[odo] I0724 07:26:04.094639    3556 schema.go:47] validated devfile schema
[odo] I0724 07:26:04.144820    3556 content.go:33] converted devfile YAML to JSON
[odo] I0724 07:26:04.144951    3556 apiVersion.go:50] devfile apiVersion: '2.0.0'
[odo] I0724 07:26:04.144997    3556 helper.go:35] devfile apiVersion '2.0.0' is supported in odo
[odo] I0724 07:26:04.149876    3556 schema.go:47] validated devfile schema
[odo] I0724 07:26:04.150045    3556 parse.go:83] overriding data of devfile with URI: https://raw.githubusercontent.com/odo-devfiles/registry/f56180b89556ee2945a355ac0dcf3428d3ab35c7/devfiles/java-openliberty/devfile.yaml
[odo] I0724 07:26:04.150227    3556 parse.go:106] adding data of devfile with URI: https://raw.githubusercontent.com/odo-devfiles/registry/f56180b89556ee2945a355ac0dcf3428d3ab35c7/devfiles/java-openliberty/devfile.yaml
[odo] I0724 07:26:04.150257    3556 parse.go:83] overriding data of devfile with URI: https://gist.githubusercontent.com/mik-dass/6f88d133b73e90bc52ffcda92833b625/raw/cc46d1ba348cd085855f163b269c0f1be87226c4/devfile-middle.yaml
[odo] I0724 07:26:04.150440    3556 parse.go:106] adding data of devfile with URI: https://gist.githubusercontent.com/mik-dass/6f88d133b73e90bc52ffcda92833b625/raw/cc46d1ba348cd085855f163b269c0f1be87226c4/devfile-middle.yaml
[odo] I0724 07:26:04.150476    3556 validate.go:32] Successfully validated devfile sections
[odo] I0724 07:26:04.150650    3556 preference.go:196] The path for preference file is /tmp/537875377/config.yaml
[odo] I0724 07:26:04.150734    3556 preference.go:196] The path for preference file is /tmp/537875377/config.yaml
[odo] I0724 07:26:04.152532    3556 preference.go:196] The path for preference file is /tmp/537875377/config.yaml
[odo] I0724 07:26:04.152695    3556 preference.go:196] The path for preference file is /tmp/537875377/config.yaml
[odo] I0724 07:26:12.020285    3556 pods.go:31] Waiting for component=dehkdp pod
[odo] I0724 07:26:13.516316    3556 pods.go:58] Status of dehkdp-8668c66c76-lfj92 pod is Running
[odo] I0724 07:26:13.516401    3556 pods.go:64] Pod dehkdp-8668c66c76-lfj92 is Running
[odo]
[odo] Validation
[odo]  •  Validating the devfile  ...
[odo] I0724 07:26:13.516658    3556 command.go:65] the command group of kind "init" is not found in the devfile
[odo] I0724 07:26:13.516684    3556 command.go:258] No init command was provided
[odo] I0724 07:26:13.516720    3556 utils.go:98] Found component "Container" with name "appsodyrun"
[odo] I0724 07:26:13.516753    3556 command.go:275] Build command: devbuild
[odo] I0724 07:26:13.516766    3556 utils.go:98] Found component "Container" with name "appsodyrun"
[odo] I0724 07:26:13.516798    3556 command.go:282] Run command: devrun
 ✓  Validating the devfile [244218ns]
[odo]
[odo] Creating Kubernetes resources for component dehkdp
[odo] I0724 07:26:13.516907    3556 utils.go:98] Found component "Container" with name "appsodyrun"
[odo] I0724 07:26:13.517144    3556 utils.go:98] Found component "Container" with name "appsodyrun"
[odo] I0724 07:26:13.517186    3556 command.go:65] the command group of kind "debug" is not found in the devfile
[odo] I0724 07:26:13.517201    3556 utils.go:270] Updating container appsodyrun entrypoint with supervisord
[odo] I0724 07:26:13.517239    3556 utils.go:149] Updating container appsodyrun with supervisord volume mounts
[odo] I0724 07:26:13.517263    3556 utils.go:159] Updating container appsodyrun env with run command
[odo] I0724 07:26:13.517280    3556 utils.go:177] Updating container appsodyrun env with run command's workdir
[odo] I0724 07:26:13.517310    3556 utils.go:98] Found component "Container" with name "appsodyrun"
[odo] I0724 07:26:13.517341    3556 utils.go:98] Found component "Container" with name "appsodyrun"
[odo] I0724 07:26:13.517365    3556 adapter.go:306] Creating deployment dehkdp
[odo] I0724 07:26:13.517400    3556 adapter.go:307] The component name is dehkdp
[odo] I0724 07:26:13.517423    3556 adapter.go:311] The component already exists, attempting to update it
[odo] I0724 07:26:23.216674    3556 adapter.go:316] Successfully updated component dehkdp

[odo]  ✗  Failed to start component with name dehkdp. Error: Failed to create the component: unable to create or
update component: unable to create Service for dehkdp: Post
https://<IP_ADDRESS>:8443/api/v1/namespaces/nbdkxklnsr/services: read tcp <IP_ADDRESS>:44140-><IP_ADDRESS>:8443: read:
connection reset by peer

Deleting project: nbdkxklnsr
Running odo with args [odo project delete nbdkxklnsr -f]
[odo]  ✗  The project nbdkxklnsr does not exist. Please check the list of projects using `odo project list`
• Failure [84.793 seconds]
odo devfile push command tests
/home/travis/gopath/src/github.com/openshift/odo/tests/integration/devfile/cmd_devfile_push_test.go:17
  Handle devfiles with parent
  /home/travis/gopath/src/github.com/openshift/odo/tests/integration/devfile/cmd_devfile_push_test.go:663
    should handle a multi layer parent [It]
    /home/travis/gopath/src/github.com/openshift/odo/tests/integration/devfile/cmd_devfile_push_test.go:689
    No future change is possible.  Bailing out early after 28.693s.
    Running odo with args [odo push --build-command devbuild -f --project nbdkxklnsr]
    Expected
        <int>: 1
    to match exit code:
        <int>: 0

Expected behavior
"odo push --build-command" should start the component during validation
Any logs, error output, etc?

Similar failure - https://travis-ci.com/github/openshift/odo/jobs/364609348#L538

I have observed similar failure occurring frequently on the prs.
One of the pr facing the same issue #3635
[odo]  •  Waiting for component to start  ...
 ✓  Waiting for component to start [3s]
[odo] I0724 13:50:24.784500    5616 deployments.go:92] Deployment "wgyrhu" successfully rolled out
[odo] I0724 13:50:24.784515    5616 deployments.go:96] Waiting for deployment spec update to be observed...
[odo] I0724 13:50:24.784569    5616 pods.go:31] Waiting for component=wgyrhu pod
[odo] I0724 13:50:24.881494    5616 pods.go:58] Status of wgyrhu-74f894b7b6-zsr88 pod is Running
[odo] I0724 13:50:24.881519    5616 pods.go:64] Pod wgyrhu-74f894b7b6-zsr88 is Running
[odo] I0724 13:50:24.881586    5616 preference.go:196] The path for preference file is /tmp/873789133/config.yaml
[odo] I0724 13:50:25.149844    5616 url.go:402] Listing ingresses with label selector: app.kubernetes.io/instance=wgyrhu
[odo] I0724 13:50:26.415250    5616 url.go:379] Listing routes with label selector: app.kubernetes.io/part-of=,app.kubernetes.io/instance=wgyrhu
[odo] I0724 13:50:26.415284    5616 occlient.go:2653] Listing routes with label selector: app.kubernetes.io/part-of=,app.kubernetes.io/instance=wgyrhu
[odo]  ✗  Failed To Update Config To Component Deployed.
[odo] Error: unable to list route names: unable to get route list: Get https://<IP_ADDRESS>:8443/apis/route.openshift.io/v1/namespaces/kvbrvbyknb/routes?labelSelector=app.kubernetes.io%2Fpart-of%3D%2Capp.kubernetes.io%2Finstance%3Dwgyrhu: unexpected EOF
Deleting project: kvbrvbyknb
Running odo with args [odo project delete kvbrvbyknb -f]
[odo]  ✗  The project kvbrvbyknb does not exist. Please check the list of projects using `odo project list`
• Failure [114.763 seconds]
odo devfile push command tests
/home/travis/gopath/src/github.com/openshift/odo/tests/integration/devfile/cmd_devfile_push_test.go:17
  Handle devfiles with parent
  /home/travis/gopath/src/github.com/openshift/odo/tests/integration/devfile/cmd_devfile_push_test.go:685
    should handle a multi layer parent [It]
    /home/travis/gopath/src/github.com/openshift/odo/tests/integration/devfile/cmd_devfile_push_test.go:711
    No future change is possible.  Bailing out early after 40.184s.
    Running odo with args [odo push --build-command devbuild -f --project kvbrvbyknb]
    Expected
        <int>: 1
    to match exit code:
        <int>: 0

Not sure why everytime --build-command throwing error.
✓  Syncing files to the component [23s]
[odo]
[odo] Executing devfile commands for component lbzila
[odo]  •  Executing firstbuild command "npm install"  ...
[odo] I0724 17:03:00.530396   23162 exec.go:27] Executing command [/bin/sh -c cd ${CHE_PROJECTS_ROOT}/nodejs-starter && npm install] for pod: lbzila-767764b4bc-rt62c in container: runtime
[odo] I0724 17:03:14.501962   23162 adapter.go:453] Executing devfile command singleenv
[odo] I0724 17:03:14.502044   23162 exec.go:27] Executing command [/opt/odo/bin/supervisord ctl stop all] for pod: lbzila-767764b4bc-rt62c in container: runtime
 ✓  Executing firstbuild command "npm install" [14s]
[odo]  •  Executing singleenv command "mkdir $ENV1"  ...
[odo]  ✗  Executing singleenv command "mkdir $ENV1" [521ms]
[odo]  ✗
[odo] Unable to exec command [/opt/odo/bin/supervisord ctl stop all]:
[odo]
[odo]  ✗  Failed to start component with name lbzila. Error: Failed to create the component: unable to execute the run command: error while streaming command: error sending request: Post https://<IP_ADDRESS>:8443/api/v1/namespaces/jqasdveqmv/pods/lbzila-767764b4bc-rt62c/exec?command=%2Fopt%2Fodo%2Fbin%2Fsupervisord&command=ctl&command=stop&command=all&container=runtime&stderr=true&stdout=true: read tcp <IP_ADDRESS>:50428-><IP_ADDRESS>:8443: read: connection reset by peer
Deleting project: jqasdveqmv
Running odo with args [odo project delete jqasdveqmv -f]
[odo]  ✗  The project jqasdveqmv does not exist. Please check the list of projects using `odo project list`
• Failure [59.825 seconds]
odo devfile push command tests
/home/travis/gopath/src/github.com/openshift/odo/tests/integration/devfile/cmd_devfile_push_test.go:17
  exec commands with environment variables
  /home/travis/gopath/src/github.com/openshift/odo/tests/integration/devfile/cmd_devfile_push_test.go:556
    Should be able to exec command with single environment variable [It]
    /home/travis/gopath/src/github.com/openshift/odo/tests/integration/devfile/cmd_devfile_push_test.go:557
    No future change is possible.  Bailing out early after 55.657s.
    Running odo with args [odo push --build-command firstbuild --run-command singleenv --namespace jqasdveqmv --context /tmp/814552147]
    Expected
        <int>: 1
    to match exit code:
        <int>: 0

One more occurence in pr #3635

Have you been able to reproduce this outside our CI environment?
All the error images look like network related

Tried thrice and none of the time i hit the issue locally

@kadel Recently most of our periodic and few pr test failing at same spec - https://github.com/openshift/odo/blob/master/tests/integration/devfile/cmd_devfile_push_test.go#L557. This time same spec hit with a different error in periodic job.
✓  Syncing files to the component [1s]
[odo]
[odo] Executing devfile commands for component tmwocz
[odo]  •  Executing devbuild command "touch blah.js"  ...
[odo] I0729 02:15:48.917034   13610 exec.go:27] Executing command [/bin/sh -c cd ${CHE_PROJECTS_ROOT}/nodejs-starter && touch blah.js] for pod: tmwocz-5945596784-k575v in container: runtime
[odo] /bin/sh: line 0: cd: /project/nodejs-starter: No such file or directory
[odo]  ✗  Executing devbuild command "touch blah.js" [617ms]
[odo]  ✗
[odo] Unable to exec command [/bin/sh -c cd ${CHE_PROJECTS_ROOT}/nodejs-starter && touch blah.js]:
[odo] /bin/sh: line 0: cd: /project/nodejs-starter: No such file or directory
[odo]
[odo]  ✗  Failed to start component with name tmwocz. Error: Failed to create the component: unable to execute the build command: error while streaming command: command terminated with exit code 1

Details:
Periodic job - https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-odo-master-v4.5-integration-e2e-periodic/1288263134854778880#1:build-log.txt%3A1034
Pr job - https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_odo/3573/pull-ci-openshift-odo-master-v4.5-integration-e2e/1288284114700472320

closing this issue as it seems to be network related


types-protobuf dependency is still on 3.x, while package supports protobuf 4.x

Hi, the title says it all.
The problem with types-protobuf 3.x for me is this issue https://github.com/python/typeshed/issues/5800.
In short: using types-protobuf 3.x overrides google cloud SDK typings, so I want to upgrade.
Can we change
protobuf = ">=3.20"
types-protobuf = "~3.20"

to
protobuf = ">=3.20"
types-protobuf = ">=3.20"

?

Definitely can change that. I should have done so when backporting this library to work with proto 3.x library. Feel free to PR or wait a bit and I'll get to it. Thanks for the report!

Good, I guess I'll try to make a PR


Deciding on the User Interface

decide on the user interface between the following options:
Angular JS
React JS

For UI, we are using JavaFX


Support for JSON projections

New feature, discussed long ago this PR adds the possibility of adding projections for JSON results. This gives the user the possibility of providing a pythonql script which will transform the JSON coming from the triplestore into a different format.
An example repo is provided. Query dbpediaCapitalsLocation fetches from dbpedia location of country capitals. dbpediaCapitalsLocation.pyql transforms the result to a GeoJSON file.
Calling this endpoint
curl -X GET "http://localhost:8088/api/c-martinez/grlc-queries/dbpediaCapitalsLocation" -H "accept: application/json"
Would usually return something like this:
{
  "head": {
    "link": [],
    "vars": [
      "country_name",
      "capital_name",
      "population",
      "lat",
      "long"
    ]
  },
  "results": {
    "distinct": false,
    "ordered": true,
    "bindings": [
      {
        "country_name": {
          "type": "literal",
          "xml:lang": "en",
          "value": "Algeria"
        },
...
}

With the new projection functionality, it would return something like this:
{
  "type": "FeatureCollection",
  "features": [
    {
      "geometry": {
        "type": "Point",
        "coordinates": [
          3.21667,
          36.7667
        ]
      },
      "type": "Feature",
      "properties": {
        "name": "Algeria, Algiers",
        "population": "40400000"
      }
    },
    {
      "geometry": {
        "type": "Point",
        "coordinates": [
          49.8822,
          40.3953
        ]
      },
      "type": "Feature",
      "properties": {
        "name": "Azerbaijan, Baku",
        "population": "9754830"
      }
...
}

Comments?

I'm merging so we have this up to dev.grlc.io ready to test, but I had no time to review.
@c-martinez please let me know if this breaks something dramatic on dev and I'll roll back

Good - I'll test it in the next couple of days


add new interface option for skipping interfaces

Description
Added an option to skip network interfaces specified by regexes so that users can have first-found logic without having to manually specify system/setup specific interfaces to skip by changing the code.
Is required for https://github.com/projectcalico/calicoctl/pull/1675
Addresses https://github.com/projectcalico/calicoctl/issues/1555
Testing

Added unit tests
Ran modified calicoctl commands against an image of these changes to verify that if regexes were specified, they would not be picked up to be used.

Looks as though the STs are failing now.  I suspect it's because the STs are running with the wrong version of calico/node and is probably related to the recent move of calico/node from the calicoctl repo to calico.

Couple of minor comments. I'm wondering though - and worth getting another opinion ... should we update the "interface=" method to also allow a list of interfaces to select - that wouldn't break the existing behavior and would mean the interface and skip interface methods were nicely aligned.

STs are failing because they are running the wrong version of calicoctl, if I move the binary from the changes in the linked PR over, then I can get the tests to pass locally.  I mixed up the dependency in the above description so I'll fix that too.


Implement static residual for single beam

We need to develop the infrastructure to calculate the residual vector for a single beam under static loading condition. The theoretical development for this work could be found in the accompanying theory guide for openturbine. The screenshot below provides an excerpt of the article.

Faisal is implementing this as a single large routine. He has a unit test in place. It is likely the routine will need to be broken into parts with additional new unit testing.

Faisal has been breaking this up into several different functions and pushed those changes. These can now be unit tested.

Need perhaps two more days to implement/debug the static residual.   Need to get the results to match up with mathematica; satisfy unit tests.

10/10 Sprint Mtg: Static residual is implemented but is failing unit tests.

Add one more unit tests to make sure we get zero back when you set mathematica scale value to zeros.


doc directory is missing

Description
IN v17.24.0 of the module there was a docs folder on the root.  If is missing ever since v18.0.  On the of the resources in that docs folder was a minimum privileged policy for EKS cluster creation.  Is the missing docs folder a bug? is the info inter still valid?
Solution
Add the missing docs folder with updated content

hi @darnone - no, that was intentionally removed. We are trying to consciously provide ample information on how the module is designed and its usage patterns, but we do not want to document general EKS/Kubernetes issues/practices (there are many other sources for these).
For the minimum IAM policy, this was removed due to the complexity required to maintain based on the number of different possible combinations. Instead, users can use 3rd party tools such as https://github.com/salesforce/policy_sentry for generating a list privilege policy that meets their clusters specifications


added notes that unified audit logging must be enabled to use APIs as…

… per PM

Docs Build status updates of commit a98c63a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

office-365-management-api/get-started-with-office-365-management-apis.md
:white_check_mark:Succeeded
View

office-365-management-api/images/authorization-flow.png
:white_check_mark:Succeeded
View

office-365-management-api/office-365-management-activity-api-faq.md
:white_check_mark:Succeeded
View

office-365-management-api/office-365-management-activity-api-reference.md
:white_check_mark:Succeeded
View

office-365-management-api/office-365-service-communications-api-reference.md
:white_check_mark:Succeeded
View

office-365-management-api/troubleshooting-the-office-365-management-activity-api.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Hydra-provisioner doesn't have build cores set

build-cores = 0 Nix config is missing for EC2 provisioned machines, I don't see they include delft/common.nix. This is why chromium takes 8h to compile, in reality it should take 40-60min.

cc @edolstra


Fix #1462, add new smart agent dynamically

A small bug exists, please let me fix later.

Add a function to get smart severs in common.sh. The functionality has been tested in single-node and multiply-node situation. @littlezhou Please review again, thanks!


[docs] release 1.4.2+aws.2

Issue #, if available:
Description of changes:

adding more use-cases to troubleshooting guide
changing format to problem, cause solution
added images

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This PR needs to go in in tandem with https://github.com/aws-quickstart/quickstart-vmware-tanzu-application-platform/pull/154

@tlindsay42 , @jacnnguyen ,  please have a look! Thanks!

@davmayd , please merge in this as well.


Automatically expose cogs as globals in python eval

The Problem
Almost every time I invoke jsk py, it starts with _bot.get_cog('MyCog').  It would be nice if this was exposed as _MyCog.
The Ideal Solution
Iterate over Bot.__cogs and expose them while generating the scope
The Current Solution
Turn on Retain Variables, and manually store cogs in the global context, or manually execute the search every time you eval something.

_bot.cogs['MyCog'] is a bit quicker to type. combine that with setting jishaku retain on by default using environment variables and it's not so bad. This also gets into the sticky issue of maintaining that state whenever a cog is reloaded. Potentially that could be solved by passing a custom dictionary type to exec that falls back to looking up bot.cogs.

I don't really like having this be done by the repl context preparation because it would mean people who use JISHAKU_NO_UNDERSCORE would end up having all their cogs in scope randomly, and since I've seen a decent number of people call their cogs things like Fun and Games I can forsee scoping issues. It would actually be pretty funny to see people be bitten by this, since it would mean people would stop asking me why I prefix the underscore by default.
A potential compromise might be to just add _cogs as an automatic variable, but even that might cause scoping issues (I know many people, including myself, who put their cogs into a cogs.whatever module).
I don't really like the idea of a global fallback dictionary because it means people unfamiliar with the behavior won't know why they have magic ephemeral variables flying around. It's easy to tell that _bot.cogs['Utils'].something() won't work for you if you don't have such a cog, but _Utils.something() is more confusing at a glance.

I don't really like having this be done by the repl context preparation because it would mean people who use JISHAKU_NO_UNDERSCORE would end up having all their cogs in scope randomly, and since I've seen a decent number of people call their cogs things like Fun and Games I can forsee scoping issues. It would actually be pretty funny to see people be bitten by this, since it would mean people would stop asking me why I prefix the underscore by default.
A potential compromise might be to just add _cogs as an automatic variable, but even that might cause scoping issues (I know many people, including myself, who put their cogs into a cogs.whatever module).
I don't really like the idea of a global fallback dictionary because it means people unfamiliar with the behavior won't know why they have magic ephemeral variables flying around. It's easy to tell that _bot.cogs['Utils'].something() won't work for you if you don't have such a cog, but _Utils.something() is more confusing at a glance.

I think I'm ultimately deciding to not do this one. You can trivially use _bot.get_cog to get this behavior with not really that much brevity loss, and without the expense of having potentially conflicting or confusing automatic names in scope.


[$500] Log in - Keyboard is not consistent in safari and pressing enter does not submit a form

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to sign in page
Enter any email
Notice that keyboard in native ios app and safari web is not the same

Expected Result:
Both keyboard should be the same, or at least pressing "Go" should submit a form
Actual Result:
Keyboards are not consistent.
a) In safari instead of "Return" sign it says "Go"
b) And pressing it won't submit the form unlike the native app
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[x] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.75-8
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Safari
https://github.com/Expensify/App/assets/78819774/b7c6dc15-1322-4fe9-9b28-800664d280cb
IOS app
https://github.com/Expensify/App/assets/78819774/ed88e01a-8af7-4aed-a4c0-cb0516abc14d
https://github.com/Expensify/App/assets/78819774/2cfe7d44-a94b-4849-82ef-3c93e9b373b4
Expensify/Expensify Issue URL:
Issue reported by: @alitoshmatov
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1696083514018509
n+is%3Aissue+label%3A%22Help+Wanted%22)
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01d106743c23a6474e
Upwork Job ID:<PHONE_NUMBER>340430848
Last Price Increase: 2023-10-01

Proposal
Please re-state the problem that we are trying to solve in this issue.
Enter key press not submitting form in iOS Safari
What is the root cause of that problem?
Root cause of the problem is simply there is onKeyPress handler in
https://github.com/Expensify/App/blob/2160babec48a63cb93c660df4365bc4dc483ccb9/src/pages/signin/LoginForm/BaseLoginForm.js#L200
What changes do you think we should make in order to solve the problem?
Adding following code in above file will ensure key press will be handled on pressing enter key.
onKeyPress={({nativeEvent}) => nativeEvent.code === "Enter" && validateAndSubmitForm()}
enterKeyHint/returnKeyType will simply set text label of return button, it will not submit form unless we have keypress handler attached to the textinput over which soft keyboard is being shown.
It should work on all platforms but it still needs to be cross verified if C+ picks this proposal.
Result
https://github.com/Expensify/App/assets/767439/234acab8-81a4-4ff4-8592-de3f908b7a05
What alternative solutions did you explore? (Optional)
N/A

@Ollyws any thoughts on the proposals above?

@Ollyws yes it is fixed.

@Ollyws One note that this is not just signin page, this issue come up on https://github.com/Expensify/App/pull/28409 which  also has one input and submit was not working. I assume this happens in other places too

@alitoshmatov @Ollyws I think this can be fixed in all places if we implement onKeyPress handler in TextInput component and pass it a prop submitOnEnter which should handle submitting form. Can be generic solution.

I agree we should resolve the root cause and for all the forms.
@Ollyws could you please take a look at the above comment.

@stephanieelliott  I'm officially no longer in the BugZero team so reassigning this as it will not close until tomorrow.

Thanks for clarifying! 🙌

Summarizing payment on this issue:

Issue reporter: @alitoshmatov $50 Upwork - PAID
Contributor: @ZhenjaHorbach $500 Upwork - PAID
Contributor+: @Ollyws $500 Upwork - PAID

Upwork job is here, no bonus is included on payout


Form: Uncaught TypeError: this.element.form is not a function

Uncaught TypeError: this.element.form is not a function at https://github.com/TechnologyAdvice/stardust/blob/master/src/collections/Form/Form.js#L81.
Variable values at the moment of error:
this.element == $(this.refs.element)
this.element.form === undefined

I'm using stardust with webpack-dev-server and this issue occurs every time I use Form, including
<Form />

It looks like jQuery is not loaded.  Is your project setup according the usage in the readme?  Per the setup instructions, we still require jQuery until we are done removing it.
If you can provide project to reproduce the error after confirming the setup, I can take a look.

It looks like jQuery is not loaded.

No, shouldn't it fail with Uncaught TypeError: $ is not a function if jQuery was not loaded correctly?

Is your project setup according the usage in the readme?

Yep, I think so.
And here is my project: https://github.com/jukkah/short-url

Sorry should have been more specific, SUI jQuery is responsible for adding the form function to jQuery. The error indicates SUI JS is not loaded.
I've looked through the project,  on my mobile,  and it looks correct. I also tested the SUI script src and it loads SUI js. I was able to find "$.fn.form =" in the JS as well, so that is correct.
We use this same setup in the doc site and our production apps, including webpack dev server, so I know it works. I'll have to try this out when I'm back to my computer to further diagnose the issue.
Perhaps @davezuko could run this project and identify any obvious issues for me?

I believe that there are two different versions of jQuery being loaded, one from the index.html file, and one from the Stardust dependency (and bundled with webpack). I introspected this by looking at jQuery on the window, which looks to be correct:

However, then I took a look at the jQuery module being used within Stardust:
  refresh() {
    this.element = $(this.refs.element)
    window.stardust$ = (0, _jquery2.default)

I confirmed this by looking at the bundle output and noticed that jQuery is indeed being bundled, so it exists twice, and only one of them is being extended, obviously. A quick and dirty solution is to add this to your webpack configuration:
  externals: {
    jquery: 'jQuery',
  }

This will tell webpack to use the jQuery that you've loaded from the browser. That should get you moving for now, but we really need to tweak the install guide to account for this.

Thanks much David. I would call it a bug that we are bundling jQuery with Stardust. I think we should consider updating the build config to use an external jQuery. This will not only make our bundles much smaller, but it will also allow users to choose their own version and build of jQuery.

If so, I would add some logic to the root stardust import that throws a huge warning at the user telling them that they need to include jQuery on their own (until we remove it, of course). That way users don't boot up the app without reading through all the instructions and scratch their heads about why jQuery isn't included.
Stardust will have to be updated accordingly, if this is the case, since it relies on local jquery imports, and unless you're going to require people to also bundle semantic jquery extensions (rather than use it from a cdn), then the only sane solution is to access jQuery directly from the window. It's kind of a damned if you do damned if you don't situation, honestly; i.e., requiring jQuery to be on the window makes webpack configuration more complex for first-time users, and the inverse of requiring jQuery to be installed as an npm dependency means users must figure out how to get the semantic extensions loaded correctly.

These are all good points.  Considering:

jQuery will isn't far from removed
Semantic 2.0 only works with jQuery 2.x
Build updates / complications required to "unbundle" it

Perhaps we instead embrace bundling for a short time.  Then we only need to update the README.md.  We could technically also do a check to see if jQuery exists on the window, if so, use that one.

Actually, I think bundling jQuery with Stardust might make even more sense.  Once it is removed, there will be no refactors necessary for users, it is just that the library will no longer include jQuery.
This assumes user's are not likely to be using jQuery with React anyway.

@levithomason What about refactoring all import $ from 'jquery' to:
import $ from 'internal/jquery'

// internal/jquery.js
import jQuery from 'jquery'

export default window.$ || jQuery

Exactly what I'm thinking, except window.jQuery to be safe.

👍

While you're at it, there's probably a test you could do to verify that semantic jquery was loaded, and, if not, throw the user a nice error. This all just being for usability pre-jQuery-removal-enlightenment.

Aye.  I'm thinking since we also need a specific version of SUI jQuery, we bundle it the same way as jQuery.  Including the conditional check to see if it was already loaded.  We can check for the SUI plugins we need on jQuery.

Hi guys, I am having the excatly same problem with Progress component, I am getting
Progress.js:83Uncaught TypeError: this.element.progress is not a function
None of the solutions that you have provided works for me ( apart from manually adding jquery and semantic.js via script tag in index.html)
Here is my webpack config:
var path = require('path');
var webpack = require('webpack');

module.exports = {
  devtool: 'source-map',
  entry: [
    'webpack-dev-server/client?http://localhost:1337/',
    'webpack/hot/only-dev-server',
    './src/js/app'
  ],
  output: {
    path: path.join(__dirname, 'dist'),
    filename: 'app.js',
    publicPath: '/dist/'
  },
  module: {
    loaders: [{
      test: /\.js$/,
      loaders: ['react-hot', 'babel'],
      include: path.join(__dirname, './src/js'),
      exclude: /node_modules/
    },
    { test: /\.less$/, exclude: /node_modules/, loader: "style-loader!css-loader!autoprefixer-loader!less-loader"},
    { test: /\.css$/,  loader: 'style-loader!css-loader!autoprefixer-loader'},
    {test: /\.jpe?g$|\.gif$|\.png$|\.ico$/, loader: 'url-loader?limit=100000'},
    {test: /\.eot|\.ttf|\.svg|\.woff2?/, loader: 'url-loader'}
    ]
  },
  plugins: [
      new webpack.optimize.OccurenceOrderPlugin(),
      new webpack.HotModuleReplacementPlugin(),
      new webpack.NoErrorsPlugin(),
      new webpack.DefinePlugin({
          'process.env': {
              NODE_ENV: JSON.stringify('development'),
              APP_ENV: JSON.stringify('browser')
          }
      })
  ],
  externals: {
    jquery: 'jQuery',
  }
};

Am i shimming/exposing jQuery good ? Any other possible fixes for that ?

@padsbanger I'm currently working on this against the example repo provided by @jukkah above.  Hope to have a fix up here soon.

@jukkah @padsbanger I've released 0.19.0 which solves the jQuery issues.  I submitted [PR #1](https://github.com/jukkah/short-url/pull/1 to @jukkah's project so you can see what a working project should look like.
In short, do not include jQuery nor Semantic UI JS on the page.  Also, do not include any config for these in your Webpack config.  It is all handled by Stardust now.
If you do have jQuery on the page, you'll notice Stardust will tell you to remove it:

If you turn on debugging for jQuery localStorage.debug = 'stardust:jquery' you can see when and what Stardust is loading:

Let me know if you have any other issues.

Thank you Sir, it works perferctly !

Awesome!  Very glad for that 😸 I'm working on the jQuery free progress right now.  Should have that done toady as well.


Roll Flutter Engine from ee65be7d8fb1 to 1fee026dc683 (2 revisions)

https://github.com/flutter/engine/compare/ee65be7d8fb1...1fee026dc683
2023-05-04<EMAIL_ADDRESS>[Impeller] Remove the DrawPaint->Clear optimization (flutter/engine#41711)
2023-05-03<EMAIL_ADDRESS>Roll Dart SDK from 3cfcfb24bc6a to 59787216f670 (2 revisions) (flutter/engine#41718)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jimgraham@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


feature: attestation checkboxes

Summary | Résumé
Closes #676
This adds a new option to the validation section in the JSON configuration. If the all boolean is set to true, it will require that all checkboxes in an element are selected.

Before
After

Test instructions | Instructions pour tester la modification

In the Github deployment, load form: https://forms-staging.cdssandbox.xyz/en/id/309
Test checking various combinations of selected checkboxes: all, none, some. Only when all checkboxes are selected should be the form be submitted.

Pull Request Checklist
Please complete the following items in the checklist before you request a review:

[x] Have you completely tested the functionality of change introduced in this PR? Is the PR solving the problem it's meant to solve within the scope of the related issue?
[x] The PR does not introduce any new issues such as failed tests, console warnings or new bugs.
[ ] If this PR adds a package have you ensured its licensed correctly and does not add additional security issues?
[x] Is the code clean, readable and maintainable? Is it easy to understand and comprehend.
[ ] Does your code have adequate comprehensible comments? Do new functions have docstrings?
[ ] Have you modified the change log and updated any relevant documentation?
[x] Is there adequate test coverage? Both unit tests and end-to-end tests where applicable?
[x] If your PR is touching any UI is it accessible? Have you tested it with a screen reader? Have you tested it with automated testing tools such as axe?

It looks good to me if we want to do it this way but I have this weird feeling that this solution is kind of a hacky one. I think it would have been a good use case for a new component dedicated to attestation.

At first I thought we'd need a new component. After talking with @srtalbot and @connorscarolyns about the requirements, this solution presented itself as the easiest to implement, meeting all the requirements without overly complicating the code. I am quite pleased with its simplicity.


heatmap color change

Hi,
My data condition have three levels, how can I change the annotation bar color ?

hi @wu1997-shu,
just so i'm clear, which function are you calling here for the heatmaps?

There is a workaround for exactly this here:
https://github.com/HelenaLC/CATALYST/issues/244


gl size mismatch

if there is a size mismatch between the window size and the image size, then we get a cryptic error. maybe should have rescaling also as option?
raise CudaException("Unable to copy from tensor to texture")
CudaException: Unable to copy from tensor to texture

resolved. now if size mismatch is detected, fast GPU interpolation is used to resized input to defined canvas size


Case convert

In this I have made a function named screaming snake case which takes the input as String and then convert the case in upper with underscore which is screaming snake case  #64

File changes are not correct.

Can you explain me what changes are required in file, because I have the function in case_convert file and then do the work


build: remove dist/

Previously the dist/ contained archives built for either platform, that
were then included by other targets to be used in the example apps. This
had the benefit of demonstrating how the targets could be used in a
bazel setup. The downside with this approach is that it was required to
be non-hermetic, and made builds a 2 step process that you had to go
through if you wanted to test framework changes. This is now removed and
replaced with a more standard bazel setup where the example targets
reference other targets in the build, removing the need for 2 steps.
This also eliminates issues caused by manually editing the files in the
dist/ directory, which bazel wouldn't pick up since it was non-hermetic.
For android this is a no-op because we still continue to include the aar
directly, for iOS this isn't currently possible because the
apple_static_framework_import rule requires a list of files, which
isn't possible to compute from the zip file produced by the
ios_static_framework rule that is only meant for distribution. Instead
the examples now depend on the swift_library directly, which is
slightly different, but shouldn't be different enough to cause
significant issues.
Signed-off-by: Keith Smiley<EMAIL_ADDRESS>

The other piece to this, that is perhaps even more significant, is that having the test apps depend on the distributable packages allows us to actually test the viability of the packages in CI. We'd miss that coverage if we switched exclusively to internal bazel targets for tests.

I still feel that having the example apps rely on internal targets makes them less generally helpful for the average potential user, since we're no longer demonstrating how the distributable packages can be used.
Arguably, we could set up the examples as even more traditional Android and iOS projects that don't rely on Bazel at all, as most folks are likely not using Bazel to build their app.

This is exactly the point I was going to make, we can and should have validation on CI for all our supported installation methods, I'm happy to spend time setting up that infra. Keeping the bazel parts hermetic is a big win.

I pushed an update which allows us to import the framework directly just as before with the help of a small rule. This should negate any concerns about this behavior being different than dist/ before

Thanks @keith, your update definitely helps to allay my concern about the CI coverage aspect.
Out of curiosity, if we were to move in the direction of setting up example apps specifically as more traditional Xcode/Android Studio projects (i.e. without Bazel, necessarily), do you have any ideas for what that might look like with this setup?

Out of curiosity, if we were to move in the direction of setting up example apps specifically as more traditional Xcode/Android Studio projects (i.e. without Bazel, necessarily), do you have any ideas for what that might look like with this setup?

A vanilla Xcode project could refer to the .framework directly in bazel-bin/. I imagine the equivalent on Android would be similar, where the Android Studio project configuration could point to the .aar in bazel-bin/ too.

This reorganizes the Android/iOS example apps CI jobs from being an initial step to build Envoy Mobile, uploading the release artifact as a GitHub Actions artifact, the spawning multiple jobs for each example app that downloads the built Envoy Mobile. The new format builds and runs all example apps in parallel, which will shorten overall CI time, but won't benefit from reusing a single cached built artifact, but with bazel's reproducibility and caching features, this shouldn't really be a problem.

This was actually substantial performance improvement O(hours) to CI at least prior to having RBE. The app tests are somewhat more prone to flakiness due to network faults and the like, and previously having to rebuild the entire library to rerun them was extremely painful. Do we have RBE caching effectively across runs?

We should invest in a validation suite that integrates Envoy Mobile in all our supported installation methods the same way a user would integrate it. The framework_imports_extractor is an impressive trick to get close to that on the iOS front, but does not really reflect how our users would integrate the framework in Xcode without bazel, and doesn't validate our other supported installation methods.

This was the essence of my question above - I feel the example apps are if anything moving away from being representative of an "example" of how to use Envoy Mobile from an average user's perspective. To your response @jpsim, are the .framework and .aar output to stable directories inside bazel-bin?

This was actually substantial performance improvement O(hours) to CI at least prior to having RBE. The app tests are somewhat more prone to flakiness due to network faults and the like, and previously having to rebuild the entire library to rerun them was extremely painful. Do we have RBE caching effectively across runs?

Yes, the RBE cache should be pretty effective, and in fact probably even more now that we've removed the non-cached, non-hermetic artifacts in dist/. I also have seen that uploading and downloading built artifacts from GitHub Actions was pretty slow. We may get a speed up from the bazel cache and executors all being in EngFlow's network.
As a point of comparison, android_build took 6 minutes and java_helloworld took 8 minutes in this PR, compared to 9 minutes + 12 minutes in #2261, so from commit to job complete, java_helloworld took 8 minutes in this PR vs 21 minutes in #2261.

This was the essence of my question above - I feel the example apps are if anything moving away from being representative of an "example" of how to use Envoy Mobile from an average user's perspective. To your response @jpsim, are the .framework and .aar output to stable directories inside bazel-bin?

Yes, the .framework and .aar artifacts are output to stable locations with this PR, they just happen to be in bazel-bin/ instead of dist/. My point was actually that neither what we were doing before, nor with this PR, do we have a representative setup of how most users will integrate Envoy Mobile, and that it would be worth us investing in a validation suite that confirms that all our supported installation methods work: bazel, .framework/.aar, Maven, CocoaPods & SwiftPM. On main today and with this PR, we have a mixed bazel/binary validation that in practice none of our users are likely to have.

have code at the ready that could be run on top of the real distributable artifact

With this change, the app code still runs on top of the real distributable artifact, but what you shared offline is something slightly different, and still valuable, which is the ability to more easily build the framework and the app with different build settings. As it stands now, with building the app also building the framework, those build settings propagate unless you go add explicit setting overrides to where the targets are defined.
I think the building an installation method validation suite I've suggested here would achieve that.


build: bump angular

@angular-eslint/schematics  18.1.0 -> 18.2.0
@angular/cdk                        18.1.2 -> 18.1.3
@angular/cli                          18.1.2 -> 18.1.3
@angular/core                       18.1.2 -> 18.1.3
PR Checklist

[ ] Unit Tests have been added for new changes
[ ] API tests have been updated if applicable
[ ] All commented code has been removed
[ ] If you've added a dependency, you've ensured license is compatible with Apache 2.0 and clearly outlined the added dependency.

What are you changing?

Anything the reviewer should know when reviewing this PR?
If the there are associated PRs in other repositories, please link them here (i.e. open-amt-cloud-toolkit/repo#365 )

:tada: This PR is included in version 8.0.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Provide information about boot-time performance.

Motivation
We've gotten slow, apparently.  Why?
Modifications
Add instrumentation, printed after boot, to tell us where we are spending
our time.
Result
More log output!

[X] Have you followed the guidelines in our Contributing document?
[ ] Have you created a JIRA and used it in the commit message?
[X] Have you checked to ensure there aren't other open Pull Requests for the same issue?
[X] Have you built the project locally prior to submission with mvn clean install?

retest this please

Retest this please

retest this please


Update _custom.scss imports in other builds

Correctly places the _custom.scss file first in the other two buids.
Also removes the clearfix mixin from the grid build because flexbox yo.

Fixes #21682.

/cc @Quy who commented on my commit but I forgot about it until now because commit comments 😅

I also commented here too: https://github.com/twbs/bootstrap/pull/21603#issuecomment-271488213 but it looks like it went unnoticed. I was going to do a pull request and I totally forgot about it.


Connection to wss:// not working in nodejs

It seems, that I can't pass rejectUnauthorized : false option for using self-signed certificate
https://github.com/tavendo/AutobahnJS/blob/master/package/lib/transport/websocket.js#L80-L82

this is a nodejs specific option not avail in browsers


Corrected source URLs

1.x docs should be referring to the mdl-1.x branch, not the master branch.

LGTM, thanks.


HaveIBeenPwned Module

What type of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Refactor
[ ] Documentation
[ ] Not Sure?

Does this PR introduce breaking changes?

[ ] Yes
[x] No

List any relevant issue numbers:
#69
Description:
This adds the HaveIBeenPwned module to the Checker package.
cc: @louistiti I used Google Translate to translate English expressions/answers to French, I am not sure of the accuracy of the translation so I'd appreciate your help in helping to look that over.

Hello @iifeoluwa,
Thanks for this PR and this cool new module! 😎
Let me come back to you once the 1.0.0-beta.2 is released (which means in the coming days).

Great! I'm currently looking through the roadmap for other stuff I can help out with. If you have any suggestions, please let me know.

Hello @iifeoluwa,
Thanks for your work! :tada:
I've made a few changes to allow us to have several data breaches in one output.

 ✨ Checker Package - Have I Been Pwned Module


I/flutter (20472): #139    StatefulElement.performRebuild (package:flutter/src/widgets/framework.dart:4684:11)
I/flutter (20472): #140    Element.rebuild (package:flutter/src/widgets/framework.dart:4227:5)
I/flutter (20472): #141    StatefulElement.update (package:flutter/src/widgets/framework.dart:4716:5)
I/flutter (20472): #142    Element.updateChild (package:flutter/src/widgets/framework.dart:3210:15)
I/flutter (20472): #143    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4536:16)
I/flutter (20472): #144    StatefulElement.performRebuild (package:flutter/src/widgets/framework.dart:4684:11)
I/flutter (20472): #145    Element.rebuild (package:flutter/src/widgets/framework.dart:4227:5)
I/flutter (20472): #146    StatefulElement.update (package:flutter/src/widgets/framework.dart:4716:5)
I/flutter (20472): #147    Element.updateChild (package:flutter/src/widgets/framework.dart:3210:15)
I/flutter (20472): #148    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4536:16)
I/flutter (20472): #149    StatefulElement.performRebuild (package:flutter/src/widgets/framework.dart:4684:11)
I/flutter (20472): #150    Element.rebuild (package:flutter/src/widgets/framework.dart:4227:5)
I/flutter (20472): #151    BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2632:33)
I/flutter (20472): #152    WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:864:20)
I/flutter (20472): #153    RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:284:5)
I/flutter (20472): #154    SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1113:15)
I/flutter (20472): #155    SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1052:9)
I/flutter (20472): #156    SchedulerBinding.scheduleWarmUpFrame. (package:flutter/src/scheduler/binding.dart:861:7)
I/flutter (20472): (elided 6 frames from class _AssertionError, class _RawReceivePortImpl, class _Timer, and dart:async-patch)
I/flutter (20472):
I/flutter (20472): ════════════════════════════════════════════════════════════════════════════════════════════════════

Hi @aarifali,
When opening an issue, please try to provide all or some of the information indicated in the template.

Issue Template
If you are looking for support, please check out our documentation
or consider asking a question on Stack Overflow:
- https://flutter.dev/
- https://api.flutter.dev/
- https://stackoverflow.com/questions/tagged/flutter?sort=frequent

If you have found a bug or if our documentation doesn't have an answer
to what you're looking for, then fill our the template below. Please read
our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports

Steps to Reproduce

Please tell us exactly how to reproduce the problem you are running into.

Please attach a small application (ideally just one main.dart file) that
reproduces the problem. You could use https://gist.github.com/ for this.

If the problem is with your application's rendering, then please attach
a screenshot and explain what the problem is.

1. ...
2. ...
3. ...

Please tell us which target platform(s) the problem occurs (Android / iOS / Web / macOS / Linux / Windows)
Which target OS version, for Web, browser, is the test system running?
Does the problem occur on emulator/simulator as well as on physical devices?

Target Platform:
Target OS version/browser:
Devices:

Run your application with `flutter run --verbose` and attach all the
log output below between the lines with the backticks. If there is an
exception, please see if the error message includes enough information
to explain how to solve the issue.

Run `flutter analyze` and attach any output of that command below.
If there are any analysis errors, try resolving them before filing this issue.

Finally, paste the output of running `flutter doctor -v` here.

Closing this issue, since no information has been provided.
Thank you.


.File.BaseFileName on zero object. Wrap it in if or with: {{ with .File }}{{ .BaseFileName }}{{ end }}

dear team,
i am using your awesome docport theme - or at least i am trying :)

i am using the latest build of the docport theme available for download here

i am also using the latest available hugo version which is:

hugo v0.111.3-5d4eb5154e1fed125ca8e9b5a0315c4180dab192+extended windows/amd64 BuildDate=2023-03-12T11:40:50Z VendorInfo=gohugoio

this issue happens only when using the docport theme - at least i get site builds with other themes

when i run the site build - it terminates with this warning and the output folder stays empty
C:\hugo\sites\quickstart [master +3 ~0 -0 | +7 ~0 -1 !]> hugo
Start building sites …
hugo v0.111.3-5d4eb5154e1fed125ca8e9b5a0315c4180dab192+extended windows/amd64 BuildDate=2023-03-12T11:40:50Z VendorInfo=gohugoio
WARN 2023/03/20 13:43:28 .File.BaseFileName on zero object. Wrap it in if or with: {{ with .File }}{{ .BaseFileName }}{{ end }}
               | EN

-------------------+-----
Pages            | 20
Paginator pages  |  0
Non-page files   |  3
Static files     | 15
Processed images |  0
Aliases          |  0
Sitemaps         |  1
Cleaned          |  0
even though the pages and static files seem to be build; they stay empty
the config file i am using looks like this
baseURL = "http://example.org/"
languageCode = "en-us"
title = "MyTitle"
theme = "hugo-theme-docport-master"

DefaultContentLanguage = "en"
pygmentsCodeFences = true
pygmentsStyle = "monokai"

defaultContentLanguageInSubdir= false
enableMissingTranslationPlaceholders = false

# googleanalytics = "UA-123-45"

disableKinds = ["taxonomy", "taxonomyTerm", "category", "RSS"]

# Keep this as is
[outputs]
home = [ "HTML", "RSS", "JSON"]

# Site params
[params]
ordersectionsby = "weight" # ordersectionsby = "title"
disableNavChevron = false # set true to hide next/prev chevron, default is false
menushortcutsnewtab = false # set true to open shortcuts links to a new tab/window

#editURL = "https://github.com/vjeantet/hugo-theme-docport/edit/master/exampleSite/content/"
enableGitInfo = true
color_main = "#ff0000"
color_second = "black"
disableSearch = true

[mediaTypes]
  [mediaTypes."application/netlifyconfig"]
    suffixes = ["yml"]

[outputFormats]
[outputFormats.netlifyyaml]
mediaType = "application/netlifyconfig"
isPlainText = true
isHTML = false
notAlternative = true

[markup.goldmark.renderer]
unsafe = false #was true

# Code highlight configuration
[markup.highlight]
codeFences = true
guessSyntax = true
hl_Lines = ""
lineNoStart = 1
lineNos = false
lineNumbersInTable = true
noClasses = true
style = "monokai"
tabWidth = 2

is there anything i have overlooked? i am fairly new to hugo itself, but have basic/intermediate experience with site generators and feel confident, that what i am trying to do is not completely non sense :)
the content of the
please let me know if there are any missing information
cheers and best regards
marc

sorry - i may was a bit fast here - the issue occurs with other themes too. closing this one and try to get my grib around things :)


Code completion removed by improved minification

My IDE does no longer offer code completion for the HTTP status code identifiers, only getStatusText() is suggested. For example:
HttpStatus = require('http-status-codes');

response.status(HttpStatus.    <== code completion only showing 'getStatusText()'

This makes me sad, as I have to look up the code identifiers again and have to type more (without typos). No doubt is the 'improve minification' commit an improvement, however it's also a regression.
My preference is code completion over minification but perhaps there is a win-win?

Hey rhmeeuwisse. Sorry for the delay. I understand the frustration here. Can I ask which IDE you are using ? Is this still happening.

Hah! Thanks for asking me to check again, code completion is working properly now.
I'm using WebStorm 10.0.4 now which has "reworked support for JavaScript from the ground up". When I opened this issue I was on the then current WebStorm 9.
Thanks for your time.

Good to hear it. Thanks for taking time to check, and sorry again for the delay.


Prometheus read integration

URL for relevant page?
https://docs.influxdata.com/influxdb/v1.8/supported_protocols/prometheus
What products and version are you using?
InfluxDB version: 1.7.10
Where did you look before opening the issue?
https://github.com/prometheus/prometheus/issues/4739
Please update the page with latest information as per the below link
https://github.com/prometheus/prometheus/issues/4739#issuecomment-621242152

setting read_recent is part of the Promethues config file, not InfluxDB config file

Hi did you solve it?


Adding multiple tabs simultaneously doesn't work for lots of tabs

Bad Request Request Line is too large (7383 > 4094)

Fixed with #19.


Rename length to size and length_mvt to size_mvt

Summary
The title says it all. This PR replaces length() with size() and length() with size_mvt().
It also remove the mat/fun/size.hpp that returned size only for std::vector<T>.
Tests
/
Side Effects
/
Checklist

[x] Math issue Closes #1512

[x] Copyright holder: Rok Češnovar

[x] the basic tests are passing

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

@rok-cesnovar, don't know if you saw, but this has merge conflicts.

I saw the error from Jenkins but not the merge conflicts. Thanks!
This is probably from the PRs merged earlier. Will get to this soon.

This is not ready yet, because I have to clear up some variables named size, that are causing issues:
size_t size = max_size(n, alpha, beta);

for (size_t i = 0; i < size(n); i++) {

Thank again for reviewing these PRs that touch a bunch of files. I think I addressed everything.

So is it intentional to leave size_mvt in namespace stan rather than stan::math?

Ah no, I misunderstood, fixed now.

This seems ready to go! Hooray!

Thanks!  This has been bugging me for ages!


Question: what ways can I detect whether a user has enabled tracing?

Hi folks! I was wondering if there are ways to detect at runtime whether tracing is enabled / configured. our only dependency is on @opentelemetry/api
I can think of a few ways:

create a span and check if it's recording
create a span and check if spanContext is valid

But I was wondering if there's an api for checking whether a global tracer provider has been configured by the user at runtime without creating a span?
Context here is we'd like some way to short-circuit tracing operations unless the customer has enabled tracing. I know the API does a great job at providing no-op implementations if nothing is configured but we have our own logic that we'd love to bypass.
Any other options here?
Thanks!

I'm not aware of a dedicated API. As you indicated there are several ways to do this by looking at created objects. Looking at a span has the risk that sampler my decide to not sample your test span.
In general caching the info if an SDK is present or not is some sort of risky as an SDK may be installed later.

Thank you @Flarna - I appreciate the insight.

Looking at a span has the risk that sampler my decide to not sample your test span.

This is really useful information - thank you! So checking if a given span is recording is not a reliable proxy for "tracing is enabled" as that can be different on a span-by-span basis depending on the sampling settings, correct?
If so, just curious, does that also happen within nested spans? Or if the root span is sampled all its children will be as well? Where can I read more about this?

In general caching the info if an SDK is present or not is some sort of risky as an SDK may be installed later.

I was thinking more like asking the API if SDK is currently present / tracing has been enabled, rather than relying on created spans. In general I think this would be a useful feature in the API - to know whether tracing has been enabled globally - would you consider it?

can be different on a span-by-span basis depending on the sampling settings, correct?

Yes

If so, just curious, does that also happen within nested spans?

This may happen also within nested spans. It depends on the actual sampler used. Some use a fresh random on each span others use a random only for the root span and childs use the decision of the parent.

I was thinking more like asking the API if SDK is currently present / tracing has been enabled, rather than relying on created spans. In general I think this would be a useful feature in the API - to know whether tracing has been enabled globally - would you consider it?

I'm not sure if this is really a good choice. OTel is intended for production use. Therefore application should behave equal independent of OTel present/not presetn or OTEL enabled/disabled.
I think the main focus should be that OTel without SDK adds that less overhead that it is simply don't care to call the APIs.


Adjust layer scale and offset using screen size instead

Hello,
I am honestly not sure if this is the right approach, as I am a bit new around here. But, this solves a problem where editing image states across different screen size/devices would not properly adjust layer scale and position.
This also alters the data structure of import of export, so checking whether the default values are sane is also appreciated. So far I have used a Size.zero absence of this field in previous JSON files for retro-compatibility. The recalculate function takes care of this case so it works fine (in my testing) with older versions.
However: The proper calculation will only work in newly exported images, since we didn't have the original aspect ratio of the image state in the past.
Note 2: It is not 100% accurate, but it does a much better job imho. Not sure if any calculations could be better done?
Before (problem)

After (solution)

Not working as expected in various scenarios. Pulling back.


Allow resource types to be changed per work types

Still need to write tests for HykuAddons::QaSelectService, but it is working.

Ugh, I don't know why these tests are failing now.  I don't think they're related to this PR.

Ugh, I don't know why these tests are failing now.  I don't think they're related to this PR.


Fix neuro cli version

Ideally, we want to auto-update the pinned version number and publish a new image on every neuromation release.
The publishing requires manual steps (bumping the version number at least) but the dependency checker can make a PR automatically as Dependabot does.
@romasku already implemented something similar for platform-pipelines.
You can borrow the idea from here: https://github.com/neuro-inc/platform-pipelines/blob/master/.github/workflows/update-images.yml


Standardized aka.ms links for tsc and tsconfig

Fixes #46919

@gabritto please forgive me, I went back (again) on aka.ms/tsconfig vs aka.ms/tsconfig.json ... The extra .json in there just seemed unnecessary. I can change it back to aka.ms/tsconfig.json if you'd prefer (but personally like aka.ms/tsconfig just a bit more). 😅


Strange/Glitchy navigation animations in Release 1.5.8

Firstly, thanks for an amazingly detailed library! I am currently using it in my published app for the introduction setup.
Right now, my latest published app uses Release 1.5.5 of your library. This version seems to do fine with regard to the page navigation and the corresponding animations. Firstly, some context on my usage of your library: I have used multiple "SimpleSlide"s for my setup process. Some of these slides need to disable "CanGoForward" as the user is forced to click on the Cta button. The button issues an Intent that launches another app's activity and upon return to my app, in the onActivityResult, I retrieve the particular SimpleSlide, and replace it with an identical slide where "CanGoForward" is set to true. I haven't figured out a way to change a SimpleSlide's "CanGoForward" data member, so I had to replace it with a new Slide object. Then the user can press the forward button and continue.

This setup worked fine with the library version 1.5.5. See the following 30 second video for the corresponding workflow and the transitions of the slides: https://www.dropbox.com/s/05sfzz9fckx832j/Fit Notifications with Lib v1.5.5.mp4?dl=0
But then, with library version 1.5.8, the transitions are very buggy after I replace the slide in the onActivityResult in my setup activity. See the glitchy animations starting from time 00:12 in video: https://www.dropbox.com/s/s9v8d3424azs3m7/Fit Notifications Debug with Lib v1.5.8.mp4?dl=0

Starting from 12th second, upon returning from the other app's activity + replacing slide with another that allows forward navigation, this is what happens: When I navigate forward by pressing the forward arrow, rather than a smooth transition, I see a sudden jump to the next Slide. Scrolling seems fine. However, on the next Slide, where "CanGoForward" is false again, scrolling causes the Slide's content to vanish (at 00:18 in 2nd video). Pressing the forward arrow disallows navigation as expected though. Pressing the back arrow causes some strange navigation animations that I can't quite explain.
Could you please look into this as I cannot currently use the latest version due to this strange animation issues?

This is fixed in the latest snapshot, as I fixed it in commit 2bb3fc3. If you want to use the latest version, replace the dependency with this:
com.heinrichreimersoftware:material-intro:c68005f. That will use the latest commit, but will not change if something else or a new bug is added to the library.

Thanks @daniel-stone for pointing that out. I think I should release a quick bug fix release soon.

Thanks @daniel-stoneuk and @HeinrichReimer for quickly resolving this issue!

@abhijitvalluri could you make another screen recording preferably with a higher frame rate so that we can see the glitch?

Ah right, sorry for assuming it was fixed. I was having similar issues and that fixed it.

Can you not just get the slide at an index and then call a public method  (after checking instance of) to change the canGoForward variable?

Yep, @daniel-stoneuk is right about that. If you want to change canGoForward FragmentSlide and SlideFragment are your friends. Check out how I implemented the LoginSlide in the sample. It checks wether the user logged in and notifies the IntroActivity that it's canGoForward has changed.
If you don't want to use a FragmentSlide because you only need the default slide style, check out NavigationPolicy. You could store a boolean variable in your shared preferences when someone clicks the CTA button and then call lockSwipeIfNeeded() on your IntroActivity to notify the intro that your canGoForward has changed.

@daniel-stoneuk you can't modify a SimpleSlide.

Ah yup, I was thinking of FragmentSlide

@daniel-stoneuk nor can you modify a FragmentSlide ;-)

You can only modify the Fragment if you used FragmentSlide.Builder.fragment(Fragment fragment).

The behavior with the latest commit was exactly the same as the one with
Release 1.5.8 shown above. However, I have identified the cause of the
problem. I have been using a SimpleSlide and in some cases I decided to set
canGoForward to false, because the user of my app has to interact with the
slide, such as click the CTA button to launch an external app for setup
purposes. When the user finishes the interaction on the slide, I had to
create a new SimpleSlide with canGoForward set to true, because there is no
public method to set its value after building the slide. Only option was to
replace the slide. However, when I use the setSlide() method, it calls
notifyDataSetChanged() which then calls scrollTo(0,0). This sets the data
members mScrollX and mScrollY of the ViewPager to (0,0) as well. This is
the root of the problem.
From here on out, the logic in updatePosition() in
SwipeBlockableViewPager.java goes out the window because the current
slide's mScrollX is no longer currentItem*getWidth() but instead it is 0!
So when that method is called it uses the incorrect and outdated value for
x, i.e. the first parameter, and so I see all that crazy scrolling.
I think there is no way to reliably fix this unless you make sure that
users don't use setSlide() in the middle or may be save the edit to
mScrollX caused by notifyDataSetChanged() in setSlide(). Also, I could have
avoided using setSlide() if there was a public method to set canGoForward
and canGoBackward.
I currently fixed my glitch by using FragmentSlide's instead of the
SimpleSlide and avoiding setSlide(). This made my intro nicer anyway!
Thanks for looking into this!
On Sep 12, 2016 8:10 AM, "Daniel Stone"<EMAIL_ADDRESS>wrote:

Ah right, sorry for assuming it was fixed. I was having similar issues
and that fixed it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@abhijitvalluri nice catch. I'll check out this issue with notifyDataSetChanged() next weekend. Have you tried the method I described by using a NavigationPolicy?

@HeinrichReimer I did not use NavigationPolicy, but I extended SlideFragment and overrode the canGoForward and canGoBackward methods and defined my own methods to set them as well. And then, I used FragmentSlide.Builder.fragment(Fragment fragment) with my custom SlideFragment.

Yep, that should work

@HeinrichReimer That's what I meant... Of course 😂😂


connect screen - 'recent channels' need to be indicated (label)

see furthest left here

updated styles for connect:
opening first time: http://zpl.io/bllpY4G
opening with recent channels: http://zpl.io/adx7Jyl
searching: http://zpl.io/29qZ0dp
searching with some channels selected: http://zpl.io/bo1xXAm
long copy in search bar: http://zpl.io/2vMYZDj
some selections with a new private channel added: http://zpl.io/2EmA088


Cb/listen server server only

Fixes https://github.com/cBournhonesque/lightyear/issues/211

Codecov Report
Attention: Patch coverage is 34.90566% with 69 lines in your changes are missing coverage. Please review.

Project coverage is 61.31%. Comparing base (7134b29) to head (8875dbd).

Files
Patch %
Lines

lightyear/src/connection/local/client.rs
0.00%
20 Missing :warning:

lightyear/src/server/replication.rs
6.25%
15 Missing :warning:

lightyear/src/client/networking.rs
12.50%
14 Missing :warning:

lightyear/src/client/input.rs
66.66%
8 Missing :warning:

lightyear/src/shared/config.rs
20.00%
4 Missing :warning:

lightyear/src/connection/client.rs
0.00%
3 Missing :warning:

lightyear/src/client/plugin.rs
80.00%
2 Missing :warning:

lightyear/src/client/connection.rs
0.00%
1 Missing :warning:

lightyear/src/connection/id.rs
0.00%
1 Missing :warning:

lightyear/src/server/config.rs
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #212      +/-   ##
==========================================
- Coverage   61.92%   61.31%   -0.62%
==========================================
  Files         141      142       +1
  Lines        8911     8964      +53
==========================================
- Hits         5518     5496      -22
- Misses       3393     3468      +75

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Thinkpad trackpoint config optimization (plus possible bug?)

I don't have a lot of experience with trackpoints, but coming from a mac I couldn't get the touchpad into a shape where I felt comfortable so I turned it off and rely on the trackpoint entirely.
Optimal configuration
(1) is there a consensus that the default trackpoint config is good? In https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/tasks/trackpoint.nix I can see that the default sensitivity is 128 and the default speed is 97. The Lenovo configs in this repo don't configure that.
I found that my finger started to hurt and the trackpoint seems to require a lot of pressure. I'm running libinput 1.9.4. Lots of users online say that the Linux Thinkpad trackpoints are not ideal - see a bunch of threads https://www.reddit.com/r/thinkpad/search?q=trackpoint+linux&restrict_sr=on&include_over_18=on
I bumped mine to 255 for speed and sensitivity in hardware-configuration.nix - but it didn't seem to be noticeable. cat /sys/devices/platform/i8042/serio1/serio2/{speed,sensitivity} showed the same values even after reboot. echo 255 | sudo tee /sys/devices/platform/i8042/serio1/serio2/speed" from the same thread clearly increased the speed, but did not persist on reboot. Is anyone else seeing this bug, or is it user error? I confirmed that the proper value was set with nixos-option hardware.trackpoint.speed.
In a thread from last week https://www.reddit.com/r/thinkpad/comments/8ea9eh/how_to_make_touchpad_and_trackpoint_work_nicely/ people suggest libinput 1.10.0 so I added the unstable nixos channel and just tried it (using nixos-rebuild test). Don't notice much different so far.
Other problems - hardware, worn out rubber, skill, expectations
Aside from configuration, I imagine that thinkpads have varying trackpoint hardware? Possibly different ideal sensitivities apply.
I'm hoping that I'll just get better with a trackpoint over time and it will be less painful.
I'm using a slightly worn trackpoint so I have fresh ones on the way https://www.amazon.com/gp/product/B072PQ7NT3/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1
Anyone out there super-happy with their trackpoints speed / sensitivity?
Other workarounds: I end up relying even more heavily on vimium in chromium and vim mode in editors since scrolling is so painful.

I have a shell script that does echo "240" > /sys/bus/serio/devices/serio2/sensitivity, but it seems I need to rerun it most of the time after I unsuspend. I have no idea how to set that up declaratively.

Incidentally, replacement caps can be gotten much cheaper on eg. AliExpress if you're willing to wait a few weeks for them; for example, see this listing.

fyi, the libinput trackpoint code is being actively worked on - recent bug filed at https://bugs.freedesktop.org/show_bug.cgi?id=106448 against 1.10.6
I'm currently on nixos-unstable and doing a rebuild on 1.10.5, but it's taking a long time..
noticed that some trackpoint configurations got added for 440s and 450s but no 460s (https://github.com/wayland-project/libinput/blob/93dfd0fa548e4daf43f06c5a04c35bc3fcf8b1be/udev/90-libinput-model-quirks.hwdb) - not sure why. will be continuing to investigate...

Seems like echo 255 | sudo tee /sys/devices/platform/i8042/serio1/serio2/speed isn't working for libinput 1.10.5

sudo vi /sys/devices/platform/i8042/serio1/serio2/speed


Signature of pyvs_transcript.py get_pyhgvs_data inconsistant

def get_pyhgvs_data(self, transcript_id, genome_build, sacgf_pyhgvs_fork=False)
    if build_coords is None:
        return {}, False
     ....
     pyhgvs_data["exons"] = exons
        return pyhgvs_data

So in the error case it returns a Tuple of an empty dict and False.
In the success case it returns a Dict (not as part of a Tuple with True).
Maybe an Exception is better use case if the genome_build is missing?
Would also be useful to declare the dictionary that gets returned, e.g. as a starting point
class PyhgvsDataDict(TypedDict, total=False):
    id: Any
    chrom: Any
    start: Any
    end: Any
    strand: Any
    cds_start: Any
    cds_end: Any
    gene_name: Any
    cdna_match: Any
    start_codon_transcript_pos: Any
    stop_codon_transcript_pos: Any
    other_chroms: Any
    exons: Any

Would have made a PR myself but not sure how you want to handle the current Tuple vs Dict response value.

I have no idea what was going on there, everything that calls it just expects a dict, fixed to always return dict