QueryBuilder in xpc-sys?

I ran across the xps-sys library, which looks like it's exactly what I need for a project that talks to launchd. However, the xpc-sys library references a QueryBuilder trait, which doesn't seem to exist within the xpc-sys crate, but instead in the launchk crate. Should the QueryBuilder trait get moved into the xpc-sys crate so that it's available for use to xpc-sys consumers?

@kaisq whoops -- yes that's quite inconvenient 😅! Will fix that and post a new release. Hang tight!

Thanks for the quick response! I see the PR you opened and it looks pretty straightforward and the build passed -- is that close to release?


Can anyone upload a pretrained model?

HI, Deal all,
Can anyone kindly upload a pretrained model. Training is really time consumping, I just want to evaluate the performance. Thank you.

ESPNetv2 is merged with EdgeNets. Check EdgeNets that contain several pretrained models for different tasks.
https://github.com/sacmehta/EdgeNets


Replace event_init() with event_base_new() for thread safety

Change to use event_base_new() instead of obsolete event_init() for creating
new event base. Also add evthread_use_pthreads() before using any libevent
function to enable thread-safe functions and structures in libevent.
By default, using this combination of APIs will add a lock to the event base.
This can prevent a potential race condition where one worker thread is polling on
its event base and handling requests while a new connection is dispatched and
added to that worker's event base. The performance is unlikely to be affected
by the lock.
This patch may relate to an ancient issue from 2010, or the one from 2012. According to libevent documentation, event_init() is deprecated and is totally unsafe for multithreaded use.

So there was an actual bug with very old versions of libevent which was causing those errors. I haven't personally seen a report of one in probably 6 years.
This change probably causes a performance regression; currently workers only modify their own libevents, and nothing changes cross-thread. If you look at thread.c and look around the cq_push/pop/etc stuff, you'll see that new connection dispatch works via pinging a pipe. The pipe is then read as a normal libevent event, and the worker thread modifies its own queue. This avoids having to lock/unlock around every libevent operation when connection handoffs are relatively rare.

Thanks for your detailed explanation! I also worry about the performance regression caused by lock.
But I still think using newer API would be good (more robust and easy to adapt to new features). So in my updated commit, I changed from old API to event_base_new_with_config(), and explicitly disabled locking on event_base by using event_config_set_flag(cfg, EVENT_BASE_FLAG_NOLOCK).

I'm a little paranoid about people building this against ancient libevents that may not have these API's...
I'll have to check (or you can and update here) on when it was added, in what version, or if it's reasonable to test for them before use.
I'd also probably remove the pthread/thread bits entirely from the libevent stuff until they're actually used, since that may have a side effect of making it harder to build for some people.

I removed pthread/thread bits from my PR entirely.
According to libevent changelog, event_base_new_with_config() and EVENT_BASE_FLAG_NOLOCK first appeared in Libevent 2.0.1-alpha.
So here are two choices:

Detect the libevent version: if version < 2.0.1, then use event_init(), otherwise use the newer APIs.
Ask users to upgrade to newer version of libevent if they want to use the newer version of memcached.

thanks!

is definitely not happening :) Many people switch to other key/value stores when posed with the trouble of having libevent on the system at all. Telling them to upgrade in the past has been a total wash, and there's no pressing feature need to force people to do it (yet).

There's an example of a version check on libevent in the code somewhere already.. there was some ancient version which broke everything and it does error on that.

I updated my PR with a version check and choose the corresponding API.
The event_base_free() function is defined in <event2/event.h>. It was first implemented in Libevent 1.2. So it is not affected by the version.

does that compile against older versions? :P (sorry, I'm being picky at this point)

Sorry for that :P
The solution is to check LIBEVENT_VERSION_NUMBER. If it is larger/equal to 0x02000101 (>= 2.0.2-alpha), it indicates that we can use newer APIs.

rad! pretty sure I'm okay with this :P maybe we'll use more features, maybe we'll rip out libevent. we'll see.
this change goes with the next release, either way.

went out in 1.5.6


Refactor out the ui services out of -api

To make a clear distinction of what is included in the "client" and "ui" api we can split the ui specific services out to a -ui module that depends on -api.
This enables us to easily separate the generation of the openapi files.

As mentioned on chat,
everything with JsonNode. ArrayNode, ObjectNode types are problematic, and we should make sure we try to split them out into a UI-api in the first instance where we can
we should also look at where we return jakarta.ws.rs.core.Response and probably change to org.jboss.resteasy.reactive.RestResponse, because we can have a typed response.
jakarta.ws.rs.core.Response is not generic

And also we should validate the non-ui api openapi schema,  set this to false:
https://github.com/Hyperfoil/Horreum/blob/master/horreum-api/pom.xml#L98

Ideally we should only use "core" data types to Java or the platform.
It could be good to spend a bit of time to look at other platforms way of doing it such that we make sure that we can make clients work across programming languages

I have looked at how we integrate with other programming languages and frameworks.
For all the JSON data I think we have to rely on java.lang.String, and then we need to validate in each of the API endpoints.
I would prefer the Jakarta classes, but the RestEasy one is ok as well


K8SPSMDB-764 release psmdb 1.13.0 fix operator image hash

Test name
Status

api-tests
passed


integ-cli: skip more case-senstive dockerfile tests on Windows

Followup to #11186. I was not able to catch those ones initially. These
tests overwrite dockerfile by creating another file named Dockerfile
and NTFS is case-sensitive. So skipping those tests for windows CLI.
Tests skipped:

TestBuildApiLowerDockerfile
TestBuildapiDoubleDockerfile

Signed-off-by: Ahmet Alp Balkan<EMAIL_ADDRESS>cc: @duglin @tiborvass

actually hold on --these tests might be failing because fakeGIT(...) is starting a web server on test machine not the remote DOCKER_TEST_HOST.

yep that's the case, I'll fix this once #10893 is merged.

Ping @ahmetalpbalkan

@tiborvass yeah still investigating sorry.

Submitting the correct fix at #11278.


Spk build pipelines should set image repository in the build

As a:
spk user
I want:
The spk service build and update pipeline to also pin a container repository
So that:
The generated manifest points to the ACR repository and image that is being built.
Describe the solution you'd like:
When i create a service, the build and update pipeline also runs fab set for both the image.tag and the image.repository mycontainerregistry.azurecr.io/image name
Acceptance Criteria:

[x] in the second stage of the the service build and update pipeline, when setting image.tag via fabrikate, also sets image.repository. The name of the acr is already in the variable group.

Describe alternatives you've considered:
Currently the user is expected to overwrite the image.repository value manually in a config file in the hld repository
Additional context:
By default, when creating a helm chart though helm, there are 3 default variables for image:
image:
  repository: mycontainerregistry.azurecr.io/mycontainername
  tag: latest
  pullPolicy: Always

the build pipeline sets image.tag, but we need to set image.repository at least once.
Does this require updates to documentation?:
Yes

If this is marked good first issue why the rush to get this in without a corresponding update to the integration tests.


book or resource that explains the math

I am watching this lecture:  https://www.youtube.com/watch?v=vz3D36VXefI
I can sort of follow but are there any other resources for an undergrad CS student to learn the underlying math and principles?

There are three other resources linked in the references section, two papers and one book, that cover this topic in extensive detail. I suggest starting there.
Bayesian stats and Gaussian Processes are really all you need to know.


Can this be applied to dynamic scenes?

Can this method be applied to dynamic scenes? Or is it limited to static scenes?

Our approach only applied to static scenes. We can further adapt to dynamic reconstruction by predicting the deformability of the cloud codes.


Sony RX1R M2 keeps crashing after enabling Wifi in the OpenMemories-Tweak

Hey,
i want to use a FTP App to Transfer my bought Sony Apps from my Camera as a backup.
But I can't connect to Wifi with my FTP App, so I have to use the Open Memories-Tweak app to enable Wifi and Connect to my Wifi Router... in the app everything is working I can enable and connect to my wifi, even Telnet is working just fine, but when I try to exit the app with the menu button or the play button my camera just reboots :(
Anything I can do about it?
PS Happy new year :)

Okay, found an easy way to get my installed apps from the camera, adb ftw. But the problem with crashing on exit the app still exists

Here's something to try: tweak-dev.zip (unzip to get the apk)
The app should now exit to the android launcher instead of the menu, maybe this fixes the issue?

Hi,
I mainly registered to say thank you for this "dev-update"!
I've just bought an RX10M3 and put my old SD card into it. Due to its size it can get easily full. That shouldn't be a problem, because the cam has wi-fi, as well my smartphone and tablet, with about 5-5 GB free space on them. Real shame that the built in send to smartphone function sends only a low-res jpg and also no raw.
3rd party apps can't turn the wi-fi for themselves on and freeze. I had the earlier mentioned "camera restarts after exiting the OM Tweaks" problem when i tried to turn wi-fi on with that. But the latest build just works awesomely! Exiting only to the android launcher fixes the restart issue.
So if somebody wants to be able to send data from the camera to an FTP server, this is how you do it!
I'm really not into programming and electronics, but if I can help you in any ways, or just provide data, tell me.

Here's something to try: tweak-dev.zip (unzip to get the apk)

The app should now exit to the android launcher instead of the menu, maybe this fixes the issue?
i Want to install the APK and test it, but all my Macs are on high Sierra and I can't connect the camera to them because the Mac will crash instantly, when I try to install the apk to the camera.
Thanks for the help maybe with some more time and a windows pc I will test it and give you feedback.
Greetings
Carsten

@bulba220 Thanks for testing and reporting, I'll commit this change to the repository.
I'm always interested in firmware dumps. It would be great if you could dump the RX10M3 firmware and upload it as described in my comment above. Please let me know if you need any help.

@bam2000 The os x driver situation is a mess. I can only suggest setting the camera to MTP mode, this might be more reliable.

thanks for the tip with MTP Mode :)
I have installed the modified apk and can confirm it is not crashing when enabling wifi on my RX1R M2
great work :)

@bulba220 Thanks for the dump!


Revert "Some common utilities to avoid duplication."

Reverts AzureAD/microsoft-authentication-library-common-for-android#978
I thought the checks has passed - my mistake.

just an unstable CI build. :/


ENH: Add Python wrapping for SpatialOrientationAdapter

To simplify this, SpatialOrientationAdapter no longer
inherits from OrientationAdapterBase.
Also add test to exercise Python wrapping of SpatialOrientationAdapter.
PR Checklist

[ ] No API changes were made (or the changes have been approved)
[x] No major design changes were made (or the changes have been approved)
[x] Added test (or behavior not changed)
[x] Updated API documentation (or API not changed)
[x] Added license to new files (if any)
[x] Added Python wrapping to new files (if any) as described in ITK Software Guide Section 9.5
[ ] Added ITK examples for all new major features (if any)

The first force-push makes a small change, the second is a plain rebase.


[Accessibility]A11y_AzureDataStudio_CreateDatabaseMasterKey_ColorContrast: Color contrast ratio of "Preview button" for normal theme is below the expected ratio i.e 4.5:1

