New command: List Outlook messages

Usage
outlook message list
Description
Gets all mail messages from the specified folder
Options

Option
Description

--folderId [folderId]
ID of the folder from which to list messages

--folderName [folderName]
Name of the folder from which to list messages

-o, --output [output]
Output type. json,text. Default text

--verbose
Runs command with verbose logging

--debug
Runs command with debug logging

Additional Information

must specify either folder ID or Name but not both
folderId and folderName autocomplete with well-known folder names (https://docs.microsoft.com/en-us/graph/api/resources/mailfolder?view=graph-rest-1.0)
if multiple folders with the same name are found, the command throws error asking the user to disambiguate the folder

Status update: command code is code-complete. Next step tests


Add pretty graphics to the website and examples

With #2  is done, add pretty graphics to the website and examples.
Current webpage is horrendous, and the examples use the same style.
http://meddelare.com/
http://meddelare.com/meddelare-examples

Have updated the layout and graphics, but it's far from a great design. Keeping this open hoping for contributions!

Closing due to Meddelare project shutdown.


@intlify/unplugin-vue-i18n not support HMR with Static bundle importing

Reporting a bug?
Using "@intlify/unplugin-vue-i18n": "^1.2.0"
I've follow README.md's guide to setup my project like reproduction section.
And I put locale files to src/locales/en.json, i18n works fine but dev server will refresh page everytime when I update the json file.
And I got output like this:
11:39:17 AM [vite] page reload src/locales/en.json

Is my setting wrong? Thanks for help!
Expected behavior
When I saving only the text section update.
Reproduction
// vite.config.ts
export default defineConfig({
  plugins: [
    vue(),
    vueJsx(),
    UnoCSS(),
    VueI18nPlugin({
      include: [path.resolve(__dirname, './src/locales/**')],
    }),
  ],
  resolve: {
    alias: {
      '@': fileURLToPath(new URL('./src', import.meta.url)),
    },
  },
});

// main.ts
import messages from '@intlify/unplugin-vue-i18n/messages';

import App from './App.vue';

const app = createApp(App);

app.use(createPinia());
app.use(
  createI18n({
    legacy: false,
    locale: 'en',
    globalInjection: true,
    fallbackLocale: 'en',
    messages,
  }),
);

Issue Package
unplugin-vue-i18n
System Info
System:
    OS: macOS 13.4.1
    CPU: (8) arm64 Apple M1
    Memory: 96.44 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.17.0 - /usr/local/bin/node
    npm: 9.6.7 - /usr/local/bin/npm
    pnpm: 8.6.12 - ~/.npm-global/bin/pnpm
  Browsers:
    Chrome: 116.0.5845.187
    Safari: 16.5.2
  npmPackages:
    @intlify/unplugin-vue-i18n: ^1.2.0 => 1.2.0
    vite: ^4.3.9 => 4.4.7
    vue: ^3.3.4 => 3.3.4
    vue-i18n: ^9.3.0 => 9.3.0

Screenshot
No response
Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the README
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.

It looks like this is blocked by Vite issue #12912.  If the code that was reverted as part of the PR referenced in the ticket is re-applied, then virtual module updates can be accepted, including the @intlify/unplugin-vue-i18n/messages virtual module


Message visibility timeout

Is your feature request related to a problem? Please describe.
From what I can tell the result of the lambda is either success or failure.  We'd like to use a message's visibility in order to retry a message after its timeout.  The only way I see to achieve similar functionality today is if the lambda were to add the message back to the queue.  The problem with that is the message goes to the back of the line.  It will now be subject to the queue's delay configuration as it will process messages already in the queue first.
Describe the solution you'd like
Provide a way to specify a message should not be acknowledged after processing so that it reappears in the queue after its visibility timeout.
Describe alternatives you've considered
As mentioned above we could add the message back to the queue but it will delay its processing based on the number of messages enqueued.
Additional context
We'd like to use this in order to throttle executions of CodeBuild builds.  We need to ensure only a limited number of builds are being performed at a time.  When under heavy load, or if a dependency is having issues, we will need to throttle the number of concurrent builds.  We're essentially wanting to wait until an execution slot is available or get as close to possible to that idea.  Lambda concurrent message configuration doesn't help as the lambda will only be executing for the duration of the start build request and not the full build.

You might look into using a dead-letter-queue, or another Lambda Function, to receive the events that you return failures for. Be aware that Lambda also has a configurable retry mechanism built-in for asynchronous events.
I'm closing this issue, as it is not unique to the Go runtime. You might try reaching out to customer support, or posting on the AWS forums, about the problem you're trying to solve.


Gunship Cannot Start Without debug_draw.glsl

Gunship is hard-coded to look for shaders/debug_draw.glsl on startup, so if that file doesn't exist then the game crashes with a rather unhelpful warning message about unwrapping an Err value. debug_draw.glsl is distributed with the Gunship source code, however the resource loader uses relative paths so it still won't find the file unless the developer copies it to their local shaders directory.
While there are a bunch of changes that need to be made to the resource manager and the way Gunship handles resource files in general, I think the solution here is to have the shader code hard-coded insude debug_draw.rs the same way that the debug wireframe meshes are. To do this will require the following:

Copy the contents of debug_draw.glsl into a raw string in debug_draw.rs.
In DebugDraw::new() remove the call to call to resource_manager.get_shader().
Split up ResourceManager::get_shader() into two functions: get_shader() and compile_shader() where get_shader() loads the contents of the file into a string and then passes it to compile_shader() which parses and those contents and has the renderer compile them.
Have DebugDraw::new() call resource_manager.comiple_shader() passing in the hard-coded shader string.

This issue has been invalidated for the time being due to the async refactor. If the issue crops up again we can re-open the issue.


(DRAFT) Support interoperability with Interledger

Details will be added soon.
Back in June (2017) that meant supporting hash locks (sha256 conditions). We should just do it!
/cc @diminator  @emschwartz

Issue #725 may be related.

Indeed, this means that one should always sign the transaction - rather than assuming the input-fulfillment has a signature forced

Out of curiosity, how long do BigchainDB transactions take to process? Also, do you guys have any plans to support some kind of payment channels (or would that be outside the scope of your use cases)?

Out of curiosity, how long do BigchainDB transactions take to process?

Once we've integrated Tendermint (i.e. in the next month or so), BigchainDB transaction finality should take around a second or so, for a globally-distributed network.

Also, do you guys have any plans to support some kind of payment channels (or would that be outside the scope of your use cases)?

I don't know of any plans to support any kind of payment channels.


Watch folder?

Hello, is there a way to watch folders for changes and then trigger organize?

This is not currently not integrated into organize itself, but a solution might be available for your OS:

linux: inotifywait (https://askubuntu.com/a/819290)
macOS: fswatch (https://stackoverflow.com/a/25524053/300783)
windows: Watch 4 Folder (https://www.raymond.cc/blog/3-portable-tools-monitor-files-folders-changes/)

But this is something that could be interesting for a lot of users. So thank you for the suggestion, I added to the todo list 👍

I'm currently looking for a moving solution on my unraid server and this would be a great thing to have. thinking about making a docker for this so it runs whenever a file changes and/or periodically.

@martinjuhasz I took a first stab at Dockerizing Organize for exactly the same reason. You can find the image here: https://hub.docker.com/r/dskaggs/docker-organize

@dskaggs cool, thanks for the effort. will absolutely give it a try. would love to see the ability to use inotifywait instead of a regular cron so i get my files instantly moved when ready. i can give it a try, but have not too much time currently. i also don't know how much overhead it is running it f.e. every minute.

@martinjuhasz I'll see what I can do. Feel free to comment here: https://github.com/dskaggs/docker-organize/issues/1

Some code examples for how to get this working under each OS would be really helpful here. I've been tinkering with this working on Linux and actually had more luck with inotify-hookable than inotify-tools.
inotify-hookable can be installed via most package managers. I'm on Kubuntu and so just used sudo apt install inotify-hookable.
https://metacpan.org/pod/App::Inotify::Hookable
# ~/.bash_profile
inotify-hookable -w ~/Downloads -c "organize run" --no-r &

-w ~/Downloads Watches my ~/Downloads directory.
-c "organize run" sets up the command to run when a file in my watched directory is modified.
--no-r disables recursive watching which is enabled my default.
& runs the process in the background (omitting this gave me troubles logging back in, naturally).

Loving organize BTW. Just started messing around with it yesterday. As a previous macOS Hazel user this is an itch I've been looking to scratch on Linux for some time :)


Passing datetime as option only initialized on server restart

In the following example, won't the minDate only be initialized when the server starts?
(datetime.date.today() + datetime.timedelta(days=1)).strftime('%Y-%m-%d')
So if I run this today 2019-01-24 it will result in 2019-01-25. But then tomorrow (unless server has been restarted) it will still be the same value?
datetime_field = forms.DateTimeField(
        widget=DateTimePicker(
            options={
                'minDate': (datetime.date.today() + datetime.timedelta(days=1)).strftime('%Y-%m-%d'),  # Tomorrow
                'useCurrent': True,
                'collapse': False,
            },
            attrs={
               'append': 'fa fa-calendar',
               'input_toggle': False,
               'icon_toggle': True,
            }
        ),
    )

Excellent point, it would have to be done in the view. I'm removing it from the example.


Azure portal link for Azure Spring Cloud

In step one of provision the service, the Azure portal link currently does not work due the fact it’s in private preview. Please use this link instead: https://ms.portal.azure.com/?microsoft_azure_marketplace_ItemHideKey=AppPlatformExtension#blade/Microsoft_Azure_Marketplace/MarketplaceOffersBlade/selectedMenuItemId/home/searchQuery/Azure Spring Cloud

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

ID: 6e98683b-f725-7c9f-8883-df20af1c9ddb
Version Independent ID: a7f9e113-0593-cb19-e3ee-f71a362478ee
Content: Launch an Azure Spring Cloud application using the Azure portal
Content Source: articles/spring-cloud/spring-cloud-quickstart-launch-app-portal.md
Service: spring-cloud
GitHub Login: @v-vasuke
Microsoft Alias: v-vasuke

@seanli1988 Thanks for the comment. We are actively investigating on the issue and will get back to you shortly with an update.

@seanli1988 Verified and updated the document as required. Thanks.


Optimize simplify name analyzer

Before

After

(it's the code fix recalculation for 1100 lines file from FSharp.Editing.Tests project from VFPT solution)
It looks like the diagnostics is called twice by VS, I think we should cache the last result in a Dictionary<DocumentId, TextVersion hash * ImmutableArray<Diagnostic>>

These speed improvements look great - but over 400 lines of code added with no tests? :(

Added the cache:

These speed improvements look great - but over 400 lines of code added with no tests? :(

It's all copied with adjustments, and the code is not used anywhere except this analyzer.

so how much faster is it now?

@forki 29 seconds => 800 ms ~= 36 times faster.

Cool. Now do that to the rest of the compiler :P
Am 14.01.2017 4:45 nachm. schrieb "Vasily Kirichenko" <
<EMAIL_ADDRESS>
@forki https://github.com/forki 29 seconds => 800 ms ~= 36 times faster.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/visualfsharp/pull/2254#issuecomment-272632037,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNMuGxhqhw8aOJ2FMdLNqn-7fY2e3ks5rSO2igaJpZM4Ljlnf
.

I've not optimized the compiler, I copied functions and make them fast for my particular case. In short, the existing functions return all items resolvable in a scope, my functions just check that an already resolved item can be resolved being prefixed with a given long ident. It's faster because 1. I pull the available items lazily, until the needed item is found 2. I know the kind of item (ctor, prop, ns or module, etc.) and search only for items of same kind. So these optimizations cannot be used in compiler.

I got that and was obviously joking.
Am 14.01.2017 4:53 nachm. schrieb "Vasily Kirichenko" <
<EMAIL_ADDRESS>
I've not optimized the compiler, I copied functions and make them fast for
my particular case. In short, the existing functions return all items
resolvable in a scope, my functions just check that an already resolved
item can be resolved being prefixed with a given long ident. It's faster
because 1. I pull the available items lazily, until the needed item is
found 2. I know the kind of item (ctor, prop, ns or module, etc.) and
search only for items of same kind. So these optimizations cannot be used
in compiler.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/visualfsharp/pull/2254#issuecomment-272632497,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNJTuW-bkndIePQG7UPbQDBinivWPks5rSO9ygaJpZM4Ljlnf
.

@vasily-kirichenko is it wroth to put some comments on the copied functions, to mention the place they are copied from?
I'm thinking that if down the road the original functions change, having that mention would help figure out if catch-up is necessary in those customized functions.

A few IDE tests failes
Test Run Summary
    Overall result: Failed
   Tests run: 2936, Passed: 2901, Errors: 9, Failures: 26, Inconclusive: 0
     Not run: 99, Invalid: 0, Ignored: 99, Explicit: 0, Skipped: 0
  Start time: 2017-01-14 21:41:17Z
    End time: 2017-01-14 21:57:58Z
    Duration: 1000.828 seconds

Very nice @vasily-kirichenko.

@vasily-kirichenko I gather that the space optimization of MaybeLazy vs System.Lazy are following:

F# compiler turns a 2 case DU into a classes with no field in the base class (relies on typeof to identify the Tag)
System.Lazy has an extra lock object (thread safety) + a flag (loaded) overhead

Is that it?
Is it worth it to make MaybeLazy a struct DU?
I think it is worth to mention that kind of information around the type defintion.

@smoothdeveloper yes, you are right about MaybeLazy, however there are only about 10k such objects on FCS solution having TypeChecker.fs open :) So making it struct does not worth it.
The cool thing about making Ident a struct is that there were a lot of such objects (~1M in the above scenario) and all of them lived in Gen 2, so the GC had to check them all in memory pressure case.

Look at ~3.7M objects, which are nodes of F# Maps :( Is anybody know if making them Dictionary (or ImmutableDictionary) would reduce number of objects in the heap? As I remembers, dictionaries contains a lot of "buckets".

@vasily-kirichenko do you have a comparison of memory usage before the simplify name analyser was implemented in your previous PR? I'm slightly concerned that this analyser will cause even more GC pauses/memory pressure as you mentioned in #2202. I hope you can prove otherwise because this analyser looks great 👍

@saul this analyser is slow on large files. It takes it about 800 ms on a 1k lines file to finish and about 1.5 minutes on TypeChecker.fs. However, it's asynchronous and nicely cancellable, so it should not freeze UI at all.

I'm not concerned about how long it will take, but how much memory it will allocate. As we're already doing all of our work in process on a 32-bit process, is this going to increase our already high memory pressure? I'm worried that there will be more GC pauses (UI thread lockups).

@saul our problem is that FCS keeps huge caches, which naturally sit in gen 2. What this feature does (as all the other ones, btw) is just querying and searching in those caches. It do have its own cache for found diagnostics, but it's really tiny.

@vasily-kirichenko Just to say that I'm still concerned that we're using projectCacheSize=200.  (I know you said here that you're experience was that reducing this did not help w.r.t. memory usage.)
Or to put it another way I'm concerned that FCS is not holding enough of its cached information weakly.
Like @saul I do fear that each extra feature runs the risk of ramping up the amount of data held strongly by FCS, or simply the churn in a compute-allocate-cache-collect cycle.  We really need to get a grip on the whole question of memory usage by the language service.

@dsyme when memory pressure is here, even tooltips can appear with a very long delay, even though code has not changed at all, i.e.:

We occupy 2.5GB
Hover over a symbol - tooltip appears immediately
Hover over another symbol - high CPU load, very long delay and finally we got our tooltip

I think that's because either generating the second tooltip triggered blocking GC or a weak cache data for current file have become available for GC between the first and second tooltips, so the file was rechecked.

@dsyme when memory pressure is here...

My impression is that we must avoid memory pressure > 2GB at all costs, even if some features simply don't work in reasonable time.  Once you go above 2GB, nothing works anymore until you restart.

In my case (with VS2015 + VFPT), I've seen that things may stall or not disregarding the memory occupied by devenv.exe (looking at Working Set (Memory) in task manager).
I've seen process with 2.7gb still doing fine and process with 2gb being unworkable, and I can't really identify why.

My impression is that we must avoid memory pressure > 2GB at all costs, even if some features simply don't work in reasonable time.

It's not about features, it's about FCS caches. Features themselves do not add anything to gen 2.
I was thinking about an external process. Maybe it's better to move some FCS internal caches there, not FCS itself, keeping the current VS <-> FCS API untouched.

It's not about features, it's about FCS caches. Features themselves do not add anything to gen 2.

But features do cause information to be required more often. This adds requests to FCS (potentially lengthening the request queue, especially if cancellation is not performed), and may add to compute/allocate/collect churn.  The use of a feature can trigger a Gen2 collection in the worst case, while turning off a feature can only improve things.
I'm just concerned we're going to see Gen2 collections or blocking UI pauses triggered by features we can't turn off.  When using VFPT I regularly turned off all but a couple of the most important features.

Just as an FYI - a 32-bit process on a 64-bit OS will get a full 4GB of address space, so yes, it's possible to use 4GB of Virtual Memory.  Note that things like task manager don't actually report the total VM though - they leave out some categories of memory.  To get an accurate picture of VM, use something like vmmap.
For people running 32-bit processes on 32-bit machines, they get either 2 or 3 GB of VM, depending on OS Version and whether the app declares itself large address aware (VS does).  The OS always keeps at least 1GB for kernel address space though.
Note however that even with 4GB of address space, you can run into issues with fragmentation on large allocations - the OS (or the CLR) may not have enough contiguous address space to perform an allocation.
Note also that everything I said above was about virtual memory.  The amount of physical memory the machine has has no bearing on it - if the machine doesn't have enough physical memory for the virtual memory, some will be swapped to disk.  If the machine has more physical memory, it will not be accessible to the process (except through transparent OS optimizations like file-system caching).  Address space/VM really come down to pointer-size.  A 32-bit process uses 32-bit pointers, which means they can only address 4GB of memory, no matter how much is physically present.

We'd better merge it to RTM (because it speeds up the analyzer at about 80 times) or disable it there.

@dotnet-bot test this please

@vasily-kirichenko can you resolve the conflicts pls.
Kevin

@KevinRansom Could you please merge it? The analyzer is slow and it's still disabled it in this PR (as in master) until we have a proper settings dialog to turn it on and off. Keep it up to date with master is cumbersome.

@vasily-kirichenko Lots of good changes here - I'm only just reviewing them - I hadn't realized there were core changes in the compiler.   I added some comments about the changes to the core compiler code
@KevinRansom Probably best you make sure I review changes to the core compiler code.  Just for a double check.

The cool thing about making Ident a struct is that there were a lot of such
objects (~1M in the above scenario) and all of them lived in Gen 2, so the GC had to check
them all in memory pressure case.

@vasily-kirichenko Yes, you're likely correct that Ident should be made a struct.  However it can be hard to tell for objects that contain range - which is already a struct - and quite a large one for 32-bit systems.  Also in many cases Ident objects can I presume be shared.  Making them structs can potentially lose that sharing.
BTW I've found it quite hard to measure the pros/cons of these perf choices  - the compiler perf scripts aren't yet accurate enough, though the memory tests are fairly accurate.  Focusing on reducing memory by using structs can sometimes lead to reduced throughput through lots of data copying.


Revert "[Backport 2.x] add query group stats constructs"

Reverts opensearch-project/OpenSearch#15473

The pull request (https://github.com/opensearch-project/OpenSearch/pull/15473) was merged while breakinh API compatibility checks and as such - blocks all further pull requests from being merged.

@reta I don't think we need to revert these changes. I had commented on this issue let me know if there are any concerns

Closing this PR in favor of actual fix: https://github.com/opensearch-project/OpenSearch/pull/15486


Preserve inherited types order and minor internal templates improvements

          1 Warning

:warning:
Big PR

  Generated by :no_entry_sign: danger

@krzysztofzablocki I've also added an improvement for handling void throwing methods in protocols


[List] Remove Paper

[x] PR has tests / docs demo, and is linted.
[x] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

Paper is redundant, as, like Menu, List is used wrapped in other components  such as LeftNav, which may already use Paper.

This is good :+1: But it's a breaking change we should document it and update the examples too. also, zDepth should error as it's functionality is not deprecated but rather removed

All good points - I think I rushed this! :smile:

@mbrookes @alitaheri I know conceptually this sounds weird/crazy, but if we made this change, we could probably just deprecate List altogether, since List would essentially be an alias/wrapping of a standard <div />.
Users could nest ListItem components in a standard <div /> or a <Paper /> element themselves without List.
Is that too weird?
I guess another option to make it less weird is we could get rid of the selectable-enhance HOC and implement the selectable functionality in the List component. So if you selectable behavior, use List, if not, just use <Paper /> and <ListItem />. Are there any other use cases for selectable-enhance other than List?

we could probably just deprecate List altogether

I thought the same thing when I first looked at this - about the only thing that is some padding, which varies depending on whether there's a Subheader, however it does seem a bit unnatural not to have a List component to wrap ListItem.

Are there any other use cases for selectable-enhance other than List?

It looks fairly tightly coupled to List, although I'm curious as it's been named and located as if it's a standalone component.
There was a request on gitter today for a multi-select menu, but I'm not sure how useful this would be there.
I do intend to revisit this PR, but last time I tried to update it, I was plagued by the inline-style-prefixer issue!

I do intend to revisit this PR, but last time I tried to update it, I was plagued by the inline-style-prefixer issue!

I hear you! :smile:

It looks fairly tightly coupled to List, although I'm curious as it's been named and located as if it's a standalone component.

I've thought about it some more, I think my vote is let's expand List to include some the selection functionality. I think it makes sense. Menu and List are related to each other, but Menu currently manages it's own selection state and I don't think it will ever make sense use selectable-enhance with it.
Also, having a parent List component may help one day if we want to support something like Leave Behinds.
I think if we get the API right, the Menu components could be dramatically simplified because right now there is a lot of duplicating functionality/API.

zDepth should error as it's functionality is not deprecated but rather removed

@alitaheri That's a fair point. I wanted to show some kind of meaningful message, so rather than just remove the prop I've used warning directly.
Let me know if you'd suggest something different. I think a warning is reasonable, as nothing will break if the prop is provided, it just won't generate a shadow if one was expected.
Most devs will be using List inside LeftNav or Popover anyway.
@newoga I think your suggestions deserve their own PR, perhaps combined with deprecating valueLink from the HOC.

I think a warning is reasonable, as nothing will break if the prop is provided, it just won't generate a shadow if one was expected.

Good point :+1: And the warning explicitly expresses that it's removed not deprecated :+1: :+1:

The only downside is the prop still appears in the docs, but I added a notice in the description.
Is this good for now? If so, I'll add the warning to Menu.

Well why not @ignore it?

Doh!

This looks good :sweat_smile:

@mbrookes Mind squashing it?

I really like the direction this PR is taking :+1:. Let's split the concern of each component.

Thanks a lot @mbrookes :+1: :+1:

Ops, I forgot to push the merge button.


ReferenceError: WebSocket is not defined

I'm getting ReferenceError: WebSocket is not defined when calling const relay = relayInit('wss://nostr-pub.wellorder.net') on 1.0.0-rc1

On Node.js?

See https://github.com/fiatjaf/nostr-tools#interacting-with-a-relay. On Node.js you must install and import websocket-polyfill first.

I am using Nuxt 3 and getting:
[nuxt] [request error] [unhandled] [500] WebSocket is not defined
Although I have installed and then imported websocket-polyfill  in my ~/server/api/test.ts
Seems like I have to specifically declare WebSocket but could not figure out how.


Specify maximum supported platform version for v1.5.0

Describe the bug
Plugin v1.5.0 currently has open ended maximum supported version. Due to various changes in IntellIJ 2019.3, current version can't be supported beyond 2019.2.* and same should be made explicit to avoid plugin accidentally getting updated on supported platform.
See -
<idea-version since-build="191"/> <!-- no until-build -->

Hello, thank you for this issue.
Unfortunately we won't be doing this because I would need to release a new version of the plugin for each version of Intellij, meaning I would need to test every version myself. I don't have that kind of time. By leaving the version open, the plugin gets crowd tested. It is also on par with what I've seen on other plugin projects.
Concerning the annotation, I'm pretty sure we can just add it and backport the changes in all branches and versions.

... By leaving the version open, the plugin gets crowd tested.

Understood.

Concerning the annotation, I'm pretty sure we can just add it and backport the changes in all branches and versions.

If you are referring to annotation changes for @NonInjectable then these can't be backported as the annotation is only available for platform v2019.3+.

If you are referring to annotation changes for @NonInjectable then these can't be backported as the annotation is only available for platform v2019.3+.

This is awful


created a new Dictionary struct instead of the BTreeMap and added support for Iterators

I also began using binary search on a Vector instead of the BTreeMap for decoding
On my machine the decoding is about twice a fast and encoding 5 times
The benchmark should use a BTreeMap cache of loaded files so it is much quicker

Thanks for making these changes! Everything looks good, I learned some things from reviewing your code :)


Little bit cleaner code

@tnix100 ^

Alright, I will check it

Hm, I will need to locally build, so I'll need to get npm on my laptop

im gonna unrequest changes on the main pull until we are really done

btw what i said was: wait, that review wouldnt actually work, because i could do "hi: hi" on discord and it would render as "hi"
example sentence: "for example: print("hello") would work right?" would turn into "for example"

Oh I see your point


Management command

I added a management command for cleaning expired files via CLI. #42

Also this PR contributes towards #43, not #42

Also this PR contributes towards #43, not #42

Sorry for the mistake, Now it's fixed.


Use hiding list to reduce lag from many annotations

Instead of keeping every annotation element in the list at once (causing significant lag when recalculating layout), use a special list that applies display:none to offscreen elements so their dimensions can be ignored in layout.
This fixes https://github.com/seung-lab/neuroglancer/issues/364.
Also, this will conflict with https://github.com/seung-lab/neuroglancer/pull/360, so when that is integrated some changes will be need to made (probably flattening the DOM from a tree to a flat list).

Names have been updated to be more descriptive overall. I also changed some instances of "height" to "Y" to make the distinction between "Y position in the list" and "height of list element" more clear.


fix: megacloud extractor grabbing correct key

Fixed the megacloud extractor to grab the correct key/secret.
Credits to itzzzme with the solution in issue #30.

Thank you so much @WBRK-dev ❤


MUIC-638: [Android] Update Glia Android SDK dependency to 0.23.0

Jira issue:
https://glia.atlassian.net/browse/MUIC-638
Additional info:
Updated dependency of core sdk to 0.23.0
Introduced additional Authorization method for Glia Core SDK
Screenshots:

Perhaps you missed it, so just wanted to clarify, did you update TestingApp UI with these suggestions?

A few questions about TestingApp UI:

Since SiteId it is not part of the authorization method, please move out SiteId field out from the authorization chooser screen to the main settings view as was before.
I see the label "needs restart", could you please clarify why the restart is needed? The Core SDK could change the authorization method in runtime, but why restart is required in TestingApp?

I see the label "needs restart", could you please clarify why the restart is needed? The Core SDK could change the authorization method in runtime, but why restart is required in TestingApp?
GliaWidgets are initialized in this current implementation on application start
see Application.class this is how it worked before for changing apptoken btw. it wasnt marked tho.

Widgets can be initialized during runtime aswell for example in some sort of activity - so this is note for testing mostly

Perhaps you missed it, so just wanted to clarify, did you update TestingApp UI with these suggestions?
Yup, didn't see the comment - was checking files requests. Sorry :)

In case siteId needs to be returned to authentication for clarity just revert last commit

Squashed


Remove repository check-out and tool install steps

Expect the code to already be checked out and ready to work with as with our other actions.

This is currently included in the boilerplate as an un-pinned dependency so we'll need to work out a plan to make a breaking change which doesn't immediately break all external providers.
Example:
https://github.com/prodvana/pulumi-prodvana/blob/ec3b44a9c205f14d5f9c3ee127b33f617cf895b8/deployment-templates/upgrade-provider.yml#L16


Not issue:    training code

https://github.com/3DTopia/OpenLRM/tree/main/openlrm/runners/train
objvavese render的代码也有
尽管有差别，比如那个Local Patch之类的，但可以从这个相似的training code上修改。

This link https://github.com/3DTopia/OpenLRM/tree/main/openlrm/runners/train has lrm model class attached. Could you please guid me to re-train TripoSR Model with custom datasets.

@yuedajiong is there any source code to re-train TripoSR Model with own dataset.

I am writing.
early CoP code here:  https://github.com/VAST-AI-Research/TripoSR/issues/15#issuecomment-2008596810

@Rameshkumardas
#phase-1:  reproduce TripoSR
1.   data prepare  (I have not powerful GPU, so just small dataset, you can try this big dataset iff you have GB200.)
1.1  download objavese and more
1.2  render few views, pick better object  (too many garbage)
1.3  render enough views: camera poses,  lighting,  data augment, ...
.....
2.  implement training code  (I am writing, will share ...)
......
3.  training execution
......
#phase-2:  surpass TripoSR
1.  optimize triplane and later encoder MLP, likes 'MultiPlaneNeRF: Neural Radiance Field with Non-Trainable Representation'
2.  implement 'equivariant' triplane for input, then we can directly train on 2D images, lots of.

Thanks @yuedajiong.
I have one more questing regarding ===>>> NpzFile './data/nerf/tiny_nerf_data.npz' with keys: images, poses, focal
How to create image into NpzFile './data/nerf/tiny_nerf_data.npz'  with keys: images, poses, focal
I mean how to create nerf_data.npz from my own images.
data = np.load('./data/nerf/tiny_nerf_data.npz')  #TODO  render and load objavase for training
images, poses, focal = data["images"],data["poses"], data["focal"]
@yuedajiong Thanks.

You can render 3D objects  dataset, eg, objaverse, ABO, Omini, ....
you can get rendered images and related camera poses.
pls try to study how to render a .obj file.
you can find too many samples in github.

@Rameshkumardas
--- for Gauss Splat
camera code, like this:
camera.py.txt
dataset, like this:
dataset.py.txt
--- for TripoPlane
triplane_dataset.py.txt
I mentain the camera_pose in filename, like this: image__distance_2_0__elevation_000__azimuth_000.png
you can modify base on your requirements.


OCPBUGS-1775: Testing jira-lifecycle-plugin

/jira refresh

/jira refresh

/hold
This is just a test.  Ignore

/jira cherry-pick OCPBUGS-1775

/jira cherry-pick OCPBUGS-1775

/jira refresh

/jira cherry-pick OCPBUGS-1775

/jira cherrypick OCPBUGS-1775

This is just a return
This is a shift-return
testing...testing...1...2...3...

/close


Cursor is not visible when testcafe run with proxyless

What is your Scenario?
cursor is not visible when proxyless mode is running. Because of this the hover function in nested dropdown isn't working.
What is the Current behavior?
cursor not visible
What is the Expected behavior?
cursor to be visible
What is your public website URL? (or attach your complete example)
Not relevant--
What is your TestCafe test code?
test('Check', async t => {
'use strict';
await t
.maximizeWindow()
.navigateTo('https://mdbootstrap.com/docs/standard/extended/dropdown-multilevel/')
.click('#dropdownMenuButton')
.hover(new Selector('main .dropdown-item').nth(2))
.click(new Selector('main .dropdown-item').nth(3));
;
});
Your complete configuration file
Not relevant--
Your complete test report
Not relevant--
Screenshots

Steps to Reproduce
1.Run the test I just added or on a nested dropdown
TestCafe version
2.4.0
Node.js version
16.15.1
Command-line arguments
testcafe -- -t 'Check' --experimental-proxyless
Browser name(s) and version(s)
chrome  111.0.5563.65
Platform(s) and version(s)
Windows 10
Other
No response

You are right. The Cursor is invisible right now. It's an implementation feature of the --experimental-proxyless mode. We are aware of this.
Regarding the issue, I did not manage to reproduce the described behavior. The test passes. I do not think that the issue can be related to the missing pointer because the arrow pointer is made for convenience. It is not involved in the event emulation process.


Add cache to findRecords

Hash update and call to clear cache before execution.
Pull requests into cqm-execution require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[x] This pull request describes why these changes were made.
[x] Internal ticket for this PR: https://jira.mitre.org/browse/BONNIE-2068 https://jira.mitre.org/browse/BONNIE-2119
[x] Internal ticket links to this PR
[x] Code diff has been done and been reviewed
[x] Tests are included and test edge cases
[x] Tests have been run locally and pass

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Codecov Report

Merging #68 into 2019-standards-update will increase coverage by 0.01%.
The diff coverage is 100%.

@@                    Coverage Diff                    @@
##           2019-standards-update      #68      +/-   ##
=========================================================
+ Coverage                  87.09%   87.11%   +0.01%
=========================================================
  Files                          6        6
  Lines                        705      706       +1
  Branches                     212      212
=========================================================
+ Hits                         614      615       +1
  Misses                        91       91

Impacted Files
Coverage Δ

lib/models/calculator.js
94.56% <100%> (+0.05%)
:arrow_up:

Continue to review full report at Codecov.

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


Manual packet fragmentation

This PR implements the following logic:

Collect all mappings, insertions, removals and despawns into so-called init message and send it over reliable channel. This message contains changes only for this replicon tick.
Collect all component changes into so-called update message and send it over unreliable channel. This message contains changes since the last acknowledged tick for each entity. When insertion detected, then last acknowledged tick becomes this tick (since reliable message will reach the destination). Since this message contains only component changes, all data can be naturally splitted between messages by entities up to packet size.

This not only helps us implement packet fragmentation, but also improves other things:

We serialize most of the world only once, only updates get re-serialized if the client did not acknowledge them.
We no longer need despawn and removal trackers since we need them only since the last run. But it also requires 0.12.1: https://github.com/bevyengine/bevy/pull/10077.
We can avoid sending empty messages with tick when event (or now also components update!) occurs because we can just reference older init tick.
Client mappings no longer need to reference a tick.

I also fixed tick increment when no server is present. Needed to fix tests.
I also need to drop tick's entities that wasn't acknowledged for too long. I will probably do it in a separate PR.
Benchmark results:
entities send           time:   [68.015 µs 68.085 µs 68.167 µs]
                        change: [-35.330% -35.155% -34.971%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 2 outliers among 20 measurements (10.00%)
  2 (10.00%) high mild

entities receive        time:   [144.37 µs 144.86 µs 145.48 µs]
                        change: [+10.786% +11.708% +12.525%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 1 outliers among 20 measurements (5.00%)
  1 (5.00%) high mild

entities update send    time:   [64.368 µs 64.520 µs 64.728 µs]
                        change: [+2.6338% +4.2286% +5.7505%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 2 outliers among 20 measurements (10.00%)
  1 (5.00%) high mild
  1 (5.00%) high severe

entities update receive time:   [59.716 µs 60.222 µs 60.894 µs]
                        change: [+135.46% +140.30% +144.64%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 1 outliers among 20 measurements (5.00%)
  1 (5.00%) high mild

While it shows that performance has been regressed for updates, I think that in real scenarios this implementation will outperform the old solution because it less sensitive to packet loss and re-serializes less things.

But why Unordered? We need to apply init messages in their order. In Renet it's based on UDP, so it basically just buffer out of order messages for us.


X/GUI support

It would probably be nice to have --allow-x11 command-line flag and setting which could work without any additional setup. While it could work now (see #126) there are couple of issues:

A volume must be defined both in settings and in container
Graphic drivers might need to be installed

While (1) is just inconvenience, (2) comes seriouly against the vagga's philosophy of "configure once, run everywhere".
(1) can be fixed easily by making a shortcut which adds the volume
(2) needs more serious work:
a. Detecting video driver (where detection method depends on host system, but installation target depends on guest system)
b. Allowing to customize it somehow
While (a) is a great convenience, it will never work for all cases. On the contrary (b) can work for everyone, but require a little bit preparation work (but the work may be reusable across the project).
Probably it can be done with something like:
  setup:
  - !Ubuntu trusty
  - !Install [firefox]
  - !CustomInstall video-driver-ubuntu-trusty

And the settings file which has something along the lines of:
custom-installs:
  video-driver-ubuntu-trusty:
  - !Install [xserver-xorg-video-intel]

Related issues #126, #131

Hi, under Ubuntu 15.04 (XUbuntu and lightdm) there is an issue with firefox and chromium:
no protocol specified
cannot open display: :0.0

It requires ~/.Xauthority to be accessible in container.
However, this only solved the issue for firefox, chromium still fails to start

@popravich While I don't have the solution, I have a suggestion.
This is not a vagga specific issue. When I know that it is a container issue(that you run the command/software/... in the container), I usually search the same issue related to docker since docker has been in the wild for a long time and you can find more info about docker related issues.
Here, I searched on Google for "docker display 0.0" and this is my first result: http://stackoverflow.com/questions/28392949/running-chromium-inside-docker-gtk-cannot-open-display-0

Well, we have few working examples already. I think this issue doesn't need any more attention.


Fix for GridMaterial line intersections

Fixes the issue seen in the below playground where the points of intersection between the grid lines are too bright, by using the max axis contribution instead of the sum of the axes contributions.
Playground: https://playground.babylonjs.com/#2KKVBH#113
Forum: https://forum.babylonjs.com/t/fix-for-gridmaterial-line-intersections/25644

conversation happened in the forum, the PR will be updated to prevent the breaking change.


Optional values and drop down fields

Describe the bug
When the optional field is a drop down menu, the first value is taken, even though this is not intended.
To Reproduce
Steps to reproduce the behavior:

Go to https://matwerk.datamanager.kit.edu/repo-management.html
Click on Create Data Resource
Enter Title of the resource
while saving the Title will be saved with the type ALTERNATIVE_TITLE
All the current resources now, have ALTERNATIVE_TITLEs without having any other main TITLEs

Expected behavior
Either the type should not be saved so. Or there should be an entry which says Main Title or something similar.
Desktop (please complete the following information):

OS: MacOS
Browser Safari
Version 16.2

Additional context
Add any other context about the problem here.

One workaround is to include a blank item as the first item of the dropdown list

Do you have an example for such an optional field? All cases I can imaging for the repo-management UI involve elements from a controlled list, which do not allow empty values, i.e., taking a contributor, which is per se optional, but as soon as you add a contributor, its contribution type becomes mandatory and as the UI cannot "guess" some proper contribution type, the first entry is selected as default.

Yes, first and foremost Title Type. It is optional. But the default is ALTERNATIVE_TiTLE. How can we save something of the type main title and not ALTERNATIVE_TITLE (or rather not enter the Title Type at all)?

There is no value "main title" in the DataCite Standard (see https://schema.datacite.org/meta/kernel-4.4/include/datacite-titleType-v4.xsd) But you are right, according to the standard, the title type is optional, which is currently not supported in frontend-collection and should be supported in the next version.


User selected channel is selected as notification channel

The user-selected channel is selected as the notification channel when the user's preferred channel is in the self-registration request even though channel resolving is not enabled.

Fixed with https://github.com/wso2-extensions/identity-governance/pull/324


[DO NOT MERGE] Enterprise Template TelemetryClient/AppInsights conversation analytics capabilities

Description

Updated ET to work with new 4.2 SDK which will support more App Insights telemetry out-of-the-box.
OnboardingDialog is a sample of how the WaterfallDialog telemetry works by passing ITelemetryClient from parent->child dialog.
Refactored Middleware properties to all use camelCasing standard.

Related Issue

#134
#354
https://github.com/daveta/analytics/blob/master/va_reports.md
Testing Steps

Build VSIX project and get .vsix from /bin/debug folder. Install the new template and have a working bot.
Checklist

[X] I have commented my code, particularly in hard-to-understand areas
[X] I have added or updated the appropriate unit tests
[X] I have updated related documentation

If this contains changes that needs to be replicated between the Enterprise Template <-> Virtual Assistant

[X] A duplicate issue is filed to track future work. #135

Nice work Ryan!
FYI: (low priority) For your VSIX build, @cleemullins (and I think @darrenj) cooked up some steps where you don't have to check in the zip file.  Check out the bot builder vsix csproj..  They add a PreBuildEvent..


NSwagStudio MSI link broken?

On this page https://github.com/RicoSuter/NSwag/wiki/NSwagStudio
The link for the MSI installer of NSwagStudio
brings you here: https://github.com/RicoSuter/NSwag/releases
and there is no MSI file for NSwag v13.17.0
I do see it for v13.16.1

I've updated the release with the missing artifacts, please try now.


Anticheat for second door doesn't seem to work correctly

I can still go back the way I came with the second door, forming only half a heart.

Huh, didn't even think people'd be looking at this repo. Thanks, it's been fixed! The full minigame is out now - http://ncase.me/door/ - thanks again!


I found very diffucult to implement. Finally I Dropped. You have any examples

Please give me some links, I don't understand the idea behind this package

Dude, go to https://github.com/tuupola/slim-jwt-auth scroll down and you can see a full sample usage of this package, nothing special.

If you are not familiarized with JWT I suggest you the following links:
https://auth0.com/blog/2014/01/27/ten-things-you-should-know-about-tokens-and-cookies/
http://www.jamiekurtz.com/2014/11/25/5-keys-to-web-app-token-authentication/

There is quite much information of what JWT is available. Also check Learn how to use JSON Web Token project. Although the example code is for Node it contains much good basic information on JWT.

I will try a shorten explanation:

The user sends to your api user/password credentials in a specific route to authenticate (http://mydomain.com/auth/try)
In this authentication route, you will do validations with user data like user/password length, database comparsion, etc.
If this credentials are true, you generates a JWT and give it back to the user, storing in your application local storage or session, it's your choice where you kept the data.
For every request the user does, you need to send the generated token in the header, as the following: Authorization Bearer {GENERATED_TOKEN}

WHERE:
Authorization: is the key in the header
Bearer {GENERATED_TOKEN}: is the value of Authorization key in the header
An example looks like this:
Authorization Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJSb25hbGRvIEpyIiwiaWF0IjoxNDQ0NDAwMjQyLCJleHAiOjE0NDUwMDUwNDIsInVpZCI6InJvbmFsZG9Ac3lzdGVtYXIuY29tLmJyIn0.ZuAR7Itp-kT7XCwuRi2TSiLA9bvWpP6WU4Wkwaj5cdc
Everytime any request is sent, JWT middleware validates if this token is OK, if IT IS, the middleware let the route pass, IF NOT, middleware rejects the request.
Take care with token expiration, sometimes credentials are ok, but expiration has gone.

Example code of what @ronaldo-systemar explained abobe.

I understand, If you provide a example project, Then programmers with minimum knowledge like me can cross-check the sample code.
What I thought initially about this package

Its a complete package for generating and verify tokens
I seen ['read','write','delete'] in the code, so I thought RBAC also available.
And I expected options comes under one middleware.

My Questions: you might add it  to faqs documentation if its meaningful

I'm using for API security. Why Basic HTTP Authentication.
If you're not generating token, What is reason behind login
Sample code is always underlying layer independent. Actual code is depending on the Token generation algorithm. OS variations(https://github.com/tuupola/slim-jwt-auth/issues/9)

My Expectations:

Sample Demo Code Repo https://github.com/manjeshpv/slim-jwt-auth-demo

This are issues I got, and way I followed

tuupola/slim-jwt-auth 3.x Documentation not directly available.(I switched branch and found docs)

>  composer require slim/slim 3.x-dev
>  tuupola/slim-jwt-auth 2.0.0

The I created file https://github.com/manjeshpv/slim-jwt-auth-demo/commit/bf1f0b03d38c52e7aaec999c6d10cd30a3d8c2e5
Fatal error: Class 'Slim\Slim' not found in slim-jwt-auth-demo\index.php on line 19
Because Slim 3.x-dev come with Slim\App
Fatal error: Class 'Slim\Middleware\HttpBasicAuthentication' not found in D:\xampp\htdocs\slim-jwt-auth-demo\index.php on line 32
Here Installed composer require tuupola/slim-basic-auth
D:\xampp\htdocs\slim-jwt-auth-demo>composer require tuupola/slim-basic-auth
Using version dev-master for tuupola/slim-basic-auth
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Can only install one of: slim/slim[2.x-dev, 3.x-dev].
    - Can only install one of: slim/slim[3.x-dev, 2.x-dev].
    - Can only install one of: slim/slim[2.x-dev, 3.x-dev].
    - tuupola/slim-basic-auth dev-master requires slim/slim ~2.3 -> satisfiable by slim/slim[2.x-dev].
    - Installation request for tuupola/slim-basic-auth dev-master -> satisfiable by tuupola/slim-basic-auth[dev-master].
    - Installation request for slim/slim 3.x-dev -> satisfiable by slim/slim[3.x-dev].

Installation failed, reverting ./composer.json to its original content.

The I got to know all package are latest dev branchs
>composer require tuupola/slim-basic-auth 2.x-dev
Now
GET http://localhost/slim-jwt-auth-demo/index.php/secured
{"message":"token success","access_token":"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiIsImp0aSI6IjRmMWcyM2ExMmFhIn0.eyJpc3MiOiJodHRwOlwvXC9tYW5qZXNocHYuY29tIiwiYXVkIjoibW9iaWxlQXBwIiwianRpIjoiNGYxZzIzYTEyYWEiLCJpYXQiOjE0NDU2NjcxMDAsIm5iZiI6MTQ0NTY2NzE2MCwiZXhwIjoxNDQ1NjcwNzAwLCJ1c2VyX2lkIjoxLCJzY29wZSI6WyJyZWFkIiwid3JpdGUiLCJkZWxldGUiXX0.i1oLa8YUxhf5TVFcArN3nXn-AfHIvP6V2dpFKe7ggpM"}

GET: http://localhost/slim-jwt-auth-demo/index.php/secured
Method Not Allowed
POST: http://localhost/slim-jwt-auth-demo/index.php/secured
Authentication: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiIsImp0aSI6IjRmMWcyM2ExMmFhIn0.eyJpc3MiOiJodHRwOlwvXC9tYW5qZXNocHYuY29tIiwiYXVkIjoibW9iaWxlQXBwIiwianRpIjoiNGYxZzIzYTEyYWEiLCJpYXQiOjE0NDU2NjcxODUsIm5iZiI6MTQ0NTY2NzI0NSwiZXhwIjoxNDQ1NjcwNzg1LCJ1c2VyX2lkIjoxLCJzY29wZSI6WyJyZWFkIiwid3JpdGUiLCJkZWxldGUiXX0.OkaQwFkuAA3_hxq_T6RfiR2EyzVuhOb-E4p1fxYBJ94

{"message":" success","data":"Secured Content"}

Now here

With or without token route is working. no http authentication prompt
How can I access token verified status in code , leads to error

$response = array('jwt'=>$app->jwt);
```php
$app->add(new HttpBasicAuthentication([
    //"path" => "/token", // If  I comment this line auth works
    "users" => [
        "user" => "password"
    ]
]));

https://github.com/manjeshpv/slim-jwt-auth-demo
Can you please fork the aboe repo and complete the implementation for me. Thanks in Advance

My advice is programmers with minimum knowledge should not use JWT authentication. It is really easy to shoot yourself in the foot.

What I thought initially about this package. Its a complete package for generating and verify tokens
I seen ['read','write','delete'] in the code, so I thought RBAC also available. And I expected options
comes under one middleware.

Second column in the README says:

It does not implement OAuth 2.0 authorization server nor does it provide ways to generate, issue or
store authentication tokens. It only parses and authenticates a token when passed via header or
cookie. This is useful, for example, when you want to use JSON Web Tokens as API keys.

In any case Github issues in not place for general programming help. Stackoverflow is better place for such questions. Check especially JWT, Slim and Composer tags.

Thank you. But I have to do. Sorry for making u trouble. because of my lack of knowledge.

@manjeshpv to create your endpoint token you must use
use Firebase\JWT\JWT;

$time = time();
$key = 'your_secret_key_here';
$token = [
    "iss" => 'example',
    "iat" => $time,
    "exp" => ($time + 604800),
    "scope" => ["read", "write", "delete"]
    ];

$jwt = JWT::encode($token, $key);

then everything magically work

I would replace the word "must" with "can". It is not mandatory to use Firebase\JWT. You can use anything which produces valid JWT.

You are right , the recommendation is to be used with tools that are already.


Add option to show pull requests again

This change adds a long-form flag --show-pulls to hub issue that directs hub to include pull requests in the issue listing.  The default value is false; the default behavior does not change.
Temporary fix until a better abstraction for pull requests can be designed in #1303.
Related: vermiculus/magithub#44

Ooops. I guess I should have “requested changes” instead of approving this PR 😅 But it's on the right track! 👍

@mislav There you go! 😄

Looks good!

I'm interested in using this feature to list which of my local branches have an open pull request on github.
In order to do that, I hoped I could get the name of the branch the pull request is based on (e.g. as one of the format placeholders). Is that supported?

@withrocks This would be an excellent feature, but it isn't supported because the API endpoint queried here doesn't contain extended data about PRs, such as their head and base branches. https://developer.github.com/v3/issues/#list-issues-for-a-repository
We would probably need to create a hub pr list subcommand to query the Pull Requests endpoint specifically. https://developer.github.com/v3/pulls/#list-pull-requests


Question: How to map dynamic properties?

I want to build a client for the partnerize brands api: (campaigns endpoint here)
https://api-docs.partnerize.com/brand/#tag/Campaigns
The response of the "campaign_languages" can in real be not existing, emtpy string, null or an object of key values like:
                "campaign_languages": {
                    "en_us": {
                        "destination_url": "https:\/\/www.foo.com
                    }
                }

My phpdoc looks like this:
    /** @var null|string|string[] */
    public $campaign_languages;

My Problem is that the key "en_us" and "destination_url" are dynamic and can be "de_de" "source_url" or whatever.
Do you have any ideas how to map this into a object structure or dynamic?

Hi,
I used stdClass, which was OK, but if I used a class from stdClass it does not work.
Like:
class Term extends \stdClass
{
}

Should that be working by default?

Closing for now, feel free to reopen if more help is needed. You could also open a discussion as it doesn't seem to be an issue with JsonMapper

I used a stdclass, which worked so for me it is not ideal but managable. It is ok for me to close it.


Allow some things to come before imports block

If you are using Jest, for instance, you might need some lines to appear before your imports block, such as calls to jest.unmock. Some people may even have these lines embedded within the imports block.
We might be able to add some configuration that would allow some things like this to appear before or within the imports block, but I'm not entirely sure what that would look like exactly to provide the flexibility that might be needed for this type of thing.

I think the right way to fix this is to change the logic of where we start the import block.

If there are no previous imports, we start at the top (unless there's comments, use strict etc)
If there is one or more previous imports, start there.

This sounds like a pretty good strategy. I think we also need to look only at import statements that are at the top level, since require can be used within functions. This will be easier once we switch to an AST-based approach.
The drawback is that if there are non-import calls within the import block, things get messy. Here's an example:
jest.unmock('something');
import foo from './foo;

jest.unmock('something-else');
import bar from './bar';

I'm sure there are other examples that can be found. This is also related to #215. This might just be a limitation that we are okay with, but it would be nice to find an elegant solution. Perhaps we should detect this scenario and disable sorting and put new imports after the last import?

Yep, we should only consider top level imports.
Interesting example. What if we keep scanning until we find the last, top-level defined, import and then add our block of imports together with that import?

Shebang for node scripts is another case I've run into recently.
#!/usr/bin/env node

Note that there is some relationship between this issue and  #215 Comments in import blocks.
I'm in agreement that we must limit ourselves to top-level imports. Note that Meteor supports "import" in conditionals and nested contexts. Our tech lead is a TC39 member and is bringing the subject of allowing nested imports back up with the committee this month.
But, I have also considered this top-level import after other code question in the past.
I believe we will encounter the case of projects that want to keep imports near the first code that depends on them. It is a relatively common pattern in other languages. This would cause imports to spread throughout the file. It argues for putting our imports near the first ones we find, not the last ones.
The gotcha I wonder about is in the case of detecting that another named export needs to be added to the list being imported from a package that already has an import further down in the file. Do we move that whole import to the top? Do either of you know whether the ES6 specification tolerates multiple import statements for the same package? Or perhaps it guarantees that no matter where you put an import in the file, its results are present throughout?


[Logging v2] Windows RKE2 	rancher-logging-root-win-agent-fluentbit pod is in Imagepullbackoff

Rancher Server Setup

Rancher version: 2.6-head Commit ID cb9ccde
Installation option (Docker install/Helm Chart): Helm

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE2

Proxy/Cert Details:

Information about the Cluster

Kubernetes version:  v1.24.4
Cluster Type (Local/Downstream): downstream

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): ec2

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions: admin

Describe the bug
Installing rancher-logging:100.1.3+up3.17.7 - rancher-logging-root-win-agent-fluentbit goes into imagepullbackoff and does not recover - errimagepull; This results in the logging-crd unable to create resources.
To Reproduce

import windows rke2 cluster
install rancher-logging

Result
fluentbit pod is in error state;
Expected Result
logging installs; required pods are active; logs flowing to elasticsearch as indicated in cluster-ouput.
Screenshots

Additional context
reproducible 100%

/backport v2.6.10

Fixed issue by changing rancher/fluent-bit image to an existing version. I.e. the version was upgraded without check the image existed.

testing this in 2.7-head commit id 4092002 i was able to delete the rancher-logging-root-win-agent-fluentbit pod and when it restarted, it ran successfully.
`
Fluent Bit v1.8.9
Mon, Oct 10 2022 3:01:58 pm | * Copyright (C) 2019-2021 The Fluent Bit Authors
Mon, Oct 10 2022 3:01:58 pm | * Copyright (C) 2015-2018 Treasure Data
Mon, Oct 10 2022 3:01:58 pm | * Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
Mon, Oct 10 2022 3:01:58 pm | * https://fluentbit.io
Mon, Oct 10 2022 3:01:58 pm |
Mon, Oct 10 2022 3:02:00 pm | [2022/10/10 19:02:00] [ info] [engine] started (pid=7056)
Mon, Oct 10 2022 3:02:00 pm | [2022/10/10 19:02:00] [ info] [storage] version=1.1.5, initializing...
Mon, Oct 10 2022 3:02:00 pm | [2022/10/10 19:02:00] [ info] [storage] in-memory
Mon, Oct 10 2022 3:02:00 pm | [2022/10/10 19:02:00] [ info] [storage] normal synchronization mode, checksum disabled, max_chunks_up=128
Mon, Oct 10 2022 3:02:00 pm | [2022/10/10 19:02:00] [ info] [cmetrics] version=0.2.2
Mon, Oct 10 2022 3:02:00 pm | [2022/10/10 19:02:00] [ info] [filter:kubernetes:kubernetes.0] https=1 host=kubernetes.default.svc.cluster.local port=443
Mon, Oct 10 2022 3:02:01 pm | [2022/10/10 19:02:00] [ info] [filter:kubernetes:kubernetes.0] local POD info OK
Mon, Oct 10 2022 3:02:02 pm | [2022/10/10 19:02:02] [ info] [filter:kubernetes:kubernetes.0] testing connectivity with API server...
Mon, Oct 10 2022 3:02:03 pm | [2022/10/10 19:02:03] [ info] [filter:kubernetes:kubernetes.0] connectivity OK
Mon, Oct 10 2022 3:02:03 pm | [2022/10/10 19:02:03] [ info] [sp] stream processor started`
This is fixed

Confirmed with @eliyamlevy that rancher-logging chart has fixes to use the rancher/fluent-bit: 1.8.9 image for Windows, since the previous image tag 1.9.3 does not exist for windows. https://github.com/rancher/rancher/issues/38851
diff -uNr charts/rancher-logging/100.1.3+up3.17.7/values.yaml to-be-released/rancher-logging/101.0.0+up3.17.7/values.yaml
--- charts/rancher-logging/100.1.3+up3.17.7/values.yaml	2022-11-11 01:03:54.000000000 -0800
+++ to-be-released/rancher-logging/101.0.0+up3.17.7/values.yaml	2022-11-11 00:26:01.000000000 -0800
@@ -154,7 +154,7 @@
   nodeagent_fluentbit:
     os: "windows"
     repository: rancher/fluent-bit
-    tag: 1.9.3
+    tag: 1.8.9
   fluentbit_debug:
     repository: rancher/mirrored-fluent-fluent-bit
     tag: 1.9.3-debug


setChoiceByValue does not remove choice from dropdown

I am creating my choices on a multi select dynamically with setChoices and duplicateItemsAllowed set to false, then immediately selecting the items I want using setChoiceByValue. This works fine, but the choice is not removed from the dropdown. The behavior should be just like if the user selected the choice, the item is selected, and the choice is removed from the choices dropdown.

@ezerr Hey - could you provide a jsfiddle reproducing the problem please?

@jshjohnson Sure thing. In the below link, as soon as you load it, it will have a selected item that was set by setChoiceByValue. But when you click on the select, you can still see that selected item in choices, it was not removed.
https://jsfiddle.net/mhkbs0zt/2/

@ezerr Thanks - it was a regression issue. It's been fixed in 4.1.3 now :)


LSTM code bug

Currently, line 107, 108 is:
  local i2h = nn.Linear(inputSize, 4 * hiddenSize)(x)
  local h2h = nn.Linear(hiddenSize, 4 * hiddenSize)(prevH)

however, line 108 should be changed to
  local h2h = nn.Linear(hiddenSize, 4 * hiddenSize, false)(prevH)
Otherwise, there would be two bias.
Similar problem in 'GRU.lua' line 127.

From @jsenellart-systran:

for reference, we know that there is a redundancy here - but we added it for being equivalent with cudnn.LSTM.

@guillaumekln So it's for compatibility. Why don't directly use cudnn.LSTM? Because of memory consumption?

@helson73 - cudnn.LSTM is coming in the next release, memory consumption is a higher indeed but we have ~20-25% speed improvement (on seq2seq model) - note also that it does not support all of the features we have, for instance the brnn_merge sum.

And we still need the other implementation for CPU training/translation that's why we want them to be equivalent.

@jsenellart-systran Nvidia official website reported that cudnn could speed up RNN up to 600%. In our case, large network size neutralized speed improvement from massive parallelism?

from my experiments, the speed-up on the encoder itself is about x2.5 - but the effect reduces for larger network. Also - we have some layers around (word embedding before and the complete decoder after) - so the global impact is smaller.

@jsenellart-systran Seems like in decoder cudnn cannot be used due to input of each time step depends on previous hidden states. Shortcoming is obvious, cudnn.LSTM is far too away from flexibility, which forces users feed networks with fixed sequence-batch data. But still, improvements are encouraging. Maybe further improvements require work beyond torch community : e.g. improve cudnn itself.

@helson73 yes - indeed, we cannot use cudnn.LSTM for decoding because of input feeding - the support will only be for the encoder.


Automatic login from signup?

Is this possible to do? I'd like for people to get started ASAP and eliminating the email wait sounds like a great solution.

Looking at the code, it isn't possible at the moment.
A quick & dirty solution would to get requestToken to store the token in the request object so your /login route callback can access it and redirect to http://www.example.com?token=TOKEN&uid=UID.

Huh, that's a good hack! The redundant email is annoying though.

Since I created my own passwordless microservice, I can do this with ease.


Durability Check

[19:29] RaidInviteClassic: WARNING: Durability could not be checked for Gobstop-Herod. Player is offline or doesnt have RIC/DBM installed?
Many of my players have DBM and yet I get this message for them. How do we get the addon to work for them? Also is same possible for BigWigs?

Please try out version 2.4.2, should be fixed there, and report back here! I updated the version of the library that does the durability checking, DBM has a new one than the one included in RIC.

the overwolf says im up to date, how do I check the actual version i'm on?

You can type
/ric version
in chat

On 2.4.2. Not sure when this was pushed but I had issues 3 days ago when I originally posted this.

Closing this for now assuming this works now. Otherwise please reopen!

This is still a problem. Several of my guys have DBM installed and yet I still get this:
[19:34] RaidInviteClassic: WARNING: Durability could not be checked for Player-Server. Player is offline, doesnt have RIC/DBM installed, or a different LibDurability version.

I think I found a problem about how the player names were handled. The durability addon seems to sometimes gives us "player", sometimes "player-server" format for the durability info. So my addon was waiting for info for "player-server" but didn't get any (ignored "player"). I made sure that I convert every name to "player-server" everywhere first.
Can you download the code from
https://github.com/f90/RaidInviteClassic/tree/durability_name_fix
and paste it into the RaidInviteClassic folder to test whether the problem still occurs? You can overwrite already existing files. If it all works, I will release it to the public, then you just need to make sure your updater app brings you onto the normal update channel again and discards the "local changes" you made. This way you can beta-test it for the whole community and we can get rid of potential new bugs before everyone has to suffer from them :) Thanks :)

Ok, I'll get it and try it tomorrow.

Sorry, was not able to test this last night. My next big raid is on Wednesday next week.

Good to see that it works again!
People having lower durability than you reported to them is because we measure the average gear durability, they are probably looking at the minimum gear durability. Just a small detail there but still everything works as expected.
Why someone was notified that he was 75% repaired but he was fully repaired I cannot tell you to be honest, never had this issue occur. If you can find a way to reproduce the error let me know... Potentially he has some items in his inventory that are not fully repaired and are counted into the calculation somehow? Just a guess
Just reply if you find out more or have the issue again in the future!


Ensure Mship\Models\Account is touched

In gitlab by @A-Lawrence on Jan 10, 2016, 22:04
Whenever any relations are updated or modified, the account itself should be touched.  This is important as we implement various event listeners as the AccountTouched event will trigger the pushes to other systems.

mship_account_ban
mship_account_email
mship_account_note
mship_account_qualification
mship_account_role
mship_account_security
mship_account_state

Related to #330

In gitlab by @A-Lawrence on Feb 8, 2016, 19:33
mentioned in issue #381

In gitlab by @A-Lawrence on Feb 20, 2016, 03:00
:thumbsup: mship_account_emails

In gitlab by @A-Lawrence on Feb 20, 2016, 03:55
mentioned in commit 9e0b38671ad387c25a4e62197f6d873035ebfbc6


feat(FareSalesAmenityCard): add info and modal (frontend)

Summary of changes
The front-end piece of #1654

Asana Ticket: Amenity Modal | Fare Sales

Some refactoring to account for the changed data structure now including fares
Made a helper method for scaffolding a Stop for our tests.
Added the modal content and amenity card text. Shows either information about fare vending machines or a link to view retail sales locations.
Used styling from .responsive-table as a reference for the CSS (but couldn't copy it outright... too many differences)

This is finally cleaned up and synced with the changes in #1654 for review.

Just added a commit for:
Asana Ticket: Amenity Modal | Fares Content Changes


An exception occurred while receiving the file through the HTTP server. (IDFGH-6420)

Environment

Development Kit:      [none]
Module or chip used:  [ESP32S2]
IDF version (run git describe --tags to find it):
v4.4-dev-3675-g35b20cadce
Build System:         [idf.py]
Compiler version (run xtensa-esp32-elf-gcc --version to find it):
xtensa-esp32-elf-gcc (crosstool-NG esp-2021r2) 8.4.0
Operating System:     [Windows]
(Windows only) environment type: [ESP Command Prompt].
Using an IDE?: [VSCode]
Power Supply:  [USB]

Problem Description
Expected Behavior
The mobile APP connects to the AP of the ESP32S2, accesses the HTTP server of the ESP32S2, sends the file to the ESP32S2 through POST, and saves the file to the TF card when the ESP32S2 receives the file.
Actual Behavior
The post buffer is set to 4096, but during transmission, the number of buffers received is sometimes less than 4096 bytes. If the number of consecutive packets received is less than 4096 bytes, an error of "httpd_txrxx: httpd_sock_err: error in recv: 11" is likely to occur. Then the HTTP server dies and the WiFi AP continues to work.
Steps to reproduce

Open AP mode, set max_connection to 1, set static to IP<IP_ADDRESS>
Start the HTTP server and wait for the user to connect to the AP to send the file to ESP32S2.
In the process of file transfer, the received buffer is less than the configured buffer size occasionally. Once this phenomenon occurs, the HTTP server will die. At this time, WiFi is still working normally. However, this phenomenon is not inevitable every time, and it needs many tests to appear.
Through the test, it is found that the error"Httpd_txrxx: httpd_sock_err: error in recv: 11" is due to file timeout, so the default value of "recv_wait_timeout" in "httpd_config_timeout" has been changed to 100 instead of 5, but this problem persists even after the timeout is increased.

Code to reproduce this issue
https://gist.github.com/CYCHEN97/ef96694d0d777925a67344fb1d3ef4f3

Debug Logs

I (22261) example: bufsize:4096

I (22274) SD_Write: writesize:4096

I (22294) example: bufsize:4096

I (22307) SD_Write: writesize:4096

I (22328) example: bufsize:4096

I (22339) SD_Write: writesize:4096

I (22359) example: bufsize:4096

I (22370) SD_Write: writesize:4096

I (22391) example: bufsize:1696

I (22400) SD_Write: writesize:1696

I (23416) example: bufsize:2880

I (23425) SD_Write: writesize:2880

I (30555) example: bufsize:512

I (30564) SD_Write: writesize:512

I (38575) example: bufsize:512

I (38584) SD_Write: writesize:512

I (38890) example: bufsize:416

I (38899) SD_Write: writesize:416

I (39263) example: bufsize:512

I (39272) SD_Write: writesize:512

I (152517) example: bufsize:1128

I (152526) SD_Write: writesize:1128

I (152821) example: bufsize:688

I (152830) SD_Write: writesize:688

I (158768) example: bufsize:188

I (158777) SD_Write: writesize:188

I (159580) example: bufsize:188

I (159588) SD_Write: writesize:188

I (167374) example: bufsize:188

I (167382) SD_Write: writesize:188

I (182681) example: bufsize:188

I (182690) SD_Write: writesize:188

I (183030) example: bufsize:188

I (183039) SD_Write: writesize:188

I (183438) example: bufsize:124

I (183447) SD_Write: writesize:124

I (183919) example: bufsize:188

I (183927) SD_Write: writesize:188

W (283941) httpd_txrx: httpd_sock_err: error in recv : 11
I (283941) example: HTTPD_SOCK_ERR_TIMEOUT
Other items if possible

[ ] sdkconfig.txt

@CYCHEN97 The errno means the receive timeout. But we don’t know if the phone did not send data or the device server did not receive the data.
print_tcp_data.zip
Could you please help modify the file like the attachment patch. I want to see the TCP data flow. It would be better if you can grab the wifi air packet for comparison.

SaveWindows2021_12_15_12-12-58.TXT

Sorry, I don't know how to grab air pack data for comparison.

@CYCHEN97 The errno means the receive timeout. But we don’t know if the phone did not send data or the device server did not receive the data. print_tcp_data.zip Could you please help modify the file like the attachment patch. I want to see the TCP data flow. It would be better if you can grab the wifi air packet for comparison.

@ESP-YJM This is the TCP data stream log.
SaveWindows2021_12_15_12-12-58.TXT
I'm really sorry that I don't know how to get air pack data for comparison.

@CYCHEN97 For your question

Why received is sometimes less than 4096 bytes.
Although the buffer size is 4096, the recv function reads data from the  LWIP data buffer, and reads as much data as there is. If the data in LWIP data buffer is less than 4096, the recv function will read the actual data and return, will not wait until the data to 4096, which is what you see that data size is less than 4096. Sometimes, poor WIFI environment or peer data sent logic will make TCP retransmission, reduce the data transmission rate，and the LWIP data buffer maybe less than 4096. I think this is a normal issue. If you want to reduce this, you can try change the TCP_WND and your buffer size. In LWIP, TCP_MSS is 1440, and default TCP_WND is 1440 * 4,you can change the buffer size to integer multiples of TCP_MSS, such as 4320, and enlarge the TCP_WND to 2*4320,or only reduce your buffer size to 1440*2.

From your log,  It seems that the log is not over yet, what about the follow-up log, such as the log when an error occurs(httpd_sock_err: error in recv: 11).

@ESP-YJM

Next, esp32s2 has been waiting for receiving information in the file handler. After a minute or two, the mobile app prompts that sending the file failed. Later, all HTTP services of esp32s2 are unavailable and the log shows
"W (1068873) httpd_txrx: httpd_sock_err: error in recv : 11
I (1068873) example: HTTPD_SOCK_ERR_TIMEOUT".

@CYCHEN97 I want to know from the log I (245488) TEST: @@ WiFi Tx TCP - L:40, S:811650527, A:1467562905, SP:80, DP:40326, F:10 to �[0;33mW (1068873) httpd_txrx: httpd_sock_err: error in recv : 11�[0m, whether the mobile app send data to http server? So could you paste the whole log. From the log, i only know we ask the mobile app to send TCP sequence number<PHONE_NUMBER> data. I'm not sure if the phone sent.

@ESP-YJM
The mobile APP debugging tool fails to display Post.

Esp32s2 is still waiting to receive information when canceling resending the file.
SaveWindows2021_12_15_16-18-33.TXT

@CYCHEN97 Thanks for offering the whole log. From the log, it seems the http server still want to receive the data, but now mobile app not send data, maybe like the photo you pasted above, it fails to post. From the TCP protocol itself, i think the mobile app has the problem. Because the http server request the mobile app send TCP sequence number<PHONE_NUMBER> data, and mobile app not send. So http server receive data timeout. Could you please try another tool to upload file to server? Such as postman, or other http client tool.

@ESP-YJM
Now, the file receiving timeout is added to esp32s2 to exit the current file receiving after two times, which solves the problem that the HTTP server has been waiting for the current file information and cannot respond to other requests. However, if there is an exception in receiving a file once, it is easy to see another exception in receiving a file when the app re sends a file. The following is the log information of three consecutive failures in receiving a file.
log_202112201501.TXT

@CYCHEN97 I think this problem is the same with before. The mobile app not send data and receive timeout.

@ESP-YJM
However, in this case, if restart esp32s2, it will generally succeed.

@CYCHEN97 Could you give me the whole log.

@ESP-YJM
I don't think it's our app's problem. I found the HTTP tool of "网络万用表" on the Internet for testing, and there will also be sending exceptions.
log_202112211413.TXT

@CYCHEN97 Yes, i see the receive timeout  in 5s mobile app not send data until after 6s, it send the data that the server want.

And in here, also the receive timeout, but the mobile app maybe close the TCP, and the server re-send data to mobile app, it send RST to close the connection.

Could you please try close the WIFI sleep mode and try to test whether it can reduce the receive timeout.
You can call esp_wifi_set_ps(0) before you call esp_wifi_start.

Redmi Note 10 Pro
Mi Note 3

@ESP-YJM
The latest test found that when sending files using "Mi note 3 mobile phone", it is easy to have file sending exceptions. When sending files using "redmi note 10 Pro mobile phone" / "Huawei yal-al 10 mobile phone", there is no file sending exception. I'd like to know whether this exception of sending file is related to the mobile phone?

@CYCHEN97 It maybe releated to implementation of the WIFI protocol of various mobile phone manufacturers, the size of the TCP window and the sending mechanism.

@ESP-YJM
If it is really due to the mobile phone, if the user's mobile phone is similar to mine, there will be many complaints about poor product performance in the future. Is there any way to make the file transmission more stable and reliable?

@CYCHEN97 You can call esp_wifi_set_ps(0) before you call esp_wifi_start to test.

@CYCHEN97 You can call esp_wifi_set_ps(0) before you call esp_wifi_start to test.
After calling "esp_wifi_set_ps (0)", the file transfer exception still exists.

@ESP-YJM
After calling "esp_wifi_set_ps (0)", the file transfer exception still exists.

@CYCHEN97 I think we need to locate the problem from the TCP protocol layer, whose problem is whose problem is, and this kind of problem is not a compatibility problem. Can you grab the WIFI air packet? I need to use this to confirm the problem.

@ESP-YJM
I haven't grabbed WiFi air bag before. How do I grab this?

@CYCHEN97 You can use OmniPeek to capture. Before capture, you may need buy a Wireless network card.

@CYCHEN97 You can follow this https://docs.espressif.com/projects/esp-idf/zh_CN/latest/esp32/api-guides/wireshark-user-guide.html. Note, set the AP as open mode and not set password.

@CYCHEN97 Do you have any update for this issue? If not, we will close this issue.

Thanks for reporting, will close due to short of feedback, feel free to reopen with more details.


uncertainty traps

Could eliminate the two auxiliary functions (down from 4) and get rid of the broadcasting.

Took a look at this last week, and it's not worth the trouble.


bazel.tsan tests are very flakey

I noticed this previously, but since resolving other flakes this has now become a pretty regular feature
This is easily reproducible locally running the tsan tests - in fact i struggled to ever get them to pass - i will investigate this further
What is interesting is that there are always multiple failures, if any - eg:

/test/extensions/filters/http/rbac:rbac_filter_integration_test          FLAKY, failed in 2 out of 6 in 321.6s
  Stats over 6 runs: max = 321.6s, min = 257.1s, avg = 280.2s, dev = 26.7s
  /build/tmp/_bazel_envoybuild/b570b5ccd0454dc9af9f65ab1833764d/execroot/envoy/bazel-out/k8-dbg/testlogs/test/extensions/filters/http/rbac/rbac_filter_integration_test/shard_3_of_4/test_attempts/attempt_1.log
  /build/tmp/_bazel_envoybuild/b570b5ccd0454dc9af9f65ab1833764d/execroot/envoy/bazel-out/k8-dbg/testlogs/test/extensions/filters/http/rbac/rbac_filter_integration_test/shard_4_of_4/test_attempts/attempt_1.log
//test/integration:multiplexed_integration_test                           FLAKY, failed in 2 out of 10 in 312.0s
  Stats over 10 runs: max = 312.0s, min = 201.6s, avg = 260.9s, dev = 34.9s
  /build/tmp/_bazel_envoybuild/b570b5ccd0454dc9af9f65ab1833764d/execroot/envoy/bazel-out/k8-dbg/testlogs/test/integration/multiplexed_integration_test/shard_5_of_8/test_attempts/attempt_1.log
  /build/tmp/_bazel_envoybuild/b570b5ccd0454dc9af9f65ab1833764d/execroot/envoy/bazel-out/k8-dbg/testlogs/test/integration/multiplexed_integration_test/shard_8_of_8/test_attempts/attempt_1.log
//test/integration:filter_integration_test                              TIMEOUT in 2 out of 13 in 313.4s
  Stats over 13 runs: max = 313.4s, min = 255.0s, avg = 277.8s, dev = 16.9s
  /build/tmp/_bazel_envoybuild/b570b5ccd0454dc9af9f65ab1833764d/execroot/envoy/bazel-out/k8-dbg/testlogs/test/integration/filter_integration_test/shard_1_of_12/test.log
  /build/tmp/_bazel_envoybuild/b570b5ccd0454dc9af9f65ab1833764d/execroot/envoy/bazel-out/k8-dbg/testlogs/test/integration/filter_integration_test/shard_1_of_12/test_attempts/attempt_1.log

https://dev.azure.com/cncf/envoy/_build/results?buildId=129052&view=logs&j=d1f76054-8f79-554b-6f4a-11d6a63b8e00&t=266e17e3-d213-54b5-deef-0dcee01da137&l=7976
its always the same integration tests that fail, or rather its always some of the same ones, as not all fail every time it does
this seems to point to some underlying test framework issue - or maybe there just are a lot of tsan failures that are not always being exposed for some reason
running the tests individually never seems to trigger anything

cc @danzh2010 who i believe has a fix for at least one of the flaking tests

highlighting the issue in analytics

in fact i struggled to ever get them to pass

the reason for this was that i was running locally due to not having the ENVOY_RBE env var set which meant that ci/do_ci.sh ignored my local bazel config

reopening this as we are now seeing it a lot without rerunning flakes

Closing in favor of opening individual test bugs


Make PDA rechargeable

Reason
Medics use their pda instead scanners so scanners are pointless for them. If they use their PDA it'll lose it power so they should actually use scanners.
Crew members will use their ID card properly. ID slot would make more sence, since PDA looks off the style of slot.

bad idea

if this is done mappers should map extra chargers into med

If we make a comparison with tg/station, cause they have these functionality, (if remember well) its still nonsense for us to have charge pda due of having functionality, that belongs exsclusive for medical departament.
Pda just give us info about manifest, note app and news block. Oh and little lighter, why again we need a charge it? For what we must pay by our time?


Tab character not considered whitespace.

The top one works, but the bottom one errors out with: error: invalid character: '\t'
pub fn main() -> %void {
    @import("std").debug.warn("Hello, world!\n");
}

vs
pub fn main() -> %void {
	@import("std").debug.warn("Hello, world!\n");
}

cf. #544
Maybe we could add this to invalid_char_error
    } else if (c == '\t') {
        tokenize_error(t, "invalid horizontal tab, use spaces instead");

I'm curious as to the design choice behind rejecting tabs as indentation...

Arguing about tabs vs spaces is for other languages. In Zig nobody argues about tabs vs spaces. Instead we work on writing robust, high performing software.

I don't want to start a flame war.
I was actually just wondering.
Because of that I'll probably have to put zig down.


Force outside sensor, what does it do?

Hi, didn't find an explanation for what the "Force outside sensor" does

@mstendah it forces the outdoor sensor to be registered in HA even if it's not reporting a valid temperature at startup.

Removed in v1.1.0


InitSensor(); return error

In my setup when I call InitSensor(); for my sensor it returns an error all the time, even if I put it in a loop, I've tried going into the header files a bit, inside the InitSensor method, it returns an error from the VL53L4CD_SensorInit() method, further than that I didn't get into.
It won't even run when I upload one of your examples.

Hi
Could you share your setup ?
Core version, board, ...

Hey,
I somehow got past that error with one sensor, but my board is going to use 2 sensors on the same i2c.
I'd love it if you could maybe even upload an example with 2 or more sensors, how you would init them and use them afterwards.
When I try to use 2 of them, weird errors occur, but I'm almost sure it's because of me, since I'm probably not using them correctly.
I'm uploading my init of the sensors, it won't even go to loop as far as I can see, maybe I'm doing something out of order.
I'm using an Arduino nano 33 ble.

Hi @AlexLazarovich ,
here you can find how to do the setup of more than one sensor for VL53L4CD. Are pin "A1" and pin "A2" respectively the XSHUT pins for dSensorL1 and dSensorL2? It's important that the XSHUT pins are well connected to the board in order to use more than one ToF sensor. Finally, please try to change 0x53 I2C address (with for example 0x10) for dSensorL1. The I2C addresses 0x52 and 0x53 are already used by dSensorL2 respectively for write operations and read operations on I2C bus.
Best Regards,
Carlo

Hey, the XSHUT pins are connected correctly, the address change did the job. I didn't know that it uses 2 addresses, that is probably why my Serial kept crashing after I've init-ed them with 0x52 and 0x53, there was a collision on 0x53, I'd love it if you could add that remark, that when adding more than one I2C user in general, keep the next address available.
Also, for the original problem of the issue, if someone would find it helpful in the future, my problem in advance was, that when I designed the board I've routed 5v to the sensors, so I've had to add a step-down level shifter (chose it instead of flying wires at first) which dropped down the voltage to about 3.05v which should be a ok for the sensor, but my XSHUT was routed correctly to an analog output pin on my arduino nano 33 ble, which was outputting 3.3v, and the sensor would not init.
When I connected the sensor with 3.3v from my nano 3.3v voltage output it miraculasly came to life.
My only guess is that the difference in voltages between the XSHUT input and the VDD input just didn't let it work.
May my experience help someone in the future.
Thank you for your help!
Alex.

Hello @AlexLazarovich ,
actually the info about the I2C address is contained in the datasheet of the component here paragraph 3:
"A message contains a series of bytes preceded by a start condition, and followed by either a stop or repeated
start (another start condition but without a preceding stop condition), followed by another message. The first byte
contains the device address (0x52) and also specifies the data direction. If the least significant bit is low (that
is, 0x52) the message is a master-write-to-the-slave. If the LSB is set (that is, 0x53) then the message is a
master-read-from-the-slave."
Thanks to have shared your tips.
I will close this issue.
Best Regards,
Carlo


TCH quote-annotations fixes introduced runtime errors into my tests

This is one of the inputs to my function, after quotes were automatically added (and I manually turned QuerySet['ContractVersion'] into 'QuerySet[ContractVersion]' due to #9135 and #9136:
contract_versions_list: list['ContractVersion']
    | 'QuerySet[ContractVersion]'
    | None = None,

When I manually changed it to the following, the tests ran fine again:
contract_versions_list: 'list[ContractVersion] | QuerySet[ContractVersion]| None' = None,

I'm on Ruff v0.1.8 in a Django 4.2.7 project, running tests with PyTest 7.4.3

What was the original annotation?

The issue here is that you changed QuerySet['ContractVersion'] to 'QuerySet[ContractVersion]' which isn't valid -- you need to quote the entire binary operation. But I'm just trying to understand, because you applied that change yourself?

Yes, it looks like I introduced this error when trying to manually resolve the warning from Ruff, since I didn't realize it was invalid to quote just part of it. I'm surprised Pyright doesn't complain about an invalid annotation. Is it possible to make Ruff complain about it?
My original annotation had no quotes in it:
list[ContractVersion]
    | QuerySet[ContractVersion]
    | None = None,

We could probably lint against that, yeah.

Repurposing the issue to lint against "int" | str which is invalid.


Fixed redirect with port

Fix redirect when there is a :port in the URL.
Fixes #716

@alexander-schranz updated to use the php parse_url function, it now supports query and fragments.
Not sure how to refactor it upstream though.. I can't see a good way to do it without refactoring. Maybe @danrot can advise.
If not I suggest we merge this as-is.


BUG: requests without timeout

Description
The code scan that occurs for PRs when we push now fails with multiple instances of "request without timeout."
Steps to Reproduce
Push any code change with a PR, and watch the "code scan" fail.
Additional Info & Resources
Here are instances of the failure.
example request with timeout: r = requests.get('https://example.com/', timeout=5)
Workaround
We can manually ignore the failure for other tickets.
Impact/Urgency
This is urgent because it can affect every PR.
Expected Behavior

[ ] Every request has a timeout parameter.
[ ] Code Scan does not report these errors on PRs

QA Considerations
For QA to populate. Leave blank if QA is not applicable on this ticket.

Hey team! Please add your planning poker estimate with Zenhub @cris-oddball @EvanParish @ianperera @jakehova @justaskdavidb2 @k-macmillan @kalbfled @ldraney

These changes cleared to code scan failure, but we later discovered that the timeout value often causes user-flows tests to fail.  I increased to timeout value to 5s (read and write) for user-flows as part of the changes for #724.


Mock yahoo finance service during testing

Changed

Refactored YahooFinanceService as SecurityService, allowing yahoo-finance2 code-behind to be mocked during testing
Added Yahoo Finance Service mock, relevant testdat files (json) and added it to all the tests

Checklist

[ ] Added relevant changes to README (if applicable)
[x] Added relevant test(s)
[x] Updated GitVersion file

Fixes #60

Need to add some instructions on how to add new testdata to the mock.

@lildude I found an issue in the Freetrade converter where it seemed like it didn't process dividends correctly. I believe the result file of the main-branch version of the tool would not be accepted by Ghostfolio. I think I fixed that.

Whoops. I thought I didn't need that so removed it instead of moving it. Good catch. Thanks.


Petermetz/issue1471

Primary changes:

Added robust debug logging to the express middleware of the API server
so that problems like this are easier to debug in the future (e.g.
trouble with the Open API spec documents themselves)
Refactored the ci.yaml document so that there are separate jobs for
each tape based Fabric connector integration test. This has reduced
(or potentially eliminated) the presence of the flake that we were
encountering during the contract deployment test cases. It also has the
upside of faster CI because of more parallelism in the CI jobs.
Updated the assertions in a couple of test cases where the newer Fabric
versions were causing the assertions to fail because the returned JSON
response in the example asset transfer chaincode is now referring to the
asset owner via a property named "Owner" not "owner" (casing difference)

Fixes #1471
Signed-off-by: Peter Somogyvari<EMAIL_ADDRESS>

FYI: I've split this into 2 commits because one of them is an important bug-fix (that I uncovered while investigating the test flake) while the rest of the diff is much bigger and not an actual bug fix (just addresses the flakiness of the test but does not fix bug in the production code at all)


chore: Update and release workspace members for SDP 24.11

Part of https://github.com/stackabletech/issues/issues/647.
Update and Release Workspace Members for Stackable Release 24.11

[!NOTE]
During a Stackable release we update all dependencies in the operator-rs
repository. After these bumps, each workspace member is released using an
appropriate SemVer version. Later, each product operator repository can then
use the updates crates.

Replace the items in the task lists below with the applicable Pull Requests
### Tasks
- [ ] https://github.com/stackabletech/operator-rs/pull/899
- [ ] https://github.com/stackabletech/operator-rs/pull/897
- [ ] https://github.com/stackabletech/operator-rs/pull/900
- [x] Push the release tags using `.scripts/tag_and_push_release.sh`.
- [ ] https://github.com/stackabletech/docker-images/pull/902

Update Rust Version and Workflow Actions

[!NOTE]
The PR is usually titled: chore: Bump Rust version and workflow actions

Adjust the version of the channel in the rust-toolchain.toml file. See
https://releases.rs.
Adjust the version RUST_TOOLCHAIN_VERSION in the workflows:

.github/workflows/build.yml
.github/workflows/pre_commit.yaml

Add a changelog entry.
Update any actions (using the Git commit hash) in the workflows. Hint: Also
make sure that the cargo-udeps action is up-to-date, otherwise the CI might
report errors.

Update Rust Dependencies

[!NOTE]
This PR is usually titled: chore: Bump Rust dependencies

Bump minor versions of dependencies in the Cargo.toml manifest.
Then run the cargo update command.
Fix any code which needs updating due to the dependency bumps.
Locally update any product operator to identify any breaking changes
downstream.

Hint: Use the [patch."https://github.com/..."] mechanism to temporarily
override the dependency.

Add a changelog entry if required.

Adjust and Verify Crate Versions

[!WARNING]
Currently, all workspace members use 0.X.Y versions. This means we can
introduce breaking changes in any version without needing to bump the major
level. But we still have the following rules:

Breaking changes (internally and externally) will bump the minor level of
the version, so 0.X.Y becomes 0.X+1.Y.
All other non-breaking changes will bump the patch level of the version, so
0.X.Y becomes 0.X.Y+1.

[!NOTE]
The PR is usually titled: chore: Release workspace members

Bump the crate versions in their appropriate Cargo.toml manifests.
Verify the previous step using .scripts/verify_crate_versions.sh.

Completed.