Windows 10 IoT and Windows Server production supported or not?

Hi, I am not sure I understand whether Windows 10 IoT and Windows Server are supported in Production. According to this page:
For development and test scenarios, Azure IoT Edge with Windows containers can be installed on any version of Windows 10 or Windows Server 2019 (build 17763) that supports the containers feature.
Develpment and test? But according to the page https://docs.microsoft.com/en-us/azure/iot-edge/support#operating-systems Windows 10 IoT and Windows Server are part of Tier1, therefore supported for production.
Please clarify.

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

ID: 4f41e023-819c-64a1-8bef-d050481a7ef7
Version Independent ID: 6f918de8-3e37-5f10-9b5b-aaf453869d2e
Content: Install Azure IoT Edge on Windows
Content Source: articles/iot-edge/how-to-install-iot-edge-windows.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

@smoms Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Hi @smoms, licensing and version support is always tricky to communicate. We talk about development and testing on any Windows 10 device, because developers may want to install the IoT Edge runtime on their own Windows 10 machines for inner loop development. However, for deploying IoT Edge in production you should only use devices running the operating system versions listed in the support page.  Does that make sense?

@kgremban thanks. Sorry but to me does not make sense. Because i am asking whether those Windows OS are supported, Yes/No?
By the way I think today I've found the answer here: https://techcommunity.microsoft.com/t5/Azure-IoT/June-IoT-Edge-updates/m-p/690821#M134  What do you think?

Olivier's post is consistent with what's in https://docs.microsoft.com/azure/iot-edge/support
There's a difference between an operating system that works with IoT Edge, and an operating system that Microsoft declares to be 'generally available' for IoT Edge. The tier 1 generally available operating systems listed in the support page are those that we test before every release and agree to support if you deploy it in production and find bugs or issues. However, we don't want block customers who are just trying out the service by making them use one of three officially supported versions of Windows. You may have a laptop running Windows 10 Enterprise. You can install IoT Edge on it, and it'll work fine, and you can do all your development and testing there. But if you deployed your solution to production using Windows 10 Enterprise laptops, Microsoft wouldn't be able to provide support.

@kgremban  From what I understand Windows Server is now GA, that means Tier 1, right? If yes, you would need to review the doc.
Windows 10 Core is Tier 2, but soon will become Tier 1, right?
I would appreciate you could answer these questions only.
thanks lot.

Yes, everything in this article is accurate for devices in production: https://docs.microsoft.com/azure/iot-edge/support#operating-systems. Windows Server 2019 and Windows Server IoT 2019 are GA. Windows 10  IoT Core is still in public preview, but is working towards GA.

Many thanks. If so, I am not sure if you agree that this page https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/iot-edge/how-to-install-iot-edge-windows.md then needs to be slightly updated.

How would you update the how-to-install article that would be more clear?

well what we have said so far is not perfectly consistent with statement: For development and test scenarios, Azure IoT Edge with Windows containers can be installed on any version of Windows 10 or Windows Server 2019 (build 17763) that supports the containers feature.

Yes, I understand that your issue is with that statement, but I don't know what I could say to make it more clear for future readers. From my perspective, that statement is not in contradiction to what we have said so far. Perhaps you could make a suggestion for a new statement that makes more sense to you. Otherwise, we can just mark this issue as resolved because your question has been answered.

@smoms 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.


Change operators with Object.entries to use Object.keys to improve cross browser compatibility

As you pointed out, Object.entries is not supported by internet explorer.
All methods using Object.Entries should be able to be reworked to use Object.keys, do you see any downsides?
References

Object.entries
Object.keys

All methods using Object.Entries should be able to be reworked to use Object.keys, do you see any downsides?

No. When this project started, IE support wasn't really considered. Now that I've spent many hours digging through documentation to plan the scope, I think adding 'ie polyfill' as a selling point will be good to attract users.
Since this change is non-breaking, lets table it until after the 1.0 release.


The description of poll's returned value is not always acurate

There is a sentence in the documentation says:

The "recursive" result happens when the current running code was invoked by a callback, and tries to call poll again.

But actually the "recursive" result occurs when the event is posted concurrently, without being invoked by a callback.
For instance:
    init_worker_by_lua_block {
        local events = require("resty.worker.events")
        local ok, err = events.configure({shm = "worker-events", interval = 0.1})
        if not ok then
            error("failed to init worker event: " .. err)
        end
        events.register(function()
            ngx.sleep(1)
        end, "source", "event")
    }
    lua_shared_dict worker-events 1m;
    server {
        listen 9999;
        location / {
            content_by_lua_block {
                local events = require("resty.worker.events")
                local res, err = events.post("source", "event")
                if not res then
                    ngx.say(err)
                    ngx.exit(503)
                end

                if res ~= "done" then
                    ngx.log(ngx.ERR, "res ", res)
                end
            }
        }
    }

With the configuration above and wrk http://<IP_ADDRESS>:9999, we can see lots of "recursive" in the error log.

thx for the report @spacewander !


Pinebook Pro repository confusion

What's the difference between using this repository vs https://github.com/samueldr/wip-pinebook-pro ?  I found this initially because I was looking for where you implemented the uboot boot selection.  Thanks for your work again!

Ah, sorry! This here is an experiments repository, this is used in combination with #162 to allow "external" devices to work. I don't expect the Pinebook Pro in this repo here will ever be useful for end-users, only as dogfooding for myself in some future.
The actual "WIP" repository as you linked is where "real deal NixOS on Pinebook Pro" happens.

alright, thanks for the explanation.


docs: update stale metrics docs

Signed-off-by: yeya24<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
Some metrics labels are stale, and this PR update them.
Ⅱ. Does this pull request fix one issue?

NONE
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #972 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #972   +/-   ##
=======================================
  Coverage   46.48%   46.48%
=======================================
  Files         116      116
  Lines        6908     6908
=======================================
  Hits         3211     3211
  Misses       3440     3440
  Partials      257      257

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 6bc8da9...da13b91. Read the comment docs.

LGTM.


Inconsistent Word-Spacing

The word-spacing across the website seems to be inconsistent. Look at this skill for example. Some of the words are way more spaced out than others, yet they both only have one space between them.

This is intentional. It uses text-align: justify . Hence, the space between the words adjusted automatically to fill the line.

For anyone looking at this in the future if you want consistent spacing change the following code in style.css.
.card-body{
    text-align: left
}


ClassNotFoundException when applying custom plugin

Expected Behavior
A custom plugin should be able to refer to a potentially missing class if guarded by a target.pluginManager.withPlugin statement.
Current Behavior
When Gradle tries to apply the plugin a java.lang.ClassNotFoundException is found if the optional dependency is not found on the classpath.
Context
We have a custom plugin that helps us configure the Kotlin Gradle Plugin. The plugin looks like this:
target.pluginManager.withPlugin("org.jetbrains.kotlin.jvm") {
    target.extensions.configure(JavaPluginExtension::class.java) {
        it.sourceCompatibility = JavaVersion.VERSION_1_8
        it.targetCompatibility = JavaVersion.VERSION_1_8
    }
    target.tasks.withType(KotlinCompile::class.java).configureEach {
        it.kotlinOptions.configure()
    }
}
target.pluginManager.withPlugin("org.jetbrains.kotlin.android") {
    target.extensions.configure(JavaPluginExtension::class.java) {
        it.sourceCompatibility = JavaVersion.VERSION_1_8
        it.targetCompatibility = JavaVersion.VERSION_1_8
    }
    target.extensions.configure<BaseExtension>("android") { android ->
        android.kotlinOptions.configure()
    }
}
target.pluginManager.withPlugin("org.jetbrains.kotlin.kapt") {
    target.extensions.configure<KaptExtension>("kapt") {
        it.includeCompileClasspath = false
    }
}

The plugin support many types of Kotlin plugins among them is the Kotlin plugin for Android. Our plugin has a compileOnly dependency on the Android Gradle Plugin since not all consumers use Android. For these consumers the second config block should never be executed but when using Gradle 7+ applying the plugin causes an exception when Gradle tries to scan the plugin:
Caused by: java.lang.NoClassDefFoundError: com/android/build/gradle/BaseExtension
        at org.gradle.internal.reflect.ClassInspector.inspectClass(ClassInspector.java:70)
        at org.gradle.internal.reflect.ClassInspector.visitGraph(ClassInspector.java:56)
        at org.gradle.internal.reflect.ClassInspector.inspect(ClassInspector.java:36)
        at org.gradle.internal.instantiation.generator.AbstractClassGenerator.inspectType(AbstractClassGenerator.java:272)
        at org.gradle.internal.instantiation.generator.AbstractClassGenerator.generateUnderLock(AbstractClassGenerator.java:211)
        ... 247 more
Caused by: java.lang.ClassNotFoundException: com.android.build.gradle.BaseExtension
        ... 252 more

Steps to Reproduce
To reproduce you need to create a library project that refers to some dependency using compileOnly and some class in that dependency should be referenced inside a pluginManager.withPlugin block.
The consumer should then try to apply this plugin.
Your Environment
This is using Gradle 7.3

Sorry that you're having trouble with Gradle!
Your issue lacks information about how to reproduce the problem you're having. A reproducer project can really help us track down and fix your problem quicker.  We may also be able to suggest workarounds or ways to avoid the problem if we can reproduce it.
This issue will be closed after 7 days, unless you can provide more information.
Also, could you please try reproducing the issue without the configuration cache enabled?

I had the same issue with a custom plugin in the android app. My plugin was in buildSrc, it had AGP compileOnly dependency as:
dependencies {
    compileOnly("com.android.tools.build:gradle:7.3.0")
}

and I was applying this plugin on my android library module so the library module for sure had AGP in the classpath. I was getting:
Caused by: java.lang.NoClassDefFoundError: com.android.build.api.variant.LibraryAndroidComponentsExtension

during the gradle sync. Plugin code:
class MyPlugin : Plugin<Project> {
    override fun apply(target: Project) {
        with(target) {
            val extension = extensions.getByType<LibraryAndroidComponentsExtension>() // fails here
        }
    }
}

I was able to resolve it by moving the plugin from buildSrc into a standalone module build-logic and having this module as included build:
pluginManagement {
    ...
    includeBuild('build-logic')
}

It solved the issue with no other code changes, only by moving it out of buildSrc. Hope it will help someone but would be great to get the explanation from the Gradle team on the root of the issue.

We appreciate the effort that went into adding details to this issue, but we must ask for more information.
As stated in our issue template, a minimal reproducible example is a must for us to be able to track down and fix your problem efficiently. Our available resources are severely limited, and we must be sure we are looking at the exact problem you are facing.
If we have a reproducer, we may be able also to suggest workarounds or ways to avoid the problem.
The ideal way to provide a reproducer is to leverage our reproducer template. You can also use Gradle Project Replicator to reproduce the structure of your project.

