Ref Issues

If you are trying to reference data on the same page, you need to use quotes
When content updates, Mosaic crashes stating there is a circular ref.

i think is caused by the mdx serialiser.  If the value is not a string then it gets changed to null by the serialiser.  Related -- > https://github.com/kentcdodds/mdx-bundler/issues/72

Is caused by the SharedConfigPlugin.  Not sure what causes it exactly but when that plugin is enabled, updating content breaks....

Actually looks like its not the sharedconfigplugin...but normalisation of refs
On second pass I see a page has a ref to itself, but that ref is for an index page that is using a wildcard reference


[Backport 2.x] Bump org.apache.logging.log4j:log4j-core from 2.19.0 to 2.20.0 in /buildSrc/src/testKit/thirdPartyAudit/sample_jars

Description
Manual backport of #6490
Issues Resolved
N/A
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #6503 (1378043) into 2.x (1eb5b22) will increase coverage by 0.09%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##                2.x    #6503      +/-   ##
============================================
+ Coverage     70.35%   70.45%   +0.09%
- Complexity    59247    59334      +87
============================================
  Files          4797     4797
  Lines        284416   284416
  Branches      41328    41328
============================================
+ Hits         200115   200373     +258
+ Misses        67538    67300     -238
+ Partials      16763    16743      -20

Impacted Files
Coverage Δ

.../org/opensearch/client/indices/AnalyzeRequest.java
31.00% <0.00%> (-45.00%)
:arrow_down:

...nsearch/rest/action/cat/RestCatRecoveryAction.java
43.61% <0.00%> (-42.56%)
:arrow_down:

...h/action/ingest/SimulateDocumentVerboseResult.java
60.71% <0.00%> (-39.29%)
:arrow_down:

...cluster/coordination/PublishClusterStateStats.java
33.33% <0.00%> (-37.51%)
:arrow_down:

...search/search/aggregations/pipeline/EwmaModel.java
24.44% <0.00%> (-33.34%)
:arrow_down:

.../java/org/opensearch/index/reindex/RemoteInfo.java
50.45% <0.00%> (-29.36%)
:arrow_down:

...a/org/opensearch/index/mapper/MapperException.java
75.00% <0.00%> (-25.00%)
:arrow_down:

...x/snapshots/blobstore/RateLimitingInputStream.java
60.00% <0.00%> (-25.00%)
:arrow_down:

...pensearch/index/mapper/MapperParsingException.java
77.77% <0.00%> (-22.23%)
:arrow_down:

...a/org/opensearch/transport/netty4/Netty4Utils.java
42.42% <0.00%> (-21.22%)
:arrow_down:

... and 453 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Can't detect HiDiffusion package

I am on Windows, trying to use HiDiffusion. After installing the Pip package, my system is unable to resolve the hidiffusion import, when trying to follow the instructions on the Readme.
Within my IDE:

Import "hidiffusion" could not be resolved

Example from my console:

F:\Localllm\AlternateInference> pip install hidiffusion --no-cache-dir
WARNING: Skipping C:\Users---\anaconda3\Lib\site-packages\torch-2.2.0.dist-info due to invalid metadata entry 'name'
Collecting hidiffusion
Downloading hidiffusion-0.1.5-py3-none-any.whl.metadata (15 kB)
Downloading hidiffusion-0.1.5-py3-none-any.whl (32 kB)
WARNING: Skipping C:\Users---\anaconda3\Lib\site-packages\torch-2.2.0.dist-info due to invalid metadata entry 'name'
Installing collected packages: hidiffusion
Successfully installed hidiffusion-0.1.5
PS F:\Localllm\AlternateInference> & C:/Users/--/AppData/Local/Programs/Python/Python310/python.exe f:/Localllm/AlternateInference/inference_engine/image_inference.py
Traceback (most recent call last):
File "f:\Localllm\AlternateInference\inference_engine\image_inference.py", line 1, in
from hidiffusion import apply_hidiffusion, remove_hidiffusion
ModuleNotFoundError: No module named 'hidiffusion'

I have attempted to use pyenv, and conda environments, as well as setting the python version to 3.8, as opposed to my system default of 3.10. Here we have the end of the install from a requirements.txt I put up from the requirements listed on the instructions. I have marked where hidiffusion is among these items. I have attempted to restart the IDE, the terminal, and my machine, and haven't seen a change with my system being unable to detect hidifussion, despite being installed via pip:

Installing collected packages: mpmath, hidiffusion, zipp, urllib3, typing-extensions, sympy, safetensors, regex, pyyaml, psutil, Pillow, packaging, numpy, networkx, MarkupSafe, idna, fsspec, filelock, colorama, charset-normalizer, certifi, tqdm, requests, jinja2, importlib-metadata, torch, huggingface-hub, xformers, tokenizers, diffusers, accelerate, transformers
Successfully installed MarkupSafe-2.1.5 Pillow-10.3.0 accelerate-0.29.3 certifi-2024.2.2 charset-normalizer-3.3.2 colorama-0.4.6 diffusers-0.27.2 filelock-3.13.4 fsspec-2024.3.1 hidiffusion-0.1.5 huggingface-hub-0.22.2 idna-3.7 importlib-metadata-7.1.0 jinja2-3.1.3 mpmath-1.3.0 networkx-3.1 numpy-1.24.4 packaging-24.0 psutil-5.9.8 pyyaml-6.0.1 regex-2024.4.16 requests-2.31.0 safetensors-0.4.3 sympy-1.12 tokenizers-0.19.1 torch-2.2.2 tqdm-4.66.2 transformers-4.40.1 typing-extensions-4.11.0 urllib3-2.2.1 xformers-0.0.26.dev778 zipp-3.18.1
(imageinference) F:\Localllm\AlternateInference\inference_engine>

After working through trying to get some updates going to see if it was just some environment issues, I attempted to run it again, and this time got:

(imageinference) F:\Localllm\AlternateInference\inference_engine>python image_inference.py
Traceback (most recent call last):
File "image_inference.py", line 1, in
from hidiffusion import apply_hidiffusion, remove_hidiffusion
File "C:\Users---\anaconda3\envs\imageinference\lib\site-packages\hidiffusion_init_.py", line 1, in
from .hidiffusion import apply_hidiffusion, remove_hidiffusion
File "C:\Users---\anaconda3\envs\imageinference\lib\site-packages\hidiffusion\hidiffusion.py", line 9, in
from diffusers.utils import USE_PEFT_BACKEND, replace_example_docstring
ImportError: cannot import name 'USE_PEFT_BACKEND' from 'diffusers.utils' (C:\Users---\anaconda3\envs\imageinference\lib\site-packages\diffusers\utils_init_.py)

Am I missing something?

The last problem seems that you cannot import USE_PEFT_BACKEND from diffusers. Is your diffusers version==0.27.0. Or you can try diffusers version==0.25.0

Somehow I had 0.27.2. Updating to 0.1.6 of hidiffusion and 0.27.0 of diffusers resolved the issue. Thank you.


Add [failing] test for emoji-titled headers

This provides an example of the problem described in https://github.com/thlorenz/doctoc/issues/191. Hopefully with the fix described in https://github.com/thlorenz/doctoc/issues/191#issuecomment-1207293548, this will soon pass!
also...
Add launch.json to enable test debugging
For codespaces/VS Code. This was very helpful in diagnosing https://github.com/thlorenz/doctoc/issues/191.
Based on approach taken in https://stackoverflow.com/a/39607924, though the port stuff wasn't necessary anymore.

Hi great work @kevin-david on reproducing this in a test.
I'd love if you can take a stab at fixing this as well as I currently don't have bandwidth to address it.
Thanks.

Hey @thlorenz this should be fixed by my previous change in https://github.com/thlorenz/anchor-markdown-header/pull/45 - I'm actually using my private fork at the moment, but I would love to clean that up!
We just need a new release of https://www.npmjs.com/package/anchor-markdown-header so I can consume it here, is that something you can do? Happy to update this PR to non-draft mode once that's done (with this test now passing)

Thanks, is this ready to be published to npm?

I think so, I've been testing this for a while with my fork and haven't seen any issues!


Replace combine/separate mappings with ability to group source/target fields

Part of epic #248
It has always seemed confusing to me that we've give the user the ability to combine or separate source or target fields via mappings, but all other types of transformations are accomplished via later field actions.  I would rather see a more generic ability to group fields from source or target via an action and eliminate the user's need to specify a specific type of mapping. Thus, for example, to combine source fields into a single target field, the user would still use the same DnD/selection process they do now to indicate when multiple fields are involved, but we'd simply automatically create a grouping action containing the source fields instead of creating a special combine mapping. This would simplify the details view, and a longer-term goal would be this generic grouping action could also be used later in the action chain.

See comments from #95
i.e.
This is what I've got - if a user attempts multiple mappings (map mode) to the same target element then it's flagged with an error. In this example I have an existing mapping beween source element addressLine1 and target element fullAddress and then attempt to map addressLine2 to* fullAddress*:

If a user attempts multiple combine-mode mappings to a single target then it's allowed. The user specifies the compound-selection by using M1 for the first element and ctrl-M1 for each subsequent element. The combine index is calculated as +1 from them previous index:

If a user wishes to de-select an element then they press ctrl-M1 on a previously selected element:

Note that the user must be in Combine mode.
Q: If a user is not in combine mode and presses ctrl-M1 - should we automatically change into combine mode as a convenience or should we flag an error?
Q: How should the index be refactored if a user removes an element in the middle from a combine? If element 3 is removed should we just leave the generated XML as specifying 1,2,4,5?
A similar (not yet prototyped) effort would occur for Separate mode where a single Source element would separate into multiple Target elements via ctrl-M1.

Since we support the ability for the user to designate a separator token in both combine and separate modes, we'll still need the action defined in the mapping details section of the UI.  The other related item we support is the ability to order - not just group - the elements.  This appears to me to be the most clumsy part.  What if we remove the Index and allow the users to drag the elements into the desired order with the mapping details section?

Yep, separate/combine requires a special mapping action which would have delimiter as a parameter. It would require a significant UX change there. And +1 on removing row index input from form and rely on drug&drop for the field order.
One thing we also need to support is to allow skipping some of those, e.g:

split one string into 5, but only want 2 and 4 at target side
combine 3 string source fields and generate a CSV line at target side, but want to leave 3rd and 5th empty

By the way, although current separate/combine only supports simplest delimiter stuff, #46 is also going to be one of action we should support for the combine case.

@jpav @igarashitm @pleacu
Hi, I create a wireframe for this issue, https://redhat.invisionapp.com/share/W2O9AZS8Y4G#/322055380_One-To-One1
This version is update based on our last UX review meeting.
Please help to review it. Thank you~

