start() finished() loading animation sync with apollo query result

It would be great if this module could hook the apollo query to the start(), finished() function of the global loading component.
 apollo:{
   query:`someQuery`,
   watchLoading(isLoading){
      // => it would be great if the isLoading variable could be synchronized with the nuxt state change behaviour
          // following is not working:
          if (isLoading) {
            this.$root.$loading.start()
          } else {
            this.$root.$loading.finish()
          }
   }
 }
}

Hi @dohomi
Does this code works when you implemented it?

@Atinux no it does not work. The problem is, that the routing already calls start() and finish() before the watchLoading hook is being called. And somehow (I don't know the reason) the call of
 watchLoading(isLoading){
      // => it would be great if the isLoading variable could be synchronized with the nuxt state change behaviour
          // following is not working:
          if (isLoading) {
            this.$root.$loading.start()
          } else {
            this.$root.$loading.finish()
          }
   }

Is not doing any thing at all.

I see @dohomi
Why not disabling loading into your nuxt.js app and use a custom loader that you can start/end with events instead?
BTW, you are contributing well on this module and honestly, I don't use apollo, do you want to be a maintainer of this module?
Please mention me, I have too many Github notifications so it's hard to keep track of them :/

@Atinux sure you can add me as maintainer, I will try my best.
I'm using a global indicator now and it works quite good so far. Will close it for now, maybe if I find a smarter solution I'll re-post it here

@dohomi Welcome to Nuxt Community :D

@Atinux OK thanks!

Is there any out-of-the-box solution yet or is a custom implementation the only solution?

@IgorSzymanski Not sure if you got it figured out but I was able to get it working with this
watchLoading: function(isLoading) {
    this.$nextTick(() => {
        isLoading ? this.$nuxt.$loading.start() : this.$nuxt.$loading.finish();
    })
}


TextField and Dropdown aren't aligned when both have inline props

Styleguidist code:
<div>
	<TextField inline small placeholder="Search..." header="Tax ID"/>
    <Dropdown width="300px" inline customLabel="Registration Key">
    	<li> test </li>
  	</Dropdown>
</div>

This is fixed by Issue #449


[DOC] Update OpenSearch remote store documentation to include node.attr.remote_store.state.repository in bootstrapping steps

What do you want to do?
The remote store documentation does not specify that the node.attr.remote_store.state.repository setting has to be added in opensearch.yml before bootstrapping the node.

[x] Request a change to existing documentation
[ ] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.

Thanks, @raghuvanshraj ! Will you be creating the doc PR for this update?

We do discuss the setting here: https://opensearch.org/docs/latest/tuning-your-cluster/availability-and-recovery/remote-store/remote-cluster-state/#configuring-the-remote-cluster-state

@raghuvanshraj - Does this need to be updated? If so, can you please provide the required change? https://github.com/opensearch-project/documentation-website/edit/main/_tuning-your-cluster/availability-and-recovery/remote-store/index.md. Thanks!


Video texture in shader not working

Hello!
I updated PIXI.js on my project from 4.0.0 to 4.3.2 and everything is working but one thing, videos inside custom filters (and so shaders).
I'm sending a video texture to a shader using uniforms with sampler2D type.
With 4.0.0, it worked. With 4.3.2, It doesn't work anymore and the texture doesn't appears most of the time (juste some random blinks).
The base video is working. If I use a classic sprite, the video is displaying and playing without error.
The shader is also working fine. When the video is pause, it's display well. I tried with an image instead of the video, it's also working.
It's probably some settings I haven't heard of. Or maybe I need to update the uniform.
I hope it's was clear enough and my english wasn't too bad.
Thanks

Thanks for sharing! If you could provide a fiddle for us to debug that would be ace 👍

Hey @brunosimon have you had a chance to create a code sample we can use to debug this yet?

Hey
I tried to set a sample but a had too much issues to reproduce the exact situation for the problem. I then found a solution and moved on. Sorry, I completely forgot to answer.
It seems that the problem only occurs when we send the texture to the custom filter, but it's working fine when the filter is directly applied to the video sprite (sprite based on the video texture).
We can get the texture inside the shader with the classic texture2D(uSampler, vTextureCoord) without having the glitches.
I also found that sending the video to a canvas and then updating the texture based on the canvas is more efficient. I got a better framerate using this technic.
I hope it can help.

Hi there! Closing this issue for now due to its inactivity. Feel free to give us a poke if you would like this issue reopened. Thanks 👍


EventEmitter memory leak with connect

This is like #161, but it's happening for me on the connect event:
(node:16251) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 connect listeners added. Use emitter.setMaxListeners() to increase limit
    at _addListener (events.js:223:19)
    at Socket.addListener (events.js:240:10)
    at Socket.Readable.on (_stream_readable.js:775:35)
    at Socket.once (events.js:271:8)
    at ClientRequest.<anonymous> (/home/etc/node_modules/needle/lib/needle.js:700:12)
    at Object.onceWrapper (events.js:254:19)
    at ClientRequest.emit (events.js:164:20)
    at tickOnSocket (_http_client.js:656:7)
    at onSocketNT (_http_client.js:672:5)
    at process._tickCallback (internal/process/next_tick.js:152:19)

Once a minute I'm sending off 4 HTTP requests to the same host
They aren't erroring or anything, including connect timeouts
In my last test it took 12 minutes to happen, but it's inconsistent
Node 9.3.0 and 8.9.4

I realize it might not be needle... going to try request to see if it happens there.
Basically the code I'm using (doesn't work as-is):
setInterval( () => {
    const send = async () => {
        const response = await needle( 'PUT', url, body, {
            json: true,
            headers
        });
        if ( response.statusCode !== 200 )
            throw new Error( 'etc' );
    };

    const sends = [ send, send, send, send ];
    await promiseAll( sends, { concurrency: 5 }); // p-all package
}, 60 * 1000 );

Hey @SneakyMax. How did the other test go? Are you running the latest version of needle?

@tomas no warnings with request. One error of socket hang up (but that's on our side, it could be the same thing that caused needle's warnings I suppose).
Was using needle 2.2.0.

What was/is causing the socket hang up error on your side? I'd love to replicate the issue over here.

