To support URL Pattern Whitelisting in coming build or not?

Are we supporting whitelisting URLs? The iOS TokenScript client supports whitelisting, so it blocks everything by default. But we don’t have a way to support the whitelisting of URL patterns in the TokenScript file yet.
Will the workshop let developers write their TokenScript to connect to any URL?
cc @JamesSmartCell

Practically without xml signature validation, the whitelist doesn't make it more secure. Also our hands are pretty full, it would be lovely to see the capacity to call smart contract calls from TBML (think dai or xdai bridge) than having security sorted out for demonstration.

Agreed. Have excluded whitelisting in the branch for TestFlight-ing.


Is there a way to do JSON validation that does case insensitive matching on property names?

Documentation

[X] I have consulted the documentation, and my question isn't answered there.

Nuget Package
JsonSchema.Net
Package Version
7.0.2
How can I help?  Please provide as much context as possible.
I am trying out this package for the first time, looking for a solution that adds JSON validation to some of our applications. Some applications use different property name casing rules when producing the JSON, but all of the consumers of the JSON are case-insensitive by default. Is there a way to make the JSON validation case insensitive too if the property name comes in a different case than in the schema? I did not see any options available that could do this in the c# nuget package implementation. My hope was to find something similar to how System.Text.Json has property name casing options for its serializer.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

JSON Schema in general doesn't support case-insensitive matching.
You might be able to get around it by using patternProperties and creating regexes for each property.
For example, if you have the following data:
[
  { "foo": 5 },
  { "Foo": 5 }
]

you could validate this with
{
  "type": "array",
  "items": {
    "patternProperties": {
      "^[Ff]oo$": { "const": 5 }
    }
  }
}

Of course this would take some setup, but this is how you'd do it.

If you'd like to propose case-insensitivity as a JSON Schema feature, you're welcome to open an issue in the spec repo: https://github.com/json-schema-org/json-schema-spec/issues

Would this be something that is relatively easy to add if requested? We have situations where payloads may change casing of properties as they are handed off between different steps along a chain, and we want to still verify it meets the spec but case sensitivity caught us off guard. We are used to all of our implementations being case insensitive, that this became a blocker for us implementing this type of validation. This seems more like a tooling implementation detail, rather than a change to the spec. That seems like it would be a much larger lift to request.

Would this be something that is relatively easy to add if requested?

Possibly, but I'm unsure.  I'd have to dig into it.  I'm sure it's doable, but what that looks like and how easy it might be will require some investigation.

This seems more like a tooling implementation detail, rather than a change to the spec.

In general, tooling should meet the requirements of the spec.  If the spec doesn't support case insensitivity, then the tooling shouldn't either (by default).
Tools can offer configurations that operate outside of the spec, but these configurations should be disabled by default so that they have to be explicitly set by the user.  This way, the user is opting in to non-standard behavior.

Some applications use different property name casing rules when producing the JSON, but all of the consumers of the JSON are case-insensitive by default.

I recognize that this is the situation that you're in now, and fixing your ecosystem to unify all of your JSON producers may be a long job.
However this kind of inconsistent data formatting is the root of the problem, and I believe it should be addressed eventually.

We are used to all of our implementations being case insensitive...

Thinking through the various JSON functionality that I've built here and seen other places, I can't think of a specification that allows case insensitivity.  The only place I can think that I've seen it is in serializers.

Another option would be to perform some pre-processing on your JSON data prior to validation.
void CamelCasePropertyNames(JsonNode? node)
{
    if (node is not JsonObject obj) return;

    var propertyNames = obj.Select(x => x.Key).ToList();
    foreach (var propertyName in propertyNames)
    {
        // there's an issue going from snake-case directly to camelCase
        // go through humanized first resolves it
        var adjustedName = propertyName.Humanize().Camelize();
        var value = obj[propertyName];
        obj.Remove(propertyName);
        obj[adjustedName] = value;

        CamelCasePropertyNames(value);
    }
}

This will normalize all of your names for you.  It requires Humanizer.

@JasonRodman does this answer you question (albeit probably not as you had hoped)?

@gregsdennis It does, thanks. I wish there was an easier solution. It is going to make adoption for us a bit more painful. It just seems silly to be case sensitive with json property names. It would be a fantastic opt-in feature to the tooling if it was ever added.

It just seems silly to be case sensitive with json property names.

FWIW, in my experience (which you can see from the extensive JSON support in this project), I've never seen any JSON-related technology support case-insenstivity (with the single exception of deserialization, and even that's usually opt-in).
JSON is basically always exact match on strings.


Update Overview.md

Fix for PowerShell scripts.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Skype/Skype-For-Business-Bot-Framework/docs/Overview.md
:white_check_mark:Succeeded

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

@tomoemp This is an old PR, so closing. If you still think these changes need to be made, please file a new PR. Thanks.


Repairs and new add

Hi!
I´ve used Python 3 for the try
Repair warning error in google.py with beautifulsoup4 (html5 parser)
I've added domain support for google. Very useful for SEO tools
I´ve upgraded the example code
Sorry for my bad english..

Hey, it looks good! I hadn't even thought of it :p A couple of changes-

Do you mind passing the location as an argument in the URL rather than changing the domain itself? This way we can support both Bing and Google consistently. I found this article that might help you out.

It would be better if the new argument to the function is present at the end so that any existing code that users have won't break when they update to a new version of pws. You'll have to change the signatures of 4 functions and the calls to these functions.

The support that I added to the domain was for the SEO. For example if you will search in google Spain the web "lacrioliposis.es" with the keyword crioliposis, in the results you can see it in fourth position. But if you search it on Chile,   you can see it in sixth position. What you told me it is referred to search webs with a determined end.
This option serves to compare the position of your page on google depending on the country that you search.
Example:

I understand what you are saying, but the same can be simulated by passing the country code as an argument in the URL itself.
Example:

https://www.google.com/search?q=delta&gl=in returns results as seen in India. It mentions some stores in India etc.
https://www.google.com/search?q=delta&gl=uk returns results for the UK which omits the stores in India.

This satisfies what you're trying to do and can be done on both Bing (argument name is cc) and Google (argument name is gl).

I'm sorry it had not understood before, I tried what you said and goolge works, in bing not give any result, that is to say the search gives the same result even if you add the code for another country.
I was looking for information on the label "& gl =" and only found information in 2010, I think the domain system will make it easier for novice people. But as you want to I do not care the two methods work :+1:
https://en.wikipedia.org/wiki/List_of_Google_domains

Calling it country code instead of domain would help simplify things for users who don't want to get into the details.. :p
Bing is buggy even with the "recent" options. :( I'm just trying to make sure that the API is consistent for both the engines so that end users don't face any issues understanding it.


Change the example code 'failureType' -> 'failType'

The current examples use 'failureType', but in code is the property value 'failType' used.

Does this improve the project? If so, how?
FailureType is a common identifier in the Redux community, indicating that a single response, a FailureType is dispatched in response to an error in the middleware chain. The description is perfectly fine as it is (being widely understood, as this one is).
I suggest we leave this alone, as the changes don't significantly impact the code base in a positive way, and aren't correcting grammar. FailureType isn't a radical enough change to warrant the confusion and bikeshedding it could cause.

Well I didn't mean to change the description, but only the code examples that use wrong property.

@riston I apologize... I read this much too early in the morning, before coffee. I just noticed the failType definition where logic is created. Since this seems to align with already existing definitions of failType, 👍 .

@riston Thank you so much for this PR. They always say in programming naming is one of the most difficult things, and I agree. I go through many iterations privately before I settle on something I'm somewhat happy with. Problem is that sometimes I forget to cleanup docs or old code in that iteration, so I'm glad that you took the time to write the PR to correct these things.


Reimplement contributor form

So that users can sign up to volunteer again, or fill the form in again if they change their mind.
Closes #1673.
I hope I didn't butcher the frontend too bad :/
Regarding the duplicate of state of whether the form is filled in the backend: this is a bit of debt from the way the forms were done in the past. I think we should import the existing forms (that can be matched against emails/usernames) and then get rid of the semi-duplication of state. But that's another PR.
Backend checklist

[x] Formatted my code by running autoflake -r -i --remove-all-unused-imports src && isort . && black . in app/backend
[ ] Added tests for any new code or added a regression test if fixing a bug
[ ] All tests pass
[x] Run the backend locally and it works
[ ] Added migrations if there are any database changes, rebased onto develop if necessary for linear migration history

Frontend checklist

[x] Formatted my code with yarn format && yarn lint --fix
[x] There are no warnings from yarn lint
[ ] There are no console warnings when running the app
[ ] Added any new components to storybook
[ ] Added tests where relevant
[ ] All tests pass
[x] Clicked around my changes running locally and it works
[ ] Checked Desktop, Mobile and Tablet screen sizes

@lucaslcode tried to fix it up, not sure if I screwed it up?

Tested locally, works fine


Update help feature

Describe your changes
Update list of commands in help window
Enable java assertion
Fix UI issue in help window
Issue ticket number and link
Closes #103
Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] If it is a core feature, I have added thorough tests.

Codecov Report
Attention: Patch coverage is 0% with 26 lines in your changes missing coverage. Please review.

Files with missing lines
Patch %
Lines

src/main/java/seedu/address/ui/HelpWindow.java
0.00%
26 Missing :warning:

Files with missing lines
Coverage Δ
Complexity Δ

src/main/java/seedu/address/ui/HelpWindow.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)


WebSocket algebra

References https://github.com/endpoints4s/endpoints4s/issues/954.

Since browser clients cannot interact with upgrade response/request, I though it would be best to explicitly separate webSocket and webSocketWithUpgrade. My thinking was that if an endpoint describes an interaction with headers and client is unable to provide them, it should not be able to communicate over said endpoint because it will be incompatible with server implementation. Slight issue with that approach is that browsers can implicitly pass some headers, like cookies, so server implementation can interact with them, but I am not sure if this implicit contract should be handled by the implementation.
Only upgradeRequestHeaders and upgradeResponseHeaders are provided because the spec seems to not put any importance into request/response entities.
@julienrf What do you think?

After doing more research and thinking, I do not think that a stream is a correct abstraction to express data flowing through a WebSocket. Issue with streams is that they have a definition of an end, and WebSockets lack that - neither client nor server can communicate they either of them have stopped sending their messages, they can only close the connection. Inability to explicitly communicate these clearly separate behaviors puts a limit to the available expression and requires developers to come up with their own protocols. This makes WebSockets not as valuable as I thought before, and they are not a replacement for ChunkedEntities.


Multiple instances of singleton shared dependencies are fetched and ran in runtime - "Cannot read properties of null (reading 'useEffect')"