“Check out Keros!  - Identify accessibility bugs before check-in and make bug fixing faster and easier.
GitHubTags: #A11yMAS; #A11yTCS; #MAS1.4.3; #A11y_AzureDataStudio; #Win32; #DesktopApp
Environment Details:
Application name: Azure Data Studio
Version: 1.8.0-insider (user setup)
Electron: 3.1.8
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763
Additional Details
Tool Name: ColorContrast
MAS Reference:MAS1.4.3
Repro Steps:
1.Launch Visual Studio code desktop application.
2.Navigate to "Enable SQL server2019 preview->select table from the database->Create External Table screen should open->click on next button.
3.Navigate to Setting button of Activity Bar and select "Color Theme" option.
4.Open color contrast analyser and check the color contrast ratio.
5.It shows color contrast ratio less than expected color contrast ratio.
Actual:
Color contrast ratio for "Preview", "Next", and "Cancel" buttons is showing as 3.5:1 for normal theme.
Same issue observed for below page:
1.CreateConntionDataSrc: Enable SQL server2019 preview->select table from the database->Create External Table screen should open->Next button->Create Database Master Key screen should open->click on next button.
2.CSVModifyColumn: Connect to database->navigate to the Data services folder->HDFS Folder-> navigate to CSV files folder->Right click on the files->Select option Create external table from CSV->Click on the "Next" button->Click on next button.
Expected:
The expected color contrast ratio for "Preview", "Next", and "Cancel" buttons should be greater than or equal to 4.5:1 ratio.
User Impact:
Low vision User will find it difficult to understand and will be confused if they will not able to see the buttons on this page.
Recommendations:
Please refer the following snippet link for fixes:
https://microsoft.sharepoint.com/teams/msenable/mas/pages/browse-fixes.aspx
MAS Reference:
MAS1.4.3- https://microsoft.sharepoint.com/%3Aw%3A/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={a73546c7-765f-489c-b18f-afb659fe99e6}
Attachment For Reference:

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

Similar to issue : #6667
Should be fixed in https://github.com/microsoft/azuredatastudio/pull/6774

As @udeeshagautam mentioned the issue has been fixed since this bug was opened. Closing.


allows to log RotationAxisAngle directly in Python

What
I found myself wanting to write this:
rr2.log("world/child", rr2.dt.RotationAxisAngle(axis=(0, 1, 0), angle=i / 100.0))

In order to do so, I made it so that this now logs a Transform3D archetype, just like logging TranslationRotationScale3D  and TranslationAndMat3x3 already do.
Now that I have it down, I see good reasons why we shouldn't do this: Why not also allow logging Rotation3D as an archetype (this is a component that is used inside Boxes3D archetype).
Checklist

[ ] I have read and agree to Contributor Guide and the Code of Conduct
[ ] I've included a screenshot or gif (if applicable)
[ ] I have tested demo.rerun.io (if applicable)

PR Build Summary
Docs preview
Examples preview
Recent benchmark results
Wasm size tracking

let's not do this


Is there a way to package local dependencies?

I'm writing a tool that packages rust crates into python packages. For that, I need to pack all local crates into a .tar.gz. For a single crate, I use cargo package --list --allow-dirty and take those files. This however breaks when another local crate is linked.
I can find all local packages using cargo metadata and copying also works, but then I need to rewrite each Cargo.toml to point to the updated locations since I can't conserve the existing directory structure. Are there any rules or references on how to rewrite the Cargo.toml, or is there a recommended mechanism for doing this kind of automated replacement?

cargo vendor may do what you're looking for.

Is there an option to only vendor local crates? As I understood it, cargo vendor will always vendor everything, which most users wouldn't want.

I don't think there is anything existing that will do that.

can't conserve the existing directory structure

Why can you preserve the original structure?

Why can't you preserve the original structure?

Users might e.g. use crates that are on a different disk or other file system funkiness, and I expect trying to reproduce that structure in a zip file would rather error-prone, especially cross platform.

I don't think there is anything existing that will do that.

Ok, thanks anyway, I've now gone with a cargo-edit style solution of rewriting the toml (https://github.com/PyO3/maturin/pull/441)


Support additional CI variables

Fix https://github.com/firecow/gitlab-ci-local/issues/653, https://github.com/firecow/gitlab-ci-local/issues/1112

@firecow Do you know when you are going to create a new release?

@hverlin I'll make one now

Thanks!


fix: continue if wordform cannot be generated from analysis

Fixes #693
Note: I have NO IDEA how to reproduce this bug, but I've made the log dump more useful information to actually reproduce #693.

Codecov Report

Merging #792 (f429ebc) into master (2c6afac) will increase coverage by 0.05%.
The diff coverage is 100.00%.

:exclamation: Current head f429ebc differs from pull request most recent head 629e9d9. Consider uploading reports for the commit 629e9d9 to get more accurate results

@@            Coverage Diff             @@
##           master     #792      +/-   ##
==========================================
+ Coverage   79.75%   79.80%   +0.05%
==========================================
  Files         109      109
  Lines        4178     4179       +1
  Branches      615      615
==========================================
+ Hits         3332     3335       +3
+ Misses        734      731       -3
- Partials      112      113       +1

Impacted Files
Coverage Δ

CreeDictionary/API/search/lookup.py
91.37% <100.00%> (+3.66%)
:arrow_up:

.../search_quality/management/commands/featuredump.py
32.69% <0.00%> (ø)

...ranslate/management/commands/translatewordforms.py
73.17% <0.00%> (ø)

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 2c6afac...629e9d9. Read the comment docs.


[Macros] Macro-metaprogram macro roles

Introduce X-macros for the various macro roles, and use them to macro-metaprogram a lot of boilerplate involved with introducing new macro roles.

@swift-ci please smoke test

@swift-ci please smoke test


issue with channel selection when untargeted & targeted LCNTables are present

I have a test service list with 1 untargeted (default) LCNTable as well as 3 targeted LCNTables
http://dvb-i.bmt-technik.de/demo/bmt_plugfest_2020.xml
After selecting the service list in the SL selection, the UI will present the different regions for choice, but clicking on any region will do nothing.
I have narrowed down the issue. After removing the untargeted LCNTable, there is no issue, so it appears the combination of both is causing issues.
http://dvb-i.bmt-technik.de/demo/bmt_plugfest_2020_ohne_default_lcn.xml
The issue was not present 2 weeks ago before the latest updates.

What should be the user experience when a service list contains both untargeted and region targeted LCN tables?
I can envision a couple of options

The untargetted LCN table is ignored and the user must select a region
The user selection should include a default choice which selects the untargeted LCN table

Option 2 seems like the bets choice and aligns with the specification text "TargetRegion: If not specified, no regional constraints exist and the LCN table is applicable everywhere."

Agreed, option 2 seems like the best choice, esp. for testing purposes. Option 1 is like it was implemented before.
In general, I like to include an untargeted LCNtable as a default incase a device/app does not implement region selection/ there is no match after entering a postcode / user skips region selection.


Update Links “tiktok-29”

Automatically generated by Netlify CMS

👷 Deploy Preview for distracted-hoover-7b89cc processing.
🔨 Explore the source changes: ae09701738dc8a725af93d8b2f16816f5695391b
🔍 Inspect the deploy log: https://app.netlify.com/sites/distracted-hoover-7b89cc/deploys/611f32a43cb8ee0008640dd3


wrong answer whether a URL is allowed

Wrong answer whether a URL is allowed with such robots rules:
Crawl-delay: 1

User-agent: *
Disallow: /*%
Disallow: /*.aspx
Disallow: /*.aspx*

There are a lot of urls with Crawl-delay: in the head of the file.
Source url:  https://learningnetwork.cisco.com/robots.txt
Steps for reproducing:
In [1]: from reppy.cache import RobotsCache
   ...: cache = RobotsCache(capacity=100)

In [16]: cache.allowed('http://learningnetwork.cisco.com', 'my')
Out[16]: False

Full robots file:
# Puppet managed file

Crawl-delay: 1

Sitemap: https://learningnetwork.cisco.com/sitemap.xml

User-agent: *
Disallow: /*%
Disallow: /*.aspx
Disallow: /*.aspx*
Disallow: /*.jspa
Disallow: /*.jspa*
Disallow: /*/authors/
Disallow: /*/bookmarks
Disallow: /*/customize-container.jspa
Disallow: /*secondVersionNumber*
Disallow: /*/profile-status-list.jspa
Disallow: /*/render-widget!execute.jspa
Disallow: /*/restore
Disallow: /*/restore?version=
Disallow: /*/spotlight-search.jspa
Disallow: /*/status
Disallow: /*/version
Disallow: /*?author
Disallow: /*?containerType=
Disallow: /*@
Disallow: /*=tags
Disallow: /*answerCategory=
Disallow: /*author=
Disallow: /*bookmarks*
Disallow: /*filterID=
Disallow: /*itemView=
Disallow: /*jsessionid=
Disallow: /*-picker.jspa?
Disallow: /*searchQuestions=
Disallow: /*start=
Disallow: /*tab=
Disallow: /*tags=
Disallow: /*tagSet=
Disallow: /*targetUser=
Disallow: /*tstart=
Disallow: /*version=
Disallow: /*view=
Disallow: /bookmarks/
Disallow: /c-
Disallow: /*c-*
Disallow: /docs/*/c-
Disallow: /docs/c-
Disallow: /ITDIT/
Disallow: /mailto*
Disallow: /message/
Disallow: /people/*
Disallow: /poll-post!input.jspa?
Disallow: /post!
Disallow: /post!imagePicker.jspa
Disallow: /post!reply.jspa?messageID=
Disallow: /Products/*.aspx
Disallow: /search.jspa?
Disallow: /servlet/JiveServlet
Disallow: /*servlet*
Disallow: /tags
Disallow: /thread/*/c-
Disallow: /thread/c-
Disallow: /thread-to-doc.jspa
Disallow: /user-picker.jspa

Can you please include what version of reppy you're using? In rep-cpp, I see an exception thrown with a message saying "Need User-Agent" which is fairly reasonable behavior for a malformed robots.txt. Yes, I realize that you may be seeing this as a common error, but I don't think it's reasonable behavior for reppy to assume a malformed robots.txt is allowing robots.
Similarly, using reppy directly, I see the following:
>>> robot = Robots.parse('http://learningnetwork.cisco.com/robots.txt', """
... Crawl-delay: 1
...
... User-agent: *
... Disallow: /*%
... Disallow: /*.aspx
... Disallow: /*.aspx*
... """)
Traceback (most recent call last):
  File "<stdin>", line 8, in <module>
  File "reppy/robots.pyx", line 71, in reppy.robots.ParseMethod (reppy/robots.cpp:2375)
  File "reppy/robots.pyx", line 129, in reppy.robots.Robots.__init__ (reppy/robots.cpp:3947)
ValueError: Need User-Agent

You may be able to handle this by changing the Cache policy to use something other than ReraiseExceptionPolicy.

Hi.
Reppy version:
pip freeze | grep reppy
reppy==0.4.3

Regarding DEFAULT_CACHE_POLICY:
class RobotsCache(BaseCache):
    """A cache of Robots objects."""

    DEFAULT_CACHE_POLICY = DefaultObjectPolicy(ttl=TTL, factory=AllowAll)

Why do you think this robots.txt is malformed?

