AnsiCte (with text/ansi) adds extra line to end of file

Describe the bug
AnsiCte - text/plain

[x] Zero length files should show as having one line.
[X ] One line files should show as having one line.
[X ] 1000 line files should show as having 1000 lines.

AnsiCte - text/ansi

[ ] Zero length files should show as having one line.
[ ] One line files should show as having one line.
[ ] 1000 line files should show as having 1000 lines.

Describe the bug
AnsiCte - text/plain

[x]  Zero length files should show as having one line.
[x] One line files should show as having one line.
[x] 1000 line files should show as having 1000 lines.

AnsiCte - text/ansi

[x]  Zero length files should show as having one line.
[x]  One line files should show as having one line.
[x]  1000 line files should show as having 1000 lines.

Implemented a workaround for: https://github.com/pygments/pygments/issues/1435
                    if (!string.IsNullOrEmpty($"{file}.an") && File.Exists($"{file}.an")) {
                        Log.Debug("Reading {file}", $"{file}.an");
                        document = await File.ReadAllTextAsync($"{file}.an", Encoding.UTF8).ConfigureAwait(true);

                        // HACK: Because of this bug: https://github.com/pygments/pygments/issues/1435
                        if (document[^1] == '\n')
                            document = document.Remove(document.Length - 1, 1);
                    }


303 KiB _app in Next.js Example

I am referring to this example:
https://github.com/mui-org/material-ui/tree/master/examples/nextjs
Run the following commands:
curl https://codeload.github.com/mui-org/material-ui/tar.gz/master | tar -xz --strip=2  material-ui-master/examples/nextjs

cd nextjs

yarn install

yarn build

and you'll see a 303 KiB _app page in red. Why is that?

I don't know, nor I think that Material-UI has leverage over it.


doc: remove Pull Request note in README.md

Since we now accept Pull Requests via GerritBot, this comment is obsolete.

Oh the irony.

Let's try this again.

Brad Fitzpatrick has posted review comments at golang.org/cl/92995.

Actually I didn't write a single English word. I just voted +2. Ideally we'd revise this message to be more specific. Low priority.

Brad Fitzpatrick has posted review comments at golang.org/cl/92995.

Actually I didn't write a single English word. I just voted +2. Ideally we'd revise this message to be more specific. Low priority.

nice. Is this also powered off your superduper-emailpubsub?

@hanwen, yes, it uses https://maintner.golang.org/ and https://pubsubhelper.golang.org. But of course there's plenty of code on top of that. See https://github.com/golang/build/tree/master/cmd/gerritbot

this is epic


How to Add Github Badge

Feature Request
The Problem
It does not appear to be possible to associate a badge with this Action. The reason being that the Action spawns a separate job which (as shown in the image above) seems to associate itself to other workflows depending on whichever one is running at the time.
Question
Is there a way to associate the pass/fail state of Rubocop to the main workflow?

hm you appear to be correct. Are you interested and trying to find a fix?
Recreated with https://github.com/andrewmcodes/rubocop-linter-action-148/actions/runs/166108630.

Hello, @pacarvalho

Is there a way to associate the pass/fail state of Rubocop to the main workflow?

Yes, the linter action can return an exit code, to stop the main workflow.
Keep in mind that this does not execute the next steps after the failure of the linter.


increase coverage

Is your feature request related to a problem? Please describe.
Coverage is around 70%, looking on coverall looks like reporter.py and friends are not hit!
Reason is that reporter tests are done via docker, so they are not covered.
Describe the solution you'd like
Have coverage to get data also from reporter and friends, probably this can work by
running pytest from the container itself and mounting a folder.

closed by #441.


linux-yocto-3.14.bbappend: remove

The linux-yocto-3.14.bbappend breaks compilation against current
OE-core master because linux-yocto-3.14.bb was removed. Therefore we
also need to remove the .bbappend.
The oldest supported OE-core is Dizzy, which already has linux-yocto
3.17. If someone still needs the 3.14 kernel patches, they will have
to maintain them in the BSP layer.
Signed-off-by: Patrick Ohly<EMAIL_ADDRESS>

+1


Add the SAP Launchpad Service

Tutorials: https://developers.sap.com/tutorials/btp-app-launchpad-service.html
In steps 10 and 12 it is not possible to enter destination cpapp-app-srv.  The generator only shows value "None" and using the arrow keys doesn't show any more options, and it's not possible to enter a value manually.  This destination is properly configured in my mta.yaml.
Additionally, after adding the content to the Launchpad and clicking the Risks app it gives the following error:  "Application could not be started due to technical issues.
File not found"
Please help!

Thank you for your feedback. We haven't heard from you in a while, so we are closing the issue.
If you still have questions, feel free to reopen the issue.

Hello, I have the same Issue:
In steps 10 and 12 it is not possible to enter destination cpapp-app-srv. The generator only shows value "None" and using the arrow keys doesn't show any more options, and it's not possible to enter a value manually.
This destination is properly configured in my mta.yaml.
Thank you for your cooperation

@jegiraldog Try to update the extensions and modules if you haven't, also you might need to update the generators which are seprate.
Trigger updates of the generators from VS Code as follows:

In VS Code, invoke the Command Palette ( View → Command Palette or Shift + Command + P for macOS / Ctrl + Shift + P for Windows) and choose Fiori: Open Application Generator.
Click on the link "Explore and Install Generators".
Next to search for Generators input field there is a dropdown called "Search Shortcuts", click on the dropdown and select "SAP Fiori". VS Code should install and updates for generators if available.

Create a new issue if you need further support as this one is closed and you can tage me.
Best regards,
Maha (She/Her)


RequestError (500): send request failed (original: Get "http://<IP_ADDRESS>:9000/local-files/yang***/*****/3k2xr8hc/wandb-metadata.json": dial tcp <IP_ADDRESS>:9000: connect: connection refused)

When I update wandb-local from v0.9.39 to v0.9.43, I can't open website page. The error message is :
RequestError (500): send request failed (original: Get "http://<IP_ADDRESS>:9000/local-files/yang***/*****/3k2xr8hc/wandb-metadata.json": dial tcp <IP_ADDRESS>:9000: connect: connection refused)
I don't know why to have a port 9000.

@JieGenius this indicates that the minio object store running inside of the container is not accepting connections.  I would try restarting the container.  If that doesn't work, you can exec into the container and see if there are any details in the following log file: /var/log/minio.log

@vanpelt Thank you! I have solved this problem by checking the log file.
The message from the minio.log file:
ERROR Invalid command line arguments: Cross-device mounts detected on path (/vol/minio) at following locations [/vol/minio/local-files/xxxxxx/warehouse]. Export path should not have any sub-mounts, refusing to start.       > Please check the FS endpoint
It works fine when I unmount another disc.


How to apply style to the inner text of the date time control

Hi,
Can you tell me how to apply style to the inner text of the date time control ? I have tried like below.But it's not working.

   {{ user.date | date:'MM-dd-yyyy' }}

Here is my Fiddler : Fiddler

Hi @ckosloski Can I have any support for this ? Thanks.

Are you trying to style the text in the textbox in your fiddle?

Exactly @ckosloski It is date picker control.I need to give a colour to that date text.

Currently the bsdate control doesn't support the e-style attribute.
Does the color change per row?  If not, you could setup a css class to style the text.

Actually @ckosloski  I need to give a colour according to the condition as shown below.Could you tell me how to do that ?

       {{ note.date | date:'MM-dd-yyyy' }}

It's going to require a change to editableBsdate directive to support e-style.

Oh.. OK @ckosloski Then you can mark this issue as an enhancement no ? Hope you'll do that and will let us know.Thanks.

Thanks a lot @ckosloski  Have you released new version or what ?

I added a fix for your issue.  There has not been a new release.  You would have to build it yourself locally in order to get the latest changes.

Oh..   :open_mouth: Then can you please tell me how to do that or may be a simple reference link about the way how to do that @ckosloski  ?

You need to clone the repository locally.
install npm if you don't have it
install grunt globally, if you haven't already: npm install -g grunt-cli
npm install in the project
grunt jade - to create the test files
grunt build - to build the project files

Thanks  a lot @ckosloski    :thumbsup:  I really appreciate it.I'll try it and will let you know if I'll have any issue.


Accuracy is High but Validation Accuracy is Bad

Hi, I have been working on the channel ordering issue and finally I managed to train the model but the results are very bad. Do you have any suggestions on how shall I improve the results?
The results are as attached below:
https://colab.research.google.com/drive/1xHghjvOEVZc3bGtLfgRNw6Xq51d7U_XA
https://colab.research.google.com/drive/1G_oh_f-2TxF8oa6bVpn-qXlRyOfAPAAq

Hi,
There are no clear answer to this question.
But there can be at least two approaches:

increase number of sample data (cause it's a deep learning, that means more data you have better network can learn)
experiment with the current model. You can add more layers, change activation functions.

Also it's highly expected that multi class is less accurate than simple binary.


GitHub Backend o-auth permissions set too widely

Currently when using Github Backend, the app requires access to pretty much everything.

The scope is hard coded to repo here : https://github.com/netlify/netlify-cms/blob/78e4b829d0ced72f8f38721d38c0d67ccb092aaf/src/backends/github/AuthenticationPage.js#L26
It would make more sense to have a much more limited scope or at least a way to customise it.
I'd suggest public_repo by default.
In the future, maybe deploy keys would work better, allowing only access to a single repo.

I suppose making this configurable would be fine, just might require some error handling around attempts to access restricted repos.
Proposing:

Keep the current default, it's important that this "just works"
Accept an auth_scope property under backend in config.yml
Restrict accepted values to those that work for the CMS, currently repo and public_repo

Thoughts?
cc/ @Benaiah @talves @tech4him1

@erquhart The screen capture implies the login has access to ALL repos within the login. Is that true or is it only the repo logging into?

@talves It has access to every repo on your account -- the only two OAuth scopes available for repo access are repo (ALL repos) and public_repo (write access to ALL public repos).

The permissions are insane. I don't need Netlify to have read/write permissions over ALL repo's and I don't need Netlify to have organization access. What for does Netlify need this? Plus, the default setting is that it wants PUBLIC and PRIVATE repo access? Seriously, this is red flags all over for me and it's making me not want to use Netlify.

I'm going to prioritize this one to better support the open authoring workflow (no need for private repository access)


Exporting Asesst Error

Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Import: Unable to read MonoBehaviour, because some assemblies are missing Export: Unable to export asset icon_up Export: Unable to export asset checkmark Export: Unable to export asset icon_lock Export: Unable to export asset uisprite_white Export: Unable to export asset arc Export: Unable to export asset plus Export: Unable to export asset dropdown_arrow_white Export: Unable to export asset icon_point_edit Export: Unable to export asset icon_band_aid Export: Unable to export asset icon_eraser Export: Unable to export asset icon_eye Export: Unable to export asset icon_plus Export: Unable to export asset cell_mask Export: Unable to export asset icon_blur Export: Unable to export asset male_type Export: Unable to export asset female_type Export: Unable to export asset icon_mirror Export: Unable to export asset icon_eyedropper Export: Unable to export asset icon_pen Export: Unable to export asset icon_cursor Export: Unable to export asset Particle Export: Unable to export asset Pencil Export: Unable to export asset OvalSoft Export: Unable to export asset Grunge Export: Unable to export asset Slash General: Finished!!! Import: Game file 'app.info' has been found Import: Game file 'data.unity3d' has been found Import: Assembly 'UnityEngine.IMGUIModule' has been loaded Import: Assembly 'UnityEngine.CoreModule' has been loaded Import: Assembly 'UnityEngine.TextRenderingModule' has been loaded Import: Assembly 'mscorlib' has been loaded Import: Assembly 'UnityEngine.UI' has been loaded Import: Assembly 'UnityEngine' has been loaded Import: Assembly 'Assembly-CSharp' has been loaded Import: Assembly 'UnityEngine.AnimationModule' has been loaded Import: Assembly 'Unity.Postprocessing.Runtime' has been loaded Import: Assembly 'UnityEngine.UIElementsModule' has been loaded Import: Assembly 'UnityEngine.StyleSheetsModule' has been loaded Import: Assembly 'UnityEngine.PhysicsModule' has been loaded Import: Assembly 'UnityEngine.Timeline' has been loaded Import: Assembly 'UnityEngine.Networking' has been loaded Import: Assembly 'UnityEngine.TestRunner' hasn't been found Import: Assembly 'UnityEngine.GoogleAudioSpatializer' hasn't been found Import: Assembly 'Unity.Analytics.Tracker' has been loaded Import: Assembly 'UnityEngine.SpatialTracking' has been loaded Import: Assembly 'UniRx.Examples' hasn't been found Import: Assembly 'Assembly-CSharp-firstpass' has been loaded Import: Assembly 'Mux.Tests' hasn't been found Import: Assembly 'Google.Protobuf' has been loaded Import: Assembly 'Mux.Markup.UI' has been loaded Import: Assembly 'UniRx.Async' has been loaded Import: Assembly 'UniRx' has been loaded Import: Assembly 'Unity.TextMeshPro' has been loaded Import: Assembly 'Mux' has been loaded Import: Assembly 'Mux.Markup.UI.Tests' hasn't been found Import: Assembly 'Unity.Analytics.DataPrivacy.Tests' hasn't been found Import: Assembly 'Mux.Markup' has been loaded Import: Assembly 'Mux.Markup.Animation' has been loaded Import: Assembly 'Unity.Analytics.DataPrivacy' has been loaded Import: Assembly 'Unity.TextMeshPro.Tests' hasn't been found Import: Assembly 'Unity.Postprocessing.Runtime.Tests' hasn't been found Import: Assembly 'Unity.Analytics.Editor' hasn't been found Import: Assembly 'UnityEngine.TilemapModule' has been loaded Import: Assembly 'UnityEngine.AudioModule' has been loaded Import: Assembly 'UnityEngine.UNETModule' has been loaded Import: Assembly 'System.Core' has been loaded Import: Assembly 'Xamarin.Forms.Core' has been loaded Import: Assembly 'netstandard' has been loaded Import: Assembly 'UnityEngine.UIModule' has been loaded Import: System.ArgumentOutOfRangeException: length' חייב להיות לא שלילי. שם פרמטר: length    ב-  System.Text.StringBuilder..ctor(String value, Int32 startIndex, Int32 length, Int32 capacity)    ב-  uTinyRipper.Converters.Script.Mono.ScriptExportMonoType.GetGenericName(TypeReference genericType, IReadOnlyList1 genericArguments)
ב-  uTinyRipper.Converters.Script.Mono.ScriptExportMonoType.GetName(TypeReference type)
ב-  uTinyRipper.Converters.Script.Mono.ScriptExportMonoType.GetFullName(TypeReference type, String module)
ב-  uTinyRipper.Converters.Script.ScriptExportManager.RetrieveGeneric(TypeReference generic)
ב-  uTinyRipper.Converters.Script.ScriptExportManager.RetrieveType(TypeReference type)
ב-  uTinyRipper.Converters.Script.Mono.ScriptExportMonoType.Init(IScriptExportManager manager)
ב-  uTinyRipper.Converters.Script.ScriptExportManager.RetrieveType(TypeReference type)
ב-  uTinyRipper.Converters.Script.Mono.ScriptExportMonoType.Init(IScriptExportManager manager)
ב-  uTinyRipper.Converters.Script.ScriptExportManager.RetrieveType(TypeReference type)
ב-  uTinyRipper.Game.Assembly.Mono.MonoManager.GetExportType(ScriptExportManager exportManager, ScriptIdentifier scriptID)
ב-  uTinyRipper.Game.AssemblyManager.GetExportType(ScriptExportManager exportManager, ScriptIdentifier scriptID)
ב-  uTinyRipper.Classes.MonoScript.GetExportType(ScriptExportManager exportManager)
ב-  uTinyRipper.Converters.ScriptAssetExporter.Export(IExportContainer container, IEnumerable1 assets, String dirPath, Action3 callback)
ב-  uTinyRipper.Project.ScriptExportCollection.Export(ProjectAssetContainer container, String dirPath)
ב-  uTinyRipper.Converters.ProjectExporter.Export(String path, GameCollection fileCollection, IEnumerable1 files, ExportOptions options)    ב-  uTinyRipper.GameStructure.Export(String exportPath, Func2 filter)
ב-  uTinyRipperGUI.MainWindow.ExportFiles(Object data)`
I put both all data include the data.unity3d and I got that error

+1 for Atom Rpg game.
I confirm the presence of such errors.
And level scenes, texture layers of terrain are not yet extracted. C # scripts are inferiorly extracted.

Unity Version 2019.1.14f
GoG version of the game attached for research.
https://1drv.ms/u/s!AqcT_cxckp3KjttCM0r748yJ5zqg5A?e=oopRiH

@DemonRem I need game files to reproduce this issue.
@Ratigorr what errors do you mean? "Unable to read MonoBehaviour, because some assemblies are missing" ? Those are just warnings. They just indicate, that output may be incorrect. As for texture layyers of terrain, I think they are implemented as a separate asset type, for which export is not implemented.

Hi!.
1.

A few textures. Not all. Snap to layers is damaged.
.

@mafaca yes, you're right, files with the extension .terrainlayer are not extracted.
in folder Assets\Resources\terrain\

just ignore it
terrain layer is supported by ripper, but its export is disabled. i'll enable it when i have time to test it.
i think those textures are generated by unity during import stage for its inner purposes.

will be very cool if it works.

enabled terrain layer export in c3e9a5c32b30b7ed8dbf79a18fba2d286f05745b

Nice work! Thank you!


Spiller support constant column

What problem does this PR solve?
Issue Number: close #7512
Problem Summary:
In current spiller, if a block contains constant column, the spiller will convert it to full column before spill, a better solution is not spill constant column at all.
What is changed and how it works?

remove constant column before spill
add constant column back after restore

Check List
Tests

[x] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

/run-integration-test

/rebuild


Enable containers UI by default

@abonas Please review.

cc @simon3z
Hi @zakiva , you need to enable it in the config file, no change of code is needed.

I think this boils down to add only:
 product:
   maindb: ExtManagementSystem
+  containers: true

in config/vmdb.tmpl.yml. Not sure if we have to do more in order to enable containers in current installations. Maybe we can remove the option completely (or anyway assume true as default), this should make easier the transition from existing installations. /cc @chessbyte

@abonas Should we just enable Containers tab by default at this point?

@abonas Should we just enable Containers tab by default at this point?

@chessbyte , why not?
If there are any concerns regarding this, please let us know.
cc @simon3z @itamarah

@zakiva @abonas The normal way we enable something that was hidden behind a product setting is to remove the check in the code as the product setting is just temporary to allow folks to try unreleased features.  So, no product setting for containers and remove the check.  Thx, Dan

@zakiva Will you be reworking this commit to not make the check in the code for the product setting?  (see above)

@dclarizio Please review

@zakiva what about this code? it still checks for containers
https://github.com/ManageIQ/manageiq/blob/5541cb0bfb1b6c939c3cfbc048d07ba73fe94bf8/app/helpers/application_helper.rb#L1216


chore: enable multiprocessor compilation

Summary of the Pull Request

Speed up C++ source compilation by enabling parallel build
Enable parallel project building on CI

PR Checklist

[x] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Validation Steps Performed

rebuild Release version of the solution

Do we need to update build section in readme?

@htcfreek
no.


The model didnot convergence

Hi, I have the trouble to train the model, the model didnot convergence,. I really need your help, thx very much. my some code:
The optimizer setting:
policies = get_optim_policies(model)  criterion = nn.CrossEntropyLoss().cuda()  optimizer = torch.optim.SGD(policies, args.lr, momentum=args.momentum, weight_decay= rgs.weight_decay)
The transform setting:
`   train_transform = video_transforms.Compose([
video_transforms.Scale((182)),
video_transforms.MultiScaleCrop((160, 160), scale_ratios),
video_transforms.RandomHorizontalFlip(),
video_transforms.ToTensor(),
normalize
])
test_transform = video_transforms.Compose([
        video_transforms.Scale((182)),
        video_transforms.CenterCrop((160)),
        video_transforms.ToTensor(),
        normalize
])`

the Train steps:
`
def train(train_loader, model, criterion, optimizer, epoch):
batch_time = AverageMeter()
data_time = AverageMeter()
losses = AverageMeter()
top1 = AverageMeter()
top3 = AverageMeter()
model.train()
end = time.time()
for i, (inp, target) in enumerate(train_loader):
# measure data loading time
    #show_loader_item(inp, target)

    data_time.update(time.time() - end)
    inp = inp.float().cuda(async=True)
    target = target.cuda(async=True)
    input_var = torch.autograd.Variable(inp)
    target_var = torch.autograd.Variable(target)

    output = model(input_var)
    loss = criterion(output, target_var)
    writer.add_scalar('data/loss', loss, i + epoch * (len(train_loader)))

    # measure accuracy and record loss
    prec1, prec3 = accuracy(output.data, target, topk=(1,3))
    losses.update(loss.data[0], inp.size(0))
    top1.update(prec1[0], inp.size(0))
    top3.update(prec3[0], inp.size(0))

    # compute gradient and do SGD step
    optimizer.zero_grad()
    loss.backward()
    optimizer.step()

    # measure elapsed time
    batch_time.update(time.time() - end)
    end = time.time()
    if i % args.print_freq == 0:
        #for name, param in model.named_parameters():
        #    writer.add_histogram(name, param, i)
        print('Epoch: [{0}][{1}/{2}]\t'
              'Time {batch_time.val:.3f} ({batch_time.avg:.3f})\t'
              'Data {data_time.val:.3f} ({data_time.avg:.3f})\t'
              'Loss {loss.val:.4f} ({loss.avg:.4f})\t'
              'Prec@1 {top1.val:.3f} ({top1.avg:.3f})\t'
              'Prec@3 {top3.val:.3f} ({top3.avg:.3f})'.format(
               epoch, i, len(train_loader), batch_time=batch_time,
               data_time=data_time, loss=losses, top1=top1, top3=top3))

`
Can you help me to check if there are some mistakes?

From the code that you support , I can not figure out the key part which makes a training error.
Maybe you should check LR, policies and input images more carefully.

Thanks for reply, My lr=0.001, and multiply 0.1 every 10 epochs; the policies is same with your code. I will check my code again, thanks again.

hi
did you find the reason. same thing happens to me as well.


Request detailed time usage for individual modules

I'd like to see which module of crab is faster.

crabfetch --benchmark
fastfetch --stat

Also you should use this fastfetch config
{
  "$schema": "https://github.com/fastfetch-cli/fastfetch/raw/dev/doc/json_schema.json",
  "display": {
    "separator": " > "
  },
  "modules": [
    "title",
    {
      "type": "separator",
      "length": 16 // print 16 charactors to match crab
    },

    "cpu",
    {
      "type": "gpu",
      "detectionMethod": "auto" // ignore disabled gpus
    },
    "memory",
    "swap",
    "disk",
    "host",
    "chassis",
    "display",

    "os",
    "kernel",
    "packages",
    "de",
    "terminal",
    "shell",
    "editor",
    "uptime",
    "locale",
    "media",
    "initsystem",
    "processes",
    "battery",
    "localip",

    "break",
    "colors"
  ]
}

Strangely, the default color for fastfetch is green for Arch Linux. I wonder how you made it magenta without specifying it in the config file

the default color for fastfetch is green for Arch Linux
blue, but asides from that the readme uses different configs from the benchmarks,  although colors are the only change

will update configs on the benchmarks wiki later, got other things i would like to focus on asides from rebenchmarking on my laptop once again


Fix typo in gradle dependency

I'm not sure that I made the right correction, but I wanted to at least highlight that it seemed broken the way it was.

Thanks for pointing that out. I was aware anyway. There are more places requiring an update, I'll update them once this is merged to master.

Sounds good.  Hopefully it gets fixed soon.  It took me too much time to figure out that was the source of my problems trying to get the rxjava2.0 branch working.  :)


Need revision to limitations in listed Dataflow documentation

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
Two external documents have to update/revised

[Use Machine Learning and Cognitive Services with dataflows - Power BI | Microsoft Docs] (https://docs.microsoft.com/en-us/power-bi/transform-model/dataflows/dataflows-machine-learning-integration)

Dataflows Limitations, restrictions and supported connectors and features - Power BI | Microsoft Docs

What part(s) of the article would you like to see updated?
Considerations and limitations: (Current List)
AI insights (Cognitive Services and Azure ML models) are not supported on machines with proxy authentication setup.
AzureML models are not supported for Guest users.

*New Considerations and limitations to be added:

The AI features cannot be supported on the Power BI Gateway.
Additional information
No response

@akangsha121 This repository is for docs.github.com and we don't handle chances made to Microsoft docs, so I am going to close this issue now 💛


Radix Sort

Add comment to get assigned to your desired language.
Submission Title
Radix Sort
Submission Type
Algorithm
Submission Description
Write Radix Sort Algorithm
Submission Directory
Algorithm => Sorting => Radix _Sort => Radix_Sort.extension
Language

[x]  C++
[x]  C
[ ]  Python
[x] Java
[ ] JavaScript
[ ] C#

Hey Can i work on Redex Sort

Hey Can i work on Redex Sort

@amintai Language?

Java

Hii, can you please assign me Radix sort in c?
Thank You

Hii, can you please assign me Radix sort in c?
Thank You

Assigned for C

I would like to contribute using C++.

I would like to contribute using C++.

@Dwarikanathmishra Assigned for C++

Can you assign this to me for python ?

Can you assign this to me for python ?

@leli-1 Assigned for Python

Pleas assign C#.

Pleas assign C#.

@nzubair Assigned for C#

Can you assign this to me for python ?

@leli-1 you are assigned for more than 7 days. Still no PR?

Can you assign this to me for java?

Can you assign this to me for java?

@Neha2827 Assigned for Java

please may you assign me this for javascript.

please may you assign me this for javascript.

@verma-shivani Assigned for JavaScript

please may you assign me this for python also.

please may you assign me this for python also.

@verma-shivani Assigned for Python


Adding serverless blog example

PR for https://github.com/vuejs/vuejs.org/issues/1432
CC @sdras
Looking forward to your feedback!

Overall, its a great start! I think this is a great introduction. This is also easy to follow. There are a couple of major things that need to be changed to get the PR through:

We need the initial comment to properly index the recipe (that's probably why all the checks are failing
This doesn't really follow the acceptable format for cookbook entries. It think it's pretty clear we can stray a bit, with the exception of when to avoid this pattern and alternative patterns, which this particular recipe needs in order to sound like documentation and not advertisement
You mention "Serverless" in the title and barely mention it in the article. It either needs to be clarified in the post or removed. At this point, I'm thinking removal makes more sense because it's not a central theme of the article, which seems more based around CMS and blog creation.

@sdras Thanks for the great feedback!  I've made your suggested changes but did have one question.  Regarding your feedback on "when to avoid this pattern" - could you provide more detail in the context of adding a blog to an application?
I could also use a bit more direction on what you're looking for in terms of "Alternative patterns".  Would this be an alternate way to add a blog to your Vue.js app?
Thanks!

@jakelumetta good question! You could probably explore such options as Nuxtent, which allow you to use Vue Component inside your markdown files, which allow you to write and process markdown files instead of using a static site generator like jekyll. That would be a good candidate for a quick compare/contrast or at least mention in case people want to know what their options are.

@sdras Very cool. Wasn't aware of Nuxtent actually, thanks :)
I just added an Alternative Pattern section.  Let me know your thoughts.

This is looking great! We're almost there. I left a few more comments, when we've squared those away, I think we'll be good to merge

@sdras awesome - I've made all of your suggested updates. Thanks for the great editing help. 👍

Perfect! Well done.


Invoking an external script with Nix interpolation

I feel like this is a bit of a hack,
https://github.com/srid/nix-health/blob/0c4735b6403a4fd13ef170f3c21296e05cd32fe5/flake.nix#L21
        packages.default = pkgs.nuenv.mkScript {
          name = "nix-health";
          script = ''
            ${lib.getExe pkgs.nushell} ${./nix-health.nu} ${system}
          '';
        }

nix-health.nu references the system variable, so I'm passing it as a command-line argument. Also, I have to manually pull in pkgs.nushell to invoke the script. Is there a more idiomatic way of achieving this? The main goal is to put the script body in a separate file, whilst still being able to reference Nix variables in scope.

This is still hacky!
You can use substituteAll to replace string instances inside of a file surrounding the replacement targets with @, eg:
foo = pkgs.substituteAll {
  name = "foo.nu";
  src = ./foo.nu;
  system = "${system}";
  nushell = "${pkgs.nushell}";
  nix-health = "${./nix-health.nu}";
}

#foo.nu
@nushell@ @nix-health@ @system@

However, I'm not sure of an elegant way to plug the resulting file into the script value.
Instead you can reuse the same syntax and just use replaceStrings directly on the file contents:
foo = pkgs.nuenv.mkScript {
  name = "foo";
  script = (builtins.replaceStrings
    [ "@system@" "@nushell@" "@nix-health@ ]
    [ "${system}" "${pkgs.nushell}" "${./nix-health.nu}" ]
    (builtins.readFile ./foo.nu)
  );
};

@srid Nushell itself is available in the scripts, so this, for example, should work:
script = ''
  nu ${./nix-health.nu} ${system}
'';

In terms of passing in system, @siph's approach is the only way I can think of that doesn't involve passing them as args in script.

I pushed PR #27 which adds nuenv.writeShellApplication. That accepts runtimeInputs which sets environment variables in the script. Using that feature I think you could do it like this:
packages.default = pkgs.nuenv.writeShellApplication {
  name = "nix-health";
  runtimeEnv = { inherit system };
  text = builtins.readFile ./nix-health.nu;
};

Then in nix-health.nu you would access system as $env.system.

I pushed PR #27 which adds nuenv.writeShellApplication.

Great! I'll see if I can use that to replace this:
https://github.com/srid/nixos-flake/blob/cab6539d198792f94fbac029e5a63523604fd172/nix/nu.nix#L4-L7


ps4eye under Ubuntu 16.04

Ubuntu 16.04 LTS kernel 4.4.0-38-generic

Firmware applied via phyton script - "PS4 camera firmware uploaded and device reset"
lsusb report: http://i.prntscr.com/cc566ce1068540cbb34de4e85eaced7c.png
guvcview reports:

eugene@EBUB:~/ps4eye/script$ guvcview
GUVCVIEW: version 2.0.2
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
GUVCVIEW: couldn't get a valid audio context for the selected api - disabling audio
libv4l2: error turning on stream: No space left on device
V4L2_CORE: (VIDIOC_STREAMON) Unable to start stream: No space left on device
V4L2_CORE: (get_v4l2_frame) video stream must be started first
V4L2_CORE: (get_v4l2_frame) video stream must be started first
V4L2_CORE: (get_v4l2_frame) video stream must be started first
V4L2_CORE: (get_v4l2_frame) video stream must be started first
Thank you in advance!
Eugene

I've got same error with my MacBook Air + Ubuntu 16.04 LTS kernel 4.4.0-38-generic.
Sorry to say, I have no idea to solve this problem right now.
Do you have any idea, users?

Would you please say what kernel / OS will support it for sure? I am considering to setup older platform.

Please see #23 for the reported working environments.
With my pc, newer kernels somehow dont work (see also #19).
The hacked firmware may be the reason of dependency on the environment. Unfortunately I can't do anything with the firmware.
Thanks,

I tried multiple kernels including 3.17.3 and 3.19.0 as recommended, but the outcome is always the same.
And I tested on 2 computers - PC box and laptop.
Both PC and laptop are about are based on i7 26xx CPUs.
I connected camera to all possible USB3 ports, using different hubs.
Do you think I should try some other hardware?

I have just received my Jetson TK1 and tried on it - PS4 Camera works like a charm there.
So these problems might appear hardware dependent.
So trying different hardware solves problem in my case.

Thank you for reporting!


Update docs to reflect Configu v1

Suggestion
The documentation website does not reflect the changes made to the project and the interfaces as part of the release of Configu v1.
List of pages identified as needing an update:

https://docs.configu.com/introduction/overview

The quickstart/interfaces accordion -> interfaces -> internal SDKs -> the copy should be updated

https://docs.configu.com/introduction/concepts

Cfgu - the copy needs to be updated, type is no longer a thing
ConfigStore - ConfigStore Collection seems like a broken link
learn-more-about-configstore

.configu file - broken link
support a wide range of ConfigStores - broken link

ConfigSchema - learn-more-about-configschema

The second paragraph mentions the type cfgu prop which doesn't exist anymore
The examples of schema files are outdated in terms of file structure

Sercert Manager - typo error, should be Secret Manager
Add a section for ConfigExpression

https://docs.configu.com/introduction/workflow

The image shows an outdated schema file structure and the old type property
Export Configurations - Purpose - outdated copy which mentions Configu Proxy & SDKs, quite sure SDKs is wrong now.

https://docs.configu.com/interfaces/.cfgu

The Properties section needs to be updated
The Example section needs to be updated

https://docs.configu.com/interfaces/.configu

The opening paragraph says that .configu files are optional which
Properties - stores - change ref of cache to backup
Properties - cache - change to backup
Example - Change all refs of cache to backup
environment-variables ref to mustache should be removed as we don't use it anymore, we should just generically point to configuration-template-engine without mentioning what engine we use here.

https://docs.configu.com/interfaces/cli/setup

After finalizing cd-cli and installation scripts and decide on dns alias

https://docs.configu.com/interfaces/cli/ref

Search for help dump for clipanion same as in oclif readme

https://docs.configu.com/interfaces/proxy/ref

Update json schema for /export
Add more descriptions and styling
GET /docs - update image due to outdated schema

https://docs.configu.com/interfaces/sdk/overview

Remove node, browser, and common
Rename ts to configu SDK
Enrich readme
Change tsdoc to produce sdk only docs

#601
Add docs for expressions under @configu/integration
https://docs.configu.com/integrations/store/configu

NOTE: all these doc updates should only happen after the Configu Platform is migrated to v1.
Configs Explorer - Upsert Configs Wizard - outdated schema structure in image
Configs Editor

Old ref to SDKs that should be removed.
Editor form image shows old type cfgu prop

Configs History

Evaluating with a tag - the example needs to be updated

https://docs.configu.com/guides/hashicorp-vault

outdated schema file structure

#656

Motivation
The docs must reflect the new state of the Configu Orchestrator to ensure users aren't onboarding with outdated information.

solved by #659


Dart semantic completion doesn't work

I'm using built-in Dart LSP and created TabNine.toml file with this content:
[language.dart]
command = "dart /usr/local/opt/dart/libexec/bin/snapshots/analysis_server.dart.snapshot"
args = ["--port", "9000", "--lsp"]

If I manually start that command it works and I can check it via http://localhost:9000. But VS Code returns me the message which says:
TabNine was unable to start the dart semantic completion backend. The command tried was: `dart /usr/local/opt/dart/libexec/bin/snapshots/analysis_server.dart.snapshot --port 9000 --lsp` This means you need to install the backend manually. For help, see tabnine.com/semantic. Or, type TabNine::no_sem to disable semantic completion for Dart. (TabNine works well even without semantic completion.)

TabNine logs:
[2020-08-02][13:05:17][lsp::language_server_transport][INFO] Starting language server: `dart /usr/local/opt/dart/libexec/bin/snapshots/analysis_server.dart.snapshot --port 9000 --lsp`

What I need to do to be able to run TabNine with Dart semantic completion?

And also in my opinion this should be the default for Dart language because LSP is now part of SDK.

Hi, @svipas
Thanks for pointing this out.
running TabNine with the following TabNine.toml settings:
[language.dart] command = "dart" args = ["/usr/local/opt/dart/libexec/bin/snapshots/analysis_server.dart.snapshot","--lsp", "--port", "9000"]
Language server initialisation fails due to non-supported initialisation param (exception is documented in the status info of the diagnostics server [...is not a folder. Only support for folder analysis is implemented currently.]).
marking this one as a bug for now.


Adding "Ecommerce" Segment with "ProductOverview" and "ProductList" Components

Added "Ecommerce" segment with "ProductOverview" and "ProductList" components. Enhances ecommerce functionality. Please review.

check


[WIP] LLMQs Implementation

This is my current state of the LLMQ implementation. It's for review only and not meant for merging for now. It also contains https://github.com/dashpay/dash/pull/2296. There are also still a few things to do, also in regard to compatibility to the actual DIPs. Some things are not implemented yet and for other things it turned out that the DIPs need to be modified.
If you want to experiment with it, there is the ./qa/rpc-tests/quorums.py script available which will locally start up a few MNs and leave them running until you kill that script. It will generate the necessary blocks to fund the MNs and activate DIP3. After all MNs have been started, sporks are put in place so that you can start testing LLMQs. At this point, no LLMQs have been created yet.
Regtest has a single LLMQ type configured, which creates a LLMQ of size 10 every 24 blocks. Give the DKG enough time (a second per block) when you generate blocks by yourself.
After a LLMQ has been activated/mined, send some TXs around to see LLMQ signing happen.
Connect to the MN network with either RPC or (as I do) a dash-qt instance with this configuration:
datadir=<mydatadir>
regtest=1

# needed if you want to control sporks from dash-qt
sporkkey=cP4EKFyJsHT39LDqgdcB43Y3YXjNyjb5Fuas1GQSeAtjnZWmZEQK

# listen as this dash-qt instance will also act as a MN
listen=1
bind=<IP_ADDRESS>
port=31001
externalip=<IP_ADDRESS>

allowprivatenet=1

# This one might be different on your machine, check out the running MNs and their configs (somewhere in /tmp) to find the correct port
addnode=<IP_ADDRESS>:12001

# Activates the budget system faster (probably not needed, but then it must be removed from quorums.py as well)
budgetparams=240:100:240

# Let's watch all quorums
watchquorums=1

# Let's run dash-qt as masternode
masternode=1

# probably not needed for these tests? We immediately activate DIP3 which then requires BLS keys
masternodeprivkey=cUP3knDebUNdFDRNAivB1Qcw4SQscmQgv7hUTYnuiwk39r3wDieE

######
# Depending on which library/curve you compiled, you'll have to uncomment another line than the one for BN254
# quorums.py will try to guess which public key to use

# herumi BN254
masternodeblsprivkey=3rUD3fbNKJSNtLRnYpBz5DK445DySSspnFuP6K1CoZGSmyyPUsg

# herumi BLS12-381
#masternodeblsprivkey=3sCr2hJEfkyxKjzzxgYcJTSFugnuNsuL2XSASyboKkjQaesGgsy

# chia BLS12-381 (reversed)
#masternodeblsprivkey=3rXqSk3Krgs2sTNZ9peLQJdahBYKb7toBz43hisXKjHMJyLjMu1

Just force-pushed my current version. This version is now based on the current develop branch (v13).
A lot has changed in the code, especially the way I propagate and validate signature shares between LLMQ members. In the previous version, I was directly pushing sigshare batches to intra-quorum connected nodes, without checking if these already have these shares. I did this because the classical INV system would already send around messages of at least 32 bytes size, so I assumed directly sending the shares itself would actually reduce the overhead of the INV system. Turned out it still produces too much overhead and chatter between nodes, especially as we now have switched to BLS12-381 with 96 byte signatures. With this switch, even the classical INV system would probably be better performing then what I did initially (direct push).
Instead of switching the the INV system, I implemented a specialized inventory system for signature shares. It should perform MUCH better and with much less overhead then the general purpose INV system.
Instead of announcing INV items to the other nodes, LLMQ members will now send CSigSharesInv messages to other members. It contains some information to identify the signing session to which the shares belong and a bitset that represents the shares that to offer. Each bit represents a share from a LLMQ member. Bit at index 10 means it's a share from member 10.
Members will now regularly (every 100ms) check which shares were announced by other members and which shares are missing locally and request these from other members. They will also check what other nodes requested and send them these shares. All the communication is leveraging the CSigSharesInv object to reduce overhead to the minimum and to request/announce as many shares as possible in one go. Shares are still sent with the CBatchedSigShares to reduce overhead even further.
Also, in the old version I extensively used the CBLSWorker to speed up things in the handling of signature shares. I removed this and will also remove the use of it in other places later. Turned out that the overhead due to moving BLS primitives around between threads destroys most of the performance gains. Especially now as we switched to BLS12-381, where the primitives got a lot larger.
Instead, I'm leveraging (single-threaded) batched verification as much as possible now. Incoming shares are put into a pending batch and then processed every 100ms. Verification is then done in sub-batches to avoid DoS attacks (an attacker sending 100 valid shares and one last invalid one). I first try to batch together from all nodes and if that succeeds, all shares are accepted. If it fails, I revert to per-node batching to figure out which node sent the invalid shares.
I'll document all this in-code when I find time, as reviewing it will otherwise not be fun.
Another change is how I determine to which nodes to announce shares to. Previously, I only sent shares to members which were determined by the intra-quorum connections selection algorithm. This however had the disadvantage that it only announced shares to outgoing connections and did not take incoming connection from other members into account. As there is no easy way to determine which incoming connection is from a LLMQ member, I implemented something like "if someone ever sends me a share belonging to my quorum, he must be interested in my shares as well, so I announce him all the shares I got from now on". It doesn't necessarily mean it's really a member of the same LLMQ, but its 99% likely.

Also updated the example dash.conf to work with the changes we did in develop


Execution failed for task ':react-native-agora-chat:configureCMakeDebug[arm64-v8a]'.

Description
Hello all, I am trying to build application with  version 0.72 but after installing chat dependency it is showing following error during build
Execution failed for task ':react-native-agora-chat:configureCMakeDebug[arm64-v8a]'.
Version
1.0.11
Output of npx react-native info
System:
OS: Windows 11 10.0.22621
CPU: (4) x64 11th Gen Intel(R) Core(TM) i3-1115G4 @ 3.00GHz
Memory: 956.27 MB / 7.80 GB
Binaries:
Node:
version: 18.12.1
path: C:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm:
version: 8.19.2
path: C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: AI-213.7172.25.2113.9123335
Visual Studio: Not Found
Languages:
Java: Not Found
Ruby: Not Found
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.72.7
wanted: 0.72.7
react-native-windows: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
Steps to reproduce
Started new project with react native version 0.72.7. After installing dependencies of agora it is failed during build.
Snack, code example, screenshot, or link to a repository

Platform

[ ] All
[X] Android
[ ] iOS

SimulatorOrDevice

[X] All
[ ] Simulator
[ ] Device

iOSVersion

[ ] All
[ ] iOS Earlier than 8
[ ] iOS 8
[ ] iOS 9
[ ] iOS 10
[ ] iOS 11
[ ] iOS 12
[ ] iOS 13
[ ] iOS 14
[ ] iOS 15
[ ] iOS 16 or above
[ ] Android Earlier than API Level 23
[ ] Android API Level 23
[ ] Android API Level 24
[ ] Android API Level 25
[ ] Android API Level 26
[ ] Android API Level 27
[ ] Android API Level 28
[ ] Android API Level 29
[ ] Android API Level 30
[ ] Android API Level 31
[ ] Android API Level 32
[ ] Android API Level 33 or above

Due to the space between the name i also faced the same issue so i tried to run the same in D folder directly then the build is successful and the error is also not coming so try to run the project directly in C or D folder


Remove blast in favor of ilpOverHttp

See BlastConfig.java for example.
This ticket relates to #221 and #181

Also see EnabledProtocolSettings. Rename "blast" to "ilpOverHttp" here too, and any other place in the project.


[Bug Report] [Bug Report]'el-time-picker'has a minute style error when the arrow-control property is set, even if the'selectable Range' property is used

Element UI version
0.1.0
OS/Browsers version
chrome 71.0.3578.98
Vue version
2.6.7
Reproduction Link
https://jsfiddle.net/w4p3gn1f/1/
Steps to reproduce
给el-time-picker组件同时设置arrow-control属性和selectableRange属性
分钟选择器的样式错误，不可选的分钟样式未设置未disabled样式
What is Expected?
分钟选择器样式为不可选
What is actually happening?
分钟选择器样式不发生改变

Element UI version=2.5.4

pr welcomed


Facing UserWarning after running the command -> output = model(input_data)

I am having PyTorch 1.9.0 installed with all the other requirements.
In the inference_example.ipynb file. When I run the command -> output = model(input_data)
It throws me a user_warning:-
/home/enord/.local/lib/python3.6/site-packages/torch/_tensor.py:575: UserWarning: floor_divide is deprecated, and will be removed in a future version of pytorch. It currently rounds toward 0 (like the 'trunc' function NOT 'floor'). This results in incorrect rounding for negative values.
To keep the current behavior, use torch.div(a, b, rounding_mode='trunc'), or for actual floor division, use torch.div(a, b, rounding_mode='floor'). (Triggered internally at  /media/nvidia/NVME/pytorch/pytorch-v1.9.0/aten/src/ATen/native/BinaryOps.cpp:467.)
return torch.floor_divide(self, other)
And my system also comes in a hold position, the cursor of mouse stops working, the system performance lacks a lot and after that  the browser collapse.
Please tell me how to resolve this as soon as possible.
I will be very thankful to you.

The user warning is because of a recent torch upgrade that changes the behavior of //. When an operation like b=a//2 is used, this warning is thrown. You can find these operations in positional encoding here.
To avoid this warning, you can update it to b = torch.div(a, 2, rounding_mode='floor')

I am having the same issue after running---------output = model(input_data)
My system start lagging, my system stop working
And I am using Jetson xavier NX torch version is 1.6

@EhrazImam
I am sorry that I don't have any experience with SOM. I am afraid I can't offer any help here. Have you tried with any other PCs/GPUs that you have?


Pipeline updates, testing for .NET 6

Update tests to run .NET 6 instead of 5 #764
New builds by component/feature with path triggers for faster responses (related to #756, but still in devops)
#787

/azp run Steeltoe.All


Refs #35030 -- Added more tests for @user_passes_test decorator.

Extra tests that I want to merge before working on #17621.

@nessita Thanks for checking :+1:


Adding note about GCCH/DOD

Docs Build status updates of commit c24eb7d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/New-CsGroupPolicyAssignment.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit ce76405:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/New-CsGroupPolicyAssignment.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit f069290:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/New-CsGroupPolicyAssignment.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@Kateyanne Please merge this PR. Thanks

Docs Build status updates of commit 6f4630c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/New-CsGroupPolicyAssignment.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit c7e0bfe:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/New-CsGroupPolicyAssignment.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Enable non-interactive use without tty

Running in a non-interactive shell (i.e. on a CI server) is currently not possible, because $(tty) is used for printing and some features.
This patch checks for TTY and calls the corresponding commands without $(tty) when appropriate.
Please check if I missed it somewhere!

Hi, thanks for pointing out this issue.
 In addition, I'm pretty sure (testing now) that the changes in sdm-cmdsubs aren't needed, and the redirection from tty is not needed either. Lastly, sdm-gburn is a completely interactive script, so using tty there is fine.
Will have this checked in later today or tomorrow at the latest.
Thanks again.

Sounds good!
It worked for me with only the changes in sdm.sh, just wanted to be thorough.
Thank you!

In looking at this, I'm not convinced that explicit output to tty is required anywhere, so unless something shows up in my testing today, will be removing it. Everywhere.

Just checked in changes for this. non-terminal input works as expected for --mount, --explore, and --customize. LMK if you run into any issues with it.

I am getting an error now during --customize and --explore. Happens with interactive console and without.
--customize:

...
* Phase 0 Completed
* nspawn into image 'output.img' for Phase 1
systemd-nspawn: unrecognized option '--console'
umount: /mnt/sdm/boot unmounted
umount: /mnt/sdm unmounted

--explore

mount: /dev/loop0p2 mounted on /mnt/sdm.
mount: /dev/loop0p1 mounted on /mnt/sdm/boot.
* nspawn into IMG 'output.img'
systemd-nspawn: unrecognized option '--console'
umount: /mnt/sdm/boot unmounted
umount: /mnt/sdm unmounted

Running on Raspbian Buster on RPi 4B

Hmm...Oh crap. Just realized. systemd-nspawn on Bullseye supports the --console switch. It didn't occur to me that this might be a NEW switch that isn't supported on Buster.
Still waking up here, will have a look at how best to correct this. Stay tuned.

Indeed, sytemd-nspawn V241 is in Buster. the --console switch was added in V242. I'll check the version and avoid using the switch, my only concern is what this might mean for the overall non-interactive usability, but will know that soon enough 🙄

It works perfectly now, thank you very much!

Great, thanks for letting me know and thanks for your support! Since you're running sdm on Buster, just wanted to remind you about the systemd-nspawn compatibility issue between versions: sdm and system-nspawn compatibility


Line : 635 | IndexError | list index out of range

Is there an existing issue for this?

[X] I have searched the existing issues

I'm submitting a ...

[X] bug report
[ ] feature request
[ ] support request --> Contact me over mail for support https://github.com/MShawon

Description
Hi!  I downloaded the last release and i kept getting this error.
Im trying with a random live video and a free proxy list (already passed through proxy checker)
I get this error on "opening  anew driver":
Line : 635 | IndexError | list index out of range

Here are my txts:
GoodProxy.txt
search.txt
urls.txt
Environment
- OS : win
- Python : /EXE withouth Python
- Script version : 1.7.4

config.json
{
    "http_api": {
        "enabled": true,
        "host": "<IP_ADDRESS>",
        "port": 5000
    },
    "database": true,
    "views": 10,
    "minimum": 85.0,
    "maximum": 95.0,
    "proxy": {
        "category": "p",
        "proxy_type": "http",
        "filename": "GoodProxy.txt",
        "authentication": true,
        "proxy_api": false,
        "refresh": 0.0
    },
    "background": false,
    "bandwidth": false,
    "playback_speed": 1,
    "max_threads": 5,
    "min_threads": 2
}

Edit config.json "authentication": true, to "authentication": false,


create ui/ux for choosing whether or not a user wants to share

this will be handled on ticket #146


move miniziti.bash

This will help by providing a predictable URL and download file name and avoid transient link checker failures due to stale GH Pages cache.

Move to static assets or maybe a separate repo so it can have an independent release life cycle.

If we place miniziti.bash in openziti/ziti/quickstarts then it would follow the new BASH quickstart's release versioning lifecycle that's becoming defined in https://github.com/openziti/ziti/issues/898

Would you really classify miniziti as a quickstart in the same sense the others have been defined by? I view miniziti as a local development stack manager. None of the other quickstarts offer a full cli, for example. It also might confuse the issue of what role miniziti should play with regard to the other quickstarts.


Added section on specifying the location of pandoc binaries.

Looks good to me. 👍
@janschulz Feel free to merge once you feel like it. 😄

@gwgundersen (Sorry for the late reply: Germany had some holidays...) There is already some sentence regarding the PYPANDOC_PANDOC right in the installation section: can you include this information in your new section and replace it in the installation section with a small sentence which includes a link to that section? That way it is all in one place :-)

@janschulz, good catch. I've consolidated the sentences into a single section. Please let me know if those sentences don't make sense together.

Thanks for pinging me, this looks great, thanks you!


Ends on should be 7 days by default

Currently, it shows 7 days but not getting updated to 7 days until the user manually updates it to any date(After setting the title and date user will be able to submit the form)
Tasks :-

[ ] Make ends on default value to 7 days

Will be fixed with new task workflow project


Are there plans to remove the restriction of "Omnisharp needs to be restarted after adding a new package reference"

For context, I'm interested in using dotnet-script as a potential replacement for LinqPad based scripting that my company uses today. LinqPad offers a great scripting dev environment, but the CLI environment (based on lprun) is slow to start, Windows-specific, and doesn't provide a great way to split scripts out across files. In contrast, dotnet-script looks like the perfect C# scripting solution!
After reading through the docs for dotnet-script, this is the once piece that seemed like it would be pretty clunky to work with and that it could lead to a lot of developer frustration. Pretty much every LinqPad script we write today leverages a number of NuGet packages, so this would be a heavily-used feature.
Obviously I have no idea what it would take to resolve this issue and whether the "fault" lies with OmniSharp vs. dotnet-script, but consider this a vote for fixing it.

For context, I'm interested in using dotnet-script as a potential replacement for LinqPad based scripting that my company uses today. LinqPad offers a great scripting dev environment, but the CLI environment (based on lprun) is slow to start, Windows-specific, and doesn't provide a great way to split scripts out across files. In contrast, dotnet-script looks like the perfect C# scripting solution!

@madelson I was in the same situation as you. I had lots of LINQPad scripts where LINQPad was mostly used as a low-ceremony (though still a highly capable & productive development environment) alternative to Visual Studio for simple programs. However, I didn't have any run-time dependency on LINQPad and so LPRun, besides being slow, had me unnecessarily locked to Windows and .NET Framework. I wrote LINQPadless as my answer. At the time I published version 1, .NET Core was very new and still going through growing pains. For version 2 of LINQPadless, I wanted to take advantage of .NET Core when it had matured with 2.x so that I could use LINQPad to develop on Windows but eventually have the option to run the code on other platforms when authored in a portable way. This version is in another branch, and while it's still in development (pending some polish and documentation), I am using it for production workloads. I considered using dotnet-script but there was some contention around caching strategies and the dotnet-script maintainers decided to settle on their own pick. There are also some corner cases that C# scripting can't handle so in the end, I decided it may be best to go with the approach of transforming a LINQPad script into a .NET Core console project (transparently and on-the-fly) and run that, with subsequent invocations reusing previous compilations whenever possible. If interested, come join the show. :wink:
BTW, dotnet-script is an awesome project so this is not an attempt to steal any thunder; I use it regularly and follow it with great interest. I am just sharing my journey given that I was once at the same cross-roads that you seem to be now, especially with regards to LINQPad.

Obviously I have no idea what it would take to resolve this issue and whether the "fault" lies with OmniSharp vs. dotnet-script, but consider this a vote for fixing it.

the actual root cause is in the Roslyn compiler - I have a pending PR that will address the root problem https://github.com/dotnet/roslyn/pull/25422
Once that is merged, it will open up some clean ways of handling this.
Basically what happens now, is that assembly dependencies from nuget are scanned upon OmniSharp startup and loaded then. And if you change the nuget directives, they are not picked up anymore, since the compilation model is set (except for #r that directly reference DLLs - not nugets - those are processed in real time). I have been working on a workaround in OmniSharp that will allow Nuget dependencies to be resolved upon saving the file too, which hopefully would improve the behavior.
@seesharper also had a nice prototype of a VS Code plugin that was used to install Nuget dependencies into a script file (sort of Nuget package manager for scripts) - you can find it here https://github.com/seesharper/dotnet-script-vscode/releases.
it allows you to select nuget packages from nuget using command palette and adds the selected version to the CSX as #r. Then it silently restarts OmniSharp for you as part of this "installation". It's sort of a neat way to work around the problem, perhaps you'd find this useful.


Add inmetro.gov.br to the list of domains

Inmetro is a Brazilian national institute that offers Metrology and Biotechnology  Pos-Graduate programs. Both  programs have strong foundations in computer science, where one of the focuses of the programs is to develop solutions for Industry 4.0 . In addition, Inmetro offers a Technical Course in Cyber Security whose general objective is to train professionals in Information Technology, with the ability to investigate and solve problems, applying specific knowledge of Cyber Security, as well as using innovative solutions.

@inmetro-lainf First stage of verification passed, official domain is gov.br as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.


[Debug] Add _DebugDescription macro

Implementation of the DebugDescription macro pitched on the forums: https://forums.swift.org/t/pitch-debug-description-macro/67711. In this initial commit, the macro is named _DebugDescription to indicate it's internal use at this time, pending Swift Evolution.
rdar://115180949

@swift-ci test

@swift-ci test

@swift-ci test windows

@swift-ci test

@swift-ci test

Test failures are due to use of String.contains and CI sets the deployment target to 10.13 where contains isn't available. I will push an update to fix it.

@swift-ci test

@swift-ci test

This pull broke building the stdlib with a compiler with SWIFT_BUILD_SWIFT_SYNTAX disabled, as macros are unavailable then:
stdlib/public/core/DebuggerSupport.swift:36:14: error: macros are not supported in this compiler
public macro _DebugDescription() =
             ^
/home/ubuntu/jenkins/workspace/oss-swift-RA-linux-ubuntu-16.04-android/swift/stdlib/public/core/DebuggerSupport.swift:42:14: error: macros are not supported in this compiler
public macro _DebugDescriptionProperty(_ debugIdentifier: String, _ computedProperties: [String]) =
             ^

Thanks. It seems I should restore the #if $Macros that existed in b2c4c3c4197d98a306cdce51641730df445c0a13.

@finagolfin https://github.com/apple/swift/pull/70351


PropType validation is throwing an error because of RoutingContext

I'm getting the following error for all the props that I am validating:
Warning: Failed propType: Required prop `assetType` was not specified in `AssetManagementShow`. Check the render method of `RoutingContext`.

Warning: Failed propType: Required prop `assetTypes` was not specified in `AssetManagementTransactionsFecher`. Check the render method of `RoutingContext`.

My Routes look like this:
      <Route path='asset_management' component={AssetManagementContainer} >
          <IndexRoute component={AssetManagementIndex} />

        <Route path=':name' component={AssetManagementTransactionsFetcher}>
            <IndexRoute component={AssetManagementShow} />
            <Route path=':transactionKey' component={TransactionsShow} />
        </Route>
      </Route>

I'm getting this error when trying to render AssetManagementShow( and  TransactionsShow).  I'm getting an error from the props of both AssetManagementTransactionsFetcher and AssetManagementShow.
The AssetManagementContainer only fetches data and renders the child route using React.cloneElement. AssetManagementTransactionsFetcher does the same - it fetches data and renders the child route with new props.
I think this is where the problem arises. When I pass props to a child route using React.cloneElement, the child route does not validate its PropTypes properly.
I'm running react-router v1.0.3

Thanks for your question!
We want to make sure that the GitHub issue tracker remains the best place to track bug reports and feature requests that affect the development of React Router.
Questions like yours deserve a purpose-built Q&A forum. Could you post this question to Stack Overflow with the tag #react-router? https://stackoverflow.com/questions/ask?tags=react-router.
We also have an active and helpful React Router community on Reactiflux, which is a great place to get fast help with React Router and with the rest of the React ecosystem. You can join at https://discord.gg/0ZcbPKXt5bYaNQ46.

@taion Thanks for the quick reply. So I'm guessing this is not a bug?
I posted this question a couple of times on reactiflux. The first time somebody told me to file a github issue. The second time nobody responded. I'll try stackoverflow.
Though, how do we assess if something is a bug or a user error?

This isn't a router issue. It's a React issue.

@timdorr do you mind elaborating? If it is indeed a React issue then I'll file an issue there.
Though, the problem seems to be coming from how react-router passes props to child routes. The error references RoutingContext , and I'm not sure how that fits into the picture.

This isn't a bug. If you need a more detailed explanation, either consult the docs or ask elsewhere – not on the issue tracker.


Strange behavior in edit mode

In "My flux", then I click on a edit button (pencil), then I click on the "back" button, it's not the previous page but the statistics page.
Same thing if I click on the "ok" button (the red one), it shows me the statistics page.

The back and "ok" buttons are not contextual
You always return to the feed view, even you if you were on list


Add support for 24-bit RGB and BGR pixel formats

Adds support for the following pixel formats:
/**
 * 24-bit RGB format, [23:0] R:G:B little endian
 */
WL_SHM_FORMAT_RGB888 = 0x34324752,
/**
 * 24-bit BGR format, [23:0] B:G:R little endian
 */
WL_SHM_FORMAT_BGR888 = 0x34324742,

Without this, screenshots appear with the image squeezed in the left $3/4$ of the screen with the colors messed up when using those pixel formats, which sounds similar to this description from #11:

The issue is simply that 1/3 of the screen will be blank when --screenshot is passed and the screenshot will be fit inside the remaining 2/3, which is counterintuitive.

I’ve merged #18 that’s solving a similar problem. Can you please reevaluate whether this PR is still relevant and if it is, rebase it against the current master?

@jirutka I've faced the same issue and looked into this:
#18 is different from this, since the formats implemented in #18 are all 32bit (which is the same size as a pixel expected by cairo). This PR implements 24bit pixels. Since the two sizes are different, one must add extra padding before each pixel, so we end up with the 32bits expected by cairo again

Is it really needed to add a conversion function for every possible pixel format? Isn’t it already implemented in some of the user libraries?

Is it really needed to add a conversion function for every possible pixel format? Isn’t it already implemented in some of the user libraries?

Apparently cairo supports 24-bit formats(https://www.cairographics.org/manual/cairo-Image-Surfaces.html#cairo-format-t), but their selection of formats looks very limited.
Looking at the way grim(https://git.sr.ht/~emersion/grim/) does it, one could use pixman for conversion(They support way more formats than cairo). I don't know however if pixman images can be rendered by cairo.


improves documentation for isDate()

Was confused by the docs which said isDate takes a string. Took some time to figure out correct way. Hoping this helps others avoid that.

It does take a string! The library validates strings only, and your dates are being coerced to a string before validation:
> new Date(2015, 1, 26).toString()
'Thu Feb 26 2015 00:00:00 GMT+0900 (JST)'

The date validator is fairly lenient which may be confusing (#476). Can you provide some examples that you found confusing?

@chriso I see that I didn't investigate enough. My expectation was that isDate would accept any string that works with new Date(). However I ran into the following problem:
 > new Date('2011-12-21')
<· Tue Dec 20 2011 16:00:00 GMT-0800 (PST)

 > isDate('2011-12-21')
<· false

 > isDate(new Date('2011-12-21'))
<· true

While looking into it I found #476, which says to use toDate on strings before passing them to isDate. This worked for the above date, so I made a bad assumption.
 > isDate(toDate('2011-12-21'))
<· true

Is it supposed to be that isDate only accepts strings in the format output by date.toString()?

As noted in #476, the isDate validator uses the built-in Date.parse() function which is very lenient. If Date.parse(str) returns something other than NaN then the validator attempts to filter out invalid dates such as 2015-02-29:
> validator.isDate('2011-12-21')
true
> validator.isDate('2015-02-29')
false

The fact that your validator.isDate('2011-12-21') is returning false is a bug, probably timezone related (#472, #431). What version are you using and what's the result of new Date().getTimezoneOffset() for you? Do any of the unit tests fail (npm test)?

@chriso Version is 4.5.1
> new Date().getTimezoneOffset()
480

One test fails:
  77 passing (256ms)
  1 failing

  1) Validators should validate dates:
     Error: validator.isDate(2011-09-30) failed but should have passed
      at test/validators.js:19:23
      at Array.forEach (native)
      at test (test/validators.js:14:23)
      at Context.<anonymous> (test/validators.js:892:9)

The same input fails in the browser. Here's a screenshot of the inspector:

Thanks. Would you mind applying the following diff and the re-running the tests?
diff --git i/validator.js w/validator.js
index 900e718..cd3b777 100644
--- i/validator.js
+++ w/validator.js
@@ -522,7 +522,8 @@
         } else {
             timezone = iso8601Parts[21];
             if (!timezone) {
-                return null;
+                // if no hour/minute was provided, the date is GMT
+                return !iso8601Parts[12] ? 0 : null;
             }
             if (timezone === 'z' || timezone === 'Z') {
                 return 0;

The following two dates are both valid ISO8601 dates, but Date.parse() parses the first in the user's timezone and the second in GMT:
> new Date('2015-01-01 12:00')
Thu Jan 01 2015 12:00:00 GMT+0900 (JST)
> new Date('2015-01-01')
Thu Jan 01 2015 09:00:00 GMT+0900 (JST)

@chriso tests pass with the patch

Thanks. I've published the fix in 4.5.2. Did you have any other issues/inconsistencies with the validator?

Thanks I'll grab the new version and let you know if I run into any other issues :)

Awesome, thanks!


White spaces around  tag when it inside  tag disappeared with the new version of django-ckeditor

I am upgrading Django1.7 project to Django2.2, so I upgrate django-ckeditor from 4 to 6.0 version (I tried and 5 version)
Now I got the display of my text field, where a tags are inserted without spaces. I couldn't find any settings that would help fix this. I will be very grateful for your help

This sounds like a behavior change of CKEditor itself.


Mark generated constants as unnamed_addr when appropriate

unnamed_addr means that identical constants can be merged. This change reduces the size of optimised binaries by avoiding duplicated constants. Constants with meaningful addresses (e.g. type descriptors) still aren't marked as unnamed_addr.
As a side-effect of this change, different instances of the same string literal now have the same identity. gen_string now caches generated strings in order to have a consistent behaviour on string literal
identity between debug and release builds, since unnamed_addr constants aren't merged in non-optimised builds.

I find this side-effect: "As a side-effect of this change, different instances of the same string literal now have the same identity." to fit nicely with what I expect when using a String literal.

Agreed, this is how I expect string literals to behave.  In fact, now that it works, I'd like to guarantee it as a property of the language.
Can we add a test somewhere that "foo" is "foo"? Doesn't necessarily have to be this PR if you don't think it's appropriate, but I'd like to make it a language guarantee, with a test so that we won't accidentally regress on it, if a user program is depending on this behaviour.

I'm wondering how string literal identity as a language property would interact with distributed Pony. I don't know all the details of object identity in the distributed setting but it seems to me that it would be hard to have that guarantee.

@Praetonus - that's definitely a good question, but possibly one we could resolve when some of the implementation details of distributed Pony are fleshed out a little better.


Session optimizations

Change Description

Removed cache.hpp and moved it entirely into session.  Updated session by rolling all the containers used to managed various state information into 1 container.
Change Type
Select ONE

[ ] Documentation

[x] Stability bug fix

[ ] Other

[ ] Other - special case

Consensus Changes

[ ] Consensus Changes

API Changes

[ ] API Changes

Documentation Additions

[ ] Documentation Additions

Closing this PR as it was much simpler to branch from develop and copy my changes into a new branch off develop than to git merge.  All outstanding comments in this PR should be addressed in the new pr.
The new PR is here:  https://github.com/EOSIO/eos/pull/9600


fix color of version number in docs

This fixes #80 .

Coverage increased (+0.5%) to 88.451% when pulling cb867c8040cdaa0dbc2ccee4e241ecc55547e0f5 on fix-80 into be81e48dc0bc172fd229a9e10029013c0dd3d7fe on develop.

👍 Thanks!


question mark

are you gonna add your visuals and and misc stuff or you're gonna keep it as sdk

soon would be added some functions: a simple rage, legit, and so on


"unsharded" view of XDS

For Istio 1.7, Central Istiod will be a key feature.
The istioctl commands documented in https://github.com/istio/istio/issues/23978 , proxy-status, version, wait, and describe currently contact all of the Istiod pods.  This is not possible without Istiod running in a cluster the user has admin access to.
@costinm suggested using ClusterLoadAssignment to get all of the XDS endpoints.  This works (see discussion at https://github.com/istio/istio/issues/24639 ) but unless there is a flat network it will not be possible to contact the endpoints returned by Cluster Load Assignment.
This work item tracks the implementation of a way that the istio.io/connections, /nacks, and other XDS Event typeURLs can be fetched for the entire mesh via any XDS endpoint.
cc @costinm , @howardjohn

https://github.com/istio/istio/pull/26573


azure-http-specs, add ARM LRO case

fix https://github.com/Azure/cadl-ranch/issues/696
supported both Location and Azure-AsyncOperation

PUT with poll/final-state through Azure-AsyncOperation
DELETE with poll through preferred Azure-AsyncOperation and final-state through Location
Whether you choose to poll/final-state through either of the headers, first equivalent provisioning state be "InProgress", second "Succeeded"

ARM LRO guideline: https://github.com/cloud-and-ai-microsoft/resource-provider-contract/blob/master/v1.0/async-api-reference.md
not covering legacy cases

:x: There is undocummented changes. Run chronus add to add a changeset or click here.
The following packages have changes but are not documented.

:x:@azure-tools/azure-http-specs

Show changes

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs

I don't get this line

DELETE with poll through preferred Azure-AsyncOperation and finalResult through Location

Why DELETE got a finalResult?

I don't get this line

DELETE with poll through preferred Azure-AsyncOperation and finalResult through Location

Why DELETE got a finalResult?

I mean get final-state. In our core, we do have logic for POST/DELETE to get final state when poll succeeded:
https://github.com/Azure/azure-sdk-for-java/blob/8ddf6da837a50543dfcb689887fdd6b1dcf0f8cf/sdk/core/azure-core-management/src/main/java/com/azure/core/management/implementation/polling/AzureAsyncOperationData.java#L181-L185
Mark is also mentioning this pattern: https://teams.cloud.microsoft/l/message/19:906c1efbbec54dc8949ac736633e6bdf@thread.skype/1729624003961?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=3e17dcb0-4257-4a30-b843-77f47f1d4121&parentMessageId=1728977564024&teamName=Azure SDK&channelName=TypeSpec Discussion&createdTime=1729624003961
playground
Do you mean it's uncommon for DELETE to do a get final state?

I don't get this line

DELETE with poll through preferred Azure-AsyncOperation and finalResult through Location

Why DELETE got a finalResult?

Changed description to use final-state instead of finalResult.

I don't get this line

DELETE with poll through preferred Azure-AsyncOperation and finalResult through Location

Why DELETE got a finalResult?

Changed description to use final-state instead of finalResult.

I think for DELETE via AAO, when status=Succeeded, we get the final-state (the resource was deleted). There is no need to follow Location as long as the finalResult is void.
(maybe there is corner case that this flow does have effect, when finalResult is not void, as we had Java code)
I would take majority of this case is for POST, where AAO header is for status (and final-state), while Location header is for finalResult.

I would take majority of this AAO/Location case is for POST, where AAO header is for status (and final-state), while Location header is for finalResult.

Makes sense. Let me update the case be:

verb
lro type
expected polling pattern

PUT
AAO
poll through AAO, get final result through original(resource) uri

POST
AAO+Location
poll through AAO, get final result through Location

DELETE
Location
poll through Location, until 204

this pr has not cover the action operation?

Yeah, I'm going to cover that, see https://github.com/Azure/typespec-azure/pull/1821#issuecomment-2463654211
Let me know your thoughts.

this pr has not cover the action operation?

Added resource action case.

Hi @markcowl , I've addressed your comment, would you help review again?


GeoNode API userinfo endpoint does not work

The o/userinfo endpoint is documented as providing information about the authenticated end user. However, it seems this endpoint is not working.
In order to try this out I have configured a new OAuth application on the staging environment. It is called QGIS Desktop resource owner. Check it here:
https://dev.nexus.geosolutionsgroup.com/en/admin/oauth2_provider/application/
It is using the Resource owner password-based authorization grant type in order to make it easier to test out on the command-line. We ultimately will want to access it with the Authorization code grant type instead. We need this endpoint in order to get details on the current authenticated user inside the QGIS GeoNode plugin. This is needed in order to support performing layer actions from QGIS, for example kartoza/qgis_geonode#120
I've tried accessing it via CLI with the following:
BASE_URL=https://dev.nexus.geosolutionsgroup.com
USERNAME=myusername
PASSWORD=mypassword
CLIENT_ID=clientid
CLIENT_SECRET=clientsecret

TOKEN=$(http --form POST ${BASE_URL}/o/token/ grant_type=password username=${USERNAME} password=${PASSWORD} -a ${CLIENT_ID}:${CLIENT_SECRET} | jq -r '.access_token')
http ${BASE_URL}/o/userinfo/ "Authorization:Bearer ${TOKEN}"

The snippet above uses httpie and jq
I am able to request a new access token and store it inside the TOKEN variable. The request to /o/userinfo is responded by the server with the standard GeoNode error page rendered in HTML, which seems like a defect.

@ricardogsilva a breif report of the outcomes from our review this morning.
The oauth2_provider version currently used in GeoNode comes from our custom geonode-oauth-toolkit module. It was forked because the original one didn't support OpenID.
By the way the OpenID support in our custom module is half implemented. In particular it's not supporting the standard email and profile scopes, and the claims reported inside the id_token do not reflect the additional scopes.
We have found that the original Django Oauth Toolkit now offers the overridable methods to manage these scopes and, consequently, the claims. It was introduced with the long waited OpenID support which was merged (and release with 1.5.0) 23 days ago :)
It could be the right moment to get rid of our fork, but we need to accurately check any customization that was done on our side. In particular @afabiani noted that something was changed specifically to support the authentication from QGIS.
 However I will create a task to investigate the replacement of geonode-oauth-toolkit. If it proves too much demanding we will eventually try to implement the management of the additional scopes and claims inside it.

@ricardogsilva @giohappy just did a test against GeoNode master branch using the new dependencies.
The sample request provided by @ricardogsilva by default returns just the user id
Content-Language: en
Content-Length: 15
Content-Type: application/json
Date: Wed, 19 May 2021 16:37:30 GMT
Server: WSGIServer/0.2 CPython/3.8.5
Set-Cookie: sessionid=ouq74mjgf3naev35bksfifwfo3750dc6; expires=Wed, 02 Jun 2021 16:37:30 GMT; HttpOnly; Max-Age=1209600; Path=/; SameSite=Lax
Vary: Authorization, Accept-Language, Cookie, Origin
X-Content-Type-Options: nosniff
X-Frame-Options: ALLOW-FROM ALL
X-XSS-Protection: 1; mode=block

{
    "sub": "1000"
}```

@giohappy @ricardogsilva by providing the following custom Oauth2Validator
class OIDCValidator(OAuth2Validator):

    def get_additional_claims(self, request):
        return {
            "sub": request.user.email,
            "first_name": request.user.first_name,
            "last_name": request.user.last_name,
        }

the outcome is the following one:
HTTP/1.1 200 OK
Content-Language: en
Content-Length: 53
Content-Type: application/json
Date: Wed, 19 May 2021 16:58:08 GMT
Server: WSGIServer/0.2 CPython/3.8.5
Set-Cookie: sessionid=p5dl97cxhw572p380euo9uqrm86wbdua; expires=Wed, 02 Jun 2021 16:58:08 GMT; HttpOnly; Max-Age=1209600; Path=/; SameSite=Lax
Vary: Authorization, Accept-Language, Cookie, Origin
X-Content-Type-Options: nosniff
X-Frame-Options: ALLOW-FROM ALL
X-XSS-Protection: 1; mode=block

{
    "first_name": "",
    "last_name": "",
    "sub"<EMAIL_ADDRESS>}

One thing that we will need, in scope for the QGIS  GeoNode plugin is some way to retrieve the user permissions for resources. With this in mind I guess the user id is likely also a useful thing to show in the response of the userinfo endpoint.
We will likely then use the user id to do permission checks on the layers loaded in QGIS to see if the user is allowed to modify them.

@ricardogsilva permissions on resources are now returned inside the perms property of a resource.

@ricardogsilva I invite you to check the current status on this and report any update.


Import measures through UI gives error

I am trying to import a measure by using admin/measures pagein PopHealth. I am using HQMF file (examples attached here
CMS22v5.xml.txt
CMS22v5.xml.txt
d here).

It is giving error Error importing measure
unknown document type

Is this correct way and format of attaching the file?
MD

@dabimahesh - when we wanted to import measures, I remember having to create my own bundle.  I ran into similar errors trying to import XML files directly.  The bundle was a zip file which contained the measure logic in a JSON format, and also had the value sets.  I used the Bonnie tool to create the measure JSON files.  I know Bonnie has been updated to work with CQL, so the newest version may no longer work with HQMF XML files.  I was using an older version (~1.3), but I think you could use the latest v1.X branch: https://github.com/projecttacoma/bonnie/tree/v1.6.12
Once I had the measures loaded into Bonnie, I would do the following to build a bundle:
a.  Export the bundle from Bonnie
b.  Extract the zip file
c.  Edit the bundle.json to have the right version and description
d.  Remove the test patients from the directory and bundle.json
e.  Zip up the bundle.  From the directory where the bundle files live (not a level above) run:  zip -r ../my-bundle-1.0.0.zip .

@lrasmus - Have you added just one single custom measure to the existing measures that are already loaded?  Or is it always been just import a new custom measure bundle?

Hi
I tried to import one measure (old version). Latest bundle is already there.
Thanks
Mahesh
On Tue 11 Sep, 2018, 19:45 peter li<EMAIL_ADDRESS>wrote:

@lrasmus https://github.com/lrasmus - Have you added just one single
custom measure to the existing measures that are already loaded? Or is it
always been just import a new custom measure bundle?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/OSEHRA/popHealth/issues/149#issuecomment-420289899,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAa39i6bY-Wh-vM8QxhygQq_ht4HM88Pks5uZ8WRgaJpZM4Wg0Eu
.