Dockerfile no longer builds - AttributeError: cython_sources

I started getting the error below in my pipeline 9 days ago which is also the day Python 3.12 was released.  Bumping PyYAML to 6.0.1 in setup.cfg seems to resolve the issue.
Digest: sha256:5624c7648b31ecd8b03eef4b0805f3ecd8b9703a7caf2480c0d3beb2a09968b4
Status: Downloaded newer image for python:3
 ---> e5f0ac29ea7f
Step 2/16 : WORKDIR /code
 ---> Running in 4306a0a7a14e
Removing intermediate container 4306a0a7a14e
 ---> e03917533c36
Step 3/16 : COPY . .
 ---> 9142c9141354
Step 4/16 : RUN pip install --user --no-cache-dir --no-warn-script-location .
 ---> Running in 75a2cf22b1c8
Processing /code
  Installing build dependencies: started
  Installing build dependencies: finished with status 'done'
  Getting requirements to build wheel: started
  Getting requirements to build wheel: finished with status 'done'
  Preparing metadata (pyproject.toml): started
  Preparing metadata (pyproject.toml): finished with status 'done'
Collecting apprise==1.4.5 (from mailrise==1.4.0.post1.dev4+gf7543c3)
  Obtaining dependency information for apprise==1.4.5 from https://files.pythonhosted.org/packages/fe/3d/abff61b16fc4fd06e6d7be7c1645514447ab6e2950134f67d0cf7860def0/apprise-1.4.5-py3-none-any.whl.metadata
  Downloading apprise-1.4.5-py3-none-any.whl.metadata (41 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 41.5/41.5 kB 2.6 MB/s eta 0:00:00
Collecting aiosmtpd==1.4.4.post2 (from mailrise==1.4.0.post1.dev4+gf7543c3)
  Downloading aiosmtpd-1.4.4.post2-py3-none-any.whl (154 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 154.2/154.2 kB 9.9 MB/s eta 0:00:00
Collecting PyYAML==6.0 (from mailrise==1.4.0.post1.dev4+gf7543c3)
  Downloading PyYAML-6.0.tar.gz (124 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 125.0/125.0 kB 32.9 MB/s eta 0:00:00
  Installing build dependencies: started
  Installing build dependencies: finished with status 'done'
  Getting requirements to build wheel: started
  Getting requirements to build wheel: finished with status 'error'
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [54 lines of output]
      running egg_info
      writing lib/PyYAML.egg-info/PKG-INFO
      writing dependency_links to lib/PyYAML.egg-info/dependency_links.txt
      writing top-level names to lib/PyYAML.egg-info/top_level.txt
      Traceback (most recent call last):
        File "/usr/local/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/usr/local/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/usr/local/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
          return hook(config_settings)
                 ^^^^^^^^^^^^^^^^^^^^^
        File "/tmp/pip-build-env-2yih6re6/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 355, in get_requires_for_build_wheel
          return self._get_build_requires(config_settings, requirements=['wheel'])
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/tmp/pip-build-env-2yih6re6/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 325, in _get_build_requires
          self.run_setup()
        File "/tmp/pip-build-env-2yih6re6/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 341, in run_setup
          exec(code, locals())
        File "<string>", line 288, in <module>
        File "/tmp/pip-build-env-2yih6re6/overlay/lib/python3.12/site-packages/setuptools/__init__.py", line 103, in setup
          return distutils.core.setup(**attrs)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/tmp/pip-build-env-2yih6re6/overlay/lib/python3.12/site-packages/setuptools/_distutils/core.py", line 185, in setup
          return run_commands(dist)
                 ^^^^^^^^^^^^^^^^^^
        File "/tmp/pip-build-env-2yih6re6/overlay/lib/python3.12/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
          dist.run_commands()
        File "/tmp/pip-build-env-2yih6re6/overlay/lib/python3.12/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
          self.run_command(cmd)
        File "/tmp/pip-build-env-2yih6re6/overlay/lib/python3.12/site-packages/setuptools/dist.py", line 989, in run_command
          super().run_command(command)
        File "/tmp/pip-build-env-2yih6re6/overlay/lib/python3.12/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/tmp/pip-build-env-2yih6re6/overlay/lib/python3.12/site-packages/setuptools/command/egg_info.py", line 318, in run
          self.find_sources()
        File "/tmp/pip-build-env-2yih6re6/overlay/lib/python3.12/site-packages/setuptools/command/egg_info.py", line 326, in find_sources
          mm.run()
        File "/tmp/pip-build-env-2yih6re6/overlay/lib/python3.12/site-packages/setuptools/command/egg_info.py", line 548, in run
          self.add_defaults()
        File "/tmp/pip-build-env-2yih6re6/overlay/lib/python3.12/site-packages/setuptools/command/egg_info.py", line 586, in add_defaults
          sdist.add_defaults(self)
        File "/tmp/pip-build-env-2yih6re6/overlay/lib/python3.12/site-packages/setuptools/command/sdist.py", line 113, in add_defaults
          super().add_defaults()
        File "/tmp/pip-build-env-2yih6re6/overlay/lib/python3.12/site-packages/setuptools/_distutils/command/sdist.py", line 251, in add_defaults
          self._add_defaults_ext()
        File "/tmp/pip-build-env-2yih6re6/overlay/lib/python3.12/site-packages/setuptools/_distutils/command/sdist.py", line 336, in _add_defaults_ext
          self.filelist.extend(build_ext.get_source_files())
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "<string>", line 204, in get_source_files
        File "/tmp/pip-build-env-2yih6re6/overlay/lib/python3.12/site-packages/setuptools/_distutils/cmd.py", line 107, in __getattr__
          raise AttributeError(attr)
      AttributeError: cython_sources
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.
The command '/bin/sh -c pip install --user --no-cache-dir --no-warn-script-location .' returned a non-zero code: 1
exit status 1

Thanks for the report. All looks good with the pyyaml bump.


iroh-dns-server: very heavy disk write load

The iroh dns server seems to do a lot of writing. I have about 30,000 clients at the moment with a republish interval of 2 minutes (so that should average to 250/sec), and I'm seeing a write throughput of about 7Mb/sec from 1,500 writes/sec on the dns server disk.
I'm surprised to see this much load considering the records should be around 1KB, so I'd expect more like 0.25Mb/sec.
This seems so wrong I'm wondering if my Endpoint is somehow misconfigured?
let discovery = ConcurrentDiscovery::from_services(vec![
    Box::new(PkarrPublisher::with_options(
        self.secret_key.clone(),
        self.iroh_config.pkarr_url.clone(),
        30,
        Duration::from_secs(60 * 2),
    )),
    Box::new(DnsDiscovery::new(self.iroh_config.dns_url.clone())),
]);

let endpoint = Endpoint::builder()
    .secret_key(self.secret_key.clone())
    .alpns(vec![ALPN.to_vec()])
    .relay_mode(RelayMode::Custom(relay_map))
    .discovery(Box::new(discovery))
    .transport_config(transport_config)
    .bind()
    .await
    .unwrap();

I don't have prometheus set up to scrape the server metrics yet, but I'll try to see if there's any crazy metrics tomorrow

My first thought is that the writes might be inflated due to the filesystem block size.  But I haven't checked and am not familiar with this codebase.

Actual size seems to even just half that
let key = SecretKey::generate();
let node_id = key.public();
let node_info = NodeInfo::new(
    node_id,
    Some("https://my-relay.com".parse().unwrap()),
    [
        "<IP_ADDRESS>:1245".parse().unwrap(),
        "<IP_ADDRESS>:1246".parse().unwrap(),
        "<IP_ADDRESS>:1247".parse().unwrap(),
        "<IP_ADDRESS>:1248".parse().unwrap(),
        "[::]:1241".parse().unwrap(),
        "[::]:1242".parse().unwrap(),
        "[::]:1243".parse().unwrap(),
        "[::]:1244".parse().unwrap(),
    ]
    .into_iter()
    .collect(),
);
let ttl = 1024;
let packet = node_info.to_pkarr_signed_packet(&key, ttl).unwrap();

assert_eq!(packet.as_bytes().len(), 450);

So worst case storing ~500 bytes for the value + 32 bytes for the key.

My first thought is that the writes might be inflated due to the filesystem block size.

That is unlikely, as that wouldn't show up as actual IO ops asfaik, only that things are slow.

I believe this is fixed with #2995


github api user agent

hopefully this will mitigate the risk that github api calls return a 403 forbidden
the docs suggest this should always have happened, if you read them a certain way
https://developer.github.com/v3/#user-agent-required
so i'm not sure this is the cause/fix for intermittent 403s, we shall see

Now respinning the 'minimal' tests a few times, to exercise this fix a bit more ...

respinning the 'minimal' tests a few times

Done that + all seems solid.
Much nicer than a retry.
:clap: Awesome righteous fix @marqh !


File copy in UNC folders doesn't work anymore

VSCode Version: 1.17.0
OS Version: Windows 10

Steps to Reproduce:

Open a folder
select file
copy file
Error: A system error occurred (UNKNOWN: unknown error, mkdir '\\servername\servername\myprojects\myproject')

Correct path in my example is: \\servername\myprojects\myproject
Reproduces without extensions: Yes

We should always use resource.path when we use uri.with calls.
This was first introduced by https://github.com/Microsoft/vscode/commit/a7e2b9827f0a32a344629237faa78cf063e406d7
@jrieken can you please code review

👍 Yeah, that is a good change

I built latest insiders and verified this works.
Easy verification steps open a local file on windows as it is a unc path via
\\localhost\c$\my_dir

I pushed the fix on top of release/1.17
@jrieken can you please verify once we have stable builds out tomorrow?

Yeah, will do

Doesn't appear anymore for me


Kong Regex In Uri

Hi i have 2services that i want to share same Domain...the difference is if user go to "www.domain.com" should redirect to my Landings Service but if user add anything after the domain itself like "www.domain.com/[UserName]" user should redirect to My DashBoard Service...for that i used a Regex in Uri for the Dashboard Service like below:
/(?=(.[a-z0-9]){3}+)(?=(^((?!static|js|css).)$))
all it say is the username should be at least 3 characters or numbers and url should not contain any js or css or static words in it....
now when i save this changes  it dosent work and always redirect user to DashBoard Service even if user enters "www.domain.com" and nothing after it...
i dont know how to make it work!
P.s: the uri for the Landings Service is just a "/"
P.s2: if i empty the browser cache and try  "www.domain.com" it sends a request to "www.domain.com/css/main.css" and redirects to My Landings wich is what i want but i refresh "www.domain.com" it goes to dashboard again!

We appreciate you took the time to open an issue for this. However, kong github issues are for bug reports only. I'd like to ask you to post this on the Kong Nation forum
I'll close this issue now. If you think this was closed in error, then please reopen.


refactored GET /api/tickets/{id}/artifacts/{artifact} route to GET /a…

…pi/tickets/{id}/artifacts/screenshots for specifically getting screenshots. need to add functionality to eventually get js (once honeyclient implements and captures). For issue #41

Looks good, reviewed in person at Keller.


voice commanded email bot

This is the code for the voice recognition automation bot. we can send emails with your voice commands without typing anything which is very helpful in sending multiple emails in a very short duration

Awesome work just attache the ss here of you output.

Awesome work 🎊

@neelshah2409 are you from ITNU?

@neelshah2409 are you from ITNU?

Awesome work 🎊

Thanks 😊


GRPC compression hurting CPU performance.

What version of gRPC and what language are you using?
Release Date          2023-04-17 18:46:47
Release Version       1.54.0 (stable)
API Version           1.54.0 (stable)
What operating system (Linux, Windows,...) and version?
gLinux - 6.1.20-2rodete1-amd64
What runtime / compiler are you using (e.g. python version or version of gcc)
php7.4
What did you do?

I tried to compress request messages in example php client side.

I compressed in per call basis by setting the grpc-internal-encoding-request header metadata to gzip.
Verified the compression by setting grpc debug flags: GRPC_VERBOSITY=info and GRPC_TRACE=compression.
Created a script to send multiple request in a loop with each request's size being ~1MB.

For server, used the nodeJS example server.
Ran the client in a docker container and observed it's performance and bandwidth using cAdvisor.

What did you expect to see?
I expected to see ~47% bandwidth savings(shown in GRPC logs) and less than 2 times increase in CPU usage for realistic repeated twitter like data as this is the case in Java grpc.
What did you see instead?
Bandwidth savings are more than expected but the cpu utilisation increases by 5 times atleast. Tried the same using PHP pub sub client and saw a cpu increase of 3 times with the slightly more than expected bandwidth savings.
Anything else we should know about your project / environment?
No

Was the CPU of node JS server increased 5x as well?
What's your hardware configuration?
Was client and server on the same host?
How much qps did you get with and without compression?
Can you share your test script?

Thanks @alto-php for looking into this. Below are some more info regarding this as requested:-
Hardware configuration
It's a cloud machine with 48 CPUs with 2 cores each and 192 gb Ram. Debian OS.
CPU for Node JS server
I'm running the docker and the node js server on the same system. So it's hard to say how much CPU increase only for NodeJs server.
Code to repro
For NodeJS server

I just ran the example which is provided in the grpc repo.

For PHP Client

Ran this client in a separate docker container.
The container used this php image
Used the HelloWorld example.
I modified the BaseStub.php > __simpleRequest() method by adding the compression header to enable compression in per call basis as follows:

protected function _simpleRequest(
        $method,
        $argument,
        $deserialize,
        array $metadata = [],
        array $options = []
 ) {
        // Added this line
        $metadata['grpc-internal-encoding-request'] = ['gzip'];
        // Rest of the code...
 }

Modified the greeter_client.php so that it sends request in loop iterating 3 times and logs the QPS.

    $starttime = microtime(true);
    $request = new Helloworld\HelloRequest();
    $request->setName($name);
    for ($x = 0 ; $x < 300 ; ++$x) {
        list($response, $status) = $client->SayHello($request)->wait();
    }
    $endtime = microtime(true);
    $timediff = $endtime - $starttime;
    printf('Time taken is: ' . $timediff . ' and QPS = ' . 1000 / $timediff . PHP_EOL);

Exact CPU utilisation
Got this from running docker stats. 100% => Full utilisation of 1 CPU I think because it shoots more than 10% when simultaneous scripts are run
Without compression:

CPU - ~12.5%
QPS - ~356 queries per second

With Compression:

CPU - ~97%
QPS - ~71.5 queries per second

Thanks for the detailed numbers.
First of all, you don't need to change BaseStub.php  to enable compression, you can just pass the metadata to SayHello for per-call compression. Alternatively you can also enable compression to the channel as documented here.
Regarding the CPU utilization, sending requests in a loop should always get you close to 100% cpu utilization, you can try run the test longer so you will observe that CPU jumped to 100%.
Compression is done in c code where the overhead should be similar to all languages that use c-core.
Following are my test resutls using cpp server (kept getting 'invalid wire type 7' errors with nodejs server) with 1MB payload, where the cpu usage is close to 100% with php, and with cpp it's like 2x CPU and half the QPS.
Given the test client/server basically does nothing but send and receive the data, it make sense that compress/decompress cost most of the CPU as it's mostly compression vs copying. For a production servers/clients that has other logics, the cost of compression should become less significant. If CPU utilization is an issue, you can also try different compression algorithms and levels to find the right balance for your use case.
Test results:
with compression:
client: 83%, server: 18%, QPS: 12
without compression:
client: 94%, server: 9%, QPS: 23

@alto-php, thanks for all the insights.

Regarding the CPU utilization, sending requests in a loop should always get you close to 100% cpu utilization, you can try run the test longer so you will observe that CPU jumped to 100%.

I increased the loop count to 10000 in without compression and still observe <15% utilisation.


Update translation files with fixes

Files:

[x] https://praekelt.atlassian.net/browse/NDOH-294
[x] https://praekelt.atlassian.net/browse/NDOH-296

@imsickofmaps Please review.

:+1:


Too many hardcoded pathnames

The user "ubuntu" and pathname "/home/ubuntu" are hardcoded in several places in the teuthology tree which makes it impossible to run as a user other than "ubuntu".
It is possible to workaround some of this but it would be more robust if the "ubuntu" username were made to be a global configuration variable or something easier to change.

See http://tracker.ceph.com/issues/10086


ci(release): fix misconfigured npm plugin

Closes https://github.com/okp4/eslint-config-okp4/issues/11#issue-1170967806

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


cant provision provider 1.1.4 from registry

When using provider declaration from registry, I get a unexpected SHA error :
Initializing the backend...

Initializing provider plugins...
- Finding alexissavin/solidserver versions matching "1.1.4"...
- Installing alexissavin/solidserver v1.1.4...

Error: Failed to install provider

Error while installing alexissavin/solidserver v1.1.4: checksum list has
unexpected SHA-256 hash
6302c196352e167784582de2b85e83590791926d8245d45bfa21aef491be5bcc (expected
6b4ffd8a604ff6ab2fc22f83d966d4be923f52b82bd057807c4621692ff14b81)

providers.tf
terraform {
  required_providers {
    solidserver = {
      source = "alexissavin/solidserver"
      version = "1.1.4"
    }
  }
}

Using 1.1.3 version works.

Hello,
Well, that's quite surprising, I don't know how do you end up with this hash.
From the information provided, I suppose you are running terraform on linux and trying to use the following file: terraform-provider-solidserver_1.1.4_linux_amd64.zip.
What's surprising is that the sha256sum value in the terraform-provider-solidserver_1.1.4_SHA256SUMS seems correct.
#sha256sum  terraform-provider-solidserver_1.1.4_linux_amd64.zip
6302c196352e167784582de2b85e83590791926d8245d45bfa21aef491be5bcc  terraform-provider-solidserver_1.1.4_linux_amd64.zip

I don't understand how you can get the following value : "6b4ffd8a604ff6ab2fc22f83d966d4be923f52b82bd057807c4621692ff14b81".
I will try to reproduce.
Kind regards

Hello,
Fixed by version 1.1.5.
I suspect some caching issue with Terraform registry.
The files available on GitHub seems to differs from the ones downloaded by the Terraform installer.
Please confirm that this version works for you.
Kind regards

I can confirm it's fixed now ! Thanks for your work on this provider ;)


NoteStorage/Note does not notify the GUI when a note has been changed

Need to implement IPropertyNotify somewhere.

Fixed on branch https://github.com/NoteTakerPlus/NoteTakerPlus/tree/C006.4-update-gui


Integrate low-level (point nav + social nav + pick + place) policies for the demo

The initial integration of point nav (find the object), pick, social nav (return to human after picking up the object), and place neural network skills are finished.
There are still a few things that need to be polished, such as the place policy drops the object at a few steps without too much arm animation, etc.

CLI to run the demo
python examples/siro_sandbox/sandbox_app.py --app-state fetch --disable-inverse-kinematics --never-end --width 1920 --height 1080 --gui-controlled-agent-index 1 --save-gfx-replay-keyframes --save-filepath-base "/Users/jimmytyyang/Downloads/soc_nav_video/video_v8" --ang-speed 10 --cfg examples/siro_sandbox/configs/fetch.yaml --cfg-opts \~habitat.task.measurements.agent_blame_measure habitat.task.actions.agent_0_oracle_nav_action.type=OracleNavCoordAction habitat_baselines.evaluate=True habitat.simulator.step_physics=True

The Google folder link to download neural network skills (point-nav, pick, social-nav, place): https://drive.google.com/drive/folders/1Ddmt30hBUPL0pwfsXWj-K4CQYgOGsZNg?usp=sharing

The New CLI without OracleNavCoordAction
python examples/siro_sandbox/sandbox_app.py --app-state fetch --disable-inverse-kinematics --never-end --width 1920 --height 1080 --gui-controlled-agent-index 1 --save-gfx-replay-keyframes --save-filepath-base "/Users/jimmytyyang/Downloads/soc_nav_video/video_v8" --ang-speed 10 --cfg examples/siro_sandbox/configs/fetch.yaml --cfg-opts \~habitat.task.measurements.agent_blame_measure  habitat_baselines.evaluate=True habitat.simulator.step_physics=True

Note that the point nav policy was updated. Please go to Google link above and download the new model (checkpoint)


Change links in Flutter docs pointing to 'Getting Started' for installation/setup instructions. Point to 'Flutter Setup' page instead.

Fix any old references pointing to the Getting Started for installation-related instructions.
Instead, they should link to the 'Flutter Setup' page (https://flutter.io/setup) as the central location for installation/configuration steps.

I'm going to close this on the basis that we don't know which links this referred to and we'll fix them as we find them.


permission denied, mkdir '/opt/stacks'

Getting this error when trying to start backend, i am using Gitpod as i my pc dont support Docker :(

Since I am developing this on Windows, I think you need to set DOCKGE_STACKS_DIR=<your path> at this moment.

Since I am developing this on Windows, I think you need to set DOCKGE_STACKS_DIR=<your path> at this moment.
But I don't think gitpod could run docker compose commands either? Should develop it on your PC.

Ohhh so then i will give it a try on codespace.

Also just to remind u didn't make a release for 1.0.2 on release page and not 1.0.3

Also just to remind u didn't make a release for 1.0.2 on release page and not 1.0.3

Forget to press release.😂


Captions not showing in slideshow

How do I display photo/video captions when using slideshow mode. The caption display when using browse mode but not slideshow mode.
Thanx

When you say "captions" are you referring to the photo details / date? a.k.a Pause overlay.
The "Pause Overlay" is displayed when you Pause a slide show or Click UP / Down arrows during slide show.


Implemented restart retrying

This autoheal container watches for unhealthy containers and sends a restart command to unhealthy container when finds some.
However, sometimes that container starts and fails again, or it fails to restart.
This patch adds an ability to look after restarting container until it restarts successfully.
AUTOHEAL_RETRIES container parameter was also introduced for maximum restart attempts.

I would argue that if the container keeps on retrying, there's typically an underlying issue with the container itself, and not just a temporary condition.
Could you give an example where this has been an issue for you?

In my case this is the HomeAssistant  container. It crashes for some external reason, and the original Autoheal fails to restart it.
More details: external reason is a VPN container, which restarts once a day. Its warm-up time might be a bit longer than HomeAssistant's, that's why HA crashes immediately after start.
I put my changes directly into Autoheal and it restarts HA successfully at 2-3 attempt.
I would say that VPN might be offline temporarily for different reasons and my case is just a small individual case.

I would argue that if the container keeps on retrying, there's typically an underlying issue with the container itself, and not just a temporary condition.
Could you give an example where this has been an issue for you?

I generically can state race conditions with services - including other services healed by autoheal. A case is a webservice with healthcheck that leads on database connection and the database also dies.
Also, this PR may need to be refreshed from main branch.


Weather Data Error

your weather data has a duplicate value "2020-05-12 06:00:00"

Sorry for the mistake. You can delete the duplicate value.


Increase MaxIdleConnsPerHost for feeder TestClient

On macOS tests often fail with the following error:
"Get "http://<IP_ADDRESS>:xxxx/get_{feeder gateway method}?{arg}={value}": dial tcp <IP_ADDRESS>:xxxx: connect: can't assign requested address"
This error make running local tests, in quick succession, difficult because we have to wait for the OS to release ports. Sometimes the sync tests will hang because sync process will keep requesting if there was some error. This problem is further exacerbated by having parallel tests.
Increasing test client's idle conns allow for large concurrent requests to be made from a single test client.

Done


A small ambiguity in luna_preprocess.py

I'm not sure if the local_windows should be saved in the second np.save statement.

Thanks for pointing it out. This is a misalignment between our local version and the online one. We have fixed it in the update.

@ZAX130 Have you achieved the effect of the code?


chore: release 1.2.323

:robot: I have created a release *beep* *boop*
1.2.323 (2024-07-31)
Bug Fixes

build, buildah, dockerfile, staged: ensure setting ENTRYPOINT correctly resets base image CMD (83fe844)
build, buildah, dockerfile, staged: fix handling of CMD and ENTRYPOINT in exec format (02dd60c)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/werf/werf/releases/tag/v1.2.323 :sunflower:


Border of lsp float window disappears when writing function in insert mode

Description
I have set the highlight of NormalFloat and FlaotBorder to fit my background color(I am using gruvbox colorscheme), as follows:
vim.cmd("hi NormalFloat guibg=#32302F")
vim.cmd("hi FloatBorder guibg=#32302F guifg=#F2E2C3")

Then when my cursor is right after the parenthesis of a function in the insert mode, the lsp float window shows up, like this:

I want the window to be bordered, so after checking the wiki I set
local lspconfig = require("lspconfig")
local handlers = {
	["textDocument/hover"] = vim.lsp.with(vim.lsp.handlers.hover, { border = "rounded"}),
	["textDocument/signatureHelp"] = vim.lsp.with(vim.lsp.handlers.signature_help, { border = "rounded"}),
}
lspconfig.pyright.setup({
	handlers = handlers,
})
lspconfig.lua_ls.setup({
	handlers = handlers,
})

But it seems not working, what should I do? Any help would be appreciated.
Btw, when I invoke vim.lsp.buf.hover in the normal mode, there is a bordered float window shown beside my cursor, which is what I also want when writing a function in the insert mode.

Neovim version
NVIM v0.9.1
Build type: Release
LuaJIT 2.1.0-beta3
Nvim-lspconfig version
a981d44
Operating system and version
macOS 12.6.7
Affected language servers
all
Steps to reproduce
Same as description.
Actual behavior
Border of lsp float window disappears when writing function in insert mode.
Expected behavior
Border of lsp float window shows when writing function in normal mode, like when vim.lsp.buf.hover is invoked.
Minimal config
vim.cmd("hi NormalFloat guibg=#32302F")
vim.cmd("hi FloatBorder guibg=#32302F guifg=#F2E2C3")
local lspconfig = require("lspconfig")
local handlers = {
	["textDocument/hover"] = vim.lsp.with(vim.lsp.handlers.hover, { border = "rounded"}),
	["textDocument/signatureHelp"] = vim.lsp.with(vim.lsp.handlers.signature_help, { border = "rounded"}),
}
lspconfig.pyright.setup({
	handlers = handlers,
})
lspconfig.lua_ls.setup({
	handlers = handlers,
})

LSP log
https://gist.github.com/yizhenAllen/7f724d12a5cafe29d307b4068eaf08da

how do you trigger signatureHelp ?

You mean the first image in my comment? The float window shows up automatically.
As for vim.lsp.buf.hover, I map it to a shortcut in normal mode.

that's set by your completion plugin I think there is no way auto open signaturehelp in builtin . some completion plugin do it . if you want test the behavior of the override handlers try :lua vim.lsp.buf.signature_help

vim.lsp.buf.signature_help does show up a float window with a border.
I use nvim-cmp to autocompletion, but the float windows without border still shows up after I turn off everything about cmp?

https://github.com/hrsh7th/cmp-nvim-lsp-signature-help

All right, thanks, I will go take a look.

@yizhenAllen, did you found a solution? I am facing the same problem. I can't recall it was always like that. I think it happened recently after updating some plugins and neovim nightly maybe.

@calvinchoy Not yet, actually Idk which plugin is causing this "feature" after @glepnir said nvim-lspconfig is not related to it.
I am using NVIM v0.9.1, and the plugins I am using that are relevent to lsp include mason.nvim, mason-lspconfig.nvim, nvim-lspconfig, lspsaga and nvim-cmp.

@yizhenAllen , thanks for getting back on this.
No problem, I am actually using the exact same plugins. Well it is more an aesthetic thing, so guess I will just live with it.
Thanks!

For the ones that are still looking. I figured out that the missing border is due to noice.nvim plugin:
	-- you can enable a preset for easier configuration
	presets = {
		lsp_doc_border = false, -- add a border to hover docs and signature help
	},

Changing lsp_doc_border = true, brings back the border as configured. I assume the default in noice set it to false overwriting whatever you have configured somewhere else.

For the ones that are still looking. I figured out that the missing border is due to noice.nvim plugin:
	-- you can enable a preset for easier configuration
	presets = {
		lsp_doc_border = false, -- add a border to hover docs and signature help
	},

Changing lsp_doc_border = true, brings back the border as configured. I assume the default in noice set it to false overwriting whatever you have configured somewhere else.

noice.nvim also makes signature_help showing up automatically which is annoying in some cases.
https://github.com/folke/noice.nvim/blob/bf67d70bd7265d075191e7812d8eb42b9791f737/doc/noice.nvim.txt#L257
hover = {
  enabled = true,
  silent = false, -- set to true to not show a message if hover is not available
  view = nil, -- when nil, use defaults from documentation
  ---@type NoiceViewOptions
  opts = {}, -- merged with defaults from documentation
},
signature = {
  enabled = true,
  auto_open = {
    enabled = true,
    trigger = true, -- Automatically show signature help when typing a trigger character from the LSP
    luasnip = true, -- Will open signature help when jumping to Luasnip insert nodes
    throttle = 50, -- Debounce lsp signature help request by 50ms
  },
  view = nil, -- when nil, use defaults from documentation
  ---@type NoiceViewOptions
  opts = {}, -- merged with defaults from documentation
},


Instance type i3 not supported

Hi, the new i3 instance type is not supported as per cloudformation/cfncluster.cfn.json. Andreas

Yes, this would be quite nice; any ETA?

Hi,
I added all i3 instance types to cloudformation/cfncluster.cfn.json and uploaded it to a publicly accessible location. This was done similar to b81a164c932fef3d5a9ea312ed8d391cfefe414b
When I then select any i3 instance as master and specify the above url with  --template-url I still get:

Parameter MasterInstanceType failed to satisfy constraint: Must be a valid EC2 instance type, with support for HVM.

This should work though, right?
Andreas

Hi @andreas-wilm ,
I've similar problem with others new instances.
I've resolved the problem with add the template_url inside config file ( documentation http://cfncluster.readthedocs.io/en/latest/configuration.html#template-url ).

Just to pile on - x1.16xlarge also not supported though x1.32xlarge is; I will try your solution apalazzin thank you!

Please support r4 instances

This will be fixed in CfnCluster 1.3.2.  You can track the patch set at pull request https://github.com/awslabs/cfncluster/pull/188.

I3 instances are now supported with the release of CfnCluster 1.3.2.  Please note that auto-creation of /scratch doesn't work on I3 (see https://github.com/awslabs/cfncluster/issues/195).  This will be fixed in a follow-on release.


Feature Request: Add support for setting "exclude from SSO" on network members

currently the zerotier_member resource does not support setting the "exclude from sso" attribute on a member.
According to the docs, this is supported by the Central API
Could we get support for this in the terraform provider?
I have tried figuring out the required changes in terraform-provider-zerotier  & go-ztcentral on my own, and to me it seems like the parameter would only need to be added to the spec for the member config in both to achieve this, but I'm not familiar with the code nor well versed in go, so take this with a grain of salt.

@someara


backup-capi-clusters

implement etcd backups for generic CAPI cluster using Kubernetes proxy port forwarding
pkg/etcd/proxy code is copied from the cluster-api control plane controller, unfortunately, its under an internal package and it cannot be imported co its  just copy-paste

{"caller":"github.com/giantswarm/etcd-backup-operator/v3/service/controller/resource/etcdbackup/backup.go:23","controller":"etcd-backup-operator-etcd-backup-controller","event":"update","level":"debug","loop":"76","message":"Attempt number 1 for gohan","object":"/etcd-backup-20220705120319","resource":"etcd-backup","time":"2022-07-05T12:07:49.75181+00:00","version":"5351931"}
{"caller":"github.com/giantswarm/etcd-backup-operator/v3/service/controller/resource/etcdbackup/backup.go:50","controller":"etcd-backup-operator-etcd-backup-controller","event":"update","level":"debug","loop":"76","message":"Creating backup file","object":"/etcd-backup-20220705120319","resource":"etcd-backup","time":"2022-07-05T12:07:49.751858+00:00","version":"5351931"}
{"caller":"github.com/giantswarm/micrologger@v1.0.0/logger.go:66","level":"debug","message":"Compacting etcd instance","time":"2022-07-05T12:07:49.751881+00:00"}
{"caller":"github.com/giantswarm/micrologger@v1.0.0/logger.go:66","level":"debug","message":"Revision is 5352499","time":"2022-07-05T12:07:50.455319+00:00"}
{"caller":"github.com/giantswarm/micrologger@v1.0.0/logger.go:66","level":"debug","message":"Compacted etcd instance","time":"2022-07-05T12:07:50.551593+00:00"}
{"caller":"github.com/giantswarm/micrologger@v1.0.0/logger.go:66","level":"debug","message":"Defragging etcd instance","time":"2022-07-05T12:07:50.551627+00:00"}
{"caller":"github.com/giantswarm/micrologger@v1.0.0/logger.go:66","level":"debug","message":"Defragged etcd instance","time":"2022-07-05T12:07:52.439772+00:00"}
{"Created temporary directory: /tmp/440399139":"(MISSING)","caller":"github.com/giantswarm/etcd-backup-operator/v3/pkg/etcd/etcdv3.go:169","time":"2022-07-05T12:07:52.451703+00:00"}
{"level":"info","ts":"2022-07-05T12:07:52.452Z","logger":"etcd-client","caller":"v3@v3.5.4/maintenance.go:211","msg":"opened snapshot stream; downloading"}
{"level":"info","ts":"2022-07-05T12:08:09.652Z","logger":"etcd-client","caller":"v3@v3.5.4/maintenance.go:219","msg":"completed snapshot read; closing"}
{"caller":"github.com/giantswarm/etcd-backup-operator/v3/pkg/etcd/etcdv3.go:131","file":"gohan-gohan-v3-2022-07-05T12-07-52.db.tar.gz","level":"info","msg":"Etcd v3 backup created successfully","time":"2022-07-05T12:08:27.651711+00:00"}


Sia crashes on start.

It was working yesterday but still hasn't finished syncing my wallet. It's stuck at 99.1%
Loading...
(0/6) Loading siad...
(1/6) Loading gateway...
(2/6) Loading consensus...
(3/6) Loading transaction pool...
(4/6) Loading wallet...
(5/6) Loading host...
(6/6) Loading renter...
Finished loading in 0.962055 seconds

Are you still having an issue?  Can you upload your log files?  Try asking for help at https://discord.gg/sia


IGNORE THIS

This was a mis-directed keybase proof.

Do not file keybase proofs as issues on rustup please.


Support setup.py for windows and call make install from setup.py

I like that. So the idea is that

We only support cmake to build and install
setup.py simply calls cmake for both
It is not supported to import the package without installing it, one must install it first, then import it.

I think that's the way to go, but I just wanted to make sure that's how it works.

It is not supported to import the package without installing it, one must install it first, then import it.
You can just build (python setup.py build and import it)

We really need to fix https://github.com/symengine/symengine/issues/577.
+1 to merge this PR.


some wishlist items to be done

Todo

[x] include searchcount() function by default (like vim-anzu)
[x] extend the wordcount extension by "time left to read" (see here
[ ] explore Vim9script features to improve performance

Could I pin the issue?

sure

https://github.com/vim-airline/vim-airline/pull/2291
about Vim9script

Hi, there. Maybe searchcountneed an extra space? Check below img:

end[1/9] is provided by airline, end(1/9) by anzu.
And maybe will be better is could set the section to show it!
Thanks!

I think I have fixed it

I think I have fixed it

@chrisbra
This issue has been closed even though 'explore Vim9script features to improve performance' is not yet completed.
Do you think it's better to build a new issue or reopen this one?

Should be okay, we have the open PR that takes care of it. And I have to
finally update it
Am 2021-02-19 19:31, schrieb IK:

@chrisbra [1]
This issue has been closed even though 'explore Vim9script features to
improve performance' is not yet completed.
Do you think it's better to build a new issue or reopen this one?
--
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub [2], or unsubscribe
[3].
Links:
[1] https://github.com/chrisbra
[2]
https://github.com/vim-airline/vim-airline/issues/2154#issuecomment-782259487
[3]
https://github.com/notifications/unsubscribe-auth/AAB3ZP2CJB5XNTCE2JUBZW3S72U77ANCNFSM4OBISZVA

Ok, I got it.
Thanks for your quick reply.


feat: attach config passed to widget to window

Summary
attach config passed to widget to window
e.g.:
window.__rango.config
How did you test this change?
The config is available in the console.
Checklist:

[x] I have performed a self-review of my code

For debugging purposes we need to have a full representation of config, not only the part passed by dApp. It's possible to change default configs during releases for us, so we need to know what config user is using. I think that would be good to keep these two (dApp input and default configs) separated.


[3.2.0] externalize-deps behavior changed from 3.1.8 - unable to import tailwindcss/plugin

Describe the bug
In v3.1.8 this worked.
// vite.config.ts
import plugin from 'tailwindcss/plugin'

It is currently failing. Have verified that in the reproduction, if the vite version is set to "3.1.8" instead of "^3.1.8" it will not throw the error.
Update: have checked that this is also present on 3.2.0-beta.0 (using the same reproduction)
Reproduction
https://stackblitz.com/edit/vitejs-vite-dyzuez
Steps to reproduce
both dev and build fails
System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 7.17.0 - /usr/local/bin/npm
  npmPackages:
    vite: ^3.1.8 => 3.2.0

Used Package Manager
npm
Logs
✘ [ERROR] [plugin externalize-deps] Cannot find module '/home/projects/vitejs-vite-dyzuez/node_modules/tailwindcss/plugin' imported from /home/projects/vitejs-vite-dyzuez/vite.config.ts

    node_modules/esbuild/lib/main.js:1321:27:
      1321 │         let result = await callback({

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

thanks, verified that adding .js extension works with 3.2.0 and will try to use that moving forward


HTTP NET Error when attempting to start ZSeries

Reproduction Steps:

Get a Rasp Pi Zero W, and run through the steps here
Add address=/picobrew.com/<IP_ADDRESS> /etc/dnsmasq.conf
Connect to your new WiFi network and run nslookup picobrew.com and verify it goes to your server
Clone this repo, and start the server with sudo python3 server.py
Connect your Picobrew Z to the new network and watch it startup

Expected: The Picobrew starts with no recipes
Actual: The Picobrew doesn't start. It shows an "HTTP NET ERROR" and is stuck. I have to turn off the wifi network to continue. The local python environment shows a 200 for the request:
<IP_ADDRESS> - - [22/Jul/2020 23:29:17] "GET /zseries_recipes HTTP/1.1" 200 -
<IP_ADDRESS> - - [22/Jul/2020 23:29:19] "GET /zseries_recipes HTTP/1.1" 200 -

I'm sure there may be some step I'm missing here, and this isn't actually a bug, but maybe there's an obvious step I'm missing or something special missing for the ZSeries...

you need recipes to send to the device
if you're not using our pi image, it's up to to support your configuration

@austinchambers the logs shown aren't requests made by the connected picobrew hardware instead those look like requests made by you manually to retrieve /zseries_recipes (the frontend UI for recipe library for the Z Series).
Logs from the Z should be in the following format:
/Vendors/input.cshtml?ctl=<Controller>&token=<Token>

or
/Vendors/input.cshtml?type=<Type>&token=<Token>

Ah, I actually didn't realize that there was a preconfigured image. I was going off the readme.md. I'll try that image out now -- thanks!

It works!! Thanks again!

awesome, yeah we have forgotten to update the README.md with both references for the RaspberryPi bundled release images as well as updating for specific dependencies needed to get ZSeries devices to work (requirement for ssl, etc)

Trying to help where I can. Hope it's useful: https://github.com/chiefwigms/picobrew_pico/pull/69


Forecast one value for each sample (t to t+1)

I'd like to pass a time series with N samples as input and predict t+1 for each sample. How can I accomplish this?
In the parameters, I have only found a way to change the prediction horizon, but it appears that this method uses the history to predict t+1 only for the last time step, rather than for all the samples.

Hi @luizfysouza. Can you provide more details, please? By sample, do you mean timestamp, right? So you want to predict rolling forecasts for the entire time series. The predict method is designed only to produce outsample forecasts (the future after the last observation of the input data). You can use the cross_validation method to produce rolling forecasts for the test set (specified with n_windows or test_size).

Hi @luizfysouza. Can you provide more details, please? By sample, do you mean timestamp, right? So you want to predict rolling forecasts for the entire time series. The predict method is designed only to produce outsample forecasts (the future after the last observation of the input data). You can use the cross_validation method to produce rolling forecasts for the test set (specified with n_windows or test_size).

Yes, I mean timetamp... Sorry, not very used to time series haha.
So, yes, I'd like to predict my target variable at each timestep using just the previous timestamp. So, if I pass, for example, a series with 100 values, it should return me the prediction for all the 100 values (the last one being in the future). That is, I'd like to shift my series one to the left, pass it as input, predict t+1 for each timestamp and compare to the original (not shifted) in each position.
In order to do that, I should use input_size = 1 and horizon=1, right?
However, when I pass the number of windows or test size as the number of timestamps, it returns  "Exception: No windows available for training"

Yes, it should be input_size=1 and horizon=1. Is there a reason you want only to use one value as input to forecast? You can have a larger input size and keep the horizon=1.
You need to have windows available for training. Usually, we split the whole available data into train and test sets (everything before a particular timestamp is training data). The models are trained on the train set and then evaluated on the test set. If you set test_size=total_length, then the train set is empty.
You have two options:

Define a train/test split, and recover the forecasts only for the test set, using the cross_validation function.
Train the model with fit and set test_size=0. Then, use the predict_insample to produce all the forecasts for your data. Note that these are insample predictions, so the forecasts should be very accurate.

Ok, that's exactly what I wanted, thtank you. It makes sense, the question was a bit stupid, i'm not used to using a  lib that is so encapsulated like this one.
Another question: Is there an easy way to predict more than 1 time series? For example, predict Temprature, humidity and energy consumption. If yes, how do I do it? Because I think i can't define 'y' as a vector, like [Temp, Humidity, Energy]. The only option would be to use the 'unique_id' and  predict one by one?

The library is building global models, which means that one model will be used to forecast all the unique_id time series from the dataset (also named cross-learning). Most models are univariate, so forecasts are independent between them. You can set different features using the unique_id column (in a long format).


feat: Customize header ids

This pull request adds new feature: customizable header ids.
It’s useful for non-Latin texts, where header might be, for example, in Russian, but user wants id to be in English.
This feature allows user to set id for header manually, using curly braces:
## Привет, мир {hello-world}

I'm currently looking into this and will try to merge before next release

merged this PR with some changes. The custom ID will be the last bracketed text.
# some header {foo} {bar} {baz}

results in:

some header {foo} {bar}

👍


Feature/imports 4a

Test reports are working. Need to do granular commits from imports-3-frozen once again.


Update tomcat-catalina, tomcat-coyote, ... to 10.0.5

Updates

org.apache.tomcat:tomcat-catalina
org.apache.tomcat:tomcat-coyote
org.apache.tomcat:tomcat-util-scan

from 9.0.45 to 10.0.5.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (9.0.45).
You might want to review and update them manually.
website/src/hugo/content/changelog.md

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.apache.tomcat" } ]

labels: library-update, semver-major, old-version-remains

Not ready for the servlet leap.


Add b2c authentication properties with auto-config, #464.

Inject properties to auto-configuration.
Add test for bean and properties.

Signed-off-by: Pan Li<EMAIL_ADDRESS>

FYI
azure:
  activedirectory:
    b2c:
      tenant: xxxxx
      client-Id: xxxxxx
      policies:
        sign-up-or-sign-in:
          name: xxxx
          redirect-url: xxxx
        profile-editing:
          name: xxxx
          redirect-url:
        password-rest: xxxx
          name: xxxx
          redirect-url: xxx


Automatic classification of TS data type

Implement an algorithm for automatic classification of data type for specialized data cleaning/normalization workflow driven by the type and nature of data.

Future enhancement. Focus on the assumption that the data type is known.

PR https://github.com/IBM/TSML.jl/pull/20


Add option to skip warning severity checks

Is your feature request related to a problem? Please describe.
The checks with the severity WARNING are only recommendations, not security holes in the infrastructure. Thus, they can be tolerated in some cases.
Describe the solution you'd like
A command line option to skip warning checks. For example: tfsec --ignore-warnings.
The same configuration should also be available in the config file.

Thanks for implementing this feature quickly.

yup, thanks @michal-franc

I see this has been marked as deprecated now with #871 - is there an alternate recommended way to ignore all warning-level checks, or can checks only be ignored via tfsec -e <check> or by adding a comment to the tf code?


WIP: add lerna changelog

Fixes #18
So far, I'm just getting a list of commits that are either the merge commit or a commit to master directly.

Running:
 GITHUB_AUTH=auth-token-here GITHUB_ORG=babel GITHUB_REPO=babel ./node_modules/.bin/lerna changelog
Right now we error if you pass more than 2 args so we'll either have to support multiple args, do more process.env stuff, or add a config file?

Almost done but it's needs to be generalized (just want to get it working for babel)

Didn't get to updating the readme but I would do that as well
Maybe a screenshot or example of what it looks like (or just link to the next babel changelog release when we do it).

Can pr the one in the repo instead of my branch.


[Hue] Cannot connect to my bridge

Extension
https://www.raycast.com/pindab0ter/hue
Description
Error:
Error: No Hue Bridge configured

Object.le:toggleAllLights.ts:19:48

---
16: export default async function ToggleAllLights() {
17:   try {
18:     const bridgeConfigString = await LocalStorage.getItem<string>(BRIDGE_CONFIG_KEY)

### Steps To Reproduce

Unsure how to reproduce.
Cannot reconnect my Hue Bridge even after reinstalling the app.

### Current Behaviour

_No response_

### Expected Behaviour

_No response_

Does this happen with all commands, or just the Toggle All Lights command?


Calendar widget not responding to on tap on date

Steps to reproduce:

Login
Add a new work out
Pop back to Calendar page
Click on current date
Observe nothing happens

Current: Nothing happens
Expected: I should be able to see workout for that day
Video:
https://user-images.githubusercontent.com/26508767/183371431-7f9350e4-0758-40ef-ae41-5e3f5bf6522c.mp4

@KalleHallden 👀

@KalleHallden I haven't tested this branch but is it possible that this branch (https://github.com/KalleHallden/exer_log/tree/calendar-page) wasn't merged and the feature is working fine there?

@dinurymomshad
The calendar-page branch contains 1 line of code change that does not affect functionality.
I believe the issue is that you clicked on the back button (left arrow at the top right). You should have clicked on the checkmark icon on the top right.

@KalleHallden For this use case that @dinurymomshad shared, we may need a 'confirmation dialog' when back button is pressed. Something like "Your workout is not saved. Are you sure?"

Hah, was wondering what that button was for. Thanks @ckelwin

@dinurymomshad  Safe to close this issue then?


tmt.Tree().plans() fails with Assertion error, missing context_object

$ipython3
Python 3.9.13 (main, May 24 2022, 21:28:44)
In [1]: import tmt
In [2]: tmt.Tree().plans()
AssertionError                            Traceback (most recent call last)
Cell In[2], line 1
----> 1 tmt.Tree().plans()
File /usr/local/lib/python3.9/site-packages/tmt-1.19.0-py3.9.egg/tmt/base.py:2141, in Tree.plans(self, keys, names, filters, conditions, run, links, excludes)
2138     sources = None
2140 # Build the list, convert to objects, sort and filter
-> 2141 plans = [Plan(node=plan, run=run)
2142          for plan in [
2143              *self.tree.prune(keys=local_plan_keys, names=names, sources=sources),
2144              *self.tree.prune(keys=remote_plan_keys, names=names, sources=sources),
2145     ]]
2147 plans = self._filters_conditions(
2148     sorted(plans, key=lambda plan: plan.order),
2149     filters, conditions, links, excludes)
2150 if Plan._opt('shallow'):
File /usr/local/lib/python3.9/site-packages/tmt-1.19.0-py3.9.egg/tmt/base.py:2141, in (.0)
2138     sources = None
2140 # Build the list, convert to objects, sort and filter
-> 2141 plans = [Plan(node=plan, run=run)
2142          for plan in [
2143              *self.tree.prune(keys=local_plan_keys, names=names, sources=sources),
2144              *self.tree.prune(keys=remote_plan_keys, names=names, sources=sources),
2145     ]]
2147 plans = self._filters_conditions(
2148     sorted(plans, key=lambda plan: plan.order),
2149     filters, conditions, links, excludes)
2150 if Plan._opt('shallow'):
File /usr/local/lib/python3.9/site-packages/tmt-1.19.0-py3.9.egg/tmt/base.py:1043, in Plan.init(self, node, run, skip_validation, raise_on_validation_error, **kwargs)
1039 # Expand all environment and context variables in the node
1040 with tmt.utils.modify_environ(self.environment):
1041     self._expand_node_data(node.data, {
1042         key: ','.join(value)
-> 1043         for (key, value) in self._fmf_context().items()})
1045 # Initialize test steps
1046 self.discover = tmt.steps.discover.Discover(
1047     plan=self, data=self.node.get('discover'))
File /usr/local/lib/python3.9/site-packages/tmt-1.19.0-py3.9.egg/tmt/base.py:1184, in Plan._fmf_context(self)
1182 """ Return combined context from plan data and command line """
1183 combined = self.context.copy()
-> 1184 assert self._context_object is not None  # narrow type
1185 combined.update(self._context_object.fmf_context)
1186 return combined
AssertionError:
even though I can do tmt plans ls or tmt plans show without issues.
I have tmt from git main branch.

A fix for this particular issue is trivial, https://github.com/teemtee/tmt/pull/1747
The question is, is this use case supported? How much is tmt package supposed to be usable as an importable library? There might be - there are - other places where the existence of CLI "context" object is assumed.

We got to it with @psss when debugging trying to create tests for some clickable_urls. As this works fine for tests and stories I would expect also plans to work the same.

Riiight, importing tmt bits from tests does indeed make sense :)


Vis custom colors, bug fixes

Closes https://github.com/datavisyn/reprovisyn/issues/458
https://github.com/datavisyn/reprovisyn/issues/800
https://github.com/datavisyn/reprovisyn/issues/949
https://github.com/datavisyn/reprovisyn/issues/976
Developer Checklist (Definition of Done)
Issue

[ ] All acceptance criteria from the issue are met
[ ] Tested in latest Chrome/Firefox

UI/UX/Vis

[ ] Requires UI/UX/Vis review

[ ] Reviewer(s) are notified (tag assignees)
[ ] Review has occurred (link to notes)
[ ] Feedback is included in this PR
[ ] Reviewer(s) approve of concept and design

Code

[ ] Branch is up-to-date with the branch to be merged with, i.e., develop
[ ] Code is cleaned up and formatted
[ ] Unit tests are written (frontend/backend if applicable)
[ ] Integration tests are written (if applicable)

PR

[ ] Descriptive title for this pull request is provided (will be used for release notes later)
[ ] Reviewer and assignees are defined
[ ] Add type label (e.g., bug, feature) to this pull request
[ ] Add release label (e.g., release: minor) to this PR following semver
[ ] The PR is connected to the corresponding issue (via Closes #...)
[ ] Summary of changes is written

Summary of changes

Adding selection to violin plots
Adding filter in/out/clear buttons to bar charts and violin plots
Fixing bug that threw plotly error in console
Removing color from bar chart except when grouped
Added custom color options to all columns
Improved display of descriptions for columns in the sidebar

Screenshots
Additional notes for the reviewer(s)

Thanks for creating this pull request 🤗

This PR can be merged once https://github.com/datavisyn/visyn_core/pull/36 is merged.


MultiStepper Arduino example

The AccelStepper Arduino library is able to group stepper motors together and move them in sync. We should explore this feature.
Have a look at this example on how to set things up.

We managed to move multiple stepper at once and updated the example. We should really test the code with all 6 stepper motors connected.

With old drivers, Multistepper was not ideal since it does not support acceleration, which turns out to be essential for some movements (especially the ones involving the shoulder).
Maybe we can give it another try with the new TB6560 drivers?


p2p: update protocol magic bytes

Each network (mainnet, testnet, regnet) needs to get their protocol magic bytes updated to unique Navcoin values.
Ideally they should not be equal to other bitcoin-based networks, but for the sake of simplicity, they can be set randomly.

So, this is pchMessageStart in src/chainparams.cpp.
As this is a change in the network protocol, we'll also need to support the old values (here and perhaps somewhere else) until old versions are phased out

Ideally they should not be equal to other bitcoin-based networks, but for the sake of simplicity, they can be set randomly

Random values are good enough — 4 bytes is too much entropy for any collision to occur, realistically speaking. One caveat is that the randomness should be good (ran this on an i7-3615QM with RDRAND support):
$ hexdump -n 12 -e '4/1 "%02x " "\n"' /dev/random
11 56 a6 9d
05 c9 85 bd
89 a7 7f 85

Thanks Ilya for your observation and your careful approach. In our specific case we don't need to keep backwards compatibility with old nodes as we are starting a new chain. And essentially, we want to make old clients incompatible with the new one so their interactions are prevented.

Since the code changes for this were already merged, I think we should be closing this issue?


Fix issue where toolbox successResponses is stripped

Fixed a bug wth successResponses similar to #228

Signed CLA

Thanks, @mahwy!


GitHub API Integration Issue - Content Encoding Requirements Mismatch

2 days ago this was working just fine, and now I keep on encountering errors when I try to create, edit, push new files on Github. I don't know what could've changed since then, but I double checked to make sure the 'Claude_desktop_config.json' file was correct, as well as the API token settings on Github, and all is the exact same as it was 2 days ago. Any suggestions are welcome. Thanks in advance!
Bug Report:
Issue Description:
The create_or_update_file function in the GitHub API integration is failing due to a mismatch between the function schema and GitHub's API requirements for file content encoding.
Error Message:
CopyError executing code: MCP error -32603: Invalid arguments: content.encoding: Required, content.content: Required
Current Implementation:
The function schema currently accepts content as a simple string:
json
{
  "content": {
    "description": "Content of the file",
    "type": "string"
  }
}

Required GitHub API Format:
GitHub's API requires content to be provided with explicit encoding information:
json
{
  "content": {
    "encoding": "base64",
    "content": "base64_encoded_string"
  }
}

Reproduction Steps:
python
create_or_update_file(
    path="test.txt",
    repo="job-hunter-test",
    owner="Gonzo3030",
    branch="main",
    content="Test content",
    message="Test commit"
)

Expected Behavior:
The function should automatically handle base64 encoding and structure the content object according to GitHub's API requirements.
Impact:
This issue prevents any file creation or updates via the GitHub API integration, which was working previously (as evidenced by successful commits on November 30, 2024).

same error here . hope this to get resolved soon

Hi, I'm unsure how to test this locally, but I think a minor change fixes this issue.
Opened PR >> https://github.com/modelcontextprotocol/servers/pull/222

Sorry guys, I thought the issue was resolved somehow, but then I noticed Claude just decided to use push_files instead of create_or_update_files and then it works... My last PR didn't solve the issue correctly.
I've opened a new one that I think does.. The Github response from that call has a different structure than
the zod validator on your side >>
https://github.com/modelcontextprotocol/servers/pull/316
^^ Just updated the interface.


Add new page for kernel-level constraints

Fixes #39601
Add a new concept page that documents and compares the available kernel-level security constraints for Pods and containers

Where content was pulled from different pages, I've added comments. That content is verbatim, no grammar or style changes.
There are several outstanding TODOs that block merging
The Security Checklist page  has smaller conceptual sections about seccomp apparmor and SELinux that we can remove, making the checklist more streamlined. Haven't done that yet
I used an HTML table because I wanted to wrap the lines

What's needed?

Review the content for accuracy
Address outstanding TODOs
Identify any other pages in the doc set that need to link to this page

/sig docs
/sig security
/language en
/wip
/cc @sftim @pjbgf @tallclair

My first reaction to this PR is that we may be placing the content under the wrong directory.
Not all users care about kernel level settings or constraints. Even they do care, their role might be the cluster administrator or a similar role who can manage node level configurations.
It may be okay to link to this level of details from the concepts section, but the contents themselves look to me more like cluster administration tasks. As an regular user, I sometimes cannot do a thing at this layer.

kernel level settings or constraints

That sounds like a (new) reference page to me. Maybe under https://kubernetes.io/docs/reference/node/?

@tengqm @sftim yeah good points. It doesn't really have a ton of reference information (unlike, say, a page that lists the exact dropped capabilities in the default seccomp profile). But it's more fitting in the reference directory!
(As an aside, I dream of seeing the TOC organized by the goal, not by DITA category - so "Secure" being a section, with the security pages there and broken into sub-goals like "Use ServiceAccounts to give an identity to Pods". That'd be a massive undertaking though so I doubt it'd happen)

(As an aside, I dream of seeing the TOC organized by the goal, not by DITA category - so "Secure" being a section, with the security pages there and broken into sub-goals like "Use ServiceAccounts to give an identity to Pods". That'd be a massive undertaking though so I doubt it'd happen)

I did once try that as a proposed revision to https://kubernetes.io/docs/tasks/
Lots of work and hard to make (IMO) other than as a big-bang, size/xxl change.

It makes more sense to me as a reader. I want to do the thing > I learn what the thing is > I learn how to do the thing. I think it's the kind of change that would need tech writer support from CNCF eh?

@shannonxtreme
Are you actively working on these changes?

I am, but I'm on holiday and will only be back at it in January, after the 15th

I have pending TODOs that I don't know how to resolve:

Confirm that Privileged containers ignore AppArmor profiles
Confirm how privileged containers interact with SELinux
Need a sample CVE that used the mount(2) syscall

SIG Node and SIG Security folks should be able to give advice here. At least I hope so.

Confirm that Privileged containers ignore AppArmor profiles

This is effectively done by the container runtime. Both cri-o and docker fallback to unconfined when the given container is privileged. AFAIK, this is pretty consistent across runtimes.

Confirm how privileged containers interact with SELinux

I believe this is also the case, example would be docker or podman's documentation:

A privileged container turns off the security features that isolate the
container from the host. Dropped Capabilities, limited devices, read-only mount
points, Apparmor/SELinux separation, and Seccomp filters are all disabled.

Hello @shannonxtreme, Good day! We want to merge this sooner rather than later. Could you please rebase this PR so we can proceed with a second round of docs and tech reviews?

uh oh, I messed something up in the push

uh oh, I messed something up in the push

https://xkcd.com/1597/

Lol, okay we're good now

@shannonxtreme if you fix https://github.com/kubernetes/website/pull/43214#discussion_r1548172622 then I think this'll be good to merge; all the other feedback is much less important.

/remove-language ja

Just a lil bump

Can we merge this without incorporating the remaining nits? My only question is for the comments in markdown that say where the original content in some sections came from verbatim - is that helpful for localization or should I remove the comments before merge?

Yes; nits are (kind of) defined as things that don't block a merge. This PR is awaiting approval.

/approve


Support musl-libc

Dart has no official support for musl-libc.
However, it turns out the SDK can be in fact be built against musl-libc when not using tcmalloc. To provide the support we will have to build our own SDK and then build dart-sass-embedded.
Stay tuned!

Support will land in next release!

1.58.0 is now available.


fix(docs): Updated the documentation on using local workflow

Why:
Closes: #19023

What's being changed (if available, include any code snippets, screenshots, or gifs):
The documentation on referencing local workflow file to the repository is updated in more than one location in a resuable content snippet. (See modified files).
The changes emphasizes the relative path to the checkout location of the repo, while referencing the workflow as suggested in comment
Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

@cmwilson21 - Any leads on the review? I see it is still in waiting stage. Just checking.


Add version 0.14 to readme

As part of the post-release process, we add the new version 0.14 to readme.
Note: this should only be merged after the release of torchvision 0.14.

BTW since we expect to release tonight, I think it's fine to merge it now - but it's up to you :)

Thanks @NicolasHug

When we merge this PR after the release, this happens: the current README on PyPI is the readme from 0.12 (instead of 0.13!). This is because the wheels that were updated on PyPI were built before the PR was merged, and thus were relying on the "old" version of the readme.

This is a good point, I will merge now (shortly before release), hopefully PyPI use 0.14 later.


alphametics: optimise implementation for last test

Don't work on this issue until #895 is merged, or use that PR as a base branch.
The last test currently takes > 30s to complete. When fixed, replace test.skip with xtest.

Addressed in PR 935.

Addressed in PR 935.


Namespaced pages are not decorated

Whichever namespace display mode is active, a namespaced page is not currently decorated with a reference count.
Environment

Extension version 1
Roam 0.9.8-5a7c150e
Safari

Examples

Minimal
Abbreviated
Full

Thanks, i had not tested namespace display modes! It will be fixed in v.2.

I just saw this happening in my graph - thanks for implementing it.


Fix typo in entrypoint folder

Changes
Fix typo in entrypoint folder
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Includes tests (if functionality changed/added)
[x] Includes docs (if user facing)
[ ] Commit messages follow commit message best practices
[ ] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
NONE

Hey Yawen, thanks for the fix! The change looks good, there's just a couple things we need to do before we can merge this:

Add a release notes section. In this case, since there are no changes to report in the release notes, I've just edited your PR description to add a release-note block.

 To do this from your terminal, in the branch where you're making this change, see the "Squashing Commits" section of https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History

Let me know if you have any trouble and I can try to help in either case.

/ok-to-test

Oh we'll also want a more descriptive PR title than "Typo" -- your change description in the PR body ("Fix typo in entrypoint folder") would make a good PR title.
(This is actually also related to commit squashing -- when a PR includes multiple changes GitHub chooses the branch name for the PR title, which tends to be pretty non-descriptive. When there's only one squashed change, GitHub chooses that commit description for the PR title, which is usually much better)

Thanks for the comment. Edited the commit based on them

/kind documentation

/lgtm

/lgtm
/cc @chmouel

/lgtm
Looking Good! 🤙🏽

/test check-pr-has-kind-label

kind/documentation

I still have check-pr-has-kind-label marked as yellow but it already has a kind tag.

My checks were stuck, so I tried pushing a empty commit to re-try the checks to see if it fixes it.

/lgtm

/assign @imjasonh

/approve
🎉


[pkg/spec] Update spec packaging for tflite layer

Update spec packaging for tflite layer with tflite dependency
Self evaluation:

Build test: [x]Passed [ ]Failed [ ]Skipped
Run test: [x]Passed [ ]Failed [ ]Skipped

Signed-off-by: Parichay Kapoor<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #1201. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnstreamer.mooo.com/.


Allow push/pull through to underlying grit object

The current grit_adaptor breaks automatic pulls/pushes using the method described at https://github.com/gollum/gollum-lib/issues/12#issuecomment-24854800
This pull request allows push/pull through to the underlying Grit::Git object.

As  this is currently not merged, we're in the position of having to push using a cron job which is a bit nasty.  Is there a way to do what this pull request does, but in config.ru or a custom app.rb until such times as this is accepted and released?

Closed this in favor of https://github.com/gollum/grit_adapter/pull/10. Functionality is merged now, sorry for the wait!

Released in version 1.0.0 of this gem.


Layer Display broken with DisplayLayerProgress 1.19.1

Same here.

Sorry guys about this. I'm in conversations with the developer of the DisplayLayerProgress plugin here https://github.com/OllisGit/OctoPrint-DisplayLayerProgress/issues/136.
BTW, are you using OctoPrint-OctoPod plugin? Depending on what the developer of the plugin answers I might need to require the user of OctoPrint-OctoPod plugin to see layer information. A lot of users will basically lose seeing layer information if we go this way since not everyone uses OctoPrint-OctoPod plugin.

BTW, are you using OctoPrint-OctoPod plugin?

Yes, I am.

I am also using Octopod Plugin.

For all interested, here's a simple workaround until this is fixed:
In settings for "State", set to [current_layer] / [total_layers] like so:

What you end up with in OctoPod:

...and in OctoPrint:

(not ideal long-term, but totally fine by me for the time being)
@gdombiak Thank you for continuing to develop and support OctoPod! I use it religiously for my remote printing/monitoring needs. It's wonderful.

Thanks @sschwartzman. You are spot on, that is another workaround this issue. Thanks for sharing!!!

You asked if I wanted to beta test in the AppStore. Please tell me how.

Hey @JaySea77, good to see you here.  You will need to follow these steps:

Install plugin https://github.com/OllisGit/OctoPrint-DisplayLayerProgress/releases/download/1.20.0dev/master.zip. This will replace the version that you have with the new version that will be released. This version requires you to go to Settings and enable WebSocket-Communication. I asked the developer of the plugin to have that enabled by default for the final release
Install TestFlight app on your iPhone/iPad if you do not have it already installed. This is how Apple let's you install beta versions of applications
Open https://testflight.apple.com/join/Pq7JqNCx to accept installing Beta version of OctoPod
If you installed OctoPod in your Apple TV then you will need to also install TestFlight on your Apple TV and from there install the beta version of OctoPod

Let me know how it goes and if things are working fine or not.
Thanks,
Gaston

Thanks, the app now shows the layer again. Will try it with a print tomorrow.

Great to hear that @JaySea77. Thanks for helping test the new version and confirming that things are working. Let me know if you ran into something that needs fixing.
Gaston

The dev version of DisplayLayerProgress and the OctoPod app from TestFlight, work great!

New version of the plugin is out. Ready to submit new version of OctoPod to the App Store.


Add to PackageControl

PackageControl is the de-facto way to install ST2/3 packages.
I would like to suggest that this package be added to their repository. Instructions on how to do that can be found here: https://packagecontrol.io/docs

I'd llike to second this even though it's ages old. The instructions for installing on the main page are also out of date as they don't work on current builds of sublime3.

Here here


Current user has insufficient permissions to perform this operation

Category

[x] Question

Question
I tried to install SharePoint starter kit v2. It was NOT possible to use the tenant admin user<EMAIL_ADDRESS>because I've already activated MFA. I tried to use another user which already had administrator privileges.
Although some webparts have been installed , during the installation process I encountered below error

Invoke-PnPTenantTemplate : The current user has insufficient permissions to perform this operation.

Please tell me , what kind of permissions do I need to perform this command ?

Did you add this second use as a site collection admin directly to the app catalog site collection?

@eoverfield thanks for your response, Yes I've already added second user to a site collection administrators group.
The authenticated user which I perform that commands , has a site collection admin permission.

I am having the same issue. I have even gone as far as granting the provisioning user, administrator rights to all office products, i.e., Exchange, Global, SharePoint. etc.

It is possible this is being thrown when the term set is being provisioned.
https://github.com/pnp/sp-starter-kit/blob/v3/documentation/common-provision-results.md#error-term-set-permissions-required


ModuleNotFoundError: No module named '_testcapi'

from py_vollib.black_scholes_merton import black_scholes_merton
raises
ModuleNotFoundError: No module named '_testcapi'
Python 3.11.7
py-vollib               1.0.1
Issue mentioned elsewhere:
https://github.com/vollib/py_vollib/issues/11
https://github.com/vollib/py_vollib/issues/20
Is this issue still a known problem with the pip package?

What finally worked for me, as of April 2024, was to install both py_vollib AND py_lets_be_rational from github rather than PyPI.
When they said it was fixed in Github in issue 11, I'm pretty sure they meant it was fixed in py_lets_be_rational. Even if you install py_vollib from github, it seems pip will still grab py_lets_be_rational from PyPI, so you have to install that from Github first.
pip install git+https://github.com/vollib/py_lets_be_rational.git
pip install git+https://github.com/vollib/py_vollib.git

from py_vollib.black import black
flag = 'c'  # 'c' for call, 'p' for put
S = 95  # price of the underlying
K = 100  # strike
t = .2  # annualized time to expiration
r = .2  # interest-free rate
sigma = .2  # implied volatility
black(flag, S, K, t, r, sigma)
1.4739294832475103


feat: sending email with services

Issue link
closes: #
relates: #5
What does this PR do?
(Optional) Additional Contexts for PR Reviews

24-03-19 15:05:19 git/6ow3idGirl [feat/5/brevo] % npm run start

><EMAIL_ADDRESS>start
> nest start

[Nest] 74731  - 03/19/2024, 3:05:24 PM     LOG [NestFactory] Starting Nest application...
[Nest] 74731  - 03/19/2024, 3:05:24 PM     LOG [InstanceLoader] HttpModule dependencies initialized +6ms
[Nest] 74731  - 03/19/2024, 3:05:24 PM     LOG [InstanceLoader] AppModule dependencies initialized +1ms
[Nest] 74731  - 03/19/2024, 3:05:24 PM     LOG [RoutesResolver] AppController {/}: +2ms
[Nest] 74731  - 03/19/2024, 3:05:24 PM     LOG [RouterExplorer] Mapped {/, GET} route +1ms
[Nest] 74731  - 03/19/2024, 3:05:24 PM     LOG [RouterExplorer] Mapped {/healthz, GET} route +0ms
[Nest] 74731  - 03/19/2024, 3:05:24 PM     LOG [RouterExplorer] Mapped {/mail, POST} route +1ms
[Nest] 74731  - 03/19/2024, 3:05:24 PM     LOG [NestApplication] Nest application successfully started +1ms
GET /healthz 200 2.399 ms - 15
{
  sender: { email<EMAIL_ADDRESS>name: 'hwakabh' },
  to: [ { email<EMAIL_ADDRESS>name: 'admin' } ],
  subject: '[Brevo] test mail',
  textContent: 'This is a test mail body.'
}
{ messageId<EMAIL_ADDRESS>}
POST /mail 201 2886.526 ms - 63


GitHub: An invalid PAT should surface a user friendly error

Description
If a GH PAT is not valid, an actionable user friendly error should be surfaced.
Reproduction Steps
export ADO_PAT="VALID_PAT"
export GH_PAT="1234"
gh ado2gh migrate-repo --ado-org "valet-testing" --ado-team-project "build-playground" --ado-repo "forecast-regression-test" --github-org "import-testing" --github-repo "build-playground-forecast-regression-test"
Will output the following:
[2023-10-12 10:29:39] [INFO] You are running the latest version of the ado2gh CLI [v1.2.0]
[2023-10-12 10:29:39] [INFO] ADO ORG: valet-testing
[2023-10-12 10:29:39] [INFO] ADO TEAM PROJECT: build-playground
[2023-10-12 10:29:39] [INFO] ADO REPO: forecast-regression-test
[2023-10-12 10:29:39] [INFO] GITHUB ORG: import-testing
[2023-10-12 10:29:39] [INFO] GITHUB REPO: build-playground-forecast-regression-test
[2023-10-12 10:29:39] [INFO] Migrating Repo...
[2023-10-12 10:29:40] [ERROR] Failed to lookup the Organization ID for organization 'import-testing'

A 401 error was surfaced in the logs:
2023-10-12 10:29:05] [ERROR] OctoshiftCLI.OctoshiftCliException: Failed to lookup the Organization ID for organization 'import-testing'
 ---> OctoshiftCLI.OctoshiftCliException: Unauthorized. Please check your token and try again
 ---> System.Net.Http.HttpRequestException: GitHub API error: {"message":"Bad credentials","documentation_url":"https://docs.github.com/graphql"}
 ---> System.Net.Http.HttpRequestException: Response status code does not indicate success: 401 (Unauthorized).
   at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()

I haven't looked on how errors are surfaced in Octoshift, and I know each provider has its own set of error codes for different errors, but it would be really nice to surface a user friendly error that shows the correct perms needed!

Echoing this, I had to dig a little to find the verbose flag. I'll stick up a PR to at least suggest that on this failure.


Adding 1-26 support in dev

Issue #, if available:
Description of changes:
1-26 dev bundles

Should there be changes in generatebundlefile/hack/release_staging.sh and release_prod.sh?

Should there be changes in generatebundlefile/hack/release_staging.sh #2, and #3 and some places in release_prod.sh?
Edit: adding links

Yea I'm going to add staging/production in another PR once we can run a few 1.26 e2e tests with the Dev bundles.

/hold

/unhold


Extensions

Hi @kchemorion
How to persist installed extension after exiting and re-launching Slicer. The installed extensions disappear after re-launch.
Thanks
Sameer

Hi @SameerShanbhogue ,
Thanks for reaching out. If you want the extensions to persist then you need to persist the configuration found at: /root/.config/NA-MIC/Slicer.ini. Let me know if this works.