The Crawl-Delay declaration must appear under the scope of User-Agent declaration. It is technically not allowed at the "top-level". The correct order would be:
User-agent: *
Crawl-delay: 1
Disallow: /*%
Disallow: /*.aspx
Disallow: /*.aspx*

The original given example is unclear which bot the Crawl-delay is intended to apply to. There is no implicit wildcard scope for Crawl-delay. You must declare User-agent: * first if you want it to apply globally according to the specification.

I've been sort of on the fence about how to deal with this (directives appearing outside of a User-Agent block). On the one hand, it is malformed, per the RFC (in the case of Allow and Disallow) and presumably by extension for Crawl-Delay. On the other hand, surely some level of flexibility is called for. I see no obvious winner among:

throw an exception saying it's malformed and why
ignore those directives that appear outside of User-Agent (provided they ought to be in such a block)
treat those directives as associated with the default User-Agent (*)

This is actually more common that I'd originally hope. I'm trying to dig up some numbers from some experiments I did.

In a sample of about 7.7M URLs taken from Silo (a Moz-internal source of URLs that are believed to be on relatively high-quality sites):
7249712 (93.58%) allowed
 497216 ( 6.42%) disallowed (via `Disallow` or exception)
 144112 ( 1.86%) exceptions

Just under 2% experienced an exception while trying to check if a page was allowed. The exceptions encountered:
Exceptions by type
------------------
  77720 ( 1.00%) ValueError
  23192 ( 0.30%) ConnectionException
  20656 ( 0.27%) TimeoutException
  18603 ( 0.24%) BadStatusCode
   2824 ( 0.04%) ExcessiveRedirects
    658          SSLException
    137          DecodeError
    116          ContentTooLong
    114          MalformedUrl
     86          ProtocolError
      6          LocationValueError

Some of these are transient or at worst, unrelated to reppy itself. But for 1% of URLs that got a ValueError:
ValueError
----------
  69071 ValueError('Need User-Agent',)     # Starts with "Disallow"
   8608 ValueError('Need User-Agentm',)    # Starts with "Allow"
     41 ValueError('stoi',)

The stoi errors come from parsing this (notice the Allow directive has an odd URL. But this is small potatoes, and an issue for url-py and url-cpp.
User-Agent: *
Allow: //sitemap:http://www.lifeguardbreathtester.com/sitemap.xml

User-Agent:*
Disallow: /staging/

More interesting is the fact that essentially about 1% of URLs have a robots.txt that experiences this issue. Not a disastrous portion, but enough to be problematic for a library with high aims.
Methodological note: these URLs were sampled directly from Silo, with no uniquification. So necessarily, this describes fewer than 7.7M FQDNs (and thus fewer than 7.7M robots.txt files).

I think choice 3 is reasonable; especially, if you create a new top-level User-Agent context that is distinct from the literal * agent. This way you could actually report on them like site issues for Aardwolf, but still handle them gracefully.

agree with point 3, it would be more preferable

This was resolved by #54. Unscoped Crawl-Delay directives are treated as the * agent.


Incorrect type promotion in random.choice

As discovered in #11237, random.choice throws a type promotion error when x64 is enabled and p is float32.
The following demonstrates the issue. Executing:
import jax
import jax.numpy as jnp
jax.config.update("jax_enable_x64", True)
with jax.numpy_dtype_promotion("strict"):
    jax.random.choice(jax.random.PRNGKey(0), 5, p=jnp.ones(5, dtype=jnp.float32))

results in the following type promotion error:

Traceback
Traceback (most recent call last):
  File "<stdin>", line 2, in <module>
  File "/Users/dforemanmackey/src/google/jax/jax/_src/random.py", line 499, in choice
    r = p_cuml[-1] * (1 - uniform(key, shape))
  File "/Users/dforemanmackey/src/google/jax/jax/_src/numpy/lax_numpy.py", line 4586, in deferring_binary_op
    return binary_op(self, other)
  File "/Users/dforemanmackey/src/google/jax/jax/_src/numpy/ufuncs.py", line 80, in fn
    x1, x2 = _promote_args(numpy_fn.__name__, x1, x2)
  File "/Users/dforemanmackey/src/google/jax/jax/_src/numpy/util.py", line 332, in _promote_args
    return _promote_shapes(fun_name, *_promote_dtypes(*args))
  File "/Users/dforemanmackey/src/google/jax/jax/_src/numpy/util.py", line 262, in _promote_dtypes
    to_dtype, weak_type = dtypes._lattice_result_type(*args)
jax._src.dtypes.TypePromotionError: Input dtypes ('float32', 'float64') have no available implicit dtype promotion path when jax_numpy_dtype_promotion=strict. Try explicitly casting inputs to the desired output type, or set jax_numpy_dtype_promotion=standard.

The offending line is: https://github.com/google/jax/blob/de464fcf22c8bf7a2931182f8095bc01530df9fe/jax/_src/random.py#L499
And I think the fix is as simple as:
- r = p_cuml[-1] * (1 - uniform(key, shape))
+ r = p_cuml[-1] * (1 - uniform(key, shape, dtype=p_cuml.dtype))

But I haven't checked in detail!

Good catch - thanks!


Fixed a bug where if awscli is missing, or missing credentials causes…

… puppet to fail and stop processing anything else

Relates to issue #2


V3 design doc

It's got all the text. A few diagrams will probably be helpful.
It's a start.

LGTM


Instances Panel returns 404 Not Found

The NiFi instances panel under Configuration > Lookups > NiFi Instances throws a 404 error. Will need the instances panel to correctly configure a NiFi instance to use with the Splunk app. Do let me know if there are any updates on this! Thanks!

Hi jowayn,
I have that error in the past on
What splunk version are you using?
do you have the access to Lookups menu in splunk  because can be  problem related to permissions
thanks

Hi, I am using Splunk version 9.0.0. Yes, I do have access to the Lookups Menu. Is the Instances panel working on your end? What suggestions might you have to fix this issue? Thanks!

yes menu is working find on my instance where I'm admin with full access  splunk 8.1.1
if you don;t have access to lookups menu in splunk (Settings--> Lookups)  fast solution is to import a lookups in csv file, i did this and was working but let's see what @kudawdev suggest.

Could you elaborate on what you mean by a lookups csv? What should this csv contain?
I do have access to Settings --> Lookups as admin. Have tried to downgrade to Splunk 8.1.1 as well, but still facing the same issue of a 404 error when accessing the Lookups > NiFi Instances panel. Thank you so much for your help!

Update: Have found the fix for the problem. It is simply a matter of installing the additional 2 Splunk apps
(Lookup File Editor
Status Indicator - Custom Visualization

yes correct  related to app "Lookup File Editor" , in my scenario for security policy  this app is denied, so I'm uploaded CSV .
Thanks for details

Hi,
We add the pre-requisites in the documentation:

Thanks.

Hello, it's related to pre-requisites. Regards


安装报PIP依赖错误

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
sentence-transformers 2.2.2 requires scikit-learn, which is not installed.
sentence-transformers 2.2.2 requires scipy, which is not installed.
sentence-transformers 2.2.2 requires torch>=1.6.0, which is not installed.
sentence-transformers 2.2.2 requires transformers<5.0.0,>=4.6.0, which is not installed.
torchvision 0.16.0 requires pillow!=8.3.*,>=5.3.0, which is not installed.
torchvision 0.16.0 requires torch==2.1.0, which is not installed.
nicegui 1.4.22 requires fastapi<0.110.0,>=0.109.1, but you have fastapi 0.99.1 which is incompatible.

似乎不是这个项目的，nicegui 和 fastapi 。请按照文档新建一个 conda 环境。


Api refactoring

Description
Improve API, implement missing algos, fix headers installation:

use ThermoInterface as the minimum one and introduce ThermoExtendedInterface for inverse methods

use templates to implement an interface for a given type (double, or vector for instance)

make PolyGas properties accessible
implement pickling of binded types
refactor function args naming
rename template names to be more explicit
rename PolyGas.gas to PolyGas.m_props
implement IdealGas.mach_f_wqa instead of dummy value 1. returned
add overloads without tol and max_iter for non iterative functions of IdealGas (keep signature with tol and max_iter for compliance with the interface)
add bindings for all methods
add boost dep
fix installed headers

Closes #7


[NEW ALGORITHM] Reversing the linked list (reversing the links)

Issue will be closed if:

You mention more than one algorithm. You can create a separate issue for each algorithm once the current one is completed.
You propose an algorithm that is already present or has been mentioned in a previous issue.
You create a new issue without completing your previous issue.

Note: These actions will be taken seriously. Failure to follow the guidelines may result in the immediate closure of your issue.

Name:  Reversing the linked list
[NEW ALGORITHM]
About:
Reversing the linked list basically wants to reverse the links of node by keeping the position of nodes same.
ex- 1->2->3->4->5->NULL
after reversal: NULL<-1<-2<-3<-4<-5

Labels:
new algorithm, gssoc-ext, hacktoberfest, level1

Assignees:

[x] Contributor in GSSoC-ext
[x] Want to work on it

Reversing the linked list in singly, circular singly, doubly and circular doubly linked list.

@Tanyajain2006 @pankaj-bind
Please assign this to me . I would Like to work on this.

@Tanyajain2006 @pankaj-bind Please assign this to me . I would Like to work on this.

Hi Ritika, I'm so sorry. I have already done this. When the project admin agrees, I just have to create a pull request, that's it

Hello sir, you just assigned it to me and now you have closed it. So,
should I now not work on it?
On Mon, 28 Oct, 2024, 11:21 am Pankaj Kumar Bind, @.***>
wrote:

Closed #1251 https://github.com/AlgoGenesis/C/issues/1251 as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/AlgoGenesis/C/issues/1251#event-14945521323, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BCRSCNYGEICT5M5HQSOGAO3Z5XGGBAVCNFSM6AAAAABQUM3TDWVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUHE2DKNJSGEZTEMY
.
You are receiving this because you were assigned.Message ID:
@.***>


Reeplace mesh obtained from maliput by lines

Context
When exporting via mcap we are using the mesh of the road network as it comes from maliput::utility::GenerateObjFile method.
Proposal
It would be better (more performant) if we add lines representing the boundaries of the lanes in the scene rather than the entire mesh of the road network.

:+1:


Package tidy up

Repo checklist:
Urgent:

[x] A require-dbt-version parameter in the dbt_project.yml:

require-dbt-version: [">=0.17.0", "<0.18.0"]

[x] The dbt_project.yml is in version 2 format (upgrading docs)
[x] Any sample dbt_project.yml snippets in the README.md are in v2 syntax (especially for packages that use vars
[x] Release is of format major.minor.patch, e.g. 1.0.0
[x] A license (example)
[x] If this package relies on dbt-utils, make sure the range allows v0.4.x

packages:
  - package: fishtown-analytics/dbt_utils
    version: ["???", "<0.5.0"]

Integration tests
If this package has integration tests:

[x] The dbt_project.yml of the integration tests is in v2 format
[x] CircleCI uses python v3.6.3
[x] The dbt_project.yml does not have a require-dbt-version config (it should be inherited from the package)

Quick wins:

[x] Issue and PR templates (examples — make sure you update for the right package name)
[x] A codeowner (example)
[x] If required, a level of support header in the README

⚠ This package is currently not actively maintained.

More in-depth improvements

[x] Installation instructions (see segment), including:

Link to packages docs
Variables that need to be included in the dbt_project.yml file
Listed database support

[ ] A link to our package contribution guide (Might formalize this as a CONTRIBUTING.md file)
[x] Models are documented
[ ] Macros are documented
[x] Integration tests
[x] Move model logic intro model files, rather than entirely in adapter macros

Requires admin rights / Claire

[x] Repo is named dbt-<package_name>

[x] The hub URL listed on the repo

[ ] A Zap to the #package-releases channel in dbt Slack

@clrclr any plans to support dbt_utils at 0.5.0? 🙂


Support Exclusion of H1 Headings

We follow CommonMark – we have a single H1 to start each document. In most cases this duplicates (or slightly restates) the title from the metadata, which looks weird and takes up unnecessary space in Confluence.
This request is for a flag to remove the leading H1 on all documents before pushing to Confluence.

Is it possible that H1 headings are now always ignored, with or without use of the --drop-h1 flag? I'm not using the flag, and yet my H1 is not being included.

Nevermind - it seems that a line break is required between the metadata and the first line of content.
With this, the H1 isn't rendered in Confluence ...
<!-- Space: <space> -->
<!-- Title: <title> -->
# H1 Title

With this, the H1 is rendered in Confluence ...
<!-- Space: <space> -->
<!-- Title: <title> -->

# H1 Title

If this seems like a bug, I can open a new issue.

@rhbecker thx for the bug report. It is a bug. I'll just rename the issue.


fix: Can not add properties in "SetProperties" action

Description
SetProperties leverages the ArrayFieldItem component. On blur, the item is removed if it has an empty value:

The children of SetProperties rely on Intellisense fields. But the onBlur callback was not passed in the array of dependency of the useEffect responsible for managing Intellisense blur. Therefore the initial (empty) value was used and always removed the item, regardless of the current real value. Adding to the array of dependency fixed the issue.
This PR also contains some minor optimizations (rendering and listeners) for Intellisense.
closes #4526
Screenshots

Coverage decreased (-0.006%) to 55.166% when pulling 8563fa942a2ff721574c608893f3f9ef957a0434 on leugene/issue4526 into 5bf51997a5b43f142b66f8f31cab150fed3caf49 on main.


[AVM Module Issue]: Missing the output IDENTITY_PRINCIPAL_ID

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Issue Type?
Feature Request
(Optional) Module Version
No response
(Optional) Correlation Id
No response
Description
Please add the output  IDENTITY_PRINCIPAL_ID.
For example (azd):
https://github.com/Azure/azure-dev/blob/main/templates/common/infra/terraform/core/host/appservice/appservicejava/appservicejava_output.tf#L5
CC: @jongio and @donovm4

Hi @Menghua1 - please reference 0.7.0 for the latest outputs.
In the examples/interfaces, there is an example using the output with managed_identites


hue changed to zero

When creating an hsl object with a specific hue, but saturation an lightness set to 0, the hue will also be set to zero
test case:
expect(colord({ h: 50, s: 0, l: 0 }).toHsl().h).toBe(50)

this test will fail and the received result. The expected result is, that the hue stays the same.

Hi! Not sure it's a bug: a color with no saturation and lightness is black.
Black doesn't have any hue since... you know... it's black :)

Well, we use colord for our color picker. As you can see, when you change the hue, color panel should change. This is only possible if we know the hue.

We had to implement a fix on our side, where we override the hue manually on the object colord gives us. This extra step should not be necessary. An HSL object passed to the colrd function should always be the same as the one we receive when calling toHsl()

As a developer of a color picker component, I would highly recommend storing the current hue in a separate variable.
You can't rely on color conversion libraries here since white, black and any grayscale color could break the conversion between color spaces.

This makes sense. Thanks for you help!


signInWithPassword ignores options.data instead of writing it to user_metadata

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
signInWithPassword ignores the options.data field, even though the TypeScript definitions list options.data as a supported field – at least in the case where you provide a phone number.
To Reproduce
Call supabase.auth.signInWithPassword({ phone, password, options: { data } }).
Expected behavior
options.data should be persisted in auth.users.user_metadata.
Ideally, this should also work for the case where you provide email instead of phone.
System information

Version of supabase-js: 1.110.1
Version of Node.js: 18.17.1

Additional context
Related question: https://github.com/orgs/supabase/discussions/8873

Uhm... any chance this will be resolved at some point? Or are we better off using the REST API directly?

Or would a pull request fixing this be merged?

Is this an issue with the type definition
export type SignInWithPasswordCredentials =   | {       /** The user's email address. */       email: string       /** The user's password. */       password: string       options?: {         /** Verification token received when the user completes the captcha on the site. */         captchaToken?: string       }     }   | {       /** The user's phone number. */       phone: string       /** The user's password. */       password: string       options?: {         /**          * A custom data object to store the user's metadata. This maps to the auth.users.user_metadatacolumn.          *          * Thedatashould be a JSON object that includes user-specific info, such as their first and last name.          */         data?: object         /** Verification token received when the user completes the captcha on the site. */         captchaToken?: string       }     }

