Large bundle size

I am trying to build a background scene using Threlte with SvelteKit Static Site Generation.
I am getting a chunk that is about 800~kB in size.
> vite build

vite v4.0.1 building SSR bundle for production...
✓ 178 modules transformed.
Unknown output options: sourcemapIgnoreList. Allowed options: amd, assetFileNames, banner, chunkFileNames, compact, dir, dynamicImportFunction, dynamicImportInCjs, entryFileNames, esModule, experimentalMinChunkSize, exports, extend, externalImportAssertions, externalLiveBindings, file, footer, format, freeze, generatedCode, globals, hoistTransitiveImports, indent, inlineDynamicImports, interop, intro, manualChunks, minifyInternalExports, name, namespaceToStringTag, noConflict, outro, paths, plugins, preferConst, preserveModules, preserveModulesRoot, sanitizeFileName, sourcemap, sourcemapBaseUrl, sourcemapExcludeSources, sourcemapFile, sourcemapPathTransform, strict, systemNullSetters, validate

vite v4.0.1 building for production...
✓ 178 modules transformed.
Unknown output options: sourcemapIgnoreList. Allowed options: amd, assetFileNames, banner, chunkFileNames, compact, dir, dynamicImportFunction, dynamicImportInCjs, entryFileNames, esModule, experimentalMinChunkSize, exports, extend, externalImportAssertions, externalLiveBindings, file, footer, format, freeze, generatedCode, globals, hoistTransitiveImports, indent, inlineDynamicImports, interop, intro, manualChunks, minifyInternalExports, name, namespaceToStringTag, noConflict, outro, paths, plugins, preferConst, preserveModules, preserveModulesRoot, sanitizeFileName, sourcemap, sourcemapBaseUrl, sourcemapExcludeSources, sourcemapFile, sourcemapPathTransform, strict, systemNullSetters, validate
.svelte-kit/output/client/_app/version.json                                   0.03 kB
.svelte-kit/output/client/vite-manifest.json                                  3.10 kB
.svelte-kit/output/client/_app/immutable/assets/index.ca7f1f30.css            0.04 kB │ gzip:   0.06 kB
.svelte-kit/output/client/_app/immutable/assets/0.3e221d88.css                5.34 kB │ gzip:   1.71 kB
.svelte-kit/output/client/_app/immutable/nodes/0.638a2a38.js                  0.55 kB │ gzip:   0.37 kB
.svelte-kit/output/client/_app/immutable/chunks/preload-helper.41c905a7.js    0.76 kB │ gzip:   0.48 kB
.svelte-kit/output/client/_app/immutable/chunks/index.c6e6613d.js             0.82 kB │ gzip:   0.50 kB
.svelte-kit/output/client/_app/immutable/nodes/1.1d5582db.js                  0.99 kB │ gzip:   0.58 kB
.svelte-kit/output/client/_app/immutable/chunks/singletons.46fe4679.js        2.45 kB │ gzip:   1.23 kB
.svelte-kit/output/client/_app/immutable/entry/app.fa93fc0f.js                4.91 kB │ gzip:   1.85 kB
.svelte-kit/output/client/_app/immutable/chunks/index.e70780ae.js            10.89 kB │ gzip:   4.27 kB
.svelte-kit/output/client/_app/immutable/entry/start.2ed2750d.js             23.88 kB │ gzip:   9.48 kB
.svelte-kit/output/client/_app/immutable/nodes/2.77648294.js                 53.38 kB │ gzip:  17.34 kB
.svelte-kit/output/client/_app/immutable/chunks/index.f6c80858.js           854.25 kB │ gzip: 242.57 kB

(!) Some chunks are larger than 500 kBs after minification. Consider:
- Using dynamic import() to code-split the application
- Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/guide/en/#outputmanualchunks
- Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.
.svelte-kit/output/server/vite-manifest.json                    2.20 kB
.svelte-kit/output/server/entries/pages/_layout.server.ts.js    0.05 kB
.svelte-kit/output/server/internal.js                           0.19 kB
.svelte-kit/output/server/entries/pages/_layout.svelte.js       0.25 kB
.svelte-kit/output/server/entries/fallbacks/error.svelte.js     0.79 kB
.svelte-kit/output/server/chunks/index.js                       2.36 kB
.svelte-kit/output/server/chunks/internal.js                    5.32 kB
.svelte-kit/output/server/chunks/index2.js                      6.26 kB
.svelte-kit/output/server/entries/pages/_page.svelte.js        18.76 kB
.svelte-kit/output/server/index.js                             99.89 kB
.svelte-kit/output/server/chunks/index3.js                    257.27 kB

Run npm run preview to preview your production build locally.

> Using @sveltejs/adapter-static
  Wrote site to "build"
  ✔ done

Weirdly enough,  removing the following from vite.config, still results in a working build (but inflates index3.js to 1.4mB)
	ssr: {
		noExternal: ['three']
	}

The index.f6c80858.js chunk contains what looks like entirerity of threejs, with most notably shaders for unused materials and other things. Is there something that can be done?

Which version of Threlte are you using? I wonder if this is because of how <T> is implemented...

Which version of Threlte are you using? I wonder if this is because of how <T> is implemented...