Thanks @deernano, added 2 comments - I think we're almost there :)

@igarashitm @jpav @pleacu @heiko-braun
Hi, I updated the wireframe for this issue to the latest version. https://redhat.invisionapp.com/share/W2O9AZS8Y4G#/322055150_Design-Change1
Please review and confirm it. Thank you~

@igarashitm Is this something you plan for 7.4?

Yes, @pleacu is already working on this.

I think now main part is done, leftovers from design sketch are #895 and #912 but we can say these are separated enhancements. Moving this to Done.


source compatibility project Deferred fails with a compiler error

Description
/build/swift-source-compat-suite/project_cache/Deferred/Sources/Deferred/Executor.swift:129:13: error: 'getCFRunLoop' is inaccessible due to 'internal' protection level
127 |             perform(body)
128 |         } else {
129 |             getCFRunLoop().submit(body)
    |             `- error: 'getCFRunLoop' is inaccessible due to 'internal' protection level
130 |         }
131 |     }

Reproduction
builds:
https://ci.swift.org/job/swift-6.0-source-compat-suite-debug-ubuntu-2004/121/
https://ci.swift.org/job/swift-6.0-source-compat-suite-ubuntu-2004/121/
https://ci.swift.org/job/swift-source-compat-suite-debug-ubuntu-2004/499/
https://ci.swift.org/job/swift-source-compat-suite-ubuntu-2004/599/
log: https://ci.swift.org/job/swift-6.0-source-compat-suite-debug-ubuntu-2004/121/artifact/build/swift-source-compat-suite/FAIL_vapor_routing_4.2_BuildSwiftPackage.log
Expected behavior
should build fine
Environment
CI
Additional information
No response

Caused by #4927.


[HW] Dovile Perednyte

Name: Dovile Perednyte
Email<EMAIL_ADDRESS>Linkedin Profile: https://www.linkedin.com/in/dovile-perednyte-65641b17a/
Attach the homework step I screenshots below:

Looking good! Thanks Dovile!

Hey Dovile Perednyte, great job! Congrats! Here is your badge! https://api.badgr.io/public/assertions/VJGoijLMQHWW1mQWiW2g7g


Errors on LiveView mount are reported twice

When raising an error on the LiveView mount hook it gets reported twice and generates two occurrences instead of one. The occurrences are generated from the following Phoenix telemetry events:

[:phoenix, :router_dispatch, :exception]
[:phoenix, :live_view, :mount, :exception]

Is this due to the fact that mount is called twice, once for the initial page view and again when the websocket connects ?

This is correct @tjarratt. I meant to close this issue past week but then I forgot about it.
Since mount is called twice, the errors are reported twice as well. Just like any function throwing an error would report the error every time it is called.


Build aborts because iTunes Connect still processing

Hi
We've got apps building through Bitrise using this step, but the build aborts because it sometimes hits the 45 minutes whilst waiting for iTunes Connect to finish, as sometimes that part seems to take an hour or so. The app is uploaded fine, so is there any way we could get an option that tells this step on Bitrise to not wait for iTunes Connect to say its 100% finished?

Yes, that's actually disabled by default, I think you enabled it at some point, the option is: submit_for_beta - https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/blob/master/step.yml#L91

We've got that disabled already.

Could you please send us the full build log in email / through onsite chat?


question from another other python dev

i starred the repo, anyway
why are you using tls_client and not requests?

tls_client is better and safe
using requests may disable our discord account.


How to Extend Colours?

How can we add a colour to the default colours model?
Should we create a new database for new colours? or add in the app settings metadata?

@creecros Hello, any input on your side for the above questions?  If you could use the app model to create a random colour for me, I can then look into the code and make more colours.  I have no idea how to work with the model.
So far, the plugin displays the default colours in a settings page with the values and now also the dropdowns show the coloured boxes.

https://github.com/creecros/Group_assign/blob/master/Model/GroupColorExtension.php

There is also a hook, you can just add colors using the hook:
https://github.com/kanboard/kanboard/blob/7c0a239ec399124207b86fcd6b22ade38c5c7574/app/Model/ColorModel.php#L157

There is also a hook, you can just add colors using the hook:
https://github.com/kanboard/kanboard/blob/7c0a239ec399124207b86fcd6b22ade38c5c7574/app/Model/ColorModel.php#L157

I saw this but how do I work with it? it's not the same as a template hook.
$this->hook->reference('model:color:get-list', $listing);

Should I code?
$this->hook->reference('model:color:get-list', config/new-colours);   // plugin template file

then the plugin template file contains text fields with manual colour values that it can add to the list

I've been playing with it for the hour and have yet to figure it out

I figured it out, I'll explain it once i get a moment to fully explain it.

It should be updated now so that you can easily add colors.
what you can do now is instead of hard coding the colors into the plugin, use metadata and allow people to add their own colors.

Im also proud to say, i did it with 0 overrides

It should be updated now so that you can easily add colors.
woaaah thanks! let me study that...

what you can do now is instead of hard coding the colors into the plugin, use metadata and allow people to add their own colors. (this might be tricky if you don't know what you are doing, because you going to need arrays and metadata columns do not save array data, only strings. You will need to convert array to string when saving and string to array when reading.)
will consider... i am doing this colours thing because of my tags plugin as i have x amount of tags with customcss colours which i am thinking i will add to the protected function you created and see how i can play with it (the white and maroon were tests, which might hold my customised list... will test)

@creecros Is this hook still needed after the latest commits?
https://github.com/aljawaid/KBColours/blob/691778c880216de4999a0bcf3013e2bb440d0fcd/Plugin.php#L31


Query param to select address

Open specific address via query parameter. This is nice to be able to share wallet analytics via link.

You can now get analytics for a any address at merklin.xyz/address/0x...


Conda install of 0.12.0 points at example manifest from main

Workaround for conda:

https://github.com/conda-forge/rerun-sdk-feedstock/pull/23

Proper fix in Rerun repo:

https://github.com/rerun-io/rerun/pull/4781


change DB and TX to interface

Both DB and TX are structure and should be modified to common interface.
Insert, Select, Update statements should be provided on the interface.

Perhaps you are looking for https://pkg.go.dev/github.com/uptrace/bun#IDB

@vmihailenco yes thanks


test(e2e): check whether rule-evaluator reload was successful

Resolves https://github.com/GoogleCloudPlatform/prometheus-engine/issues/765 by checking both rule-evaluator status and config-reloader logs.
Most code was simply revived from the original e2e tests: https://github.com/GoogleCloudPlatform/prometheus-engine/pull/747
Help prevent situations such as: https://github.com/GoogleCloudPlatform/prometheus-engine/pull/763

Investigating test failures...

That's a really great idea, and it would help out Autopilot users who are forbidden from port-forwarding the pod and hitting the endpoint directly. I think this warrants a deeper design discussion, though. For example, why reload status in the OperatorConfig and why not rule status in the individual Rule objects which would be more granular?
That's indeed true. My concern is that if GCM testing is disabled in e2e tests by default, it will not be caught. The other benefit of these tests is that they're more specific: you know which component (rule-evaluator vs. config-reloader vs. gcm) was responsible for the failure.

Ultimately, I would still like to move forward with these tests to unblock testing the rule-evaluator compression changes. Once we make a more concrete decision, it will be trivial to remove these tests.

Converting to draft until https://github.com/GoogleCloudPlatform/prometheus-engine/pull/894 is merged!

Ready for review now!


policy with a long name not working properly

https://github.com/open-cluster-management/backlog/issues/10215

This seems reasonable to me to add to this fix:

It seems reasonable to check the length of . and warn the user eventually, because there are namespaces having more than 10 characters.
https://github.com/open-cluster-management/backlog/issues/10215#issuecomment-796706119

@ChunxiAlexLuo Can you please update this error message as well https://github.com/open-cluster-management/grc-ui/blob/main/tests/cypress/config/InvalidYamlTests/invalidYamlErrors.yaml#L2?


Start SATRE WP1 doc (draft reference architecture)

[x] coordinate with WP1 and see if anyone else is already doing this
[ ] create an overleaf doc github pages with sphinx for this repo and start by copying in the agreed TRE features from the TRE survey

[ ] draft some paragraphs that describe these
[ ] also include and repurpose the comparison paper

See PR: https://github.com/sa-tre/satre-specification/pull/8


common/resolver: resolve an address or url

Codecov Report

:exclamation: No coverage uploaded for pull request head (dbentley/resolver@35e93d4).

Continue to review full report at Codecov.

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


support cargo's --manifest-path

self-explanatory. issue raised in #95

Could you fix CI/clippy errors?

Could you fix CI/clippy errors?

The clippy warning is not related to this change. Just a new warning on nightly.
https://github.com/rust-embedded/cargo-binutils/pull/147/files

Correct, I think none of the failing CI scripts have to do with my changes. I built and installed this on my machine on latest rust stable without any issues.
One more comment because i noticed it with my current work that uses cargo-binutils:
Some of the flags that are re-implemented from cargo, like --release and --no-default-features are not implemented correctly, they still require a value instead of just working as a flag.
With clap, the Arg builder needs this additional setting: .action(ArgAction::SetTrue), and it also should be retrieved as a flag instead of a normal .get_one() parameter.
The current workaround is to pass --some-cargo-flag true (or any other value).


Datagrid: return all selected row data together

What will this achieve?
Follow up issue to https://github.com/carbon-design-system/ibm-products/issues/2909, this enhancement would return all of the selected row data similar to how selectedRowIds returns an array of selected row ids.
How will success be measured?
When datagrid is able to return an array of select row data.

To add.  All the selected row data across multiple pages should be returned.
Example.  Pagination enabled, table re-renders with subsequent page scroll and user is selecting items.  Selection count should be tracked across pages and returned with this new function.

That is correct @vnikiten01, it will return all rows across pages if pagination is included.

There is a challenge in keeping selectedRowIds and selectedRowData (assuming that's the name for the proposed state) in sync in case of providing initial selections (initialState.selectedRowIds), along with server side pagination.
In this case, the initial selections may include some ids that are not available in the first page of data. Since the Datagrid cannot find the rowData for all the selectedRowIds the size of these objects is not guaranteed to be the same, so they are likely to not be in sync.
// Assume:
// Server-side pagination, 2 per page
// Server data: [
//     { id: 1, name: 'Bob' },
//     { id: 2, name: 'Joe' },
//     { id: 3, name: 'Dave' },
//     { id: 4, name: 'Dan' },
//     { id: 5, name: 'Alice' },
// ]
// initialState.selectedRowIds: { 1: true, 5: true },
// initialState.pageSize: 2
// State will look like:
{
    selectedRowIds: { 1: true, 5: true },
    selectedRowData: {
      1: { id: 1, name: 'Bob' }
      // Maybe 2: null?
    }
}

In this example, the problem is that "Alice" (id: 5) should be selected, but the Datagrid cannot find the rowData for that selection, until it reaches a page where id: 5 is present and get the rowData from there, therefore selectedRowData is missing a selection.
Therefore, it is likely that selectedRowData might be missing some selections (or all the selections), which questions its usefulness if it might contain false information and we still need selectedRowIds to get the actual selections.
@matthewgallo  Are you aware of this limitation and is there a plan for this?
IMO this problem is a blocker from implementing a logic that returns all of the selected row data. We can probably ignore the initial selections and return the user selected row data, the rows that user has manually selected by clicking on the checkbox, but that's something different.


Make Recurrence implement JsonObject

Currently, Recurrence class doesn't implement JsonObject interface.

@vishnuinfrrd
It's true that Recurrence does not implement JsonObject.  How is that impacting you? Can you explain why you want it to, and how you are relying on JsonObject?  Currently, it seems to me that JsonObject is unnecessary and I am considering deprecating and removing it.

@ddlatham I was getting below error when I tried accessing messages().list()

com.fasterxml.jackson.databind.exc.InvalidDefinitionException: No serializer found for class com.nylas.Event$Recurrence and no properties discovered to create BeanSerializer (to avoid exception, disable SerializationFeature.FAIL_ON_EMPTY_BEANS) (through reference chain: com.nylas.Message["events"]->java.util.ArrayList[0]->com.nylas.Event["recurrence"])

However, I could get rid of this error by setting spring.jackson.serialization.FAIL_ON_EMPTY_BEANS=false in application.properties file.

@vishnuinfrrd Apologies for not getting back to you sooner.
That looks like an error trying to serialize a Message using the Jackson JSON library.  The Nylas Java SDK doesn't use jackson at all internally (rather, it uses Moshi for JSON serialization).  So I'd guess that something else in your application is trying to serialize the Message object using Jackson.  Does that sound right?  If not, can you share a more complete stack trace including the entry point into the the Nylas SDK code?
I did try to reproduce it or any other problem with listing Messages containing Events that have Recurrences and have not been able to reproduce any problem.

Thanks @ddlatham for the updates.
Will check this and get back to you if we need any help.

Closing.  Let us know if there is more needed here.


Optimize RustStr's Equatable implementation

Addresses #148.

I addressed your review. Sorry...

Great work!


How to load checkpoint and continue training?

How should I continue to execute 20000 rounds of training (similar to finetune's idea) after the 20000 rounds of fine training have ended?

I'm working on it, code will be updated soon!

Hi, this is a new PR.
I've checked it on the bouncingballs. I'd appreciate it if you could help me recheck it or use the code on your custom dataset.


one problem and some  questions

problem
typo
Version 8.1.0
Support StanSanple.jl v5.3 multithreading in cmdstan

question 1:   how to plot  model

how to use julia's DataFrame'object at  stan model

Hi @math4mad ,
Thanks for pointing out the typo, I'll fix it in the next release. As this is way down in the "Versions" section of the latest release (I think), which version of Stan.jl are you looking at?
In any case, plotting is not really part of Stan.jl or StanSample.jl as there are many options in Julia. I these days mostly use Makie and Pluto in projects such as RegressionAndOtherStories. Although relatively new, that might be a good start the understand how to plot and use DataFrames with Stan.
Do you have Stan's CmdStan installed and built? Which platform are you using (Linux, MacOS, Windows)?
Rob

Hi @math4mad ,
Thanks for pointing out the typo, I'll fix it in the next release. As this is way down in the "Versions" section of the latest release (I think), which version of Stan.jl are you looking at?
In any case, plotting is not really part of Stan.jl or StanSample.jl as there are many options in Julia. I these days mostly use Makie and Pluto in projects such as RegressionAndOtherStories. Although relatively new, that might be a good start the understand how to plot and use DataFrames with Stan.
Do you have Stan's CmdStan installed and built? Which platform are you using (Linux, MacOS, Windows)?
Rob

about typo  In Versions sections, I  find  since  ver9.5.0  has problem .

about  plot.   Actually , my question is : I  don't know  how to extract  params.  better has some demo

makie is great library,  maybe  contribute  a demo  to beautiful.makie.org

Yeah , I already built and  installed   CmdStan , several demos work fine.   My computer is m1  MacBook Pro. MacOS:12.6 . When I installed c++ tool chain  application from  github , got  error information, I don't know why , but when  I test   command, it works!.  I remember last year I  installed an  cross-platform application  framework. here  it is Tauri. Seems another way  to install c++ tool chain for MacOS . Many people stuck in this place?

As for  installation,  this repo stan in docker  is a  good  routine.

Hi @math4mad
Maybe it is better to use a MWE:
# StanSample & GLMakie must be available from your environment.

using StanSample, GLMakie

model = "
data {
  int<lower=0> N;
  int<lower=0,upper=1> y[N];
}
parameters {
  real<lower=0,upper=1> theta;
}
model {
  theta ~ beta(1,1);
    y ~ bernoulli(theta);
}
";

sm = SampleModel("bernoulli", model);

data = Dict("N" => 10, "y" => [0, 1, 0, 1, 0, 0, 0, 0, 0, 1]);

rc = stan_sample(sm; num_chains=4, data);

if success(rc)
  df = read_samples(sm, :dataframe);
  df |> display
end

density(df.theta) |> display

A more complete  example using RegresssionAndOtherStories.jl and Pluto.jl can be found here.


Support reqwest >=0.11

#85

Hm. This doesn't seem to work so easily.
Luckily https://github.com/open-telemetry/opentelemetry-rust/pull/1674 upgraded reqwest to 0.12. Maybe we'll just do the same here.


g2o: unstable-2019-04-07 -> 20200410

Motivation for this change
Updates g2o to the latest release and fixes the "Log limit exceeded" error on Hydra. At least the first commit in this PR should probably be backported to 20.03 for ZHF.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

backported the first commit 0f920b05cbcdb8c0f3c5c4a8ea29f1f0065c7033

thanks @lopsided98 :sparkles:


Check append

Pull request
Please confirm that this pull request has done the following:

[x] Tests added
[x] Documentation added (where applicable)
[x] Example added (either to an existing notebook or as a new notebook, where applicable)
[x] Description in CHANGELOG.rst added

Adding to CHANGELOG.rst
Please add a single line in the changelog notes similar to one of the following:
- (`#XX <https://github.com/znicholls/silicone/pull/XX>`_) Added feature which does something
- (`#XX <https://github.com/znicholls/silicone/pull/XX>`_) Fixed bug identified in (`#YY <https://github.com/znicholls/silicone/issues/YY>`_)

I have raised separate point #85 for additional columns ruining everything.


Feat: update authentication to passport strategies

If we use passport we could implement different authentication strategies with ease.

Closing this issue, because I, myself moved away from using passport. Feel free to open a new Issue if you think this could improve this project.

curious to know what auth module you moved on to using...

@pauloladimeji Sorry for the late response... I myself got away from login strategies via FB, Google, Twitter, since I create mostly business applications where a JSON web token and a refresh token is mostly anything you need. But also for new hobby projects I got away for from other strategies, since JSON web tokens are self contained, no need for a third party... Of course if you want to use other strategies it would be better to rely on a library that provides easy use of them.


Update configure-cross-site-publishing.md

Made changes and replaced the invalid link with https://support.office.com/en-us/article/keyboard-shortcuts-86d68234-7f1a-40fc-a3d6-4c39c7a5ddaf?ocmsassetID=HA010369395&CorrelationId=1313c2d0-6e28-43a4-bc2b-d7be614597f3&ui=en-US&rs=en-US&ad=US

@nenonix @JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@JoanneHendrickson Changes look correct. Could you please review and merge? Thanks!


Use git tags

Please consider using git tag to tag releases.

Closing as the team started tagging releases (Thanks @gustavo-moreira!)


Fix gifv which hasn’t gif alternative but mp4

Coverage increased (+0.003%) to 97.657% when pulling 1b65f735b920c11c203713d02a03ce308c5a1791 on imgur-mp4 into 69a52793df82f0d3b7c7cc271fcdfa5e7d117e11 on master.

Coverage decreased (-0.004%) to 97.65% when pulling 5d84f9f9b35dc3f0e86f14161aee7625d43422ba on imgur-mp4 into 69a52793df82f0d3b7c7cc271fcdfa5e7d117e11 on master.


chore: update dependencies

Description
What is changing?
Prod:
 mongodb-connection-string-url        ^2.3.2  →   ^2.4.1
Dev:
 @microsoft/api-extractor           ^7.18.21  →  ^7.19.4
 @types/node                       ^16.11.12  →  ^17.0.9     // major
 @typescript-eslint/eslint-plugin     ^5.6.0  →  ^5.10.0
 @typescript-eslint/parser            ^5.6.0  →  ^5.10.0
 downlevel-dts                        ^0.7.0  →   ^0.8.0     // major
 eslint                               ^8.4.1  →   ^8.7.0
 eslint-plugin-import                ^2.25.3  →  ^2.25.4
 mocha                                ^9.1.3  →   ^9.1.4
 tsd                                 ^0.19.0  →  ^0.19.1     // major
 typescript                           ^4.5.2  →   ^4.5.4
 yargs                               ^17.3.0  →  ^17.3.1

What is the motivation for this change?
Keeping up with the times
Double check the following

[x] Ran npm run check:lint script
[x] Self-review completed using the steps outlined here
[x] PR title follows the correct format: <type>(NODE-xxxx)<!>: <description>
[x] Changes are covered by tests
New TODOs have a related JIRA ticket

Got one of our flakey results: here. Since we've seen it before I think its unrelated to these changes.

We can merge without waiting on the CI run for this latest commit ^
I bumped the @types/node and if you run:
npm diff --diff<EMAIL_ADDRESS>--diff<EMAIL_ADDRESS>
You'll see there's no type definition changes


New release for <IP_ADDRESS>5

Toltec bases itself off the releases, it would thus be appreciated if a new release could be made (tagging the latest commit e7a4819 with v0.0.23) to allow toltec to upgrade to the new version.

v0.0.23 has been released.
Thanks


Features Request for Search Source File

When I go to search a source file I would like the ability to search for these two items; similar to PDM search.

Case sensitivity

Position of the text

Also, I would like the ability to:

Open a member from results of the search

The other two might be possible with regex, but

Open a member from results of the search

already exists.

Related to #165

already exists.

Follow the link:

@thebeardedgeek

@SJLennon I think an incoming change might be to make it link right to the line number.

Okay so this is the plan:

I need to get the regex search working, which supports case-sensitive search.
I am not going to work on searching by column.

Closing in place of #165 - @thebeardedgeek I will be working on this this week


add missing close tag

@zencrust : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


CPU only for test

Hi,
Is it possible for me to run demo only on a computer without GPU (CPU only)?
Thank you in advance.

@tengerye it should be okay to run on cpu with roi_pooling.


Isuue with scanning cards

Hi,
i scanned 2 to 3 different axis bank cards it scanning perfectly, some cards are not scanning mostly like cards with silver tags, please give me some solution for this.
Thanks & regards,
Gopi.

There is no quick fix, and certainly no fix I can make without having access to the cards. However, if you feel inspired, you could grab the source and try to figure out what stage of the pipeline the scanning is failing at.


Minimal example for image inference

Hello
I am trying to use other model and it gets complicated.
I was wondering whether someone haev minimal example on how to run inference on existing image from memory? This way it will be simpler to understand how to adapt different model.
Thanks for the repo!

@yonatanbitton
Does the "existing image from memory" mean UIImage type on iOS? or CVPixelBuffer?
Please tell me more detail about your issues.

Thanks for the response.
I've managed to run your app with my model, this is very helpful, thanks!
Now I want to run it on a list of png images. I am wondering how to adapt the existing code to use single image from memory. I am not sure if it should be UIImage or CVPixelBuffer. This way I am looking for some reference about how to do it.

Hmm.. in this repo, there is no minimal method for inferencing just images without launching the app.
When you make that kind of function, I'll appreciate it if you make PR 🙃
Here is the Q&A that looks like what you want
https://developer.apple.com/forums/thread/79976
I hope it could be helpful to you.


[Question] There is only mysql in  "type menu" and "datasource menu" of  sqoop node?

I draw a sqoop node in the DAG,These is only one mysql option in the drop menu of source or target section;I copied ojdbc to sqoop lib dir and dolphinscheduler lib dir,I can import list-tables in oracle with sqoop; I can create  oracle datasource in dolphinscheduler and import data with the  oracle datasource  in datax node; But still I can not see a "oracle" or "postgresql"
options to select in sqoop node ,just only mysql。What could I do ? Thanks!
I meet the trouble in 1.3.4 and 1.3.5
Additional context
Add any other context about the problem here.
Requirement or improvement
Centos 7.2 or Centos 7.4

Currently, sqoop only supports mysql


fix bug in emplace

need to slice buffer if it's bigger than the classInstanceSize

Is this bug 6204?


PEP-440 .devN releases should not be considered pre-releases

I am developer and maintainer of the sanic-cors and sanic-plugins-framwork python libraries.
I use the PEP-440 guidelines for versioning in sanic-plugins-framework.
sanic-plugins-framework release versions look like this: 0.6.4.dev20181101
I've had a couple of issues raised this year about incomptibilities with pipenv and the PEP-440 versioning used in sanic-plugins-framework. I know pepenv prefers semver versions over PEP-440, but I wanted to open this discussion in order to try to come to a resolution for the users of those libraries.
Related:
https://github.com/ashleysommer/sanicpluginsframework/issues/4
https://github.com/ashleysommer/sanicpluginsframework/issues/9
https://github.com/pypa/pipenv/issues/2002
https://github.com/pypa/pipenv/issues/2063
It appears earlier related issues resolving versions with .devN suffix are now fixed, but users are still required to use the --pre flag in order to install them.
I believe this is incorrect behaviour, because my interpretation of the PEP-440 document is that the .devN suffix does not imply a pre-release version.
Reading this section of PEP-440 in Developmental Releases:
https://www.python.org/dev/peps/pep-0440/#id27
It shows that .devN can be applied on pre-release, release-candidate, release, and post-release versions. Therefore to me a developmental release is not the same as a pre-release.
In fact, see this section in PEP-440 regarding compatibility with other forms of semantic-versioning:
https://www.python.org/dev/peps/pep-0440/#id48
Specifically:

One possible mechanism to translate such semantic versioning based source labels to compatible public versions is to use the .devN suffix

So to me that implies that using .devN will increase compatibility of publicly released versions, with semantic versioing systems, not decrease it.
Currently using --pre to install these releases is not a good solution for the users.

There is a workaround to specify pipenv install sanic-cors --pre to resolve pre-release dependency, BUT this flag affects all other dependencies (for example it will coverage==5.0.3a, etc).

We are very familiar with the pep, however, as you assuredly know from your research, we use pip to install things, and pip also treats dev releases as prereleases.
For example:

$ pip install --pre sanic-plugins-framework
...
Successfully installed aiofiles-0.4.0 httptools-0.0.11 multidict-4.4.2 sanic-0.8.3 sanic-plugins-framework-0.6.4.dev20181101 ujson-1.35 uvloop-0.12.0rc1 websockets-5.0.1
...
$ pip list | grep -i plugins-framework
Sanic-Plugins-Framework 0.6.4.dev20181101

So would you mind linking the issue you've filed against pip?

I know pepenv prefers semver versions over PEP-440, but I wanted to open this discussion in order to try to come to a resolution for the users of those libraries.

I also just want to take the opportunity to say I have actually no idea what you're referring to on this point because we have no position on semver... we have an implementation with limitations in it, and if you have a bug to report about that we'd be happy to hear about it but we certainly don't have any strong feelings about how people version things. Pipenv itself doesn't even implement a sort order that is different from pip's when evaluating versions, it uses native packaging.version.Version objects to do comparisons with which don't even allow the kind of deviations you're describing.
Any behaviors here are not malicious acts by pipenv or attacks by its maintainers on the semantic versioning scheme OR on pep 440, please don't come to the issue tracker acting like we are personally crusading against semver. This is the first time anyone has ever even suggested (to me at least) that we even have a position on the topic.  If you take the time to look, we even have an issue open on the topic (#1760) with our plan for the path forward -- if you want to implement that, well, probably you should write an enhancement proposal so we can nail down the behavior, but we'd certainly appreciate the contribution.
As far as the pep itself, we aren't likely to break from pip's behavior as a reference whether or not you agree with it, since it's the behavior users expect. Thanks for filing the issue, sorry we can't be of more help.

@techalchemy
It seems you've taken offence to my opening this issue.
That was certainly not my intent, and I am sorry if my language has been interpreted as attacking the pipenv library in some way. I was not. I was wanting to open a discussion on this matter so that I am come to a resolution for the users of my libraries.

$ pip install --pre sanic-plugins-framework
...
Successfully installed aiofiles-0.4.0 httptools-0.0.11 multidict-4.4.2 sanic-0.8.3 sanic-plugins-framework->0.6.4.dev20181101 ujson-1.35 uvloop-0.12.0rc1 websockets-5.0.1
...
$ pip list | grep -i plugins-framework
Sanic-Plugins-Framework 0.6.4.dev20181101

But pip by itself can install sanic-plugins-framework without using --pre.
$ pip3 install sanic-plugins-framework
...
Successfully installed aiofiles-0.4.0 httptools-0.0.11 multidict-4.4.2 sanic-0.8.3 sanic-plugins-framework-0.6.4.dev20181101 ujson-1.35 uvloop-0.12.0rc1 websockets-5.0.1
...

$ pip list | grep -i plugins-framework
Sanic-Plugins-Framework 0.6.4.dev20181101

The reason I opened this issue against the pipenv repository is because installing the library works fine using pip without --pre (in fact that is the way users normally install this project) but the behaviour of pipenv is not the same, using pipenv you need to add --pre.

I also just want to take the opportunity to say I have actually no idea what you're referring to on this point because we have no position on semver.

That is my mistake. I personally don't use pipenv myself, but a colleague who does use it, told me that pipenv prefers semver-compliant versions over PEP-440. A couple of the PEP440-related pipenv issues that I read about this morning seemed to me to also give that impression. But I see now that is wrong, and I'm sorry that you seem to have taken offence at that assertion.

Any behaviors here are not malicious acts by pipenv or attacks by its maintainers on the semantic versioning scheme OR on pep 440

I did not say there was any malicious acts, not did I think there was. At no point did I think pipenv or its maintainers were attacking anything, and I don't know why you thought that.

please don't come to the issue tracker acting like we are personally crusading against semver.

I don't believe I don't believe I have done that. Can you point out where I was "crusading"?

So is the actual problem that pipenv cant install sanic plugins framework? That’s because we don’t select prerelease candidates by default when they are the only choice that satisfies a dependency. We would like to do that but it’s pretty complicated due to some implementation details involving hooking into pip internals. I haven’t looked at this recently but it was a roadblock as of a few months ago

So is the actual problem that pipenv cant install sanic plugins framework?

Yes, that is what this Issue is about. Sorry if that wasn't clear in the original post.
The crux of the matter is that users can't install spf using pipenv unless --pre is added. But SanicPluginsFramework releases are not pre-release versions.
If it is the pip library that is causing that, by incorrectly interpreting .devN suffix as implying pre-release, then I will open an issue against the pip project repo.
What I am seeing is that pip install sanic-plugins-framework will work fine and install the latest version (0.6.4.dev20181101), but pipenv install sanic-plugins-framework does not work. Users can add --pre to make the pipenv command work, but doing so they get pre-release versions of other things like coverage==5.0.3a, etc.
I've worked around this for now by releasing a "0.6.5" version of SanicPluginsFramework, without the .devN extension.

The main behavioral difference here between pip and pipenv is actually that pip makes an assumption that it should install an ‘unreleased’ version (the fact that it’s a dev or  rc or an alpha isn’t that important, the sort priority favors everything above dev options when possible). Pip assumes this if and only if there is no released version available in the index (this is technically correct according to the PEP).
Pipenv doesn’t do this, not for any philosophical reason, but just because we haven’t implemented the fallback properly. You can file an issue to pip if you like but I suspect they will tell you that a dev release is a pre release and if you put it on a postrelease it is a prerelease of a postrelease. Internally they use --pre as a way of lifting all restrictions on what they are allowing to be included in the candidate set — postreleases are already allowed by default which is why the flag makes sense (and the behavior probably does too, to a certain extent)


Go module support

Initial go module support.
Created folders for examples to support
go build ./...
go test ./...
Signed-off-by: Jason Taylor<EMAIL_ADDRESS>

@jasonltaylor , Thanks for your contribution.
We will be reviewing it soon and merging it with the master branch.


Develop execution shell for bots

Run reliably at proper times
Recover from failure
Use AWS secret manager for keeper keys

This has been accomplished in https://github.com/Badger-Finance/python-keepers/tree/main going to close


Support BigQuery integration

Motivation
As odd-platform supports redshift and so on, it would be awesome to support BigQuery integration.

Hi, @yu-iskw. Thanks for creating feature request. This one is looks really interesting. We'll take it in our plan.

hey @yu-iskw, sorry it took so long.
https://github.com/opendatadiscovery/odd-collector-gcp
now we have an integration of BigQuery, please take a look. If you have more questions and bug reports, please feel free to create issues in odd-collector-gcp repository


[Student View] Set up Initial Setup flow from Login to Enter Acad Details

Use FlowRouter to route to Acad Details component after user has been created

Flow was already set up beforehand in Week 6.5, but here is the complete UI in this commit: 1efbd40


add compodoc documentation generator

What kind of change does this PR introduce?
Feature
What is the new behavior (if this is a feature change)?
this PR adds support for compodoc angular documentation generator (as discussed in #1326)
Other information:
npm run docs builds the documentations in docs folder.
npm run docs:serve builds the documentations and serves it on http://localhost:8080/
More information:
https://compodoc.github.io/website/guides/getting-started.html
https://github.com/compodoc/compodoc

updated...
It does work fine.

Awesome, merged.


Fixed #31395 -- Made setUpTestData enforce in-memory data isolation.

https://code.djangoproject.com/ticket/31395#ticket

@adamchainz completely agree that the tests were lacking.
I ported the existing ones from https://github.com/charettes/django-testdata/blob/master/tests/tests.py that made the most sense.

Thanks for the docs review @adamchainz 🙇 !

@felixxm just to make sure, should I target 3.2 here?

Pushed a !fixup commit that re-targets 3.2.

buildbot, test on selenium.

buildbot, test on selenium.

buildbot, test on oracle.

I agree "deepcopyable" is bit unreadable, but "deepcopy able" reads worse to me. "deepcopy-able" would be a more correct combination but it's similar.
Perhaps instead we can use "copyable with deepcopy" or "work with deepcopy"?

What do you think about my proposition? "... support creating deep copies with copy.deepcopy()" :thinking:

Sure, it can't hurt to be explicit!

Thanks for the merge and the review @felixxm and @adamchainz 🎉


Switch to tty-command for error output

Uses tty-command to display errors when calling buildkite-agent to add annotations.

@morganick The test suite fails on purpose to generate annotations.

@ryansch this has already been approved.


🐛 [BUG] - Too strict validations prevent acceptance of valid outputs

Describe the bug
Hey folks 👋, one major use case for us is using Primer Brand components with data coming from a CMS. That works smoothly for several components but presents some challenges with a few of them. For example, the River.Content component has a strict validation in the kind of children it may contain (according to the docs, it does only support Text, Heading, and Link). That prevents us from using components such as ReactMarkdown to parse incoming Markdown data and transform it into the same Text and Link components that the River.Content component expects to contain.
Here is a link to a Codepen showing this behavior. As shown there, the ReactMarkdown component will return a Text element with an InlineLink inside, something that River.Content should be able to handle. Instead, it ignores the ReactMarkdown element entirely and shows a blank space.
Do you have any guidance about how to proceed in such cases?
Reproduction steps
https://codepen.io/sergioalvz/full/bGmaqBx

Expected behavior
The `River.Content` component renders the result of evaluating the `ReactMarkdown` element.

Screenshots
No response
Browsers
No response
OS
No response

@rezrah, do you have any estimates for when the Prose component will be ready? This is blocking a few work streams we want to complete by the next two weeks.

@sergioalvz - sorry for late response. We're drafting the prerequisite issues for Prose this week, eng to begin shortly after. ETA for the component in the published library is just an estimate at this point, but we can expedite release to within the next two weeks.

@sergioalvz Quick update on the Prose component: we have started to work on the API exploration and do some research but unfortunately won't be able to ship within 2 weeks due to scheduled OOO of Primer Brand team.
cc @JoshBowdenConcepts @enstyled @rezrah

@rezrah, great news! Is it possible to use the Prose component inside other components (for example, inside the River.Content component)?

👋 @sergioalvz - Prose can't be used in River.Content just yet, as that component guards the children types to Heading, Text and Link as you mentioned. Anything besides those children are ignored.
To clarify why that decision was made.. it's to ensure visual consistency of the River pattern across all marketing pages, mitigating situations where we see inconsistently sized (or levelled) headings, or even buttons that end up being used instead of links.
The use-case for Prose is limited to situations where you can't use or map against React components. I.e. you need to dangerouslySetInnerHTML for editorial text. Even if you could use Prose in the River.Content, you would lose the ability to guardrail presentation, as the CMS could any heading level (should be h3), and the paragraph text won't inherit default styling (slightly larger than the default).
I think we could solve for the use-case in the description in a few different ways:

Allow Prose as a valid child of River.Content in Primer Brand, and apply the appropriate styles internally. We can action this, and is also why the issue is still open for us.

Use a markdown parser function instead of a React component
I recommend pre-processing the markdown outside of the return statement. Using a library like marked, you can avoid using a React component (which gets ignored) and pass the converted markdown directly to Prose, which requires html input.
import {parse} from 'marked';

parse('hola, this is just a [test](#) description for a River.'); // "
hola, this is just a test description for a River.
"

Then pass ☝ straight into Prose. This helps us to maintain required guardrails around valid types, while adding new, vetted components to the safelist like Prose. It's also more performant, because you can memoise that value now.

Extract content in a markup-agnostic way and use Primer Brand components natively
The preferred approach - if possible - would be to extract data from the CMS without additional markup, so that you could pass the raw text directly into typographic components. Is it possible to retrieve this from Contentful using independent fields? The closer we can get to using the recommended API the better 🙏. We'll still look at enabling Prose in River in the interim. cc. @JoshBowdenConcepts.

Thanks for the context, @rezrah!
In the long term, we are heading towards option 3) since Contentful provides a way to directly map RichText content to React elements.
Supporting markdown-generated content inside River elements would be handy in the short/mid-term since some pages don't benefit from Contentful support yet and are developed without direct access to Primer Brand primitives. Developers use a custom River component that forwards the content to Primer Brand's River component. We considered improving the interface for this custom River component to support rich text formatting by leveraging Markdown. I guess only option 1) would help on that front.
To provide some more context, we created these custom abstractions on top of Primer Brand components to make sure they are easy to connect with Contentful later this year and that the pages created following this approach are easy to migrate as well (because they are constrained to strict limitations in customization and styling).