@mb21 @JJAHMEDAMER apologies for the oversight, this is an issue with the type definition and i've just put up a PR to fix this: https://github.com/supabase/gotrue-js/pull/848

@kangmingtay thanks for taking a look at this! My preferred outcome would of course have been that the data is written to user_metadata, not that the type definition is removed. Would this be considered a feature request? Would it be merged if I made a PR?

@kangmingtay and @hf you're working for supabase, right? Could you please answer my question(s) about whether a PR would be accepted to save signInWithPassword's options.data argument to user_metadata? Or should I open a new issue with this feature request?

@mb21 Hi, may you share your solution?
Anyway.. they removed the option to pass data when you sign in..
so i think we need to use a procedure/function in order to sign in..

@Giasinit I haven't actually coded anything and am not going to unless somebody from supabase gives an indication that it might be merged. But as unresponsive as they have been it's unclear to me whether supabase auth is actively developed. Therefore we're looking to switch to https://lucia-auth.com


nefi crashing during pipeline processing

Is nefi2 running without errors for you?
I am having some issues, for example.

run nefi2 from source
open an image and run the pipeline
click "Run" button again
I received:

Failed to process pipeline
Traceback (most recent call last):
  File "/home/tastyminerals/dev/nefi/nefi2/view/main_controller.py", line 1883, in run
    self.pipeline.process()
  File "/home/tastyminerals/dev/nefi/nefi2/model/pipeline.py", line 318, in process
    self.save_pipeline_json(pip_name, os.path.join(out_path, pip_name))
  File "/home/tastyminerals/dev/nefi/nefi2/model/pipeline.py", line 689, in save_pipeline_json
    with open(url + ".json", "wb+") as outfile:
FileNotFoundError: [Errno 2] No such file or directory: '/home/tastyminerals/dev/nefi/output/polycephalum_high_poly_#2_17h17m11s/polycephalum_high.json'

This occurrs because polycephalum_high_poly_#2_17h17m11s dir does not exist when nefi searches for polycephalum_high.json.
Another issue:

run nefi2 from source
open an image and run the pipeline
open another image and choose another pipeline
click "Run"
I received:

Set modified
Set modified
Set modified
Set modified
Set modified
Set modified
Start pipeline at 0
UnSet modified
Current cat <segmentation.CatBody object at 0x7fb7ec079898>
UnSet modified
Current cat <thinning.CatBody object at 0x7fb7ec0799e8>
UnSet modified
Current cat <gdetection.CatBody object at 0x7fb7f1165e80>
UnSet modified
Current cat <gfiltering.CatBody object at 0x7fb7f11597b8>
discarding a total of 155 edges ...
UnSet modified
Current cat <gfiltering.CatBody object at 0x7fb7f11522b0>
Smoothed a total of 173 degree 2 nodes ...
UnSet modified
Current cat <gfiltering.CatBody object at 0x7fb7f114cdd8>
Set modified
Set modified
Set modified
Set modified
Set modified
Set modified
Set modified
Set modified
Set modified
Set modified
Set modified
Set modified
Start pipeline at 0
UnSet modified
Current cat <preprocessing.CatBody object at 0x7fb7f11c6080>
Segmentation fault (core dumped)

I can't tell if these two issues are connected.
Can you reproduce the following?

test comment

Hi, i cant reproduce your error. Everything works smooth for me

Before trying out, I removed my local source files and did a fresh clone, I renamed thinning.py into thinning_alg.py because it was conflicting with thinning module. After that I ran ./nefi2.py and executed the steps above. Make sure you run nefi from command line, not IDE and you have fetched the upstream changes.

Still working for me.
We shouldn't merge anything with master which could create problems. User which want to work on the actual software branch would be affected too. At least create a separate branch.
Anyways, the problem still persists?

Disregard the second one, local issue.
I have reproduced the first error in virtualbox. When you run the pipeline once and then hit "Run" again, the pipeline crashes.


about depth loss increasing.

Hi,
When I add the use the depth-nerfacto,  the depth loss and intervel loss increased.
The train script is below.
export CUDA_VISIBLE_DEVICES=0
ns-train depth-nerfacto  --viewer.websocket-port=7009 \
                --machine.num-gpus 1 \
                --experiment-name kitti_00_200_depth \
                --data data/kitti/kitti_00_200_depth \
                --vis tensorboard

The detailed log is below.

The predicted depth map

The render image

It looks interesting! Could you please share how you preprocess the kitti data? Thanks!

@rockywind I have the same problem, please tell me how you solved it.

I am observing similar issue on scannet

Hi, When I add the use the depth-nerfacto, the depth loss and intervel loss increased. The train script is below.
export CUDA_VISIBLE_DEVICES=0
ns-train depth-nerfacto  --viewer.websocket-port=7009 \
                --machine.num-gpus 1 \
                --experiment-name kitti_00_200_depth \
                --data data/kitti/kitti_00_200_depth \
                --vis tensorboard

The detailed log is below.   The predicted depth map  The render image

Same problem as yours, have you found any reasons or solutions?

Is the depth loss for eval being computed on your sparse depth input? If so, there are a lot of zeroes for the invalid regions.

Thank you, Ethan.
The depth is not too sparse I think, I am using depth maps from scannet, which has holes where the kinect sensor didn't record valid depth. The depth loss is masked out at those invalid locations.
I checked the min/max of the scannet depth (which is gt) and the nerf predicted depth. I am noticing that they have same min/Max values i.e. between (0,9) but the sensor depth is usually between 0-2 with some outliers > 2, while the nerf depth has lots of depths > 2. My guess is that it is being sensitive to these outliers, and if I mask out the outliers from ground-truth, it might work.  I am going to try it now and report back how it went.
Let me know what you think, and if you think there is a better way to deal with outliers, let me know.

Does the depth of the NeRF look reasonable when you don't train the depth-nerfacto model and instead just train a normal nerfacto model -- perhaps with more paramaters (nerfacto-huge, etc.)? I guess the outliers could cause some issues, as you're suggesting. If the NeRF depends on the depth to get good results, then it's probably just a hard setting where there isn't enough parallax in your training data. Maybe worth switching to a surface-based method in that case.
Also maybe you could try relative depth supervision (i.e., sparse nerf). It defeats the purpose of having exact metric depth, but it could be helpful to not hurt the NeRF from optimizing it's photometric objective.

I did try training a nerf model without depth supervision -- it is the same architecture and parameters but I zero out the depth loss. The corresponding wandb is here: https://wandb.ai/ayushjain1144/nerfstudio-project/runs/9leiok9q?workspace=user-ayushjain1144. I think the depth maps look much worse compared to with depth supervision.