'@theatre/core':
    specifier: ^0.6.1
    version: 0.6.1
  '@theatre/studio':
    specifier: ^0.6.1
    version: 0.6.1<EMAIL_ADDRESS>  '@threlte/core':
    specifier: next
    version: 6.0.0-next.7
  '@threlte/extras':
    specifier: next
    version<EMAIL_ADDRESS>  '@threlte/preprocess':
    specifier: ^0.0.2
    version: 0.0.2
    ```

It looks correct to me, you are on next - the version numbers aren't synchronized, you need to look at the specifier. I'm not sure if and how tree shaking is implemented in Threlte.
Maybe its good to do a minimal test with a fresh project where only one class of ThreeJS is used with <T>?
BTW I notice you are using Theatre here; I'm working on a new release of @threlte/theatre and if you have time to give feedback, feel free to drop a comment in this PR: https://github.com/threlte/threlte/pull/380

Maybe its good to do a minimal test with a fresh project where only one class of ThreeJS is used with <T>?

I will come back with an MRE asap.

BTW I notice you are using Theatre here; I'm working on a new release of @threlte/theatre and if you have time to give feedback, feel free to drop a comment in this PR: #380

That looks awesome but still is WIP? I had a theatre use case in mind but theatre itself lacks the ability to visualize Sheet-specific data as of now, and I have to repurpose that, but I will definitely get back to you on this.

I will come back with an MRE asap.

Great!

That looks awesome but still is WIP? I had a theatre use case in mind but theatre itself lacks the ability to visualize Sheet-specific data as of now, and I have to repurpose that, but I will definitely get back to you on this.

Its a WIP but in late stages; we hope to merge it to next soon (in the coming week or two). Can you elaborate a bit about your usecase? What data do you want to visualize?


T35591 Read block definition from resource files

Taking as reference commits from #147
Notable changes:

The loading occurs in the new block catalog, not in the UI.
Changed the file matching to use case-insensitive "globbing".
Sync'ing things like tooltips (description field) that have been updated in main.

There are more blocks that can be ported. I'm finding missing ones like "Await scene ready". I'm making sure we don't miss anything in the port. The if/else can't be ported as-is unless we split them into 2 blocks.


commit bower components

Status: Ready to Merge
Reviewers: @donnielrt @marlowpayne @mikenikles
Changes

committing bower components

Todos:

[ ] Engineer +1

How to Test

See if bower_components exists in root directory

@stewartyu, would you be able to re-open this PR against the develop branch? I'd rather not merge anything to master unless we're deploying something.

@stewartyu can we open this and the other PR against develop please? That way we can combine all the changes into a release and deploy it.


Growth spike/add remaining UI elements

Summary
Add the remaining UI components to the health dashboard, as described in the board card:
Peding UI elements:
The ok/successfull green SVG for the success scenarios.
The overal score header Problems big red alert Circle
Implement the buttons for CTA and learn more.
Add ability to accordion component to dont be able to expand if it does not contain elements and not even show the chevron.
Ticket Link
https://community.mattermost.com/boards/workspace/7dqusmf8stn3dens5ckhyatbdo/boattb15z9fr4m85etwrdekkduh/v37ny5c5eafnk3dypexwzagip7a/cg98h6gnnsprx5b8nf8f4cdycyh
Related Pull Requests
Screenshots

Release Note
NONE

@michelengelen @michaelgamble @mkraft gentle ping on this one :)

@furqanmlk I've added you early to this PR, as requested, however this one will probably be merged into the main feature branch without QA review approval.


Can I run this on a remote machine and access it through the browser instead of running it with Electron?

I've been assisting a company in putting together the demo of a DApp that needs to be presented to potential investors.
The DApp was designed for Ehereum, but we cannot rely on the network at the moment due to the ongoing changes.
I plan to use Ganache as a temporary solution just to be able to run such application and showcase the project.
It would be best if I could have the Ganache UI running on a remote server so that I people presenting the app prototype don't have to worry about any laptop-based setup.
I know I could just run the Ganache CLI as a background process on a remote machine, but then people presenting the app prototype would not be able to easily see the list of accounts, the ETH balance, etc., through a browser.
Since this is in essence an SPA, wouldn't it be possible to start it without Electron and just serve it from a server?

Not yet, but we are planning on implementing this.


Add deployment option to instack-ironic-deployment

Adds a new --deploy-nodes option, which deploys a heat stack
containing some baremetal servers, with some initial minimal
logic which proves the ironic config injection works.
Note the template will probably need updating for the top-level
metadata key when the real discovery data is injected, this
expects dummy data, added like this:
ironic node-update  add extra/configdrive_metadata='{"hardware": {"foo": "bar"}}'

Tested this; works; thanks.


Safe mutability test

I'm writing a small bit of infrastructure to cache values derived from keys of Immutable.Record objects, which for invalidation relies on the fact that mutation results in a distinct object. These cached values are actually getters on the prototype of objects that inherit from Immutable.Record, so they're accessed just like non-derived properties. I'd like to ensure, though, that the cached values aren't accidentally updated while mutating such an object using withMutations. In order to do this, I need a reliable way to determine whether the object is either currently mutable, or has been somehow altered. Currently, I'm doing this with the wasAltered, which works fine for my purposes, but I noticed that it isn't officially documented anywhere. Could this become part of the official API? Or, alternatively, could something like isMutable be added to Immutable.Record objects?

Closing this since it's aging, but caching utilities is still an open area of discussion


Write me an essay about yoga

I'm ok, thanks.

This is a page for issues related to the StableLM project, view the readme to learn how to test-drive the model.


[bug] Check extra73 Fail: Message omits bucket name

The textFail message appears to indicate that there was an access issue but the bucket name is left off or omitted.
Example: "Access Denied Trying to Get Public Access Block for "
If I had to guess, it looks like I'm seeing the output from line 43 in check_extra73, where $bucket isn't defined yet.

Hi @urazie1, thanks for the heads up. First of all make sure you are using the latest version of Prowler from master since line 43 in checks/check_extra73 is empty. Then run prowler as bash -x ./prowler -c extra73 and see what is the result of the variable $ALL_BUCKETS_LIST. It seems to be empty in your case.

Hi @urazie1, thanks for the heads up. First of all make sure you are using the latest version of Prowler from master since line 43 in checks/check_extra73 is empty. Then run prowler as bash -x ./prowler -c extra73 and see what is the result of the variable $ALL_BUCKETS_LIST. It seems to be empty in your case.

I was pulling the latest container from the master branch prior to running, so we got that error using the latest in the master branch (I must have been looking at an older file version when filing the bug report though).
Specifically, the line is now on 48 (from the Sept 2, 2020 commit)
textFail "Access Denied Trying to get Public Access Block for $bucket"
If I'm understanding right, I only see $bucket declared further down in the For loop (line 76), which could cause the blank name in the message.

I was pulling the latest container from the master branch prior to running, so we got that error using the latest in the master branch (I must have been looking at an older file version when filing the bug report though).
Specifically, the line is now on 48 (from the Sept 2, 2020 commit)
textFail "Access Denied Trying to get Public Access Block for $bucket"
If I'm understanding right, I only see $bucket declared further down in the For loop (line 76), which could cause the blank name in the message.

Prowler gets the list of existing buckets in variable ALL_BUCKETS_LIST from line 66 the uses $bucket to query each one. If you run prowler with bash -x as mentioned before you will see the result of that aws s3api list-buckets command and if the error is somehow related to it.

Prowler gets the list of existing buckets in variable ALL_BUCKETS_LIST from line 66 the uses $bucket to query each one. If you run prowler with bash -x as mentioned before you will see the result of that aws s3api list-buckets command and if the error is somehow related to it.

@toniblyx I see what he is talking about, I raised https://github.com/toniblyx/prowler/pull/724 to fix

@toniblyx I see what he is talking about, I raised https://github.com/toniblyx/prowler/pull/724 to fix

Ok, it was a matter of the message itself. This is adressed now. Thanks!

Ok, it was a matter of the message itself. This is adressed now. Thanks!


Return the correct RPL from GDT::add_entry()

Now the RPL of the returning selector is determined from whether the given descriptor has its DPL_RING_3 set.

Thank you!

Published together with #151 as v0.10.2.


Rewrite api loader

To be compatible with Metarhia api, example: https://github.com/metarhia/Example/tree/master/application/api

Here is pure node.js loader implementation: https://github.com/metatech-university/NodeJS-Pure/pull/3

Fixes in RPC call from ws transport.
Refs: https://github.com/metatech-university/NodeJS-Pure/pull/4

Please assign this issue to me


Set up parser for gdc2xena

Closes #16
Needs a rebase once #24 is merged.

Is this on top of #24 ? If so, let's work #24 out, then rebase this PR. da4c41fe15d8cefd570b357d5f799cae6ea9aaff looks fine. But I'll take another look after #24 and rebase.

#24 merged. Please rebase as you want.

Rebased.

The code for this PR went with the last PR itself, and the reason being the last commit I added. Thus, I am closing this PR.


How to extract the trajectory of the joint angle of the model

I would like to ask, after the model is trained, how to extract the joint angle,  can see the trajectory of the joint angle during the movement.thanks.

what do you mean by extract the joint angles? Do you mean record the motion produced by the simulation and export that into a file?

Yes，I want to compare it with the reference data. Can you tell me?

@skylbc I also I want to compare it with the reference data. Did you manage how?


[Bug] Can't read notifications from multiple characteristics in Android

I am having issues reading multiple characteristics using the Android version of the library. I ran the same code in UWP and it is working fine.
Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

[ ] iOS
[x] Android
[ ] UWP
[ ] .NET Standard

Version of Library
6.2.6
Version of OS(s) listed above with issue
Android 9, API 28
Steps to Reproduce

Find the first service
Write to settings characteristic in this service
Enable Notifications in another characteristic in same service
Find second service
Enable notifications and read characteristic from this service

Expected Behavior
Both characteristics on which notifications are enabled should show notifications
Actual Behavior
I can get the response after writing to the first characteristic saying the settings are properly set
but  only the characteristic from the second service shows notifications

Please send a reproducible sample.

Getting the first characteristic
//getting the first service
IGattService firstService = await scanResult.Device.GetKnownService(Guid.Parse(SensorUUIDs.UUID_POL_SERV));
                            var settingsChar = await firstService.GetKnownCharacteristics(new Guid[] { Guid.Parse(SensorUUIDs.UUID_POL_SETI) });
//sending some data which gives settings to this characteristic
await WriteSettingsChar(settingsChar);

//adding and removed this line gives the same result, I tried it in case this characteristic was notifying
//await settingsChar.DisableNotifications();

//getting the other service
var secondService = await scanResult.Device.GetKnownService(Guid.Parse(SensorUUIDs.UUID_HRA_SERV));
//getting the second characteristic
var secondChar = await firstService.GetKnownCharacteristics(new Guid[] { Guid.Parse(SensorUUIDs.UUID_HRA_DATA) });
//getting the notification characteristic from the first service
var firstChar = await secondService.GetKnownCharacteristics(new Guid[] { Guid.Parse(SensorUUIDs.UUID_POL_DATA) });
//tried both with and without MainThread from Xamarin Essentials, same result
MainThread.BeginInvokeOnMainThread(async () =>
{
   //enable the notifications of first characteristic
    await secondChar.EnableNotifications();
   //tried both with and without delay
    await Task.Delay(200);
   //enable notifications of second characteristic
    await firstChar.EnableNotifications();
 });
//FirstCharInfo is a string property that is supposed to be updated and is bound to the XAML
//this line fires indicating that the activity characteristic can notify
FirstCharInfo = $"can notify: {firstChar.CanNotify()}";
await Task.Delay(200);
//subscribe to the first notification, this one is supposed to do some processing
//and update the FirstCharInfo property
firstChar.WhenNotificationReceived().Subscribe(async result => { await OnFirstNoteification(result); });
await Task.Delay(200);
//subscribe to the second notification
//this one is getting some data and updating another property
secondChar.WhenNotificationReceived().Subscribe(async result => await OnSecondNoteification(result));

Any update on this?

@ArifSohaib you tell me?  Have you done any debugging?  If you are just expecting me to fix this for you, you've come to the wrong place.  You'll have to wait until I have time/energy to look into it myself.

I have found code examples on how to do it but they are all in Android Java https://stackoverflow.com/questions/36539473/how-to-enable-multiple-ble-characteristic-notifications-on-xamarin-android which lists two solutions that I can't figure out how to map to C# and I found out that older versions of Android only allow 1 notification but my current minimum version(API 21) allows 15 notifications based on BTA_GATTC_NOTIF_REG_MAX.


bramWriter write strb==0 in GenericAxi4LiteSlave

prevent request become read when the write strb is zero

Good catch, this has been fixed for BlueAXIBRAM, but not in this case.


Changing tests to prevent tests from intermittently timing out

#234 mentions the intermittent failure of the test anchorMarkdownHeadings/makes pretty slugs on Travis-CI.

Have you been able to reproduce these failures by any chance?

I've been able to replicate the operator: fail failure by reducing the timeout to single digits.
I saw the following log that fails: https://travis-ci.org/nodejs/new.nodejs.org/builds/85753833
Locally I get the following:
  not ok 1 test timed out after 5ms
    ---
      operator: fail
    ...

This error is slightly different - test exited without ending instead of  test timed out ....
I'm hoping that specifying the number of plans will resolve the unexpected ending.

Okey, lets give it a try and keep our eyes open for these failures..

This can probably be reverted as https://github.com/nodejs/new.nodejs.org/pull/265 is merged


Treating added objects as obstacles?

❓ Questions and Help
When I run ./build/viewer data/habitat-test-scenes/skokloster-castle.glb --enable-physics and add objects using o. The agent does not treat the added object as an obstacle and goes right through it. Is there a way such that the agent can stop when it comes in contact with the added objects? The object that I am adding to the scene is nested_box.glb and nested_box.physics_properties.json looks as follows:
{
    "render mesh": "nested_box.glb",
    "join collision meshes": true,
    "use bounding box for collision": true
}

Hey @naruarjun, there are two ways to do this depending on whether or not you would like to run physics simulation and move the obstacle often.

You want a kinematic solution that does not require simulation and the obstacle will remain un-moving somewhere. In this case you can bake the obstacle into the NavMesh by setting its motion type to STATIC and recomputing the NavMesh:

object_id = sim.add_object(template_id)
sim.set_object_motion_type( habitat_sim.physics.MotionType::STATIC, object_id)
navmesh_settings = habitat_sim.NavMeshSettings()
navmesh_settings.set_defaults()
sim.recompute_navmesh(sim.pathfinder, navmesh_settings, include_static_objects=True)

You want the obstacle to block an embodied, fully simulated agent. You can attach the agent to a physical body, then control the agent with velocity or force commands. Note: the NavMesh will not be respected in this case.

#attach agent to simulated rigid object
agent_object_id = sim.add_object(body_object_template_id, attachment_node=agent_node)
obstacle_object_id = sim.add_object(obstacle_object_template_id)

#to control the agent with velocity_control, manipulate this struct
vel_control = sim.get_object_velocity_control(agent_object_id)

#or control the agent with force
sim.apply_force(...
sim.apply_torque(...

Hi @aclegg3 , I tried your first suggestion on the already provided banana object. When is use include_static_objects=True flag, I get segmentation fault. But it does not give any error if include_static_objects=False. What might be causing this?
Thanks in advance

@shivanshpatel35 can you provide the code you are running and console output when crashing?
Tests are working with "data/scene_datasets/habitat-test-scenes/van-gogh-room.glb" and the banana object on my side.

@aclegg3 Hi, it was my fault. I missed enabling physics in api here. Now I am not getting any error.
I am inserting object in habitat-api using the following code snippet
object_id = env._sim._sim.add_object(0)
env._sim._sim.set_translation(object_position, object_id)
env._sim._sim.set_object_motion_type(habitat_sim.physics.MotionType.STATIC, object_id)
navmesh_settings = habitat_sim.NavMeshSettings()
navmesh_settings.set_defaults()
env._sim._sim.recompute_navmesh(env._sim._sim.pathfinder, navmesh_settings, include_static_objects=True)

After this when I try to check navigability at the object_position using env._sim._sim.pathfinder.is_navigable(object_position), it returns True. I was expecting it to return False

Hey @aclegg3, this has solved my issue. Thank you for the help.

After this when I try to check navigability at the object_position using env._sim._sim.pathfinder.is_navigable(object_position), it returns True

Depending on the object and object_position, this may be expected as the top of the object can be navigable.  Any flat-ish surface will be navigable, however, the agent won't be able to climb up onto the object from the floor as long as the object is sufficiently tall.

Depending on the object and object_position, this may be expected as the top of the object can be navigable. Any flat-ish surface will be navigable, however, the agent won't be able to climb up onto the object from the floor as long as the object is sufficiently tall.

That clears my doubt, thanks! We can close the issue now.

Is there a way to treat included objects with kinematic motion type as obstacles for the agent. I added locobot object body to the agent (from this comment) but it still goes right through it. I want to control both the object and the agent but wouldn't want them to collide with each other or other objects. Thanks!

@nnsriram97 you may want to open a new issue if my answer here isn't sufficient since your question is somewhat tangential to the original question.
From what I understand:

You want to control the object kinematically by setting it's transform explicitly.
You want to control the agent via the navmesh.
You want the agent to collide with the object via the navmesh.
You want to the object to collide with the agent and other objects (preventing you from setting it's state?)

Sounds like there are a few contradictions here. A kinematically controlled object has no collision response (it has infinite mass and can only be moved by manual state setting), so you would need to manually reject state updates that cause a collision.
If you are doing that anyway, you may add a collision object to the agent (as discussed in the Habitat-Sim for Interaction tutorial from our ECCV 2020 tutorial series) and then also reject state setting which causes the agent to collide with an object, the stage, or anything else. You could modify the collision filter function (also discussed in that tutorial) to do this.
Alternatively you could consider dynamically controlling the object and the agent to get collision responses without the navmesh (you could still use the navmesh to constrain target locations as in the tutorial).
If the object will not move often (e.g. you are placing a new piece of furniture) you could try a hybrid approach where you set the object to STATIC once it is placed and recompute the navmesh with that placement. You can follow the tutorial to see how you might place the object in the scene in a valid location.


how Rectified Adam effect?

author make some experiments in other dataset??

There paper has experimental results.

i know ,i only ask you about yourself make experiment？？
---Original---
From: "Somshubra<EMAIL_ADDRESS>Date: Wed, Aug 21, 2019 20:10 PM
To<EMAIL_ADDRESS>Cc: "daixiangzi"543826458<EMAIL_ADDRESS>Subject: Re: [titu1994/keras_rectified_adam] how Rectified Adam effect? (#1)
There paper has experimental results.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I tried it out on CIFAR 10 just to see if the optimizer works. Didn't test for full training.

i think you should try to train all data,its  effect could be exaggerated
---Original---
From: "Somshubra<EMAIL_ADDRESS>Date: Wed, Aug 21, 2019 20:35 PM
To<EMAIL_ADDRESS>Cc: "daixiangzi"543826458<EMAIL_ADDRESS>Subject: Re: [titu1994/keras_rectified_adam] how Rectified Adam effect? (#1)
I tried it out on CIFAR 10 just to see if the optimizer works. Didn't test for full training.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I don't have the time or the compute. You are free to try it.

ok
---Original---
From: "Somshubra<EMAIL_ADDRESS>Date: Wed, Aug 21, 2019 20:56 PM
To<EMAIL_ADDRESS>Cc: "daixiangzi"543826458<EMAIL_ADDRESS>Subject: Re: [titu1994/keras_rectified_adam] how Rectified Adam effect? (#1)
I don't have the time or the compute. You are free to try it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Node.js example status fix #177

Fixes #177
The nodejs example was sending the text status from flow.post to express. Replaced with a regular expression to test for good values.
If the callback was changed to send back null on success we could follow the callback(err, results) convention and do something like this:
app.post('/upload', multipartMiddleware, function(req, res) {
  flow.post(req, function(error, filename, original_filename, identifier) {
    console.log('POST', error, original_filename, identifier);
    if (ACCESS_CONTROLL_ALLOW_ORIGIN) {
      res.header("Access-Control-Allow-Origin", "*");
    }
    res.status(error ? 500 : 200).send();
  });
});

@AidasK : Even though there is no testcase, given that two other PR proposed a very similar change and it's only about samples, I'd assume it's safe to merge.

It's already merged from other PR


GHC 8.0.2 has directory-1.3

Whoops!  I already fixed this in https://github.com/Gabriel439/Haskell-Turtle-Library/commit/f6eff07e197feeec3f3d22658886398c933b6150 before getting to your PR in my inbox

this can be closed @alanz


Linker error after updating to Xamarin.Facebook.CoreKit.iOS 5.0.2

After updating Xamarin.Facebook.CoreKit.iOS to 5.0.2 and Xamarin.Facebook.LoginKit.iOS, Xamarin.Facebook.MarketingKit.iOS, Xamarin.Facebook.PlacesKit.iOS, and Xamarin.Facebook.ShareKit.iOS to version 4.40.0 I started receiving this linker error:
Error MT5211: Native linking failed, undefined Objective-C class: FBSDKSystemAccountStoreAdapter. The symbol '_OBJC_CLASS_$_FBSDKSystemAccountStoreAdapter' could not be found in any of the libraries or frameworks linked with your application.
I tried cleaning, rebuilding, deleting bin and obj folders, and deleting and reinstalling the above Nuget packages, but received the same error.
After deleting and reinstalling these Nuget packages I also noticed that version 4.39.1 of Xamarin.Facebook.CoreKit.iOS is downloaded first, instead of 5.0.2, and then later it reports that it needs to be updated, despite just having been downloaded. Not sure if this is related, but it seemed odd.
In the meantime I reverted to the last versions of all the above packages and this solved the problem with iOS not building.
If you need any more info I'd be happy to provide it.
Thanks for your time.

@ashleypringle we had an internal problem when pushing the iOS bits to NuGet and only CoreKit made it to NuGet. Now the other sdks are live now, try updating the NuGets and the problem must be fixed. Hope this helps you!

I've the same behavior on 4.40 and I can also confirm that for 5.0.2 enum has only one value - Browser..

The LoginBehavior enum only has one value, Browser, for me as well. LoginBehavior.Native is no longer available. Also, the LoginButton class no longer has a ReadPermissions property.
Are LoginBehavior.Browser and ReadPermissions no longer necessary? According to this link they are still required: https://github.com/xamarin/FacebookComponents/blob/master/Facebook.iOS/docs/LoginKit/Details.md


Enable horizontal scrolling in pre elements

The default content width is rather narrow, which is reasonable for text, but tends to wrap the code blocks.
Before:

After:

Thanks!


Feat/add docker push

关联的Issues (Related Issues)

close
改动 (Proposed Changes)

附注 (Additional Info)

自查清单 (Checklist)
在你认为本 PR 满足被审阅的标准之前，需要确保 / Before you mark the PR ready for review, please make sure that:

[ ] 符合Venus项目管理规范中关于PR的相关标准 / The PR follows the PR standards set out in the Venus project management guidelines
[ ] 具有清晰明确的commit message / All commits have a clear commit message.
[ ] 包含相关的的测试用例或者不需要新增测试用例 / This PR has tests for new functionality or change in behaviour or not need to add new tests.
[ ] 包含相关的的指南以及文档或者不需要新增文档 / This PR has updated usage guidelines and documentation or not need
[ ] 通过必要的检查项 / All checks are green

Codecov Report

Merging #161 (3166d86) into master (02a0689) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #161   +/-   ##
=======================================
  Coverage   44.56%   44.56%
=======================================
  Files          39       39
  Lines        4364     4364
=======================================
  Hits         1945     1945
  Misses       2189     2189
  Partials      230      230

Flag
Coverage Δ

unittests
44.56% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Enhance Login and Signup Form Overlay with Cross Button for Closure and Center Alignment

Description: The current login and signup form overlays lack essential features for usability and aesthetics. They need the following adjustments:
To Reproduce

Navigate to the login or signup section.
Click on the login or signup button to open the respective form.
Note that there is no cross button to close the form.
Ensure that the form is not centered on the page.

Expected behavior

Each form (login and signup) should include a cross button to close it.
The forms should be centered on the page for improved accessibility and aesthetic appeal.

Screenshots

Additional Context
Both the login and signup form overlays need enhancements. Adding a cross button for closure and centering the forms on the page will enhance user experience and visual consistency.
Please assign me this issue.

There is no existing issue specifically addressing the addition of a cross button for closure on the login and signup forms. The current issues listed focus on different aspects like UI/UX enhancements and login signup designs and their alignment also. But this issue also pertains specifically to improving  user experience with a cross button and centered alignment for the login and signup forms.

Kindly assign me this.

hey , we already have cross button on the homepage sign in , since people are already working on Ui , this is a part of UI and hence will be fixed by them , kindly ask if they need any help !

i cannot assign this issue to you , it will cause a lot of conflicts in future


Update required for the dev dependencies

I would love to use youre package, but I can't install it, because, it is not compatible my nestjs common library.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@nestjs/common
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nestjs-plugins/nestjs-nats-streaming-transport
npm ERR!   @nestjs-plugins/nestjs-nats-streaming-transport@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /home/kisstamasj/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/kisstamasj/.npm/_logs/2022-10-18T21_05_44_452Z-debug-0.log

I would appreciate your help.

Version updated for NestJS 9


Error: db.add is not a function

Hello and thank you for the library.
Im trying to follow the tutorial but Im getting an error:
Error: db.add is not a function
import { defineEntity, createClientDb } from '@clientdb/core';

interface Todo {
  id: string;
  title: string;
  doneAt: Date;
}

const todoEntity = defineEntity<Todo>({
  name: 'todo',
  fields: ['id', 'title', 'doneAt'],
});

const db = createClientDb([todoEntity]);

const todo = db.add(todoEntity, {
  id: 'todo-0',
  title: 'Buy milk',
  doneAt: null,
});

You can check this at this URL:
https://stackblitz.com/edit/react-ts-xk1t2c?file=App.tsx
Is the documentation outdated ?

It should be. Seems docs are outdated. Sorry about that.
const todo = db.entity(todoEntity).create({
  id: 'todo-0',
  title: 'Buy milk',
  doneAt: null,
});


fix/readme-document

close #11
I have added a detailed Readme file. Please review it. Thank you

Great work @itsmeabhishek03


Support single FASTA ReferenceSets

We need to support ReferenceSets based on a single FASTA file for CRAM support (see #928). Splitting the references by chromosome seems artificial, and will be messy if there are large numbers of contigs in an alignment (perfectly possible in non-model organisms that don't have a good reference).
This may introduce a backward incompatibility with the data repo format currently supported, so we should look carefully at what the best option is:

Only support single FASTA ReferenceSets, and provide a script to update old data repo formats to the new one;
Only support single FASTA ReferenceSets, and not worry about existing users (there may not be any not using the example data);
Support both single FASTA ReferenceSets and multi-fasta ReferenceSets.

Any thoughts @dcolligan, @diekhans?

Hm, do we have any idea of which use case is more common?  Or what the preference of the users might be?

A single fasta is most like the more common approach and it's
easy to create a single fasta from multiple fastas.
For less finished assembles, there can be tens of thousands of
scaffolds, so contig per fasta would be a big problem.
Danny Colligan<EMAIL_ADDRESS>writes:

Hm, do we have any idea of which use case is more common? Or what the
preference of the users might be?
—
Reply to this email directly or view it on GitHub.*

#829

what is the ETA on finishing this?

I'm putting it on my next week (March 28) sprint schedule

Closed by #1166.


Look Into Node Framework(s) for editor UI

The current UI works (technically) but it really isn't pretty. Adding to that, apparently the debugger coloring isn't working on at leasrt one installation. Not sure if that is because of the IMGUI code or just because of windows 10, but it is worth a look anyways.

2019/2018.3 beta have a new graph FX node blackboard system that is apparently open to hook into... but it has no documentation and we don't know exactly how well it works compared to IMGUI (....experience dictates that it literally can't be worse. lol)

I have started ripping out the internals to the blackboard used in shader graph in scriptable render pipeline... It is working beautifully and I think this is the way we want to go. Closing this as solved.


Transfers as Encounters

The transfers table has been translated into two resources.

MIMIC_Organization: each careunit is now part of an organization tree in fhir. The BIDMC organization resource is the parent resource with all careunits as children Organization resources.
Encounter_Transfers: Each transfers has been made into an Encounter resource which refrences the careunit through MIMIC_Organization and points to the main hospital encounter resource.

Currently only grabbing inpatient transfers, simplified the process

Also the careunits were added as new terminology for serviceType.

Ended up switching careunits from being stored in an Encounter resource, instead into a Location resource. The Location resources are then referenced in the main Encounter.location element.


"State of the art" testing in RxJS 5

Hi guys,
This isn't an issue with the code but rather a theoretical question on what is the "state of the art" method to test RxJS 5 code?
On this documentation page I see that there is a TestScheduler which can create stub observables given a marble syntax. As far as I understood, one can use these fake observables as inputs to test a specific operator or a whole chain of operators.
But I think most of the time I'm not interested in testing how the control flow was built up using the operator chain - instead I'd like to test the side effects of a subscription while mocking & stubbing some dependencies out to make the test faster. One such dependency is time - see my related StackOverflow question
It seems in RxJS 4 there was a way to set up a TestScheduler which you could use to set the virtual time manually. In RxJS 5 I don't find its equivalent. Do I miss something which is not documented yet?

We're in a state of huge refactor to testscheduler interface to allow various usecase sceanarios. While it is not ready yet, you still have way to setup current TestScheduler as you want to try out cases, esp. current marble-based test cases are also testing time-based dependencies as you described. In your question probably what you need is just inject testschduler, record subscription messages, and flush scheduler. If you'd like to try RxJS4-ish scheduler interface, there are 3rd party module I wrote for those purpose you can try out. So it is correct (for now) you don't see any documentation for v4-compatible test scheduler interface since there isn't thing like those yet.

Related: #1791

@kwonoj is there a way to follow up on the progress of this refactor? We want to upgrade to RxJs 5 but want to wait until the unit testing infrastructure is ready and complete.

@amoerie I don't have visibility of its status (as I'm not owning those task at this moment).
But I don't think test blocks your migration - marble-based DSL will be available in a compatible manner (will have some new syntaxes though) and just requires setting up test scheduler of your own in your code, can be gracefully migrated even after refactoring. This is way I'm doing for my codebases now.

Let's say you want to run this code without waiting 10 seconds
interval(1000).take(10).subscribe(observer);

You can use the VirtualTimeScheduler like this
let vs = new VirtualTimeScheduler(VirtualAction);
interval(1000, vs).take(10)
.subscribe(observer);
vs.flush();


added docstrings

nice to have these on the REPL so i don't have to reference the README.

Coverage remained the same at 90.485% when pulling 6e9aca17e86d775a298de769f65bdf3a858d4e7a on bjarthur:docs into 2c0304321b1def601ffecaa1282b47eb666fb948 on simonster:master.

I'd like this. Looks like it could use a rebase.

thanks tim!  tests now pass on all but nightly.
has moving this MAT.jl to JuliaIO been considered?

I thought it had perhaps been discussed, but a brief search didn't turn up the issue for me.


v8 Disassembler config in General, not Usage

The usage config for the Atomic Disassembler is in the General section instead of Usage.
Minor issue, but it will be confusing if someone goes looking for it.

I'd rather leave it in general - I want to keep the usage section strictly for machinery.


Correction for raw affiliation Cemagref, UMR ITAP, 361 Rue J.-F. Breton, 34196 Montpellier Cedex 5, France

Correction needed for raw affiliation Cemagref, UMR ITAP, 361 Rue J.-F. Breton, 34196 Montpellier Cedex 5, France
raw_affiliation_name: Cemagref, UMR ITAP, 361 Rue J.-F. Breton, 34196 Montpellier Cedex 5, France
new_rors: ;00ftatp57
previous_rors:
works_examples: W2095728494
contact: 481d7c01bb27272275149f605fcc8804:de10a0e3b76848b30d0152f90a6e0201b597 @ inrae.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-18. The new affiliations should be visible within the next 7 days.


Use chef-style comment header & modes as strings

Auto-corrected with Cookstyle
Signed-off-by: Tim Smith<EMAIL_ADDRESS>

          1 Error

:no_entry_sign:
Please include a CHANGELOG entry.

          1 Warning

:warning:
This Pull Request is probably missing tests.

  Generated by :no_entry_sign: Danger


Unhandled ProvisionedThroughputExceededException crashing Mono server

When running multiple stress tests (locally on windows and on our Mono servers) we encountered an unhandled ProvisionedThroughputExceededException when writing to our DynamoDB.
Even having a try catch around the SDK call, the exception isn't handled.
This unhandled exception seems to crash our Mono server.

AWSSDK version: <IP_ADDRESS>
.NET runtime: 4.5
Mono 4.2.1

StackTrace:
at Amazon.Runtime.Internal.HttpRequest.GetResponse() in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSSDK_DotNet35\Amazon.Runtime\Pipeline\HttpHandler\HttpWebRequestFactory.cs:line 114
  at Amazon.Runtime.Internal.HttpHandler`1.InvokeSync(IExecutionContext executionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSSDK_DotNet35\Amazon.Runtime\Pipeline\HttpHandler\HttpHandler.cs:line 84
  at Amazon.Runtime.Internal.PipelineHandler.InvokeSync(IExecutionContext executionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSSDK_DotNet35\Amazon.Runtime\Pipeline\PipelineHandler.cs:line 57
  at Amazon.Runtime.Internal.Unmarshaller.InvokeSync(IExecutionContext executionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSSDK_DotNet35\Amazon.Runtime\Pipeline\Handlers\Unmarshaller.cs:line 48
  at Amazon.Runtime.Internal.PipelineHandler.InvokeSync(IExecutionContext executionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSSDK_DotNet35\Amazon.Runtime\Pipeline\PipelineHandler.cs:line 57
  at Amazon.Runtime.Internal.ErrorHandler.InvokeSync(IExecutionContext executionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSSDK_DotNet35\Amazon.Runtime\Pipeline\ErrorHandler\ErrorHandler.cs:line 70

Can you post code that repros this issue?

Hey Pavel, thanks for your quick reply.
We basically just send the write call using the AWS SDK:
        {
            if (entity == null)
            {
                return false;
            }

            try
            {
                await Context.SaveAsync(entity).ConfigureAwait(false);
                return true;
            }
            catch (Exception e)
            {
                return false;
            }
        }

Where Context is of type: Amazon.DynamoDBv2.DataModel.DynamoDBContext
In any case, this exception should be caught by the try catch around the SDK call, shouldn't it?
Remark:
We encountered the same issue when using the
Save<T>(T value, DynamoDBOperationConfig operationConfig = null)
function of the AWS SDK.
Thanks again for looking into this!
Cheers.

Are you encountering the same un-catchable exception if using the sync methods? Can you provide the code which calls your Save method? Can you provide the simplest possible sample that reproduces this behavior consistently?

Hei Pavel,
thanks for following up.
We indeed encounter the same behavior when using the sync methods. The code looks like this:
public bool Save<T>(T entity) where T : class, new()
{
	try
	{
		using (var client = new AmazonDynamoDBClient(awsAccessKey, awsSecretKey, config))
		{
			using (var context = new DynamoDBContext(client, ContextConfig))
			{
				context.Save(entity);
			}
		}

		return true;
	}
	catch (Exception e)
	{
		//	log error
		return false;
	}
}

As Requested I gonna provide a small project with the simplest sample that reproduces this behavior as soon as possible tomorrow morning.
Thanks again for looking into this.
Cheers

Hey Pavel,
thanks for being patient.
I just put together a small project as requested.
You can find it here: https://github.com/foliba/ServiceStackIssue320
We added both versions: async and sync.
The async version reproduces our issue 100%. The sync calls in about 75% of all cases.
Thanks again for looking into this.
Cheers,
Roman

Thanks for the repo.
Running the code locally on Windows, I am able to see the exception dialog ("ProvisionedThroughputExceededException was unhandled by user code"), though this does not crash the IIS server. Is this the same behavior you are seeing?
How are you running this code on Mono?
We're not sure why this is happening yet, but one way to avoid the exception seems to be to use the client. For instance, you can replace the context.SaveAsync... call with
await client.PutItemAsync(
    context.GetTargetTable<T>().TableName,
    context.ToDocument(entity).ToAttributeMap()).ConfigureAwait(false);

Hey Pavel,
correct, we are running on Mono. Sadly this exception causes the server to crash. IIS seems to be a bit nicer here.
Thanks for the suggestion. Will communicate with our other developers and report back.
Cheers,
Roman

Hey Pavel,
Just wanted to let you know that your supposed fix works flawlessly. We deployed to our test servers some weeks ago and monitored for for a while. No uncaught exceptions anymore. ;-)
Thanks for your help! Much appreciated.
Cheers,
Roman


[QUESTION] generate json from flow ?

Is there a way to generate the Json of the created flow??

You'll need to use your own "state wrapper", just like the [https://github.com/MrBlenny/react-flow-chart/blob/master/stories/ExternalReactState.tsx](ExternalReactState Story).
You'll then be able to access your state (e.g. this.state) and turn it into a json.
Example: https://codesandbox.io/s/react-flow-chart-poc-4t8j2

ty man :')


localdns issue

localDNs hijack dns request to <IP_ADDRESS> , so , when deployed with localDNs, the document could mention set  cni.externalCIDr  in the coordinator

Fixed by https://github.com/spidernet-io/spiderpool/pull/2012
We can configure the address of localDNS in helm values, example:
helm install spiderpool -n kube-system . --set coordinator.hijackCIDR={<IP_ADDRESS>}


Quick demo video for YouTube (TikTok?)

Motivation
We want people to use this template to build stuff. So we should do our best to publicize it.
Finish Line

[ ] Punchy, short overview video of using the template to build an app? Or walking through it?

Check out this video for an example of short and punchy overview (100k+ views!!

We have the speed run!


add multiple accounts for local geth node in dev mode

Some truffle tests in the centrifuge-ethereum-contracts require multiple accounts packed with ETH for testing.
The geth node should provide per default more pre-configured accounts instead of only one for successfully running truffle tests against it.

This is a year old. I'm closing this. Likely we'll move away from truffle anyway.


insufficient privileges when talking to route53

I create an aws account with the following permission:
      - 'route53:ChangeResourceRecordSets'
      - 'route53:GetChange'
      - 'route53:ListHostedZonesByName'
      - 'route53:ListHostedZones'

then pass the account credentials to a cluster issuer this way:
          route53:
            accessKeyID: ${AWS_ACCESS_KEY_ID}
            # A secretKeyRef to a google cloud json service account
            secretAccessKeySecretRef:
              name: cert-manager-dns-credentials
              key: aws_secret_access_key

when I try to create a certificate I get this error:
I0725 20:03:07.099366       1 dns.go:101] Presenting DNS01 challenge for domain "console-openshift-console.apps.cluster-2d3c.sandbox37.opentlc.com"
I0725 20:03:07.298363       1 controller.go:198] cert-manager/controller/orders "level"=0 "msg"="syncing resource" "key"="openshift-console/console-1399319360"
E0725 20:03:07.298409       1 controller.go:215] cert-manager/controller/challenges "msg"="re-queuing item  due to error processing" "error"="Failed to determine Route 53 hosted zone ID: InvalidClientTokenId: The security token included in the request is invalid.\n\tstatus code: 403, request id: 14f60dd1-824f-4385-a236-41a85d6a1021" "key"="openshift-console/console-1399319360-0"

which suggests that the account does not have enough permissions.
I know I am not using a IAM account (I cannot in my situation), but rather a key/secret and this is not documented but it seems to be supported by the API, can you confirm?
Also what more permissions are needed?
I am using this version of cert-manager:
quay.io/jetstack/cert-manager-controller:v0.8.1
/kind question

my bad, my credentials were badly configured.


fix wrong exeption message escaping

Hello,
Current escaping of error string escape space as "\ ". This is not necessary, thus I propose to escape using saxutils escaping function that look more apropriate than the base python escape function.
Best regards

Thanks


plasma-browser-integration does not work with Firefox

Issue description
plasma-browser-integration doesn't work with Firefox
Steps to reproduce

Install plasma-browser-integration

Install Firefox

Install the plasma browser integration addon for Firefox

Technical details

system: "x86_64-linux"
host os: Linux 4.14.81, NixOS, 19.03pre159472.80738ed9dc0 (Koi)
multi-user?: no
sandbox: yes
version: nix-env (Nix) 2.2pre6526_9f99d624
channels(root): "nixpkgs-19.03pre159472.80738ed9dc0"
channels(pasquale): "nixpkgs-19.03pre153701.46651b82b87"
nixpkgs: /home/pasquale/.nix-defexpr/channels/nixpkgs

No,adding   nixpkgs.config.firefox.enablePlasmaBrowserIntegration = true; didn't solve the problem

And now it does


chore(deps): update common-dev-assets digest to 7d9cc29

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
2c92e37 -> 7d9cc29

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Bug:  issue with building when the mux/mux-player-react is installed

build issue with building after installing mux/mux-player-react @1.5.1
typescript version @4.3.5
node version 18
Tried to switch to mux-video-react @0.7.2  still the same issue

Checklist

[*] Verified whether your issue exists in the latest version Mux Element(s) release: npm install @mux/[element_name] or yarn @mux/[element_name].

(NOTE: If the issue is not occurring in the latest version, we may not resolve it.)

[*] Confirmed that this issue hasn't already been filed.

Which Mux Elements/Packages has a bug?
mux-video-react @0.7.2 and mux/mux-player-react @1.5.1
Which browser(s) are you using?
unrelated
Which operating system(s) are you using?
macOS
How are you using Mux Elements?
npm package/yarn
Describe the bug
yarn tsc, or next build  both failing
Steps To Reproduce
yarn tsc
Link to code example:
The current behavior
The expected behavior
expect to be able to build

Seems like these inline type imports may not be available prior to TS 4.5 https://www.typescriptlang.org/docs/handbook/2/modules.html#inline-type-imports

Though, we do use downlevel-dts, which should handle this, so, not sure exactly what's wrong here.

Oh, I see. For whatever reason, it's using the later syntax, i.e. dist/types/index.d.ts. It should be using dist/types-ts3.4/index.d.ts, based on the config of playback-core:
{
  "types": "dist/types-ts3.4/index.d.ts",
  "typesVersions": {
    ">=4.3.5": {
      "*": [
        "dist/types/index.d.ts"
      ]
    }
  }
}

As @luwes kindly pointed out, it could be that our version range in the typesVersions is too permissive, and I just didn't realize that when looking earlier.
@terryli0095 if you are able/get the chance, can you manually modify the package.json locally<EMAIL_ADDRESS>to be ">4.5" in the typesVersions and see if some of these errors go away?

I can confirm that the build errors go away when the typesVersion is updated to >4.5


chore: cover 100% of builder with tests

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.29%. Comparing base (b5a6c53) to head (ebdff89).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master       #8      +/-   ##
==========================================
+ Coverage   83.43%   93.29%   +9.85%
==========================================
  Files           8        8
  Lines         157      164       +7
==========================================
+ Hits          131      153      +22
+ Misses         21       11      -10
+ Partials        5        0       -5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Text data

This https://drive.google.com/file/d/1SuyUQYdizJ5RcQl-450ZOROTRS12M8i9/view?usp=sharing  is generated by the TreeView. Can I get this data as an object?
Example: https://codesandbox.io/s/admiring-cerf-gzcp9b?file=/src/plugins/TreeViewPlugin.js

You can get the editor state as JSON here: https://lexical.dev/docs/concepts/serialization#json


Inferring the Causer of an Activity

If we assume that all activity caused by a backpack user is inside backpack admin namespace (crud interface) we could add it in a middleware that checks if the route starts by backpack route prefix.
A middleware seems like something that would be too large of a scope. It would run on all requests, whether it's needed or not. But the idea with the route prefix... THAT I like...
What if we create an Observer for Activity? We can register one in our package's service provider, even if Activity is in the Spatie package. That way... when an activity is created (and only then)... we do some checks.
One way of checking would be:

if route is backpack, use the guard configured in Backpack's config
else use the guard configured in spatie config

That's if we don't have a way to get the currently-active guard... which... we should, right? Laravel should have a getGuard() on the AuthManager or something... right?

Originally posted by @tabacitu in https://github.com/Laravel-Backpack/activity-log/pull/8#discussion_r1310410449

Fixed here; 8d4fc52 (#8) 🎉


Update the downtime warning banner for the planned Easter maintenance

Might be worth someone checking those new Date(...) calls as well as me, but they are supposed to be the Wednesday before and going away at 9am on the day.

No need for a no-break space since there's no newline to cause whitespace trimming, but good thought because that has bitten us before now!


Perf variability: e2e Perf numbers

Not sure if this an actual issue or just environmental noise (e.g. network), but it is interesting that spikes appear in data from our e2e test targeting ODSP for average time across all tests for those build.  Can we see if there is some cause on the server side not?
let testData = union kind=outer database("Office Fluid Test").*ffautomation*
| where Data_testVariant == "odsp" and Event_Time >= ago(7d) and Data_testName contains "Non-Compat";
let passTest = testData
| where Data_eventName == "fluid:telemetry:Test_end" and Data_state == "passed"
| project Data_buildId, Data_testName;
let testDate = testData
| summarize max(Event_Time) by Data_buildId;
let passTestData = passTest
| join kind=inner testDate on Data_buildId
| join kind=inner testData on Data_buildId, Data_testName
| extend Build=strcat(Data_buildId, " (", format_datetime(max_Event_Time, "MM-dd HH:mm"), ")");
passTestData
| where isnotempty(Data_duration)
    and Data_eventName !startswith "fluid:telemetry:SummaryManager"
    and Data_eventName !startswith "fluid:telemetry:DeltaManager"
    and Data_eventName !startswith "fluid:telemetry:Summarizer"
    and Data_eventName !endswith "_cancel"
    and Data_eventName != "fluid:telemetry:OdspDriver:ConnectionSuccess"
    and Data_eventName != "fluid:telemetry:OdspDriver:MultipleRetries"
| summarize avg(Data_duration) by Build, Data_eventName
| summarize d=make_bag(pack(Data_eventName, avg_Data_duration)) by Build
| evaluate bag_unpack(d)
| render linechart with (xcolumn=Build)

No progress yet, keep pinging right folks :)

The most useful visualization of prod data that shows time sensitivity:

Office_Fluid_FluidRuntime_Performance
| where Event_Time > ago(30d)
| where Event_Time < ago(0d)
| where Data_eventName == "fluid:telemetry:OdspDriver:createNewFile_end"
| summarize count(), P=percentile(Data_duration, 95) by bin(Event_Time, 1h)
| where count_ > 1000
| project P, Event_Time
| render timechart

And the most useful query about our builds:

let testData = union kind=outer *ffautomation*
| where Data_testVariant == "odsp" and Event_Time >= ago(7d) and Data_testName contains "Non-Compat";
let passTest = testData
| where Data_eventName == "fluid:telemetry:Test_end" and Data_state == "passed"
| project Data_buildId, Data_testName;
let testDate = testData
| summarize max(Event_Time) by Data_buildId;
let passTestData = passTest
| join kind=inner testDate on Data_buildId
| join kind=inner testData on Data_buildId, Data_testName
| extend Build=strcat(Data_buildId, " (", format_datetime(max_Event_Time, "MM-dd HH:mm"), ")");
passTestData
| where Data_eventName == "fluid:telemetry:OdspDriver:createNewFile_end"
| where isnotempty(Data_duration)
| where Data_duration < 100000
| summarize count(), P=percentile(Data_duration, 90) by Build
| where count_ > 200
| project P, Build
| order by Build
| render linechart with (xcolumn=Build, ycolumns=P)

The correlation with time is not as strong as per build, so there are some unique things happening per build that I can't explain simply by when build runs.

I've ported it as https://dev.azure.com/fluidframework/internal/_workitems/edit/852


Fix race in test registry setup

Wait for the local registry-v2 test instance to become available to avoid random tests failures (as made obvious in #10471).

LGTM

LGTM


7005 rasa interactive cannot write non ascii character

Proposed changes:

fix #7005

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[x] updated the changelog (please check changelog for instructions)
[x] reformat files using black (please check Readme for instructions)

Thanks for submitting a pull request 🚀 @desmarchris will take a look at it as soon as possible ✨

Hey, the failing step wait for doc tests in CI workflow has fixed. The PR should be ready to review when the fix merged into your PR. 😊

Seems like the fix does not work with the situation when updating from the base branch I will fix this soon!

👋 Hey, the error is fixed. Please update the branch.

Thanks! @HotThoughts

@HotThoughts will look into it!

Thanks for the feedback @twerkmeister !


Error. MyQ no longer responding

Thenplugin no longer opens or closes then doors. I even updated to the latest pre-release 7.6.9. I a, gettin the follow error
Nov 1, 2021 at 10:19:40 PM
uniFiAP                         comsumeDictData Total excessive time consumed:8.6; <IP_ADDRESS>-2-APdict len:65,  item:{u'wifi_caps': 8306401, u'countrycode_table': [840, 124, 630], u'ip': u'<IP_ADDRESS>', u'uptime': 32
Reloading plugin "MyQ 7.6.9"
Stopping plugin "MyQ 7.6.9" (pid 3694)
MyQ Error                       exception in deviceStopComm(Mark’s Garage Door): 'ascii' codec can't encode character u'\u2019' in position 4: ordinal not in range(128)
MyQ                             Stopping MyQ
Stopped plugin "MyQ 7.6.9"
Starting plugin "MyQ 7.6.9" (pid 3714)
Started plugin "MyQ 7.6.9"
MyQ                             Starting MyQ
MyQ Error                       exception in deviceStartComm(Mark’s Garage Door): 'ascii' codec can't encode character u'\u2019' in position 4: ordinal not in range(128)

UPDATE….Deleted everything, reinstalled 7.72 and now it is working after reboot


Hi It would be really appreciate if anyone can help me on below -- I have a fileupload control (written in .net core) which takes end users solution folders so i need to upload entire folder and its files to azure devops git repo? can i do, as of now im able to upload all files to blob storage

Which version of the AzCopy was used?
Note: The version is visible when running AzCopy without any argument
Which platform are you using? (ex: Windows, Mac, Linux)
What command did you run?
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
What problem was encountered?
How can we reproduce the problem in the simplest way?
Have you found a mitigation/solution?

Hi @sivasaisambela, azcopy cannot be used to copy to git repo. Please find alternate solutions. Thanks.


Update 3.deploy-listener.md

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


Memory Management

Most programming languages have some mechanisms for automatic memory management. A large majority of languages utilize RAII (Resource Allocation Is Initialization) to automatically handle memory allocation for the programmer, but there are multiple strategies for automatic de-allocation.
Rust, the language Rouge is being written in, has its ownership and borrowing system to handle automatic de-allocation as well as its safety assurances. It's an extremely flexible system that still gives you a level of control while making sure you don't shoot yourself in the foot, but dealing with its quirks can feel like slamming your head into a brick wall (and I'm saying this as someone who really likes Rust).  Which is understandable, as it is the most common strategy. But you can't count on a tracing garbage collector doing its job in a timely manner, and there are multiple algorithms and strategies for implementing it.
A much simpler solution is to perform reference counting. You probably have an idea as to how this is done - each object has a number associated with it that indicates how many references to it exist. When that number hits 0, the object is de-allocated immediately. This extremely simple method of garbage collection is used by Apple's Swift programming language, and I'm thinking we use it in Rouge.
Reference counting does come with its own problems, however. Firstly, you can get a reference cycle wherein two objects have references to each-other. This prevents either object from being automatically de-allocated. While CPython has a cycle-detecting algorithm, another solution is to use weak references. These are references that don't contribute to the reference count, and become invalid when the referenced object is de-allocated. This could be done either by somehow detecting when a weak reference is necessary at interpret or compile time, or by adding a keyword that lets developers decide when to use weak references. There's also the fact that it must be done atomically to be thread-safe, and the quite obvious fact that the reference count needs to be stored in memory and that modifying that count adds a performance hit.
There are also more specific problems dealing with memory and thread safety. With reference counting by itself, there's nothing stopping the code holding those references from all trying to modify the object at the same time. Considering this, the first solution that came to mind was implementing copy-on-write semantics. Essentially, when multiple references exist for a given object, any attempted modification through those references causes a copy of the object to be produced. The reference used is then switched to the copy (decrementing the original's reference count in the process), and the copy is modified instead of the original object.
This works, but introduces some programming challenges. Suppose you want to implement a multi-producer single-consumer channel, which will probably be done in the standard library but isn't for now. You need multiple transmitter objects, a single receiver object, and a buffer or queue to send messages along that the transmitters can push to and the receiver can pull from. However, given the mechanisms discussed so far, this likely wouldn't be possible.
The whole purpose behind writing this issue is to try and get opinions on what I've thought of so far, as well as suggestions for how to deal with memory management. Whether those suggestions are modifications to what I've proposed here, or full on alternatives, I'm open to hearing them.
Thank you for taking the time to read this text vomit, and have an awesome day.

Hi! Found this through your discord bio and thought it was a pretty promising project, so I thought I'd leave my thoughts.
I like to think of memory management strategies as effectively being transparent to the user, but having different trade-offs between performance/implementation difficulty. Refcounting is fairly easy to implement, but the slowest method. GC is harder, but faster, and RAII is the hardest but fastest. As such I generally would say that RAII is the gold standard, and the only choice for a serious language. However, it's very difficult to implement in a nice way, and particularly to prevent issues like dead pointers and such which rust introduces the borrow checker for. So for the sake of implementing something now, it's also reasonable to go with something else. Rust even had a GC at one point.
I also don't think they really differ in terms of capabilities; refcounting can get into memory leaks, sure, but so can GC if you have static data or forget to clear an event delegate or something. C# has those kinds of issues, particularly forgetting to clear events. And then RAII doesn't normally have memory leaks in safe code, but if you use the refcounting tools like Arc you can form the same leaks as refcounting for the whole language can. In all cases the user has to be aware of the memory management semantics and work around it, but it's by far the least common in RAII.
I also don't think RAII is actually all that difficult for the user. The borrow checker can be frustrating, but the user will probably never actually think about RAII itself. If you write simple rust programs without borrowing, it "feels" just as easy as a GC/RC language but has the performance of manual memory management. You only really have to start worrying about it when you start creating custom allocating structs, which is very rare.
There are other forms of escape analysis than rust's borrow checker. Recently I found the Val language, which has a novel approach (which I still don't fully understand). C# also has its own, interesting form of limited borrow checking via ref semantics. Something along these lines might be easier to implement/friendlier to users than a full-fledged lifetime-annotated borrow checker.
If you're going along the refcounting route, it might also be helpful to look at Vale. They seem very proud of some optimization they used that they claim to have sped up their refcounting significantly. I'm not fully trusting of it though, they make suspiciously bold claims and that's always a red flag for me.
I think copy-on-write semantics might be odd; OOP users are going to be used to mutability, and CoW would make it impossible to take a reference to a thing and change the original. Could be fine in a more immutable, functional language, but given that Rouge seems to have inheritance it looks more OOP to me.
As a side note, I'm currently developing a bytecode-consuming interpreter/JIT engine pair for a custom IR called Devl. It's still just as young as this project, and can only barely do some basic addition, but I think it'd be neat if one day rouge could compile to DEV-IL.

You make a lot of good points. I'm just about to go to bed, but I'll try and give a more detailed reply in the morning.
(Also, you might be one of the first people to take a look at this project. So, thanks!)

Hi! Found this through your discord bio and thought it was a pretty promising project, so I thought I'd leave my thoughts.

Glad to have your thoughts! One thing I should note is that a lot of the stuff about this language is very much in flux - I keep looking at other programming languages to try and get ideas for useful (or just plain interesting) features, or to find better ways of doing certain things.

I like to think of memory management strategies as effectively being transparent to the user, but having different trade-offs between performance/implementation difficulty. Refcounting is fairly easy to implement, but the slowest method. GC is harder, but faster, and RAII is the hardest but fastest. As such I generally would say that RAII is the gold standard, and the only choice for a serious language. However, it's very difficult to implement in a nice way, and particularly to prevent issues like dead pointers and such which rust introduces the borrow checker for. So for the sake of implementing something now, it's also reasonable to go with something else. Rust even had a GC at one point.

Yeah, that's one of the reasons why I wanted to go with reference counting. If it's determined to be necessary I can probably move to other management strategies later on, but reference counting is a good starting place.

I also don't think they really differ in terms of capabilities; refcounting can get into memory leaks, sure, but so can GC if you have static data or forget to clear an event delegate or something. C# has those kinds of issues, particularly forgetting to clear events. And then RAII doesn't normally have memory leaks in safe code, but if you use the refcounting tools like Arc you can form the same leaks as refcounting for the whole language can. In all cases the user has to be aware of the memory management semantics and work around it, but it's by far the least common in RAII.
I also don't think RAII is actually all that difficult for the user. The borrow checker can be frustrating, but the user will probably never actually think about RAII itself. If you write simple rust programs without borrowing, it "feels" just as easy as a GC/RC language but has the performance of manual memory management. You only really have to start worrying about it when you start creating custom allocating structs, which is very rare.

That's valid. RAII is probably best for safety and runtime speed, and I agree with it potentially being just as easy as GC or RC - although one thing to note is that borrowing is basically a necessity for anything useful in Rust. The only thing is that - as you said previously - RAII is the most difficult strategy to implement.

There are other forms of escape analysis than rust's borrow checker. Recently I found the Val language, which has a novel approach (which I still don't fully understand). C# also has its own, interesting form of limited borrow checking via ref semantics. Something along these lines might be easier to implement/friendlier to users than a full-fledged lifetime-annotated borrow checker.

Just looked into Val - seems interesting, has 'mutable value semantics'. That strategy is also present in Swift according to some guy on Quora (second search result on DDG), which automatically implements it for any types with a fixed size, and can be implemented for types of variable size using lazy copy-on-write. There's a research paper partially written by Google employees which dives further into this: here's a link if you're curious. I'll have to look further into this.

If you're going along the refcounting route, it might also be helpful to look at Vale. They seem very proud of some optimization they used that they claim to have sped up their refcounting significantly. I'm not fully trusting of it though, they make suspiciously bold claims and that's always a red flag for me.

I've heard of Vale before. They have this strategy they call 'generational references'. From what I can read on their blog, there's a 'generation number' that indicates how many objects have been at a particular memory location, and that number is incremented whenever an object is freed. They claim it's faster because you only incur overhead on de-reference - not on alias or de-alias as with regular RC - and it's supposedly friendlier for cache and branch prediction. And this is supposedly only the first part of their overall strategy of 'hybrid-generational memory' - which is just gen-refs combined with static analysis and scope tethering. Sounds interesting, but I'm just as skeptical as you are about their claims. I guess it's a 'wait and see' kind of deal.

I think copy-on-write semantics might be odd; OOP users are going to be used to mutability, and CoW would make it impossible to take a reference to a thing and change the original. Could be fine in a more immutable, functional language, but given that Rouge seems to have inheritance it looks more OOP to me.

While Rouge was going to have inheritance at some point, I have since decided against it in favor of going all-in on what are basically mixins (but I call them parts because I have this whole separation of data and behavior thing going on here). I still haven't pushed the updated README though - still working some things out. But your point is still entirely valid.

As a side note, I'm currently developing a bytecode-consuming interpreter/JIT engine pair for a custom IR called Devl. It's still just as young as this project, and can only barely do some basic addition, but I think it'd be neat if one day rouge could compile to DEV-IL.

So young that I can't seem to find a repository for it on your profile. But it definitely sounds interesting - if you've got any further information about it you'd like to share, send me a message on Discord or something.

One thing I should note is that a lot of the stuff about this language is very much in flux...
I'd hope so! I also enjoy looking around at new languages and experimentation. That's why I looked here! Rouge doesn't seem to have any particularly new features, but statically-typed scripting languages are, for some reason, pretty rare, so it's kinda novel overall.

While Rouge was going to have inheritance at some point
Ooh, even better. I strongly dislike inheritance, and am glad to see languages choose any other approach. I can begrudgingly deal with it in a scripting language but I still far prefer compositional approaches. When you say mixins, do you have an example of how they work? Is it like javascript's mixins, where methods are copied from one "class" (or something less than a class") into a class?

So young that I can't seem to find a repository for it on your profile
Yeah, it's in extreme flux right now. Once the IR is more or less stable I'll put up a public repo. I have a tendency to start local, push when I've reached a certain size, rather than clone from github. Also no guarantee that it will be finished, but so far it's been coming along well. I also want to do some writeups about the decision making process and technical details of it, but I want the repo up before that.

And then you would include the part in a class like so:

Interesting! I think I recall seeing an alternate form of this where any struct can be inlined. It would look something more like
class Player is:
    inline Transform,
    ...
end

I think this might avoid code duplication- if Transform is a part instead of a normal type (and thus can't have traits implemented for it) then there'd have to be a separate type for implementing traits, and I think that'd get pretty messy quick. Inlining arbitrary types would give the same ability to "flatten" the type hierarchy while still allowing the use of types as normal. I'm also not entirely sold on the usefulness of this mixin-style code regardless. What does it actually buy aside from reducing .thing accesses? Also, it seems like this might be related to delegation (basically copying a type's impl to a parent type as sugar for re-implementing all those methods to access the inner type)

I have been considering making the commas optional and dropping the colons - thoughts?

I'm all for that. I've yet to see a perfect example of what I'm thinking, but I think it should be possible to create a language with whitespace-significant-like syntax, without actually being whitespace significant. Or at least, having whitespace significance be entirely for format's sake, not because it actually disambiguates anything. Like your class definition example could be:
class Player is part Transform string name float health float max_health float energy float max_energy end

while horrible as far as readable code goes, this is perfectly parseable as-is. I believe an entire language could be designed in this way, and be really clean. I'm planning on trying it out once devl is usable, if it ever does mature (fingers crossed)
I also might recommend changing class to type. I think I've only seen really functional languages do this, but it makes a lot more sense to me than class/struct. Struct is already jargon, it basically means nothing, and class is loaded with so many expectations that don't really apply here that I don't think it makes sense. type is super explicit and clean imo. Also aligns terminology so that a generic type literally is a generic type, not a generic class/struct.


[Q] Partial Grid Search using sweep config

Is there a way to specify partial grid search in the sweep yaml file? By partial, what I mean is -
hyperparameter1 - [v1, v2, v3, v4, v5] - there are values for hyper parameter 1 that I want to search over.
hyperparameter2 - [x1, x2, x3, x4, x5, x6, x7, x8, x9, x10]
hp2 - [y1,y2,y3,y4]
but say I want to only run combinations of v1 with x1, x2 - v2 with x3, x4 and so on, and all combinations of hp3
is there a way of specifying this in the sweep config? I think this can be a pretty useful feature if we know that in our use case some combinations of hyperparameters do not make sense.
Thanks for your time and please let me know if anything is unclear!

hI @meghbhalerao, this is not currently available but we have a feature request for conditional parameters in sweeps if you would like me to add you to the request?
Basically it would select parameters based on the selection of other parameters so if hp1 was V1 then you could set conditional logic to not use certain values for hp2.

Hi @meghbhalerao, I wanted to follow up and see if you think that feature request would solve your use case?

Hi nate
Yes I think the feature request you mentioned will be helpful and it would
solve the thing I need.
Thanks !
On Sat, 17 Jun 2023, 01:11 nate-wandb, @.***> wrote:

Hi @meghbhalerao https://github.com/meghbhalerao, I wanted to follow up
and see if you think that feature request would solve your use case?
—
Reply to this email directly, view it on GitHub
https://github.com/wandb/wandb/issues/5698#issuecomment-1595201057, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AH5KGEGED7AV6WHNK66XITDXLSZHDANCNFSM6AAAAAAZBLBV3A
.
You are receiving this because you were mentioned.Message ID:
@.***>

Ok, I can follow up once we are able to implement this. Thank you!

Im also interested in conditional parameters. Some parameter combinations might result in errors (and I know which ones).


How can I use the seq2seq model tensorflow serving ?

I would like to know I can I serve this model with tensorflow and predict for a single sentence input ?

hi,have you get this method?Can you tell me?

have any idea?i have the same question.

您的邮件已收到，，，我会尽快回复的，，，


Deletion of LTR Backups

I would like the documentation to be clear as to deletion of LTR Backups.  Assume a scenario where an Azure account was compromised (hacked) and the person deleted the LTR backups and then deleted the Azure Sql Server.  Could the database(s) still be restored from either the most recent backups or the LTR backups?  Is this documented anywhere?

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

ID: 2b388152-5d9d-bfb9-1dd3-168b4877ac5a
Version Independent ID: 901abe21-41fd-c208-6301-9cc45acf0e4f
Content: Store Azure SQL Database backups for up to 10 years
Content Source: articles/sql-database/sql-database-long-term-retention.md
Service: sql-database
Sub-service: backup-restore
GitHub Login: @anosov1960
Microsoft Alias: sashan

@Johnsiii88 Thanks for the feedback. We are investigating into the issue and will update you shortly.

@Johnsiii88 LTR Backups would need to be deleted separately from the Azure SQL Server instance. In the case or PITR backups, the deletion of the Azure SQL Server instance also deletes all associated PITR backups. The specific section that details Deletion of LTR backups touches on your point.

What you are likely looking for is a means to stash backups in a more secure location for full disaster recovery. I suggest you comment on and up-vote the following Uservoice entry: Export SQL Full and Diff backups directly to blob storage

We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.

Thanks.  So maybe I'm re-stating what you said but I want to be very clear.  I think you are saying that currently, a user account with the appropriate permissions could delete all of the LTR backups and then delete the sql server and the database and all backups would be instantly and permanently gone and could not be recovered either by the client or by Microsoft.  I have seen comments in other threads that implied that Microsoft could still recover the LTR backups within 7 days but I have not read that in any official Microsoft documentation.  This seems like a large concern for anyone using Azure Sql database in a production capacity.  There needs to be some type of immutable option for PITR and LTR backups.

@Johnsiii88 This is correct. If the actions you mentioned were to play out, there would be no recovery option a customer could invoke to recover the deleted assets. However, a customer could perform an export of an Azure SQL Database and retain this in a storage solution (on-premise or in Azure) that would be separate from (and not associated with) the SQL Server or the subscription. This is more of a strategic step and not necessarily a technical solution (other than the media where the file is stored). I highly suggest that you create an entry in the UserVoice forum to bring this idea to the Product Group.


python 3.4 artifact build is broken (due to c-ares?)

https://grpc-testing.appspot.com/view/Artifacts/job/gRPC_build_artifacts/3204/architecture=x86,language=python,platform=linux/console
https://grpc-testing.appspot.com/view/Artifacts/job/gRPC_build_artifacts/3204/architecture=x64,language=python,platform=linux/console
warning: no files found matching '*.h' under directory 'src/python/grpcio/grpc'
warning: no files found matching '*.python' under directory 'src/python/grpcio/grpc'
warning: no previously-included files matching '*.so' found under directory 'src/python/grpcio/grpc/_cython'
warning: no previously-included files matching '*.pyd' found under directory 'src/python/grpcio/grpc/_cython'
error: [Errno 2] No such file or directory: 'third_party/c-ares'
+ rm -rf /tmp/pygrpc.qW1224
+ FAILED=true
+ '[' artifacts '!=' '' ']'
+ docker cp build_and_run_docker_e28b54c7-e2cf-4d2a-80b1-e85d496bea24:/var/local/git/grpc/artifacts /home/jenkins/workspace/gRPC_build_artifacts/architecture/x86/language/python/platform/linux
+ docker rm -f build_and_run_docker_e28b54c7-e2cf-4d2a-80b1-e85d496bea24
build_and_run_docker_e28b54c7-e2cf-4d2a-80b1-e85d496bea24
+ '[' true '!=' '' ']'
+ exit 1

2017-04-12 06:53:27,783 FAILED: build_artifact.python_linux_x86_cp34-cp34m [ret=1, pid=20137]

#10683 closed this issue automatically. But it still needs to be verified.

Python linux artifact builds have been fixed by #10683. But the windows artifact build is still broken.

#10781 fixed the windows artifact build by disabling c-ares for python on x64 windows.
https://grpc-testing.appspot.com/view/Artifacts/job/gRPC_build_artifacts/3271/


Fetch latest spec and regenerate

Added a utility to fetch the latest published OpenAPI spec
Regenerated the client from the current spec

This change is

TFTR!


Bug in MqttTcpChannel (.NET Framework/NetStandard1.3)

I ran into a issue when trying to connect via SSL with a Self-Signed Cert. I needed to override the validation function to always return true for self-signed certs. In previous versions of .NET I could use
ServicePointManager.ServerCertificateValidationCallback = (sender, certificate, chain, errors) =>             {                 return true;             };
In dotnet CORE this is ignored. My only remaining option is to call the SslStream ctor overload that accepts a validation function
public SslStream(Stream innerStream, bool leaveInnerStreamOpen, RemoteCertificateValidationCallback userCertificateValidationCallback)
I implemented a custom MqttClientFactory that in turn called public MqttTcpChannel(Socket socket, SslStream sslStream)
This allowed me to pass in the custom validation logic. However when I ran the code the certificate was still being flagged as invalid. Upon digging into the code I noticed
public async Task ConnectAsync(MqttClientOptions options)
Ignores this value... by always overwriting it with _sslStream = new SslStream(new NetworkStream(_socket, true));
 if (options.TlsOptions.UseTls) {                    _sslStream = new SslStream(new NetworkStream(_socket, true));                     await _sslStream.AuthenticateAsClientAsync(options.Server, LoadCertificates(options),                      SslProtocols.Tls12, options.TlsOptions.CheckCertificateRevocation); }
This does not appear to be 100% correct, I see that one overload is intended for SERVER opposed to CLIENT channel. However I don't think having ConnectAsync stomp on the value set in the ctor is correct.  Its also not intuitive that only a specific overload must be used depending on which end of the channel is communicating.
I would be happy to submit a pull request. I'm thinking that Client/Server need separate implementations of IMqttCommunicationChannel OR marking one as internal (this may not work without the ugly InternalVisibleToAttribute)
Another approach is to just expose the validation delegate as a property on MqttClientOptions. This seems hacky and does nothing to address the greater issue (specific ctor for Client vs. Server)
Thoughts?

Hi,
yes I know that global solution from regular .NET framework.
In general there is a dedicated object for Tls options for this in the MQTT client.
In my opinion there should be a new boolean value which allows ignoring self signed certificates. Something similar is already there for revoked certificates. Maybe this can be reused or already works for your case!?
Then the implementations should inspect the options and add a handler in the SslStream etc. so that there is no new factory required and the user can set it with a simple option.
What do you think about this solution?
Best regards
Christian

I don't think a simple Boolean property would be sufficient. There isn't a specific property on a Self-Signed cert identifying it as such. A Func<,,,> matching the signature of the delegate could be exposed as a property. This would allow the developer full control over what certificates to accept/reject.
I think something alone these lines would work for my specific use case. I guess what I was also trying to resolve is the need to always have a property for each setting that should be mapped back. At some point if the needed functionality deviates from the standard design the developer would be better off constructing the SSL stream externally. The public MqttTcpChannel(Socket socket, SslStream sslStream) signature indicates this is possible, alas the SslStream property is always overwritten by an internal call. At a minimum this overload should be changed to public MqttTcpChannel(Socket socket) to match the behavior of the object.

I agree but the Func you mentioned must be sufficient for all frameworks. I saw that core has different properties than the classic .NET stuff. If you provide such a function the implementation must map this function to the used stream which might be not possible because UWP don't has this function. It only has several enum which are describing what certificate status can be ignored. So a Func will not make sense in my opinion. A boolean is easier for that. What do you think about this?
Best regards
Christian

Please have a look at the develop branch. I added several TLS options regarding certificate validation. Please let me know if this fits your needs.

Looks like it should work fine for my needs. I will take the updated package a run a few tests.

I also added a callback mechanism for dealing with complex certificate validations. It is described in the wiki. I will close this ticket. Please let me know it you need more features to deal with certificates.
Best regards
Christian


Digital input counter & reset exposed in Presence IPSO object

Some optional resources now are created.

https://github.com/CreatorKit/libobjects/pull/16/commits/053a1d1e17912da8d59fbbd73c398352fbeff63c is a sync to your local repo and should not be committed to github repo

It seems the actual fix is https://github.com/CreatorKit/libobjects/compare/dev...thetoster:presence_update?expand=1
please open a new Pullrequest with only this change.


Test CI

@gavanderhoorn CI works, badge is ok and pull request trigger builds.
Not sure what I/you made right but it now works!


Upgraded to support MongoDB both v4 and v5 drivers

Tested with both the v4 and the v5 driver in the Cloudize API Games Framework. All downstream tests pass, so this looks good.

Thank you! This looks good. Will target to roll a new version with this change tomorrow

Available in v2.5.4


Extends FieldArgTypeCoercion

Hello @chanind, here's an extension proposal for the FieldArgTypeRewriter rewriter.
This PR is backwards compatible.
New functionalities are included for the FieldArgTypeRewriter rewriter.

fieldName now optional in case matchConditions are passed: Useful to avoid having to create a new rewriter for every field, as now the matching can be delegated to the matchConditions

coerceVariable function now receives context in second argument: Context includes all of query's variables and arguments, and very useful for coercion that needs the value of other argument values as in pagination coercion (e.g., [limit, offset] to [pageSize, pageNumber])

In-Query argument values can be coerced: _Now, there's the coerceArgumentValue that allows support when argument values come in the query document.

Unit Tests for new functionalities

Hey @chanind, thanks for taking a look at this. Ive fixed the lint issues and your suggestions as well.

:tada: This PR is included in version 3.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Display project languages for each issue in Mariner output

When outputting an available issue, Mariner should include the language(s) used in the repo the issue belongs to. This will make it easier for a potential contributor to know whether or not it's a good issue for them.

by display the language, do you mean adding it as a shield in the readme? Or is there is something else that would be helpful?

If it's a badge I made an issue #104 and included a language badge in description, a contributor added it #105

This issue is for Mariner's output. Not the Mariner repo itself, but the repos/issues it reports on. I just edited the initial description and issue title to be more clear. Let me know if you think it still isn't clear.

It looks like we can obtain a list of languages for each project by adding this to our query, within the repository block:
            languages(first: 10) {
              edges {
                node {
                  name
                }
              }
            }

This will come back with a list of up to the first 10 languages that were detected in that project, which we could assemble into some kind of formatted output, and include on a per-project (not per-issue) basis. I believe the languages will by default be listed in order from most-used to least, but if not, we should be able to pass "SIZE" to the languages() as the sort parameter. I chose 10 as an arbitrary number that seemed reasonable. We could use 3 or 5 or 25.


Inserted assert_warns to ignore warnings

I inserted assert_warns to ignore DeprecationWarning.

How about fixing this test.

It also checks the error message.

LGTM!


app: add FlareSolverr

In this PR;

FlareSolverr added.
It is some kind of a proxy app for HTTP requests. Some of Prowlarr's indexers require that solver to bypass CloudFlare.

How to test:

Install FlareSolver app.
Test with curl:

curl -L -X POST 'http://localhost:8191/v1' \
-H 'Content-Type: application/json' \
--data-raw '{
  "cmd": "request.get",
  "url": "https://prowlarr.servarr.com/v1/ping",
  "maxTimeout": 60000
}'

Do not forget to change your hostname.

If you get a response, it is working :)

Or, directly test with Prowlarr: https://trash-guides.info/Prowlarr/prowlarr-setup-flaresolverr/#add-flaresolverr-to-prowlarr

Hello @CorrectRoadH
Would you be able to take a look at this PR? I added testing instructions to make it easy to test for you :) I think many prowlerr users dependant on this app too :)