I also happen to the problem
when write plugin at buildSrc and depency     dependencies {
compileOnly("com.android.tools.build:gradle:7.3.0")
}


Should allow chaining?

If h and t could return the HTML element we could allow chaining.

Made a test for it at brsrkr repo


@ActionSpec should only need to be attached to top level.

@ActionSpec should only need to be attached to top level but this this property is not tested.
And FSM related tests are giving it to all the overriding methods.
public enum IncorrectSpec implements FSMSpec<ModifiedMealyMachine> {
  @StateSpec I {
  },
  @StateSpec S {
    @ActionSpec // <-- This is not necessary
    public Expectation<ModifiedMealyMachine> getS(Expectation.Builder<ModifiedMealyMachine> b) {
        ....
    }

    @ActionSpec // <-- This is not necessary
    public Expectation<ModifiedMealyMachine> getI(Expectation.Builder<ModifiedMealyMachine> b) {
      return b.valid(S).build();
    }
  };

...

  @ActionSpec(alias="method")
  public Expectation<ModifiedMealyMachine> method(Expectation.Builder<ModifiedMealyMachine> b, String s) {
    ...
  }

This issue was not reproducible and test was added for this issue. (See Issue39Test.java).


Vocabulary::update() does not update descriptions

https://github.com/habari/system/blob/master/classes/vocabulary.php#L236 prevents a vocabulary with a new description (or any other field) from being updated if the name has not.

not a bug, I was setting vocabulary->name to the existing value. Careful coding - just setting the field to be updated - should prevent problems.


Release Boosted 5.1.0

Tasks

[x] Bootstrap proposal PR has been merged so I can keep my modification in this PR. One less thing to merge the next time :)
[ ] Show to the designers Add new offcanvas support to navbars

Asked for a feedback the 24th of August

[ ] Remove in all *.md files aria-label="Close" and replace it by Close inside the buttons
[ ] At the end, regenerate the package-lock.json

Yeah, I just recreate it:
git clean -dfx
rm package-lock.json or del package-lock.json
npm i
Just be careful because in some cases the package ranges in package.json will install a newer version (at the time of writing autoprefixer for example). In those cases, just temporarily pin the dep.
This is needed unfortunately because when using dependabot over time the package-lock.json file becomes bloated. I haven't switched to npm 7.x to see if the issue is fixed there.

[ ] Show to the designers the new "Placeholders" component

Asked for a feedback the 24th of August

[ ] Fix d4664f4913843f9f099ed7081fcedcd58736fe87 from e72916e5b741b07b94b12b3707129e868811bdbb: work to do on text/background opacities

Release

[ ] Run linters;
[ ] Run compilers;
[ ] Run tests;
[ ] Check documentation site: examples and contents;
[ ] Test cross-browser compatibility locally and with BrowserStack:

Firefox ESR
IE11 (v4 only)
Latest Edge, Chrome, Firefox, Safari
iOS Safari
Chrome & Firefox on Android

[ ] Including RTL mode;
[ ] Ask for reviews and accessibility testing;
[ ] sync with Bootstrap's release and probably wait for it;
[ ] npm run release-version $current_version $next_version to bump version number

if bumping a minor or major version:

[ ] Manually change version_short in package.json
[ ] Add docs version to _data/docs-versions.yml
[ ] Manually change docs_version in _config.yml
[ ] Update redirects in docs frontmatter
[ ] Move docs to the new docs' subfolder?
[ ] Ensure Algolia indexes new release content (probably requires a PR)

check wrong matches in CHANGELOG.md, and maybe site/content/docs/<version>/migration.md
:warning: check the package-lock.json content, only "boosted" should have its version changed!

[ ] if year changed recently, happy new year :tada: but please change © year in .scss main files (reboot, grid, utilities and main file) as well as in NOTICE.txt.
[ ] npm run release to compile dist, update SRI hashes in doc and package the release
[ ] Prepare changelog:

install Conventionnal Changelog and conventional-changelog-cli globally
run conventional-changelog -p angular -i CHANGELOG.md -s
and probably maintain a ship list (eg for v4.4.0)

[ ] commit and push dist with a chore(release) commit message
[ ] merge (on v4-dev or v5-dev)
[ ] tag your version, and push your tag
[ ] create a GitHub release:

attach zip file
paste CHANGELOG / Ship list in the release's description

[ ] run build/ship.sh x.x.x to… (v4 only)

Pull the latest changes update new version numbers
Compile CSS and JS
Compress dist files
Generate the hashes and update our config's cdn section
Compile the docs
Copy-pasta built docs to bs-docs-named clone of Boosted.

[ ] npm pack then npm publish

if you are already logged in NPM (with a personnal account, for example), you'd better use a repository scoped .npmrc file
if you're releasing a pre-release, use --tag, eg for v5-alpha1 npm publish boosted-5.0.0-alpha1.tgz --tag next

[ ] publish on Nuget
[ ] check release on NPM, Nuget, Packagist…
[ ] publish documentation on gh-pages:

[ ] copy ../_site (v5-dev) or ../bs-docs (v4-dev) to the gh-pages branch
[ ] check every index.html used as redirections to be redirecting to the new release
[ ] when bumping minor version: ensure dist URLs in examples' HTML has changed
[ ] double-check everything before pushing, starting by searching for forgotten old version number occurences

[ ] make an announcement in Plazza :tada:

[ ] Bootstrap proposal PR
[ ] Show to the designers Add new offcanvas support to navbars

Just coming back and seeing commit names, what is it with them ? These are Bootstrap commits ?

Just coming back and seeing commit names, what is it with them ? These are Bootstrap commits ?

Yep, it is easier to track for me during the development and for the review.

https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/pull/772/commits/c5d150832f4d28005acba383d73025584ecd449c fixes pa11y issues. Here is my proposal:

Fix in Boosted of the 2 main issues regarding the documentation
Fix proposal in Bootstrap for those 2 issues
Ignore the errors coming from the Bootstrap examples (not yet Orange-ified) by adding .exclude-from-pa11y-analysis:

Dropdowns: 19 errors
Footers: 13 errors
List groups: 12 errors
Modals: 2 errors

The main goal of my proposal is to have a "green" pa11y for the main branch and to create an issue to remove the .exclude-from-pa11y-analysis hack from the examples by Orange-ify the examples or fix the issues directly within Bootstrap if possible.

Find in https://deploy-preview-772--boosted.netlify.app/docs/5.0/layout/css-grid/#customizing
--bs-gap fallback mention 1.5rem, but in boosted it's 1.25 because gap use grid-gutter-widthvariable
gap: var(--#{$variable-prefix}gap, #{$grid-gutter-width});

We need to update the doc


allow mapping color palette

expose some way of instead of using the default color.
so i can change green (etc) to be light green, or even a completely different color.
currently i can just .replace("#color", "#color") but yeah..

never mind it seems that you can use a style sheet

never never mind it seems the style sheet thing is for like "terminal" styling

I've actually been meaning to open an issue about this same feature! (It's one of the reasons I wanted a to-html config file)
My use case is that currently the styling will generate something like this
$ to-html 'ls --color'

> ls --color
file.txt  dir
>

where the color blue is hard-coded through . For my use case I would like it to be  instead
I was thinking that we could handle all the 4-bit colors by adding a section to the config like so
[color]  # alias for [colour] as well
black.attr = "<attr-value>"
# The same for all other 4-bit colors

So I could handle the above by setting
[color]
black.class = "term-black"
red.class = "term-red"
# ...
bright-black.class = "term-bright-black"
bright-red.class = "term-bright-red"
# ...

This doesn't handle 8 or 24 bit colors, but it seems so much less likely that someone would want to customize them that I think we could just kick the can on handling it. Could probably be something like
[color]
eight_bit = [
    ["16", { attr = "<attr-value>" }],
    # ...
]

I don't think the color values should be configurable by hand, but using CSS classes rather than inline styles makes sense.
I'd like having a flag, --color-classes, for producing class="red" instead of style="color:#f00".
The --prefix flag can be used here as well, so you can write --color-classes --prefix=term to get class="term-red".
I initially went with the hard-coded color values to make to-html very easy to use out of the box, with no setup. This is insufficient when you want to customize it, but it should still be intuitive and easy to use, so I think CSS classes make the most sense here.

That sounds like a nice simple solution 👍
I can give the implementation a shot sometime later this week unless someone else wants to handle it

Thanks! BTW I'm against customizing 8 bit or 24 bit colors; these correspond to specific sRGB values, and unlike 3/4 bit colors, usually aren't customizable in terminals either.

I use the library, not the CLI, so can there be a flag there too?

I use the library, not the CLI, so can there be a flag there too?

Yup, that's where the core functionality will have to live 👍

@bend-n interesting, may I ask what you use it for?

A html terminal panel thing which is dark-theme'd.


Creating a computer account fails