👋 @sergioalvz - quick update for you on this topic following a discussion at Primer Brand maintainer sync on 10th July.
We discussed the trade-offs around increasing responsibility and scope of River.Content, carefully weighing up pro's and cons..

Decision was that enabling Prose at this time inside River.Content presents too much of a design pattern risk. For example, Prose supports more elements than River.Content is intended to handle, E.g. multiple paragraphs, multiple headings etc. The unpredictability of the input could lead to unintentionally facilitating anti-patterns.

The preferred approach for using Markdown input going forward is as described in an earlier post:

Parsing the markdown AOT and mapping the relevant parts of the AST to River components like Heading, Text and Link
The conversion of markdown isn't a responsibility of the library at this time, as we avoid taking heavy third-party dependencies  to ensure maximum interop with a wider range of projects. As a result, we would expect the conversion to happen AOT. Happy to jam with you on a few different ways you could do this though! LMK.

Re. input from Contentful.. could you create a simple text-only mapping between dedicated heading, description and link to ensure that we only pass in the necessary data to the River.Content layer?

Thank you, folks, and thank you for your time yesterday. I think we're cool closing this issue and parsing the Markdown AOT. With the latest shift in priorities, we'll connect things to Contentful sooner than we expect, so this becomes less of a problem (I think we won't be leveraging Markdown in the short term, either).


No able to obtain proper result from "      Metrics::classification_report(y_train, train_predictions);"

With the last versionof MALE5 3-0.0 I got issue to compile the example previously share. I ahve updated the code to finally manage to compile :
/--- Normalizing the independent variables
StandardizationScaler Scaler1;
X_train = Scaler1.fit_transform(X_train); // we fit the scaler on the training data and transform the data alltogether
X_test = Scaler1.transform(X_test); // we transform the new data this way

 Print("X_Train == ", X_train);

//--- Training the  model
 decision_tree.fit(X_train, y_train); //The training function

//--- Measuring predictive accuracy
 vector train_predictions = decision_tree.predict(X_train);

 Print("GC train prediction vector  == ", train_predictions);

 Print("Training results classification report");
 Metrics::classification_report(y_train, train_predictions);

//--- Evaluating the model on out-of-sample predictions
 vector test_predictions = decision_tree.predict(X_test);

 Print("Testing results classification report");
 Metrics::classification_report(y_test, test_predictions);

//---
ArraySetAsSeries(rates, true);

However it looks like this step doesn't work as expected      Metrics::classification_report(y_train, train_predictions). COuld you support?

can you show the current outcome you are receiving from the classification report, and what were you expecting to see

if fact I see in the tester that the confusion matrix is full of zero ...

then I see the classification report full of zero as well..

then I can see oall other valauble to zero. I enter in the function file Metrics to try to understant where wome from the issue... by adding some "print".

thanks for your support

It seems that you are using the classification report for a regression problem. That is where the issue lies.
Check your predictions the classification report is for classification problems

Thanks for your reply. I have investigated more in details. In fact  , I had to create a new function to be able to enter "y" vector that was a binary one. In MatrixExtend the option to select the "y" vector disappeared and per default "y" was the last column from the matrix X ..that didn't match my code.
in your exemple you also used this function with "y" vector but it is not available anymore in your version MAT5 3.0.0
MatrixExtend::TrainTestSplitMatricesGC(X, y,X_train, y_train, X_test, y_test, train_size, random_state);
In anycase thanks for your answer and let see if I can manage to use this library efficiently ;-).

