Error: This does not seem to be a WordPress installation

I'm having issues with WP-CLI 2.4.0 using ddev version v1.17.0-alpha4 on Apple M1, not sure if this is M1 related, though.
I created a new WordPress project and installed WordPress via web installer. Both frontend and backend work fine under https://wordpress-demo.ddev.site/. Executing ddev wp in ~/DDEV/wordpress-demo works fine, it shows all available WP-CLI commands, but as soon as I call a specific command it shows an error, e.g.
➜ ddev wp core version
Error: This does not seem to be a WordPress installation.
Pass --path=`path/to/wordpress` or run `wp core download`.
Failed to execute command wp core version: exit status 1

I also tried executing the command from ~/DDEV/wordpress-demo/htdocswhich is where WordPress is located, as well as passing the path like so --path="~/DDEV/wordpress-demo/htdocs" and so --path="/Users/nick/DDEV/wordpress-demo/htdocs", both return the same error.
And this didn't work either 😱
➜ ddev wp core download
Error: Failed to get url 'https://api.wordpress.org/core/version-check/1.7/?locale=en_US': cURL error 28: Connection timed out after 10004 milliseconds.
Failed to run wp core download: exit status 1

Wondering if others experience problems with WP-CLI, too?
Oh yeah, and I tried the fix from issue https://github.com/drud/ddev/issues/1462, too. Doesn't make any difference.

So to simplify things, just ddev ssh and use the wp command there until you have things working. ddev wp is just a wrapper that runs that. So while you're debugging, do that. Obviously if you're unable to access api.wordpress.org, that's nothing to do with wp, but rather your networking or their server.
For pathing, you have to be thinking inside the container. Where everything starts with /var/www/html. So definitely start with ddev ssh and get wp doing what you want in there, and then you'll be ready to use ddev wp later.

From inside the container the wp commands work, although I'm still getting the "unexpected error" that "WordPress could not establish a secure connection to WordPress.org". When I ping wordpress.org from outside the container, it works, but not from inside. And not only wordpress.org, but any domain I ping from the inside.
In addition to that there's various PHP warnings and notices, here's the complete output:
nick@wordpress-demo-web:/var/www/html/htdocs$ wp plugin list
PHP Warning:  An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the support forums. (WordPress could not establish a secure connection to WordPress.org. Please contact your server administrator.) in /var/www/html/htdocs/wp-includes/update.php on line 408
Warning: An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the support forums. (WordPress could not establish a secure connection to WordPress.org. Please contact your server administrator.) in /var/www/html/htdocs/wp-includes/update.php on line 408
PHP Notice:  Trying to access array offset on value of type null in phar:///usr/local/bin/wp-cli/vendor/wp-cli/extension-command/src/Plugin_Command.php on line 662
Notice: Trying to access array offset on value of type null in phar:///usr/local/bin/wp-cli/vendor/wp-cli/extension-command/src/Plugin_Command.php on line 662
PHP Notice:  Trying to access array offset on value of type null in phar:///usr/local/bin/wp-cli/vendor/wp-cli/extension-command/src/Plugin_Command.php on line 663
Notice: Trying to access array offset on value of type null in phar:///usr/local/bin/wp-cli/vendor/wp-cli/extension-command/src/Plugin_Command.php on line 663
PHP Notice:  Trying to access array offset on value of type null in phar:///usr/local/bin/wp-cli/vendor/wp-cli/extension-command/src/Plugin_Command.php on line 662
Notice: Trying to access array offset on value of type null in phar:///usr/local/bin/wp-cli/vendor/wp-cli/extension-command/src/Plugin_Command.php on line 662
PHP Notice:  Trying to access array offset on value of type null in phar:///usr/local/bin/wp-cli/vendor/wp-cli/extension-command/src/Plugin_Command.php on line 663
Notice: Trying to access array offset on value of type null in phar:///usr/local/bin/wp-cli/vendor/wp-cli/extension-command/src/Plugin_Command.php on line 663
+---------+----------+--------+---------+
| name    | status   | update | version |
+---------+----------+--------+---------+
| akismet | inactive | none   | 4.1.8   |
| hello   | inactive | none   | 1.7.2   |
+---------+----------+--------+---------+

It sounds like you have some network problems. Are you behind a proxy or a VPN?  Perhaps it's a work environment where they have a man-in-the-middle https inspection routine?  Do you have a way to turn off these features? If not, you'll have to do to the web image whatever is required of your work computer.
I have no trouble doing curl -L https://wordpress.org from inside the web container.

I'm working from home. macOS firewall disabled and no other firewalls that I know of. If there were, I shouldn't be able to ping or curl https://wordpress.org from outside the container, should I?
Maybe it's a bug with my docker preview version? Will try upgrading to Docker Desktop preview 3.1.0 (60984) from February 11, 2021.

Just read the following in the release notes 😅

The host.docker.internal and vm.docker.internal DNS entries now resolve.

I tested on a mac M1. host.docker.internal doesn't have to do with what you're facing.  But the release notes explain how to set up with it anyway.