Describe the bug
When a host app imports a remote directly without lazy loading, in certain scenarios the shared singleton dependencies (in our case React) get downloaded for both the host and the remote, they can end up each using their own respective versions of that shared dependency.
After some investigation, we think the issue happens when the remote entry files finishes downloading before the host dependencies - see the example below, the host depends on react 18.2.0, the remote on react 18.3.1.

In cases where the react 18.2.0 chunk ends up finishing loading first, we do not see this issue:

Reproduction steps:
run pnpm i
run pnpm --filter=host dev
run pnpm --filter=remote dev
Expected: page loads correctly
Actual: page fails to load due to incorrect request for the deps of remote app.
The example config is (using the latest versions from @rsbuild/core, @rsbuild/plugin-react and @module-federation/rsbuild-plugin):
Host
import { defineConfig } from '@rsbuild/core';
import { pluginReact } from '@rsbuild/plugin-react';
import { pluginModuleFederation } from '@module-federation/rsbuild-plugin';

export default defineConfig({
  server: {
    port: 3000,
  },
  plugins: [
    pluginReact(),
    pluginModuleFederation({
      name: 'host',
      remotes: {
        remote: 'remote@http://localhost:3001/foo/remoteEntry.js',
      },
      shared: {
        react: {
          singleton: true,
        },
        'react-dom': {
          singleton: true,
        },
      },
      dts: false,
      shareStrategy: 'loaded-first',
    }),
  ],
});

Remote
import { defineConfig } from '@rsbuild/core';
import { pluginReact } from '@rsbuild/plugin-react';
import { pluginModuleFederation } from '@module-federation/rsbuild-plugin';

export default defineConfig({
  server: {
    base: '/foo',
    port: 3001,
  },
  plugins: [
    pluginReact(),
    pluginModuleFederation({
      name: 'remote',
      filename: 'remoteEntry.js',
      exposes: {
        './Button': './src/Button',
      },
      shared: {
        react: {
          singleton: true,
        },
        'react-dom': {
          singleton: true,
        },
      },
      dts: false,
      shareStrategy: 'loaded-first',
    }),
  ],
});

Reproduction
https://github.com/danhorvath/rsbuild-demo
Used Package Manager
pnpm
System Info
System:
    OS: macOS 15.1
    CPU: (12) arm64 Apple M3 Pro
    Memory: 1.42 GB / 36.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.17.0 - ~/.nvm/versions/node/v20.17.0/bin/node
    npm: 10.8.2 - ~/.nvm/versions/node/v20.17.0/bin/npm
    pnpm: 9.12.3 - ~/.nvm/versions/node/v20.17.0/bin/pnpm
  Browsers:
    Chrome: 130.0.6723.92
    Edge: 130.0.2849.56
    Safari: 18.1

Validations

[X] Read the docs.
[X] Read the common issues list.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Module federation issue and not a framework-specific issue.
[X] The provided reproduction is a minimal reproducible example of the bug.

What if you set it to version first for the strategy

React plugin takes options. Ensure router and runtime are set to false. Inspect types to see exactly what to pass.

I belive this issue is not specific to react. We had very similar problems with an internal package that we use as a shared dependency, which relies it being a singleton - it exports an instance of a class that needs to be initialized, and occasionally the microfrontend causes a runtime error when it loads a different, un-initialized instance.

What if you set it to version first for the strategy

We had that setting when we ran into this issue for the first time - we later changed to loaded-first hoping that it would fix it but unfortunately it didn't.

Please provide a repo we can debug

Do you use any dynamic remotes that are not import() or import from?

Okay so doing this: https://github.com/danhorvath/rsbuild-demo/pull/1
I have added window.loaction.reload() to the remote, this will refresh the page perpetually till a hook error happens then stop since useEffect cant be called.
With version-first, ensuring i share react/(jsx-dev-runtime|jsx-runtime), and setting the packages to ^ and not pinning them - it i am not able to make it throw an error. If you can use that PR, edit it and make it crash we can take a look further, but i left it for a few min (about 3000 page reloads) without error, soon as i remove version first, within ~60 reloads it would crash depending on what loaded first and causing a missmatch in version.

even without
"react/": {
singleton: true,
},
or the ^ on the react and react dom in the package json, it still seems to work - as long as version-first is set.

I miss to consider the shared is loading ... Okay i fix it on this pr https://github.com/module-federation/core/pull/3176

Do you use any dynamic remotes that are not import() or import from?