All the code used in the example are from version 3.0.0 which is the recent-released version. Be sure you are not having version conflicts.


add @sharetribe/sharetribe to real-world-rails/apps

hello @eliotsykes  =)
i will go adjust and update the PR.

Thanks for the quick turnaround @vtorves and apologies for not mentioning these in the earlier feedback:

Please adjust submodule to reference the latest commit from https://github.com/sharetribe/sharetribe/commits/master
Please squash commits into a single commit with the original commit message you wrote "add @sharetribe/sharetribe to real-world-rails/apps"


SIMSBIOHUB-529: Initial commit

Links to Jira Tickets

SIMSBIOHUB-529

Description of Changes

Adds an error dialog whenever the Projects List or Project Details page fails to load.

Testing Notes
You should see an error dialog when the request fails while attempting to:

[ ] View the projects list page
[ ] View the project page for a single project

Multiple ways to test this locally:

Once you've loaded the project page/project list page, hot-reload the API, and then navitgate to the project page or project list page while the API is compiling. You should see the error dialog.
Throw an exception in the project view endpoint or project list endpoint. You should see the error dialog when loading either of the respective pages.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 72.64%. Comparing base (92ff54b) to head (549865a).

Additional details and impacted files
@@             Coverage Diff             @@
##              dev    #1251       +/-   ##
===========================================
+ Coverage   52.43%   72.64%   +20.20%
===========================================
  Files         577      216      -361
  Lines       17195     8791     -8404
  Branches     2677     1254     -1423