Upgrading to the latest preview version solved the connection issue.
nick@wordpress-demo-web:/var/www/html$ ping wordpress.org
PING wordpress.org (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from wordpress.org (<IP_ADDRESS>): icmp_seq=1 ttl=46 time=114 ms
64 bytes from wordpress.org (<IP_ADDRESS>): icmp_seq=2 ttl=46 time=112 ms
64 bytes from wordpress.org (<IP_ADDRESS>): icmp_seq=3 ttl=46 time=116 ms

Hence this now also works
nick@wordpress-demo-web:/var/www/html/htdocs$ wp plugin list
+---------+----------+--------+---------+
| name    | status   | update | version |
+---------+----------+--------+---------+
| akismet | inactive | none   | 4.1.8   |
| hello   | inactive | none   | 1.7.2   |
+---------+----------+--------+---------+

Thanks for your great support, very much appreciated!

Glad it's working for you! Happy to continue the conversation here or elsewhere. Closing this for now.


Powershell command example ignored VM HyperV Generation

$image = New-AzImageConfig -Location $location -SourceVirtualMachineId $vm.Id

The source VM might be v2, which should be this case.
$image = New-AzImageConfig -Location $location -SourceVirtualMachineId $vm.Id -HyperVGeneration V2

Is there any way to get HyperV Generation from $vm?

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

ID: 7d299c34-ffe1-b930-bace-f43c8d8217ca
Version Independent ID: b9eab64c-51a9-ad18-705c-15e553e0b2fe
Content: Create a managed image in Azure - Azure Virtual Machines
Content Source: articles/virtual-machines/windows/capture-image-resource.md
Service: virtual-machines-windows
Sub-service: imaging
GitHub Login: @cynthn
Microsoft Alias: cynthn

@WenceyWang -
Thanks for brining this to our attention. We will investigate it further and update you shortly.

@WenceyWang -
Thanks for brining this to our attention. We will investigate it further and update you shortly.

@WenceyWang -Have you tried using Get-AZVM or Get-AzOSDisk.

@WenceyWang -Have you tried using Get-AZVM or Get-AzOSDisk.

@WenceyWang - Please try the above suggested commands and if that helps.
At this moment, Since there is no doc update required, We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

@WenceyWang - Please try the above suggested commands and if that helps.
At this moment, Since there is no doc update required, We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Promote SLSAv1.0 offering of Chains format to beta

Since SLSAv1.0 was released, Chains provided support for it starting with provenance format slsa/v2alpha2. At this point, it is slsa/v2alpha4 (which includes support for StepActions and StepResults).
We propose stabilizing this to a Beta version: v2beta1 so that there is reduced immediate breaking changes and our users can adopt it more.
Here, I highlight some missing items:

Implement support for Tekton Artifacts. The final PR is under review and we can introduce support for it in Chains right after.
Identify the name of the pipelineTask/pipelineRun/taskRun/Step using the remote resource (Pipeline, Task, StepAction) in the resolved dependencies and byProducts. This will help with completeness.
Capture the origin of a remote StepAction (i.e. uri and digest) in the resolved dependencies: https://github.com/tektoncd/pipeline/pull/8106

cc @lcarva @renzodavid9

@renzodavid9 please add any other items here that I may have missed.

With https://github.com/tektoncd/pipeline/pull/8106 merged we can implement last point from https://github.com/tektoncd/chains/issues/1160#issue-2417114302, I'll take a look an open a PR for it

@chitrangpatel @renzodavid9
I'll work on this part

Identify the name of the pipelineTask/pipelineRun/taskRun/Step using the remote resource (Pipeline, Task, StepAction) in the resolved dependencies and byProducts. This will help with completeness.


Footer css

Issue reference:
Fixing Small Css Issue of Footer
Proposed changes:

Change the icon color of all footer icons to var(--clr-primary-5)
Change the text color of the footer links and the bottom-most text to var(--clr-grey-6)
Apply hover effect on the footer links: Change text color to var(--clr-primary-5) on hover

Type of change:

[ ] New feature (non-breaking change which adds functionality)

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings

@sagnik2001 Please use prettier and format the files you changed. you can download the extension for it if you are using VS Code
Other than that, everything looks fine.

Hey @varunKT001 I used the prettier and it adds a space between the files(footer -styles.js) will it be ok??

Yes, totally fine. It's following the prettier configuration file .prettierrc so no issues 👍

Done

You have also formatted the constants.js file, right?

yes its already been using prettier so no additional changes

Okay then 👍
Thanks for contributing 🎉


Please add a light theme

Hello,
currently ConnectBot only has a dark theme.
Would there be any chance you could also add a light theme?
It would be much appreciated.
Regards

You can see some guidelines for a light theme in the Google Material Design guidelines over there:
https://www.google.com/design/spec/style/color.html#color-themes
Regards

PS:
When the light them is in use, the FG and BG colors for the terminal should also be inverted by default of course. So, FG should be black and BG should be white.
Regards

Switching themes at runtime is problematic.

@kruton wrote:
Switching themes at runtime is problematic.

Why?
There are several other (open source) apps which allow to switch between dark and light themes, like for example Amaze File Manager, TextSecure, spaRSS, Kore, OsmAnd, primitive ftpd and probably many many more...
None of those have issues switching the theme while the app is running AFAICT.
You might want to have a look at Amaze File Manager, as the theme switching is working really nice in it.
Anyway, even if the theme switching would cause problems, which it obviously shouldn't as Amaze File Manager proves, then you could simply add a disclaimer to the option, which tells the user that this option requires a restart of the app and/or prompt the user to restart the app.
Regards

I've just implement a Light/Dark in one of my applications.
I had problems using it before setContentView(). It seems preferable to use it before onCreate().
  protected void onCreate( Bundle savedInstanceState )
  {
    if(setup.useLightTheme())
      setTheme(R.style.AppTheme_Light);
    super.onCreate(savedInstanceState);
  }

Any follow-ups for a light color theme?
On an e-ink device, dark background doesn't look right. I'm mainly talking about the main menu and settings menu, because the console itself can be set to light background anyway.


grouping and binary operator results differ between thanos vs prometheus engine

Query:
sum by (cluster, namespace, pod, container) (irate(container_cpu_usage_seconds_total{image!="",job="kubelet",metrics_path="/metrics/cadvisor", container="alertmanager"}[5m])) * on (cluster, namespace, pod) group_left (node) topk by (cluster, namespace, pod) (1, max by (cluster, namespace, pod, node) (kube_pod_info{node!="", pod=~"alertmanager-.*"}))

Results using thanos engine:

Results using prometheus engine:

As you can see the left and right side of the query is the same before and after but how the engine apply grouping results in different results.

Given that UI is missing some elements, I'm guessing that you are running an old Thanos version. Care updating to the newest one and testing again?

Adding fix here: https://github.com/thanos-io/promql-engine/pull/320. Will close this issue once the newer promql-engine is in Thanos.


fix(runtime-core): add if

Hi.
I have problems with the generated html using vue 3 and jsx.
some html tags are not painted correctly.
Can you add the code of @ConradSollitt?
https://github.com/vuejs/jsx/issues/141
Thanks.

This is the wrong fix. h only accepts 3 arguments. JSX implementations should generate code using createVNode.

Hi @yyx990803,
accepts more than 3 arguments when add .
I have an example using vue3 with htm with the problem.

@yyx990803,
Here you have a link with the example of the problem. I have to replace rc6 with the fix to see html correctly.
https://github.com/ivanheral/vue3_fix


add missing --no-confirm-changeset option

Why is this change necessary?
It is impossible to switch changeset confirmation off
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@fbeister You can turn it off by not supplying the option though. What's the use-case for strictly needing a flag?

If I don't supply the option, "confirm changeset" defaults to True (at least for the version I have) and there is no way to get a non-interactive mode.

Cross reference: https://github.com/awslabs/aws-sam-cli/issues/1600

@fbeister I don't think that is the intended behavior. What version are you running? Do you have a samconfig.toml file where confirm_changeset is set to True?
I do think have complementary flags is a good thing. I want to take a little time and think this completely through and run some cases through to make sure we don't regress or change behavior (especially with guided).

@fbeister I don't think that is the intended behavior. What version are you running? Do you have a samconfig.toml file where confirm_changeset is set to True?

Well, how do I put this, ...
confirm_changeset = true --- my bad :-D
I created this samconfig when I was starting to experiment with SAM and never came back to really look at it when it became my copy-and-paste blueprint for samconfigs to come. Let me try to remove this statement, then :roll_eyes:

@fbeister No worries. So I think there are a couple things here then.

We need to output when we are reading from the config. While this doesn't solve the issue, I think part of this is no communication was given that we were picking up the config. Giving the clue of, hey we are reading values from here, would have helped you realize something was happening 'magically'.
This pr.

I should have time today to do look at this one deeper.

Can this change be documented here? I just went on a goosechase looking for this option and only found this PR after implementing a hack and then deciding to create an issue (which now I don't have to do). TIL that the --help documentation is more up to date than the online documentation.
For anyone curious, here is my use case: I have a samconfig.toml file in my project that is intended for local deploy testing only (confirm changeset is as expected, etc), so confirm_changeset = true in that file. sam build cannot exclude files, so this config file goes into the build and when the build enters our CI/CD pipeline, sam deploy cannot override confirm_changeset = true without something like --no-confirm-changeset.


updated final

Hi Bry, we misse you today. Please send a 5 minutes screen recording of you explaining your final submission.
Also, there are some conflicts with your pull request. Could you please sync your remote branch with my dev branch, pull from VS code, commit again from your VS code to your remote branch and then create a new pull request please?
Thanks, let me know if you have questions.

Hi Nico,
Sorry I joined at the beginning there but I was on airport wifi and it kept crashing. I’ve synched my changes hopefully it works.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Nico Arellano @.>
Sent: Wednesday, December 20, 2023 1:37:29 PM
To: nicoarellano/reposarch @.>
Cc: brymcghee @.>; Author @.>
Subject: Re: [nicoarellano/reposarch] updated final (PR #381)
Hi Bry, we misse you today. Please send a 5 minutes screen recording of you explaining your final submission.
Also, there are some conflicts with your pull request. Could you please sync your remote branch with my dev branch, pull from VS code, commit again from your VS code to your remote branch and then create a new pull request please?
Thanks, let me know if you have questions.
—
Reply to this email directly, view it on GitHubhttps://github.com/nicoarellano/reposarch/pull/381#issuecomment-1865030123, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BCNT2CUBEUZZ3AJZUCBVNDLYKM47TAVCNFSM6AAAAABA5GLEE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRVGAZTAMJSGM.
You are receiving this because you authored the thread.Message ID: @.***>

No worries,
I hope your had a safe trip.
I'll take a look tomorrow, but it looks like everything was merged properly.
Please take a look to the course portal and let me know if you are missing anything.
You can keep pushing code until Friday if you need.
Happy holidays. Have a good break.


KTOR-6743 Add new tutorial "Create a websocket application"

KTOR-6743 Add a new tutorial "Create a WebSocket application" to replace the existing tutorial "Creating a WebSocket chat"
Preview on Staging

[x] add content
[x] add a sample project
[x] add code blocks and reference code from project where possible
[ ] add screenshots for light and dark theme
[ ] add links

@garthgilmourni I seem to have some import wrong in ApplicationTest.kt. Can you please check it?
Also, as this tutorial will replace "Creating a WebSocket chat" should the "Creating a Websocket chat client" also be removed?


Returning a response is forcing application/json content-type

What version of Elysia is running?
1.1.12
What platform is your computer?
No response
What steps can reproduce the bug?
I'm running a Vite dev server with bun + elysia, not sure if that is relevant BUT the issue is pretty strait forward:
My handler has code along these lines:
const r = new Response(html, { headers: { 'content-type': 'text/html' } });

// This logs out "_Response", which turns out to be important due to internal elysia handler logic
console.log(r?.constructor?.name);

return r;

Seems like response mapping depends on the constructor name property, and checks for "Response" here -> https://github.com/elysiajs/elysia/blob/main/src/handler.ts#L471.
This check does not pass, since in my setup it turns out to be "_Response".
Thus, it falls back to a instanceof check in the default handler, which does pass -> https://github.com/elysiajs/elysia/blob/main/src/handler.ts#L582-L587.
Problem is that logic doesn't return the response as-is - it forces an application/json content-type. Might make sense to pass response as-is and only set the content-type if not already present?
What is the expected behavior?
No response
What do you see instead?
No response
Additional information
No response
Have you try removing the node_modules and bun.lockb and try again yet?
No response

Fixed and published under 1.1.13 with test case included
see https://github.com/elysiajs/elysia/compare/1.1.12...1.1.13
If this doesn't fix the issue, feel free to tag me or reopen the issue.

Nice, the changes look like it should resolve it for sure, thanks!


32 bit support fails

Sparrow seems to hard-code that the underlying archiotecture is 64bit, see build.log in https://koji.fedoraproject.org/koji/taskinfo?taskID=121660160

It's more like the layout code is following the usual C++ container logic of assuming that container/arrays can't be bigger than what the native address space supports, therefore 32bit platforms have 32bit pointers and 32bit elements size value types. However ArrowArray impose 64bit sizes whatever the platform, and the difference is caught at compile-time when we attempt to move an iterator with an offset of 64bit type.
Reproducible on Windows (and probably all platforms) by trying to build for 32bit.


Plug leaks in RSA key imports

Error path of soter_rsa_{pub,priv}_key_to_engine_specific() does not free various BIGNUM components of RSA keys. This may cause memory leaks if OpenSSL fails to read or import key data. Use goto fail pattern to handle error path properly.
Also, add error handling for RSA_set0_key() and its siblings which may fail (though, it's very unlikely in our case).
Do this for both OpenSSL and BoringSSL backends, which are similar but not identical.
Also, avoid direct access to RSA fields in BoringSSL backend. Historically it was allowed by OpenSSL so BoringSSL keeps the fields accessible. However, direct access has been deprecated in favor of accessor functions. OpenSSL 1.1+ does not allow direct field access at all. Replace direct accesses in BoringSSL with functions too. (Here we change only functions immediately related to memory leaks. There are more direct accesses throughout the code base. They will be fixed later.)
This should resolve issues #514 and #515.

I'd wait for a review by @ignatk – our resident OpenSSL guru – before merging this.

@vixentael, uh... we can rename it into something less eerie. goto error, goto free, goto out, goto cleanup, etc. Do you like any of them?

Why you decided not to use BN_secure_new() for allocation?

@vixentael, uh... we can rename it into something less eerie. goto error, goto free, goto out, goto cleanup, etc. Do you like any of them?

my objections were not based on the naming itself, but rather on a pattern :))
but it's more a joke-like comment, i'm ok with general approach.

@outspace,

Why you decided not to use BN_secure_new() for allocation?

I just mimicked the existing code. I forgot about your comment about BN_secure_new() in #514.
I'm not sure that it will actually improve security because Themis keys (which we import into OpenSSL) are not encrypted in any way and are stored in regular heap. Sure, we can copy them into OpenSSL's secure heap, but they are still accessible by other means.
Moreover, BN_secure_new() is not available in OpenSSL 1.0.2 which is still supported. And I believe there are many more allocations which could make use of secure heap capabilities. I'd suggest to leave this out of scope of this PR. I've created issue #526 to track this.


I met issue

Thank you for nice module..
Can you address below issue?

Thanks for pointing it out. This came from a bad test after committing, it should be fixed.


Changed radiogroup color in dark-mode

Environment
"dependencies": {
"@gits-id/ui-nuxt": "^0.15.1"
},
"devDependencies": {
"nuxt": "3.0.0",
"sass": "^1.57.1",
"@nuxtjs/tailwindcss": "^6.2.0"
}
Reproduction
https://stackblitz.com/edit/github-ycbgbo-ptanzw?file=app.vue
Describe the bug
hi @gravitano
RadioGroup text color is not standard with other components.
it is #E5E5E5, while the other text color is black.

please make default
👍
Additional context
No response
Logs
No response

thank you @gravitano
solved, nice 👍


pcalg and kpcalg not installed in docker image

Hi. I am using the cdt GPU docker image (nv-cdt and nv-cdt-dev) to run a PC algorithm.
After importing the cdt in python3, I use print(cdt.utils.R.RPackages), and it shows that pcalg and kpcalg are not installed (showing False values).
This causes the failure of createing a PC() object with an error output:
ImportError: R Package (k)pcalg/RCIT is not available. RCIT has to be installed from
https://github.com/Diviyan-Kalainathan/RCIT
Plus: the cdt CPU docker image does NOT have this problem. Could you please update the GPU docker image ? Thx.

Did you manage to solve this issue? If yes, please assist. Thanks.

@shahdhardn Sorry, I didn't find a solution for this problem.
I used CPU version cdt docker instead.
I am waiting the authors of cdt to offer a solution.

Hello,
Sorry for the delay, I'll update the image ASAP
Best,
Diviyan

We had some CICD issues that are being solved, sorry for the wait !
We should be good soon !


Questions regarding the order independent transparency example

Hi,
In OIT (Order Independent Transparency) test, I noticed that the "early_fragment_tests" layout qualifier is being used in the shader "geometry.frag". However, the OIT test disables the depth test and stencil test. As a result, the early fragment tests may not function as intended.
Are there any other testing purposes associated with enabling the early fragment test?

Sadly can't help on this. The sample was an external contribution. If you think this is an error, a PR is very much appreciated.


Refactor filesystem with pathlib + improve CLI UX

08be4aa
This commit refactors the way we interact with the filesystem by replacing the os.path module with pathlib.Path. This makes the code more readable, easier to understand and less error-prone.
Key changes include:

Introduced a global variable, LOG_DB, to represent the path of the log database file. This eliminates the need for the get_log_db_path() function.
Replaced the os.path.exists checks with the Path.exists() method.
Replaced the os.path.expanduser calls and string concatenations for file paths with the / operator provided by pathlib.Path.
Used the Path.mkdir() method for directory creation.
Improved the formatting of string messages by using f-strings for more readability and flexibility in the future.
A helpful instruction has been added to the exception raised when no log database is found, guiding the user to run llm init-db, similar to the scenario when ~/.llm/log.db is absent and a chat history needs to be read.

These changes should improve the maintainability and readability of the code without altering the functionality.

9cb5224
This commit improves the CLI UX by adding the help text for no-arg scenarios; however, it preserves the pipe compatibility—the prompt can still be manipulated with --system.
Running llm without any arguments no longer causes the program to hang indefinitely.

974f9d2
Add a helper message for the logs command.
This will be displayed in the general --helper message.

I'm actively rewriting this code at the moment so I won't be able to merge this.


Fix ahistorical CTV BIP summary

To the extent that optech wishes to accurately reflect history of BIP development, the page is innacurate with respect to the CTV proposal's development.
The original publication was https://github.com/JeremyRubin/bips/blob/op-checkoutputshashverify/bip-coshv.mediawiki which describes the entirety of the summary.
I've noticed that this text is being cited as a true history, and I think it's wrong.

thanks for the fix!

Left some replies for @JeremyRubin, but I'm reasonably convinced at this point that our existing text is accurate.  That said, I don't think there's any reason for our ~300 word summary to mention any historical details besides the fact that the proposal used to be called COSHV.  I have work already scheduled for today and tomorrow, but I'll try to PR my own edit on Thursday.
Let's keep this PR open in the meantime to remind me that there's an outstanding issue.

I'll try to PR my own edit on Thursday.

See #1816

Closing in favor of https://github.com/bitcoinops/bitcoinops.github.io/pull/1816 which contains many more updates


move rx_boost and tx_boost to RadioKind config

This change simplifies the API and removes parameters that does nothing (ex tx_boost does not exist on sx126x). In the future this could be expressed as gain or whatever makes sense for the used module but to keep the scope of this PR small this will do for now.

One downside with this PR there will be no way to change the boost without recreating the whole LoRa struct but I think it is worth it. If we want to be able to modify this again we could expose the config trough a trait type and impl setters for the values that can be changed on the Config struct.

One downside with this PR there will be no way to change the boost without recreating the whole LoRa struct but I think it is worth it. If we want to be able to modify this again we could expose the config trough a trait type and impl setters for the values that can be changed on the Config struct.

Well, internally tx_boost just configures different output (see #192) and that is something that is defined by physical board layout. So in the end all we need is actually tx power as "input" from lora layer and phy-layer then tweaks the gain based on region (see #162) and attempts to route the RF signal through correct output.


⚠ Bofrost.lu has degraded performance

In 33eebde, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 949 ms

Resolved: Bofrost.lu performance has improved in 03ecf34 after 7 minutes.


15 07 2020 Alloy Commodity Reference Data WG Meeting

Date
08/07/2020 16:00 BST
Approve past meeting minutes

July 1st Meeting minutes were approved

Agenda

[ ] Allow for further feedback on data definitions
[ ] Other types of possible data that could be included in product model (e.g. Regulatory)
[ ] CDM Payout Updates - Extension of swap scenario now in Alloy

Minutes:
The group walked through the commodities payout updates to capture the extended swap use case proposal that was raised in a previous meeting. This proposal details the commodityPayout as a distinct payout and not combined with equities as was previously considered. The group will continue to build out this commodities payout and look to capture all of the features that exist within the commoditySwap fPML (financial payouts).
WebEx info

Meeting link: https://finos.webex.com/finos/j.php?MTID=me57eb4b2609b694befaaaf62c107f7e0
Meeting number: 667 751 733
Password: M4SiJxsth47
Join by video system: Dial<EMAIL_ADDRESS>You can also dial <IP_ADDRESS> and enter your meeting number.
Join by phone: +1-415-655-0003 US Toll | +44-20319-88141 UK Toll| Access code: 667 751 733

@aitana16

hi!

Greetings!

Untracked attendees

Nigel Cobb / Regnosys / nigelcobb
Junji Katto / Itau / junjikatto
Jing Wu / GS /
Kenneth Poon / GS / kenneth-hei


[T3A2][T15-A3] Desmond Tan

Ready for review

@e0012764 Good job on catching the need for getter method. Try using the imperative form of the verb, i.e. change instead of changed.


KingKonf::ConfigError: unknown environment variable RACECAR_SSL_CA_CERTS_FROM_SYSTEM

after upgrading to racecar 2.1.0 , I received this error:
KingKonf::ConfigError: unknown environment variable RACECAR_SSL_CA_CERTS_FROM_SYSTEM

We rely on this configuration but the consumer won't boot with it.

What version were you upgrading from?

1.0.1

The underlying Kafka client library has been swapped in v2, can you try and see if your app works if you don't set that env var? It could have been a necessity only with the old library.

I might not be able to in the near future since the ssl config is only necessary for our production deployment and we'll probably stick with v1 until we have tested v2 better outside of production.  If we do get a chance, I'll report back.

Removing RACECAR_SSL_CA_CERTS_FROM_SYSTEM env var did allow the consumer to boot but it did not consume anything from the kafka topic. I'm assuming this is due to ssl issue but I'm not sure how to confirm.
Using same code but racecar v1 does work however.

In racecar 2.x, ssl settings can be configured using this documentation
https://github.com/zendesk/racecar/blob/meqif/liveness-probe/README.md#ssl-encryption-authentication--authorization


Reply method returns None

For the template
+ [*] [what] [is|are|were|was] [_] (latest|new|hot off the press) [news|info|information] [_] [please|thanks|thank you|thank you very much]
- latest

and the input message "what is new" the reply method returns a None.
Traceback:
File "basic_bot.py", line 42, in on_message
    reply = self.rs.reply(user, message)
  File "/Library/Python/2.7/site-packages/rivescript/rivescript.py", line 1786, in reply
    reply = self._getreply(user, msg, ignore_object_errors=errors_as_replies)
  File "/Library/Python/2.7/site-packages/rivescript/rivescript.py", line 2142, in _getreply
    reply = self._process_tags(user, msg, reply, stars, thatstars, step, ignore_object_errors)
  File "/Library/Python/2.7/site-packages/rivescript/rivescript.py", line 2391, in _process_tags
    reply = reply.replace('<star>', stars[1])
TypeError: coercing to Unicode: need string or buffer, NoneType found

It seems you're on an old version of rivescript-python: the filename and line referenced in the exception is no longer in that place, but is now in rivescript/brain.py near line 579.
Bug #54 has the same problem you do, and I'm going to fix it and deploy a new version in a few minutes.

This problem should be resolved if you update to v1.14.3.


Register into General

@JuliaRegistrator register

Error while trying to register: Register Failed
@dubosipsl, it looks like you are not a publicly listed member/owner in the parent organization (ClimFlows).
If you are a member/owner, you will need to change your membership to public. See GitHub Help

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/102147
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 9868df4546da9688f530a7f648a56c22b4e01465
git push origin v0.1.0

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/102148
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 9868df4546da9688f530a7f648a56c22b4e01465
git push origin v0.1.0


Fix welch windows

reported here https://mne.discourse.group/t/is-this-a-bug-in-the-new-compute-psd-method/5734
The corrected computation was based on what they do in scipy.signal._fft_helper
The new test fails on main and passes here.

looks like codespell updated... sigh.  Will fix tomorrow.

backported.


Update VS Code syntax highlighting extension.

I've now fixed some problems left in the last PR and the highlighting is now error-free in terms of user experience (at least from my side). (I still didn't strictly follow the BNF in constructing the syntax because I realized it's not necessary for now as long as the highlighting gets its job done.) I haven't packaged and published this new version yet in case I need to make further modifications. If you notice anything wrong with the highlighting, please tell me. Thanks!

@EricWay1024 Thank you for this follow up!
I don't see any problems with the pull request.
Shall I merge it in? :-)

Certainly :-) I'll package and publish this new version in the market place. Thank you!

Done! Thank you very much, @EricWay1024 !


Creating a substitution doesn't check for existing substitution with the same name

We check whether there are any existing setters with the same name, but we don't check for any existing substitutions. This can cause users to inadvertently replace existing setters.

@mortent Doesn't this mean user is trying to modify existing substitution? We should not throw error in such scenario and update the existing substitution.

But the current behavior seems broken. This will update the definition of the substitution in the Kptfile and add the openapi ref to the new fields, but it doesn't clean up the existing openapi references in the manifests or check if this substitution is references by other substitutions.
An example is https://github.com/mortent/solutions-modern-cicd-anthos/tree/KptFunction/krm/kpt/cicd_cluster which has a substitution cluster-name that is used by several other substitutions. If I do something like
kpt cfg create-subst . cluster-name --field-value anthos-platform --pattern \${platform}-platform

Things end up in pretty weird state.
I'm not sure what is the desired behavior here, but it seems clear that we at least would need to remove the existing openapi references to the substitution. What is the use-case for updating a substitution vs just requiring users to remove it and re-create it?

There is no delete substitution command yet. But yeah, I agree that we need to atleast have some flag like --update-if-exists to modify it. The default behavior for create-subst or create-setter should be to throw an error. So in this case, we should first implement delete-subst command before we implement throwing an error. WDYT?


Pre-releas v4.0.0-beta.2 - [merged]

Merges 87-reproducible-gui-setup -> master
Changelog:

Supports autosubmit_api==4.0.0b2
Configuration updated to support dotenv files.
Experiment configuration tab is enabled and supported for Autosubmit 4.0 experiments
Fixed redirections on not Unauthorized responses from the API

requested review from @LuiggiTenorioK

approved this merge request

mentioned in commit e85de8e45d06232217ed74273cd130a389ad1696


Print description for disabled transformers

Closes #114

Codecov Report

Merging #122 (8d9c558) into main (ba85d1b) will increase coverage by 0.00%.
The diff coverage is 100.00%.

:exclamation: Current head 8d9c558 differs from pull request most recent head d53aa1e. Consider uploading reports for the commit d53aa1e to get more accurate results

@@           Coverage Diff           @@
##             main     #122   +/-   ##
=======================================
  Coverage   97.02%   97.02%
=======================================
  Files          24       24
  Lines        1242     1243    +1
=======================================
+ Hits         1205     1206    +1
  Misses         37       37

Impacted Files
Coverage Δ

robotidy/cli.py
93.79% <100.00%> (+0.04%)
:arrow_up:

robotidy/transformers/__init__.py
94.73% <100.00%> (ø)

Continue to review full report at Codecov.

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


Add ID and reference intepolation support, based on pull request #107

So I met issue #102 , and then found pull request #107 .
However, it cannot solve my problem completely, because the SVG file we get from designer might use ID and reference (contains "url(#a)") for complicated design request.
So I added this, but it got to base on #107 to work.

Hi @jhamlet are you still maintaining this repo?


[Improvement-14942][dolphinscheduler-ui] On the list page of workflow instances and task instances, the default query time range is the current day

Purpose of the pull request
Fix: https://github.com/apache/dolphinscheduler/issues/14942
Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

Codecov Report

Merging #14943 (1718083) into dev (2f2884f) will increase coverage by 0.00%.
Report is 1 commits behind head on dev.
The diff coverage is n/a.

:exclamation: Current head 1718083 differs from pull request most recent head 0d0d0ae. Consider uploading reports for the commit 0d0d0ae to get more accurate results

@@            Coverage Diff            @@
##                dev   #14943   +/-   ##
=========================================
  Coverage     38.81%   38.81%
+ Complexity     4588     4586    -2
=========================================
  Files          1234     1234
  Lines         43385    43351   -34
  Branches       4794     4777   -17
=========================================
- Hits          16841    16828   -13
+ Misses        24680    24658   -22
- Partials       1864     1865    +1

see 26 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

hi, @chenshuai1995 please check the failed CI


No longer working.

I'm not able to run this project on eclipse. I think it's outdated and needs some sort of update. Thanks.

Thanks for the report!
I just bought a new Garmin Venu 2 and was planning to get this project running again and support AMOLED screens. I'll see if I can fix this for other devices as well!

Hey! Just got everything up and running with the latest SDK and opted to use Eclipse this time since the IntelliJ support isn't 100%. I just had to set connectIq as project nature in the settings and got this to build. Would you mind help me with steps to reproduce this? Thanks!

Hey! I already set connect IQ but still can't run this watch face. I don't
know what's missing. Probably some files in the bin folder.
On Sat, Aug 14, 2021 at 3:32 PM Simon Sawert @.***>
wrote:

Hey! Just got everything up and running with the latest SDK and opted to
use Eclipse this time since the IntelliJ support isn't 100%. I just had to
set connectIq as project nature in the settings and got this to build.
Would you mind help me with steps to reproduce this? Thanks!
[image: image]
https://user-images.githubusercontent.com/3248948/129446407-0235efca-099c-4b0c-a741-7f183ba304f7.png
[image: image]
https://user-images.githubusercontent.com/3248948/129446415-193a7fcd-7eef-49f4-a20e-9b4bcd9af7c8.png
[image: image]
https://user-images.githubusercontent.com/3248948/129446426-7d73f159-77e6-4707-bf9d-991f61fa3b04.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bombsimon/garmin-seaside/issues/1#issuecomment-898888599,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO73DIUQRNRNDQEFSQU47FTT4ZO43ANCNFSM5B4Z34VQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

The bin folder is just the output where the compiled result will end up, it's empty before compiling for the first time.
Do you get any error message? Do you see anything in the console (if you're using Eclipse)?

There's no IQ icon on the project folder. I am attaching screenshots for
your reference.
On Sat, Aug 14, 2021 at 4:37 PM Simon Sawert @.***>
wrote:

The bin folder is just the output where the compiled result will end up,
it's empty before compiling for the first time.
Do you get any error message? Do you see anything in the console (if
you're using Eclipse)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bombsimon/garmin-seaside/issues/1#issuecomment-898895574,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO73DIXAKF46CK5TGMCIXMDT4ZWQBANCNFSM5B4Z34VQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

That indicates that you do not have set up Eclipse properly for the project. Right click on the root folder and select Properties. Navigate to Project Natures:

Click Add, then OK on the popup and select connectiq.projectNature:

Click Apply and Close, you should now have the IQ icon on the project folder and from there be able to build and run the project.

Hi Simon,
It gives this error this time;
BUILD: ERROR: vivoactive3: ERROR: assembler: extraneous input
@.*_871091088' expecting {IntNumber, HexNumber, OctalNumber}
BUILD: WARNING: The launcher icon (30x30) isn't compatible with the
specified launcher icon size of the device 'vivoactive3' (40x33). Image
will be scaled to the target size.
BUILD: WARNING: Character id '0' will not display due to an
incompatibility with the graphics system.
BUILD: Complete
Aborting launch due to failed build.
On Sun, Aug 15, 2021 at 7:13 PM Simon Sawert @.***>
wrote:

That indicates that you do not have set up Eclipse properly for the
project. Right click on the root folder and select Properties. Navigate
to Project Natures:
[image: image]
https://user-images.githubusercontent.com/3248948/129485014-3e57243d-a9a1-4284-8edb-e5b6f2b10448.png
Click Add, then OK on the popup and select connectiq.projectNature:
[image: image]
https://user-images.githubusercontent.com/3248948/129485037-c3dd4eff-b848-4123-a8e4-4d589e634b24.png
Click Apply and Close, you should now have the IQ icon on the project
folder and from there be able to build and run the project.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bombsimon/garmin-seaside/issues/1#issuecomment-899074683,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO73DITHMLKA4QXZBHCWD4TT47RSJANCNFSM5B4Z34VQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Have you tried with the Visual Studio Code extension that seems to replace the Eclipse one? Works just as well with this one for me.


chore(events/api): make list APIs operate on event-level objects

Types of changes

[x] Bugfix
[x] New feature
[x] Refactoring

WHY
The schedule API returns the id from the event-level model in the response while the other event APIs return the id from the proposal-level model. It makes frontend development harder to associate detail pages to the main schedule page.
HOW
Major:

Make all APIs for retrieving data in the events app operates on event-level models (& return event-level id).
Implement speech API for querying data based on given query parameters or path parameters:

# List Event API
GET /api/events/speeches/?event_types=<event types>

# examples
GET /api/events/speeches/  # list all talk, sponsored, & tutorial events
GET /api/events/speeches/?event_types=tutorial  # list all tutorial events
GET /api/events/speeches/?event_types=talk,sponsored  # list all talk & sponsored events
GET /api/events/speeches/?event_types=wrong  # return 404

# Detail Event API
GET /api/events/speeches/<event_type>/<pk>/

# examples
GET /api/events/speeches/talk/9  # get detail of talk event with pk=9
GET /api/events/speeches/tutorial/1  # get detail of tutorial event with pk=1
GET /api/events/speeches/wrong/2  # return 404
GET /api/events/speeches/talk/wrong  # return 404

Minor:

refactor serializer of event API
fix EventWrapper for handling speaker_name of sponsored event
add a new field of youtube_id for talk event & sponsored event

Codecov Report

Merging #1036 (409d09a) into master (e316aa4) will increase coverage by 0.02%.
The diff coverage is 59.77%.

@@            Coverage Diff             @@
##           master    #1036      +/-   ##
==========================================
+ Coverage   68.55%   68.57%   +0.02%
==========================================
  Files          90       90
  Lines        3520     3523       +3
==========================================
+ Hits         2413     2416       +3
  Misses       1107     1107

Impacted Files
Coverage Δ

src/events/api/urls.py
100.00% <ø> (ø)

src/events/api/views.py
43.71% <47.72%> (+1.02%)
:arrow_up:

src/events/api/serializers.py
65.78% <70.73%> (+0.27%)
:arrow_up:

src/events/models.py
84.90% <100.00%> (+0.19%)
:arrow_up:

src/proposals/models.py
87.50% <0.00%> (-0.79%)
:arrow_down:

Continue to review full report at Codecov.

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

@setmao

The suggested change is applied with modification.
The implementation of get_proposal_serializer_class() is reverted.


Generation of shares

Hi,
The spec mentions:

This construction yields a beneficial property where the identifier transforms into exactly the first three words of the mnemonic code, so the user can immediately tell whether the correct shares are being combined (i.e. they have to have the same first three words). Moreover, the forth word encodes exactly the index/threshold values, so for example share #2 of 3 required shares will always correspond to the same word.

However, I don't observe this when generating the shares. Could you provide some additional clarification?

The specification of SLIP-0039 is subject to change. Do not use any implementation for now.


OAK-9893 Prefetch for queries

Details are in https://issues.apache.org/jira/browse/OAK-9893

I think we should also add a higher level test where we validate the result set of a few queries in case of prefetch enabled especially a case where the result set size would be greater than the prefetch count.

@nit0906  I have added the test you described now, and a few more. The code coverage of the PrefetchCursor was nearly 90% before these tests, and is now >90%. Actually I don't think the code coverage can be increased further in a reasonable way.

I have added the test you described now, and a few more. The code coverage of the PrefetchCursor was nearly 90% before these tests, and is now >90%. Actually I don't think the code coverage can be increased further in a reasonable way.

Thanks. I was actually thinking on the lines of adding a test in oak-search where Oak might be initialised with system property to enable the prefetch feature for queries. But yes, you are right, that might not increase the line coverage as such.
I think the new added tests should also give good coverage.


specify package versions in conda environment.yml

I deleted my flusion conda environment and rebuilt it successfully from this updated environment file, and afterwards the integration test passes on mac os:
pytest
====================================================== test session starts ======================================================
platform darwin -- Python 3.11.0, pytest-7.4.0, pluggy-1.0.0
rootdir: /Users/elray/research/epi/flu/flusion/code/gbq
collected 1 item

tests/test_gbq.py .                                                                                [100%]

================================================= 1 passed in 80.50s (0:01:20) ==================================================

Thanks, @nickreich .  You'll need to be in the code/gbq folder for the pytest to do its thing.  (This is in the readme somewhere, but it's been a common point of confusion -- you're not alone!)

...additionally, the tests currently don't pass on my desktop, only my laptop, I think due to some underlying random number generation in some C++ library not yielding stable results cross-platform.  Am working on adding a Docker container in hopes that will get us actual reproducibility.
Which is to say, if you can at least get the test to run I think we should call it a win 😅

I got the tests to run, but did get this failure message:
(flusion) SPH-VP4TP416Y0:flusion nick$ cd code/gbq
(flusion) SPH-VP4TP416Y0:gbq nick$ pytest
======================================= test session starts ========================================
platform darwin -- Python 3.11.0, pytest-7.4.0, pluggy-1.0.0
rootdir: /Users/nick/Documents/research-versioned/flusion/code/gbq
collected 1 item

tests/test_gbq.py F                                                                          [100%]

============================================= FAILURES =============================================
___________________________________________ test_gbq_qr ____________________________________________

tmp_path = PosixPath('/private/var/folders/_x/jjpykbt13y7dlp4c38x97yqdbp66vt/T/pytest-of-nick/pytest-0/test_gbq_qr0')

    def test_gbq_qr(tmp_path):
        os.system(f'python gbq.py --ref_date 2024-03-30 --short_run --output_root {tmp_path}')
        actual_df = pd.read_csv(tmp_path / 'UMass-gbq_qr' / '2024-03-30-UMass-gbq_qr.csv')
        expected_df = pd.read_csv(Path('tests') / 'test_gbq_qr' / '2024-03-30-UMass-gbq_qr.csv')
>       assert actual_df.equals(expected_df)
E       assert False
E        +  where False = <bound method NDFrame.equals of     location reference_date  horizon  ... output_type output_type_id        value\n0   ...   78.200548\n476       US     2024-03-30        1  ...    quantile          0.975  5953.266428\n\n[477 rows x 8 columns]>(    location reference_date  horizon  ... output_type output_type_id        value\n0         01     2024-03-30       -1...    80.432531\n476       US     2024-03-30        1  ...    quantile          0.975  5838.668967\n\n[477 rows x 8 columns])
E        +    where <bound method NDFrame.equals of     location reference_date  horizon  ... output_type output_type_id        value\n0   ...   78.200548\n476       US     2024-03-30        1  ...    quantile          0.975  5953.266428\n\n[477 rows x 8 columns]> =     location reference_date  horizon  ... output_type output_type_id        value\n0         01     2024-03-30       -1...    78.200548\n476       US     2024-03-30        1  ...    quantile          0.975  5953.266428\n\n[477 rows x 8 columns].equals

tests/test_gbq.py:9: AssertionError
--------------------------------------- Captured stdout call ---------------------------------------
bag number 1
bag number 2
bag number 3
bag number 4
bag number 5
bag number 6
bag number 7
bag number 8
bag number 9
bag number 10
--------------------------------------- Captured stderr call ---------------------------------------
/Users/nick/Documents/research-versioned/flusion/src/timeseriesutils/src/timeseriesutils/featurize.py:507: FutureWarning: Not prepending group keys to the result index of transform-like apply. In the future, the group keys will be included in the index, regardless of whether the applied function returns a like-indexed object.
To preserve the previous behavior, use

        >>> .groupby(..., group_keys=False)

To adopt the future behavior and silence this warning, use

        >>> .groupby(..., group_keys=True)
  .apply(taylor_coefs_one_column_grp,
/Users/nick/Documents/research-versioned/flusion/src/timeseriesutils/src/timeseriesutils/featurize.py:507: FutureWarning: Not prepending group keys to the result index of transform-like apply. In the future, the group keys will be included in the index, regardless of whether the applied function returns a like-indexed object.
To preserve the previous behavior, use

        >>> .groupby(..., group_keys=False)

To adopt the future behavior and silence this warning, use

        >>> .groupby(..., group_keys=True)
  .apply(taylor_coefs_one_column_grp,
/Users/nick/Documents/research-versioned/flusion/src/timeseriesutils/src/timeseriesutils/featurize.py:507: FutureWarning: Not prepending group keys to the result index of transform-like apply. In the future, the group keys will be included in the index, regardless of whether the applied function returns a like-indexed object.
To preserve the previous behavior, use

        >>> .groupby(..., group_keys=False)

To adopt the future behavior and silence this warning, use

        >>> .groupby(..., group_keys=True)
  .apply(taylor_coefs_one_column_grp,
/Users/nick/Documents/research-versioned/flusion/src/timeseriesutils/src/timeseriesutils/featurize.py:507: FutureWarning: Not prepending group keys to the result index of transform-like apply. In the future, the group keys will be included in the index, regardless of whether the applied function returns a like-indexed object.
To preserve the previous behavior, use

        >>> .groupby(..., group_keys=False)

To adopt the future behavior and silence this warning, use

        >>> .groupby(..., group_keys=True)
  .apply(taylor_coefs_one_column_grp,
===================================== short test summary info ======================================
FAILED tests/test_gbq.py::test_gbq_qr - assert False
=================================== 1 failed in 77.20s (0:01:17) ===================================

@elray1 I will let you decide if this test is "good enough" for review approval.

OK, "great".
...I think I'll merge this and deal with the reproducibility issue in a separate PR more focused on Docker


Fix non-editable regression

Fixes https://github.com/natejenkins/socialApp/issues/3167
Switching from doc's getSelection to squire's here https://github.com/natejenkins/squire/pull/43 caused the regression with moving out of non-editable nodes.
The range object they return are slightly different - doc's has the start/end container as the text node, squire's has it as the non-editable node (span, say). moveNodeOutOfNotEditable doesn't handle the later correctly, since it starts its search with the starting node's parent, not the node itself.
An alternative fix would be to modify moveNodeOutOfNotEditable to handle this case; this here fix is quicker.

[Fragility PSA] Regression tests needed for long-term stability

Agreed. Was just trying to write a click-test for this; can't seem to get a convincing enough simulation of the click event to trigger the bug using our pure html/js tests. Headless browser - I think it's high-time.

@jmnicholson this fixes your equation troubles (they are currently impossible to delete)

An alternative fix would be to modify moveNodeOutOfNotEditable to handle this case; this here fix is quicker.

I disagree.  I spent some time looking at this to fully understand the problem.  moveNodeOutOfNotEditable is functioning properly.  It is meant as a safeguard to ensure we are never inside of a non-editable node.  With normal cursor operations in squire this is not possible.  However with things like mouseclicks or external functions setting cursor positions it can and does happen.  One instance is clicking at the end of a line.  If we look at the source of the function:
var moveNodeOutOfNotEditable = function( node, nodeOffset ){
    var startContainer = node
    var moveRight = false
    var nextSibling
    var currentParent = startContainer.parentNode
    var newParent     = currentParent
    var textLength, startOffset, offset

    if(startContainer.nodeType === TEXT_NODE){
        textLength = startContainer.data.length
        // if we are for some reason, likely an up or down arrow, finding ourselves in the middle of a
        // text area that isn't editable, we need to decide if we should be in front of that element
        // or to the right of it.  At the moment this will only work for a single text element in a series
        // of non-editable structures, but it can be extended to work for all cases if necessary.
        if(nodeOffset > textLength/2){
            moveRight = true
        }
    }

there is a variable moveRight which is initially false.  If you think about it, as you are moving up the tree you can decide to move up and left or up and right.  That is what determines if the current selection will be the parent of the non-editable node or its nearest right neighbor.  If I click more to the right in a non-editable node, that results in my cursor appear to the right of it, the anticipated behavior.
Here the bug wasn't really with moveNodeOutOfNotEditable.  Changing the document selection to that of squire caused the selection to be pointing at the non-editable node and not "in" the non-editable node.  Which means there is nothing to do, it is a no-op.  Pointing at a non-editable node is a perfectly valid cursor position which you can explore with the keyboard.

Pointing at a non-editable node is a perfectly valid cursor position which you can explore with the keyboard.

This was what I  misunderstood - thanks for the explanation!


[Improve] Add deprecated annotation for ReadonlyConfig::toConfig

Purpose of this pull request
This PR add deprecated annotation for ReadonlyConfig::toConfig. We should make sure it not be used with new code. Because we will delete it in the future.

Does this PR introduce any user-facing change?
no

How was this patch tested?
unnecessary.

Check list

[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

cc @hailin0 @EricJoy2048 @ruanwenjun


rcRadius attribute is ignored

Even when set to app:rcRadius="1000dp" it rcRadius doesn't change the default radius

same issue here, rcRadius doesn't do anything. Still have square corners


[Feature]: Change the indicator in the onboarding flow

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
Many users are not noticing this indicator onboarding, it should be replaced
https://user-images.githubusercontent.com/20532920/178671869-4537760b-117b-496b-850d-9f478c9e18a9.mov
Why should this be worked on?
 This isn't very noticeable, and users often miss it entirely.

Stats

Stat
Values

Reach
4000

Effort (months)
0.5


Determine configuration strategy for new events

A/C

[ ] An ADR detailing how new events will be rolled out to the community

Since https://github.com/openedx/openedx-events/pull/249, new events can be added to the event bus via configuration only (no code changes). Some options for how we would roll out new events:

All events are off by default. New events are added to the configuration map in the producing service's configuration file with enabled=False so people know what events are available
All events are on by default. New events are added to the configuration map in the config with enabled=True
All new events start disabled by default, but are updated to be enabled by default as part of a planned release (with the change noted in the release notes)

Note: Option 3 uses enabled as a temporary rollout toggle. If we use this route (which I like), we'd need to also understand how to get the best of https://edx.readthedocs.io/projects/edx-toggles/en/latest/how_to/documenting_new_feature_toggles.html. Or, maybe we should quite literally be using the toggle annotations for each of these?


Fix sourceMap.sourcesContent = undefined

Minor fix regarding when sourceMap.sourcesContent is undefined
https://github.com/webpack/webpack/blob/master/lib/SourceMapDevToolPlugin.js#L163

@piecyk thanks! Do you know what devtool option, SourceMapDevtoolPlugin configuration, or other detail might make this situation so I can make a regression test for it?

Published in 0.5.12

@mzgoddard awesome work 👏 Just did write an test for this, and outcome is not general and not related to webpack...
It looks like some kind of bug in third party loader that inject stuff to source and tries to update the source maps also...
So IMHO there is no need any test for this, also adding this check is harmless so we can live with it...
sorry for the hassle 👍


Error: Cannot find native module 'ExpoMaterial3Theme'

In an Expo v48 managed app, I get the following error when attempting to use this module:
Error: Cannot find native module 'ExpoMaterial3Theme', js engine: hermes

Ah, apologies! I didn't realize that Expo uses Expo Go by default, which doesn't support third-party native modules.


IDE does not signal progress update from "Downloading new runtime"

I tried running project-manager with an upgraded GraalVM version, and so, I got tons of these messages in project-manager's log: (Downloading GraalVM runtime with progress parameter)

But the IDE does not signal anything to me - it is just blank. I would expect a message similar to "Compiling standard library, this could take a while ... "

Duplicate of #6402
@Akirathan or @sylwiabr feel free to bump priority of that task (and/or put it in the milestone) if you think it's important.


Support Node LTS

Running this example:
const { Deno } = require("deno.ns");

I get the following in Node v14.17.1:
> node test.js
node_modules\deno.ns\dist\deno\stable\classes\PermissionStatus.js:7
class PermissionStatus extends EventTarget {
                               ^

ReferenceError: EventTarget is not defined
    at Object.<anonymous> (node_modules\deno.ns\dist\deno\stable\classes\PermissionStatus.js:7:32)
    at Module._compile (internal/modules/cjs/loader.js:1085:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
    at Module.load (internal/modules/cjs/loader.js:950:32)
    at Function.Module._load (internal/modules/cjs/loader.js:790:14)
    at Module.require (internal/modules/cjs/loader.js:974:19)
    at require (internal/modules/cjs/helpers.js:92:18)
    at Object.<anonymous> (node_modules\deno.ns\dist\deno\stable\classes\Permissions.js:5:31)
    at Module._compile (internal/modules/cjs/loader.js:1085:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)

This is because EventTarget was not a global until node v15 I think (works in 16). Current LTS version of node is v14. We should try to support at least Node LTS.

Alternatively, node 16 is active LTS from end of this month (October 26th). Since deno.ns might not be "stable" for a few weeks even by the most optimistic estimate, it might not be so bad to only support active LTS from then (node 16).

drop src/hacks/web-streams.ts (blob.stream() added in: v16.7.0) ~https://t.me/fromdeno/12244


TBI - Add new module @sap-ux/ui5-application-inquirer to support UI5 app generation prompting

Description (include screenshots)
Provides functionality to prompt end users for the inputs necessary to generate a UI5 application.
Value
Optional - details on how this technical backlog item provides value to end-users or dev team eg. Performance, Quality, Maintainability. This will help determine the ranking in relation to feature development
Architecture Elaboration
Does it requires architecture elaboration?
Notes
Tasks

[ ] Task 1

Closing as done


self-serve instances

Add a form for users to request a new instance and have it created for them, instead of requiring that the multisite admin create it for them

A suggested consideration: addition to an admin-approval process, perhaps permit auto-approval of any request that comes from one of a given set of domain names (e.g., every municipal government in a particular state). IMHO, it's not important that this feature exist at the time of release, but rather that it be possible to later add this feature, perhaps just making this something to keep in mind when creating that approval cycle.


feat: load experiment config from yaml file

This PR introduces a way to store all the configuration related to an experiment in a YAML file.
To give the user the flexibility to fully describe the parameters of an experiment in the YAML, I've introduced the notion of template entrypoint scripts. These are bash scripts that the user writes, but with placeholders for some parameters. If the entrypoint script ends in _template.sh, slurmpilot will generate the final script by replacing every keyword that appears in the template with its desired value. The keywords and their values are defined in the template section of the YAML file. So an experiment can be fully described by a combination of a config.yaml and a cluster_script.sh or cluster_script_template.sh.
You can test this by running python launch_hellocluster.py config.yaml
Ideally, the script launch_hellocluster.py should be a standalone command like slurmpilot --run config.yaml so that we can launch experiments from the command line.

The idea of having a CLI to launch jobs makes sense (it is in this list of planned features) however, I think we should refine a bit the user experience.
For instance, we do not want user to have to write launch_hellocluster.py as it is generic to every job. I think ultimately, we would want to have something where you just specify the jobinfo arguments as CLI with something like this:
sp-launch --jobname helloworld --entrypoint main.py --partition GPUlarge --cluster cloud

Converging on this may take a few iterations, I propose to start the discussion in a separate issue so far I have been writing notes, for instance here is the note I wrote before adding python support.
For this PR, I would like to decouple the templating idea from the main class (having templating in the main class would be a biggish decision, I tend to prefer to remove stuff from the main class than to add it). This can be done by moving the templating into an util and calling the templating and config completion into launch_hellocluster.py.

Upon thinking a little more, I decided that it's best not to integrate the template feature into slurmpilot at all (i.e., not even in its utils). This code works well as a standalone example for consuming SP, showcasing how flexible it can be.
We can discuss more about making a CLI to launch jobs in a separate issue :+1:

Makes sense thanks for the contribution and lets build a nice CLI!


Catch missing methods in brew cask audit.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew tests with your changes locally?
[x] Have you successfully run brew man locally and committed any changes?

brew cask audit currently passes when a cask calls an undefined method is called. This collects all missing methods and makes it fail.

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.


gha: install caikit-nlp-client in a virtualenv

When not using a venv, pip complains about an externally managed environment:
+ pip install caikit-nlp-client
error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
    python3-xyz, where xyz is the package you are trying to
    install.

    If you wish to install a non-Debian-packaged Python package,
    create a virtual environment using python3 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
    sure you have python3-full installed.

    If you wish to install a non-Debian packaged Python application,
    it may be easiest to use pipx install xyz, which will manage a
    virtual environment for you. Make sure you have pipx installed.

    See /usr/share/doc/python3.12/README.venv for more information.

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.

Kserve smoke test failure to be fixed in #371


Responsive Spline Element does not cover full screen?

Hey there
I am currently trying to integrate my spline design into a Next.js project but when I add it into my page. It only shows up at the top of the page like so:

I tried wrapping it in a div that occupies the full height of screen but still displays in the same position.

Any help would be appreciated
Mr Biskit

Hi Mr Biskit,
Does the div also occupy full width?


Missing line number on fist page.

Im trying print some code, but i have no line number on fist page, on Firefox browser.
But on Chrome has line number.
Firefox has custom header, Chrome not while printing.

I have the same issue, but with Firefox.  No problems with the other pages, but the first one has no line numbers.

Same issue. No line numbers on first page with Firefox.


power_connector_max_current

in version 2.5.4 when i number.alfen_eve_single_pro_line_power_connector_max_current goes from 0A to 16A it goes after a few seconds back to 0A.
In version 2.5.2 it still works fine.

which version do you got this problem?

I've just compare both version:
https://github.com/leeyuentuen/alfen_wallbox/compare/2.5.2...leeyuentuen:alfen_wallbox:2.5.4
I don't see a direct link that this gives this issue.
Could it be that there is another instance running so normally it was 16A but if they can't connect they will return to 0A?
maybe try the latest beta version, it could be that this can fix this issue:
https://github.com/leeyuentuen/alfen_wallbox/releases/tag/2.6.3

I think the service is going wrong: Alfen Wallbox: set_current_limit

Do you still have the problem in the newest version 2.6.6? I have that version installed and have no issues.

it seems there is some issue with the service set_value, I'll take a look on it later

maybe take a look at this version, could fix that service call issue:
https://github.com/leeyuentuen/alfen_wallbox/releases/tag/2.6.8

@Dominic-070  still got this issue?

I'm renovating in our new home and then on vacation. I'll have a look in October but I think it works.


Redo the safe build option

I completely misunderstood how the docker daemon interacts with containers and how the build step operates. By default containers can't access the host's daemon in any way and even trying to install a functional daemon inside a container requires additional permissions.
This means that we don't need to archive images to prevent other teams from building off of them or interacting with them in some way. My understanding now is that the only way they have to actually interact with them is via FROM <image>, so there basically are two things we can do to prevent that:

Build them with the pull option. This will make it so that docker always tries to pull images from the docker hub even when a local version exists. As long as there are no images on docker hub with that name, the build process fails.
Don't give them deterministic tags (or none at all). If teams can't reference the other team's images then they can't build off of them.

The first option has the downside that a team may upload an image to the docker hub to prevent the build process from failing completely. I'm not sure how the versioning and caching of docker works well enough, so the uploaded image might not actually override the local one.
Because of that, I've essentially combined it with the second option by building with the pull option and also giving the images random names. This means that in principle they could be referenced but only by guessing the correct name and also uploading an image with that name to the docker hub. The upside of this is that we're not creating a bunch of unnamed and unidentifiable images. I'm not super sure if this is worth the potential risk here, happy to drop that commit if you feel like building without names at all is better.
Since this fix doesn't affect the build times at all we can just always do this and thus don't need the safe_build option in the config at all.

We are clearing up all images after the run. There currently isn't an option to not not have that happen during development. I'll put it on the todo list.
Since we're not printing the straight logs anymore I'm also not sure if the students can even see the image names, but there probably is some way to create error messages that include them. So this would still run into problems if docker doesn't clean them up properly or something else goes wrong. Maybe we can just also delete any image that follows our naming pattern algobattle_00000000 before we start building new ones. We can then easily detect if anything goes wrong there and stop the build process if it does.
We could also do something like reject dockerfiles that include FROM algobattle_00000000, though that'd mean parsing them with something like a regex which seems like a pretty finnicky solution.
The easiest and safest solution would be just not tagging the images at all. But we'd then be leaving unidentifiable images around. Though this only is an issue if you either chose not to clean them up or if some error happens, so it shouldn't be an actual concern for the server running the actual matches.
Maybe we could combine the two configs into something like a development mode where we then do give the images proper names and don't clean them up. We could later then also add other nice to have features like it logging the instances/solutions so teams can see what caused their programs to fail with more details.

I think your suggested solution of a developer mode is good. We should put this on the check-list before the merge, to evaluate whether there is a realistic 'attack vector' left. I do not think that we need to be concerned with supervised students exploiting these images anymore, but in the context of a bigger contest including teams outside our supervision, this may ultimately be a concern.


workflows' manifests/base/crd missing crd from argo-events

Summary
In the Argo UI, when clicking on Event Sources or Sensors icon, error message will appear if the CRDs from argo-events/manifests/base/crds/ have not been installed.
Diagnostics
I am using AWS EKS, running v1.19 kubernetes
I just completed a fresh install of Argo Workflows v3.0.2
In the UI, these are sample error messages:
Unsuccessful HTTP response: the server could not find the requested resource (get eventsources.argoproj.io)

 Unsuccessful HTTP response: the server could not find the requested resource (get sensors.argoproj.io)

From the Argo server  kubelogs, these are sample error messages:
time="2021-04-25T17:46:22.504Z" level=info msg="finished unary call with code NotFound" error="rpc error: code = NotFound desc = the server could not find the requested resource (get eventsources.argoproj.io)" grpc.code=NotFound grpc.method=ListEventSources grpc.service=eventsource.EventSourceService grpc.start_time="2021-04-25T17:46:22Z" grpc.time_ms=2.474 span.kind=server system=grpc

time="2021-04-25T17:48:04.981Z" level=info msg="finished unary call with code NotFound" error="rpc error: code = NotFound desc = the server could not find the requested resource (get sensors.argoproj.io)" grpc.code=NotFound grpc.method=ListSensors grpc.service=sensor.SensorService grpc.start_time="2021-04-25T17:48:04Z" grpc.time_ms=4.163 span.kind=server system=grpc

Once the CRDs from argo-events are installed, the above errors goes away. https://github.com/argoproj/argo-events/tree/master/manifests/base/crds

You need to install these from the argo-events repository.

https://argoproj.github.io/argo-events/quick_start/


When to compile the file size can be less than 100KB ？

like  vuejs?

Monday at noon.

Compiling with AOT and tree shaking (not currently available on webpack) can offer significant size gains.
Check out https://angular.io/docs/ts/latest/guide/deployment.html for tips on how to achieve this.


scriptcs is not recognized as an internal and external command

Type: Bug
Do you have a workaround for this "scriptcs is not recognized as an internal and external command" while trying to run a "HelloWord.cs" program.
VS Code version: Code 1.78.2 (b3e4e68a0bc097f0ae7907b217c1119af9e03435, 2023-05-10T14:39:26.248Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: Yes

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz (8 x 2419)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
15.77GB (8.16GB free)

Process Argv
--crash-reporter-id d28106b3-cd04-490a-b194-f819821f7d80

Screen Reader
no

VM
0%

Extensions (43)

Extension
Author (truncated)
Version

vscode-django
bat
1.10.0

better-toml
bun
0.3.2

markdown-julia
col
0.0.1

c-cpp-compile-run
dan
1.0.45

python-environment-manager
don
1.0.4

python-extension-pack
don
1.7.0

code-runner
for
0.12.0

c-cpp-runner
fra
5.4.0

auto-using
Fud
0.7.15

chatgpt-vscode
gen
0.0.8

fsharp-language-server
geo
0.1.28

vscode-javac
geo
0.2.45

vs-code-runner
Har
2.0.1

Ionide-fsharp
Ion
7.5.4

vscode-csharp-snippets
jor
1.1.0

language-julia
jul
1.47.2

vsc-python-indent
Kev
1.18.0

csharpextensions
kre
1.7.3

python-path
mge
0.0.14

csharp
ms-
1.25.7

python
ms-
2023.8.0

vscode-pylance
ms-
2023.5.40

cmake-tools
ms-
1.14.31

cpptools
ms-
1.15.4

cpptools-extension-pack
ms-
1.3.0

autodocstring
njp
0.6.1

java
red
1.18.0

rust-analyzer
rus
0.3.1533

rust-pack
Swe
0.3.3

tabnine-vscode
Tab
3.6.51

python-extended-snippets
tus
0.0.1

cmake
twx
0.0.17

vscode-lldb
vad
1.9.2

intellicode-api-usage-examples
Vis
0.2.7

vscodeintellicode
Vis
1.2.30

vscode-gradle
vsc
3.12.7

vscode-java-debug
vsc
0.50.0

vscode-java-dependency
vsc
0.22.0

vscode-java-pack
vsc
0.25.11

vscode-java-test
vsc
0.38.2

vscode-maven
vsc
0.41.0

vscode-spring-initializr
vsc
0.11.2

jinja
who
0.0.8

(1 theme extensions excluded)

Sounds like an issue with your system configuration, make sure that tool is installed and on your path.

I installed VS IDE first before VS Code, how should I ensure that the tool is installed properly.  Do I need to download the scriptcs is available.
--- Andrew Goh
On Thursday, 1 June 2023 at 11:24:38 am SGT, Rob Lourens<EMAIL_ADDRESS>wrote:

Closed #183807 as completed.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Hi Rob,
I have chocolatery installed.  How do I set set myself up for Administrative privilege access using Microsoft PowerShell?
Thanks,
--- Andrew Goh
On Thursday, 1 June 2023 at 03:04:01 pm SGT, Andrew Goh<EMAIL_ADDRESS>wrote:

I installed VS IDE first before VS Code, how should I ensure that the tool is installed properly.  Do I need to download the scriptcs is available.
--- Andrew Goh
On Thursday, 1 June 2023 at 11:24:38 am SGT, Rob Lourens<EMAIL_ADDRESS>wrote:

Closed #183807 as completed.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Docker container

Added a docker container so that folks can get going with just docker compose up --build.

Hey thanks for the PR.
My personal taste when it comes to boilerplates is to have 0 bloat. That means only stuff that's needed by most projects should be included, even if that means some things a big part of users would benefit from will be missing.
And I think making this Docker-friendly falls in that category. Potentially useful, but definitely not for everyone.
I believe optional things like this are better added to individual projects that use the boilerplate.


offset

Hi,
Great work. The character setups are very easy to offset for truncated domes, as laid out by Paul Bourke by changing the size and position of the fisheye camera. Is there anyway to do this with the shader example? - most of my attempts to manipulate the v2f to offset or enlarge circle just break it.
Best wishes
Luke

Hi Luke,
what do you mean truncated domes? can you link a picture?

its a forward facing dome where the back part is actually removed. So the domemaster is often bigger and offset to not include the back camera but still fills the screen.
Like this: http://wiki.blender.org/uploads/1/1e/Dev-GameEngine-Dome-Rear-Truncated.jpg

You can either modify the shader or render the fisheye camera to a texture, place it on a plane, then use an orthographic camera for final output. The second method allow you to make adjustments using Unity editor controls.

Render to texture method works well, thanks for help.


SCM: change icon hides when extension is installed

I have no clue why but with this extension installed, icons for change type are removed from my SCM view shortly after window load:

/cc @joaomoreno

cc @jrieken

hm, interesting...

Not able to reproduce this with 0.1.2

I'm also not able to reproduce this with the latest version, 0.1.6, so will close this

Still happens:

Steps? Logs? Console logs?

@jrieken

yo code
git commit -m "init"
rm README.md
Git > Changes View
wait 2 seconds

=> :bug: icon is gone

logs.zip

I am still seeing this all the time, was this pushed?

Hmm, yeah it was pushed. The change should be in version 0.2.0 of the extension

Still happening:

Closing as a duplicate of https://github.com/microsoft/vscode/issues/81467


std::cell::RefCellregex::exec::ProgramCacheInner can't be shared between threads

Apologies if this is documented and I missed it. I'm currently working with regex in some async stream work, and came across this error:
error[E0277]: `std::cell::RefCell<regex::exec::ProgramCacheInner>` cannot be shared between threads safely
   --> crates/nu-cli/src/commands/parse.rs:155:15
    |
155 |     Ok(stream.to_output_stream())
    |               ^^^^^^^^^^^^^^^^ `std::cell::RefCell<regex::exec::ProgramCacheInner>` cannot be shared between threads safely
    |
    = help: the trait `std::marker::Sync` is not implemented for `std::cell::RefCell<regex::exec::ProgramCacheInner>`

Is it possible to run regex in a mode that won't trip over the RefCell for the inner cache, by chance?

Can you provide a sample reproduction? Regex itself implements both Send and Sync, so it's not clear to me why you're seeing this error.

@BurntSushi - apologies for the noise. I managed to work around it using a different approach. I had been using the async_stream! macro to help create an async stream of output, but there was some kind of bad interaction between it and regex. When I rewrote it using the normal stream operators (like .map), the error went away.

I ran into the same error with Regex 1.3.9 in my project. Updating this crate to the latest 1.4.5 fixed it.
CaptureMatches (which I was using) does not implement Send in that version which can also be seen in its documentation:
https://docs.rs/regex/1.3.9/regex/struct.CaptureMatches.html#impl-Send
Not sure why that is, but in case anyone else is running into this, upgrading to latest version should fix it.

@kangalioo That's interesting. I am myself not even sure why the Send impl changed for the CaptureMatches iterator. There's been some recent work in this area, specifically, #749. But CaptureMatches should have still been Send.
Since regex uses iterior mutability and does some of its own synchronization, a lot of these marker traits are relevant. It's probably a compatibility hazard at this point, which means we probably need to be a bit more rigorous about asserting which marker traits are implemented on each public API type. A tedious endeavor, no doubt.


Panic on assignment to entry in nil map at streamsMap.AddStream

On new session handleConn eventually closes the session executed in a goroutine. As part of this closure, streamsMap is set to nil.
I wonder if it is possible for session manager to return a session that is already closed, which could then result in a panic below.
panic: assignment to entry in nil map
goroutine<PHONE_NUMBER> [running]:
github.com/quic-go/webtransport-go.(*streamsMap).AddStream(0xc194fdbde8, 0xc15f2954a0?, 0xc025dc8b70)
	/go/pkg/mod/github.com/quic-go/webtransport-go@v0.5.1/streams_map.go:24 +0x66
github.com/quic-go/webtransport-go.(*Session).addStream(0xc194fdbd10, {0x7f2b66fb6cf0?, 0xc15f2954a0}, 0x60?)
	/go/pkg/mod/github.com/quic-go/webtransport-go@v0.5.1/session.go:173 +0x152
github.com/quic-go/webtransport-go.(*Session).OpenStreamSync(0xc194fdbd10, {0x136cb60?, 0xc087ad9920?})
	/go/pkg/mod/github.com/quic-go/webtransport-go@v0.5.1/session.go:324 +0x21e
github.com/libp2p/go-libp2p/p2p/transport/webtransport.(*conn).OpenStream(0x4b23f034feb1?, {0x136cb60?, 0xc087ad9920?})
	/go/pkg/mod/github.com/libp2p/go-libp2p@v0.25.1/p2p/transport/webtransport/conn.go:48 +0x2b
github.com/libp2p/go-libp2p/p2p/net/swarm.(*Conn).openAndAddStream(0xc0d09e8ab0, {0x136cb60?, 0xc087ad9920?}, {0x1376500, 0x1d05f40})
	/go/pkg/mod/github.com/libp2p/go-libp2p@v0.25.1/p2p/net/swarm/swarm_conn.go:220 +0x42
github.com/libp2p/go-libp2p/p2p/net/swarm.(*Conn).NewStream(0xc0d09e8ab0, {0x136cb60, 0xc087ad9920})
	/go/pkg/mod/github.com/libp2p/go-libp2p@v0.25.1/p2p/net/swarm/swarm_conn.go:211 +0x175
github.com/libp2p/go-libp2p/p2p/net/swarm.(*Swarm).NewStream(0xc000726000, {0x136cb60, 0xc087ad9920}, {0xc2252abad0, 0x26})
	/go/pkg/mod/github.com/libp2p/go-libp2p@v0.25.1/p2p/net/swarm/swarm.go:401 +0x1f0
github.com/libp2p/go-libp2p/p2p/host/basic.(*BasicHost).NewStream(0xc00027e780, {0x136cb60, 0xc087ad9920}, {0xc2252abad0, 0x26}, {0xc000868070?, 0x1, 0x1})
	/go/pkg/mod/github.com/libp2p/go-libp2p@v0.25.1/p2p/host/basic/basic_host.go:626 +0x16f
github.com/libp2p/go-libp2p-kad-dht/internal/net.(*peerMessageSender).prep(0xc23c3a3ae0, {0x136cb60?, 0xc087ad9920?})
	/go/pkg/mod/github.com/libp2p/go-libp2p-kad-dht@v0.21.0/internal/net/message_manager.go:218 +0x6a
github.com/libp2p/go-libp2p-kad-dht/internal/net.(*peerMessageSender).prepOrInvalidate(0xc23c3a3ae0, {0x136cb60, 0xc087ad9920})
	/go/pkg/mod/github.com/libp2p/go-libp2p-kad-dht@v0.21.0/internal/net/message_manager.go:200 +0x91
github.com/libp2p/go-libp2p-kad-dht/internal/net.(*messageSenderImpl).messageSenderForPeer(0xc000d88e00, {0x136cb60, 0xc087ad9920}, {0xc2252abad0, 0x26})
	/go/pkg/mod/github.com/libp2p/go-libp2p-kad-dht@v0.21.0/internal/net/message_manager.go:150 +0x233
github.com/libp2p/go-libp2p-kad-dht/internal/net.(*messageSenderImpl).SendRequest(0xc000d88e00, {0x136cab8, 0xc16b6a9b40}, {0xc2252abad0, 0x26}, 0xe50620?)
	/go/pkg/mod/github.com/libp2p/go-libp2p-kad-dht@v0.21.0/internal/net/message_manager.go:78 +0xd8
github.com/libp2p/go-libp2p-kad-dht/pb.(*ProtocolMessenger).GetClosestPeers(0xc000868130, {0x136cab8, 0xc16b6a9b40}, {0xc2252abad0, 0x26}, {0xc0633607b0?, 0x0?})
	/go/pkg/mod/github.com/libp2p/go-libp2p-kad-dht@v0.21.0/pb/protocol_messenger.go:108 +0xd4
github.com/libp2p/go-libp2p-kad-dht.(*IpfsDHT).FindPeer.func1({0x136cab8, 0xc16b6a9b40}, {0xc2252abad0, 0x26})
	/go/pkg/mod/github.com/libp2p/go-libp2p-kad-dht@v0.21.0/routing.go:604 +0xfb
github.com/libp2p/go-libp2p-kad-dht.(*query).queryPeer(0xc1920f7cb0, {0x136cab8, 0xc16b6a9b40}, 0xc02ce7d120?, {0xc2252abad0, 0x26})
	/go/pkg/mod/github.com/libp2p/go-libp2p-kad-dht@v0.21.0/query.go:408 +0x26e
created by github.com/libp2p/go-libp2p-kad-dht.(*query).spawnQuery
	/go/pkg/mod/github.com/libp2p/go-libp2p-kad-dht@v0.21.0/query.go:325 +0x44a

That's an interesting one! The reason here is that OpenStreamSync can block at the QUIC layer. We need to check if the session is still alive after this call has returned.
Fix incoming.


fix spell damage instances getting extra damage

Even though damage instances from the items don't inherit damage bonuses anymore they still are affected by MoJ.
Probably needs a new component like AddAdditionalWeaponDamage but for spell damage.


REQUEST-920-PROTOCOL-ENFORCEMENT : Expecting a variable, got:  :  MULTIPART_SEMICOLON_MISSING

owasp-modsecurity-crs-3.0.2/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf. Line: 169. Column: 390. Expecting a variable, got:  :  MULTIPART_SEMICOLON_MISSING
Got this error message when reloading nginx with modsecurity3.
nginx version - 1.13.9

See the following ticket https://github.com/SpiderLabs/owasp-modsecurity-crs/issues/1021

This a known issue @stevepaul-alonso. Follow @csanders-git comment and also see #1701 if you need more information.

I got it fixed. Thank you very much.
On Mar 12, 2018 12:47 PM, "Victor Hora"<EMAIL_ADDRESS>wrote:

This a known issue @stevepaul-alonso https://github.com/stevepaul-alonso.
Follow @csanders-git https://github.com/csanders-git comment and also
see #1701 https://github.com/SpiderLabs/ModSecurity/pull/1701 if you
need more information.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SpiderLabs/ModSecurity/issues/1704#issuecomment-372379437,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AX7b1_GiI8yoiKw6T_hEmCqnxhIoA9Rqks5tdqaMgaJpZM4SlxrZ
.