@ethanweber I studied your suggestion of training nerf model without depth supervision in more detail -- I find the predicted depth without any supervision is at very different scale than my "ground-truth" which might point to some convention / normalization differences.
I am attaching below the precise numbers I see: you will notice that the predicted depth (after scaling back to original depth space) is very different than ground truth. The depths are z-depths i.e. distance from camera plane and I am using the default is_euclidean_depth: False

Any help would be greatly appreciated! Thank you!


Feature/add ring doorbell

Motivation for this change
Required for the Home Assistant Ring integration.
Things done

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

[x] NixOS
[ ] macOS
[ ] 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)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Actually, it looks like Home Assistant breaks with 0.7.0 (looks like an API change, I have previously been using 0.6.2 successfully).  I'll downgrade this since it seems better to commit something that works with Home Assistant.

Result of nixpkgs-review pr 114181 at 50230a48 run on x86_64-linux 1

1 package marked as broken and skipped:

python39Packages.ring_doorbell

2 packages built:

python37Packages.ring_doorbell
python38Packages.ring_doorbell

1 suggestion:

warning: unclear-gpl
lgpl2 is a deprecated license, check if project uses lgpl2Plus or lgpl2Only and change meta.license accordingly.
Near pkgs/development/python-modules/ring_doorbell/default.nix:38:5:
   |
38 |     license = licenses.lgpl2;
   |     ^

Result of nixpkgs-review pr 114181 run on x86_64-linux 1

3 packages built:

python37Packages.ring-doorbell
python38Packages.ring-doorbell
python39Packages.ring-doorbell


fails when

Consider a slim control with <style> tag in the end of the template.
Consider that an element before that <style> is a slim-control.
Consider the current control to have an input with an input event:
<span>
  <input s:id="queryInput" type="text" input="handleInput">
 </span>
 <child-slim-control s:repeat="somestuff"></child-slim-control>
<style>
 .foo{ color: blue }
</style>

When the input event is processed - I get:
Slim.min.js:1 Uncaught TypeError: Failed to execute 'appendChild' on 'Node': parameter 1 is not of type 'Node'.
    at HTMLElement._render (Slim.min.js:1)
    at HTMLElement.render (Slim.min.js:1)
    at HTMLElement.createdCallback (Slim.min.js:1)
    at init (Slim.min.js:1)

comes with log waring:
TypeError: Could not respond to event "input" on input -> "handleInput" on lab-search ... Failed to execute 'appendChild' on 'Node': parameter 1 is not of type 'Node'.
    at HTMLElement._render (Slim.min.js:1)
    at HTMLElement.render (Slim.min.js:1)
    at HTMLElement.createdCallback (Slim.min.js:1)
    at Slim.min.js:1
    at Array.forEach (<anonymous>)
    at Slim.min.js:1
    at Array.forEach (<anonymous>)
    at Slim.min.js:1
    at Function.commit (Slim.min.js:1)
    at Function.commit (Slim.min.js:1)

workaround - the style can be anywhere, just not in the end.
I really wonder why...

Played with it more - it fails whenever the style comes after the custom control with the s:repeat, no matter if there are more HTML nodes between them

I could not reproduce, can you jsbin/fiddle this?

could not reproduce. https://codepen.io/eavichay/pen/ZMQdLL


refractor the code constants are added more smothness and readable co…

refactor the code constants are added more smoothness and readable code now

refactor the code constants are added more smoothness and readable code now

Thanks for contributing in Hacktoberfest 2022.
Have a great journey ahead.


How to use in-source: false

Hello, Im newbe in rescript, this example is first time I run it.
Thanks, it works great(every electron rescript example failed for me).
But I don't want to have copies of every file in js format.
After I changed the "in-source" setting: false and js started being generated inside lib I started getting a blank page, there are no errors.

Please refer to the document of vite-plugin-rescript (Using Loader section), you could setup a configuration to support "in-source": false setting.


[angular] Update 13.1.1, 12.2.15

https://github.com/angular/angular/releases/tag/13.1.1
https://github.com/angular/angular/releases/tag/12.2.15

LGTM , thanks


Cannot rename file with spaces in filename on DO Spaces

Flysystem advices to use the AWS s3 plugin for connecting to the Digital Ocean Spaces API.
All goes well when uploading or deleting files. However when trying to rename a file that contains spaces in the file name (ie: "wp nl subscription whitepaper.pdf"), the DO Spaces API returns a 404 due to the urlencoded path:
$command = $this->s3Client->getCommand(             'copyObject',             [                 'Bucket' => $this->bucket,                 'Key' => $this->applyPathPrefix($newpath),                 'CopySource' => urlencode($this->bucket . '/' . $this->applyPathPrefix($path)),                 'ACL' => $this->getRawVisibility($path) === AdapterInterface::VISIBILITY_PUBLIC                     ? 'public-read' : 'private',             ] + $this->options         );
The urlencode results in this error:
Error executing "CopyObject" on "https://jbc.ams3.digitaloceanspaces.com/uploads_customer/55/wp%20nl%20subscription%20whitepaper%201.pdf"; AWS HTTP error: Client error: 'PUT https://jbc.ams3.digitaloceanspaces.com/uploads_customer/55/wp%20nl%20subscription%20whitepaper%201.pdf' resulted in a '404 Not Found' response: (....)
After removing the urlencode function in the CopySource line, I was able to rename the file successfully.
Could you perhaps add a config to disable the urlencode on the source path?

A PR for this would be welcome.

Just a quick update on this issue, it seems this isn't a problem any more. I'm able to rename files with spaces on DO Spaces. But, I'm not able to rename folders on the root of a space. It doesn't matter if it has spaces(characters) or not, files on root can be renamed, folders don't.

"GetObjectAcl" on "https://***.digitaloceanspaces.com/test?acl"; AWS HTTP error: Client error: GET https://***.digitaloceanspaces.com/test?acl resulted in a 404 Not Found response:

<?xml version="1.0" encoding="UTF-8"?>
<Error>
NoSuchKey
<BucketName>***</BucketName>
<RequestId>tx0000000000000a638d7d6-005ec6bd5a-*******-fra1a</RequestId>
<HostId>*******-fra1a-fra1</HostId></Error>`

Does this issue still arise with the changes proposed in #200 (PR #201)? That change fixed my problems with DO Spaces.

@emielbeinema just tested the update, and unfortunately no 😕
I still cannot rename folders.

Renaming folder is not supported in S3, no way around it.


Remove loader prop at data store level

Fixes #4911
Loader prop at the data store level has been deprecated for many versions and bohemia has been updated to use the new path (through the container scope object instead e.g. context.scope.ILoader, which is set automatically when created by a Loader).  Other issues around the relative loader have already been addressed separately as well.

shouldn't this have a breaking note?

shouldn't this have a breaking note?

@anthony-murphy it had a breaking note back when the deprecated tag was added.  should i add another one?  iirc previously i added them when something got deprecated rather than when it got removed, since the latter was sometimes causing problems at integration

I think we should do both. The first (depreciation) is more a notice, and the second is that actual break.


Add --timeout support to sign command

Summary
We can now specify a global -t/--timeout option to specify a timeout for any command. It is implemented for sign for now, which resolves a leftover TODO.
As a follow-up we can consider adding support to other commands as well.
Ticket Link

None
Release Note

- Added global flag `--timeout`/`-t`, which defaults to 3 minutes.
  This replaces the existing `--timeout` flags on
  `sign-blob`, `policy sign` and `attest`.
- Added `--timeout` supported to the `sign` command.

Looks like you have to run make docgen to update the docs!

Updated the PR, while we now can replace other --timeout flags for different subcommands.

Nice! Sorry I missed the "Approve and Run" thing here again.

@saschagrunert, there are some errors. Can you take a look?

@saschagrunert, there are some errors. Can you take a look?

Yes, sure. The unit tests seemed to be a flake but I fixed the e2e tests. Can you please re-trigger the CI?

ready @dlorenc


Revert "Make tikv-server fully generic over kv engines (#10945)"

What problem does this PR solve?
This reverts commit df2e9216f2f0f497ff158276a0171f4293516d91 as #11461 explains.
Check List
Tests

Unit test
Integration test

Release note
None

/merge


how to start private by giving --nodiscover option

how to start private network by giving --nodiscover option using embark

Hi @imhari213 , in blockchain.json, you can set "nodiscover": true.
It will set --nodiscover in geth.


Add options to create a deploy-key

Forge only allows github (or other providers) to be deployed using a personal connection, however the custom option also allows deploying with deploy-keys.
The strategy here is to first create a deploy-key on the Forge site, then install that key on the GitHub repo.
This adds two new env variables:

FORGE_GITHUB_DEPLOY_KEY which is a boolean, indicating if deploy-keys should be used
FORGE_GIT_REPOSITORY_URL the custom URL used when deploying using deploy-keys

One downside is that the GitHub actions token does not have Administration permissions, so it cannot create a deploy key. The easiest solution I found was to use a github app. How to create an app is explained here: https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/making-authenticated-api-requests-with-a-github-app-in-a-github-actions-workflow.
When creating the app you'd need to give it the "Administration" repository permissions (write) permission as mentioned here: https://docs.github.com/en/rest/deploy-keys/deploy-keys?apiVersion=2022-11-28#create-a-deploy-key
If you also set GIT_COMMENT_ENABLED you'd need to grant either "Issues" repository permissions (write) or "Pull requests" repository permissions (write), as mentioned here: https://docs.github.com/en/rest/issues/comments?apiVersion=2022-11-28#create-an-issue-comment
The provisioning script would then look like the following:
name: preview-provision
on:
  pull_request:
    types: [opened, edited, synchronize, reopened, ready_for_review]
jobs:
  harbor-provision:
    if: |
      github.event.pull_request.draft == false
    runs-on: ubuntu-latest
    container:
      image: kirschbaumdevelopment/laravel-test-runner:8.2
    steps:
      # We first need to generate a token
      - name: Generate a token
        id: generate-token
        uses: actions/create-github-app-token@v1
        with:
          app-id: ${{ vars.APP_ID }}
          private-key: ${{ secrets.APP_PRIVATE_KEY }}
      - name: Install Harbor via Composer
        run: composer global require mehrancodes/laravel-harbor -q
      - name: Start Provisioning
        env:
            FORGE_TOKEN: ${{ secrets.FORGE_API_TOKEN }}
            FORGE_SERVER: ${{ secrets.FORGE_SERVER_ID }}
            FORGE_GIT_REPOSITORY: ${{ github.repository }}
            FORGE_GIT_BRANCH: ${{ github.head_ref }}
            FORGE_DOMAIN: harbor.com

            # Indicates we want to deploy using deploy keys
            FORGE_GITHUB_DEPLOY_KEY: true

            # The git URL to be used in Forge
            FORGE_GIT_REPOSITORY_URL: "git@github.com:${{ github.repository }}.git"

            # We have to set the provider to 'custom', since Forge otherwise wouldn't use the deploy-key
            FORGE_GIT_PROVIDER: custom

            # We set the token we got from our app, instead of the default token
            # As the default actions token does not have permissions to create a deploy key
            GIT_TOKEN: ${{ steps.generate-token.outputs.token }}
        run: harbor provision

ToDo:

[ ] The harbor teardown command should also delete the deploy-key from GitHub
[ ] Idea: Also make this work for gitlab (https://docs.gitlab.com/ee/api/deploy_keys.html#add-deploy-key) and others

Going to look for a different strategy to implement this. The GIT_TOKEN (GitHub actions token) doesn't have administration (write) permissions, so using that token wouldn't be possible. Going to look at an app integration for this. Fine grained tokens would work too, but those have a limited lifetime, requiring updating those tokens every 30 days (or whatever lifetime one picks for the token)

Hi @RobertBoes, I tested this PR on a sample repository. The GitHub token is generated successfully, and everything works fine, but I’m running into a timeout after about a minute when it tries to create the deploy key (App\Services\Forge\Pipeline\InstallGitRepository::52).
I created the GitHub App with the given permissions, installed it on my account, and added the API private key with the App ID.
Just a heads up, there might be an issue with how I set up the GitHub App. However, creating the deploy key directly with a GitHub token worked fine.

Don't need to worry about this right now, but I think it would be helpful to have a rollback strategy for the provisioning process in case the GitHub createDeployKey (or anything) fails. Right now, it skips that step (createDeployKey) if we retry the provision, which could cause issues.

@RobertBoes, thanks a ton for putting this together! It really helps the project. Had a lot of fun using deploy keys to set up repositories instead of doing it manually, 😅 Setting up the GitHub App took me a bit to get right, though. I might need to add some more guides or link to an article on how to do that.
I went with finding the deploy key using the same formatted title you add when creating it. This way, it removes all deploy keys with that title. Do you think that’s safe?
Anyway, here’s the final result. Let's merge this pull request!

@mehrancodes that's awesome! Thanks for the hard work! Had some unsaved changes, but couldn't really continue working on it lately. I see you've taken pretty much the same approach as me, just too bad the API doesn't work with IDs or something that can easily be matched. Was thinking about comparing the key's fingerprint, but that was another rabbit hole. I think comparing the name should be fine.


YOUR_PROJECT_ID_HERE should be replaced in pom.xml

See title. This isn't necessary for local development, but will be for deployment.

Fixed by #16


Hang Issue in Compute Kernel

Describe the bug
In general, data flow in CB between Data Movement Kernel (DMVK) and Compute Kernel is as follows.

Fig.1 Data Flow in CB between Data Movement Kernel and Compute Kernel
While implementing the operation, we encountered a hang issue at the seventh step of the cb_reserve_back API when the pop and push operations were repeatedly executed within the compute kernel, as shown in the diagram below.

Fig.2 Detailed Data Flow and Loop in Compute Kernel
I have added test code in the hang_in_compute_kernel branch by slightly modifying moreh_sum code.
The sequence appears to be correct, but we need to verify if this kernel implementation violates any guidelines or if it is indeed a bug.
To Reproduce
Steps to reproduce the behavior:

git checkout origin/hang_in_compute_kernel
CONFIG=Debug ./build_metal.sh
source ./python_env/bin/activate
export TT_METAL_DPRINT_CORES=0,0
pytest tests/tt_eager/python_api_testing/unit_testing/misc/test_moreh_sum.py::test_compute_kernel_hang

Expected behavior
No kernel hang occurs.
Screenshots
If applicable, add screenshots to help explain your problem.
$ pytest tests/tt_eager/python_api_testing/unit_testing/misc/test_moreh_sum.py::test_compute_kernel_hang

 ......

loop 0 / 8
before cb_reserve_back
after cb_reserve_back
loop 1 / 8
before cb_reserve_back
after cb_reserve_back
loop 2 / 8
before cb_reserve_back

Related kernels are:

ttnn/cpp/ttnn/experimental/tt_dnn/op_library/moreh_sum/moreh_sum_nc_impl/kernels/moreh_sum_nc.cpp
ttnn/cpp/ttnn/experimental/tt_dnn/op_library/moreh_sum/moreh_sum_nc_impl/kernels/reader_moreh_sum_nc.cpp

Additional context
Add any other context about the problem here.

OS: Ubuntu 20.04 / <IP_ADDRESS> VM

Version of software (eg. commit)
commit 0ddee05d93f816d8cab3efba4aaff6040ce0b549 (HEAD -> pack_uint32_to_uint8, origin/main, origin/HEAD)
Author: Nenad Petrovic<EMAIL_ADDRESS>Date:   Mon Jul 22 15:25:21 2024 +0200
RDIV migration to TTNN (#10389)

#10147: Add rdiv test corrections

#10147: Corrected the naming of rdiv op test

#10147: naming modify

#10147: Linter applied

#10147: Linter applied

#10147: fix opmap

The link takes me to a PR that is already merged. If I checkout the mentioned commit ID I do not see any file named or any file containing the string "kernel_hang".  In short I cannot find the code to reproduce the problem. Is this issue supposed to be closed ? @dongjin-na

I cannot see any test code, but the pseudocode is using cb_push_back from both the reader and the compute kernels. But the guideline says this will produce nondeterministic  behaviour. See File  ./tt_metal/include/compute_kernel_api/cb_api.h
 * can only be updated from one thread at a time. Example: if compute kernel has cb_pop_front(input_id, 1)
 * and writer kernel also has cb_pop_front(input_id, 1), these calls will produce non-deterministic behavior because
 * cb pointers are not synchronized across threads. Per circular buffer index, only have one thread pop tiles
 * to update the read pointer
 *
 * Return value: None
 *
 * | Argument  | Description                          | Type     | Valid Range                                                                                | Required |
 * |-----------|--------------------------------------|----------|---------------------------------------------------------------------------------------------------|----------|
 * | cb_id     | The index of the cirular buffer (CB) | uint32_t | 0 to 31                                                                                | True     |
 * | ntiles    | The number of tiles to be popped     | uint32_t | It must be less or equal than the size of the CB (the total number of tiles that fit into the CB) | True     |
 */
ALWI void cb_pop_front(uint32_t cbid, uint32_t ntiles) {
    UNPACK(( llk_pop_tiles(cbid, ntiles)  ));
}

Dear @amahmudTT , thanks for the check.

You can run the test script using the hang_in_compute_kernel branch.
Regarding your feedback, as shown in Fig. 2, once the compute kernel (thread) receives a tile from the reader kernel, only the compute kernel handles the CB afterward. This ensures that there is no overlap where more than one thread accesses the same CB simultaneously. What do you think?

Seems like the header of the circular buffer is getting corrupted in the compute kernel. As when printed from reader cb 24 gives the following information
cb_id 24: { size: 128, limit: 7254, page_size: 128, num_pages: 1, rd_ptr: 7126, wr_ptr: 7126, wr_tile_ptr: 0 }
When viewed from the compute kernel it gives this
UNPACK cb_id 24: { size: 128, limit: 7254, page_size: 128, num_pages: 0, rd_ptr: 7126, wr_ptr: 0, wr_tile_ptr}
Note write pointer is zero and num-ages is also zero

Hello @dongjin-na  with some help from @rtawfik01  it seems we cannot write to the same buffer using the same handle from two threads even if we are not doing it at the same time. This way the handle or control flow information including the read write pointers will get corrupted. Sorry it is not made clear in the api for functions like cb_reserve_back, where it says only one thread can write at a time ( I will update the information) .
But there is a way to still do what you wanted to do. We can write to the same memory location in L1 memory from two threads but we need two separate handles. An example of that can be found in the function
tt_metal::Program create_program_single_core in file ./tests/tt_metal/tt_metal/perf_microbenchmark/1_compute_mm/test_compute_mm.cpp
I am copy pasting a portion of the code (with removed lines)
tt_metal::Program create_program_single_core (
    tt::DataFormat cb_data_format,
    std::shared_ptr<tt::tt_metal::Buffer> out_cb_addr
) {

    uint32_t out_cb_index = 16;  // output operands start at index 16
    uint32_t interm0_cb_index = 24;
    std::map<uint8_t, tt::DataFormat> partials_and_out_data_format_spec = {
        {out_cb_index, cb_data_format}, {interm0_cb_index, cb_data_format}};
    tt_metal::CircularBufferConfig cb_out_config =
        tt_metal::CircularBufferConfig(out_CB_size, partials_and_out_data_format_spec)
            .set_page_size(interm0_cb_index, single_tile_size)
            .set_page_size(out_cb_index, single_tile_size)
            .set_globally_allocated_address(*out_cb_addr);
    auto cb_out = tt_metal::CreateCircularBuffer(program, CoreRangeSet({all_cores}), cb_out_config);
}

In the above code, circular buffers at index 16 (out_cb_index) and 24(interm0_cb_index) share the same memory, and for your example Reader could probably write to out_cb_index while the compute thread could use the loop on item0_cb_index.
Hope this helps and please let me know if you have any question.

Hello, @amahmudTT.
Thanks for the detailed analysis.
I have a question to clarify.
To achieve something like what’s shown in Fig 2, as you suggested, would it be correct to use two CBs that share the same L1 memory like this?
/////////////////////////
// Reader kernel
/////////////////////////
cb_reserve_back(out_cb, 1);
cb_push_back (out_cb, 1);

/////////////////////////
// Compute kernel
/////////////////////////

//Wait for one tile to be pushed to out_cb.
cb_wait_front(out_cb, 1);

// Now iterm0_cb takes that tile.
cb_reserve_back(iterm0_cb, 1);
cb_push_back(iterm0_cb, 1);

for ( ...... ) {
  cb_wait_front(iterm0_cb, 1);
  // Do something ......
  cb_pop_front(iterm0_cb, 1);

  cb_reserve_back(iterm0_cb, 1);
  pack_tile(0, iterm0_cb, 1);
  cb_push_back(iterm0_cb, 1);
}

Thanks for the clarification. Please update the documentation with this information. I will go ahead and close this issue. :)


Miflora avoids loading of frontend with non-international version of Mi Flora plant sensors

**Home Assistant release with the issue: 0.84.6

**Last working Home Assistant release (if known): Unkown
**Operating environment (Hass.io/Docker/Windows/etc.): RasPi 3 B+ Python Virtual Environment

**Component/platform: Miflora

**Description of problem: Frontend doesn't load (or sometimes it takes forever to load) when miflora sensors with mac ID starting with C4:7C:8D:63:XX:XX or C4:7C:8D:66:XX:XX (probably non-international versions) are included in configuration. Works well when those with mac ID starting with C4:7C:8D:62:XX:XX are included. No errors in the error log.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
  mac: 'C4:7C:8D:66:4B:C8'
  name: Sardunya Pembe
  force_update: true
  scan_interval: 300
  monitored_conditions:
    - moisture
    - light
    - temperature
    - conductivity
    - battery

and similar

Traceback (if applicable):

**Additional information: I have several mi flora plant sensors with different mac id groups. I have isolated the problem to those which have mac id's as described.

I have three sensors on C4:7C:8D:66:XX:XX, no issues loading HA 84.6 frontend. Environment on Synology Docker. You should set your logger up to debug the component if you have issues.

I have three sensors on C4:7C:8D:66:XX:XX, no issues loading HA 84.6 frontend. Environment on Synology Docker. You should set your logger up to debug the component if you have issues.

With the logger in dubeg mode I'm not getting any errors.

How many sensors do you have in total? Could be too much to handle for the rpi3 perhaps seeing as the component is slow in general with its polling or faulty sensors. Are you able to see them all get picked up if you do a scan in the MiHome app?

I have 12 in total. I have a Xiaomi Mi Robot Vacuum, therefore MiHome app is set to International version and due to this I can't use Mi Home app with the sensors. I have Mi Flower Care app, which reads the ones with C4:7C:8D:62:XX:XX and C4:7C:8D:66:XX:XX) doesn't read the ones with C4:7C:8D:63:XX:XX I believe.
I tried:
sudo gatttool --device=C4:7C:8D:66:4B:C8 --char-read -a 0x38 --adapter=hci0
and got:
connect error: Function not implemented (38)

I could see all 12 within HA some time ago. I tried a lot of things to isolate the problem and I'm at this point now.

I too have this problem. I had 9 sensors when I upgraded to 0.80+ and have had random failures since. sometimes I could reload several times in a row and everything would be fine, other times it would take 15 minutes, a few hours, a day before the webui came to live, during that time home assistant was listening on port 8123 but it never returned a thing.
It took splitting up my monolithic configuration to come to the same determination that it was the mifloras. I can get 4-5 sensors working fairly reliably, after that it starts failing to load the webui.
I was going down the wrong track, because my logs were filling with auth: Failed, which from the above I am guessing it was the mifloras. During this entire time, there's never been an error message that would have lead me to this. I wish I would have gotten the error that is listed above.

I have the same problem. My Flora has mac C4:7C:8D:64:xx:xx and from version 0.92 started randomly failure. Sometimes after number of HA restarts it begins to show values but then can stop doing. Most of the time it doesn't update values and there is no any error in the log.
I very upset since it worked fine for quite a long time with HA correctly in previous versions. I start to think about integration with Mi Flora via python library (it is exists).
See also my issue Errors with bluetooth_le_tracker and non-working Mi Flora #23967.


[docs][base] Improve Base UI all components images

[x] I have followed (at least) the PR section of the contributing guide.

A follow-up to https://github.com/mui/material-ui/pull/37536 to make images crispier. Also simplified the aspect ratio to a much more common one (16/9) and added explicit width and height sizes.

@michaldudak So we'd add an explicit width in pixel on the parent Card? Uhm... is that the best approach? 🤔

TL;DR: yeah, let's ship it ;)

@michaldudak So we'd add an explicit width in pixel on the parent Card? Uhm... is that the best approach?

Not necessarily. I've found out the root cause of fractional widths is the max-width of div.main-content. It's set to 105ch and on my setup, this resolves to 814.333px. The width of a column in three-column layout with 16px gap is 260.771px, and the fractions continue.
This could be solved by setting .main-content's max-width to something like 57.5rem, which by default is 800px. One column is equal to a nice, round 256px in this case.
Now comes the (not so) fun part: images within cards are slightly smaller because cards have a 1px border. As I learned today, a 1px border isn't always a 1px border. Because I use 150% display scaling, my browsers (Edge and Firefox) render the border with 0.6667px width. This is (I assume) to ensure it occupies exactly one physical pixel and is crisp.

This means we don't know the exact width of the rendered image because it depends on display scaling settings. So no matter what we do, it could be a little blurry for some users.
Considering all the above, I suppose we can live with it. The version after the recent changes is better than before, so I'm ok with keeping it.

Shoot, well, at least you & I definitely learned something while trying to optimize this 😅
Appreciate the breakdown and summary! 🙌


[AMORO-3150] Bump up curator to 5.7.0

Why are the changes needed?

Close #3150.
Brief change log

Bump up curator to 5.7.0
We also need to upgrade the version of amoro-shade-zookeeper-3

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before making a pull request

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@rfyu Thanks for reporting this issue.
I am afraid we need to bump up version in project amoro-shade

Here is the related PR ofthe  amoro-shade project: https://github.com/apache/amoro-shade/pull/9


Pranav3

I have created the about page . But when I am adding its route in App.js ,it is giving conflicts . How to resolve it ?


Rework usages/naming of configuration macros

There are quite a few configuration macros in the project. As discussed in the #2520 issue there are a few awkward constructs. This PR makes the first step to consolidate them
Main changes:

All options (in this PR) are can have a value of 0 or 1.
The CONFIG_DISABLE_ macros were renamed to JERRY_...
Renamed ENABLE_REGEXP_STRICT_MODE to JERRY_REGEXP_STRICT_MODE.
Replaced the CONFIG_ECMA_NUMBER_TYPE macro with JERRY_NUMBER_TYPE_FLOAT64.
Added sanity checks for each macro to avoid incorrectly set values.
Added/replaced a few config.h includes to correctly propagate the macro values.

Note: this is just the first part of the configuration macro rework.

Please rebase to the current master

I agree with @rerobika, we should aim to make the code as readable as we can.
Since each guard is checked to have well defined values, I would even go as far as to say that we should skip the comparison checks as well (in case of boolean guards).
For example, instead of
#if (JERRY_A  == 1) && (JERRY_B == 0)

we could simply write
#if JERRY_A && !JERRY_B

What do you think?

@dbatyai @rerobika I'm fine with simplifying (the sanity check would catch all problems).
Another thing I was considering is the format: #if ENABLED(JERRY_FEATURE) which could hide all defined and comparison checks.
Which one would you prefer?

I think #if ENABLED(JERRY_FEATURE)  is fine, it's more descriptive while remaining well readable

The #if ENABLED(JERRY_FEATURE) is fine for me as well.

@rerobika @dbatyai I've just updated with the ENABLED version :)


readline library is broken

Both readline-6.3 and readline-7.0 are broken on Windows. Therefore irb isn't fun to use. It's probably best to switch to rb-readline.gem, as the RubyInstaller does.

@larskanis
I assume that readline-7.0 has been updated since the version of libreadline7.dll on my system is 03Feb.
It's working on my x64 builds with 2.5.0 (trunk); has about the same test failures as rb-readline.  irb seems to work also, although I haven't gone crazy using it (irb).  You may know how to test it better than I...


Fix #352

Resolves #352, added a parameter to output prints from imputes value.
User is warned that imputation always occurs at prediction, even though the user might set impute=False for pipeline.

Done, please have a look.


public documentation to github pages

And change links from homepage markdown to point to github pages links

I've got an initial version up at https://digitalslidearchive.github.io/DSA-WSI-DeID/ , which then points back to the readme and usage Rst files in master. This should be sufficient as a starting point.
I could see wanting to move the Readme and Usage to MD so that they can be more easily added into the website, or have better integration between those docs and the website. Another potential update would be to point the website to the Readme and Usage of the latest specific release versions, but then we'd need to constantly update this website, and there isn't that much drift for now between master and the latest released version.


Spurious component updates when v-model is defined in parent, but not used in child.

Vue version
3.4.27
Link to minimal reproduction
https://play.vuejs.org/#eNp9VE1T2zAQ/StbX2xm8jEtPXlCZlrgQGcKtLS9YA7C3jgCR1IlOZDJ+L93V/4KlOGSWLtvn96u9LSPvhgz29YYpdHC5VYaDw59bZaZkhujrYc9WFxN6EfkXm4RGlhZvYGYiuIBdLqWVdElZvOwYlYCZCrXynlYabs5E17AyUCV7JujPv23RuclfVL+FmLx8dNxPIH4nv/hbqTxVpYl2sCySqh8MW9lk2BaeNyYSnikFcDCGaGWVwYVcLGucAJ+Taue5H4HfmekKmGNFlMgLq5YSGVqD9vpRhdYnWRRh88imIdtiLqQWwJQU5TutV8UINXYCcHTR9y9AGRRUEYEH6ZTyMPUpKNephZVQSIK0Apwi3YHRlDME0ioEmE67StDVfsNByL7Ad+Ou91lUY9Lx+grQS2CGyPuOfXVt8gKL/UwcpZWeycLbBvvFbV63hIS53x6JGKYSdico90oAQKDsbjc7/u6plnMOcJne3Ce0STyjs5xJcvZg9OKbuw+MES53hhZob0y3dxTCBnOiarST99CzNsaJ308X2P++Eb8wT1zLIuuLTq0W8yiIeeFLdG36fObS3ym7yFJ3dcVod9J/kS6gzVrbGFfa1WQ7ANcUHsRLEW38pc7f/aoXN8UC2VkE/BZRAY7faf1Ue7x7HOoy1RDUxzc+YbnAQbXa/XbFDT6YgJPwufrV8ZnbGtJY7Vh2xa4kgqveZV0IsZzH3QBW468dkPXSpVd58DFoq58Cqquqi7a9slvBP/P53CGeSW4jG0MdZCXhmv3R1Q1sm/IMGKrZeECZPAV1aQdSSvzO1fx+3EQO99I75Lb+D/i+K7TMMwkSY7gZNn31L0us0qXSRzGS29XGMtsnAC9Zi0xJ+me40zpp+QoSOAe33vIWlfyVj86PprnfuRu6GhH9760TfMPeKP4OQ==
Steps to reproduce

Open the console on the repro
Type into the input box

What is expected?
The child components would not be updated.
What is actually happening?
The child components update lifecycle hooks indicate they are being updated. On large forms, this is leading to performance issues.
System Info
No response
Any additional comments?
Discussed on discord here
This is caused because the parent is passing the v-model to the child, which isn't being used, and the event handler isn't being cached as @skirtles-code showed in that linked thread. I've added a static <child /> outside the v-for to verify that, and don't see any updates in that situation.
Perhaps this is expected behaviour, but there were no warnings about unused props / model, and nothing indicating the updates were being triggered, other than performance issues.
Is there some part of the documentation that explains any of this?

I think this is expected, just like with CSS, where additional tools are needed to scan and compare files in order to identify unknown styles in use.

Use Vapor mode:
https://vapor-repl.netlify.app/#__VAPOR__eNp9VE1T2zAQ/Suqe7Azk9jT0pMbMtMCBzpToKXlgjkIe+MIbEmVZZNMJv+9u3L8EWjDDEm0H0/vrXZ3633ROmxq8GJvXqVGaMsqsLVeJFKUWhnLtszAcoofPLWiAbZjS6NK5mOS/7mPOluJItt7wsidCJYiEpkqWVm2VKY855az0x4s2O4mGNH6/9RQWYE/MeDe5x8+nvhT5j/S98MIxhqR52AcyjKg9HnUMkfOeLBQ6oJbwBNj80pzubjWIBllqwKmzK7w1KE8bpjdaCFztgIDMUMsypgLqWvLmlmpMihOE28fn3gsctcgdCYaDEBV6O64X2ZMyEEJhsfPsDkISDzHDAHezWYsdXUTFYqZGZAZksiYkgwaMBumOdosBnGZA5vNusw2a2DXlfZ+uOaB7h6Oryg4FQgUoYhOD9G5Un2BiUdtK5FBq7K7/v+X+6l7K0Q/uJes47ppA4vtdmiH3W4ekY0ecvR43tQTWI91uLJlMWpPfC5AVLy9LqAvJv31DZtif1m443jE9h53bNSQ0X+TQ2Fd8+4nYhR0iBfg/yQsVS1t4L/nWvuTvgNdUwhSjXYk1xYYpdgK+28p8vCpUhLVbAkda6NKLQow13rfLzFzHvLxolAv35zNmhqmnT1dQfr8D/tTtSZb4t0YqMA0WJzeZ7nJwbbui9srWOPv3tmV8ojzJ+Ds1MSxDftaywxpj+Ic20tXTZymX9XF2oKsOlFElCJ3Lj7xsL5nR6QPdE/CTy4vkTusYr9Xjq0rJX/rDN8rm7IXbtPV643VLRJtlKZdk8FSSLihU+AYDN3bU6Kmi9ktjobM95IxjdeFjZmsi8LZSJzbZ4mMInYOacEpnhYOqx2l2M3MHS9qoAnH0eaNElnlQvoNgDmxg2iZfaecYDKyXJTCVsG9/wbUf8CwRPYVCIIJO120Ivb7LyxUHviukLheXQ3CQTAu3BaUnDidEEr1EkxIlFN2bNVSp//YI2Hhtm/A3aS3C+dw0nd/AS6sNHY=

I think this is expected behavior, as explained by @skirtles-code
Thanks @Shyam-Chen for the workaround.

Yes, thanks @Shyam-Chen, I had not connected this issue with v-memo, and never used it before. So, the challenge I have is that some of those components in the v-for do use the model, and some don't (e.g. they're static 'display the question but don't let people interact' type things). This is more like my actual code:

  <component
    :is="questionComponent[question[questionId].type]"
    v-model="formData[questionId]"
    :questionId
  />

If I use v-memo="[ questionId ]" on the v-for, then the unwanted updates to all other components is solved, but now the child components don't see the updated model. The parent sees it (I'm showing the raw formData and can see the updates coming in) but it's not reflected in the child contents. So, I changed it for this—is this a valid use of v-memo in this scenario?

  <component
    :is="questionComponent[question[questionId].type]"
    v-model="formData[questionId]"
    :questionId
  />

this is valid.
v-memo="[ formData[questionId] ]"

Closing as this is the expected behavior.


How to make "private dbs" for individual users?

It's mentioned in the README but I don't see how to do it or how it works. I'll keep trying but maybe it's fairly easy to explain?

That line just refers to the fact that SQLocal databases live on the user's device, rather than being centralized on a server, so each user's data is made private and secure by their own device without sacrificing the data processing power that traditionally server-based solutions provide.
Does that make sense? Was there a different feature you were looking for or expecting when you read that line?

Ahh, that makes sense. Thanks. I was hoping there might be a way to encrypt the sqlite db somehow, so that you could have multiple "tenants" on the one device. I also am not totally sure if a B2B app that's all GDPR and SOC 1/2 compliant needs that data to be encrypted on the device... will keep looking! Wouldn't mind at all if you closed this or wanted to move this to a discussion?

I think I'm starting to understand that the OPFS is a) not visible to users and b) only accessible by web workers that c) can't be inspected or debugged or tampered with on the client. So if I use your library to create different sqlite dbs in different files then they should be pretty secure.

Files in the OPFS do not appear as regular files outside the browser, so users would not be able to find them by browsing their file system. However, as with any files used in a web page, a person with the knowledge to use the web inspector can find any code your web page sends to the browser as well as any files stored in the OPFS. Files in the OPFS are private in the sense that they can only be accessed and changed by the website (origin) that created them. The site can manipulate its own OPFS files from the main thread or a worker as long as the site is in a secure context.
You should not need to encrypt SQLite files in the browser. They are local and partitioned by user just like other browser files and settings. SQLite does offer a product that allows it to work with encrypted databases, but even they give many reasons why such a solution is pretty pointless for browser-based apps.


Build documentation on CI instead of requiring contributors to run mdbook locally

I would like to contribute to the documentation, but I am not very happy when doing that requires me to install additional tooling. Then, there are potential conflicts in HTML. Additionally, I think because mdbook is available in various versions and platforms, requiring contributors to install it may result hard to debug bugs or regressions.
Rendering the documentation on CI, would allow contributors to only modify .md files to update the documentation. Rendering could be done in a workflow that only runs from master, checks out the changes, runs mdbook and pushes rendered HTML to a separate branch. (There is a small security concern here, to not allow people to push to that branch from CI runs e.g. on pull requests). I saw similar solutions using something-different-than-jekyll to use GitHub Pages for a blog. (I am assuming here that the manual is served from Github Pages, but if it's not, then deployment would probably be similar to the current one, just based on a different branch.)

I could probably work on that sometime this week (if approved)

I could probably work on that sometime this week (if approved)

Here are permissions for the GITHUB_TOKEN that is automatically available in each action. The forked repos already have only a read permission. For PRs from within the repository (created by maintainers) I think configuring the action to only run from master is good enough.

Here are permissions for the GITHUB_TOKEN that is automatically available in each action. The forked repos already have only a read permission. For PRs from within the repository (created by maintainers) I think configuring the action to only run from master is good enough.


Update circe-core, circe-generic, ... to 0.14.6

About this PR
📦 Updates

io.circe:circe-core
io.circe:circe-generic
io.circe:circe-literal
io.circe:circe-parser

from 0.14.5 to 0.14.6
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.circe" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.circe" }
}]

labels: library-update, early-semver-minor, semver-spec-patch, version-scheme:early-semver, commit-count:1

Codecov Report
Patch and project coverage have no change.

Comparison is base (51b27ff) 50.00% compared to head (6c1fe38) 50.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the GitHub App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #456   +/-   ##
========================================
  Coverage    50.00%   50.00%
========================================
  Files            5        5
  Lines           84       84
========================================
  Hits            42       42
  Misses          42       42

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


Add attributes to worker fetch calls?

I.e. my worker is calling out to another URL.
I can't seem to get the span for these fetches even if put the getActiveSpan inside the then callback in fetch().then(() => {})

Ah ok, withNextSpan — https://github.com/evanderkoogh/otel-cf-workers/commit/9524df457025fc71aed611139b646fc616153606

Ahh.. you found the as of yet undocumented way of doing that..
But yeah, there is no easy way to add attributes by operations that are auto-instrumented in ways like that. Which is why I added withNextSpan as an experimental API. It seems to be working well enough for a bunch of people for now.
Not sure if the OTel community is going to come up with another version of it..


Doc: Minitrace goals regarding Logging and Tracing crate compatibility with debug! etc macros

It would be nice to know the scope and goals of the maintainers, with respect to compatibility with the Logging/Tracing crate ecosystems.
My preference is to place compatibility as a secondary goal, with the requirement that any compatibility does not adversely impact performance.
Specifically, here I'll address the provision of macro functions such a debug!(...), warn!(...), etc.
My 2c:
The minitrace overhead is sufficiently low that, if users find it useful to have:
fn mine() {
    ...
    server.start();
    debug!("server instance started")
    ...
}

They could be encouraged to add the #[trace] attribute to the start function.  In cases where start is defined in a 3rd-party crate, I'd advocate guiding user to adopt a "new-function" idiom/pattern that is a counterpart to the "new-type" pattern.
Where by we could say something like: Tracing your usage of third-party crates using a "new-function" idiom/pattern, gives compile time guarantees that the function start/entry and end/exit times are visible.  The previous example would become:
fn mine(){
    ...
    start(server);
    ...
}

#[trace("server-start")]
fn start(server: Server){
    server.start;
}

Has been documented in readme https://github.com/tikv/minitrace-rust#how-does-minitrace-differ-from-other-tracing-libraries


JSON parse and stringify API

Simple JSON API as described here: https://v8.github.io/api/head/classv8_1_1JSON.html

I think the API like ctx.JSON.Stringfy(...) and ctx.JSON.Parse(...) is better.
In the future, we can add ctx.Math.Min(...) etc...

Thanks for the feedback @kuoruan
The API you have suggested requires an extra allocation, with a redundant structure. I don't believe that this pattern is idiomatic Go (I can't think of any examples in the Stdlib). FYI: There is no Math API in V8; you would do this in either Go or JS directly.
The only alternative design would to make the API functions rather than methods; which is technically closer to the C++ API ie:
func JSONParse(ctx *Context, str string) (*Value, error)

func JSONStringify(ctx *Context, val *Value) string

We could also place them in there own json pacakge: ie:
import "rogchap.com/v8go/json"

val := json.Parse(ctx, str)
jsonStr := json.Stringify(ctx, val)

But seems unnecessary to create a new package for these 2 functions


Kubernetes-style resource import

We've prototyped a variety of ways to use the Registry API to add information to the registry, including custom importers for the Google API Discovery Format, the public Protocol Buffer descriptions of Google APIs, and the apis.guru OpenAPI Directory. But these are all very specialized and seem unlikely to be useful by teams in practice.
We could leave it to users to write their own importers, but we've noticed that other projects have been following a pattern that we first saw in Kubernetes - describing objects (resources) with YAML that is in a standardized wrapper that includes API version and a type identifier, along with other metadata, to identify the type of object being described. This allows users to create or modify objects using a single command: kubectl apply.
Closely following the Kubernetes pattern, a YAML file for a sample API might look like this:
apiVersion: registry/v1
kind: Api
metadata:
  name: registry
spec:
  displayName: "Apigee Registry API"
  description: "The Registry API allows teams to track and manage machine-readable descriptions of APIs."
  availability: PREVIEW
  recommendedVersion: v1
  recommendedDeployment:
  labels:
  annotations:
  apiVersions:
  - kind: ApiVersion
    metadata:
      name: v1
    spec:
      displayName: "v1"
      description: "New in 2022"
      state: STAGING
      labels:
      annotations:
      apiSpecs:
      - kind: ApiSpec
        metadata:
          name: "protos"
        spec:
          filename:
          description:
          sourceURI:
          labels:
          annotations:
  apiDeployments:
  - kind: ApiDeployment
    metadata:
      name: prod
    spec:
      displayName: Production
      description:
      apiSpecRevision:
      endpointURI: https://apigeeregistry.googleapis.com
      externalChannelURI:
      intendedAudience:
      accessGuidance:
      labels:
      annotations:

Analogously to kubectl, the registry tool could have an apply subcommand and if we followed the kubectl pattern for resource access,  registry get <resourcename> -o yaml would return a YAML representation of objects in a form consistent with the example above.

Here's an example from Backstage that shows the use of this pattern to implement the backing store for a web site in a Git repository.
/cc @theganyo for other possible examples

Work in progress in https://github.com/timburks/registry/tree/patch-yaml

Does the yaml format (specially the information in spec field), has any connection with the protos that we already have? Else, we will have to maintain definitions at two different places protos and yaml, and these can easily diverge from one another.

@shrutiparabgoogle That's true. It's not the first redundancy - we also have other places where we have to maintain duplicative definitions (the storage models, for example). I think at our current scale, it would be ok, and later if needed we could figure out a way to generate these automatically. You might think of this as an effort to work backwards from a familiar representation (Kubernetes-style objects) to the Registry API.

Here's a directory of generated YAML files representing APIs: https://github.com/timburks/registry-experimental/tree/exports/exports/googleapis/apis

Other related Kubernetes links:

kubectl create creates resources (an apparent subset of kubectl apply).
'kubectl get' gets resources, optionally in YAML format.

Addressed in #463


Add social share image and og tags

Description
Adds Open graph tags and a static share image.
Steps to test/reproduce
Share the deploy preview at https://deploy-preview-98--oddcontrast.netlify.app/, and verify the content is as intended.
https://developers.facebook.com/tools/debug may be useful.
Show me
Facebook

Elk (Mastodon client)

 I want a social media image when I paste a link to oddcontrast - maybe showing the current colors/contrast?

@SondraE  Can you check again? I'm guessing you triggered the initial crawl, and so it's working now. This is what I'm seeing on Twitter-

And Linkedin-

I switched to an en dash in e9e083c

When I switched to my personal Twitter account it worked.
It still didn't work in LinkedIn, but maybe there's a cashing issue?