===========================================
- Hits         9016     6386     -2630
+ Misses       7572     2049     -5523
+ Partials      607      356      -251

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

@curtisupshall Sorry, thought I had this in the ticket: You can use the useDataLoaderError hook to encapsulate most of the code to handle those 2 error cases. It just ties into the dataloader error field and spawns a dialog for you, without needing any of the extra context setup or try/catch logic, etc.


Configuration options

This ticket is here to track implementation progress of configuration options.

[ ] rootID: Root DOM node to render into. default: 'root'
[ ] rootRoute: Root route to connect the route handler to. default: '/'
[ ] reduxMiddleware: Custom middleware bundle for Redux
[ ] renderLayout: custom layout render function

Hi. Can I ask where you are with this issue?
This project looks awesome and just what we need but without the ability to specify custom middleware and a custom renderLayout, we can't use it just yet. If it's not on your immediate horizon, no worries but I thought I'd ask anyway, to see what is happening.
Cheers.

Sorry, I've been out sick. PR is welcome.

Grand, thanks. Feel better.


Improve grpc timeout interaction with outlier detection

Envoy currently supports reading the grpc-timeout header for setting the global timeout for the request, but doing so results in a race between the gRPC client timing out vs Envoy timing out: if the client times out, we get a downstream reset while if Envoy times out we get a DEADLINE_EXCEEDED response.
In most cases this is fine (client sees a timeout in either case) but it means that Envoy's outlier detection is not able to accurately account for gRPC timeouts when the gRPC client times out first. From our data it seems like the client will time out the request before Envoy in most cases.
Some options I can think of:

Synthetically adjust the timeout provided by grpc-timeout, for example by decreasing it by 1ms. This would reduce the likelihood that the gRPC client won the timeout race, although not eliminate it.
Treat downstream resets close to the global timeout as timeouts, for example treat any downstream reset less than 1ms away from the global timeout is treated as a timeout.
Begin the global timeout timer earlier: @mpuncel noted that the global timeout starts after the router sees the entire request, which might explain why the gRPC client times out more quickly in most cases. This would not fix this issue but might make the issue less prevalent.
Do nothing and tell people to set x-envoy-upstream-rq-timeout-ms lower than the grpc-timeout (or avoid the use of a deadline in the client lib altogether). This isn't great but would require no changes to Envoy

@snowp FWIW I would be in favor of having an option to allow (1). (2) and (3) seem not great to me. (4) is obviously my favorite solution. :)

We kinda decided to either put this in an Envoy filter or to upstream it to the filter config, so I'll get a PR ready since it's probably something other people might find useful, and it saves us from having to parse the grpc-timeout header twice for each request.


set but not used variable

In ssl_transport_security.c:538, result is set but not used

Ping ? :)

Fixed in https://github.com/grpc/grpc/pull/1128


t3000 all gather hangs w/ dprint+watcher enabled

pytest tests/tt_eager/python_api_testing/unit_testing/misc/test_all_gather.py::test_all_gather_on_t3000_post_commit[mem_config0-input_dtype0-8-1-input_shape1-0-layout1]

Confirmed this still hangs after the recent all gather fixes.  Hang is now at tear down, last line is "Closing device 7".  This was w/ DPRINT enabled only (watcher enabled runs into OOM issues)

@pgkeller  to retest after David's fix

Confirmed TT_METAL_DPRINT_CORES=all pytest tests/tt_eager/python_api_testing/unit_testing/misc/test_all_gather.py::test_all_gather_on_t3000_post_commit[mem_config0-input_dtype0-8-1-input_shape1-0-layout1] passes on latest main, but run into an issue with enabling watcher for this test on remote chips.
Problem is that having watcher enabled on remote chips and running this test causes it to slow down heavily. I see the watcher polling progressing, but very slowly. Unfamiliar with the nature of the all gather test, is it possible that watcher polling is eating up bandwidth between the chips and slowing the test down?

Confirmed TT_METAL_DPRINT_CORES=all pytest tests/tt_eager/python_api_testing/unit_testing/misc/test_all_gather.py::test_all_gather_on_t3000_post_commit[mem_config0-input_dtype0-8-1-input_shape1-0-layout1] passes on latest main, but run into an issue with enabling watcher for this test on remote chips.
Problem is that having watcher enabled on remote chips and running this test causes it to slow down heavily. I see the watcher polling progressing, but very slowly. Unfamiliar with the nature of the all gather test, is it possible that watcher polling is eating up bandwidth between the chips and slowing the test down?

Yes, this test communicates heavily across chips.  What watcher interval were you using?  I suspect for tests like this it should be 10 seconds or longer

Slowdown point (with watcher + dprint enabled) appears to happen between 20s and 25s interval, essentially the length of the test. What I think is happening is if the watcher poll happens while the test is running, it eats up the bandwidth and also slows down the watcher polling to the point where there's no dead time between polls - meaning it's going to be slow for the remainder of the test. The slowdown point is lower when running with just watcher, so likely dprint polling contributes to that slowdown as well. Think this would fall under expected behaviour, or requires further investigation?
Also, PR for a change I needed to add to get TT_METAL_WATCHER_NOINLINE working after (I think) the sfpi bump: https://github.com/tenstorrent/tt-metal/pull/9018

PR is merged, if @SeanNijjar thinks this looks fine then we can close the issue.

@pgkeller @tt-dma - it sounds like it has to do with an issue of watcher dump time vs watcher poll time? Since the watcher timer isn't expected to be very precise (I always saw TT_METAL_WATCHER=10 to mean "do a watcher poll in every 10 or so seconds. 11 is fine and so is 9 but 5 or 50 probably aren't".
Is that the intended design. If so is it possible to restart the watcher poll time on prior sample finish?

I had previously implemented the interval in a way to be as accurate as possible, but I think you're right in that the program should have priority - especially since we want people to be developing with watcher enabled. Here's a PR for that change: https://github.com/tenstorrent/tt-metal/pull/9038
FYI @pgkeller


static propTypes broking react-native application

Bug Report
Hello, im developing a react-native application using the library react-native-confirmation-code-input.
When i use the following template:
`
Properties

Basic usage

 console.log('onFulfill', code)}
  />

`
It returns the following error:
`You may need an appropriate loader to handle this file type.
|
| export default class ConfirmationCodeInput extends Component {

static propTypes = {
|     codeLength: PropTypes.number,
|     compareWithCode: PropTypes.string,
@ ./node_modules/react-native-confirmation-code-input/index.js 1:0-71 2:15-36`

Expected behavior
Render the component with Playground or PropsTable properly.
Environment

OS: [e.g. OSX 10.13.4, Windows 10]
Node/npm version: Node 11/npm 6

My question is: does this error occur due to an incompatibility of some component of this library with Docz (a native lib for example)?

What was the fix? Having same issue with RN components (TouchableOpacity).


makefile: update odf go mod depndancies & odf version to 4.16 .0

Also updated ocs version being used to 4.16

@Nikhil-Ladha @leelavg Once rook-ceph-operator bundle & client-operator bundle are updated to 4.16 please do change them here similar to this commit https://github.com/red-hat-storage/odf-operator/pull/388/commits/8367b026d7f6912a65c03527fcc3de367b7a02b0

/override ci/prow/odf-operator-e2e-aws


Add make install.tools to README.md and touch up tutorial

Signed-off-by: TomSweeneyRedHat<EMAIL_ADDRESS>- What I did
While using the tutorial, noted a few missing pieces in the README.md and tutorial.md. Added changes to clear those up.
- How I did it
vi is my friend.
- How to verify it
Install on a new VM and follow the tutorial.
- Description for the changelog
Touch ups to the README.md and tutorial.md files.

New patch pushed - 1343d19

LGTM.  No reason to run e2e since this is just docs.
Merging.


Game Media Tools - Resolution tool not working with Ico files

I guess the problem with ico files is that they consist of several images in a single file (similar to gif files), each with a different resolution. For example the ico file "game.ico" constains the following 9 images:

image1 = 256 x 256
image2 = 192 x 192
image3 = 128 x 128
image4 = 96 x 96
image5 = 64 x 64
image6 = 48 x 48
image7 = 32 x 32
image8 = 24 x 24
image9 = 16 x 16


support high-level consumer api

Hi
brod whether suppport high-level consumer api of kafka

Hi. Not yet.

Do you have any plans to support this?

Yes, we have plans.


Problems with Out char**

I am currently transitioning from ffi-napi to koffi. Thank you very much for this library!
I have one particular function that troubles me. I do not have access to the source code of the C function, only the header. The signature is int getNames(int, int, _Out_ char**). The basic idea is that the function should fill the char** with names from a database based on the two int parameters. So, after calling the function, the last parameter should look something like ['Adam', 'Beatrice'] (probably filled with null bytes).
On the JavaScript side, I tried several variations for the last parameter (a bit simplified to two elements here for brevity):
const names1 = [ '\0'.repeat(10), '\0'.repeat(10) ];
const names2 = [ [ '\0'.repeat(10), '\0'.repeat(10) ] ];
const names3 = [ [ '\0'.repeat(10) ], [ '\0'.repeat(10) ] ];

All of them lead to a segfault. I am sure that the provided length of the null byte strings is sufficient, so it must be something else.
Any idea what I am doing wrong? I tried to find anything in the docs or tests, but to no avail.

Could you give a bit more information?
Namely, the original API documentation, that details how you're supposed to use this function from C.

Wow, thank you for the quick answer!
Unfortunately, this is all information I have. I can check with the people who wrote the code, but that'll take some time.
/*!
* Returns names of elements in a database.
*
* @param[in] uniqueId ID of an existing database.
* @param[in] maxElementNameLen Maximum length of individual element names.
*
* @param[out] elementNames Element names, vector size number of elements in the table.
*
* @pre Caller is responsible for making sure elementNames is large enough to hold the number of elements in the database.
*
* @sa getNumberOfElements
*
* @return error code (0 on success)
*/
OUR_API int OUR_CALL getElementNames(int uniqueId,
    int maxElementNameLen,
    char** elementNames);