Hello @CorrectRoadH
Would you be able to take a look at this PR? I added testing instructions to make it easy to test for you :) I think many prowlerr users dependant on this app too :)

Yes, I am willing to handle this PR, but I am quite busy recently. I will test the application when I am free and merge it if it passes. It may take a day or two later.🥺

@CorrectRoadH I hope you doing well! Will you be able to take a look at this PR soon?

Thanks for your contribution!❤


auto detect source_lang not correct

in my case, some ‘zh’ strings are detected to 'wuu', 'yue', 'eo'....actually, they are all 'zh' strings.

Language detection is based on fasttext lang detect. Sadly it is not really 100% reliable, but sadly cannot change it.
What you can do:

Use a different language detection lib (https://github.com/UKPLab/EasyNMT/blob/5ea48f5fb68be9e4be4b8096800e32b8ad9a45df/easynmt/EasyNMT.py#L34), e.g. langid or langdetect
Provide the source_lang parameter to the translate method, then the language is not tried to be detected automatically.


Optimize downstream generation

As proposed by Manuel, generating the downstream of a counter does not require reading its value.

In this line, does every operation on a set need to generate a downstream op? Or just, e.g., removes?

On May 13, 2015, at 12:58, marsleezm<EMAIL_ADDRESS>wrote:
As proposed by Manuel, generating the downstream of a counter does not require reading its value.
—
Reply to this email directly or view it on GitHub https://github.com/SyncFree/antidote/issues/106.

Actually just remove


hi. request. READ.

What feature do you want to get added on the base engine?
hi. so i just wanted to say, can you list in the wiki of how to remove certain things from the main menu selection screen? thanks.
T4anoa (if I bothered you, I'm sorry. just a suggestion)
To test your sight, and reliability, please select the option of what should NOT be requested.
Code optimization that would make the game faster. (You should make a PR if this is your request, by the way.)

you cant remove main menu crap in lua
you failed the test

this is more like a Documentation

Right, but you can only create/make stuff in PlayState with lua.

Plus he failed the test


MPW6 Roll over design update

Following MPW5 to MPW6 roll over designs updated in CI.
asicle
azadi_soc_iii_dft
microwatt
prga

@vvbandeira
can you check this PR?
changed jenkinsfile to mpw6 design name, but still its looking mpw5 name and failing.