If what you mean by dynamic remotes is a runtime generated remote url, like import(runtimeUrl + "/mf-manifest.json") then the answer is no, we don't. I'm not sure of other possibilities in which we can consume a remote (except maybe if you mean require?)
The fix that @2heal1 provided should work for the exact configuration with loaded-first strategy, so really appreciate that - we can probably close this issue afterwards.
However, do you happen to have any intuition on how this could have possibly happened when running with version-first? One thing worth mentioning though was that at the time we were running with the rs-build built-in module federation configuration - which we understood is actually module federation 1.5 (since it's using<EMAIL_ADDRESS>and not 2.0.
Unfortunately we were not able to reproduce it easily in a simple repro like the one @danhorvath linked in this issue (it was in our real setup that uses 4 remotes all which had shared dependencies in different versions).

You're using v2.
With version first it should not happen. But without a repo to test it on its virtually impossible to try and debug.
Publish some fake packages or use a monorepo etc and you should be able to recreate a sample.
Otherwise send me an NDA and internal repo.

Ah, you're on an older version of RSBuild as a whole. Then yes, it may be a bug in the runtime itself that's been resolved since.
If you experience it on the latest versions, let us know and, if possible, make a reproducible sample that we can look at.

Ah, you're on an older version of RSBuild as a whole.

We were on the latest versions at the time of writing.
There is one aspect of our production setup that we couldn't model well in the repro, which is that in our setup the chunks (including the shared dependencies) can be cached by the browser, but the remoteEntry is not, so often on the initial page load the remote entry is fetched faster than the shared dependencies of the host, but on subsequent loads most (usually all) shared dependencies are loaded from the disk.
I wonder if this is the reason why we experienced the same (or at least very similar) runtime error with the version-first policy too. I will try to adjust the repro with the caching mechanism to check this.
But in any case, thank you both for the quick help, it is very much appreciated. We'll verify tomorrow if the latest version resolves our issue.

Do you have a prod url? If we can repro it in prod, we can possibly place breakpoints there and try to diagnose it.

Do you have a prod url?

We rolled back to use our old webpack setup (with the old module federation) when we noticed this issue so I can't provide a url.

It may be the reason. But version first in general seems to be far more reliable than loaded first. Loaded first is the old v1 mechanism which is less deterministic. You may also want to consider using the json protocol instead of the js remotes instead. Since it is also more robust as well as we can compute the tree before any evaluation takes place.

That's good to know. We plan to migrate to using the manifest.json as soon as we stabilized our rsbuild setup. We've been working with the loaded-first strategy mainly to avoid the runtime error (as suggested here https://github.com/module-federation/core/issues/2898#issuecomment-232375467) and for the performance benefits. Thank you for the suggestion, we'll check if using version-first + ‘manifest.json‘ is stable in our case.

manifest.json was also designed to be used to control MF at the server side. If you use the json protocol you can render "module snapshots" which are lock files for the runtime - the runtime will never change behavior when a a module snapshot is present, this is how we orchestrate and control our several thousands of remotes at Bytedance.
DM me if you want a reference of it, we do not readily supply one since it requires additional infra for user to leverage it.

manifest.json was also designed to be used to control MF at the server side. If you use the json protocol you can render "module snapshots" which are lock files for the runtime - the runtime will never change behavior when a a module snapshot is present, this is how we orchestrate and control our several thousands of remotes at Bytedance.

Interesting, we'll consider that option, thanks!
Regarding this issue - we verified the fix on our end and we don't see the runtime error anymore with the latest module federation runtime. Thanks you for the help!

You're using v2.
With version first it should not happen. But without a repo to test it on its virtually impossible to try and debug.
Publish some fake packages or use a monorepo etc and you should be able to recreate a sample.

Following your advice, we tried switching to the version-first share strategy. Unfortunately we're facing a very similar issue. We managed to create a reproduction, but since this issue with loaded-first got fixed, we decided to open a new issue with it: https://github.com/module-federation/core/issues/3209

Can you share the reproduction with version first. I'd still like us to investigate it!

We included a link with the reproduction in the new issue that we created, it's in the same repo as above but on a branch called version-first https://github.com/danhorvath/rsbuild-demo/tree/version-first
Any help is very much appreciated.


fix: handling the case where command is an invalid value

Summary
Related Issue

#285
Checklist

[x] I have added changeset via pnpm run change.
[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thank you


revokeAccessToken Promise never returns on error

Hi,
if there is a problem revoking the access token (i.E. CORS) with revokeAccessToken() the promise never returns. I think there is a "xhr.onerror" handler missing within the revocation client.
Thanks,
Thorsten

not sure. you might have to debug more to get more info.

What kind of information do you need? I noticed that after revoking a token with this method the promise did not return because of a CORS error at the revoke endpoint. Of course the server should also be configured correctly. But I would expect the promise to be rejected in this case.
I think there is a xhr.onerror callback missing:
https://github.com/IdentityModel/oidc-client-js/blob/dev/src/TokenRevocationClient.js#L52
Like
xhr.onerror = () => { reject() };

I think there is a xhr.onerror callback missing:

possibly. i will have a look when i can.

Fixed, thanks for the heads up!


Neovide is not picking up certain executables in $PATH when opened on windows from WSL

When opening and running :echo $PATH the full $PATH does not show up. How can I get the $PATH that neovide loads to match the $PATH that I use?

This has been resolved in main I believe. We now boot up bash on startup in order to find the correct path.


Unable to get all tenant properties

Category

[ ] Question
[ ] Typo
[x] Bug
[ ] Additional article idea

Expected or Desired Behavior
Be able to list all tenant properties configured on the app catalog using PowerShell.
Observed Behavior
Currently using PowerShell, you can only retrieve the details for a specific tenant property, but you cannot get the list of all tenant properties.
Steps to Reproduce
n/a

@waldekmastykarz - Thank you for your feedback, this is actually a feature request.  The right place to ask for new features is user voice.  This one in particular is already in the works though.  However, I am going to close this issue as this is the wrong forum for feature requests.


WIP: Implement e2e tests

Implements the framework for e2e tests with the first two e2e tests from the e2e-manifests.
Blockers:
Replace kubectl delete -f with python code:
https://github.com/kubernetes-client/python/issues/940
Remove forked code and contribute changes upstream:
https://github.com/kubernetes-client/python/issues/941

The PR already has a merge conflict, please rebase it

You have seen the deprecation warning :
tests/test_e2e.py::test_deny_all_traffic_to_an_application
  /home/travis/virtualenv/python3.7.1/lib/python3.7/site-packages/yaml/constructor.py:126: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
    if not isinstance(key, collections.Hashable):

And could you take a look at this warning:
/home/travis/virtualenv/python3.7.1/lib/python3.7/site-packages/_pytest/mark/structures.py:324
  /home/travis/virtualenv/python3.7.1/lib/python3.7/site-packages/_pytest/mark/structures.py:324: PytestUnknownMarkWarning: Unknown pytest.mark.e2e - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
    PytestUnknownMarkWarning,

Thanks (or at least create an issue for it).

Are you still working on this ?

No, feel free to takeover if you like to

Closing this in favor of #82 and upcoming PR(s)


Derived store gets out of sync with origin stores if some subscriber of origin store immediately changes its value

Easiest example, using propertyStore:
testStore.js
import { writable } from 'svelte/store'
import { propertyStore } from 'svelte-writable-derived'

export const outerStore = writable({ inner: '?' })
export const innerStore = propertyStore(outerStore, 'inner')

App.svelte

	$outerStore = {JSON.stringify($outerStore)}

	$innerStore = {JSON.stringify($innerStore)}

<button type="button" on:click={() => ($innerStore = 'a')}>Set inner to a</button>
<button type="button" on:click={() => ($innerStore = 'x')}>Set inner to x (should become y)</button>

Here, if we set $innerStore = 'x', it will update outerStore to { inner: 'x' } as expected. This will then cause the subscribe callback to be called, which immediately updates outerStore to { inner: 'y' }.
Expected behavior: This external update to outerStore should trigger another update to innerStore so that it also becomes 'y'.
Actual behavior: The external update is not propagated to innerStore - we now have a situation where outerStore is { inner: 'y' } but innerStore is 'x'!
See REPL.

As a workaround, the subscriber-updater can instead be added to the inner store. Lines 4-6 of App.svelte would become:
	innerStore.subscribe(value => {
		if (value === 'x') innerStore.set('y')
	})

I agree this should be fixed and will look into it.

Of course - the issue is just that in the real-world application, it's a piece of code in an entirely different place that does this subscriber-update, and it doesn't even know about any inner stores.
Thanks for looking into it!

Fix released in v2.1.4. Thanks for the report!


Use inline-elements package for unformatted HTML tags

I wanted to add a HTML element to the list of ones that are unformatted. I thought I'd have to copy the entire list from js-beautify's source and then add mine at the end. HOWEVER, I fortuitously discovered https://www.npmjs.org/package/inline-elements which contains them as a package. Awesome!
I think js-beautify should use that package :)

Inline elements have been added.  This list is not so difficult to maintain internally.


Segmentation fault on OPPO FindX7 Ultra (Snapdragon8Gen3)

DDR size = 16GB
./main_qwen_npu -s 64 -c 1 -l 512
below is tail logs
`
Memory Usage: 8910 MB(19036) at: execute graph: 94
chunk:1 execute qnn graph 95
model.layers.23.self_attn.or_split       exe_time:0.064 ms
model.layers.23.self_attn.or_split-00_view_       exe_time:0.004 ms
model.layers.23.self_attn.or_split-01_view_       exe_time:0.003 ms
model.layers.23.self_attn.o_proj       exe_time:0.002 ms
model.layers.23.self_attn.o_proj.dequantize       exe_time:0.003 ms
model.layers.23.self_attn.o_proj.dequantize-00_view_       exe_time:0.002 ms
model.layers.23.self_attn.o_proj.dequantize-00_view_-00_add_       exe_time:0.003 ms
model.layers.23.post_attention_layernorm       exe_time:0.003 ms
model.layers.23.mlp.up_proj.quantize       exe_time:0.002 ms
model.layers.23.mlp.up_proj.quantize-00_view_       exe_time:0.002 ms
model.layers.23.mlp.gate_proj       exe_time:0.002 ms
model.layers.23.mlp.up_proj       exe_time:0.002 ms
model.layers.23.mlp.gate_proj.dequantize       exe_time:0.002 ms
model.layers.23.mlp.up_proj.dequantize       exe_time:0.002 ms
model.layers.23.mlp.silu       exe_time:0.003 ms
model.layers.23.mlp.silu-00_mul_       exe_time:0.002 ms
model.layers.23.mlp.down_proj.quantize       exe_time:0.003 ms
model.layers.23.mlp.down_proj       exe_time:0.003 ms
model.layers.23.mlp.down_proj.dequantize       exe_time:0.002 ms
model.layers.23.mlp.down_proj.dequantize-00_view_       exe_time:0.002 ms
model.layers.23.mlp.down_proj.dequantize-00_view_-00_add_       exe_time:0.001 ms
QNN execution time 12.683 ms
model.layers.23.self_attn.or_split       exe_time:0.064 ms
model.layers.23.self_attn.or_split-00_view_       exe_time:0.004 ms
model.layers.23.self_attn.or_split-01_view_       exe_time:0.003 ms
model.layers.23.self_attn.o_proj       exe_time:0.003 ms
model.layers.23.self_attn.o_proj.dequantize       exe_time:0.003 ms
model.layers.23.self_attn.o_proj.dequantize-00_view_       exe_time:0.002 ms
model.layers.23.self_attn.o_proj.dequantize-00_view_-00_add_       exe_time:0.002 ms
model.layers.23.post_attention_layernorm       exe_time:0.003 ms
model.layers.23.mlp.up_proj.quantize       exe_time:0.002 ms
model.layers.23.mlp.up_proj.quantize-00_view_       exe_time:0.001 ms
model.layers.23.mlp.gate_proj       exe_time:0.002 ms
model.layers.23.mlp.up_proj       exe_time:0.002 ms
model.layers.23.mlp.gate_proj.dequantize       exe_time:0.002 ms
model.layers.23.mlp.up_proj.dequantize       exe_time:0.002 ms
model.layers.23.mlp.silu       exe_time:0.003 ms
model.layers.23.mlp.silu-00_mul_       exe_time:0.002 ms
model.layers.23.mlp.down_proj.quantize       exe_time:0.002 ms
model.layers.23.mlp.down_proj       exe_time:0.002 ms
model.layers.23.mlp.down_proj.dequantize       exe_time:0.002 ms
model.layers.23.mlp.down_proj.dequantize-00_view_       exe_time:0.002 ms
model.layers.23.mlp.down_proj.dequantize-00_view_-00_add_       exe_time:0.002 ms
QNN execution time 11.541 ms
Memory Usage: 8888 MB(19036) at: execute graph: 95
model.norm     reshape:
|| Input input0-00 shape: 1 64 1 2048 (131072) |
|| Output outtensor-model.norm-00 shape: 1 64 1 2048 (131072) |
lm_head     reshape:
|| Input outtensor-model.norm-00 shape: 1 64 1 2048 (131072) |
|| Output outtensor-lm_head-00 shape: 1 64 1 151936 (9723904) |
model.norm       exe_time:2.76 ms
lm_head       exe_time:2188.71 ms
Fre
load time: 1554.09 ms
token time: nan ms
inference speed: nan tokens/s
load time: 2773.47 ms
token time: nan ms
inference speed: nan tokens/s
0.0ms [WARNING]   sg_stubPtr is not null, skip loadRemoteSymbols
Segmentation fault`

Thank you for the detailed log.
It seems that the prefilling procedure has completed correctly, with the lm_head operator executing and the first token Fre being generated.
However, the issue is that there is no decoding log even when the DEBUG option is enabled. Did you omit or annotate the log?
Besides, if the segmentation fault occurs at the end of the total execution, this is a known issue. It results from the order in which the mllm-NPU releases QNN resources. We are working on a fix for this, but rest assured, it does not affect the normal prefilling and decoding processes.
Thanks again for your valuable assistance!


Prepend MQTT protocol to MQTT topics

Related

https://github.com/FIWARE/tutorials.IoT-over-MQTT/issues/25
https://github.com/telefonicaid/iotagent-json/pull/633

This can only be merged once JSON and Ultralight IoT Agents have been updated to support the new path.
@mapedraza

@mapedraza - I'm testing updates to the tutorial test harness, I can now successfully send measures under /ul/<apiKey>/<deviceId>/attrs, but commands are still being sent under <apiKey>/<deviceId>/cmd - if you look at MQTTBinding.js  you can see the commandTopic is not prefixed by the protocol ul - is this expected behaviour?
I would expect that an actuator would be listening on the ul/<apiKey>/<deviceId>/cmd  topic, not the <apiKey>/<deviceId>/cmd topic.
Secondly am I correct in thinking that I need to align entity_type as shown when provisioning an actuator?
curl -L -X POST 'http://localhost:4041/iot/services' \
-H 'fiware-service: openiot' \
-H 'fiware-servicepath: /' \
-H 'Content-Type: application/json' \
--data-raw '{
 "services": [
   {
     "apikey":      "4jggokgpepnvsb2uv4s40d59ov",
     "cbroker":     "http://orion:1026",
     "entity_type": "Bell",
     "resource":    ""
   }
 ]
}'

curl -L -X POST 'http://localhost:4041/iot/devices' \
-H 'fiware-service: openiot' \
-H 'fiware-servicepath: /' \
-H 'Content-Type: application/json' \
--data-raw '{
  "devices": [
    {
      "device_id": "bell001",
      "entity_name": "urn:ngsi-ld:Bell:001",
      "entity_type": "Bell",
      "protocol": "PDI-IoTA-UltraLight",
      "transport": "MQTT",
      "commands": [
        {
          "name": "ring",
          "type": "command"
        }
       ],
       "static_attributes": [
         {"name":"refStore", "type": "Relationship","value": "urn:ngsi-ld:Store:001"}
    	]
    }
  ]
}'

If the Device's "entity_type": "Bell" doesn't align with an existing service, then the default TEF apiKey is used.

https://github.com/telefonicaid/iotagent-ul/pull/400 changes the topics for sensor measuremens, but doesn't alter the location of commands - maybe this has been dealt with in another PR?

Hi @jason-fox. Let me give you
1) Expected MQTT topic for a command
It is true. It is different the topic expected in the case of commands and measures. There are different reasons:

When sending the data, the device have to explicitly idenfy the agent that process the data. For that reason, it is needed to add the prefix with the protocol, otherwise there is no way to define which agent is processing the measure since multiples agent can be subscribed to the same topic.
When sending the commands from the agent to the device, you do not need to explicitly defines a specific endpoint to the device since you already configure the protocol and the command in the agent through the device or group provision. The devices always expect the data on their own topics and does not need to be multiplexed. Otherwise, a "standard" "FIWARE Ready" device that is intend to be compatible with multiples protocols, need to be subscribed to as many topics as agents available (UL, JSON, Sigfox, LWM2M, OPC-UA, XML...)