Dear all,
I tried to create a machine catalog using the provider and I face the following error:
│   with citrix_machine_catalog.AAA-TF,
│   on machine_catalog.tf line 1, in resource "citrix_machine_catalog" "AAA-TF":
│    1: resource "citrix_machine_catalog" "AAA-TF" {
│
│ TransactionId: 4e2e6eab-a195-4091-9998-64a4447217f9
│ JobId: f5f8b338-9e11-4901-a351-a82ddb70ad7a
│ Error message: Failed to create a computer account SDNE20001, due to an unknown error.
I successfully created a machine catalog manually with the same parameters.
May I ask you to check please?
Thanks,
Steven

Hi @SLemonier,
From the logs, there seems be a problem authenticating to the domain. Can you make sure you are using the correct username and password and that the password hasn't expired.
Thanks,
Aneesh

I am 100% sure, I used the same account to manually create the machine catalog.

@SLemonier What is the format of the input that you are passing in for the service_account? Please note that we only expect the username and not domain\username.
Thanks,
Anessh

Ah correct, I removed domain\ but now it failed with:
│ TransactionId: ce0ee8ba-9869-4122-9c41-4e63cce7e86b
│ JobId: a0bd4666-a98c-4ad9-95f9-8501a17dc796
│ Error message: Failed to create the virtual machine; RCCAD\SDNE20002$.

@SLemonier,
The error I see is - You do not have access to a default security group in VPC vpc-05d0f96b3f84d67ee. Specify a security group, and try again.
Can you share your tf config for machine catalog? Specifically, we are looking for network_mapping.

I used this code for the network_mapping:
network_mapping = {
network_device = "0"
network = citrix_aws_hypervisor_resource_pool.NPRD-RIC-EUC-1A-TF.subnets[0]
}

What is the value for network?

@SLemonier Can you also make sure the service account you provided to create the hypervisor has enough permissions to perform write operation on the security group for the VPC and VPC subnet you are using.

@SLemonier When you use Studio UI to create machine catalog, what do you choose in the Security section. Is it default or something else?

I use default choice:


The documentation guide lacks explanation of how to execute the query method.

Background

I am using Kotlin JDSL for the first time and find that the documentation could be clearer in its explanation. Therefore, I want to modify and improve the clarity of this particular section.
Object

improve the clarity of this particular section.
Benefits

The description of "Execute the query section" is clearer, so users can easily follow it.

The following is the revised sentence that I want.
## Execute the query

After building the query, you can use `RenderContext` to execute the query.
For example, you can use `JpqlRenderContext` to execute the query:

```kotlin
val render = JpqlRenderer()

val context = JpqlRenderContext()

val rendered = render.render(query, context)

val jpaQuery: Query = entityManager.createQuery(rendered.query, query.returnType.java)

val result = jpaQuery.resultList

JpqlRender is a class that renders the query as String.
his class extracts the query and parameters from the RenderContext and renders them as String.
RenderContext has elements for rendering the query as String.
Kotlin JDSL provides JpqlRenderContext as the default RenderContext for the JPQL.
Creating RenderContext is expensive, so the Kotlin JDSL recommends creating it once and reusing it afterward.
Since RenderContext is immutable, you can access RenderContext from multiple threads.
Spring Support
if you want to use Kotlin JDSL comfatable with Spring, please see Spring Support.

thank you

Hi ilgolf. Thank you for your interest in Kotlin JDSL.
I like the way you've written it - it shows how to execute the query, but also explains the core components that Kotlin JDSL provides.
I will update the documentation today based on what you wrote!

I've added the content to the docs, if there's anything else you'd like to see added, please open a new issue or reopen this issue.


ChatQnA data prep failed to upload .doc file

I bring up the ChatQnA pipeline with data prep on Xeon and then i tried to upload a plain .docx file without image. The upload failed and response with such error:
files:UploadFile(filename='Understanding Cloud Computing.doc', size=39424, headers=Headers({'content-disposition': 'form-data; name="files"; filename="Understanding Cloud Computing.doc"', 'content-type': 'application/msword'}))
link_list:None
Parsing document ./uploaded_files/Understanding Cloud Computing.doc.
Converting doc file to docx file...
Converted doc file to docx file.
INFO:     <IP_ADDRESS>:52028 - "POST /v1/dataprep HTTP/1.1" 500 Internal Server Error
ERROR:    Exception in ASGI application
Traceback (most recent call last):
File "/home/user/.local/lib/python3.11/site-packages/uvicorn/protocols/http/httptools_impl.py", line 399, in run_asgi
result = await app(  # type: ignore[func-returns-value]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/.local/lib/python3.11/site-packages/uvicorn/middleware/proxy_headers.py", line 70, in call
return await self.app(scope, receive, send)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/.local/lib/python3.11/site-packages/fastapi/applications.py", line 1054, in call
await super().call(scope, receive, send)
File "/home/user/.local/lib/python3.11/site-packages/starlette/applications.py", line 123, in call
await self.middleware_stack(scope, receive, send)
File "/home/user/.local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 186, in call
raise exc
File "/home/user/.local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 164, in call
await self.app(scope, receive, _send)
File "/home/user/.local/lib/python3.11/site-packages/prometheus_fastapi_instrumentator/middleware.py", line 174, in call
raise exc
File "/home/user/.local/lib/python3.11/site-packages/prometheus_fastapi_instrumentator/middleware.py", line 172, in call
await self.app(scope, receive, send_wrapper)
File "/home/user/.local/lib/python3.11/site-packages/starlette/middleware/cors.py", line 93, in call
await self.simple_response(scope, receive, send, request_headers=headers)
File "/home/user/.local/lib/python3.11/site-packages/starlette/middleware/cors.py", line 148, in simple_response
await self.app(scope, receive, send)
File "/home/user/.local/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 65, in call
await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
File "/home/user/.local/lib/python3.11/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
raise exc
File "/home/user/.local/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
await app(scope, receive, sender)
File "/home/user/.local/lib/python3.11/site-packages/starlette/routing.py", line 756, in call
await self.middleware_stack(scope, receive, send)
File "/home/user/.local/lib/python3.11/site-packages/starlette/routing.py", line 776, in app
await route.handle(scope, receive, send)
File "/home/user/.local/lib/python3.11/site-packages/starlette/routing.py", line 297, in handle
await self.app(scope, receive, send)
File "/home/user/.local/lib/python3.11/site-packages/starlette/routing.py", line 77, in app
await wrap_app_handling_exceptions(app, request)(scope, receive, send)
File "/home/user/.local/lib/python3.11/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
raise exc
File "/home/user/.local/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
await app(scope, receive, sender)
File "/home/user/.local/lib/python3.11/site-packages/starlette/routing.py", line 72, in app
response = await func(request)
^^^^^^^^^^^^^^^^^^^
File "/home/user/.local/lib/python3.11/site-packages/fastapi/routing.py", line 278, in app
raw_response = await run_endpoint_function(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/.local/lib/python3.11/site-packages/fastapi/routing.py", line 191, in run_endpoint_function
return await dependant.call(**values)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/.local/lib/python3.11/site-packages/langsmith/run_helpers.py", line 461, in async_wrapper
raise e
File "/home/user/.local/lib/python3.11/site-packages/langsmith/run_helpers.py", line 450, in async_wrapper
function_result = await asyncio.create_task(  # type: ignore[call-arg]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/comps/dataprep/redis/langchain/prepare_doc_redis.py", line 141, in ingest_documents
ingest_data_to_redis(
File "/home/user/comps/dataprep/redis/langchain/prepare_doc_redis.py", line 53, in ingest_data_to_redis
content = document_loader(path)
^^^^^^^^^^^^^^^^^^^^^
File "/home/user/comps/dataprep/utils.py", line 290, in document_loader
return load_doc(doc_path)
^^^^^^^^^^^^^^^^^^
File "/home/user/comps/dataprep/utils.py", line 142, in load_doc
text = load_docx(docx_path)
^^^^^^^^^^^^^^^^^^^^
File "/home/user/comps/dataprep/utils.py", line 149, in load_docx
doc = docx.Document(docx_path)
^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/.local/lib/python3.11/site-packages/docx/api.py", line 27, in Document
document_part = cast("DocumentPart", Package.open(docx).main_document_part)
^^^^^^^^^^^^^^^^^^
File "/home/user/.local/lib/python3.11/site-packages/docx/opc/package.py", line 127, in open
pkg_reader = PackageReader.from_file(pkg_file)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/.local/lib/python3.11/site-packages/docx/opc/pkgreader.py", line 22, in from_file
phys_reader = PhysPkgReader(pkg_file)
^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/.local/lib/python3.11/site-packages/docx/opc/phys_pkg.py", line 21, in new
raise PackageNotFoundError("Package not found at '%s'" % pkg_file)
docx.opc.exceptions.PackageNotFoundError: Package not found at './uploaded_files/Understanding Cloud Computing.docx'

Though this is different with issue opea-project/GenAIComps#407, but it could be related too. @Ruoyu-y do you mind uploading your test docx file here?

Sure. Please find the document here.
Understanding Cloud Computing.docx

Hi @Ruoyu-y , Understanding Cloud Computing.docx you shared can't be opened by word, and I also got below error message which makes sense to me

I created a new docx file (test_hy.docx in below picture) removing all unrecognized characters from Understanding Cloud Computing.docx, and it can be uploaded successfully

Please try with the latest code and a normal .docx file that can be opened by word, and let us know if you still face issues.

Hi, sorry for the confusion. I am originally uploading the .doc file. Due to github attach restrictions, i manually changed the .doc to .docx. And now, i can still find the same problem using the new code.
A new .doc file is attached in zip. Please check.
Understanding Cloud Computing.zip

Hi @Ruoyu-y , the issue is due to lacking of libreoffice in container when uploading .doc files. Please try https://github.com/opea-project/GenAIComps/pull/542

Thanks


macOS: Realm Environment Injection Crashes Preview

How frequently does the bug occur?
Always
Description
Injecting a realm into a view as an environment value crashes preview.
Stacktrace & log output
From Preview

== PREVIEW UPDATE ERROR:

    CrashReportError: Fatal Error in SwiftUI.swift

    Realm SwiftUI macOS crashed due to fatalError in SwiftUI.swift at line 1422.

    'try!' expression unexpectedly raised an error: Error Domain=io.realm Code=10 "Migration is required due to the following errors:

    Process: Realm SwiftUI macOS[1249]
    Date/Time: 2024-06-04 22:12:28 +0000
    Log File: <none>

Can you reproduce the bug?
Always
Reproduction Steps
This is the entire project. Note the .environment injection in #Preview causes crash. With that commented out, preview works correctly.
That piece of code is taken from the documentation here Create a Realm with Data for Previews
import RealmSwift
import SwiftUI

struct ContentView: View {
    var body: some View {
        VStack {
            Image(systemName: "globe")
                .imageScale(.large)
                .foregroundStyle(.tint)
            Text("Hello, world!")
        }
        .padding()
    }
}

#Preview {
    return ContentView()
        .environment(\.realm, ItemGroup.previewRealm)  // <----- Causes crash
}

class Item: Object, ObjectKeyIdentifiable {
    @Persisted(primaryKey: true) var _id: ObjectId
    @Persisted var itemName = ""
    @Persisted var isFavorite = false
    @Persisted var ownerId = ""
}

extension Item {
    static let item1 = Item(value: ["itemName": "fluffy coasters", "isFavorite": false, "ownerId": "previewRealm"])
    static let item2 = Item(value: ["itemName": "sudden cinder block", "isFavorite": true, "ownerId": "previewRealm"])
    static let item3 = Item(value: ["itemName": "classy mouse pad", "isFavorite": false, "ownerId": "previewRealm"])
}

class ItemGroup: Object, ObjectKeyIdentifiable {
    @Persisted(primaryKey: true) var _id: ObjectId
    @Persisted var groupName = ""
    @Persisted var items = RealmSwift.List<Item>()
    @Persisted var ownerId = ""
}

extension ItemGroup {
    static let itemGroup = ItemGroup(value: ["ownerId": "previewRealm"])

    static var previewRealm: Realm {
        var realm: Realm
        let identifier = "previewRealm"
        let config = Realm.Configuration(inMemoryIdentifier: identifier)
        do {
            realm = try Realm(configuration: config)
            let realmObjects = realm.objects(ItemGroup.self)
            if realmObjects.count == 1 {
                return realm
            } else {
                try realm.write {
                    realm.add(itemGroup)
                    itemGroup.items.append(objectsIn: [Item.item1, Item.item2, Item.item3])
                }
                return realm
            }
        } catch let error {
            fatalError("Can't bootstrap item data: \(error.localizedDescription)")
        }
    }
}

Version
10.50.1
What Atlas Services are you using?
Local Database only
Are you using encryption?
No
Platform OS and version(s)
macOS 14.2.1
Build environment
Xcode version: 15.4
Realm Database: 14.6.2
Dependency manager and version: SPM

Hey, can you share the full repro project - it appears like someone else is opening a Realm with the same identifier but a different schema, so the schema validation logic kicks in, but it's not obvious from the shared code what could be culprit.

Thanks @nirinchev. The entire project is the above code - it's local only so there would not be someone else opening the realm and there are no other apps accessing that projects directory or supporting files directory.
I do have a followup question that may lead to the solution.
Keep in mind that the project itself works, it's only the preview that's crashing
#Preview {
    return ContentView()
        .environment(\.realm, ItemGroup.previewRealm)  // <----- Causes crash
}

When a new, fresh project is first run, Realm creates the default.realm file with the objects schema. If the app is then quit, and the schema is changed in the project but the project is NOT run, the only 'code' that's doing anything is the XCode code that drives the preview with the injected .environment
The preview should only be getting it's data from the ItemGroup.previewRealm so even if the objects schema were to change, if the preview is refreshed, it would still pull data only from the realm defined in the previewRealm, right?
So what would trigger a migration if the app itself is not being run?

I can't seem to repro this with the code provided. I can see a preview with a globe and "Hello world" below it and even if I update it to read some data from the Realm file, it still works just fine. Is it possible you have another instance of Xcode/your app opening an in-memory realm with the same identifier somewhere?

@nirinchev Yes, I have the same result. However, do this: Add a property to the Item object  but DO NOT RUN the project. Let the preview refresh and it will error out.
Here's the Item object (per the original report above)
class Item: Object, ObjectKeyIdentifiable {
    @Persisted(primaryKey: true) var _id: ObjectId
    @Persisted var itemName = ""
    @Persisted var isFavorite = false
    @Persisted var ownerId = ""
}

and then add a property - do NOT run the project
class Item: Object, ObjectKeyIdentifiable {
    @Persisted(primaryKey: true) var _id: ObjectId
    @Persisted var itemName = ""
    @Persisted var isFavorite = false
    @Persisted var ownerId = ""
    @Persisted var test = ""  // added property
}

and preview crashes.

I also determined the initial bug report was somewhat inaccurate and caused by operator error.
For some reason, I was thinking additive Object Model changes were handled automatically and did not require any kind of migration. That thought was incorrect as it requires incrementing the schema version

After you add your new property to the schema, you must increment the schema version. Your Realm.Configuration might look like this:
> let config = Realm.Configuration(schemaVersion: 2)
Declare this configuration somewhere that is accessible to the first view in the hierarchy that needs it. Declaring this above your @main app entrypoint makes it available everywhere, but you could also put it in the file where you first open a realm.

Once we address the preview crash noted above, this report can be closed.

@nirinchev  I am still getting the same error as in the original post - and I am narrowing the issue and think it can be duplicated.
One thing I noted is that on a 100% clean project, using the above code, without running the project, the #Preview generates the Realm files on disk. This apparently means that during development, changing an object schema, even if the added properties are not used anywhere, will crash preview without actually running any code.

Create a new macOS app, SwiftUI

Add Realm via SPM (per the documentation)

copy and paste the code in the Content View. Do NOT run the project

Preview will not work at this point. Go to the Project Target settings and delete App Sandbox and Hardened Runtime

Upon going back to the Content View, Preview will refesh and show the globe with Hello, World. If you then look at ~/Library/Application Support/your project name, you will see the Realm files have been created - even though the app has not been run

In the ContentView file, go to the Item object model and add a property @Persisted var test = "" so it looks like this

class Item: Object, ObjectKeyIdentifiable {
    @Persisted(primaryKey: true) var _id: ObjectId
    @Persisted var itemName = ""
    @Persisted var isFavorite = false
    @Persisted var ownerId = ""
    @Persisted var test = ""  //add this
}

At that point, preview will crash with a Fatal Error

Realm_Preview_Crash_PreviewReplacement_ContentView_1/ContentView.swift:71: Fatal error: Can't bootstrap item data: Migration is required due to the following errors:
- Property 'Item.test' has been added.
]

Then, delete the realm files that were generated:

delete the folder at ~/Library/Application Support/your project name

refresh preview, and it still crashes, even though the Realm files were deleted.

I thought perhaps adding a Migration (per the documentation) would help but without running the project, that migration doesn't run either.
Evening deleting the realm folder and cleaning the build folder doesn't help.
I did the above steps 4 times with the same result - My thinking is the preview should not be accessing any files on disk as an in memory realm is being injected. It's not clear (to me) what's causing the issue or how to handle changing an object model during development and have preview work.


Develop uncertainty distributions for various parameters used in CEA

Make a database on the various parameters used in CEA and the distributions they can have i.e. the min, max, std. This can then be used to develop uncertainty analysis and figure out which of the parameters are more susceptible.

Addressed in PR572


⚠ SceneTime has degraded performance

In df7d5ed, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 13509 ms

Resolved: SceneTime performance has improved in e5ad22e.


Integrate wasm module

[x] Copied in wasm module from cosmwasm/modules
[x] Updated code to cosmos-sdk:master
[x] Wrote cli commands
[x] Integrated wasm with app
[x] Tested workflows and document in docs/deploy-testnet.md

For Admin Use:

Added appropriate labels to PR (ex. wip, ready-for-review, docs)
Reviewers Assigned
Squashed all commits, uses message "Merge PR #XYZ: [title]" (coding standards)

Codecov Report

Merging #2 into master will decrease coverage by 7.26%.
The diff coverage is 50.93%.

@@            Coverage Diff            @@
##           master      #2      +/-   ##
=========================================
- Coverage   66.46%   59.2%   -7.27%
=========================================
  Files           5      11       +6
  Lines         501     929     +428
=========================================
+ Hits          333     550     +217
- Misses        137     329     +192
- Partials       31      50      +19

Impacted Files
Coverage Δ

x/wasm/genesis.go
0% <0%> (ø)

x/wasm/internal/keeper/querier.go
0% <0%> (ø)

x/wasm/internal/keeper/test_common.go
100% <100%> (ø)

app/app.go
88.88% <100%> (+0.42%)
:arrow_up:

x/wasm/module.go
18.6% <18.6%> (ø)

x/wasm/internal/keeper/keeper.go
57.59% <57.59%> (ø)

x/wasm/handler.go
80.59% <80.59%> (ø)

... and 3 more

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 801630d...a3e7c30. Read the comment docs.


MuiPickersUtilsProvider with Other Context Providers

I am currently working on combining the DatePicker with other Chakra UI components into a single library, and I have found that Chakra's ThemeProvider does not play nicely with MuiPickersUtilsProvider. When the two coexist in a Storybook, they kill the browser.
Are there workarounds? Like another way to supply the date functionality? Or is it simply that MUI's DatePicker isn't an option for me?

@neilchaudhuri Do you have a reproduction? It should be working fine.

Thanks for the quick response. I will need some time to create a reproduction since I am not allowed to share the source, but it shouldn't take long. Basically an app that looks like
<ThemeProvider theme="theme.js">
   <MuiPickersUtilsProvider utils={...}><DatePicker...></DatePicker></MuiPickersUtilsProvider>
</ThemeProvider>

...in Storybook. And who knows? It could be a weird issue in Storybook.
Anyway, please feel free to close this issue for now, and I can reopen once I make a reproduction and figure out I didn't do anything silly, which is also quite possible.

I played around a bit and things seem to be peacefully coexisting. Thanks.


Fixes #4931 : change the algorithm in the getDesciptions method

Description (required)
Fixes #4931 : changed the algorithm in the getDesciptions method and added unit tests for it
The original algorithm uses commas to separate descriptions which causes bugs when there are commas inside descriptions.
The algorithm is changed to repeatedly matching string patterns of {{languageCode|desciption}}
Tests performed (required)
Tested ProdDebug on HUAWEI HMA_AL00 with API level 29.

Oops, the build failure seems to be related to issue #4927

If the only CI failure is the invalid resource directory, we can go ahead and merge probably.

Would you mind rebasing (or pulling) from master? We just fixed a problem that was preventing Continuous Integration from running.
Thanks!

Would you mind rebasing (or pulling) from master? We just fixed a problem that was preventing Continuous Integration from running. Thanks!

No problem 😃


Use Tether's addTargetClasses option instead of manually removing classnames

As of Tether 0.7.1 (May 2015) - we introduced addTargetClasses, which prevents adding any classnames to the target el when false.  I confirmed this with the visual tests, but can add a unit test if helpful.
I found the issue referenced in the comment and will resolve, sorry that got lost.
Thanks so much for incorporating Tether!

\cc @fat

Thanks so much for incorporating Tether!

Thanks so much for maintaining Tether! Our hand-rolled positioning logic was getting pretty hairy and yet still wasn't bug-free; we were quite glad to be able to nuke it in favor of Tether.

oh this is fire

@lincolndbryant sorry took so long to get this in - thanks for the help!

:smile:


Closes #1808 : Fix android.view.InflateException on pre lollipop devices

Description

The crash occurred on pre lollipop devices since vector drawable was used in in the XML file (            android:drawableRight="@drawable/ic_arrow_drop_down")
Removed this line from the XML and added the drawable right in the activity, which fixes this crash.

Related issues and discussion
Fixes #1808
Checklist
Make sure you've done all the following (You can delete the checklist before submitting)

[x] Apply the AndroidStyle.xml style template to your code in Android Studio.
[x] Code is well documented
[x] Include unit tests for new functionality
[x] All user-visible strings are made translatable
[x] Code passes Travis builds in your branch
[x] If you have multiple commits please combine them into one commit by squashing them.
[x] Read and understood the contribution guidelines.

Hey @huzaifaiftikhar,
Your changes look good to me!


Add BlockSchema HTTP client and struct model

Closes https://github.com/PrefectHQ/terraform-provider-prefect/issues/172

Was getting an error from pre-commit:
$ g cm
Terraform fmt........................................(no files to check)Skipped
go fmt...................................................................Passed
go vet...................................................................Passed
go imports...............................................................Passed
validate toml........................................(no files to check)Skipped
golangci-lint............................................................Failed
- hook id: golangci-lint
- exit code: 1

internal/client/block_documents.go:178:46: the given struct should be annotated with the `json` tag (musttag)
        if err := json.NewDecoder(resp.Body).Decode(&blockDocumentAccess); err != nil {
                                                    ^

I suspect this came from https://github.com/PrefectHQ/terraform-provider-prefect/pull/178, but surprised pre-commit / CI didn't complain about it.
Do you get this error locally, too @parkedwards? I did kind of wonder how the unmarshaling would work since we don't have struct tags on those types 🤔

@mitchnielsen what the heck - so when I was dev-ing on #178 , I did run into this linting error
the issue is actually with this struct, but it's (1) nested in the BlockDocumentAccess, (2) I added a nolint comment, and (3) the BlockDocumentAccess struct does have struct tags
i think i upgraded my golangci-lint binary to get around this - what version are you running?
➜ golangci-lint --version
golangci-lint has version 1.59.0 built with go1.22.3 from 2059b18 on 2024-05-25T11:38:08Z

i think i upgraded my golangci-lint binary to get around this - what version are you running?

Ah interesting, I have this version from Homebrew (which it says is the latest available to it):
golangci-lint has version 1.58.1 built with go1.22.3 from dc28153 on 2024-05-07T23:17:27Z
I've been thinking we might benefit from using asdf or mise so we can track the tool versions in a file that we commit to the repo so we're all on the same page.

https://golangci-lint.run/product/changelog/#1582:

musttag: from 0.12.1 to 0.12.2

https://github.com/go-simpler/musttag/releases/tag/v0.12.2:
https://github.com/go-simpler/musttag/commit/5b5f6e32a8fa90b185daf7f30aeed01157a26656 fix: check whether a pointer-type implements a Marshaler interface (https://github.com/go-simpler/musttag/pull/94)
That seems to be what fixed it, since updating to golangci-lint 1.59.0 fixed that musttag check 👍🏼

ok phew, my sanity is restored 💆


added some simple lables to contact form

Fixes issue 85
Changes proposed in this pull request:

Added labels to contact form with using already had classes (Let me know if not what was required or I can help elsewhere on this issue)

It seems good, in that it does have the labels visible while a user is filling out the form. I'm not sure how heavily the accessibility is the goal on this specific issue. It may be worth the time to go through this article about accessibility in forms. I perused through, but didn't look very closely. One of the things that is mentioned is that nesting inputs inside of labels is good in that it implicitly associates the two tags, which may be necessary when you can't know an id coming from an API or some other situation, but it is sometimes not handled well by assistive technologies.
Also, as a general tip, if you put the # symbol before the issue number, it will actually connect the two. For example: Fixes #85. And you can do this directly in commit messages, as well as pull requests.

Thanks ticet11 for the article and the tip on linking the issue to the PR! I was just using the React docs on how they specified how to use the label tag, though it didn't provide how screenwriters or accessibility tool would handle it.

@gleekzorp It looks to me like he may have formatted it with a slightly different configuration than was previously used, because it marked the whole file as changed, but it looks like both sides are the same.

Hey Guys!
All I did was run the npm install and add no extra dependencies, I am happy to start this whole PR over and try again with the accessibility features?

Closing, please see new PR.
https://github.com/code-experiment/code-experiment-website/pull/88


bazel can not compile Tensorflow with GCC 6.2.1

When I launch
"bazel build  -c opt --jobs=10 tensorflow/tools/pip_package:build_pip_package"
to compile tensorflow from source ,it crashed at:
"external/com_googlesource_code_re2/BUILD:11:1: C++ compilation of rule '@com_googlesource_code_re2//:re2' failed: gcc failed: error executing command /usr/bin/gcc -U_FORTIFY_SOURCE '-D_FORTIFY_SOURCE=1' -fstack-protector -Wall -Wl,-z,-relro,-z,now -B/usr/bin -B/usr/bin -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-canonical-system-headers ... (remaining 32 argument(s) skipped): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1.
external/com_googlesource_code_re2/re2/dfa.cc: In constructor 're2::DFA::State::State()':
external/com_googlesource_code_re2/re2/dfa.cc:95:10: error: unknown array size in delete...
"
Here are some relative infos:
1)bazel label: 0.3.1- (@non-git)
2)gcc (GCC) 6.2.1 20160830
3)tensorflow is the latest master branch
Can you tell me how to configure bazel with clang(not cross compile) ? Thanks.

https://github.com/google/re2/issues/102  or https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70932

Looks related to a gcc bug. Assigning an owner from our side to track this until the gcc bug is fixed.

This was fixed in https://github.com/tensorflow/tensorflow/commit/7ea4e2f


Add contracts analysis for fundraising

This adds a page that shows our fundraising projections and historical contract analysis. It builds off of a visualization that @jmunroe built and adds some extra visualizations etc.
It replaces our finances.md page, because that page was no longer reflective of reality given degradation of the CS&S data we'd been using.
It also adds a little helper package to create visualizations that match 2i2c's brand, called twoc :-)

Merging this in to see if it builds properly


[question] How to show the correct ticks when I use the customFormat function

  { //block a
          lineChart1.xAxisFormat('custom')
          .xAxisCustomFormat('%dday')
  }

  { //block b
       lineChart1.xTicks(2)
  }

  the performance I expected is use customFormat with block a
  but it shows different with not using the customFormat, it shows
  more ticks which is I don't expect..

  I try to call the xTicks api in block b, but it shows less ticks
  so how to show the same ticks as not using the customFormat model?

code:
https://codepen.io/Dieber/pen/opJZGq

Hi @Dieber , did this work for you?


ValueError: invalid literal for int() with base 10: 'dev0'

I use pip to install mitmproxy, when I start it, it occur an error:
Traceback (most recent call last):
  File "/usr/local/bin/mitmproxy", line 9, in <module>
    load_entry_point('mitmproxy==0.13', 'console_scripts', 'mitmproxy')()
  File "/usr/local/lib/python2.7/dist-packages/libmproxy/main.py", line 42, in mitmproxy
    netlib.version_check.version_check(version.IVERSION)
  File "/usr/local/lib/python2.7/dist-packages/netlib-0.13.1-py2.7.egg/netlib/version_check.py", line 32, in version_check
    v = tuple([int(x) for x in OpenSSL.__version__.split(".")][:2])
ValueError: invalid literal for int() with base 10: 'dev0'

Did I miss something not install?

Thanks for the report! Looks like you have installed pyOpenSSL from master, which breaks our version detection, which is a workaround for broken Python packaging on OSX, which is outside of our control. I'll fix the version detection on master. As an alternative workaround, you can switch to a regular version of pyopenssl.


v0.3.0 examples somewhat broken

Glad to see an update with simplified syntax and improved docs! But just FYI in case nobody noticed, there's something wrong with the examples. For instance, this is how the final example in the docs renders:

The axis labels are off and the whole map is too zoomed in so it looks rectangular instead of round. Everything renders the same way when I cut & paste the code and try it myself.

@SimonDanisch I don't know what happened. All examples are actually broken: http://juliaplots.org/GeoMakie.jl/dev/#Surface-example  When I originally opened the PR, the examples looked like this:

for the scatter and surface examples respectively (ignore that surface is dark because of the different shading keyword)

Same for me. I think is the refactor of autolimits done recently by Simon.  I even tried to manually update the lists afterwards, but is not possible.
using GeoMakie, Proj4, GLMakie
trans = Proj4.Transformation("+proj=longlat +datum=WGS84", "+proj=wintri",
    always_xy = true)
ptrans = Makie.PointTrans{2}(trans)
# all input data coordinates are projected using this function
lons = -180:180
lats = -90:90
points = [Point2f0(lon, lat) for lon in lons, lat in lats]
rectLimits = FRect2D(Makie.apply_transform(ptrans, points))

fig = Figure(resolution = (1200, 800), fontsize = 22)
ax = GeoAxis(fig[1, 1], source = "+proj=longlat +datum=WGS84", dest = "+proj=wintri",
    title = "Projection: Winkel Tripel", coastlines = true)
limits!(ax, rectLimits) # this line does not work as expected.
fig

Yeah, if you look at the plots the ticks and the actual grid lines on the plot are in complete miss-match

So 0.16 fixes that the projection gets applied incorrectly - which means that now the current limits are getting properly projected by the PointTrans, but generate Inf values for the limits:

If one uses different limits it works:
using GeoMakie, Proj4, GLMakie
trans = Proj4.Transformation("+proj=longlat +datum=WGS84", "+proj=wintri",
    always_xy = true)
ptrans = Makie.PointTrans{2}(trans)
# all input data coordinates are projected using this function
lons = -170:30:170
lats = -80:30:80
points = [Point2f(lon, lat) for lon in lons, lat in lats]
rectLimits = Rect2f(Makie.apply_transform(ptrans, points))

fig = Figure(resolution = (1200, 800), fontsize = 22)
ax = GeoAxis(fig[1, 1], source = "+proj=longlat +datum=WGS84", dest = "+proj=wintri",
    title = "Projection: Winkel Tripel", coastlines = true, lonticks=lons, latticks=lats)
fig

Regarding the limits, I did this function, which captures almost all possible output cases.
function setlimits!(ax, ptrans; lonrange = -180:10.0:180, latrange = -90:10.0:90)
    lats = lonrange |> collect
    lons = latrange |> collect
    # avoid PROJ wrapping 180 to -180
    lons[end] = prevfloat(lons[end])
    lats[end] = prevfloat(lats[end])
    points = [Point2f(lon, lat) for lon in lons, lat in lats]
    xytrans = Makie.apply_transform(ptrans, points)
    function checkInfs(xy)
        xy[1] != Inf && xy[2] != Inf && xy[1] != -Inf && xy[2] != -Inf && xy[1] != NaN32 && xy[2] != NaN32
    end
    xytransClean = [1.25xytrans[i] for i in 1:prod(size(xytrans)) if checkInfs(xytrans[i])]
    rectLimits = FRect2D(xytransClean)
    limits!(ax, rectLimits)
end
``

Very nice function, but didn't you say @lazarusA that limits! anyways doesn't work with GeoAxis?

Yes, but is as Simon has said above. Is due to the new way the limits are set. Probably we could find the right points in the original Lon-lat system and applied them again. That should work.

Is due to the new way the limits are set

The best way would be to circumvent this new way and set limits directly from GeoMakie.jl. It is rather straightforward with your function. But I have no clue if this is even possible because I don't know the sequence of the plotting pipeline...

@SimonDanisch , can you please tell us what we can do to progress here and fix this? We cannot use your suggestion for smaller limits, -90 to 90 degrees are mandatory (at least for my applications). We also can't use the code of lazarus here, because it seems that this is a change that needs to happen on the Makie.jl side?

The projection used in Simon's example above works fine for longitude ±180 and latitude ±90 as well, so there is no need to limit that. The problem with the limits is the bulge on the left and right sides, beyond the corner coordinates. What we see is only the inside of the red rectangle:

julia> using GeoMakie, Proj4
julia> trans = Proj4.Transformation("+proj=longlat +datum=WGS84", "+proj=wintri", always_xy = true)
julia> ptrans = Makie.PointTrans{2}(trans)
julia> lons = -180:90:180
julia> lats = -90:90:90
julia> points = [Point2f(lon, lat) for lon in lons, lat in lats]
5×3 Matrix{GeometryBasics.Point{2, Float32}}:
 [-180.0, -90.0]  [-180.0, 0.0]  [-180.0, 90.0]
 [-90.0, -90.0]   [-90.0, 0.0]   [-90.0, 90.0]
 [0.0, -90.0]     [0.0, 0.0]     [0.0, 90.0]
 [90.0, -90.0]    [90.0, 0.0]    [90.0, 90.0]
 [180.0, -90.0]   [180.0, 0.0]   [180.0, 90.0]
julia> points_trans = Makie.apply_transform(ptrans, points)
5×3 Matrix{GeometryBasics.Point{2, Float32}}:
 [-1.00188f7, -1.00188f7]  [-2.00375f7, 0.0]  [-1.00188f7, 1.00188f7]
 [-5.00938f6, -1.00188f7]  [-1.00188f7, 0.0]  [-5.00938f6, 1.00188f7]
 [0.0, -1.00188f7]         [0.0, 0.0]         [0.0, 1.00188f7]
 [5.00938f6, -1.00188f7]   [1.00188f7, 0.0]   [5.00938f6, 1.00188f7]
 [1.00188f7, -1.00188f7]   [2.00375f7, 0.0]   [1.00188f7, 1.00188f7]

So the bottom left corner becomes (-1f7, -1f7), the upper left (1f7, 1f7). However note that the left and rightmost points along the equator are outside that box at -2f7 and 2f7 along the x.
I'm not sure how the limits are determined, but the Rect2f function gives the correct limits if you give it all the points both before and after projection:
julia> latlonlim = Rect2f(points)
GeometryBasics.HyperRectangle{2, Float32}(Float32[-180.0, -90.0], Float32[360.0, 180.0])
julia> trans_lim = Rect2f(points_trans)
GeometryBasics.HyperRectangle{2, Float32}(Float32[-2.0037508f7, -1.0018754f7], Float32[4.0075016f7, 2.0037508f7])

For me it worked to return the change the lines 131 and 132 in axis.jl (Makie). Maybe this breaks something else, but the geoaxis should work fine.

I'm not sure how the limits are determined, but the Rect2f function gives the correct limits if you give it all the points both before and after projection:

Yes, that's exactly the problem. The current limits that is set automatically from Makie.jl is not using the appraoch you suggested, which is the same as what @lazarusA has suggested. We need to be able to set limits from withing GeoMakie.jl, but that is not possible until we revert the code in Makie.jl, i.e. do the change user @TabeaW has just suggested.

I'd really like to fix this and move my work to GeoMakie. But we also need to update to Makie.jl 0.16. At the moment nothing works:
fig = GeoMakie.Figure()
ax = GeoMakie.GeoAxis(fig[1,1]; coastlines = true)

ERROR: LoadError: UndefVarError: Transformation not defined
Stacktrace:
 [1] getproperty
   @ .\Base.jl:35 [inlined]

It doesn't even tell you where the werror is coming from... @SimonDanisch can you please provide some input of how I'd fix this Transformation error and the limits? I'm happy to put in the work, but I really don't know what to do at the moment.

I've added the limit setting function from @lazarusA to the ongoing PR #100 , but the results are still totally wrong.

Note that the function from lazaro, specifically
function geoaxis_setlimits!(ax, ptrans; lonrange = -180:10.0:180, latrange = -90:10.0:90)
    lats = Float32.(lonrange)
    lons = Float32.(latrange)
    # avoid PROJ wrapping 180 to -180
    lons[end] = prevfloat(lons[end])
    lats[end] = prevfloat(lats[end])
    points = [Point2f(lon, lat) for lon in lons, lat in lats]
    xytrans = Makie.apply_transform(ptrans, points)
    check_infs(xy) = !any(x -> isnan(x) || isinf(x), xy)
    xytrans_clean = [1.2xy for xy in xytrans if check_infs(xy)]
    rect_limits = FRect2D(xytrans_clean)
    limits!(ax, rect_limits)
end

already does what @visr says, it gives the projected points to Rect2f. Results are still nonsense, though, e.g. running the scatter example from the docs:

It looks like that function does 3 things:

Avoid coordinate wrapping with prevfloat
Filter out coordinates projected to infinity
Multiply the bounding box coordinates by 1.2

At least in this example 1 and 2 were not needed. And 3 basically scales the bounding box outside in all directions by 20%, given that the center of the box is 0, 0. So this just scales the red square a bit, but does not solve the problem generally. Also I'd like to avoid the assumtion that 0,0 is in our limits.

Well if 1, 2 are not needed, its not like anything happens wrongly in the code then. I've removed the scaling by 1.2, you are right, it incorrect. The current version
function geoaxis_setlimits!(ax, ptrans; lonrange = -180:10.0:180, latrange = -90:10.0:90)
    lats = Float32.(lonrange)
    lons = Float32.(latrange)
    # avoid PROJ wrapping 180 to -180
    lons[end] = prevfloat(lons[end])
    lats[end] = prevfloat(lats[end])
    points = [Point2f(lon, lat) for lon in lons, lat in lats]
    xytrans = Makie.apply_transform(ptrans, points)
    check_infs(xy) = any(x -> isnan(x) || isinf(x), xy)
    xytrans_clean = filter(check_infs, xytrans)
    rect_limits = FRect2D(xytrans_clean)
    limits!(ax, rect_limits)
end

still doesn't fix the issue:

For me it worked to return the change of the lines 131 and 132 in axis.jl (Makie).

I don't fully understand this change, or why it would work @TabeaW, could you elaborate? I did have a look at this place, and indeed I see that this is where the bottom left and top right corners of the limits get projected. These are the red dots here:

In this example it happens to bulge in the middle. So we can instead use the midpoints, the black dots, to project and get better limits, with this hack:
https://github.com/visr/Makie.jl/commit/34400dad10e6bc45f1cbb9913a3cc04eba040f6f
And this code
using GeoMakie, Proj4, CairoMakie

trans = Proj4.Transformation("+proj=longlat +datum=WGS84", "+proj=wintri", always_xy = true)

lons = -180:90:180
lats = -90:90:90

fig = Figure(resolution = (1200, 800), fontsize = 22)
ax = GeoAxis(fig[1, 1], source = "+proj=longlat +datum=WGS84", dest = "+proj=wintri",
    title = "Projection: Winkel Tripel", coastlines = true, lonticks=lons, latticks=lats)
fig

To get

This wouldn't work in general though, say we use a Vitkovsky I projection. For that collecting the projected limits of all the gridlines or datapoints is a better idea, but I'm not sure how to plug that in? Since right now it always transforms on the corner coordinates only.


Update setup.py

Change packages required for install as proposed in https://github.com/decile-team/submodlib/issues/35

Sorry for the confusion. This should be the right pull request. Please approve so people can install submodlib via pip as described in you readme

@krishnatejakk @vishkaush Please approve this. cant really showcase the examples if not fixed.

I have tried it out locally and for me it works perfectly fine. If you are unsure, then feel free to test it out on your machine, too. It's only one line in the setup file, so nothing crazy @vishkaush


Refactor Log activity

Refactored the Log activity to be smoother.

hi @caiofaustino, thanks for this pull request!
I tested this on an API 29 emulator, with a log file that is relatively short (after installation). As I start scrolling up, the view jumps back to the bottom before you're finished scrolling and you can't really scroll up. Any ideas?

Just force pushed adding the scrollbar to the layout.

There is still an issue with the auto scrolling I couldn't fix easily.
Basically when the log file is bigger than the max number of lines we read on the screen, 10k I guess, then the list update sort of auto scrolls any way.
For example, I'm showing lines 4, 5 and 6, now the file updates and lines 4, 5 and 6 now became 6, 7 and 8 because there were 2 new lines added. The scroll still shows lines 4, 5 and 6, which now has the content of the previous lines 2, 3 and 4.
So even though the scroll position is still, the content keeps scrolling by. I can try to add some diff logic to make the list smarter and more optimized in a future PR maybe.


Initial test of HKB only turns light on not off

Just hit what looks like the same condition that spiv described on 4/7.
Homekit can turn my switch on, but not off.   Homekit shows that the device is off, indigo doesn't show any logs for HKB.
DEVICE DATA DUMP
address : 3C.35.75
batteryLevel : None
buttonGroupCount : 1
configured : True
description :
deviceTypeId :
displayStateId : onOffState
displayStateImageSel : PowerOn
displayStateValRaw : True
displayStateValUi : on
enabled : True
energyAccumBaseTime : None
energyAccumTimeDelta : None
energyAccumTotal : None
energyCurLevel : None
errorState :
folderId : 0
globalProps : MetaProps : (dict)
id :<PHONE_NUMBER>
lastChanged : 2018-04-14 23:04:59
lastSuccessfulComm : 2018-04-14 23:04:59
ledStates : []
model : SwitchLinc Relay
name : Master Bedroom (S)
onState : True
ownerProps : emptyDict : (dict)
pluginId :
pluginProps : com.eps.indigoplugin.homekit-bridge : (dict)
protocol : Insteon
remoteDisplay : True
states : States : (dict)
     onOffState : on (on/off bool)
subModel :
supportsAllLightsOnOff : True
supportsAllOff : True
supportsStatusRequest : True
version : 69

##### DEVICE SIMULATION DATA #####

Service :
	alias : Master Bedroom (S)
	model :
	subModel :
	indigoType : indigo.RelayDevice
	pluginType : Built-In
	type : Lightbulb
	desc : Lightbulb
	objId :<PHONE_NUMBER>
	serverId :<PHONE_NUMBER>
	invertOnState : False
	convertFahrenheit : False
	required : (List)
		On : True
	optional : (List)
		Hue
		Saturation
		ColorTemperature
		Name
		Brightness
	native : True
	requiresPlugin : (List)
	actions : (List)
		Action : (HomeKitAction)
			Characteristic : On
			When : equal
			Value : False (bool)
			Value2 : 0 (bool)
			Command : device.turnOff
			Arguments : [1137988370]
			monitors : {1137988370: 'attr_onState'}
		Action : (HomeKitAction)
			Characteristic : On
			When : equal
			Value : True (bool)
			Value2 : 0 (bool)
			Command : device.turnOn
			Arguments : [1137988370]
			monitors : {1137988370: 'attr_onState'}
	loadOptional : False
	characterDict : (Dict)
		On : True

hmm.  I removed the device and the accessory from HomeKit and readded and now it seems to work

What are you doing or trying to do when you get that error?

I have the one switch added to the HKB and one accessory added in HomeKit.   I’m just toggling the light from the Home app.
I don’t see that error each time.  In fact I didn’t see it when I had the original response issue.
tdc

On Apr 15, 2018, at 7:05 AM, Colorado Four Wheeler<EMAIL_ADDRESS>wrote:
What are you doing or trying to do when you get that error?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I don’t think it’s a “bug” per se because the nature of that call would mean that if it were a deep rooted bug that you would get it every time, and so would everyone else because that is currently called each time you do anything in HomeKit with a device.  That leads me to believe it could be how the device was configured or perhaps it only is coming up under a certain circumstance, like before the plugin was restarted the first time after adding the new server in Indigo.
If it’s not happening regularly then it’ll be impossible to give you any advice as to what you can do.  If you can keep an eye on it and try to determine when it happens that will help.

I’m still seeing it.  It happens on each message from HomeKit to the server when I toggle the light.  Happy to debug further if you have ideas.
tdc

On Apr 15, 2018, at 7:13 AM, Colorado Four Wheeler<EMAIL_ADDRESS>wrote:
I don’t think it’s a “bug” per se because the nature of that call would mean that if it were a deep rooted bug that you would get it every time, and so would everyone else because that is currently called each time you do anything in HomeKit with a device. That leads me to believe it could be how the device was configured or perhaps it only is coming up under a certain circumstance, like before the plugin was restarted the first time after adding the new server in Indigo.
If it’s not happening regularly then it’ll be impossible to give you any advice as to what you can do. If you can keep an eye on it and try to determine when it happens that will help.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Colorado4Wheeler/HomeKit-Bridge/issues/103#issuecomment-381409769, or mute the thread https://github.com/notifications/unsubscribe-auth/AHvdoeqU8gBZTUjF6b7Ih7dYI7qJClYHks5to1WKgaJpZM4TVW11.

Try editing the device on the server and change the alias name to something else and see if that does anything.  The message implies that there is no alias name, which is kind of strange.

Interesting, if I rename the device, delete the bridge from HomeKit, and re-add it, it still comes up with the old name, in fact even if the device has been deleted from the bridge, it still can be seen by HomeKit.
Is there a way to get it to refresh the HomeKit list without deleting and re-adding the accessory

On Apr 15, 2018, at 2:35 PM, Colorado Four Wheeler<EMAIL_ADDRESS>wrote:
Try editing the device on the server and change the alias name to something else and see if that does anything. The message implies that there is no alias name, which is kind of strange.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Colorado4Wheeler/HomeKit-Bridge/issues/103#issuecomment-381439908, or mute the thread https://github.com/notifications/unsubscribe-auth/AHvdoQdzyrIjnjriytfP2MQ9Oc6twjPZks5to70pgaJpZM4TVW11.

Rename the device and delete the bridge and what comes back as the same name - the accessory server or the device itself?  I would delete the accessory server from HomeKit, rename the server device to something new and change the alias name of any items that are mapped and see what that does.

Right now, I’m actually not able to re-add the accessory (server) in HomeKit.  But I’ll try renaming that too.
However, the problem may because I did create an alias for my device.  Maybe it would be easier if the indigo name and the HomeKit name matched?
I did the following:
Delete the HomeKit bridge device.
Added a new HomeKit bridge device (new name)
Added the same switch, with an alias
Added to the Home app (now it showed up)
No more error logs, and the light works.
Its complicated because there are so many names for the various parts in each world.  I can keep watching for stuff though (I’m a Mac developer, so should be a bit handy ;) )
I did have an insteon related question if you know, though.  Some of my lights are connected to keypads — and from past reading, a good workflow to keep them in sync was to use an insteon scene to turn both the light / keypad on off, and I use a python script when I toggle those from the indigo control page.
Of course, with home kit, now the keypad is out of sync.  Do you think one can make a HomeKit device talk to the scene?  I’m imagining using an action script to toggle that, but I’m not quite sure how HomeKit would get the status of the device.
Otherwise, I can have a watch / trigger rule in indigo, but those never work so well.
Thanks!  This is very impressive.

On Apr 15, 2018, at 3:41 PM, Colorado Four Wheeler<EMAIL_ADDRESS>wrote:
Rename the device and delete the bridge and what comes back as the same name - the accessory server or the device itself? I would delete the accessory server from HomeKit, rename the server device to something new and change the alias name of any items that are mapped and see what that does.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Colorado4Wheeler/HomeKit-Bridge/issues/103#issuecomment-381443863, or mute the thread https://github.com/notifications/unsubscribe-auth/AHvdoZeGqUtj8ynivVePEgKULS_pkFY3ks5to8yCgaJpZM4TVW11.

Maybe it would be easier if the indigo name and the HomeKit name matched?

I'm not sure what you are asking because there is the Indigo Server Accessory Device that equates to the HomeKit Accessory and then there are the Indigo devices that are mapped to HomeKit.  For me, for over 200 devices almost none of them have the same name as Indigo's device names.

Otherwise, I can have a watch / trigger rule in indigo, but those never work so well.

That's the only way to really do that.  I also use KPL's and I have a trigger that detects when a light goes on or off and then runs a Py script to update all linked KPL's.  It works 100% for me, not sure why your triggers don't work very well but they work perfectly for me.

Since there has been no further information on this ticket I'm assuming it's not an issue and closed.


swipeToNavigate not working

i have added  "workbench.editor.swipeToNavigate": true
restarted
do 3-finger swipe after some file navigation -> nothing happens
do 3-finger swipe in browser -> works

Electron requires this for reasons I do not fully understand (copied from https://github.com/Microsoft/vscode/issues/25325):
Note: in order for this to work you need to configure the trackpad in settings as below:

A little documentation would be helpful

This is broken since Electron 3 it seems 😱

Reported as https://github.com/electron/electron/issues/19131

I decided to pull out workbench.editor.swipeToNavigate given it has been broken for months without someone complaining and given it requires Electron API and cannot be implemented with Web API (as far as I know - if someone can implement this via Web API, fire up a PR).


Vimeo: race condition between ready state and call seekTo

Be sure to search for your issue before opening a new one.
Current Behavior

When users call seekTo for some services like Vimeo they could receive an error ReactPlayer: could not seek using fraction – duration not yet available because seekTo is depends on video duration. Receiving duration in case of Vimeo is async and it could happen a little bit later after loaded will be received.
Expected Behavior

ready state must be emitted after all required parameters will be received (at least duration)
Steps to Reproduce
You need to store played state somewhere locally and use it to call seekTo right after player will emit ready and also you must use pass playing: true to the player

Set progress to the middle of the video
Refresh page

I’m not sure what ReactPlayer can/should do about this. If you are seeking using fractions I would suggest disabling seeking in your app until onDuration has been called. Waiting for duration before calling onReady would couple the two events to tightly and just isn't necessary. Use onDuration rather than onReady if you require duration for your UI to be "ready".

Hi, @cookpete. I dont think you are right here. Library authors should strive to provide one API for all such things like different media services (in our case). So, I, like library user, don't wont to write different logic for each service (youtube, vimeo, etc) on my side

Library authors should strive to provide one API for all such things.

I agree with this, so I’m not sure I understand your point. onReady is called when the player is ready to be played. onDuration is called when the duration of the video is available. The behaviour of both are consistent across all players.
onReady is not "when seeking is ready" – it is "when the video can be played". It doesn’t (and shouldn’t) care about whether duration is ready or not. That’s what onDuration is for. If an action requires duration, you need to block/disable it until onDuration is called.


Optimizations

It would be nice if on property could be more detailed. Report to github and wait for response
Instead of issue_comment could be issue_comment.created

https://help.github.com/en/articles/contexts-and-expression-syntax-for-github-actions

Full action cannot be skipped. Only steps. In best possible way it would be nice to skip whole action. No building, no execution, no action in history.

🎉🎉🎉🎉🎉🎉🎉🎉
on:
  issue_comment:
    types: [created]

https://github.community/t5/GitHub-Actions/Running-Github-Actions-on-PRs-After-Explicit-Approval/m-p/32507/highlight/true#M1163
https://help.github.com/en/articles/events-that-trigger-workflows#issue-comment-event-issue_comment

Adoption for generic bucket, ash258, jetbrains, sysinternals is needed


Compilation of µWebSockets has failed and there is no pre-compiled binary available for your system

Is this a bug report?
Yes
I cloned a react-native project from github then ran npm run eject after then when i tried to run the app using react-native run-android i am getting the below error
Compilation of µWebSockets has failed and there is no pre-compiled binary available for your system.Please install a supported C++11 compiler and reinstall the module 'uws'.
Because of this the packager server exits and i couldn't connect to dev server from my physical device also one more issue i face is when i try to run adb reverse tcp:8081 tcp:8081 i am getting address already in use but i tried to kill adb using adb kill-server but still i get the same error.Need some help to get passed this as a new dev to react native.Thanks in advance !

UWS Build log
M:\cryptoR\node_modules\uws>if not defined npm_config_node_gyp (node "C:\Users\iamme\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "" rebuild )  Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch. MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe". To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visual Studio 2005 or 3) add the location of the component to the system path if it is installed elsewhere.   System Windows_NT 10.0.16299 gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\iamme\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" gyp ERR! cwd M:\cryptoR\node_modules\uws gyp ERR! node -v v8.9.3 gyp ERR! node-gyp -v v3.6.0 gyp ERR! not ok

Do you have a C++11 compiler installed on your OS?  Have you tried to reinstall the uws module?

@dnfield  Hey yes i did install c++ built tools 2015 and set env variable after a long time banging my head i found and fixed the issue just now.There was a binding.gyp file missing in node-gyp which i created manually and then it is now working will set this issue to closed.Thanks for responding.

I was able to fix this on a mac by doing:
cd node_modules/uws
npm install

@iammelvin

Dunno if this helps, but I had the same error using Node 10, switched to Node v9 and it works like a charm

@maciossek
Thx, this helps indeed.
This is because uws v8.14.0, required by the packager, is not compatible with node 10.
In order to use node 10, you can require uws v10.148.0 in devDependencies.
Sorry, I should have come back and posted it earlier, I went so many places to solve this that I forgot half of them posting feedback...


Add Offline Mode to graphqlProxy

Overview/summary
Add a feature to Shopify.Utils.graphqlProxy(ctx.req, ctx.res) to handle case where the shop is authenticated under accessMode=offline
...
Motivation

What inspired this enhancement?
Under the codebase of graphql_proxy.ts, the function called  loadCurrentSession to load the current session. However, it didn't list out the third argument, which is a boolean type of whether the session is online or offline. And the default value is online.
Thus, no matter what type of accessMode the developers wanted, this function would only call loadCurrentSession with the online option, which would cause an error either not found the session or unauthorized if they used offline accessMode.
Currently, it works fine with the online mode, but it would be better to add an extra option for developers to choose the online/offline in order to use graphqlProxy easily.
...

Area

[ ] Add any relevant Area: <area> labels to this issue

Checklist

[x] I have described this enhancement in a way that is actionable (if possible)

@zzyrd this is done by design, please see detailed comment on #140


Support for [[internal]] and [[url|text]] wiki links?

Is there a way to render [[internal]] and [[url|other]] syntax as links? This is supported by MediaWiki, DocuWiki, and others. Thanks.

I'm not sure how those link work. It doesn't look like regular markdown to me, and hence probably isn't supported by markdown2. So, I'm going to close this. If I'm mistaken, please re-open :slightly_smiling_face:


4.0.stable  playerbody falls through floor

hi,
i installed godot 4.0-stable and godot-xr-tools newest release for 4.0 . Then i created a very simple VR game for windows, but after adding MovementDirect to the RightHand controller node and press play, the player falls through the floor (floor got rigid-body with collision-shape) ?
I noticed there is the player body node automatically added.
what do i need todo, to collide with floor ?
thanks
flo

I just tried it and I'm not having this problem. You may want to make sure the Godot XR Tools plugin is enabled in the Plugins tab of the project settings. Additionally you may wish to make sure the ground collider is on layer 1.

the plugin is enabled. With "ground collider" do you mean the "Collision->Layer" of the RigidBody of the Floor node ?  If so, with this set to 1 and the PlayerBody->Collision->Layer also set to 1 (was only on 20) .
But i fall through the floor.
In PlayerBody there is also a Moving_Platform->Floor_Layers where all layers are enabled by default.

I put together this quick demo - the following is the player body:

And this is the static ground node:

The important parts are:

The PlayerBody - Collision - Mask has bits set which indicate the body will collide with objects on layer 1
The Ground - Collision - Layer has bit 1 set indicaing the ground is on layer 1

i stand on the floor when i have NOT added to the righthand the movementDirect scene .  When i add this scene to my righthand controller, i fall through the floor

Yes - I have movementDirect nodes added to both controllers, and I'm able to move and strafe around the scene. Would it be possible to zip up the project (excluding the .godot folder) and attach to this issue.

project.zip
here, if it works

I found two issues:

Your ground collider is a "RigidBody3D" - a dynamic body affected by gravity, and so the ground collider actually falls away under the player. Note the mesh isn't a child of the RigidBody so its image stays behind like the Cheshire cat's grin ;)
The player origin (the floor level of the tracking space) starts at position 0,0,0 (center of the universe), but the ground is a rectangle 1 meter thick, whose body is centered also at 0,0,0 - in other words your feet start life embedded 1/2 a meter into the ground; and that's probably going to cause issues with the physics engine.

You can fix these by changing the ground to be a StaticBody and then moving it down to Y=-0.5 so the top of the ground is at 0,0,0.

thanks, i am very thankful for your help.   StaticBody3d  was the killer
thx alot @Malcolmnixon


WIP: Support galaxy j4

progress

[x] Bootable
[x] Display
[ ] Keypad(need add support s2mpu06 keys to Exynos7570 keypad lib)

okay, im lazy to fix keypad power button


allow recipes saved by link to have an edit button in the personal cookbook

at the moment because a recipe saved by link redirects to that external link directly it is not possible to easily edit a recipe saved by link. This should be implemented for the personal cookbook.

this issue was duplicated


merge with Fisco wedpr

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 2
- Added 1

See the complete overview on Codacy


Nether wont work

Hi I know this is probably a noob question but I've been getting really frustrated over this and can't find a solution. In my world "survival" the nether portals don't take you to nether. I have it enabled in the server.properties but still can't find out why it won't work. I know its not something to do with permissions because im an admin and even I can't. Please help.

you'll need Multiverse-NetherPortals to link worlds. This is not a Core issue.


Providing a data dump?

First, thanks for this project. It really helps when you just need a Prestashop demo. :)
Populating database using Prestashop web-service is pretty slow. Wouldn't it be a good idea to provide some SQL dumps of generated data? I'm not sure which tables should be exported (that's my first Prestashop contact), but it may worth it.

Yes, it's a good idea. I do a first version (tested with Prestashop 1.5.6) without the pictures support. It's available in the branch features/sql
I will test with last version of Prestashop and add pictures support before to merge into master.

Tested with last version of Prestashop, it seems OK. Merged into the master


[loc][Query][VSCode] Please clarify meaning

Hi, we have a question from a translator. Could you help please?
Source:
A problem pattern or the name of a contributed or predefined problem pattern. Can be omitted if base is specified.
File Name:
src\vs\platform\markers\common\problemMatcher.nls.resx
Resource ID:
".resx", 0; "PatternTypeSchema.description"
Query:
Could we understand "base" as "base problem pattern"? Please confirm. Thanks!

Has base as a base class or base problem pattern. Something you subclass from.


Change Azure Cosmos SDK from track1 to track2

Update Azure Cosmos SDK from track1 to track2 in Tailwind.Traders.Cart.Api folder
@jongio for notification.

@isaacrlevin


Further Edits after renaming of repository

Problem description

The repository was renamed as requested and described within https://github.com/camaraproject/APIBacklog/pull/117 from QualityByDesign into SessionInsights.
As a followup action there might be further edits, e.g. in the README.md necessary, e.g.:

"QbD Score" -> ?
mentioning the renaming to give orientation for visitors of the repository who know the original proposal

Expected action

see above
Additional context

awesome - thx @hdamker . I will take a look and create a PR to do additional cleanup after the rename.


refactor: remove unused debug variable

removes an unused variable that was left in from removing sodium
Code change checklist

[x] I have ensured that all methods and functions are fully documented using doxygen style comments.
[x] My code follows the coding style guide.
[x] I tested that my change works before raising the PR.
[x] I have ensured that I did not break any existing API calls.
[x] I have not built my pull request using AI, a static analysis tool or similar without any human oversight.


Needs a Wall of Ex-Boyfriends or a Wall of shame with the crime they have committed

IE
Wall of Shame

Electric Sheep

Twitter Reply Guy
simps for other people on Twitter besides Ali

wall of shame is only for people who try to mess with the boyfriend list.
included in TOP BULLIES list


Paket can pick a wrong package if source is local folder

Description
When source set to folder (local or network share) paket can pick a wrong package when perform "install" command
Repro steps
repro.zip
Test setup In attached archive:
testPackage folder contains just a paket.template file for creating a test library
testSolution trying to consume created library (paket dependencies entry: nuget testlib 1.2.3)
Repro steps (in a attached setup):

go to testPackage folder
call paket pack output ..\nuget version 1.2.3-alpha
go to testSolution folder
call paket install

Expected behavior
"Can't find package" error
Actual behavior
paket create a paket.lock file with line testlib (1.2.3) and copy testlib.1.2.3-alpha.nupkg to packages folder (and you can't see it unless browse a packages folder)
Known workarounds
using nuget server instead of folder
using something like >= 1.2.3 <= 1.2.3 version constraint
Other cases
If folder contains two versions of package: <IP_ADDRESS> and <IP_ADDRESS> and dependency file line like nuget <...> 1.2 than paket pick package with version <IP_ADDRESS>.
Repro steps (in a attached setup):

go to testPackage
call paket pack output ..\nuget version <IP_ADDRESS>
call paket pack output ..\nuget version <IP_ADDRESS>
go to testSolution folder
add nuget testlib 1.2 to paket.dependencies file
call paket install

Expected: package testlib <IP_ADDRESS> in packages folder
Actual: package testlib <IP_ADDRESS> in packages folder
Workarounds: write full version in paket.dependencies file (1.2.0)

I found code in C:\sources\github\Paket\src\Paket.Core\Dependencies\NuGetLocal.fs file, function findLocalPackage:
    let v3 =
        Directory.EnumerateFiles(directory,"*.nupkg",SearchOption.AllDirectories)
        |> Seq.map (fun x -> FileInfo(x))
        |> Seq.filter (fun fi -> String.containsIgnoreCase (packageName.CompareString)  fi.Name)
        |> Seq.filter (fun fi -> fi.Name.Contains(normalizedVersion) || fi.Name.Contains(version.ToString()))
        |> Seq.tryHead

Is there valid cases with arbitrary .nupkg file name format?
Maybe paket should just stick to <id>.<version>.nupgk name format?

Ok this is clearly a bug at that location.
Since you already found it, are you interested in fixing it and sending a pull request?
Basically we need to check that the file ends with version + nupkg instead of the contains version check.
Regarding your question: yes we need to go through some hoops here since the package name is case insensitive. So we might have packackexzy in dependencies file while the file is called PackageXYZ.1.0.1.nupkg

If just check endwith version.nupkg paket will "find" file like package.1.2.3.nupkg if user write nuget package 2.3 in dependencies file.  (plus - case with <IP_ADDRESS>/<IP_ADDRESS>: version 1.2 after normalization will become 1.2.0 and will pass "endwith".
And if package id end with number it can create some trouble.
Maybe after initial filtration with contains ignorecase try to read nuspec from filtered files?
Such check may be omitted if filename excactly in id.version.nupkg or id.normalizedVersion.nupkg format.

I think if you take the filename and lowercase it then it should match lowercase [package].[version].nupkg

Case sensitivity is not the only problem here. I can see now that "contains" here for some sort of "version normalization" — package.name.<IP_ADDRESS> can be answer for user's input nuget package.name 1.0.
For 100% accuracy paket must read .nuspec in package file, parse <version> and compare version, provided by user with it as two SemVerInfo instance , but it cat be too slow (especially in case of network share).
So, i see two options here:

Do fancy file name analysys, something like
-- split name with first occurrence of dot followed by number,
-- take first part as package name (lowercase it or whatever),
-- take rest of the string as version string,
-- parse it to SemVerInfo and than compare result with user input
In that case package with name ends with "dot number" will be out of support:
From file name only you can't tell package.<IP_ADDRESS> is "package version 1.2.3" or "package.1 version 2.3.0".

As i mentions in previous comment paket can check .nuspec file from package files filtered by some "loose" condition like contains packageid && (contains version || contains normalizedVersion).
It can be slow in some cases i think.

option 1 sounds good to me
2017-06-14 9:07 GMT+02:00 lexarchik<EMAIL_ADDRESS>
Case sensitivity is not the only problem here. I can see now that
"contains" here for some sort of "version normalization" —
package.name.<IP_ADDRESS> can be answer for user's input nuget package.name 1.0
.
For 100% accuracy paket must read .nuspec in package file, parse
and compare version, provided by user with it as two SemVerInfo instance ,
but it cat be too slow (especially in case of network share).
So, i see two options here:

Do fancy file name analysys, something like
-- split name with first occurrence of dot followed by number,
-- take first part as package name (lowercase it or whatever),
-- take rest of the string as version string,
-- parse it to SemVerInfo and than compare result with user input
In that case package with name ends with "dot number" will be out of
support:
From file name only you can't tell package.<IP_ADDRESS> is "package version
1.2.3" or "package.1 version 2.3.0".
2.
As i mentions in previous comment paket can check .nuspec file from
package files filtered by some "loose" condition like contains
packageid && (contains version || contains normalizedVersion).
It can be slow in some cases i think.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Paket/issues/2419#issuecomment-308339358,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNCUd_Gz3UlvKRYeI4gmE55lfnSyZks5sD4awgaJpZM4N40OY
.