OK, got a super-quick answer from the people who made the code. Some parts had to be redacted 🙄 , but this should be the gist of it.
int getElementNames(int uniqueId, int maxElementNameLen, char** elementNames) {
  int nElem = someMagicSourceOfNumberOfElements(uniqueId);
  for (int i = 0; i < nElem; ++i) {
    std::string tmp = someMagicSourceOfStrings(uniqueId);
    int nameCopyLen = std::min(static_cast<int>(tmp.length()), maxElementNameLen - 1);
    for (int j = 0; j < nameCopyLen; ++j) {
      elementNames[i][j] = tmp[j];
    }
    elementNames[i][nameCopyLen] = '\0';
  }
  return 0; // original code is more sophisticated...
}

Thanks! The reason I asked is because the answer depends on how the strings are allocated. Here, it is the responsability of the caller to preallocate both (1) an array of pointers and (2) buffer space for each string.
I've used your code to make a working C++ sample code:
// Windows: clang++ -shared -o 121.dll 121.cc
// Linux: clang++ -shared -o 121.so 121.cc

#include <string>

#ifdef _WIN32
    #define EXPORT extern "C" __declspec(dllexport)
#else
    #define EXPORT extern "C" __attribute__((visibility("default")))
#endif

EXPORT int getElementNames(int uniqueId, int maxElementNameLen, char** elementNames);

static int someMagicSourceOfNumberOfElements(int uniqueId)
{
    switch (uniqueId) {
        case 0: return 1;
        case 1: return 6;
        default: return 0;
    }
}

static std::string someMagicSourceOfStrings(int uniqueId, int i)
{
    static const char *strings[] = {
        "foo",
        "bar",
        "FOOBAR",
        "barfoo",
        "hello",
        "world"
    };

    return strings[i];
}

EXPORT int getElementNames(int uniqueId, int maxElementNameLen, char** elementNames)
{
    int nElem = someMagicSourceOfNumberOfElements(uniqueId);
    for (int i = 0; i < nElem; ++i) {
        std::string tmp = someMagicSourceOfStrings(uniqueId, i);
        int nameCopyLen = std::min(static_cast<int>(tmp.length()), maxElementNameLen - 1);
        for (int j = 0; j < nameCopyLen; ++j) {
            elementNames[i][j] = tmp[j];
        }
        elementNames[i][nameCopyLen] = '\0';
    }
    return 0;
}

And here is how to use it from Node.js with Koffi:
const koffi = require('koffi');
const lib = koffi.load(__dirname + '/121' + koffi.extension);

// Declarations

const getElementNames = lib.func('int getElementNames(int uniqueId, int maxElementNameLen, _Inout_ char **elementNames)');

// Wrapper

function callGetElementNames(uniqueId) {
    // Provide enough space for elements, as per documentation, this
    // will work for 64 elements at most
    let maxElements = 64;

    // Each name can be 255 (+ terminating NUL byte) characters at most
    let maxElementNameLen = 256;

    let dest = Array(maxElements).fill('\0'.repeat(maxElementNameLen));

    if (getElementNames(uniqueId, dest.length, dest) != 0)
        throw new Error('getElementNames() failed');

    // Truncate empty strings at the end
    let len = dest.indexOf('');
    dest.length = (len >= 0) ? len : dest.length;

    return dest;
}

// Test

let elements = callGetElementNames(1);
console.log(elements);

Because each individual string buffer is provided by the caller, you need to use _Inout_ so that Koffi copies each buffer (sized maxElementNameLen). Which then gets filled by the C++ code, and converted back to strings by Koffi.

Great, this works! Thank you very much for your quick and competent help!
Maybe the source code you wrote (or a simplified version of it) would make a nice addition to the documentation of koffi? The key I was missing was the _Inout_ which doesn't have an example in the docs, yet.

You're welcome :)
Yes, good idea, I'll add several examples for "function returns an array of strings" API. There are multiple C API styles to handle this, and each one works differently.
An example for each style would definitely help!


[turnstile] Add changelog for October 28th

Relevant prs: #6346
Not too sure about the links & the quick summary.

Thanks


flinkx1.12性能问题：mysql-hive 如何提高离线同步效率

Search before asking

[ ] I had searched in the issues and found no similar question.

[ ] I had googled my question but i didn't get any help.

[ ] I had read the documentation: ChunJun doc but it didn't help me.

Description
1、数据量9000万+时，mysql同步至hive时，一是不能设置多通道，因为hive sink组件不支持  二是、需要设置fetchSize 实现可读，我设置2048000，但是同步依然很慢，大概需要4个小时
2、j机器性能很好，mysql数据库服务器也很好，我想问如何提交同步效率

Code of Conduct

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

@biandou1313 hdfs相关插件支持并发写入的。你这边的配置发下


Update minimum wage rates

Update worker and employer minimum wage calculators with the new minimum wage and living wage rates.
Also use the 2018-2019 rates in the regression tests for these calculators.
https://trello.com/c/P1a8k7jl/122-21-april-minimum-wage-calculator-for-workers
https://trello.com/c/2dDKFQ55/123-2-1-april-minimum-wage-calculator-for-employers
https://docs.google.com/document/d/1Ik5E2r4ixEq_hPm_f9wT4LjwZQbfxY3uvtCXCipguZ8/edit
Marked as "do not merge" because there's an outstanding question about whether we need to make any changes to the weekly accommodation offset.

@h-lame Sorry, forgot to update this PR. I've talked to Mark, and he's confirmed that we don't need to do anything with the change to the weekly rate. 👍


[IOTDB-4401] DataNode should not be stopped  when any regions are migrated failed

When executed remove-datanode.sh, if some regions are migrated failed, the DataNode should not be stopped（Always be Removing status）.

LGTM


fix(viewabilityHelper): clear timeouts during onUpdate when minimumViewTime is present

Summary

This fixes the issue with onViewableItemsChanged being called multiple time during the minimumViewTime window.
To sum up the problem, the onViewableItemsChanged callback is called multiple times during scroll event, kind of ignoring the minimumViewTime setting. So e.g. if there is FlatList with a few items, and the viewport allows 3 items to be simultaneously visible, user will scroll, and the callback will be called with [1], [1, 2] and [1, 2, 3] items. By clearing the intervals, we omit running the callback too many times.
Technical note
I haven't changed the existing unit tests for the ViewabilityHelper, but I was left a bit confused by this:
rowFrames = {
      a: {y: 0, height: 250},
      b: {y: 250, height: 200},
    };
helper.onUpdate(
      props,
      0,
      200,
      getFrameMetrics,
      createViewToken,
      onViewableItemsChanged,
    );

The 200 parameter in onUpdate is the viewportHeight. So there are few questions I don't understand completely, which makes me a bit uncertain about my change:

if the viewport height is set to 200, it means that there is always only one visible item on screen. I think that's the assumption that missed this edge case I'm trying to fix
the parameter is called viewportHeight. I'm not sure what's the impact here in case of a horizontal flatList 🤔

Changelog

[GENERAL][FIXED] - fix onViewableItemsChanged called multiple times during minimumViewTime window
Test Plan

I've added a unit test that covers the change

This still have the error in CI:
xplat/js/react-native-github/React/Fabric/Mounting/ComponentViews/ScrollView/RCTScrollViewComponentView.mm:274:56: error: no matching function for call to 'toString'
    scrollView.snapToAlignment = RCTNSStringFromString(toString(newScrollViewProps.snapToAlignment));
                                                       ^~~~~~~~
stderr: xplat/js/react-native-github/React/Fabric/Mounting/ComponentViews/ScrollView/RCTScrollViewComponentView.mm:274:56: error: no matching function for call to 'toString'
    scrollView.snapToAlignment = RCTNSStringFromString(toString(newScrollViewProps.snapToAlignment));
                                                       ^~~~~~~~
stderr: xplat/js/react-native-github/React/Fabric/Mounting/ComponentViews/ScrollView/RCTScrollViewComponentView.mm:274:56: error: no matching function for call to 'toString'
    scrollView.snapToAlignment = RCTNSStringFromString(toString(newScrollViewProps.snapToAlignment));

I'm not sure why the pipeline fails - is there something I can do about it?

I'm not sure why the pipeline fails - is there something I can do about it?

One question raised on internal review, so I need verify but share if you have any thoughts. Also, pipeline failure is from past, I think if you rebase it will pass.

I'm wondering if this just a difference of expectations of what onViewableItemsChanged should do. I haven't dug in enough into the added test to make sure it's correct, but multiple callbacks being fired for each of the visible cells as they reach the minimum view time seems correct.

I'm not sure why the pipeline fails - is there something I can do about it?

One question raised on internal review, so I need verify but share if you have any thoughts. Also, pipeline failure is from past, I think if you rebase it will pass.

I'm wondering if this just a difference of expectations of what onViewableItemsChanged should do. I haven't dug in enough into the added test to make sure it's correct, but multiple callbacks being fired for each of the visible cells as they reach the minimum view time seems correct.

I'm not sure why the pipeline fails - is there something I can do about it?

One question raised on internal review, so I need verify but share if you have any thoughts. Also, pipeline failure is from past, I think if you rebase it will pass.

I'm wondering if this just a difference of expectations of what onViewableItemsChanged should do. I haven't dug in enough into the added test to make sure it's correct, but multiple callbacks being fired for each of the visible cells as they reach the minimum view time seems correct.

I'm not sure why the pipeline fails - is there something I can do about it?

One question raised on internal review, so I need verify but share if you have any thoughts. Also, pipeline failure is from past, I think if you rebase it will pass.

I'm wondering if this just a difference of expectations of what onViewableItemsChanged should do. I haven't dug in enough into the added test to make sure it's correct, but multiple callbacks being fired for each of the visible cells as they reach the minimum view time seems correct.


It is better to use the repository field in Cargo.toml

To allow Crates.io , lib.rs and the Rust Digger to link to it. See the manifest for the explanation.

how about just add the repo field, and keep home field there?
I like that better


Ignore files in .gitignore

We should not flag any file that is ignored by .gitignore in the IDEs as those files shouldn't be in the repo and thus aren't issues with the code and may be development artifacts like that in #146.
This also requires adding an option to the extensions to "ignore" this default setting.

Dupe of #8

This will fix #8

This turns out to be difficult because git2sharp has a native binary dependency.

Does this mean that this won't be implement? There is an issue at MegaLinter that seems to show that this isn't ignoring node_modules.

I can take another look at it. I had not received any user feedback that this was an important issue, but given the issue you linked it shows there is interest.
I'm currently working on a refactor (#367) so it's a good time to take another look.

It looks like megalinter is using the .net tool CLI in docker (Linux).
I'll investigate adding this to the CLI.


Bug showing popover for the second time.

When i'm setting the variable inside the class like this:

But if I'm setting it inside the showDatePickerPopover() It's working fine. But the problem if i do that I can't call the closePopover() method inside any function. Here's the video:
https://www.youtube.com/watch?v=5AGi-6cw8gw
Thanks!

Just create another UIBarButtonItem with action of closePopover() and assign it to your button from your controller, that instantiate from storyboard. This should be sufficient.

Thanks again! ;)


clear ajax select options when clearing the value

refs: #3225
Problem: When using ajax selects with depencies, we were only setting the value of the select to null when the depency changes. Previous fetched options would still available to select while the fiield fetches the new options from the server.
Solution: When setting the elements value to null when the dependency changes, we also clear all the options from the select to make sure they can't be selected while the field is fetching the new options from server.

A new inspection was created.

The inspection completed: No new issues


include 3rd party licenses

We need an SBOM that includes 3rd party licenses and notification.  Also need a license check.

per discussion, include cyclonedx structured format and a human readable version of these.  also include couchbase software license, if not already done.

Cyclonedx bom is now included in the archive as a part of CI/release. It's not terribly human readable though...

Yes, @RekhaDS and I had a look, and you're correct, it's not terribly human readable.  Since we have Black Duck coverage for this now, let's include the product metadata notices:
https://github.com/couchbase/product-metadata/blob/master/couchbase-shell/blackduck/1.0.0/notices.txt
We will probably need to update some dependencies and update one more time, but it is acceptable to just include this in the repository since it's built after the fact.  It just needs to be updated close to release.
We also noticed the packaging, at least on MacOS, is a little funny now that the CylcloneDX file is included:

I think that's an unusual structure.  Probably a side effect?

Please replace the bom.json with the notices.txt.  Update the README to indicate "Couchbase Shell is made possible through open source components as listed with their licenses in notices.txt"
Please include the Couchbase License Agreement and reference it from the README.  https://www.couchbase.com/LA03012021

Hello Charlie @chvck - Could you please look at this one? Will help to kickstart the process with Legal.


[manifest] Exclude CMakeLists.txt; remove unnecessary path settings; reindent file

Checklist

[X] I've read the Contribution Guidelines
[X] My contributions are licensed under the Swift license.
[X] I've followed the coding style of the rest of the project.
[ ] I've added tests covering all new code paths my change adds to the project (if appropriate).
[ ] I've added benchmarks covering new functionality (if appropriate).
[ ] I've verified that my change does not break any existing tests or introduce unexplained benchmark regressions.
[ ] I've updated the documentation if necessary.

@swift-ci test and merge

@swift-ci test


feat: added password kit for improved password policy management

Centralised password validation for use across password services
Added character class policy

[ ] CHANGELOG.md updated with a link to the PR (not the Issue)
[x] Well-formatted commit messages
[x] Rebased/mergeable
[x] Tests pass
[ ] http/swagger.yml updated (if modified Go structs or API)
[ ] Documentation updated or issue created (provide link to issue/pr)
[x] Signed CLA (if not already signed)

LGTM

I don't believe should should affect any existing passwords that do not match the new character class spec, it should only block setting new passwords.

Blocked until #17200 reaches a decision


Choosers: refactor to use SVG icons

Refactored non-deprecated choosers to use SVG icons (see also: https://github.com/wagtail/wagtail/issues/6997) Custom choosers can also supply their own SVG icons using the chosen_icon and unchosen_icon blocks.
Example:
{# my_custom_chooser.html #}
{% extends "wagtailadmin/widgets/chooser.html" %}
{% load wagtailadmin_tags %} {# <-- this provides the {% icon %} tag #}

{% block unchosen_icon %}{% icon name="doc-full-inverse" %}{% endblock %}
{% block chosen_icon %}{% icon name="doc-full-inverse" %}{% endblock %}
{% block chooser_class %}custom-chooser{% endblock %}

We are keeping the relevant icon font css for custom choosers around to prevent breaking existing custom choosers that are using the icon font.
Testing instructions
Using the bakery demo verify that the choosers listed below use SVG icons and that there are no visual regressions compared to the icon font based choosers.

page chooser
document chooser
image chooser
snippet chooser

I've tested browsers using Browserstack and my own devices with these combinations:

Safari on iPadOS 14.4.2 (iPad 6th gen) (own device) :heavy_check_mark:
Google Chrome 89 on Linux (own device) :heavy_check_mark:
Internet Explorer 11 on Windows 10 (BrowserStack) :heavy_check_mark:
Firefox 87 on Windows 10 (BrowserStack) :heavy_check_mark:
Firefox 78 (ESR) on Windows 10 (BrowserStack) :heavy_check_mark:
MS Edge 89 on Windows 10 (BrowserStack) :heavy_check_mark:
Safari 14 on macOS 11 'Big Sur' (BrowserStack) :heavy_check_mark:

Todo:

[x] ~Update documentation on using icons with custom choosers~ There is no documentation on writing custom choosers
[x] Verify that existing custom choosers using the icon font continue working
[X] Do more cross-browser testing - done. did not notice any regressions.

...anything I've missed?

Here is some code to test the different choosers using the bakerdemo:
# bakerydemo/base/models.py

from wagtail.images.models import Image
from wagtail.images.edit_handlers import ImageChooserPanel
from wagtail.documents.edit_handlers import DocumentChooserPanel
from wagtail.documents.models import Document
from wagtail.snippets.edit_handlers import SnippetChooserPanel

from bakerydemo.breads.models import BreadIngredient

class ChooserTestPage(Page):
    doc = models.ForeignKey(Document, on_delete=models.SET_NULL, null=True, blank=True, related_name="+")
    custom_doc = models.ForeignKey(Document, on_delete=models.SET_NULL, null=True, blank=True, related_name="+")
    image = models.ForeignKey(Image, on_delete=models.SET_NULL, null=True, blank=True, related_name="+")
    page = models.ForeignKey(Page, on_delete=models.SET_NULL, null=True, blank=True, related_name="+")
    bread_ingredient = models.ForeignKey(BreadIngredient, on_delete=models.SET_NULL, null=True, blank=True, related_name="+")
    content_panels = Page.content_panels + [
        DocumentChooserPanel("doc"),
        ImageChooserPanel("image"),
        PageChooserPanel("page"),
        SnippetChooserPanel("bread_ingredient"),
    ]

Migrate and try adding a new chooser test page.

Tested with a custom AdminChooser using the icon font which appears to work fine.

A quick search reveals there is no documentation on writing custom choosers as far as I can tell - meaning that there is no documentation to update. Only documentation to write ;)
I did find wagtail-generic-chooser but it looks like that completely overrides the chooser.html template so that needs to be updated separately to support SVG icons.

@thibaudcolas mind reviewing this? Thanks :pray:

Awesome! - thank you for your kind words @thibaudcolas! :smile:


Fatal Python Error plugin_manager(0.0.13)  and pymodaq (3.1.12)

Hi,
I have installed the latest version of pymodaq (3.1.12) on my computer (Windows 8).
It works fine but i have encoutered several issues.
1- There is a problem with QT5Bluetooth.dll when I launch dashboard: 'This Windows version (6.3.9600) does not support the required Bluetooth API. Consider updating to a more recent Windows (100.10586 or above)' There is two ways to resolve it.
A- You can rename this DLL by QT5Bluetooth.dll1 in miniconda3\envs\pymodaq3\Lib\site-packages\PyQt5\Qt5\bin.
B- Or you downgrade PyQT5 to PyQt5==5.9.2 but this is not compatible with pymodaq 3.1.12
2- More annoying I am not able to install plugins!
--> directly with pip (downloading the package on Github (I tried several)). The package is installed but not find by pymodaq as a package while they are in the site-packages of the environnement.
 --> using plugin_manager I have the following problem:

"Fatal Python erro: init!sys!streams: can't initialize sys standard streams
ValueError: Cannot open console output buffer for reading"
I am trying to resolve this problem but I am not yet succesful. If you have suggestions...
Below the (windows 8) details of the issue:
Signature du problème :
Nom d’événement de problème:	BEX64
Nom de l’application:	python.exe
Version de l’application:	3.7.10150.1013
Horodatage de l’application:	60394710
Nom du module par défaut:	ucrtbase.DLL
Version du module par défaut:	10.0.17134.12
Horodateur du module par défaut:	587decd7
Décalage de l’exception:<PHONE_NUMBER>06e75e
Code de l’exception:	c0000409
Données d’exception:<PHONE_NUMBER>000007
Version du système:	6.3.96<IP_ADDRESS>.256.48
Identificateur de paramètres régionaux:	1036
Information supplémentaire n° 1:	45b0
Information supplémentaire n° 2:	45b089d322579fb6ea427640784cdbad
Information supplémentaire n° 3:	5d37
Information supplémentaire n° 4:	5d3767b2124964653156aab613d58c39

Update:
Direct installation with pip is in reallty working fine. But some required packages wasn't installed. Pymodaq.log file (in pymodaq_local\log) helps me to resolve the problem.
Jérémie


Relax pixel width and height check to determine the ratio

The Aseprite File Format Specification says the following about the pixel width and pixel height fields:
BYTE        Pixel width (pixel ratio is "pixel width/pixel height").
If this or pixel height field is zero, pixel ratio is 1:1
BYTE        Pixel height
But the read_aseprite() function only considers a 1:1 pixel ratio if both width and height values are 1, and not when one of these has zero value.
There are some Aseprite editors (such as LibreSprite) that don't set these fields, even when only supports a 1:1 pixel ratio. But due read_aseprite() being that strict in checking the width and height, these Aseprite files can't be read and attempting to do so will fail with the following error:
UnsupportedFeature("Only pixel width:height ratio of 1:1 supported")

@alpine-alpaca @B-Reif any comments on this ?

I’m not a maintainer of this repo, but if this is spec compliant then LGTM

I’m not a maintainer of this repo, but if this is spec compliant then LGTM

Thanks! It seems this repo is abandoned...


Modify Reviews Table added number of issues are created by user

/claim #7

/claim #7

/claim #7  #8

@seveibar


⚠ Minecraft has degraded performance

In 9925362, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 1094 ms

Resolved: Minecraft performance has improved in 5d62a4b.


Adding route of login and sign up page

Since the website is migrated to flask we can't open login and sign up directly we have to add urls in flask .
After every Web page can be accessed by Flask

@ankitapuri the work is done can i make a PR for this issue

@adarshvulli kindly assign me and allow me to make a Pr for this


Make webapp a Maven modules

Move the pom content from gateway-ha over to the webapp folder.
Add dependency to gateway-ha
Update readme
Verify build, packaging and release

This way you can run mvn commands in the webapp module separately and use Maven to rebuild the webapp only.

Wdyt .,. makes sense right @wendigo ?