Probably is a bit confusing for the developers and need to be clarified and documentation in the agent need to be improved in that way. That is the reason why it works in that way but feedback and suggestion is welcome.
2) Align entity-type
This part of the code is a bit complex and error-prone due to a not strong relationship between groups and devices when the IoT-Agent was designed and because of giving backward compatibility. In fact, there were some work done in the last week related with this part of the code (https://github.com/telefonicaid/iotagent-node-lib/issues/1211, https://github.com/telefonicaid/iotagent-node-lib/pull/1212, https://github.com/telefonicaid/iotagent-node-lib/pull/1214).
This problematic is well explained in this comment. As a resume, since there is not a strong relationship between the groups and the devices, (i.e. having a groupID parameter both in the config group and in the device), the best way is to add the APIKEY on the device provision with the same value of the APIKEY of the service group "attached".


"Invalid JSON document" error in sample code

[Enter feedback here]
{"Error":-2147024883,"ErrorMessage":"The data is invalid.","ErrorEvents":[{"Message":"The specified compute system configuration is invalid: The data is invalid. (0x8007000D, 'Invalid JSON document '$'').","Provider":"17103e3f-3c6e-4677-bb17-3b267eb5be57","EventId":11000,"Data":[{"Type":"String","Value":"%%2147942413"},{"Type":"String","Value":"0x8007000D"},{"Type":"String","Value":"Invalid JSON document '$'"}]}]}
I take the c_VmConfiguration from sample code, and get error msg above with code below:
HCS_OPERATION hCreateOperation = HcsCreateOperation(nullptr, nullptr);
HCS_SYSTEM hSystem;
HRESULT r = HcsCreateComputeSystem(
	L"Sample", // Unique Id
	c_VmConfiguration,
	hCreateOperation,
	NULL,
	&hSystem);
PWSTR resultDocument;
r = HcsWaitForOperationResult(hCreateOperation, INFINITE, &resultDocument);

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

ID: 7bf1f857-ddd8-9a95-d29b-a3c48acd7da8
Version Independent ID: 0afeee6a-5d3f-e211-233f-4dc46b013bee
Content: Quick Start
Content Source: virtualization/api/hcs/Reference/Tutorial.md
Product: virtualization
Technology: virtualization
GitHub Login: @FayMeng
Microsoft Alias: qiumeng

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


Some code cleanup around job/dataset state manipulation

Signed-off-by: Yinan Li<EMAIL_ADDRESS>

@pcadabam can you review?

Updated.

LGTM.


Allow installing with symfony 3

Ping @philipobenito.

I need time to check BC breaks to before I can merge this.

Not sure if you're aware, you probably are. Symfony 3.0 has no breaking changes, except for removed deprecated functionality. If some functionality were to be deprecated, you'd have seen it, or someone would have created an issue for it saying "your code is thowing these warnings".

Yeh, if it's broken on 3.0, it's broken on 2.x anyway.

Ah, this I didn't know, will merge and tag in the morning.
On Thu, Jan 7, 2016 at 4:51 PM, Graham Campbell<EMAIL_ADDRESS>wrote:

Yeh, if it's broken on 3.0, it's broken on 2.x anyway.
Reply to this email directly or view it on GitHub:
https://github.com/thephpleague/route/pull/98#issuecomment-169725706

Ok, wasn't sure, but good thing I mentioned it anyway then :wink:

I did think it odd that there was no PSR-7 but just haven't had time to look at what the version bump was.
Thanks both of you.


[Accordion] Control over item title text transform.

https://github.com/adobe/spectrum-css/blob/051b16be1e880fbabd98b0e98b0bbfa6173fc4fe/components/accordion/index.css#L101
Can this be updated to surface a Custom Property? There are a handful of product lines that are currently reviewing designs that have this title not in uppercase. I'm not sure if there's an established pattern to add localized custom properties like this, but happy to update to var(--spectrum-accordion-item-text-transform, uppercase) or similar via a PR.

@simshanith we're tracking the addition of a text-transform custom property here. Being able to similarly manage the font-weight sounds like a great idea!
https://github.com/adobe/spectrum-css/blob/051b16be1e880fbabd98b0e98b0bbfa6173fc4fe/components/accordion/index.css#L106

My extension used the following variables and fallbacks:
text-transform: var(
  --spectrum-accordion-item-title-text-transform,
  uppercase
);
font-weight: var(--spectrum-accordion-item-title-text-font-weight, 500);

We'll be talking about this with the Design team. We need to figure out what the default styling should be and how we override it for a11y and localization needs.

Closing this as outdated but please reopen with additional context if this still needs to be addressed.


Filtering work item by assignee as unassigned does not work

Duplicate of https://openshift.io/openshiftio/openshiftio/plan/detail/1530


Proposal: rename the nodejs/iojs-nl WG to nodejs/nodejs-nl

Dear members of the io.js Dutch WG iojs-nl
It is proposed to rename this repo to:
nodejs/nodejs-nl
As part of the io.js and node.js convergence, node.js releases are now based on the codebase and user base of the converged node.js and io.js communities. A number of the resources and repositories have already been renamed.
In the absence of objections or other discussion, this rename will occur on or after Oct 28, 2015
However, active language working groups should take ownership of this issue and discuss/dispose of it according to their own processes.
For more information or to discuss the overall issue, please see and comment on https://github.com/nodejs/node/issues/2525
This statement was authorized by the Node.js TSC
Cc: @nodejs/iojs-nl

done

ref https://github.com/nodejs/nodejs-nl/commit/143be503833786a3feccdbeae884e0368e441c88


New update changed all saved worlds to "world"

After updating to the newest version, all "world" values in datastore.json were changed to "world". This caused all of my infoheads to be wiped until manually fixing the json file.

Hi, thanks for posting the issue!
The latest update hasn't actually changed any of the serialiser logic which can be shown by the timestamps of the code on here. When this happens, it usually means that the world hasn't loaded yet. Maybe because you're using a different world manager or plugin was loaded externally e.g plugman. I can't unfortunately regulate this effectively as it's a weigh up between code integrity (should the plugin deserialise the infoheads - breaking the plugin if interacted with) or default to 'world'. And then whenever it actually gets saved to the json file, a file save was initiated for whatever reason that may be.
But incase it wasn't one of those reasons, can you send the following:

World Management Plugin(s) e.g Multiverse & version
Plugin Management Plugin(s) e.g Plugman & version
Server Version & Java version running
Server software e.g Spigot

You should add load: POSTWORLD to the plugin.yml to ensure the plugin loads after world management. We do however use Multiverse.

Closing, cannot replicate


[BUG]: Communiction failed, but works with SevenW/Plugwise-2-py

Describe the bug.
I've been using https://github.com/SevenW/Plugwise-2-py for years with about a dozen Circles and one Circle+, but I'd like to switch to this. However, I get the following:
2022-12-15 23:03:36.500 DEBUG (MainThread) [custom_components.plugwise.usb] Connect to USB-Stick
2022-12-15 23:03:37.320 ERROR (MainThread) [custom_components.plugwise.usb] Connecting to Plugwise USBstick communication failed
2022-12-15 23:03:37.320 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Stick' for plugwise integration not ready yet; Retrying in background
2022-12-15 23:03:46.955 DEBUG (MainThread) [custom_components.plugwise.usb] Connect to USB-Stick
2022-12-15 23:03:46.973 ERROR (MainThread) [custom_components.plugwise.usb] Connecting to Plugwise USBstick communication failed
``

This just loops, no matter how long I wait.

Stick is a `Bus 001 Device 005: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC`

I'm passing this into the docker container with `--device=/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9003tBk-if00-port0` and i'm setting it privilegd, but to no avail.

### Expected behavior

Connect to the circle+ and actually work. Or at least be more verbose about what isn't working.

### What version of Home Assistant Core has the issue?

2022.12

### What type of installation are you running?

Home Assistant Container

### How and which version of the integration do you have installed?

HACS

### What kind of Plugwise device is having issues?

USB: Stick

### What firmware version is your Plugwise product at?

unsure, no mobile app. definitely very old.

### Home Assistant Logging (optional)

2022-12-15 23:03:36.500 DEBUG (MainThread) [custom_components.plugwise.usb] Connect to USB-Stick
2022-12-15 23:03:37.320 ERROR (MainThread) [custom_components.plugwise.usb] Connecting to Plugwise USBstick communication failed
2022-12-15 23:03:37.320 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Stick' for plugwise integration not ready yet; Retrying in background
2022-12-15 23:03:46.955 DEBUG (MainThread) [custom_components.plugwise.usb] Connect to USB-Stick
2022-12-15 23:03:46.973 ERROR (MainThread) [custom_components.plugwise.usb] Connecting to Plugwise USBstick communication failed
2022-12-15 23:03:56.976 DEBUG (MainThread) [custom_components.plugwise.usb] Connect to USB-Stick
2022-12-15 23:03:56.977 ERROR (MainThread) [custom_components.plugwise.usb] Connecting to Plugwise USBstick communication failed

### Diagnostics information

3.10 or whatever is in the HA core docker image

### Additional information

Switching back to SevenW Plugwise works immediately after i remove plugwise-beta.

Turned out to be an issue with passing USB into Docker container. Works great so far :)


Add support for iOS devices

Xcode lets you build and deploy free or charge, otherwise a paid apple developer account is required.
Xamarin.Forms already allows to code for iOS, but currently we can't preview and fix the bugs.