Honestly, no clue :(. It's a problem I've ran into a couple times with node
when making lots of http requests at once and haven't figured out the
cause.
On Mon, Mar 5, 2018, 5:08 AM Tomás Pollak<EMAIL_ADDRESS>wrote:

What was/is causing the socket hang up error on your side? I'd love to
replicate the issue over here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tomas/needle/issues/238#issuecomment-370413740, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAU6DB958ofBnicjxQaTTF6hKwDonz6iks5tbTjngaJpZM4SbPZG
.

the same error happened with me.
I removed it changing some lines:
request.once('socket', function(socket) {
    socket.once('connect', function() {
      set_timeout('response', config.response_timeout);
    });

to:
request.once('socket', function(socket) {
    if(socket.connecting){
      socket.once('connect', function() {
        set_timeout('response', config.response_timeout);
      });
    } else {
      set_timeout('response', config.response_timeout);
    }

@lucasexe Good catch! I'll patch the code if it works.

Thanks @lucasexe!


Output Panel issues with Telemetry and Extension Telemetry channels

Does this issue occur when all extensions are disabled?: Yes

Version: 1.75.0-insider (user setup)
Commit: 5ae522f8563fe48b89470923f77a9732f96c0472
Date: 2023-01-19T14:51:00.913Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: Yes
Steps to Reproduce:

Set log level to trace
Open the output window

There are a couple of issues here:
1 - The background of the channel picker seems to be transparent now, which makes it hard to read:

2 - The name of the Extension Telemetry channel has changed to the log file path:

3 - The Telemetry channel seems to be completely missing

For contrast, this is how it looks in VS Code 1.74.3:

0723796629

I have done some fixes last week and I assume they could have fixed the missing or wrong labels. Can you please try with the latest insiders and let me know if you can still repro?

For me the extension host telemetry log still has a bad path too, I haven't made any changes here so I think this is caused by output channel changes

@sbatten Are you not only seeing the telemetry channel, but also extension telemetry channel?
@lramos15 Yours might be a glitch, can you please restart and try?

@sandy081 Restart doesn't seem to do anything. Should I delete the log file from my VS Code install path?

Which version of insiders are you on?

Which version of insiders are you on?

Version: 1.75.0-insider (Universal)
Commit: f1b09237cd400d92987cf7a9681995e8011ef54c
Date: 2023-01-23T11:52:31.652Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 22.2.0
Sandboxed: No

@lramos15 May I know if you can repro it while running out of sources?

I provided a fix for telemetry log not being shown.
@lramos15 Lets try to track yours separately

Understood the bug and added the fix to the PR.


[Linux] Can't build

$ cargo build --release
unused manifest key: package.edition
unused manifest key: profile.release.strip
unused manifest key: profile.release-lto.inherits
unused manifest key: workspace.members
unused manifest key: workspace.resolver
thread '<main>' panicked at 'invalid serialized PackageId', ../src/libcore/option.rs:704
note: Run with `RUST_BACKTRACE=1` for a backtrace.

Thanks, I accidentally used the wrong version. it builds now but I run into the same problem: #283


[#36] [iOS] [UI] As a user, I can see the Home screen with surveys

Close #36

What happened 👀

Create UI for the Home screen
Create a custom page indicator
Add a GestureVelocity DynamicProperty to detect fast swipes on the home screen.

Insight 📝
After a user login to the application, they will land on the home screen, which contains a collection of surveys.
Proof Of Work 📹
https://user-images.githubusercontent.com/22606906/236748169-d3d1a267-ff30-453d-857e-cbaf08fcf4df.mp4

@markgravity, I solved your comments above in the commit 246fad5


Fine-tuning on own documents?

Hi - what would be the recommended approach for fine tuning (not full retrain) of the model on one's own documents?
Thank you

Hi, thanks for your interest in our work! I think as long as you convert your own data into the same format as the retriever training data, you can fine-tuning on your own document. Note that our retriever omits the tokens exceeding the maximum token limitations as BERT cannot process longer than 512 sub-tokens. That said, to get the best performance, It may be better to split your documents less than the maximum token limitations.
While you can start from scratch (start training using bert-base-cased or bert-base-uncased), you can start fine-tuning from our NQ / SQuAD / HotpotQA checkpoint. I think you can do that by setting --bert_model to the path to the checkpoint directory. We recommend you using the checkpoints trained on the dataset that is most similar to your own data. If your data requires a lot of multi-hop reasoning and has some bias towards entities, the checkpoints trained on HotpotQA may be the most suitable one to start fine-tuning with. If your data has a relatively limited lexical overlap between questions and paragraphs, the one trained on NQ may be better to be adapted.
Please let me know if you have any followup questions!

I'll close this issue now but please feel free to re-open if you have any questions!


Date parsing issues in Laravel 5.4

Looks like we're still having a few issues with date serialization in Laravel 5.4. From the Thor logs:
[2017-11-06 21:36:07] production.ERROR: Exception: DateTime::__construct(): Failed to parse time string<PHONE_NUMBER>000) at position 11 (0): Unexpected character in /var/www/northstar/releases/20171106201243/vendor/nesbot/carbon/src/Carbon/Carbon.php:291
Stack trace:
#0 /var/www/northstar/releases/20171106201243/vendor/nesbot/carbon/src/Carbon/Carbon.php(291): DateTime->__construct('1510003920000', Object(DateTimeZone))
#1 /var/www/northstar/releases/20171106201243/app/helpers.php(48): Carbon\Carbon->__construct(Object(MongoDB\BSON\UTCDateTime))
#2 /var/www/northstar/releases/20171106201243/app/helpers.php(66): format_date(Object(MongoDB\BSON\UTCDateTime), 'Y-m-d\\TH:i:sP')
#3 /var/www/northstar/releases/20171106201243/app/Models/User.php(413): iso8601(Object(MongoDB\BSON\UTCDateTime))
#4 /var/www/northstar/releases/20171106201243/app/Providers/AppServiceProvider.php(51): Northstar\Models\User->toBlinkPayload()
#5 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php(348): Northstar\Providers\AppServiceProvider->Northstar\Providers\{closure}(Object(Northstar\Models\User))
#6 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php(199): Illuminate\Events\Dispatcher->Illuminate\Events\{closure}('eloquent.update...', Array)
#7 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php(172): Illuminate\Events\Dispatcher->dispatch('eloquent.update...', Array, false)
#8 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Concerns/HasEvents.php(148): Illuminate\Events\Dispatcher->fire('eloquent.update...', Object(Northstar\Models\User))
#9 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(597): Illuminate\Database\Eloquent\Model->fireModelEvent('updated', false)
#10 /var/www/northstar/releases/20171106201243/app/Models/Model.php(95): Illuminate\Database\Eloquent\Model->performUpdate(Object(Jenssegers\Mongodb\Eloquent\Builder), Array)
#11 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(515): Northstar\Models\Model->performUpdate(Object(Jenssegers\Mongodb\Eloquent\Builder))
#12 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Auth/EloquentUserProvider.php(86): Illuminate\Database\Eloquent\Model->save()
#13 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Auth/SessionGuard.php(534): Illuminate\Auth\EloquentUserProvider->updateRememberToken(Object(Northstar\Models\User), 'GTOaxS7v5TQuZx7...')
#14 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Auth/SessionGuard.php(494): Illuminate\Auth\SessionGuard->cycleRememberToken(Object(Northstar\Models\User))
#15 /var/www/northstar/releases/20171106201243/app/Http/Controllers/Web/AuthController.php(164): Illuminate\Auth\SessionGuard->logout()
#16 [internal function]: Northstar\Http\Controllers\Web\AuthController->getLogout(Object(Illuminate\Http\Request))
#17 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Controller.php(55): call_user_func_array(Array, Array)
#18 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(44): Illuminate\Routing\Controller->callAction('getLogout', Array)
#19 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Route.php(203): Illuminate\Routing\ControllerDispatcher->dispatch(Object(Illuminate\Routing\Route), Object(Northstar\Http\Controllers\Web\AuthController), 'getLogout')
#20 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Route.php(160): Illuminate\Routing\Route->runController()
#21 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Router.php(572): Illuminate\Routing\Route->run()
#22 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(30): Illuminate\Routing\Router->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#23 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Middleware/SubstituteBindings.php(41): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#24 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Routing\Middleware\SubstituteBindings->handle(Object(Illuminate\Http\Request), Object(Closure))
#25 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#26 /var/www/northstar/releases/20171106201243/app/Http/Middleware/SetLanguageFromHeader.php(33): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#27 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Northstar\Http\Middleware\SetLanguageFromHeader->handle(Object(Illuminate\Http\Request), Object(Closure))
#28 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#29 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/VerifyCsrfToken.php(65): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#30 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Foundation\Http\Middleware\VerifyCsrfToken->handle(Object(Illuminate\Http\Request), Object(Closure))
#31 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#32 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/View/Middleware/ShareErrorsFromSession.php(49): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#33 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\View\Middleware\ShareErrorsFromSession->handle(Object(Illuminate\Http\Request), Object(Closure))
#34 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#35 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php(64): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#36 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Session\Middleware\StartSession->handle(Object(Illuminate\Http\Request), Object(Closure))
#37 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#38 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/AddQueuedCookiesToResponse.php(37): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#39 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse->handle(Object(Illuminate\Http\Request), Object(Closure))
#40 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#41 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/EncryptCookies.php(59): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#42 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Cookie\Middleware\EncryptCookies->handle(Object(Illuminate\Http\Request), Object(Closure))
#43 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#44 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(102): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#45 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Router.php(574): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#46 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Router.php(533): Illuminate\Routing\Router->runRouteWithinStack(Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request))
#47 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Router.php(511): Illuminate\Routing\Router->dispatchToRoute(Object(Illuminate\Http\Request))
#48 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(176): Illuminate\Routing\Router->dispatch(Object(Illuminate\Http\Request))
#49 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(30): Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http\{closure}(Object(Illuminate\Http\Request))
#50 /var/www/northstar/releases/20171106201243/vendor/fideloper/proxy/src/TrustProxies.php(56): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#51 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Fideloper\Proxy\TrustProxies->handle(Object(Illuminate\Http\Request), Object(Closure))
#52 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#53 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(30): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#54 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(Object(Illuminate\Http\Request), Object(Closure))
#55 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#56 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php(27): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#57 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Foundation\Http\Middleware\ValidatePostSize->handle(Object(Illuminate\Http\Request), Object(Closure))
#58 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#59 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(30): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#60 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(Object(Illuminate\Http\Request), Object(Closure))
#61 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#62 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php(46): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#63 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode->handle(Object(Illuminate\Http\Request), Object(Closure))
#64 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#65 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(102): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#66 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(151): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#67 /var/www/northstar/releases/20171106201243/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(116): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request))
#68 /var/www/northstar/releases/20171106201243/public/index.php(51): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request))
#69 {main}

So this is because we're passing a raw Mongo UTCDateTime to our formatting helpers, and Carbon is unable to automatically parse that into a DateTime instance since it has milliseconds in the timestamp value. Adding these fields to the $dates property on the model clears up the problem.

This should be fixed by #690.


The so called fix button does the OPPOSITE OF FIX

This is what my avatar was supposed to look like

And this is what happened to it

It's simple its just that normals got inverted, flip them again and you will be good to go


add environmentDressing class to dressing entity

https://github.com/feiss/aframe-environment-component/pull/21 was reverted, but I still want to add the environmentDressing class to the dressing entity if that's possible. Thanks.

yup! forgot about this, that can be useful. Thanks!


Facing issue on analytics Events

@hmvmpire Would it be possible for you to share a little more of the code that is causing the error?


Allow easyinstall.sh to run without user input

Info

Which version of Pi are you using: N/A
Which github revision of software: v22.10.01
Which board version: N/A
Which computer is the RaSCSI connected to: N/A

Describe the issue
When building the Raspberry Pi OS release images, there is one step that requires user interaction half-way through. The easyinstall.sh script will ask for the user password to support the sudo commands. It would be useful if the easyinstall script could be run 100% without user input. We could potentially get to a point where Github actions can create a Raspberry Pi OS disk image for each commit to develop.

I ran through the latest develop version of the script, and the only place where it explicitly paused was in installRaScsiCtrlBoard() which I don't think is relevant for the build script, since it shouldn't get to this function (unless I'm mistaken!)

Just as a heads up, there's a few examples where I've used the --headless param ($HEADLESS) to instruct the script to use defaults/skip confirms, for non-interactive activity.

The user prompt that I run into is the sudo -v where it prompts for the user's password.
Here's the portion of the OS creation script that calls easyinstall.sh. Maybe I just need to add --headless?

@akuker Is it feasible to set the NOPASSWD flag for the user in your environment? This would entirely bypass the sudo -v command.

@akuker Can you see if this does the trick for you? https://github.com/akuker/RASCSI/pull/963


Currency parsing to currency.js

Adding currency parsing to currency.js by:

Parse the currency string for numbers, commas, and periods: valueString.replace(/[^\d\.\,]/g, '')
Run numberParser

Currency codes define the symbols and locale defines the number format. If we're just parsing the number, we can strip away the symbols and parse the number in the locale specified in the settings

I don't expect this build to pass as there are some code issues. I want some help working on the PR.

Hi @goatandsheep sorry for the delay on my review. Thanks for your interest to implement this very welcome feature. From your code, it seems you're simply doing a number parser, i.e., the currency is simply being ignored. It's important that currency parser is given which currency the input is expected to be in and if the input matches that, e.g., parsing "0,05 €" should fail if you expect USD input.

@rxaviers thank you so much for reviewing my PR. I'll get to the fixes, but first I wanted to address your concern about the simplicity of the function.
Perhaps I'm wrong about this opinion, but I believe the . vs , issue is related to locale, which your NumberParser handles beautifully.
Regarding currency symbols, unless it includes a value factor like the M in $10M, non-digits are simply identifiers of the type of currency, which can be already recognized by the currency code. We can even constraint the input to not allow value factors.

Let's define the goal of currency parser.
It should:

be able to parse strings created by formatCurrency; E.g., currencyParser("USD")(currencyFormatter("USD")(10)) // 10;

It should NOT:

try to guess on which currency the input is at. E.g., parse("$10") // {currency: "USD", value: 10} This is error prone because figuring out currency is non deterministic (there are various currencies that use the same symbol)

In terms of implementation:

It should not duplicate number code; it should leverage numberParser and only do the extra logic that is needed to get currency parsing, which is to check for the currency string. See how currencyFormatter works and read http://www.unicode.org/reports/tr35/tr35-numbers.html#Currencies

I agree with the goals that you've stated, but I don't agree that we need to look at the currency code to identify quantity. We don't need to guess because we don't even need to know the type of currency. All we need to do is strip away the currency symbols and parse the number. As I said earlier, 0,05 € is not a format that would be typed in the locale en-us, just as €0.05 would not be typed in the locale fr. NumberParser is conscious of locale, so as you mentioned, it is a great tool to distinguish the , vs .

Sorry, if one wants to simply strip away the currency symbol and parse the number, they can use today (a) this regexp to strip away currency and (b) number parser to normalize the amount. This is a BAD solution for obvious reasons (i.e., not good to assume a wrong currency).
The best way to capture such information is to provide a good UI where user can select the currency and type the amount.
The currency parser, by doing what's defined above https://github.com/globalizejs/globalize/pull/795#issuecomment-372307858), would be useful to parse a controlled input (either using mask, or a future format currency to parts).

@rxaviers @goatandsheep Are there any updates on this?

@frankrobert-ls unfortunately not because of our disagreement of opinions. @rxaviers believes that you need to extract further localization information from the currency symbol and I believe that you just need the localization information that the browser gives you.
My recommendation is just to use this other currency parser.

actually @rxaviers I don't mind redoing the whole PR to match the style of the above mentioned package, which does the currency matching

FWIW, I am not accepting this PR because it lacks (at least) functionality that prevents adding these two unit tests.

https://github.com/globalizejs/globalize/pull/795#discussion_r173446337
https://github.com/globalizejs/globalize/pull/795#discussion_r173446454

I am open to accept this PR (or a subsequent one leveraging the changes made here) if the above is met.

Sounds good! Will do.


Create Whack-a-mole game

Aim

Create Whack A Mole game

Details

Few components of the game have already been added.
Add new features or improvise the existing features

@geekymeeky I have added a pull request for this issue. Please review it and let me know if any further changes is to be made.

@geekymeeky I have added a pull request for this issue. Please review it and let me know if any further changes is to be made.

Sure

#8


[BEAM-600] Add TestCountingSource option to specify the number of splits returned by generateInitialSplits.

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[x] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[x] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[x] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

Hi @dhalperi, @dpmills, can you please take a look? Thanks!

LGTM

R: @lukecwik


CPU parsing should return an empty list if string is blank

The change looks reasonable to me, but I'm not quite sure how to reproduce the issue. Is this for when available_cpus reads the system files and finds a blank file?

The error happens when there are not isolated CPUs in the system. In that case, the list of CPUs is an empty line. I agree the fix should also address an empty line. Possibly trimming the line is the right thing to do.

LGTM. Looks like CI failed but is it just the recent snabbnfv test flakiness?


iOS app crashing when Save Image is selected

On an iOS device, the app crashes when I select Save Image - This is on the SImulator. When I select Shared Albums I get the shared albums dialog which seems fine. Just the "Save Image" link causes the app to crash.
No debug output. It just terminates.

Tried this on the device too. Same thing.
Other forms of sharing images seem to work.
FYI my image in a PNG image, only about 140kb

FYI I was able to solve this.
In iOS it is required to add the following to the Info.plist file if you do not exclude "Save Image":
<key>NSPhotoLibraryAddUsageDescription</key>
<string>$(PRODUCT_NAME)</string>

Adding this to Info.plist solved it and it works great.

@richgoldmd  yes,  "NSPhotoLibraryAddUsageDescription" should be added to the info.plist for saving images to photo library. Thanks for your feedback.


Add flake8 to tests or black to CI

Currently it looks like PRs can pass tests without passing flake8 tests.  Do we want to start enforcing style?

Do we want to start enforcing style?
I would like this. Is there a standard flake8 config and way to enforce this for dask sub projects?

Nothing fully standard.  We could grab the setup.cfg from dask/dask or
dask/distributed
On Fri, Jul 27, 2018 at 7:09 AM, Joe Hamman<EMAIL_ADDRESS>wrote:

Do we want to start enforcing style?
I would like this. Is there a standard flake8 config and way to enforce
this for dask sub projects?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask-jobqueue/issues/106#issuecomment-408429876,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AASszPiUqjXNdf4Rw-PmLiwH4buVVrpPks5uKx8LgaJpZM4Viyd0
.

See #109. As far as I can tell, we've been running flake8 all along. Maybe @lesteve or @guillaumeeb has some idea why things weren't being raised in #78.

I remember asking myself if the none.sh job_script function would show something in Travis if flake checks failed.
The thing that troubled me is that we are running flake8 and py.test in one Travis operation. Maybe we should add a && between the two calls to take into account both return codes?

Closed with #110.


Documentation improvement for macOS

Describe the bug
At least for MacPorts users, with a clean environment, the Host Dependencies part is incomplete. Without Rust and cargo, Install Python Dependencies step will fail for lack of cargo.
To Reproduce
Steps to reproduce the behavior:

Follow the Getting started guide until the pip dependencies part
get the error

Expected behavior
It should build without any error
Impact
Prevent the project from building on macOS
Screenshots or console output
The error log:
Building wheels for collected packages: cmsis-pack-manager
  Building wheel for cmsis-pack-manager (setup.py) ... error
  ERROR: Command errored out with exit status 1:
   command: /opt/local/Library/Frameworks/Python.framework/Versions/3.7/bin/python3.7 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/tmp/pip-install-4r20yn1r/cmsis-pack-manager/setup.py'"'"'; __file__='"'"'/private/tmp/pip-install-4r20yn1r/cmsis-pack-manager/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /private/tmp/pip-wheel-z866nvuj --python-tag cp37
       cwd: /private/tmp/pip-install-4r20yn1r/cmsis-pack-manager/
  Complete output (9 lines):
  fatal: Not a git repository (or any of the parent directories): .git
  running bdist_wheel
  running build
  running build_py
  creating build/lib
  creating build/lib/cmsis_pack_manager
  copying cmsis_pack_manager/__init__.py -> build/lib/cmsis_pack_manager
  copying cmsis_pack_manager/pack_manager.py -> build/lib/cmsis_pack_manager
  error: [Errno 2] No such file or directory: 'cargo': 'cargo'
  ----------------------------------------
  ERROR: Failed building wheel for cmsis-pack-manager
  Running setup.py clean for cmsis-pack-manager
Failed to build cmsis-pack-manager
ERROR: pyocd 0.21.0 has requirement cmsis-pack-manager>=0.2.7, but you'll have cmsis-pack-manager 0.1.1 which is incompatible.
Installing collected packages: pyusb, intelhex, cmsis-pack-manager, sortedcontainers, intervaltree, pyocd, pyserial, Pillow, zipp, importlib-metadata, pluggy, py, more-itertools, wcwidth, atomicwrites, pytest, gcovr
  Running setup.py install for cmsis-pack-manager ... error
    ERROR: Command errored out with exit status 1:
     command: /opt/local/Library/Frameworks/Python.framework/Versions/3.7/bin/python3.7 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/tmp/pip-install-4r20yn1r/cmsis-pack-manager/setup.py'"'"'; __file__='"'"'/private/tmp/pip-install-4r20yn1r/cmsis-pack-manager/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /private/tmp/pip-record-y3p0vclu/install-record.txt --single-version-externally-managed --compile
         cwd: /private/tmp/pip-install-4r20yn1r/cmsis-pack-manager/
    Complete output (9 lines):
    fatal: Not a git repository (or any of the parent directories): .git
    running install
    running build
    running build_py
    creating build/lib
    creating build/lib/cmsis_pack_manager
    copying cmsis_pack_manager/__init__.py -> build/lib/cmsis_pack_manager
    copying cmsis_pack_manager/pack_manager.py -> build/lib/cmsis_pack_manager
    error: [Errno 2] No such file or directory: 'cargo': 'cargo'
    ----------------------------------------
ERROR: Command errored out with exit status 1: /opt/local/Library/Frameworks/Python.framework/Versions/3.7/bin/python3.7 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/tmp/pip-install-4r20yn1r/cmsis-pack-manager/setup.py'"'"'; __file__='"'"'/private/tmp/pip-install-4r20yn1r/cmsis-pack-manager/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /private/tmp/pip-record-y3p0vclu/install-record.txt --single-version-externally-managed --compile Check the logs for full command output.

Environment (please complete the following information):

OS: macOS 10.12.6
Toolchain: Not used yet

Additional context
Similar problem with FreeBSD:
https://github.com/ARMmbed/cmsis-pack-manager/issues/97

@chenguokai  . Thanks for the bug report. Would you like to submit a pull request with a proposal of the fixes to the documentation?

@chenguokai I have never installed cmsis-package-manager or Rust or cargo on my macOS machine and build Zephyr every day. Macports is not supported officially, only Homebrew, so this is not a bug but rather an improvement

Just double-checked that, with Homebrew's Python no Rust is required at all:
Collecting cmsis-pack-manager>=0.2.7 (from pyocd==0.21.0->-r scripts/requirements.txt (line 13))
  Downloading https://files.pythonhosted.org/packages/88/e9/4cd8d5069f805eeac595eaca58ea93cf859532ed24614b6e6d0178a074c7/cmsis_pack_manager-0.2.8-py2.py3-none-macosx_10_13_x86_64.whl (2.1MB)
     |████████████████████████████████| 2.2MB 16.2MB/s

Maybe there are some differences between the python3 installed with MacPorts and Homebrew. I will try to make a pull request adding a comment for this.

Maybe there are some differences between the python3 installed with MacPorts and Homebrew. I will try to make a pull request adding a comment for this.

Thanks for that @chenguokai. Look forward to reviewing your Pull Request.


Support primary/secondary failover mode using conntrackd and keepalived

The goal here is to use a primary/secondary configuration to improve fck-nat availability without the need for outside infrastructure. It's really important to me that fck-nat does not take on additional AWS service dependencies. The ideal state is that two autoscaling groups would allow for primary and secondary nodes to self-heal and as long as both nodes aren't offline at the same time failover would be seamless.
Here's a few articles documenting the approach in a non-AWS environment:

https://satishdotpatel.github.io/ha-with-keepalived-and-conntrackd/
https://geek.cm/2017/12/ha-network-gateway-with-keepalived-and-conntrackd/
https://backreference.org/2013/04/03/firewall-ha-with-conntrackd-and-keepalived/index.html

Here's the rub: In AWS, we can't just willy nilly change our IP address. We have to explicitly move ENIs and EIPs. This takes some time. So the question becomes: In this configuration, can we move these resources fast enough to not incur downtime (packet loss is fine, downtime == dropped connections)?
This is going to take a lot of testing, but this is my ideal HA configuration for fck-nat 2.0 if it works.

I've been running conntrackd + keepalived/pacemaker for firewall and then an ipvs pair with pacemaker as my failover for firewall/loadbalacing for 16 years now, it works well, just remember not to use multicast for things.
I haven't had much of a problem moving eip between systems in a useful time, though I haven't timed moving eni's

@patrickdk77  Yeah, I've got pretty good confidence this will work. I ran plenty of conntrackd+keepalived in ye olden days, but I'm not sure how well it'll translate to AWS networking.


promiseFn is called only once even if argument has changed

react: 16.8.6
react-async: 7.0.4
react-router-dom: 5.0.1
Hi guys, I have the following problem:
<BrowserRouter>
    <Nav>
        <NavLink to="/">Home</NavLink>
        <NavLink to="/page/about">About</NavLink>
        <NavLink to="/page/contact">Contact</NavLink>
    </Nav>
    <Switch>
        <Route exact path="/" component={Home} />
        <Route exact path="/page/:slug" component={Page} />
    </Switch>
</BrowserRouter>

Then in my Page component:
...
const getPage = ({ pageId }: { pageId: string }) => {
    return new Promise((resolve, reject) => {
        resolve(pageId);
    });
};

const Page = ({ match }: { match: any }) => {
    const { data, isPending, isRejected, isResolved, error } = useAsync({
        promiseFn: getPage,
        pageId   : match.params.slug
    } as any);
...

When navigating from Home to About or Contact all works fine: getPage is called every time, BUT when navigating from About to Contact and viceversa getPage is called only the first time, like it has no idea that "pageId" has changed.
This works perfectly fine though:
const pageId = match.params.slug;
const [isPending, setIsPending] = React.useState(false);
const [error, setError] = React.useState(null) as any;
const [data, setData] = React.useState(null) as any;

useEffect(() => {
        setIsPending(true);
        getPage({ pageId }).then(data => {
            setIsPending(false);
            setData(data);
            setError(null);
        }).catch(e => {
            setIsPending(false);
            setError(e);
            setData(null);
        });
}, [pageId, setData, setError]);

Am I missing something? I really can't figure this out.
Thank you!

Navigating from Home to About/Contact makes it render a different component (Home or Page), hence triggering getPage, while navigating from About to Contact will stay in the same Page component, just with different props. This is how React works (it tries to reuse as much as possible).
 You can do so by providing  watch={match.params.slug}, so it will reload when the slug changes.

Thank you @ghengeveld! I will try and let you know.


Updating Response codes

Removing 404 not found response codes as we have removed that from the code.
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

@sranthar validations are failing as you need to remove the 404 from examples as well

/azp run automation - sdk

/azp run automation - sdk

    "responses": {

Since you're fixing responses, you should also add a default response to all operations that points to the standard error response definition in common-types. (https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content)

Refers to: specification/azsadmin/resource-manager/network/Microsoft.Network.Admin/preview/2015-06-15/Quotas.json:45 in ffa095c. [](commit_id = ffa095c67616cd75fbb597ac707f4c8554d1b437, deletion_comment = False)

Added a comment. Please take a look.

@sranthar , please address the comment.

    "responses": {

We discussed and this will be deferred to a later PR.

In reply to: 606267856 [](ancestors = 606267856)

Refers to: specification/azsadmin/resource-manager/network/Microsoft.Network.Admin/preview/2015-06-15/Quotas.json:45 in ffa095c. [](commit_id = ffa095c67616cd75fbb597ac707f4c8554d1b437, deletion_comment = False)

@sranthar, please fix the error in CI check. More error detail is available at https://dev.azure.com/azure-sdk/public/_build/results?buildId=337365&view=results.

Close it as it is duplicate to #8961 per @sranthar.


Cannot load uploaded image, stuck with loading spinner

the image uploaded in the trunk environment, can not be viewed now.
image url<EMAIL_ADDRESS>@stackia

@jizhekai As mentioned in https://github.com/mashcard/mashcard/issues/39#issuecomment-1163513240, it'll be resolved in https://github.com/mashcard/mashcard/issues/48


Adds support for multiple different helper roles

There are three main categories of role: staff (includes instructor, staff, and grader roles from Ok), helper (staff roles plus lab assistant role from Ok), and student (student or not enrolled on Ok).

Is this closed by #196? Staff members can put students on hold, but students cannot put themselves on hold. This has the same basic functionality but prevents students from using this feature to camp out at the top of the OH queue, since a staff member must put them on hold manually.


ExampleTypes assert in DisplayFields()

This code asserts:
#include <fstream>

namespace
{
	struct empty : std::ifstream
	{
		empty() {}
	};
}

int main()
{
	return 0;
}

Due to no support for LF_IVBCLASS. If you change the struct to a class, works fine.
From what I can tell here with this limited test case, replicating https://github.com/microsoft/microsoft-pdb/blob/master/include/cvinfo.h#L2521 seems like it works, but I am not quite sure that's the whole picture. I haven't had any luck in narrow down a more representative test case from what I'm getting when running across our codebase here, so figured it best to just post an issue to see what you thought.

All the examples that deal with the TPI (type information) stream are not fully complete yet.
Loading the TPI stream works, but it is up to the user code (the example) to interpret the data correctly.
Since there are a ton of different types, not all of them are understood yet and the code will simply assert.
Should be issue to add support for LF_IVBCLASS, since its layout is documented in the MS repo you linked to.

Turns out this LF_IVBCLASS issue also needed to be fixed for the examples to be able to run on the chrome.dll.pdb in issue https://github.com/MolecularMatters/raw_pdb/issues/32
The changes are on this branch:
https://github.com/lukekasz/raw_pdb/tree/chrome-dll-pdb-fixes
I will open a PR once with the changes once I've done some additional testing on others PDBs. Feel free to test it yourself :-)

Yeah, that branch works fine for my test case here.

This issue should be resolved due to the recent changes/fixes.


Weird phrasing

You're saying the same thing twice:
The exceptions are US Government Cloud Community (GCC) and Teams free. Shifts isn't available in Office 365 US Government or Teams free offerings.

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

ID: 58ea9573-59b1-1499-fb83-517d0ee0f034
Version Independent ID: bf98f739-ff51-0b90-dbc5-c594d3dacecd
Content: Manage the Shifts app for your organization in Microsoft Teams - Microsoft Teams
Content Source: Teams/expand-teams-across-your-org/shifts/manage-the-shifts-app-for-your-organization-in-teams.md
Service: msteams
GitHub Login: @kenwith
Microsoft Alias: v-lanac

@Magheno Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@Magheno thank you for reaching out and helping improve MS Docs. I'm not finding that phrasing in the article so I think it's been fixed in the interim. Please confirm and let me know.

This has indeed already been changed by LanaChin on 10 december.

@scanum this can be closed thank you.

@Magheno Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


Status site should use cloudinary images

In the current version of our site, we display images from our "website-static" repository. However, this is not an ideal solution as it requires us to manually upload images to the repository. Instead, we have images stored in Cloudinary, which are automatically uploaded to the platform. It would be better to use these images instead of the ones from our repository.

Issue Description:  In Status site currently we are using images from github repo(website-static) to display images in the site. My task is to replace those images with cloudinary images. But the problem is /tasks API return the assignee name(username) only and cloudinary api get the image by user id.
https://res.cloudinary.com/realdevsquad/image/upload/w_200,h_200/profile/XAF7rSUvk4p0d098qWYS/syvexswtmz6hx7nghrs4
https://res.cloudinary.com/realdevsquad/image/upload/w_200,h_200/profile/< USER ID >/< FILE NAME >
Solution 1:
Solution Description:  We can add a new field in /tasks API response to return the user id of the assignee. So that we can use that user id to get the image from cloudinary.
Cons:  We need to add a new field in /tasks API response.
Solution 2:
Solution Description:  We can call /users API to get the user id of the assignee by username. Then we can use that user id to get the image from cloudinary.
Cons:  We need to call /users API to get the user id of the assignee.


Fix/skip benchmark documentation

Skip benchmark for PR with documentation label
Trigger workflow when PR is labeled or unlabeled

Codecov Report

Merging #880 (dec10f2) into main (786f51a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #880   +/-   ##
=======================================
  Coverage   53.31%   53.31%
=======================================
  Files          72       72
  Lines        2144     2144
  Branches       62       62
=======================================
  Hits         1143     1143
  Misses       1001     1001

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 786f51a...dec10f2. Read the comment docs.

Should we only run benchmarks when there is a benchmark label attached?

closing this due to inactivity  please reopen when you work on it again


How to download those videos only with subtitles (no auto-gen)?

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2023.07.06 (update instructions) or later (specify commit)
[X] I've searched known issues and the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
I'd like to download those video clips only with subtitles (not auto-gen subtitles). Any quick methods? Thanks.
Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

--write-subs

--write-subs

this flag does not prevent those video clips without subtitles from being downloaded.

ah, I misunderstood your question. Try --match-filter subtitles

have you tried this ever? it doesn't really work here.

Give example URLs

--match-filter requested_subtitles

yes, changing --match-filter subtitles to --match-filter requested_subtitles made it. @pukkandan


added autonomous-hr-chatbot agent

added to agents list > autonomous-hr-chatbot
added to articles list>  'Creating a (mostly) Autonomous HR Assistant with ChatGPT and LangChain’s Agents and Tools'. The article was 'boosted' on medium and has 500+ claps.

Suer interesting combo, thanks for doing and sharing it @stepanogil


FeatureRequest: compilerOptions

Could you please add the ability to change the compilerOptions values for the TypeScript language or explain how someone else could do it?
https://stackoverflow.com/questions/40545329/property-includes-does-not-exist-on-type-string

The conversation at that stackoverflow link does not look like it's about Monaco Editor or Blazor at all. Trying to understand, I can imagine that you may want to write TypeScript in Monaco Editor and want the auto-completion to obey different rules than the ones it does. Is this what you mean?

I want to be able to modify the compilerOptions object.  The BlazorMonaco control is showing me a syntax error where the includes method in called.
(foo as string[]).includes("bar")

This is not an issue about BlazorMonaco. It's about the pre-configured TypeScript language rules in Monaco Editor. Monaco Editor supports you to register your custom language and rules. BlazorMonaco does not have support for registering languages yet. But you can register your custom language on JavaScript and use it via its name in BlazorMonaco.
You can keep track of BlazorMonaco's support for registering custom languages in the issue at #26


Cannot be installed in qBraid since python version is backdated.

While installing the package qc-grader in qBraid system, I get the error stating that the package requires a different Python: 3.9.18 not in '>=3.10'
Can we update the python requirements for this package?

Did you find any way to resolve this issue ?

@khushi707  Not really. qBraid system is very glitchy. I used a python virtualenv instead. That built fairly easily.


Show coordinates in multiple formats

Description
PR to add a new Jetpack Compose sample "Show coordinates in multiple formats" in Edit and Manage Data category.
Links and Data
Sample Epic: runtime/kotlin/issues/2571
What To Review

Compose files and ViewModel files

How to Test

Run the app to test the coordinate updates on map tapped or updating the text fields.
I would suggest to tap the map at a location to obtain a coordinate. You can copy this coordinate and tap on a different location. Updating the text field using your copied coordinate should update the map graphic to the previews point.

@hud10837 Thanks for the constructive review, I always really appreciate improving samples to meet standards and expectations. With the move to use Compose I'm sure there will be a significant understanding to do.
I've introduced a MessageDialogViewModel as a property of the MapViewModel which I'm not sure goes agains't any guidelines. To me I see the MessageDialog component to be heavily used by samples as an approach to log errors/display messages, and I didn't see the value of handling the dismiss and show functionality as part of each sample. Instead it would be better off if it was it's own ViewModel as part of the samples-lib component.
I've added in the feedback you provided and ready for your re-review.

Thanks @hud10837  for the review! Added in the MapViewState changes and a onQuerySubmit on a enter key event. Ready for your re-review :)


Coupons and Discounts

Is there a way to add a field for coupons/discounts?

Anybody have an update on this?


Call useNuxtApp two times in pinia store inside useAsyncData - Nuxt context instance error

Environment

Operating System: Linux
Node Version:     v16.20.0
Nuxt Version:     3.7.2
CLI Version:      3.8.3
Nitro Version:    2.6.3
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      modules, nitro, runtimeConfig
Runtime Modules<EMAIL_ADDRESS>Build Modules:

Reproduction
https://stackblitz.com/edit/github-bwuqrs
Describe the bug
In my personal project, I have to do two requests on the server side. For this, I was using useAsyncData, making one request, and after it, doing another with the data of the previous request.
it worked normally when I was using direct axios service. However, when I created a plugin for $api and injected it in the nuxt context, the second request started to throw an error: A composable that requires access to the Nuxt instance was called outside of a plugin, Nuxt hook, Nuxt middleware, or Vue setup function.
I do these requests inside pinia store, calling useNuxtApp().$api inside of the store, for each request.
Example of useAsyncData:
await useAsyncData('initStore', async () => {
  if (process.server) {
    const settingsStore = useSettingsStore();
   // Change condition to works
    if (true) {
      await settingsStore.get();
      await settingsStore.get();
    } else {
      console.log('No error');
      await Promise.allSettled([settingsStore.get(), settingsStore.get()]);
    }
  }
});

Pinia store:
export const useSettingsStore = defineStore('settingsStore', {
  state: () => ({}),
  actions: {
    async get() {
      try {
        const { $api } = useNuxtApp();
        console.log('$api passed');
      } catch (err) {
        console.log('error inside catch', err);
      }
    },
  },
});

Do I have to instantiate useNuxtApp inside useAsyncData and pass it to actions inside pinia? Why the second request is throwing this error? Is there a solution for that?
Ps.: If I do both requests at the same time, It works normally, the nuxt context inside pinia works.
Additional context
No response
Logs
Error: [nuxt] A composable that requires access to the Nuxt instance was called outside of a plugin, Nuxt hook, Nuxt middleware, or Vue setup function. This is probably not a Nuxt bug. Find out more at `https://nuxt.com/docs/guide/concepts/auto-imports#using-vue-and-nuxt-composables`.

Yes, this is an issue with the Nuxt pinia integration. You either need to use nuxtApp.runWithContext, or can raise a feature request to support transforming with async context within pinia.
You might also try enabling experimental.asyncContext to see if that makes a difference for you.


Compilation warning with Xcode 7 beta 6.

Compilation warning with Xcode 7 beta 6,
/Pods/MMProgressHUD/Source/MMProgressHUDViewController.m:81:1: Conflicting return type in implementation of 'supportedInterfaceOrientations': 'UIInterfaceOrientationMask' (aka 'enum UIInterfaceOrientationMask') vs 'NSUInteger' (aka 'unsigned int')

This should be resolved in the latest release: 0.3.2


[bug]: Edge Case Stuck Payment

During MPP tests and blinded paths I came across another edge case which would lead to stuck payment which would always relaunch on every startup and never resolve itself.
When registering a payment attempt we need to make sure we register a payment attempt only if we also manifested this new state on the corresponding channel. So in other words we need to make the SendPayment attempt and the registering of the attempt atomic.
Otherwise the payment might never make it to the peer and we never relaunch this payment attempt however the payment is still marked as INFLIGHT with the control tower.
Logfile output for this particular case:
The payment is launched:
2024-12-07 23:06:16.375 [DBG] CRTR: Attempt 1208 for payment 24426b8028f15c8310c608d957b18148ec4ef4c2d8b360f998667d3d72330be3 successfully sent to switch, route:<PHONE_NUMBER>447104 (1002204 mSAT) -> 0 (0 mSAT) -> 0 (0 mSAT), cltv 1355
2024-12-07 23:06:16.375 [DBG] CRTR: Collecting result for attempt 1208 in payment 24426b8028f15c8310c608d957b18148ec4ef4c2d8b360f998667d3d72330be3
2024-12-07 23:06:16.375 [DBG] HSWC: ChannelLink(5601e8ab0a9ab32fde02b7e73571da64aad3848b8ca59b21cea327e15fe44cf7:0): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=1208)->(Chan ID=993:1:0, HTLC ID=214)
2024-12-07 23:06:16.375 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending UpdateAddHTLC(chan_id=f74ce45fe127a3ce219ba58c8b84d3aa64da7135e7b702de2fb39a0aabe80156, id=214, amt=1002204 mSAT, expiry=1355, hash=24426b8028f15c8310c608d957b18148ec4ef4c2d8b360f998667d3d72330be3, blinding_point=, custom_records=map[106823:[0]]) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739

Then I abort the LND daemon:
2024-12-07 23:06:16.397 [ERR] CRTR: Error collecting result for attempt 1205 in payment 24426b8028f15c8310c608d957b18148ec4ef4c2d8b360f998667d3d72330be3: htlcswitch shutting down
2024-12-07 23:06:16.397 [DBG] CRTR: Result collected for attempt 1205 in payment 24426b8028f15c8310c608d957b18148ec4ef4c2d8b360f998667d3d72330be3
2024-12-07 23:06:16.397 [ERR] CRTR: Error collecting result for attempt 1207 in payment 24426b8028f15c8310c608d957b18148ec4ef4c2d8b360f998667d3d72330be3: htlcswitch shutting down
2024-12-07 23:06:16.397 [DBG] CRTR: Result collected for attempt 1207 in payment 24426b8028f15c8310c608d957b18148ec4ef4c2d8b360f998667d3d72330be3
2024-12-07 23:06:16.397 [ERR] CRTR: Error collecting result for attempt 1204 in payment 24426b8028f15c8310c608d957b18148ec4ef4c2d8b360f998667d3d72330be3: htlcswitch shutting down
2024-12-07 23:06:16.397 [DBG] CRTR: Result collected for attempt 1204 in payment 24426b8028f15c8310c608d957b18148ec4ef4c2d8b360f998667d3d72330be3
2024-12-07 23:06:16.397 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Received UpdateFailHTLC(chan_id=f74ce45fe127a3ce219ba58c8b84d3aa64da7135e7b702de2fb39a0aabe80156, id=212, reason=f8fdbbc86efdee4b79be17489b9b6f409c56eeb2d59b4945d18fef33cff416659cfb7aa4c37adf7788fc45763a78a4600243e097ba277c38dde8c54d70ffbef79ce1d753a00db0c4ec487990f8b1498e0d32d85077eee6b9daa7224f0a68527d6b2635c3add1e99e79164df216f52f0b642c33391b5ad8684e29bbef3c797ce612a88eea8984610fe15f802b6b3d0f9b38a8cac5f003d612ce316bb4d63db040b3388b1acc18586308ae7d8d114a435196759252eab2811ccca0ed1a35f0be558be5d65f0e9bcb722ab438f289525df4653e5cd448038c5b912c95552eb48820ca7a0b1ccd549e1c60bdd5832462f1d53bdea152d7315b0a47016f9353603cb250093940053c1076ddc4c87c3ca2f8a9c119e3c9fd6478e18a23e07b6ba15f4648439c1d) from 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739
2024-12-07 23:06:16.402 [ERR] HSWC: ChannelLink(5601e8ab0a9ab32fde02b7e73571da64aad3848b8ca59b21cea327e15fe44cf7:0): failing link: unable to update commitment: received quit signal with error: internal error
2024-12-07 23:06:16.402 [ERR] HSWC: ChannelLink(5601e8ab0a9ab32fde02b7e73571da64aad3848b8ca59b21cea327e15fe44cf7:0): link failed, exiting htlcManager
2024-12-07 23:06:16.402 [INF] HSWC: ChannelLink(5601e8ab0a9ab32fde02b7e73571da64aad3848b8ca59b21cea327e15fe44cf7:0): exited
2024-12-07 23:06:16.402 [ERR] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): unable to send msg to remote peer: peer exiting
2024-12-07 23:06:16.402 [DBG] PEER: Peer(034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c): Sending Error(chan_id=f74ce45fe127a3ce219ba58c8b84d3aa64da7135e7b702de2fb39a0aabe80156, err=internal error) to 034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c@<IP_ADDRESS>:9739

as seen above one msg fails to be flushed to the wire, thats very likely the msg from the above Sending UpdateAddHTLC msg.
Now this payment is marked as INFLIGHT (because the htlc was never marked as failed or settled) which has the side effect of the payment always relaunching its resolver during startup.
2024-12-07 23:29:28.367 [INF] CRTR: Resuming payment 24426b8028f15c8310c608d957b18148ec4ef4c2d8b360f998667d3d72330be3
2024-12-07 23:29:28.367 [INF] DISC: Authenticated Gossiper starting
2024-12-07 23:29:28.367 [INF] NTFN: New block epoch subscription
2024-12-07 23:29:28.370 [INF] INVC: InvoiceRegistry starting...
2024-12-07 23:29:28.370 [DBG] DISC: Requesting online notification for peer=0327cb365db2601f42eca18744da82e7a79a2d7af0fba5d8b80f7f461d26745376
2024-12-07 23:29:28.370 [DBG] DISC: Requesting online notification for peer=034d11a4129c8c73856c41d0c5afb5108a635ba852ead2ca2a253b01534638bd2c
2024-12-07 23:29:28.370 [INF] NTFN: New block epoch subscription
2024-12-07 23:29:28.370 [DBG] INVC: Adding 0 pending invoices to the expiry watcher
2024-12-07 23:29:28.370 [DBG] INVC: InvoiceRegistry started
2024-12-07 23:29:28.370 [INF] HSWC: Onion processor starting
2024-12-07 23:29:28.370 [DBG] DISC: New block: height=1128, hash=6247c67ce49f0f0423366772d16dd53c76a4752b6e7a29bb293e8b4f6974baff
2024-12-07 23:29:28.376 [INF] NTFN: New block epoch subscription
2024-12-07 23:29:28.376 [INF] NANN: Channel Status Manager starting
2024-12-07 23:29:28.377 [INF] CHFT: ChannelEventStore starting...
2024-12-07 23:29:28.378 [INF] CHFT: Adding 2 channels to event store
2024-12-07 23:29:28.378 [DBG] CHFT: ChannelEventStore started
2024-12-07 23:29:28.378 [INF] CHBU: chanbackup.SubSwapper starting
....
2024-12-07 23:29:28.382 [INF] CRTR: Resuming HTLC attempt 1208 for payment 24426b8028f15c8310c608d957b18148ec4ef4c2d8b360f998667d3d72330be3

Additionally it would be very beneficial to have a rationale why this peer msg is not called in sync:
https://github.com/lightningnetwork/lnd/blob/fb429d658be919c2ecfcd8ac5ebd1c2c223feff8/htlcswitch/link.go#L1764


Fix bug: TiSpark Catalog has 10-20s delay

What problem does this PR solve?
close https://github.com/pingcap/tispark/issues/1083
TiSpark Catalog has 10-20s delay, because tispark refresh catalog every 10 seconds.
What is changed and how it works?
GetTable and GetDatabase works as follows:

get latest schema version from TiKV (2 RPC, getTimeStamp from PD & getSchemaVersion from TiKV)
check schema in cache(memory) and TiKV
if schema version in cache == that in TiKV, return data from cache
if schema version in cache != that in TiKV, refresh catalog in cache

Check List
Tests

Unit test

Related changes

Need to cherry-pick to the release branch
Need to be included in the release note

/run-all-tests mode=full

/run-all-tests mode=full

/run-all-tests mode=full

/run-all-tests mode=full


[IR] accommodate preIR and IR deployments side by side

Description of change

Fixes https://github.com/meroxa/product/issues/544
Type of change

[x]  New feature
[ ]  Bug fix
[ ]  Refactor
[ ]  Documentation

How was this tested?

[x]  Unit Tests
[ ]  Tested in staging
[ ]  Tested in minikube

Demo

before
after

Additional references

Documentation updated

I tested the pre IR and IR code paths for go apps.  Test results pending for py and js.


Cvp 3273 bump tools

Bumping tools to combination of latest supported versions

@Allda please review and merge if ok with you. Thanks


Swist 2.0

I get compile errors on Xcode 7.1.  Are there going to be any updates to make it swift 2.0 compatible?

https://github.com/ayanonagon/Polyglot/pull/15 :tada:


[WebAPI] TC dev for AudioParams nominal range for Chromium 52

Impacted tests(approved): new 1, update 0, delete 0
Unit test platform: Crosswalk for Android 22.52.557.0
Unit test result summary: pass 0, fail 1, block 0
https://crosswalk-project.org/jira/browse/CTS-1862

@Honry PTAL, Thanks a lot~

@Honry I have modified the code, ptal, thanks!

LGTM


Watch no work after change css

hi all
i try laravel-mix now in webpack.mix.js i write
mix.combine([     'resources/assets/css/lib/datatables-net/datatables.min.css',     'resources/assets/css/separate/vendor/datatables-net.min.css',     'resources/assets/css/lib/bootstrap-sweetalert/sweetalert.css',     'resources/assets/css/separate/vendor/sweet-alert-animations.min.css',     'resources/assets/css/separate/vendor/lobipanel.css',     'resources/assets/css/lib/jqueryui/jquery-ui.min.css',     'resources/assets/css/separate/pages/widgets.min.css',     'resources/assets/css/lib/font-awesome/font-awesome.min.css',     'resources/assets/css/lib/bootstrap/bootstrap.min.css',     'resources/assets/css/separate/vendor/bootstrap-select/bootstrap-select.min.css',     'resources/assets/css/separate/vendor/bootstrap-daterangepicker.min.css',     'resources/assets/css/main.css',     'resources/assets/css/custom.css' ],'public/css/default.css')
then i run npm run watch
i changed custom.css  but watch not detect any changed file.
any problem from my code or i missing something?
thanks

That's expected behavior right now, since anything passed to mix.combine() will be triggered after your main Webpack bundle compiles. In this case, you're not changing any of your Webpack entry files, so nothing happens.

I just pushed a commit that will watch these files for you. It'll be tagged soon.


Kie server test improvement for Oracle RAC

Sometimes tests failed on Oracle RAC database due wrong id sequence caused by creating process instances.

+1, going to merge this now


Submit form component doesn't support nested components

Nested components don't seem to be supported for Submit. Or am I using this wrong?
# IconCheck.ex
defmodule AppWeb.Components.Base.Icons.IconCheck do
  use Surface.Component

  prop class, :string, default: "h-6 w-6"

  def render(assigns) do
    ~H"""
    <svg xmlns="http://www.w3.org/2000/svg" class={{ @class }} fill="none" viewBox="0 0 24 24" stroke="currentColor">
      <path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M5 13l4 4L19 7" />
    </svg>
    """
  end
end

# A live component with form
# ... other stuff. Aliased `IconCheck`
<Submit>
  Save
  <IconCheck :if={{ !@is_success }} />
</Submit>

Stacktrace
[error] #PID<0.987.0> running AppWeb.Endpoint (connection #PID<0.985.0>, stream id 1) terminated
Server: localhost:4000 (http)
Request: GET <INTENTIONALLY_OMITTED>
** (exit) an exception was raised:
    ** (ArgumentError) cannot convert component AppWeb.Components.Base.Icons.IconCheck with id nil to HTML.

A component must always be returned directly as part of a LiveView template.

For example, this is not allowed:

    <%= content_tag :div do %>
      <%= live_component @socket, SomeComponent %>
    <% end %>

That's because the component is inside `content_tag`. However, this works:

    <div>
      <%= live_component @socket, SomeComponent %>
    </div>

Components are also allowed inside Elixir's special forms, such as
`if`, `for`, `case`, and friends.

    <%= for item <- items do %>
      <%= live_component @socket, SomeComponent, id: item %>
    <% end %>

However, using other module functions such as `Enum`, will not work:

    <%= Enum.map(items, fn item -> %>
      <%= live_component @socket, SomeComponent, id: item %>
    <% end %>

        (phoenix_live_view 0.15.5) lib/phoenix_live_view/engine.ex:20: Phoenix.HTML.Safe.Phoenix.LiveView.Component.to_iodata/1
        (phoenix_live_view 0.15.5) lib/phoenix_live_view/engine.ex:139: Phoenix.HTML.Safe.Phoenix.LiveView.Rendered.to_iodata/3
        (phoenix_html 2.14.3) lib/phoenix_html.ex:154: Phoenix.HTML.html_escape/1
        (phoenix_html 2.14.3) lib/phoenix_html/tag.ex:89: Phoenix.HTML.Tag.content_tag/3
        (surface 0.3.2) lib/surface/components/form/submit.ex:43: anonymous fn/3 in Surface.Components.Form.Submit.render/1
        (phoenix_live_view 0.15.5) lib/phoenix_live_view/diff.ex:356: Phoenix.LiveView.Diff.traverse/6
        (phoenix_live_view 0.15.5) lib/phoenix_live_view/diff.ex:430: anonymous fn/4 in Phoenix.LiveView.Diff.traverse_dynamic/6
        (elixir 1.11.4) lib/enum.ex:2193: Enum."-reduce/3-lists^foldl/2-0-"/3
        (phoenix_live_view 0.15.5) lib/phoenix_live_view/diff.ex:356: Phoenix.LiveView.Diff.traverse/6
        (phoenix_live_view 0.15.5) lib/phoenix_live_view/diff.ex:430: anonymous fn/4 in Phoenix.LiveView.Diff.traverse_dynamic/6
        (elixir 1.11.4) lib/enum.ex:2193: Enum."-reduce/3-lists^foldl/2-0-"/3
        (phoenix_live_view 0.15.5) lib/phoenix_live_view/diff.ex:356: Phoenix.LiveView.Diff.traverse/6
        (phoenix_live_view 0.15.5) lib/phoenix_live_view/diff.ex:430: anonymous fn/4 in Phoenix.LiveView.Diff.traverse_dynamic/6
        (elixir 1.11.4) lib/enum.ex:2193: Enum."-reduce/3-lists^foldl/2-0-"/3
        (phoenix_live_view 0.15.5) lib/phoenix_live_view/diff.ex:356: Phoenix.LiveView.Diff.traverse/6
        (phoenix_live_view 0.15.5) lib/phoenix_live_view/diff.ex:430: anonymous fn/4 in Phoenix.LiveView.Diff.traverse_dynamic/6
        (elixir 1.11.4) lib/enum.ex:2193: Enum."-reduce/3-lists^foldl/2-0-"/3
        (phoenix_live_view 0.15.5) lib/phoenix_live_view/diff.ex:356: Phoenix.LiveView.Diff.traverse/6
        (phoenix_live_view 0.15.5) lib/phoenix_live_view/diff.ex:430: anonymous fn/4 in Phoenix.LiveView.Diff.traverse_dynamic/6
        (elixir 1.11.4) lib/enum.ex:2193: Enum."-reduce/3-lists^foldl/2-0-"/3

@imsekun it has been fixed with #344 on the master branch. Could you please check if it works? We'll release 0.4 of Surface soon.

@Malian My bad for the duplicate issue, I wasn't able to use the right keywords.
Works perfectly!


Docs should refer to Kubeflow user guide for deploying the TFJob operrator

Delete docs that explain how to use helm to deploy the TFJob CRD.
We don't have the resources to support and maintain helm packages.
We want to focus on just using ksonnet to deploy Kubeflow.

Fix #239

This change is

I think we could disable the coveralls comment function, it is useless for us.


Dev 3224 update contract request assignee rest api

#3224

Coverage increased (+0.03%) to 89.396% when pulling c9ff251e353155e554d00221312be91e09323d0f on dev-3224-update-contract-request-assignee-rest-api into aeb7a81abf6b49155e14b319c48871bb1c624d03 on develop.


Allow env variables to be passed to PigCliHook

We need a way to be able to specify environment variables at runtime. Specifically, we want to set the heap space available to our pig cli. We would ordinarily do this by prepending these variables before the pig executable, for example:
PIG_OPTS="$PIG_OPTS -Xmx512M" pig -useHCatalog script.pig

The subprocess.Popen method allows you to pass environment variables in, so I figured that would be the best interface. You can just define a dict in your connection option that maps environment variable names to values. At runtime, the hook will add these to the existing environment variables from os.environ and make them available when the pig command is executed.

Coverage increased (+0.02%) to 66.898% when pulling af3d586887fd0098a63c1ebadf2fb8ce1f65b0f6 on adambom:patch-1 into 7dca6636dd1b41ac40f920d51e0443977b8cff11 on airbnb:master.

@adambom, I think it is an interesting idea, but I can imagine a case where you would want to do this on a per task basis as opposed to defining it at the connection level, do you agree?
I guess I could see both a default to use for all pig tasks (But I think this should really be set at the cluster level) and a task level value.
In this case, we could add the env param in the operator to be passed to the hook at init time.

@artwr I'm not opposed to exposing it to the tasks, but you could make the same argument for pig_options. For example, you might want to run different pig operators in different mapreduce queues. If you think there's value in exposing env in the kwargs to PigOperator, we should consider exposing pig_options as well.
Regarding global defaults, we run airflow on a massive hadoop deployment, and changing cluster defaults is not really an option. The folks that maintain pig set default heap space very high (2GB) to account for extreme cases where users would otherwise run out of memory. Our environment is a lot more controlled, and we want to try and optimize memory usage for all PigCliOperators, but having a task level value is still probably a good idea.

Coverage decreased (-0.03%) to 66.845% when pulling 886aa3512633a412394446aea7711739fb98f926 on adambom:patch-1 into 7dca6636dd1b41ac40f920d51e0443977b8cff11 on airbnb:master.

Coverage decreased (-0.03%) to 66.845% when pulling 886aa3512633a412394446aea7711739fb98f926 on adambom:patch-1 into 7dca6636dd1b41ac40f920d51e0443977b8cff11 on airbnb:master.

@adambom, that sounds like a good idea too. Would you be ok amending the PR for this?
I would be happy to review it since I wrote the original.

Sure. Will try and get it done today.

@artwr How do you think task-level pig properties should extend the connection level properties? pig properties is currently specified as a space delimited string, so it's not like we can just extend a dict of key/values. Should task level pig properties just override the connection properties or should we just append the task properties to the end of the connection properties?

@adambom Sorry I dropped the ball on this. I think appending the task properties at the end should be enough since in Java, the later option supersedes the earlier one. Let me know if you are still willing to work on it, or I could probably get it across the finish line if you prefer.

Closing. No updates from submitter.


Rspec "let" in random order

Hello !
I'm having a little random problem that happens sometimes. Test fail randomly. Object are created in a different order.
Here is a quick example of my code :
context 'has two devices' do
  let!(:device1) { create :device, user: user1 }
  let!(:device2) { create :device, user: user2 }

  subject { get :index, store_id: store_id, page: page, format: :json }

  it do
    expect(subject.body).to include_json(
      devices: [
        {
          id: device1.id,
          model: device1.device_model,
          udid: device1.udid,
          adid: device1.adid,
          imei: device1.imei,
          user_id: device1.user_id,
          blacklisted: false
        },
        {
          id: device2.id,
          blacklisted: true
        }
      ]
    )
  end
end

Sometimes it will return
    Failure/Error: expect(response.body).to include_json(

                 json atom at path "devices/0/id" is not equal to expected value:

                   expected: 19379
                        got: 19380

                 json atom at path "devices/0/udid" is not equal to expected value:

                   expected: "bo350bvpxingx18pxgs6r44wwbff2zgiqovwyq4m"
                        got: "2htpr26rjs9hec5qlxxxbzad9a239ezrgrhjcp1a"

                 json atom at path "devices/0/user_id" is not equal to expected value:

                   expected: 93958
                        got: 93959

                 json atom at path "devices/0/blacklisted" is not equal to expected value:

                   expected: false
                        got: true

                 json atom at path "devices/1/id" is not equal to expected value:

                   expected: 19380
                        got: 19379

                 json atom at path "devices/1/blacklisted" is not equal to expected value:

                   expected: true
                        got: false

Sometimes
.

Finished in 0.73745 seconds (files took 0.28197 seconds to load)
1 example, 0 failures

I'm using json_expectations but the problem is the same if I parse the json with JSON.parse(subject.body) and match key with .first object and .last object.
Sometimes device1 is created after device2 so my test fail because of info that not match. It's random.
Maybe my test are not well written or it's an rspec feature.
I'm using rspec-core 3.2.3 and ruby ruby 2.2.2p95 (2015-04-13 revision 50295)

Your spec isn't necessarily saying that the let! statements run in a random order. Under the hood they setup before calls in the order defined. What is likely happening is your database is returning the results in a different order. Not all databases return things in default id order. Depending on which Rails version you are on, Rails may not be setting a default order on the query either.
I suspect if you added order(:id) to your controller query it would resolve this problem. Unless your expectation is to always get results in id order, this spec seems to have exposed an order dependent issue with json_expectations.

I would also caution you that this style of spec writing will be very confusing to other. I often re-order my let statements alphabetically. If for some reason you had different names than "device1" and "device2" it is likely that my simple re-ordering would break specs. Which would really confuse me.
I suggest instead to use a style like this:
let(:device1) { build(:device, user: user1) }
let(:device2) { build(:device, user: user2) }

before do
  device1.save!
  device2.save!
  expect(
    device1.id
  ).to (be < device2.id), "Precondition Failed: device2 id is before device1"
end

This makes the order dependent and clear.

Whats happening here is your results are not being returned in id order, this is actually not guaranteed by your database unless you manually order your query. You can use match_array to match regardless of ordering or order your query in your app.

Thanks a lot both of you for your comments. It's true I didn't specify any order in my request.
I will also be careful to organize my let alphabetically. Thanks Aaron for the tips.
It's sometimes hard to get proper examples. Relishapp is great for that but most of the times the examples you found on relishapp and on internet are very simple and doesn't reflect bigger test.
I know I'm out of thread but if you have any resources for me to follow, OS project to read and maybe contribute, I'm more than open.

We've found trivial examples are best to demonstrate features, because bigger tests are dependant on the domain, in this case dependent on both Rails and your own app specific instance, there are worked examples around for testing Rails apps but they usually suffer from being trivial app domains!


Duplicate log entries when using stix2elevator as library (as it imports stix2validator)

The issue is due to configuring the logger object when a module is loaded (stix2validator.py is used as module by stix2elevator)
logging.basicConfig(stream=sys.stdout, level=logging.INFO, format='%(message)s')
logger = logging.getLogger(__name__)

This is not correct, and while the logger object can be created at module loading time, customizations should be moved inside the main function.
Here the original issue: https://github.com/oasis-open/cti-stix-elevator/issues/293

Fixed by the referenced PR


Mockups approval

green light given during the last sprint meeting, there is a minor change already requested to paul but nothing major.


Org-mode should link correctly info:title

When I add a link to an org file, in the completion I don't see info: type of link then I type myself the info:elisp link with a description.
What did you expect to happen?
I expect org-mode links me to Emacs Lisp info manual. It's the normal Emacs behavior.
What actually happened?
Org-mode tries to create a new heading in the current file. Maybe I need to load some org module.
Additional details:

Link to your private config, if possible
https://github.com/kcurtet/doom.d

Include screenshots/casts of your issue

Replace key sequences in your steps to reproduce, use commands
C-c C-l org-link

System information:
https://pastebin.com/ucdEYJV9

To activate support for info links you need to activate the ol-info org module:
(after! org
  (add-to-list 'org-modules 'ol-info))

Since this is a configuration issue and not a Doom one I will close this, but feel free to follow up here.


updates(osp): update text content

Description
update text content. heighlight osp string in bold and italic
Why
content has been changes
Issue
NA
Checklist
Please delete options that are not relevant.

[x] I have followed the contributing guidelines
[x] I have performed a self-review of my own code
[x] I have successfully tested my changes locally

@jjeroch if you give the go I'd merge the pr


Extension of Neural ODE tutorial to SDE case is very slow

I am not sure if this is a ComponentArrays issue.
I tried extending the DiffEqFlux tutorial to an SDE, and the performance took a huge knock, each iteration of training takes around 2 minutes on my machine.
using ComponentArrays
using OrdinaryDiffEq
using Plots
using UnPack

using DiffEqFlux: sciml_train
using Flux: glorot_uniform, ADAM
using Optim: LBFGS
using DifferentialEquations
using DiffEqSensitivity

u0 = Float32[2.; 0.]
datasize = 30
tspan = (0.0f0, 1.5f0)

dense_layer(in, out) = ComponentArray(W=glorot_uniform(out, in), b=zeros(out))

function trueODEfunc(du, u, p, t)
    true_A = [-0.1 2.0; -2.0 -0.1]
    du .= ((u.^3)'true_A)'
end
t = range(tspan[1], tspan[2], length = datasize)
trueprob = ODEProblem(trueODEfunc, u0, tspan)
ode_data = Array(solve(trueprob, Tsit5(), saveat = t)) .+ (randn(2, datasize) .* 0.3)

function dudt(u, p, t)
    # display(typeof(p))
    @unpack L1, L2 = p.p
    return L2.W * tanh.(L1.W * u.^3 .+ L1.b) .+ L2.b
end
function noisy(u,p,t)
    @unpack noise_params = p
    return noise_params .* u .* 0.1
end

prob = SDEProblem(dudt, noisy, u0, tspan)

layers = (L1=dense_layer(2, 50), L2=dense_layer(50, 2))
θ = ComponentArray(u=u0, p=( p = layers, noise_params = rand(2)))
predict_n_ode(θ) = Array(solve(prob, Tsit5(), u0=θ.u, p=θ.p, saveat=t, sensealg=BacksolveAdjoint()))

function loss_n_ode(θ)
    pred = predict_n_ode(θ)
    loss = sum(abs2, ode_data .- pred)
    return loss, pred
end
loss_n_ode(θ)

cb = function (θ, loss, pred; doplot=false)
    display(loss)
    # plot current prediction against data
    pl = scatter(t, ode_data[1,:], label = "data")
    scatter!(pl, t, pred[1,:], label = "prediction")
    display(plot(pl))
    return false
end

cb(θ, loss_n_ode(θ)...)

data = Iterators.repeated((), 1000)

res1 = sciml_train(loss_n_ode, θ, ADAM(0.05); cb=cb, maxiters=100)
cb(res1.minimizer, loss_n_ode(res1.minimizer)...; doplot=true)

res2 = sciml_train(loss_n_ode, res1.minimizer, LBFGS(); cb=cb)
cb(res2.minimizer, loss_n_ode(res2.minimizer)...; doplot=true)

Probably not a ComponentArrays issue.  See https://github.com/SciML/DiffEqFlux.jl/issues/312

I'm not sure either. I would certainly expect them to be slower, but I don't have a good feel for how much slower as I haven't played around much with neural SDEs. ComponentArray support for Zygote just started a few days ago after a conversation on Slack with Chris Rackaucas. It was only vaguely on my radar before that as my day-to-day work doesn't really involve neural network type stuff. But building the same thing in a "flat" way (i.e. no ComponentArrays) and comparing is usually the best bet to see whether ComponentArrays are causing the slow down. They shouldn't be, but every once in a while I find something that needs a method overload in order to avoid a slower fallback.
Side note: θ should be defined as a ComponentArray{Float32}. I realized last night that it wasn't this way in the docs, so I updated them. The change probably hasn't been pushed through the build process yet.


Suggestions for Integrating Docker Installation Steps into Daytona Installation Steps

Hello, I would like to make a suggestion. Considering that Docker needs to be installed on the operating system before using Daytona, and that the installation of Docker usually takes some time, could the steps for installing Docker be integrated into the installation of Daytona? This way, users would only need to execute the command "(curl -sf -L https://download.daytona.io/daytona/install.sh | sudo bash) && daytona server -y && daytona" to complete all installation steps, further reducing the time required to set up the environment.

@TS35 I like the idea, we can add a prompt to ask the user if they want the script to install Docker as well.


Force xtask wrapper to use stable toolchain

Since we're cross-compiling via the wrapper script, we need it to ignore the CARGO_BUILD_TARGET environment variable. Otherwise it will also get cross-compiled and then it can't run.
Checklist

[x] Ran cargo xtask fixup for formatting and linting
[ ] Modified all relevant documentation
[ ] Updated CHANGELOG.md per "Keep a Changelog" format
[ ] Added tests covering any code changes

For posterity, this didn't work :sad:


csgo rcon controls not working

Hi There,
I'm having trouble with rcon controls for !cs maps or !cs map . However quit seems to work fine.

Hi,
could go more into detail e.g. posting a screenshot or an error message?
!cs maps should list all available maps on the server. If that is not working, there might be an issue with the conntection to the server itself.
!cs map must be followed by the map name you want to switch to e.g. !cs map de_mirage

I just checked to bot features maps and map with a server running on version <IP_ADDRESS> and it works on my site. What do you get back when you call !cs status ?


HIGH: [Polish] Add support for image-only (no alt text) inline image Markdown

Problem:
In HIGH: [Polish] Add support for inline image Markdown we added support for  ![alt text](imageURL) syntax, which is great!  However, that presumes you always have "alt text", which in my experience, is rare.
Solution:
Add support for !(imageURL), which doesn't use any alt text.

@kidroca can you comment here and/or self-assign?

I'm not able to self-assign myself to this issue, but this comment should allow anyone with access to assign me

The pull request (PR) for expensify-common is ready for review:

PR #676 on Expensify/common

However, the existing bug with live-markdown and MD image, gets in the way here as well. While trying to submit a PR for NewDot to allow QA testing of the Markdown (MD) image shorthand syntax, I encountered the same bug (detailed in #39275)  using the latest main branch. This bug prevents the usage of images with shorthand syntax. Although I confirmed the feature works with an older commit, submitting a PR based on it isn't feasible because PRs have to be based on a recent version of main.
The tricky part is the resolution to the live markdown preview issue depends on a fix included in my expensify-common PR (the on at the top), as described herehttps://github.com/Expensify/App/issues/39275#issuecomment-2027753450.
Since testing this fix directly in NewDot is impossible ATM, I recommend integrating the expensify-common update into the live markdown preview PR. This combined approach appears to be the most effective solution:

Issue #39275 on Expensify/App
Live Markdown PR #256

PRs are ready for review:

https://github.com/Expensify/expensify-common/pull/676
https://github.com/Expensify/App/pull/39759

The PR for expensify-common has been successfully merged: https://github.com/Expensify/expensify-common/pull/676.
The corresponding PR for NewDot has become redundant, as it only involved updating the expensify-common version. A newer version including my changes and additional updates has already been merged into main: https://github.com/Expensify/App/pull/39759

One potential issue is that we usually use the NewDot PR to test changes, but this PR automatically closed when I synced it with main, as there were no remaining differences.
I've provided detailed testing instructions in the PR, which QA can use to validate the new feature.

Can we close this?

Can we close this?

Yes


add result handler for gateway result callback

This adds a few other fixes I found along the way:


autogenerated config warning is not correct

The config warning states that the keybind for kitty is SUPER+RETURN, but keybind is SUPER+Q

fixed in 454d0d3f9f6b8f68a6bb59463ae3227f7ddce691
thanks


⚠ Jenkins Plugins Artifactory has degraded performance

In 6abb763, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1259 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 7a2b2ca after 12 minutes.


Why so many lifetimes?

I'm sorry for bothering you, but I'm interacting with cargo library a lot and I can't help but wonder - why is there so many complications in the API? There are many lifetimes, RefCells (that make stuff !Sync etc.
 Why not just Arc<Mutex<_>> stuff instead of playing with RefCells? I don't think there's much performance wins to be had in the code that will always be blocked on IO anyway. Is there something I am missing here?

I think the answer here is "Alex thought it was fun to avoid RefCell and Mutex", there's no real technical motivation.

Is it something that can be easily fixed? If I submitted a PR would it get accepted? It does affect my code quite a lot, because many times I do want to store these structs and it bubble up in the code.

To be honest it's not really something that's ever been considered I think. It would be a pretty massive and major refactoring of Cargo, so I suspect this would not be easily fixed. I would encourage discussing with the cargo team (e.g. not just me) about this before proceeding.

https://internals.rust-lang.org/ ?

What's the deal with interning? https://github.com/rust-lang/cargo/blob/59f50abc4ca3b9cc4594e6601f84107d2d454e34/src/cargo/core/interning.rs#L17

We don't just intern strings, we do the same for package_ids #6332 and source_ids #6342. The structure of interning has changed, but the justification is the same as when it was introduced https://github.com/rust-lang/cargo/pull/5121 (I used blame in the github UI to find that PR).
There are 3 reasons interning is grate:

A significant percent of all the strings cargo makes are the string "serde". keeping only one copy of each string significantly reduces memory usage.
Having deduplicated a string, EQ is O(1) not O(n), and does not require a cache miss.
An interned string has O(1) clone, no allocations no O(n) copy and no cache miss. The Resolver needs to copy most of its internals for each of the crates in the dependency tree, so clone speed really matters.

BTW, what project are you working on?

Oh. So it's a perf optimization. I wonder if this really makes a difference. I mean... how many dependencies people have etc.? Anyway - thanks for answer.
I am working on https://github.com/crev-dev

Considering cargo-the-library is provided as-is, a major refactor like this would likely be driven by the needs of cargo-the-bin, rather than users of the API.  It'll also likely be done opportunistically as other feature development is happening.  As such, I'm going to go ahead and close this out.  If there is a reason for us to reconsider, let us know!