Probably impossible :(


OMG.ChildChain.SyncSupervisor can die quietly

If OMG.ChildChain.SyncSupervisor dies (e.g. when a child process failed to restart after crashing), it dies silently, leaving omg_child_chain app damaged.
Notes

OMG.Watcher.SyncSupervisor is a similar, except it does produce a related (but not explicit enough) log message about BlockGetter going down. I think same fix should apply there

hey @pdobacz have you had another thought about this?
I would simply do what we've done for ethereum client monitoring.
If OMG.ChildChain.Monitor or OMG.Watcher.Monitor receive an EXIT message in
# there's a supervisor below us that did the needed restarts for it's children
  # so we just ignore the exit from the supervisor, if the alarm clears, we restart it
  def handle_info({:EXIT, _from, _reason}, state) do
    {:noreply, state}
  end

raise an alarm, unhealthy_node, and Logger.error the exit. And add the alarm type to the Health plug of each RPC applications, so that we cut the wire for new requests.
Now this really is unrecoverable error, that would likely happen if EthereumEventListeners or any if it's dependencies had a bug. Do we agree on that?

hey @pdobacz have you had another thought about this?

not in depth, no :(. So to regurgitate, the thing that I guess still bugs me is this:
We raise alarm on an unrecoverable error in code ran under the Monitor, while we crash the VM on a similar error in code ran outside this "protective umbrella". Where's the line drawn here?
I still have a hunch that we should fail louder, whenever broken code is executed. With an alarm, we're relying on a number of moving pieces (alarms themselves, get_alarm endpoint, datadog) to notify us about the condition, which might be anything, including cases when we don't want continue running at all.

First batch done here: https://github.com/omisego/elixir-omg/pull/1027
Second part comes with events going to Datadog.


Product Description

Product Description
High Level Overview

Problem Statement

Moments of Charm

Product Sketches

Hey @irm1005-itec1005-fall-2023/pixelvortex - check your text - I think it's in the comments

Awesome stuff @irm1005-itec1005-fall-2023/pixelvortex - just don't forget to add in the text under the headings (Overview, problem statement, and moments of charm)

Hey @irm1005-itec1005-fall-2023/pixelvortex - just a friendly reminder that this is not complete - I don't see anything written for the headings (Overview, problem statement, and moments of charm).
I can't offer constructive advice without the context that helps me understand the sketch you provided.


Problem when build a PC Standalone App

[x] I am at the right place and my issue is directly related to ROS#. General technical questions I would post e.g. at ROS Answers or Stack Overflow. For library-specific questions I would look for help in the corresponding library forums.
[x] I have thoroughly read the Contributing Guideline and writing this issue is the right thing to do in my case.

I have a question!

[x] I searched the Wiki, open and closed issues for an answer. I tried my best to find the answer by myself without success. I believe that the discussion we will have in this issue, and the solutions we might find, will help me, and likely other community members who have a similar problem.

Here is my question:
I'm trying to use Auto Generate Messages to generate custom messages.
It works well when I run in Unity with Play button.
But when I build a PC Standalone Application, it returns the following error:
NullReferenceException: Object reference not set to an instance of an object
  at RosSharp.RosBridgeClient.UnityPublisher`1[T].Start () [0x0000d] in C:\Users\flyma\Workspace\unity\caster_moma_remote\Assets\RosSharp\Scripts\RosBridgeClient\RosCommuncation\UnityPublisher.cs:31
  at RosSharp.RosBridgeClient.HeadController.Start () [0x00044] in C:\Users\flyma\Workspace\unity\caster_moma_remote\Assets\Scripts\HeadController.cs:24

(Filename: C:/Users/flyma/Workspace/unity/caster_moma_remote/Assets/RosSharp/Scripts/RosBridgeClient/RosCommuncation/UnityPublisher.cs Line: 31)

It seems that did not find a ros connector, but I don't know why.
Here's my code
using System.Collections;
using System.Collections.Generic;
using UnityEngine;
using RosSharp.RosBridgeClient;

namespace RosSharp.RosBridgeClient
{
    [RequireComponent(typeof(RosConnector))]

    public class HeadController : UnityPublisher<MessageTypes.PanTiltMsg.PanTiltCmd>
    {
        private Camera cam;
        private MessageTypes.PanTiltMsg.PanTiltCmd message;
        private MessageTypes.PanTiltMsg.PanTiltCmd last_message;
        private float previousRealTime;
        private Vector3 previousPosition = Vector3.zero;
        private Quaternion previousRotation = Quaternion.identity;

        protected override void Start()
        {
            message = new MessageTypes.PanTiltMsg.PanTiltCmd(0.0f, 0.0f, 30);
            last_message = new MessageTypes.PanTiltMsg.PanTiltCmd(0.0f, 0.0f, 30);
            cam = GameObject.Find("VRCamera").GetComponent<Camera>();
            base.Start();
        }

        private void FixedUpdate()
        {
            UpdateMessage();
        }

        private UnityEngine.Vector3 GetEuler(UnityEngine.Quaternion q)
        {
            float r11 = -2.0f*(q.y*q.z - q.w*q.x);
            float r12 = q.w*q.w - q.x*q.x - q.y*q.y + q.z*q.z;
            float r21 = 2.0f*(q.x*q.z + q.w*q.y);
            float r31 = -2.0f*(q.x*q.y - q.w*q.z);
            float r32 = q.w*q.w + q.x*q.x - q.y*q.y - q.z*q.z;

            UnityEngine.Vector3 ret = new  UnityEngine.Vector3();
            ret.z = Mathf.Atan2(r31, r32);
            ret.y = Mathf.Asin (r21);
            ret.x = Mathf.Atan2(r11, r12);

            return ret;
        }

        private void UpdateMessage()
        {
            // float deltaTime = Time.realtimeSinceStartup - previousRealTime;

            // Vector3 linearVelocity = (PublishedTransform.position - previousPosition)/deltaTime;
            // Vector3 angularVelocity = (PublishedTransform.rotation.eulerAngles - previousRotation.eulerAngles)/deltaTime;

            // message.linear = GetGeometryVector3(linearVelocity.Unity2Ros()); ;
            // message.angular = GetGeometryVector3(- angularVelocity.Unity2Ros());

            // previousRealTime = Time.realtimeSinceStartup;
            // previousPosition = PublishedTransform.position;
            // previousRotation = PublishedTransform.rotation;

            Debug.Log("Position:" + cam.transform.position + ", Rotation:" + GetEuler(cam.transform.rotation));

            message.yaw = -Mathf.Rad2Deg * GetEuler(cam.transform.rotation).y;
            message.pitch = Mathf.Rad2Deg * GetEuler(cam.transform.rotation).x;

            if(message.yaw > 50) message.yaw = 50;
            if(message.yaw < -50) message.yaw = -50;
            if(message.pitch > 50) message.pitch = 50;
            if(message.pitch < -50) message.pitch = -50;

            if(Mathf.Abs(message.pitch-last_message.pitch) > 5 || Mathf.Abs(message.yaw-last_message.yaw) > 5) {
                last_message.yaw = message.yaw;
                last_message.pitch = message.pitch;

                Debug.Log("aaa"+message);
                Publish(message);
            }
        }
    }
}

I'm using Unity 2019.4.13f1c1 with steamvr and latest ros_sharp from repo.

Hi @flymaxty !
all your custom messages seem to work fine. The error above is thrown in line 31 of the UnityPublisher base class:
publicationId = rosConnector.RosSocket.Advertise<T>(Topic);

where rosConnector is null. It should have been assigned to a non-null value directly above in line 30.
Did you put your HeadController Component in the same GameObject as your RosConnector is in?
I don't understand why this error happens on PC Standalone build only. Do you have any other scripts that might disable or remove your RosConnector? Make sure that all required runtime scripts are included in the build, e.g. dont' put them in folders named Editor.
This might help you debugging: https://assetstore.unity.com/packages/tools/integration/log-viewer-12047 (I didn't test it myself yet, though.)
Best,
Martin

Hi @MartinBischoff ,
Thanks for your reply!
Did you put your HeadController Component in the same GameObject where your RosConnector is in?
Yes
Do you have any other scripts that might disable or remove your RosConnector?
No, but has multiple rosconnector in different GameObject
Make sure that all required runtime scripts are included in the build, e.g. dont' put them in folders named Editor.
Yes, I'm sure.
There are also other subscribers in differect GameObject, receiving image and joint_states. All subscriber works well, except this one, which publish message to ROS.
I also tried to rebuild the Libraries on my PC, replace RosBridgeClient.dll, and the result is same.

Hi @flymaxty
a RosConnector is intended to be used once per scene with all Publishers and Subscribers located in the same GameObject.
Why are you using several RosConnectors? Each of them sets up a separate Websocket connection. Does your build work when you disable all but one?
A RosConnector creates a new thread to communicate with ROS asynchronously to Unity's (fixed) update processes. Depending on your machine and cpu load, another reason for above error might be that the thread is not initialized in time. Nevertheless the RosConnector should be non-null?!
Can you Debug.Log the relevant objects RosConnector, RosSocket to clarify what is null when it should not be?

Hi @flymaxty did my suggestions help?
Please close this issue if it is resolved.

Hi @flymaxty did my suggestions help?
Please close this issue if it is resolved.

Hi @MartinBischoff ,
Sorry for the late reply, I was in a hard time to catch up with the project schedule, and forgot this issue after everythings done.
I recreate a new unity project and follow your suggest to create only one RosConnector per scene, and the issue was solved.
I'm not sure which is the key reason, but yes, I use RosConnector in wrong way.

Hi @MartinBischoff ,
Sorry for the late reply, I was in a hard time to catch up with the project schedule, and forgot this issue after everythings done.
I recreate a new unity project and follow your suggest to create only one RosConnector per scene, and the issue was solved.
I'm not sure which is the key reason, but yes, I use RosConnector in wrong way.


alpine image very large

It seems like the alpine image is one of the largest. It might be worth noting this in the README for users who expect alpine to be the smallest image:
linuxbrew/brew      latest              fc68ca22ec7e        5 hours ago          559MB
linuxbrew/debian    latest              881c478b7622        22 hours ago         447MB
linuxbrew/alpine    latest              10ca6eb17d94        22 hours ago         954MB

Yeah, that's because it has to jump through a bunch of hoops to install glibc, since Alpine Linux doesn't include glibc, and so it ends up installing a number of dependencies like ruby and gcc using both apk and gcc. The size of the image could be reduced by combining both RUN statements into a single RUN statement, and removing the packages installed using apk after the system is bootstrapped, as well as removing ~/.cache and the apk cache if there is one.
@AlJohri Are you interested in working on that?

Sure thing, I can give it a shot. I don't fully understand what's going on in the Dockerfile but I can definitely do those steps you outlined above.

Great! Feel free to submit a PR of your work in progress if you have any questions.


Overriding GalleryTemplate CSS?

Is there a way to access and override some of the GalleryTemplate CSS? For example, I'd like to change the font size/colour of the header text.
If I have a GalleryTemplate object, can I access the CSS attribute or is there another way?

Alternatively is there a way to add a sidebar to the GalleryTemplate?


Added ability to specify folder that contains tests.

-d parameter is used to specify location:
t-rest -d ./
Traverse through the folder and try to parse all .json files.

Added simple expectation system.

Added validation against json schema


screenshare in android is not working

CommsAPI.conference.startScreenShare(t)
        .then(() => {
            alert('success')
        }).catch((e) => {
            alert('error')
        });

Your android activity needs to inherit from CommsAPISDKAppCompatActivity.
Please let me know if this fixes your issue.

Your android activity needs to inherit from CommsAPISDKAppCompatActivity. Please let me know if this fixes your issue.

can you please elaborate with implementation so we can check??

@asadumair please look at the example here
`import io.dolby.sdk.comms.reactnative.android.activities.CommsAPISDKAppCompatActivity;
public class MainActivity extends CommsAPISDKAppCompatActivity {
/**

Returns the name of the main component registered from JavaScript. This is used to schedule
rendering of the component.
*/
@Override
protected String getMainComponentName() {
return "CommsSDKExample";
}
}`

we should write our customized code.
we are not getting this solution how we can implement this

@asadumair please look at the example here
`import io.dolby.sdk.comms.reactnative.android.activities.CommsAPISDKAppCompatActivity;
public class MainActivity extends CommsAPISDKAppCompatActivity {
/**

Returns the name of the main component registered from JavaScript. This is used to schedule
rendering of the component.
*/
@OverRide
protected String getMainComponentName() {
return "CommsSDKExample";
}
}`

It worked. Thanks for your help.


[BUG] interleave for 4 fields of bytes

At the moment, interleaving 4 bytes is bad: https://godbolt.org/z/s9TYcvnns
Reducing number of lanes does not help much.
The good solution is to have interleave_groups and then:
auto [ab0, ab1] = interleave_groups(group_size, a, b);
auto [cd0, cd1] = interleave_groups(group_size, c, d);
auto abcd0 =  interleave_groups(twice_group_size, ab0, cd0);
auto abcd1  = interleave_groups(twice_group_size, ab1, cd1);
return  kumi::cat(abcd0, abcd1);

I don't want to write interleave_groups without the new shuffle but I will use bcasts to solve the rgba usecase.
UPD: shuffle 2 is also not good.

https://github.com/jfalcou/eve/pull/1203


Keep timestamps of files copied from public to dist

Description
When syncing the dist directory to the web server all files are uploaded again and again (including static images) because all files in dist have a new timestamp.
I'd prefer to have the same timestamps for static files in dist as in public.
Suggested solution
Additionally to copyFileSync some code like this could be added:
var stat = fs.statSync(srcFile);
fs.utimesSync(destFile, stat.atime, stat.mtime)

Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

The timestamp of the files in the dist folder should be new, which is currently the correct behavior. If you wish to change it, I think you could change timestamps by a script instead of making it default to Vite. Also, the timestamps in public dir are not the same.

@fi3ework For generated files I totally agree, however unmodified files copied from the public folder should keep their timestamp (in my eyes). I see no benefit in losing file properties in this case but see the advantage of keeping (copying) them.

I'm not sure about this too. It's an extra fs step that most users aren't using, especially given that git clone always refreshes the time. I think it's better implemented as a postscript if this is a feature that you need.

@ashutosh887 I can't assign as far as I know because I only opened the issue but am not responsible in the project.

I also think this can be implemented as a plugin, so we don't add complexity to core if not everyone is going to use it.


CT-1522 Support enablement deleted projects cancel deletion

Jira: CT-1522
Connection PR: https://github.com/keboola/connection/pull/5314
Before asking for review make sure that:
Checklist

[x] New client method(s) has tests
[x] Apiary file is updated
[x] You declared if there is a BC break or not (will affect next release of a client)

Release

[x] I gave the PR a proper label:

major (BC break)
minor (new feature)
patch (backwards compatible fix)
no release (just test changes)

neviem ci, nepiseme do doc info o tom ze ten endpoint ide zavolat aj ked mas featuru

Može byť přidáno


Server Crash 1.16.4

Hello, I launch my server with 37 mods, at start it crash
Failed to create mod instance...
I send the crash report
crash-2021-04-06_16.40.18-fml.txt

The 1.16.5 version is not compatible with 1.16.4.

hum ok thx


autoCompleteType prop in textInput has been renamed to autoComplete

Docs update for 26003
PR 26004

There are two commits in this branch, the second one is to fix the hyperlink. But this PR lists only the first commit.


xIisMimeTypeMapping: Make ConfigurationPath a non-mandatory parameter

Details of the scenario you tried and the problem that is occurring
I tried to use the xIisMimeTypeMapping resource without specifying the ConfigurationPath parameter as it wasn't listed as a property in the repository readme.md file. I then got an error saying that I was missing a mandatory parameter ConfigurationPath. After looking at the source code there is already a default value defined for this parameter if it's not specified here so it's unnecessary for the parameter to be mandatory.
Verbose logs showing the problem
N/A
Suggested solution to the issue
In the MSFT_xIisMimeTypeMapping.psm1 file change lines 35, 107 and 181 from [Parameter(Mandatory = $true)] to [Parameter()] so that the parameter is not mandatory and will use the MACHINE/WEBROOT/APPHOST default value if not specified.
There should also be an update to the readme.md file to reference this parameter.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
N/A
The operating system the target node is running
N/A
Version and build of PowerShell the target node is running
N/A
Version of the DSC module that was used
3.1.1

This property needs to be mandatory and a key in the schema, otherwise it wouldn't be possible to have this configuration.
        xIisMimeTypeMapping Mpeg
        {
            Ensure            = 'Present'
            Extension         = '.mpeg'
            MimeType          = 'video/mpeg'
            ConfigurationPath = "IIS:\sites\Site1"
        }

        xIisMimeTypeMapping Mpeg
        {
            Ensure            = 'Present'
            Extension         = '.mpeg'
            MimeType          = 'video/mpeg'
            ConfigurationPath = "IIS:\sites\Site2"
        }

I think instead the default values (the constants) should be removed. 🤔

I'm not saying to remove the value or parameter as I know you need to pass something to the backend functions but making the parameter non-mandatory would allow you to pick up the default server-wide ConfigurationPath and still allow you to override using the config you posted. But yeah I guess you could go the other direction and keep it mandatory and then remove the unnecessary checks for a empty variables.
I'm not too sure what the best practices are in terms of DSC resources and default values (in normal modules it's widely accepted to set default values in the param blocks) but for me, I didn't know what I needed to pass in to the ConfigurationPath to add a mime type mapping at the server level until I checked the source code and saw that default value. I guess as long as it's documented somewhere or another example is added on how to add a mime type mapping at the server level then I'm not too fussed either way :)

Ah I just realised I glossed over your point and a key in the schema
I'm pretty new to DSC so I'm not too sure about how DSC schemas are implemented and used and didn't even look in the schema file until you mentioned it lol
So I guess those keys are what define the uniqueness of the DSC resources for want of a better phrase? In that case I understand why it would be a required parameter.

Yes exactly. You are correct that the properties that have the type Key define uniqueness. It cannot exist two resource instances with the same values for those parameters in the same configuration to be able to enforce the desired state. Mandatory parameter can for that reason not have default values.
There are four possible types of type qualifiers in the schema; Key, Required, Write, and Read.
For each schema property that has Key or Required the corresponding parameter in the PowerShell module script must mandatory. But only Key properties define uniqueness.


Using zarr group members as channels and layers within Napari

Thank you for the fantastic work on this project - it's a pleasure to use! I found myself wanting to use the ome-zarr format through zarr group members that represent channels which may be loaded as layers within Napari. Generally I'm new to the format, so I don't know if this would be an invalid use of the format or how this plugin works with Napari. Would it be possible to do something like this?
Here's an example of what I seek to do which iterates through the group members, adding each one to a Napari view. Ideally I'd love to load the ome-zarr file without needing to iterate through group members, using this plugin to navigate through them as layers automatically somehow. Again, I'm not sure if this is a "valid" approach (please let me know if not!).
Many thanks for any thoughts or feedback on this!

The OME-Zarr format currently (v0.4 and the imminent v0.5) doesn't have a mechanism for linking three separate images each with one channel. v0.6 with the transform work of RFC-5 will likely be able to do this for you. For the moment, you should be able to define 3 separate one-channel images, but you will need some loading code to have them all listed as layers.

Thanks so much @joshmoore ! Understood, looking forward to v0.6! :^)


fix: remove plug imports and ensure plug is loaded

closes #117

Hey @yordis, thank you for the contribution!
Just removing the imports won't do the trick - you also need to update the usage of the functions from it (see test failures).


Update sbt-projectmatrix to 0.9.0

Updates com.eed3si9n:sbt-projectmatrix from 0.5.2 to 0.9.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.eed3si9n", artifactId = "sbt-projectmatrix" } ]

labels: sbt-plugin-update, early-semver-major, semver-spec-minor, commit-count:1

Note that this removes the JVM suffix from all projects, and removes the 2_12 suffix from any project that is built only for 2.12 and 2.13 (leaving the 2_13 to indicate the less usual alternative).


[joy-ui][Autocomplete] Occasionally doesn't drop down a list for selection when the mouse clicks

Steps to reproduce
https://github.com/mui/material-ui/assets/6795515/7c4a429c-46d6-40fc-a02b-122df2b66ccf
Current behavior
occasionally does not display the list of options
Expected behavior
Selected, click, focus to show list for selection.
Context
No response
Your environment

npx @mui/envinfo
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

Search keywords: JoyUI AutoComplete occasionally does not drop down

@stone89son It's hard to reproduce this based on a video 😓 though I may have an idea of the cause of this – are you able to reproduce it with the Material UI and Base UI autocomplete components?

Material UI: https://mui.com/material-ui/react-autocomplete/
Base UI: https://mui.com/base-ui/react-autocomplete/

I'm not saying that there's an issue with the autocomplete of base-ui or material-ui. In the video I recorded, it's Joy-UI. You can visit the link to reproduce the error. It will happen immediately.
https://mui.com/joy-ui/react-autocomplete/

@stone89son They are all built using the same hook from Base UI
Joy's autocomplete is mostly layers of styling over Base UI's useAutocomplete hook which provides all the functionality
That's why I asked if you can reproduce your issue with the Base/Material UI demos
Otherwise, I can't reproduce this based on your screen recording so far

I tried with Base UI it's no problem.
but with Joy UI any AutoComponent has that problem.

I tried my company's computer, and my computer had Bug.
Chrome is the latest version.
Windows 10
Now i captured video:
https://github.com/mui/material-ui/assets/6795515/5e30d646-00ab-4f08-b55b-d33fcd3fe815

I've discovered how to reproduce the bug, just hover the mouse over the border of the AutoComplete and click.
https://github.com/mui/material-ui/assets/6795515/6ba1bc04-6292-4998-a428-67807cc784e6


Working on the same thing

Hi! Just wanted to mention that basically, we're working on the same thing and if you have any suggestions or something that was missing on pagespeed_exporter (https://github.com/foomo/pagespeed_exporter) feel free to ask!
Great work by the way!

Hi. I know the Pagespeed Exporter and i also used it bevor. I really like it and there are now Feature i was missing. The reason why i created the Lighthouse Exporter is because the results i get from Pagespeed are different from my local Lighthouse tests. My local Results are more realistic to actually tests on device with for example 3G.
I currently have some Problems with my Exporter because Lighthouse is build to only run on test at a time. So there is some work todo that it runs perfectly.
And thanks that you like my work!


Chat parameters aren't saved when closing StreamGlass

Parameters saving wasn't implemented, it is now done. Fixed by commit ce2ad47d4d9a4ddd0fae16bfacf59c8b70d63d7e


Include HISTORY and README file in package

setup.py requires both of those packages, without them, it's impossible
to install py-translate from tar.gz package
Fixes #8

Sure, thanks for the heads up.
Looks good to me


"Faith Pd" is hard-coded as the axis label in alpha group significance box plots

Update here.

@gregcaporaso: should we rename to something more generic (e.g. 'Metric'), or should we provide an option to specify the metric name as an argument, or some other option?

I think viewing SampleData[AlphaDiversity] as a pd.Series will have the metric name available via .name. Can you try that out?


Adding Support For tailwindcss v1.2.0

I have gone ahead and added the classes from tailwind v1.2.0 release
I think I got them all. Most of them were CSS Transitions, CSS Transforms, and Grid Utilities.
I tried to keep them in order based on what I gleamed off of Adam Wathan's example code from the tailwindcss docs
I'm open for re-ordering of the classes.

Hmm.. I feel like according to the documentation here we should maybe move the classes box-border, box-content to the very top of the class priority.
I also think maybe the row-spans should be closer to the colspans. It feels a little disjoint to have legacy classes involving width & height sitting between grid related classes.
I'd probably be a little more comfortable keeping the order consistent in this area to the one listed in the sidebar on the site:

I'll need to make a few grids to get a feel for it. Anyone else have any thoughts?

I made these changes you suggested. When it came to Grid Auto Flow I moved that to the top. Because it felt like using flex-row. I can move Grid Auto Flow to last though if you would like.


use objenesis 2.6

This change excludes old version of objenesis from easymock and mockito, and use objenesis 2.6 as a dependency.

Coverage decreased (-0.004%) to 81.189% when pulling cb88a8a37eafcbfec32be2307609e6f36b20ad8e on neozwu:objenesis-dep into c48dc6d4fc2ac5830181cd57b925ecf858aea613 on GoogleCloudPlatform:master.

LGTM

Coverage remained the same at 81.193% when pulling 0d6e5942ae30d352c481aff38f0e800ba8734417 on neozwu:objenesis-dep into c48dc6d4fc2ac5830181cd57b925ecf858aea613 on GoogleCloudPlatform:master.

Changes Unknown when pulling e59bde648b2813cc10569801cb2068d2db6a32c5 on neozwu:objenesis-dep into ** on GoogleCloudPlatform:master**.


Refactor vmlCreate() so that it does not leak closure to TypeError

When document.namespaces.add() throws TypeError: Cannot read property 'add' of undefined, the TypeError persists in the memory heap snapshot.
I am not sure why Google Chrome does not garbage collect this TypeError because clearly it is not used in the returned fn. But if you look at memory Heap snapshot, you can see it persists after garbage collection.

Try it with any leaflet map such as https://leafletjs.com/ and search heap snapshot for 'TypeError' and you will see it was never garbage collected after this simple feature test was performed.

With this change, the TypeError is garbage collected and not in memory heap snapshot.
I don't think it's serious... but the change is simple and with the change I can easily see the TypeError is removed from the heap snapshot in my application.

And thanks for the detailed investigation, @darcyparker !


Bug in db_create.py

Hello,
I found bad command for oracle dialect in the file db_create.py
When I used the following command (db is SqlAlchemy engine):
etl.todb(table=table,dbo=db,tablename='TEST',create=True,drop=True,dialect='oracle')
this failed, because generated drop SQL script is not valid for Oracle database
in the file db_create.py is following line:
sql = u'DROP TABLE IF EXISTS %s;' % tablename
but Oracle doesn't support IF EXIST clause.
and there is another issue from Oracle point of view. In the file db_create.py is following line:
return text_type(sqlalchemy.schema.CreateTable(sql_table)
                 .compile(dialect=sql_dialect)).strip() + ';'

The issue is semicolon at the end of line , this semicolon caused that created SQL command failed in Oracle database.
Best regards
Paul

Hi Paul,
Thanks for reporting this, much appreciated.
Do you know if there is any alternative to "IF EXISTS" in Oracle?
On Sunday, March 1, 2015, developer999<EMAIL_ADDRESS>wrote:

Hello,
I found bad command for oracle dialect in the file db_create.py
When I used the following command (db is SqlAlchemy engine):
etl.todb(table=table,dbo=db,tablename='TEST',create=True,drop=True,dialect='oracle')
this failed, because generated drop SQL script is not valid for Oracle
database
in the file db_create.py is following line:
sql = u'DROP TABLE IF EXISTS %s;' % tablename
but Oracle doesn't support IF EXIST clause.
and there is another issue from Oracle point of view. In the file
db_create.py is following line:
return text_type(sqlalchemy.schema.CreateTable(sql_table)
.compile(dialect=sql_dialect)).strip() + ';'
The issue is semicolon at the end of line , this semicolon caused that
created SQL command failed in Oracle database.
Best regards
Paul
--
Reply to this email directly or view it on GitHub
https://github.com/alimanfoo/petl/issues/317.

--
Alistair Miles
Head of Epidemiological Informatics
Centre for Genomics and Global Health http://cggh.org
The Wellcome Trust Centre for Human Genetics
Roosevelt Drive
Oxford
OX3 7BN
United Kingdom
Web: http://purl.org/net/aliman
Email<EMAIL_ADDRESS>Tel: +44 (0)1865 287721

Hi Alistair,
I found this link with detailed explanation http://ora-exp.blogspot.cz/2013/03/oracle-drop-table-if-exists.html
I think the sufficient option is to use anonymous block:
BEGIN
EXECUTE IMMEDIATE 'DROP TABLE TABLE_NAME';
EXCEPTION
WHEN OTHERS THEN
IF SQLCODE <> -942 THEN
RAISE;
END IF;
END;
the SQLCODE 942 is exception when table doesn't exists, all others exceptions will be propagated
ORA-00942:	table or view does not exist
Best regards,
Paul

Thanks Paul, much appreciated. I'll give some thought to how best to
incorporate this.
On Mon, Mar 2, 2015 at 7:22 PM, developer999<EMAIL_ADDRESS>wrote:

Hi Alistair,
I found this link with detailed explanation
http://ora-exp.blogspot.cz/2013/03/oracle-drop-table-if-exists.html
I think the sufficient option is to use anonymous block:
BEGIN
EXECUTE IMMEDIATE 'DROP TABLE TABLE_NAME';
EXCEPTION
WHEN OTHERS THEN
IF SQLCODE <> -942 THEN
RAISE;
END IF;
END;
the SQLCODE 942 is exception when table doesn't exists, all others
exceptions will be propagated
ORA-00942: table or view does not exist
Best regards,
Paul
--
Reply to this email directly or view it on GitHub
https://github.com/alimanfoo/petl/issues/317#issuecomment-76789623.

--
Alistair Miles
Head of Epidemiological Informatics
Centre for Genomics and Global Health http://cggh.org
The Wellcome Trust Centre for Human Genetics
Roosevelt Drive
Oxford
OX3 7BN
United Kingdom
Web: http://purl.org/net/aliman
Email<EMAIL_ADDRESS>Tel: +44 (0)1865 287721

Hi @developer999, sorry for long silence on this.
Regarding the IF EXISTS problem, I think I would propose to just remove the "IF EXISTS" for all databases. This should be acceptable, as the default for the drop argument is False, so in general a user has to actively choose to try and drop the DB. So if the user attempts to drop a non-existent database and gets an error, that's reasonable.
Regarding the trailing semicolon problem, I'll investigate whether removing this causes any problems with mysql or postegres.


Include an option or layout change to make all Properties tabs visible without overflow.

What feature or improvement do you think would benefit Files?
Issue
Currently, the Properties panel uses tabs with an icon and text that displays 2 tabs, and puts the others in a roll-over menu.
This functions well for users who wish to access only the first two tabs on a regular basis; but as someone who regularly modifies shortcuts (for example), I have to rely on the roll-over menu about 80% of the time when opening the Properties menu (to the point where I tend to fall back to Windows File Explorer for such tasks more often than not).
Current Implementation

Proposal
The idea would be to either include an option or switch the default behavior to an icon-based display exclusively.
This would easily allow up to half a dozen (if not more) tabs to be displayed at once.
Here is a rough mock-up. It is mostly missing a "current tab" indicator of some sort; a small dot/bar below the icon, maybe? Or a background/border highlight?
Proposed Implementation

Requirements

Change the Properties menu's tab design to be icons only.
Remove the roll-over tabs menu, unless the UI is unable to display all tabs at once.
(Optional) Set an option to toggle between the current and proposed behavior.

Files Version
Version: 2.4.8
Windows Version
Windows 11 22621.963
Comments
Not including the tab title may present a slight reduction in first-use user experience; however:

This is a "more advanced" use of Files (meaning most users will tend to be familiar with the UI/UX at this point)
The hover title should be intuitive enough if it appears rapidly.

This is standard behavior in other parts of the UI:

What happens if you resize the window?

What happens if you resize the window?

Currently, the overflow tabs get put back inline.
However, there are 2 issues with this:

The Properties window always defaults to the same size; so you have to resize it every time… which isn't a solution at all.
As new tabs get added (and there are 2 in the works, at least that I know of), resizing will become less and less of a viable solution.

This was resolved in main.


Demo Link and Supermentor review

Project
TrustIn
Changes
Added project Demo link and supermentor review to Week 4 milestone

Raise PR for week-5 as well


Error handling clarification

Following the examples here a snippet of my code:
process.on('uncaughtException', err => {
    console.error((new Date).toUTCString() + ' uncaughtException:', err);
    console.error("Exiting...");
    process.exit(1)
})

// ...

var DB = require('node-adodb'), connection = DB.open('Provider=Microsoft.Jet.OLEDB.4.0;Data Source=pathToDatabase.mdb');

function submit(data, callback) {
    var id = data.id;
    var query = // create query from data values

    connection
        .execute(query)
        .then(data => {
            return callback({ id: id, success: true });
        })
        .catch(error => {
            console.error('submit query failed: ' + error.process.message);
            return callback({ id: id, success: false });
        });
}

So I'm expecting that if the query fails it nicely calls the callback reporting the failure.
To test it, after initialization I suddenly remove the database file. The error is apparently handled:

submit query failed: Impossibile trovare il file pathToDatabase.mdb

but then the program crashes due to an "unhandled error":

Tue, 15 Jan 2019 12:33:23 GMT uncaughtException: { Error: Unhandled "error" event. ([object Object])
Exiting...

I'm running Node v8.12.0 under Windows 7.
I forgot something in the configuration/use of node-adodb?

Some exception throw by cscript, but cscript exception information is bad！

[I don't think is so nice to immediately close an issue without waiting for a while if users have any further question...]
Anyway, I kindly ask an example how to handle such a situation. I understand cscript exception information is bad, but I cannot let my program crash. Would you mind to show m how to change my snippet above in order to correctly catch the exception? Thanks in advance.


Remove IHostApplicationLifetime from ASP.Net Core 2.1

Summary by CodeRabbit
Release Notes

Documentation

Updated README.md to clarify configuration and usage of the GraphQL.AspNetCore3 package, including removal of unnecessary service requirements and enhanced explanations of GraphQL request handling.

Bug Fixes

Improved error handling and validation in various test scenarios, ensuring accurate responses for GraphQL operations.

Tests

Enhanced coverage and robustness of authorization and middleware tests, including new test cases and refined error handling for different configurations and edge cases.

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

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 92.691%

Totals

Change from base Build<PHONE_NUMBER>5:
0.02%

Covered Lines:
1933

Relevant Lines:
2039

💛  - Coveralls


Update documentation to match method names

Current coverage is 76.21%

Merging #3369 into master will increase coverage by +1.83% as of 0ace783

@@            master   #3369   diff @@
======================================
  Files            5       5
  Stmts         3002    2489   -513
  Branches         0       0
  Methods
======================================
- Hit           2233    1897   -336
  Partial          0       0
+ Missed         769     592   -177

Review entire Coverage Diff as of 0ace783

Powered by Codecov. Updated on successful CI builds.


chore: remove unnecessary instructions in trace_end

In the previous code before https://github.com/nervosnetwork/ckb-vm/pull/298 , CKB_VM_ASM_LABEL_OP_CUSTOM_TRACE_END and prepare_trace were sharing the same code block.
Now the CKB_VM_ASM_LABEL_OP_CUSTOM_TRACE_END will only be triggered when the next trace is executed sequentially, it does not run at address 0, so we can remove the unnecessary length checking here.

Consider a testcase
main.S
  .global _start
_start:
  li a0, 0
  li a7, 93
  ecall

main.lds
SECTIONS
{
. = 0x00;
.text : { *(.text) }
}

$ riscv64-unknown-elf-as -o main.o main.S
$ riscv64-unknown-elf-ld -T main.lds -o main main.o

$ ckb-vm-runner /tmp/main
Segmentation fault (core dumped)

I didn't realize that the instruction could be constructed in the zero address, close this PR and add a test case PR #312

This is not necessarily a problem, but I do have something that I want to raise a discussion here:
Depending on how you look at the problem, the reason that the about test case triggers a segfault for this PR, could be a coincidence: .CKB_VM_ASM_LABEL_OP_CUSTOM_TRACE_END occurs before .prepare_trace in this part of code. In other words, after the initial setup phase of ckb_vm_x64_execute function, we first execute .CKB_VM_ASM_LABEL_OP_CUSTOM_TRACE_END, not .prepare_trace.
If we swap the code order between .CKB_VM_ASM_LABEL_OP_CUSTOM_TRACE_END and .prepare_trace, I believe the above test case would work.
Right now, the 2 labels above are really used for 2 different purposes:

.CKB_VM_ASM_LABEL_OP_CUSTOM_TRACE_END is used to handle sequential code execution
.prepare_trace is used to handle jumps

That brings a question: when we first execute ckb_vm_x64_execute, are we expecting to handle a jump, or a sequential code execution? I tend to believe that we should be expecting to handle jumps when we first enter ckb_vm_x64_execute, which means we should execute .prepare_trace after the initial setup in ckb_vm_x64_execute. That also means the code in this PR could be applied.
Thoughts?

+1 for switching the label, btw, if I understand correctly, the cycle overflow and max cycles exceeded checking can be removed from . CKB_VM_ASM_LABEL_OP_CUSTOM_TRACE_END also after switching?

will submit a new pr later


Struct for zoom level

Created a struct for ZoomLevel
💻 Examples

🚨 Test instructions

✔ PR Todo

[x] Included links to related issues/PRs
fixes https://github.com/maplibre/maplibre-rs/issues/95

android build is failing because of github actions, lets just merge this and see what happens


ERROR "Cannot read properties of undefined (reading 'currentPage')" - after build of new code

I posted this last week and received no response but it was marked closed???.  Just did a git pull of most recent code and still same issue..  Can u help me out with why this going on or how i can fix??  Thank you
Hello all. To start with I am using 'docker-compose.postgres.yml'. Been using Teldrive for 6ish months and love it. I have a build that is prolly 3 weeks old and works as usual with no problem. Bur for past 2 weeks if i build with updated code from github I get the error below.  However if I rollback  to previous build it is no problem.  Why is this happening and did something break or change??  And if something did change how can i fix it on my end.

I can connect to DB so I really dont know why it is doing this.

version: "3.8"

services:
  server:
    image: bpawnzz/teldrivecustom:v1
    restart: always
    hostname: teldrive
    container_name: teldrive
    volumes:
      - ./session.db:/session.db:rw
      - ./config.toml:/config.toml
    ports:
      - 1234:8080
    depends_on:
      db:
        condition: service_healthy
    dns:
      - <IP_ADDRESS>

  db:
    image: groonga/pgroonga
    container_name: teldrive_db
    hostname: postgresTeldrive
    restart: always
    environment:
      - POSTGRES_USER=teldrive
      - POSTGRES_PASSWORD=secret
    volumes:
      - ./postgres_data:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD", "pg_isready", "-U", "teldrive"]
      interval: 10s
      start_period: 30s
    dns:
      - <IP_ADDRESS>

As long as you have a DB, you won't lose any data. Test it on other OSs like Windows. Alternatively, you can also test it with Oracle's free VPS. In my experience, it also works well on Oracle's free VPS.

Try these steps.

Start with a new db.
Log in to make sure everything work.
Truncate the 'files' table in your new db.
Export 'files' table from your old db.
Import it to your new db.

Try these steps.

Start with a new db.
Log in to make sure everything work.
Truncate the 'files' table in your new db.
Export 'files' table from your old db.
Import it to your new db.

Just saw this.. Will deff give it a go.  Thank you for the response!

Try these steps.

Start with a new db.
Log in to make sure everything work.
Truncate the 'files' table in your new db.
Export 'files' table from your old db.
Import it to your new db.

So i did what you said to a t.  and i am now receiving this error in my database logs.

That error meant that you are using old db with newer version of teldrive. Which version are you able to run?

For anyone interested I was able to successfully migrate my db with the following script..  Your welcome ;)
import psycopg2
from psycopg2.extras import execute_values, Json
import json

# Source database connection details
SRC_DB = {
    'host': '<IP_ADDRESS>',
    'port': '5431',
    'database': 'defaultdb',
    'user': 'teldrive',
    'password': 'secret'
}

# Destination database connection details
DEST_DB = {
    'host': '<IP_ADDRESS>',
    'port': '5432',
    'database': 'teldrive',
    'user': 'teldrive',
    'password': 'secret'
}

# List of tables to transfer (in order, considering foreign key dependencies)
TABLES = [
    'teldrive.users',
    'teldrive.channels',
    'teldrive.bots',
    'teldrive.uploads',
    'teldrive.sessions',
    'teldrive.files',
    'public.goose_db_version'
]

def adapt_dict(python_dict):
    return Json(python_dict)

psycopg2.extensions.register_adapter(dict, adapt_dict)

def connect_db(db_config):
    return psycopg2.connect(**db_config)

def get_table_data(cursor, table):
    cursor.execute(f"SELECT * FROM {table}")
    return cursor.fetchall()

def get_column_names(cursor, table):
    cursor.execute(f"""
        SELECT column_name
        FROM information_schema.columns
        WHERE table_schema = %s AND table_name = %s
        ORDER BY ordinal_position
    """, table.split('.'))
    return [col[0] for col in cursor.fetchall()]

def transfer_table(src_cursor, dest_cursor, table):
    print(f"Transferring data for table: {table}")

    # Get column names and types
    src_cursor.execute(f"""
        SELECT column_name, data_type
        FROM information_schema.columns
        WHERE table_schema = %s AND table_name = %s
        ORDER BY ordinal_position
    """, table.split('.'))
    columns_info = src_cursor.fetchall()
    columns = [col[0] for col in columns_info]
    column_str = ', '.join(columns)

    # Fetch data from source
    src_cursor.execute(f"SELECT {column_str} FROM {table}")
    data = src_cursor.fetchall()

    if not data:
        print(f"No data to transfer for table: {table}")
        return

    # Prepare the INSERT statement with type casting for JSONB and numbered placeholders
    insert_columns = []
    for i, (col, data_type) in enumerate(columns_info, start=1):
        if data_type == 'jsonb':
            insert_columns.append(f"CAST(%s AS JSONB)")
        else:
            insert_columns.append(f"%s")
    insert_column_str = ', '.join(insert_columns)

    insert_stmt = f"INSERT INTO {table} ({column_str}) VALUES ({insert_column_str}) ON CONFLICT DO NOTHING"

    # Convert any JSON strings to dicts for proper handling
    processed_data = []
    for row in data:
        processed_row = list(row)
        for i, (col, data_type) in enumerate(columns_info):
            if data_type == 'jsonb':
                if isinstance(processed_row[i], str):
                    try:
                        processed_row[i] = json.dumps(json.loads(processed_row[i]))
                    except json.JSONDecodeError:
                        processed_row[i] = json.dumps({})  # Default to empty JSON object if parsing fails
                elif processed_row[i] is None:
                    processed_row[i] = json.dumps({})  # Default to empty JSON object if None
                else:
                    processed_row[i] = json.dumps(processed_row[i])  # Ensure it's a JSON string
        processed_data.append(tuple(processed_row))

    # Execute the INSERT
    dest_cursor.executemany(insert_stmt, processed_data)

    print(f"Transferred {len(data)} rows for table: {table}")

def main():
    src_conn = connect_db(SRC_DB)
    dest_conn = connect_db(DEST_DB)

    src_cursor = src_conn.cursor()
    dest_cursor = dest_conn.cursor()

    try:
        for table in TABLES:
            transfer_table(src_cursor, dest_cursor, table)
            dest_conn.commit()

        print("Data transfer completed successfully!")

    except Exception as e:
        print(f"An error occurred: {e}")
        dest_conn.rollback()

    finally:
        src_cursor.close()
        dest_cursor.close()
        src_conn.close()
        dest_conn.close()

if __name__ == "__main__":
    main()

That error meant that you are using old db with newer version of teldrive. Which version are you able to run?

I'm officially running newest version and successfully migrated my db.  I just posted script in thread.


在容器内使用select，弹出框在滚动时显示异常。

Reproduction link
https://ng-zorro-antd-ivy-bzjjdp.stackblitz.io
Steps to reproduce
1、点击select弹出菜单框。
2、滚动滚轮，select滚出容器范围，菜单框显示异常。
What is expected?
select的菜单栏随select一起滚动，消失在容器内。
What is actually happening?
select的菜单栏随select一起滚动，select滚出可视范围，菜单栏位置异常。

Environment
Info

ng-zorro-antd
13.3.1

Browser
chrome

This PR will fix the issue mentioned above for all components created with the CDK Overlay that are inside modals or drawers: #8804.
As a temporary fix, you can follow these steps:

Create a wrapper inside your modal or drawer
Add the cdkScrollable directive to the wrapper
Set overflow: auto on the wrapper

This way, the wrapper will handle the scrolling.
You can refer to this link for a sample.