SEO: canonical URL in header

canonical URL in the header it applies to all pages/posts

using url filter - https://lume.land/plugins/url/
testing on my lume sites no issues
<link rel="canonical" href="{{ url |> url(true) }}">

Tested it working well
<link rel="canonical" href="{{ url |> url(true) }}">

Update lume
Reload cache

"reload": "echo \"import 'lume/cli.ts'\" | deno run --reload --unstable -A -",

RUN: deno task reload

Thanks!
Why do you need to reload cache? I think this task is not needed.

Thanks!
Why do you need to reload cache? I think this task is not needed.

sometime it cached the module data
it's helps us to get fresh one while upgrading the lume or adding new plugin
personally i am using this

Thanks!
Why do you need to reload cache? I think this task is not needed.

sometime it cached the module data
it's helps us to get fresh one while upgrading the lume or adding new plugin
personally i am using this

https://github.com/lumeland/lume/issues/237

Hmm, but when Lume is updated, the url of Lume and all plugins is changed, so we don't need to force the reload.
I guess you're importing some modules from the same URL but the data may change, right?
In this case, I wouldn't include this task here, because it's a task that you have to specify in your deno.json file.

Hmm, but when Lume is updated, the url of Lume and all plugins is changed, so we don't need to force the reload. I guess you're importing some modules from the same URL but the data may change, right?
In this case, I wouldn't include this task here, because it's a task that you have to specify in your deno.json file.

for now, I removed that option it's just an optional command for re-create the lock file / plugins

Ah, got it.
Yep, maybe deno task lume upgrade should remove the lock file so it's regenerated from scratch. This is one of the reasons why I have "lock": false in my deno.json file :)
Thanks!


tool.poetry.group.dev optional=true

Make dev dependencies optional, which is what I originally thought was the default behavior.

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

Project coverage is 98.00%. Comparing base (c08b47f) to head (bd5b086).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #38   +/-   ##
=======================================
  Coverage   98.00%   98.00%
=======================================
  Files           2        2
  Lines          50       50
  Branches        8        8
=======================================
  Hits           49       49
  Partials        1        1

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


S3E23 AMC Meeting (NLP && Annual) Announcement

AMC Meeting Announcement

S3E23
Season 3 Episodes 23

Date
7-9 pm, Sunday

Location
821, 8th floor, BUPT Research Building

Chairman
@CyFeng16

Vice-chairman
@huan

Previous Meeting

Minutes
Link

Blog
S3E21 (Season 3 Episodes 21)

Issue
#473

Agenda
1. Oral

Oral should be prepared for 15 - 30 minutes, and no more than 45 minutes, including Q/A.

Presenter
Paper

2. Poster

Posters should be prepared for 5 - 10 minutes, and no more than 15 minutes, including Q/A.
No more than 4 posters per seminar. If there are more than 4 posters proposals(PRs), the chairman should pick at most 4, and leave the others in the PR queue.

Presenter
Paper

3. After Party
Everyone will be welcome. You can join or not join as you want (not required by the AMC), and change your mind at any time.

After Party will be started right after all the meeting agenda had been fulfilled.
We will find a bar and drink beers and talk whatever we want. (we can expect that it will be related to meeting topics of the day)
The bill will be paid AA

Party Animals

List all members here except those who confirmed not coming. Put 🍺 instead of 🍻 in front of the members' name if they said "maybe". Do not list them who said "not this time".

Confirmed Attendees
Total number: 2

The member that does not give a talk should be quoted after a member who gives a talk.
Example: Alice_ will give a talk but Bob_ does not, and Bob_ wants to go with Alice:
@Alice (@Bob_)_

Role
People List

🧓 Chair
@CyFeng16

🧑 Vice-chair
@huan

🗣 Oral
@

📰 Posters
@

👶 Newcomers
@

我讲一下怎么用TensorFlow实现BERT的分词器，其中遇到的问题

赞！
段清华DEAN<EMAIL_ADDRESS>于 2020年1月12日周日 下午4:37写道：

我讲一下怎么用TensorFlow实现BERT的分词器，其中遇到的问题
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/BUPT/ai-ml.club/issues/476?email_source=notifications&email_token=AHDIKHL7U7WLDJR7YIMZRA3Q5LJGBA5CNFSM4KFN2GCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIWUYFA#issuecomment-573393940,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHDIKHPQHLAWJHR3QUZQXWTQ5LJGBANCNFSM4KFN2GCA
.


Hide range selector

Overview

Separated the range-selector component from the chart
Updated showcase and cardio apps to use CSS grid layout for range selector, chart, and summary
Set initial zoom to past 30 days in patient app, hoping if we choose a good initial zoom range then we won't need a range-selector

How it was tested

Ran all 3 apps
Added lots of layers to showcase/cardio, checked layout at different window sizes
Checked layout and initial zoom in patient app
Tested that drag/scroll to zoom still works in patient app

Checklist

[x] The title contains a short meaningful summary
[ ] I have added a link to this PR in the Jira issue
[ ] I have described how this was tested
[ ] I have included screen shots for changes that affect the user interface
[ ] I have updated unit tests
[ ] I have run unit tests locally
[ ] I have updated documentation (including README)


Fix block actions (i.e ci{) in presence of quotes (VIM-1008)

Finally make it to pass all tests

Wow, this is a great refactoring! Thank you for your contribution.


Fix the Postmark template for the sign-up/verification emails

Currently, the layout of the sign-up/verification emails is overflowing horizontally, as shown in the screenshots below.
This issue happened in viewing the email in:

Apple Mail Version 16.0 (36<IP_ADDRESS>.1)
Proton mail online app (mail.proton.me)

A fix would be to update the template of the Postmark. But, I'm not sure the best place to store it (Would it be best to store a template in this repo? If so, can we use that template in the Postmark API?)
Screenshots
Sign-up

Change email

Forgot password

Originally posted by @nsunami in https://github.com/libscie/ResearchEquals.com/pull/643#pullrequestreview-1087082545

The problem is that in the "action_url" stretches out because it does not have a breaking character.
Currently:
HTML:

If you’re having trouble with the button above, copy and paste the URL below into your web browser.

{{action_url}}

CSS:
    p.sub {
      font-size: 13px;
    }

We may need to do two things:

Use overflow-wrap: break-word; to the tag that's wrapping the action_url
Fix the width of the element

@chartgerink Assigning you here since I don't have access to Postmark 🙏

Seems to work!

Closing as this is now fixed. Also fixed this in password reset.


fix a compile error

This change will fix issue #219.

@huahang , thank you very much for the contribution. Would you please put the brace associated with a control statement on the next line?
Thanks!


how to change role of a user?

POST /2/profile allows an authenticated administrator to change the role of another user, but the administrator has to be authenticated with any other means other than using the API Key method.  API Key authentication is for read methods only.
How can I programmatically change the role of another user without manually authenticating in (using methods like oauth)?

Api keys are inherently not read only but oauth is the preferred pat for authentication. We don't currently have a way to generate self authorized oauth tokens for use but it may be something we look into in the future.


Update github workflows to avoid ::set-output

We need to update our github workflows to not use ::set-output. We have by May 31 2023 to do so.
See https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Will tag this one to a release milestone due to the timeline requirement.

Still get 21 warnings in https://github.com/ChainSafe/lodestar/actions/runs/4040952032


LMstudio errors on empty assistent message

Before submitting your bug report

[ ] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS: Windows 10
- Continue: 0.8.1
- Python: 3.11.3
- IDE: 1.85.1
- LMStudio: 0.2.10

Description
continue in vs code seems to send an empty assistant message and lmstudio gives a validation error on it
To reproduce

download any model in LMStudio
start local server in LMStudio
do any request via vs code to LMStudio
error message in the logs of lm studio

Log output
[2024-01-14 14:29:35.808] [INFO] Received POST request to /v1/chat/completions with body: {
  "messages": [
    {
      "role": "user",
      "content": "lol"
    },
    {
      "role": "assistant",
      "content": ""
    },
    {
      "role": "user",
      "content": "lol"
    },
    {
      "role": "assistant",
      "content": ""
    },
    {
      "role": "user",
      "content": "lol"
    },
    {
      "role": "assistant",
      "content": ""
    },
    {
      "role": "user",
      "content": "hallo"
    },
    {
      "role": "assistant",
      "content": ""
    },
    {
      "role": "user",
      "content": "lol"
    }
  ],
  "model": "wizardcoder-7b",
  "max_tokens": 1024,
  "stream": true
}
[2024-01-14 14:29:35.808] [ERROR] [Server Error] {"title":"'messages' array must only contain objects with a 'content' field that is not empty"}

@thomas9911 Is the problem a) that the assistant messages are not empty in the UI but become empty in the messages array, or b) that you don't get responses, leading to empty space in the UI and the messages array?

I'm having the same problem - @sestinj LMK how to answer that question to @thomas9911  (as I don't see the relevant info in the logs) and I will have a look

@poldrack if (b) is happening then you should see something like this (an empty space with no response between two input boxes):

If that's the case then it's a quick fix, and perhaps I should have even just done this before.
Tangentially, I thought your profile picture was the Unknown Pleasures album cover, but seems it's either a different version or just a very similar display of some random signal?

I just released a new version that would solve (b) by simply replacing any empty messages with " "

awesome, just reloaded the VSCode extension and it works properly now.  spaces FTW!  Thanks for fixing this so quickly.
Funny that you noticed the profile picture - it was generated by a member of my group using a large dataset collected from my brain about a decade ago.  I can't remember what it's the distribution of, but each row is based on data from a different day across the study.

Nice!
Oh this is really cool. The member did a good job of transforming to something that resembles pulsar emissions. Rabbit-holing about MyConnectome now...
Closing the issue, cheers!

I think this issue requires further investigation. I received this error in LM Studio while using with AutoGen Studio
[2024-02-02 05:19:08.022] [ERROR] [Server Error] {"title":"'messages' array must only contain objects with a 'content' field that is not empty"}

Yeah got the same error.
[2024-02-02 20:07:14.709] [ERROR] [Server Error] {"title":"'messages' array must only contain objects with a 'content' field that is not empty"}


feat(ci): Use with changes rules

What does this PR do?
Restore the usage of proper with changes rules dedicated for some tests

Motivation
Execute tests based on content, improve the efficiency of the CI

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Save image => empty

I tried to save an image using the "Save" button on your project (http://evanw.github.io/webgl-filter/)
When I click on this button, an empty image appears. Why ?
Thanks

yes, same issue.

Adding update() in $('#save').click(function() fixes this.
i.e.
window.open(canvas.update().toDataURL('image/png'));

Thanks for your feedback but to me it still does not work. When saving, in open a new tab fully blank on chrome.

What still doesn't work?   You've made the edit on your local copy, or used my fork?

I was using your fork http://evanw.github.io/webgl-filter/

loading a picture.
do any changes.
tried to save: ko.

I can confirm that update() works. But browser security prevents the image from being saved: Not allowed to navigate top frame to data URL
This can be fixed using this approach: https://ourcodeworld.com/articles/read/682/what-does-the-not-allowed-to-navigate-top-frame-to-data-url-javascript-exception-means-in-google-chrome


Installation error

Below error is coming during installation -->
> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover --ansi

In PackageManifest.php line 131:

  Undefined index: name

Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 1

run composer update
then run composer install

Below error is coming during installation -->
> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover --ansi

In PackageManifest.php line 131:

  Undefined index: name

Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 1


doc: Documentation issue in 'samples/drivers/i2c/custom_target/README'

Describe the bug
old
west build -b lpcxpresso55s69/lpc55s69/cpu0 samples/drivers/i2c_target
new
west build -b lpcxpresso55s69/lpc55s69/cpu0 samples/drivers/i2c/custom_target/
<< Please describe the issue here >>
<< You may also want to update the automatically generated issue title above. >>
Environment

Page: samples/drivers/i2c/custom_target/README
Version: main
SHA-1: 00ffad91027873d8edbfb3bbef1706c8a86e0144

@ypearson-bdai can you open PR for this?


Fixes to Drag Layer API documentation.

Replace supposed typo CustomDragSource with CustomDragLayer for ES 6 documentation.

:+1:


UInt serialization differs between 64 & 32 bit architectures

When running this code:
let a = Uint::<32>::from_u8(5);
println!("{:?}", base64::encode(serde_json::to_vec(&a).unwrap()));

from a 64-bit environment (My mac), I get
"IjA1MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwIg=="

And when running the exact same code from within a wasm environment (which is 32 bit), I get
"IjA1MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAi"

Which is twice as short. This is problematic because the server's 64bit's serialization cannot be deserialized by my wasm's front end.

The 32 in Uint::<32> tells you that the number of memory words used to represent this unsigned integer is 32.
The problem you're encountering is that the size of a memory word is architecture-dependent:

a 32-bit architecture uses 32-bit words, whereas
a 64-bit architecture uses 64-bit words.

Assuming the bit-length of your unsigned integer is constant regardless of the environment, I'd recommend you replace Uint::<32> with U2048. It is the struct that contains a 2048-bit unsigned integer, regardless of the environment.


IR Camera Tracking Drift/Jumps

I found the following issues in positional tracking that can make the experience better.
When the camera faces the HMD moving from the front LEDs to the side LEDs, and vice versa, the camera has a small jump when it resets. I assume the algorithm can be tweaked to make this smoother - at the moment this seems to be the major cause of the positional tracking jumps.
Second is the IR camera tracking drift. It happens when the HMD falls out of bounds of the camera range, I think the algorithm extrapolates the movement via velocity, which then makes the HMD move all the way. Also happens when you look left really quickly (WRT the camera) and it enters that area where the camera doesn't see the LEDs.

Thanks for the feedback!
I'm cc'ing some other folks who've touched tracking that might be interested in my response below, which turned out to be longer and more of a write-up than strictly a response to an issue report - perhaps it is a whitepaper or blog post in the making. @VRguy @russell-taylor
Some info that might be helpful:
The camera does not reset at any point in the algorithm. The closest the tracking system gets to "resetting" is when it reverts to RANSAC from its normal SCAAT Kalman operating mode due to a number of possible reasons (losing sight of all beacons for some time, noticing that it's been making really bad predictions for half a second straight, excluding all visible beacons as "implausible" for an extensive period of time, etc) - indicated by a message about "losing fix". You shouldn't be seeing such a message when going from front to side LEDs - if you are, then your unit is really, really out of spec, or something else is different between your units and my unit that we probably need to discuss through other channels. There also isn't a specific "switching" from front to side LEDs explicitly handled - when in stable tracking, each recognized beacon that meets the criteria (emission direction sufficiently toward the camera, etc.) is filtered in to correct the state prediction individually. So, ideally there are several frames where both front and side beacons meet the criteria.
Due to manufacturing variances, beacon light transmission through the faceplate, presumably the fact that the faceplate and body of the HMD are not permanently fixed together (hackability is good!), and other unknown issues (the side LEDs have always seemed to be a bit of a thorn in my side, which would be a logical place :stuck_out_tongue_winking_eye:) , the side LEDs do particularly benefit from pre-calibration beyond the typical autocalibration that might happen during gameplay. Make sure you've followed the steps at https://github.com/OSVR/OSVR-Docs/blob/master/Getting-Started/HDK/Video-Based-Tracking-Calibration.md for beacon pre-calibration, especially being sure to watch the embedded video. With calibration, style is almost everything: you want smooth moves keeping lots of beacons recognized and contributing to the pose as you bring beacons in and out of sight so the algorithm can (implicitly) register their location with respect to each other.
Any specific algorithmic suggestions you might have would be appreciated - comments in the code have citations to the relevant academic literature to help you get your footing :wink: And, seriously, if do have any background in tracking/filtering algorithms or know somebody who does, do feel free to make the connections, since this is a real open source community. (I'm sure there are probably improvements that can be made, especially to the heuristics applied in choosing which beacons are eligible to use and which beacons are used but receive penalties (in the form of variance multipliers) and the nature of those penalties. Those are definitely going "off-book" in terms of moving from academic literature of theory to production implementations.)
Re: so-called "camera tracking drift" - rest assured, the camera is not drifting. I prefer to refer to this phenomenon as "coasting", and reserve "drift" for things like "yaw drift" (in IMUs/gyroscopes) where direct or reasonably direct measurements that are supposed to be constant end up having a change as a function of time. What you're seeing is expected (in some sense) behavior, but let me explain. When in normal SCAAT Kalman operating mode, the process model ("what the tracking algorithm assumes your movement will behave like") is a constant-velocity model with exponential damping (that assumes white noise/random walk for your random accelerations, to speak imprecisely).  Constant velocity models (even without damping, the presence of which reduces coasting) are pretty typical for this type of tracking, and something like them is required to make the whole system actually work.

Elaboration: Why are they required? Well...

You have to be able to predict where the tracked device will be,
in order to predict what the beacon measurement will be,
to compare (delta/measurement innovation) to what the beacon measurement actually was,
and to be able to propagate that delta or innovation, along with the measurement's covariance, back from measurement space,
through a bunch of linear algebra (including Jacobian matrices, since we're modeling a non-linear system - hooray for 3d rotation being nonlinear) that I'll spare you the details of, into a state-space correction and an update to the state error-covariance matrix,
finally giving us a new state (pose) estimate complete with an updated estimate of its uncertainty (as well as the updated velocity estimates required both to do it again and to perform predictive tracking outside of the main filter). :tada:

And that, my friends, is a condensed version of how an extended Kalman filter (EKF), and specifically the SCAAT Kalman filter in our tracker (excluding the part that does beacon autocalibration, which augments the state vector with beacon position as well), works, in a single exceedingly-long sentence. :grin:

So yes, it does extrapolate the movement via velocity. There is an exponential decay/damping factor applied so you don't go flying forever: the default is 0.9 for both linear and angular velocity, which means that the velocity after $t$ seconds is $0.9^t$ times what it was at the start (so 0.9 times after one second, 0.9^2 after two, etc.). We did initially have these much lower (as low as 0.1 or 0.01, iirc), but it negatively impacted active tracking (since it was basically turning it into a constant-position model: assuming your head was still).  You can easily tweak these from the config file (and without any academic background in tracking or filters - these were just guesses between 0 and 1 that seemed to work well): if you find a better default, please let us know and we can incorporate that. (There's a lot of parameter tuning in these filters, and the parameters interact, which is part of what makes them a challenge.)  Here's a sample chunk of the config file, hopefully you can see where it fits in to an existing config file so you can add the the two fields you're wanting to edit: linearVelocityDecayCoefficient and angularVelocityDecayCoefficient. The description of them are https://github.com/OSVR/OSVR-Core/blob/master/plugins/videobasedtracker/Types.h#L117  - note that you probably do want to keep the linear and angular ones equal (or nearly equal) to each other, since they interact, but there's no harm in experimenting. I'd just try each new attempt with Tracker Viewer before a game in case unexpected instability occurs.
        "params": {
            "showDebug": false,
            "includeRearPanel": true,
            "headCircumference": 55.75,
            "linearVelocityDecayCoefficient": 0.9,
            "angularVelocityDecayCoefficient": 0.9,
            "calibrationFile": "videotrackerCombinedCalibrationFile13.json"
        }

You'll note that you do stop coasting before the exponential decay would bring your velocity to zero - that's because one of the aforementioned "reset to RANSAC" triggers kicks in after some time of not seeing any beacons and says that the Kalman algorithm is no longer to be trusted to generate pose estimates. Figuring out an improved algorithm/heuristic for how/when to increase velocity decay and/or stop prediction altogether is an open question, and probably deserves its own issue, though with a unified IMU and video-based single-filter implementation as a probable future direction, there will be a single process model incorporating both the LED beacons and the IMU data, so we won't want to necessarily apply something to the entire model when it's just one source of data that has gone absent. And, of course, as soon as the camera sees a beacon again, it should stop coasting: either the Kalman filter is sufficiently confident in its ability to regain stable tracking that it goes right back into steady-state, or the system was waiting for a beacon to appear before resetting to RANSAC to acquire a new pose estimate entirely from scratch. You should only coast if the camera can't see any (enabled) beacons. (see the below for more on that little "enabled" caveat)
Beyond tweaking the decay parameters or some potential algorithmic contributions :wink: : there are some improvements recently merged to master that will improve the behavior and maintain positional tracking longer when looking left. We had been running with the right-side LEDs disabled for pose-estimation purposes up until now because they were too flawed and and using them introduced substantial tracking artifacts (for details, ask @VRguy on a video call and be prepared with a screen capture tool - they threatened to turn my demonstration of its behavior over skype into a GIF) However, improvements in the math and tracking code minimized/changed the nature of the artifacts, allowing us to turn those back on, so turning your head left won't cause you to "coast" as easily (since you'll still have active beacons in sight). It may also improve positional tracking smoothness turning the other direction as well - I haven't compared the new code to the pre-merge code head-to-head recently.  Though these updates have been merged, problems with the CI server have prevented an updated snapshot from coming out of the pipeline. A version number around or greater than 0.6-1056 will include the updates, so look for that.

I'm on Snapshot-v0.6-1068 with an HDK 1.3 and I've noticed similar activity to what marquistan reported.  I've tested with and without pre-calibration using the pre-calibration utility. If I enable debug mode in the server config json, I can see the tracking drop in the console whenever I switch from the front LED array to either the sides or back.  It may also be distance-related.  I've found that if the HMD is more than 0.6M-0.9M away from the IR Camera, the side and back LED beacons are not detected at all but the front ones still are.  If you get closer than 0.3M, you also lose the side and back LEDs.  That leaves a narrow field of functional position tracking without constant drops.
I see the changes made to the video positioning code a few days back but the pre-calibration utility doesn't appear to have been updated, it still ignores the one side and rear LEDs, perhaps because they are still in the skip list:
    /// these are beacon IDs we disabled (1-based)
    static const auto IDS_TO_SKIP = std::unordered_set<std::size_t>{
        1,  2,  10, 12, 13,
        14, 21, 35, 38, /* plus the rest of the back */ 36,
        37, 39, 40};

Will the pre-calibration utility be updated as well to enable the side/back LEDs during calibration?  Not sure if that would help at all with this issue, but figured I'd mention it.
In the meantime I'll try toying with the decay coefficients to see if I can get some better results with those.

@jcp219 thanks for the find! Been too busy with other things to test this out. Is it possible to actually use the LEDs on the side again? If it's too much (I recall this was an issue), can we use 2 a side instead of 3 on each? See how that helps.

@marquistan In the recent update, as I noted earlier, we did turn on all the side LEDs again.
@jcp219 Hmm, I'm surprised you've getting such short range. The decay coefficients wouldn't affect that - that would be a lighting or image processing issue.  I had been meaning to update that list in the pre-calibration utility, though I believe those are just skipped from display, not actually skipped from running calibration (the utility is just running the tracker code with a different display on it, I don't believe it's actually turning off calibration of those LEDs - doing that requires work at a different level - though I'll check it out this morning when I fix the display issue).
You don't actually want to pre-calibrate the rear LEDs because they're not rigidly fixed to the front of the HMD: their location relative to the other LEDs can change substantially every run, so pre-calibrating them would actually make tracking worse (by moving them into a less-neutral starting location), which is why they're not shown on the utility, to try to keep you from doing that. :)

@rpavlik ah I was basing it off the calibration utility, which you clarified wasn't changed to display the other side of the LEDs - I was merely basing it on that. Thanks for the clarification!


Duktape memory use question

Hi,
I have a custom memory allocator implemented and have been running memory testing with Duktape. I log the amount of memory allocated after loading my JS into Duktape and get a value of xKB. However, if I measure the change in PSS after loading, I see an increase of almost 2xKB. I was wondering if this is expected and if you had any ideas why this might occur. I have been unable to account for this PSS growth with massif.

It's unfortuntely difficult to answer without knowing how your custom allocator works. Have you checked out what happens to PSS if you allocate a set of regions with the custom memory allocator?
Typically an allocator manages memory in its own data structures, requesting more pages from the OS as needed. Pages are typically requested in "chunks" so the OS often sees a larger allocation than actually in use in the allocator.

It sounds like you’re saying the custom allocator should account for all of Duktape’s memory usage? I’m currently using a basic malloc wrapper. Do you mean trying a pooled allocator that manually uses mmap or something like that?

Duktape shouldn't bypass the custom allocator, all allocs/reallocs/frees should go through it.


add Model.createClass

This is a workaround for #53 -- you can avoid the issue described there if you create models in your app like
const MyModel = Model.createClass({
  // ...
})

instead of
class MyModel extends Model {
  // ...
}

I would reject it. Even React moving to ES2015 and removing support for createClass

@levity Does v0.10.0 work for you (#192)? This is a little too hacky in my opinion.

I’m no longer using redux-orm, but that does sound like a promising
alternative.
On Thu, Jun 7, 2018 at 7:59 AM haveyaseen<EMAIL_ADDRESS>wrote:

@levity https://github.com/levity Does v0.10.0 work for you (#192
https://github.com/tommikaikkonen/redux-orm/pull/192)? This is a little
too hacky in my opinion.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tommikaikkonen/redux-orm/pull/116#issuecomment-395452466,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAL0gyNdeENegF36CSmlxwiRAL9h-ttLks5t6T_pgaJpZM4M2Twa
.

Alright, thanks for replying anyways. I'll go ahead and close this then :slightly_smiling_face:


Show interesting donations wishes on the top of the campaign page

Which area(s) of Podkrepi.bg are affected? (leave empty if unsure)
The campaign page.
Describe the feature you'd like to request
Sometimes we have some cool donation wishes.
We can use the top right hand side of the campaign page to show them.
It would make things more encouraging for the other donors.
Describe the solution you'd like

We can put some of the latest donation wishes below this box.
Probably even one would be enough if it is randomly selected from the last 10.
I suggest to choose messages that have at least 5 words.

If there are no such choose something from the last 24 hours.
If there are no such then don't show it at all.
Describe alternatives you've considered
No response

On the latest design of the payment card I have added a tab switching between wishes and latest donations
I think we need to define the rules of wishes - who is going to select them ?

This looks much better.
Is it possible to add a bubble at the bottom with one random (long) wish?

Closing this as duplicate of: #1426

I am reopening this as the #1220 is already closed, but we have new design ideas from the design team:

I'd like to take this one.

@kzhecheva The ticket is assigned to you.


Respect optional deviceName parameter passed

However, use the name passed as a command-line option with priority.
Note that ios-sim-portable should be refactored to take the currently running simulator into account on its own, instead of having to pass it as a param from the outside.
Ping @rosen-vladimirov

::::::+1:::::::
:+1:


[stable/postgresql] Allow setting the mount path of initdb scripts

What this PR does / why we need it:
Some PostgreSQL images such as TimescaleDB are shipping with initdb scripts in /docker-entrypoint-initdb.d/. Using the same directory as mountPath results in these scripts being shadowed.
This change makes it possible to specify a different mount path (for example /docker-entrypoint-initdb.d/helm/) so that these scripts can coexist.
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

Hi @juan131
Thank you for the fast reply.
The reason adding this is that currently the path of the ConfigMap mount is fixed to /docker-entrypoint-initdb.d/.
This wouldn't be a problem, but the TimescaleDB docker image (based on bitnami/postgresql) already contains some initialization scripts: https://github.com/timescale/timescaledb-docker/tree/master/docker-entrypoint-initdb.d
When we now use the initdb feature of the helm chart only the initdb scripts are visible in /docker-entrypoint-initdb.d/. The preexisting files (000_install_timescaledb.sh, 001_reenable_auth.sh and 002_timescaledb_tune.sh) are inaccessible.
This pull request adds the ability to specify a custom mount path, e.g. /docker-entrypoint-initdb.d/helm/. This enables a coexistence of the already existing files and those from the helm chart.

Thanks for the detailed explanation. It makes total sense.

This pull request adds the ability to specify a custom mount path, e.g. /docker-entrypoint-initdb.d/helm/. This enables a coexistence of the already existing files and those from the helm chart.

Just a question. How are you supposed to run these new scripts during the initialization? I mean, the current logic (the one at Bitnami PostgreSQL image) won't detect your custom scripts (it'll only detect the ones included in the TimescaleDB docker image) and therefore, you need to find a way to execute them

Hi @juan131
I'm not sure I understand your question.
When the initdb scripts are mounted in /docker-entrypoint-initdb.d/some-custom-directory/ they are going to be found by this script https://github.com/bitnami/bitnami-docker-postgresql/blob/master/11/centos-7/rootfs/libpostgresql.sh#L580
There is no maxdepth option specified in the find command so it will decend into the custom subdirectory.
The directory layout would look like this:
/docker-entrypoint-initdb.d/000_install_timescaledb.sh
/docker-entrypoint-initdb.d/001_reenable_auth.sh
/docker-entrypoint-initdb.d/002_timescaledb_tune.sh
/docker-entrypoint-initdb.d/some-custom-directory/some-initdb-script.sql
/docker-entrypoint-initdb.d/some-custom-directory/other-initdb-script.sql

There is no maxdepth option specified in the find command so it will decend into the custom subdirectory.

 Thanks so much again for the explanation.
Please rebase your branch from master to avoid the conflicting issues.

@mwalser
Would you mind to resolve conflicting files please?
stable/postgresql/Chart.yaml
stable/postgresql/README.md
stable/postgresql/templates/statefulset.yaml

Sorry, I just saw the stale bot notification.
Yes, you should fix the existing conflicts in the following files:
stable/postgresql/Chart.yaml
stable/postgresql/README.md
stable/postgresql/templates/statefulset.yaml

In the same way, as @juan131 suggested, can you add the same change in the values-production.yaml?

Sorry, for the late answer. It was a bit of a stressful time. I'm not sure anymore the solution I proposed is the right way to go. While it might solve my specific problem it feels very hacky.
I thought about changing this merge request to always put the initdb scripts into a subfolder. But while this might work with the bitnami based images it will not on the official postgres docker image. So this is no way forward.
The next thought I had was to abandon the idea of letting the user specify the initdb script path via initdbScriptsMountPath and to just introduce a boolean initdbScriptsUseSubfolder (which would default to false). IMHO this feels slightly less hacky.
Do you have any opinions on this?


Balanced Bracket Problem

closes : #1683

@Rohan27s pls check once more i have created everything one more

Why have you deleted tree/Readme in your commit. I asked you to remove the commit of the read me file, not to delete the tree/readme file in your commit

@Rohan27s sorry i am trying to getting it back

@Rohan27s i have restored the readme file. Pls guide me how to remove that commmit

@Rohan27s I have resolved the problem pls check.

@Rohan27s ok sir

@Rohan27s  if i delete my repository will it effect the merged issues?

No @Prerna-07

@Rohan27s I have done all necessary changes pls check my pull request #1794.

@Prerna-07 don't comment on a closed pr. I will check it wait.


ci: update settings

PR Summary
updates some settings for venado and RZ systems

PR Checklist

[ ] Adds a test for any bugs fixed. Adds tests for new features.
[ ] Format your changes by using the make format command after configuring with cmake.
[ ] Document any new features, update documentation for changes made.
[ ] Make sure the copyright notice on any files you modified is up to date.
[ ] After creating a pull request, note it in the CHANGELOG.md file.
[ ] LANL employees: make sure tests pass both on the github CI and on the Darwin CI

If preparing for a new release, in addition please check the following:

[ ] Update the version in cmake.
[ ] Move the changes in the CHANGELOG.md file under a new header for the new release, and reset the categories.
[ ] Ensure that any when='@main' dependencies are updated to the release version in the package.py

@rbberger no objections. Merge when ready. (I will let you do so, to avoid repeated problems from me being overzealous. ;) )


[Feature Request] Dom-Repeat for (array-like) objects (e.g. Firebase Push-ID)

I think it would be handy if it would be possible to use Dom Repeat for objects (or at least array like objects) as created by using Firebase push.
An example of implementation can be found here:
http://stackoverflow.com/a/37015188/4178195
Thanks!
Tim

I think this is a duplicate of #1385

It is, thanks.
But unfortunately also no proper workaround solution with two way binding there :(


Tooltip misplaced if there is another absolute position element

Well, just bumped into this. I made myself a navbar with some links, added data-tooltip to them, initialized the code, tooltips show on hover, nive. Now, If I add a absolute position image below, in another component, tooltips are rendered at the bottom of the page. Anyone facing that?

Can you provide some source code?

This might be the same issue as c00c954f. Try updating to the latest github version and see if the bug is still happening.


Use Release trigger for official NuGet release

GitHub has a wonderful concept of releases, which is an extra layer on top of git tags and which provide a nice UI to create, manage and view a release.
We should use GitHub releases as a formal and conscious step to create, document and publish a NuGet package.
Add the release option as an additional CI trigger:
on:
  push:
  pull_request:
  release:
    types:
      - published

In order to kick off a deployment for a GitHub Release create a job called deploy:
deploy:
  needs: build
  if: github.event_name == 'release'
  runs-on: ubuntu-latest
  steps:
    - uses: actions/checkout@v2
    - name: Setup .NET Core
      uses: actions/setup-dotnet@v1
      with:
        dotnet-version: 3.1.301
    - name: Create Release NuGet package
      run: |
        ...
        ...
        dotnet pack -v normal -c Release --include-symbols --include-source -p:PackageVersion=$VERSION -o nupkg src/$PROJECT_NAME/$PROJECT_NAME.*proj
    - name: Push to GitHub Feed
      run: |
        for f in ./nupkg/*.nupkg
        do
          curl -vX PUT -u "$GITHUB_USER:$GITHUB_TOKEN" -F package=@$f $GITHUB_FEED
        done
    - name: Push to NuGet Feed
      run: dotnet nuget push ./nupkg/*.nupkg --source $NUGET_FEED --skip-duplicate --api-key $NUGET_KEY

I did this already.


about ux react get logged user information

symfony+symfony/ux-react,
in any_file.html.twig

now i want kown how can i get logged user information on EmployeeList.jsx file?
like in any_file.html.twig use
app.user

You have a concrete example in the ux-react documentation:
div {{ react_component('MyComponent', { 'fullName': app.user.fullName }) }}>

@ker0x i know this way.but i want get full user informations.so.did have other best way?

you can just serialize your use and pass it as json to your JS code
ref https://symfony.com/doc/current/frontend/encore/server-data.html (bottom of page)

@94noni thank you,


Duration and the docs

I don't understand. What is this : https://github.com/moment/moment/issues/4026
when these are your docs :
https://momentjs.com/docs/#/durations/
I'm under windows 10 Pro 64bit
npm 5.6.0
node 8.9.4
chrome Version 66.0.3359.117 (Official Build) (64-bit)
Angular 5.2.9
and moment 2.22.1
I don't understand.
literally none of what is advertised is available.
I can create a moment.
that's it.
maybe consult that moment's day.
but none of the really interesting stuff that is advertised on your doc is available  :

where are all my methods that should be available?

Perhaps you've misunderstood the docs.  Look at the table of contents on the right-hand-side and you'll see 20 subheadings for things you can do with a Duration listed underneath 'Duration': Creating, Clone, Humanize, ... Is a Duration, As ISO 8601 String, Locale.
The list does not include 'Format' - that's what #4026 was saying and asking for: people want to be able to format a Duration, but that functionality doesn't exist.
Higher up the table of contents, you'll see Format mentioned underneath Display, which is referring to an date/time instance of moment, not a Duration.
How could the docs / table-of-contents be reorganised to make this clearer?

update :
I replaced the auto-import :
import { moment } from 'ngx-bootstrap/chronos/test/chain';
with
import * as moment from 'moment';
now the error is as follows :

nevermind I figured it out.
so in the end what could help in the docs is to make it clear to users that the default suggested import is not the right one
and that they should type out :
import * as moment from 'moment';


Making DAG nodes composable

Just to record some thoughts from a conversation with @igorminar for future reference:
It seems to be a common pattern to use functions to compose multiple plugins:
var es6ToEs3 = function (node) { // "node" = new terminology for "tree"
  var es5 = es6ToEs5(node, { description: 'es6ToEs3 step 1: transpile to es5' })
  var es3 = es5ToEs3(es5, { description: 'es6ToEs3 step 2: transpile to es3' })
  return es3
}

var appTranspiled = es6ToEs3('app')
var testsTranspiled = es6ToEs3('tests')

This makes debugging hard, even with descriptions, because we have many instances of the es6ToEs5 plugin that are difficult to tell apart.
It's tempting to create more informative node descriptions by concatenating strings, but that seems a bit ad-hoc.
I wonder if the pattern is common enough to warrant adding support for composing a subgraph of nodes into a "supernode". For example, the es6ToEs3 might be a "supernode" on its own, taggable with a description:

(s/transpile/es6ToEs3/ in the picture) We can compose even further, e.g. an entire buildApp node.
The point of this is to be able to give names or descriptions to the "supernode", like so:
var appTranspiled = es6toEs3('app', { description: 'transpile app' })
var testsTranspiled = es6toEs3('tests', { description: 'transpile tests' })

I think this would be fairly straightforward to implement in the builder. We don't need to do this right now, but perhaps it's an interesting option for the future.

In ember-cli, we do basic grouping by "addon". But some broccoli sanctioned labeling scheme would def allow for better tooling/debugging, and likely many dev's happier.

Old issue, but the idea of "groups" of plugins which is something instrumentation, logging, and visualization tools are aware off is still worth exploring.


Usage to playback video-audio live streaming on browser

Hi,
It's really cool live streaming project. I'd like to integrate that with my project.
So, First of all, I'd would to know the usage.
I build the solution, started up the Media Encoder and the Media Server. All them start up ok, but I couldn't playback on browser using main.html or mpeg.html

Sorry for my late reply!
Can you give the screenshots about your running Media Server and Media Encoder?

Don't worry about it. Yes, I can.
Encoder

Server

Running main.html

No need to modify main.html
You may undo your changes (revert it from git) to solve the problem.
Your Media Server is listening on port 9320, which is for stream players to connect.
You may find the information about the ports from Media Server's log.
If you want  to change the ports, you may modify App.config
Media Server's "Input" ports are for encoders to connect.
Media Server's "Output" ports are for stream players to connect.

I reverted the changes.
It is no working on Chrome  60.0.3112.113. Only in Firefox.
I'm getting a huge delay. As an example, using Camera a Microphone device. The delay is about 10 seconds.
So how can I get a subseconds?


Animated subviews in   don't work

Hi,
I created a custom Checkbox component with animated check icon that should work like this:

but if I put the animated component inside  component the animation stops working and the end result is the same as this:

Note: the speed of the gifs has been slowed down to allow for understanding the animation.
I looked at the code of  component and I noticed something that could block all other animation:
https://github.com/oblador/react-native-collapsible/blob/master/Collapsible.js#L145-L147
according to the documentation:

By default, if one animation is stopped or interrupted, then all other animations in the group are also stopped.

Any workaround?

I did run into an issues with animations, breaking if they were triggered during a collapsible (open)  animation. The trick was to hook the collapsible animation end before firing animation events on my own components.
<Collapsible collapsed={!this.state.collapsible} onAnimationEnd={this.onCollapseAnimationEnd}>
Further i had issues if the collapsible contents view had dynamic height
<Collapsible collapsed={!this.state.collapsible}>
           <View ref={element => this.collapsibleRef = element} style={[{height:SOME_FIXED_HEIGHT}]}><MyComponent></MyComponent></View>
             </Collapsible>

Hey could you link to the source for that checkbox? Would love to do some testing.


Ignore tags for on push event

This PR ignores tags for on push event. We've been running all tests twice where the first one when PR gets merged and later when tagging.

This PR will be tacled by https://github.com/wakatime/wakatime-cli/pull/408


MCM will not show up at all

Hello,
I can't get the MCM to even show up in my game. I am playing the recent SE version 1.6130 ? I am using MO2 and installed the Telekinesis mod 1.3 . I ran FNIS just in case. NOTHING SHOW US . HELP.

Hey, thank you for reporting this. I fixed this issue with 1.3.1 https://github.com/garryrot/telekinesis/releases/tag/1.3.1


Cannot run demo

ImportError: cannot import name 'constant_init' from 'mmcv.cnn'
I followed the installation directions.  mmcv 2.1.0 is installed.  I do not have CUDA on my system.

You need cuda to run this repo

I hit this error too, it's not that you don't have CUDA, it's because the authors version of mmcv is likely different than when you installed it. The authors could fix this by tagging a specific version of mmcv with pip install mmcv==1.7.2 or whichever version they used.


Backend: Support for language localization

Translation for Web, Android, IOS all three platforms.
I've seen OSS projects use these sites for translation purpose

Crowdin
Transifex
Weblate

I think Weblate is better as it's opensource.
Features: https://weblate.org/en/features/

https://weblate.org/en/hosting/

+1 for Weblate, and a solid -1 for the other options.

Would love to support this, but localization is a pretty big undertaking and I'm not convinced it will lead to enough growth to pay for the initial investment and continued maintenance.


Is there a way to validate with dependancies?

Is there a way to define validate attribute dynamicaly? as a example
age : required,
guardianName: if age < 18 then required else notRequied

I would have two separate validators. One for dependents and one for guardians. Then you can split your data set by these two categories and validate separately.

Yes there is, here is an example from the documentation:
  creditCardZip: function(value, attributes, attributeName, options, constraints) {
    if (!(/^(34|37).*$/).test(attributes.creditCardNumber)) return null;
    return {
      presence: {message: "is required when using AMEX"},
      length: {is: 5}
    };
  }


[CM-2241] Fixed Date in Post Back Message | iOS SDK

Summary

Resolved date and time format issues in rich messages.
Fixed visibility issues of the Calendar UI in dark mode on devices.

@coderabbitai review


Explore alternatives to NetworkX

We currently use a Python library called NetworkX for graph modeling. In particular, our route calculation uses NetworkX's all_shortest_paths.
Alternative graph libraries reportedly are much more performant. Examples include: igraph, graph-tool, networkit. Is it worth switching to another graph library?
Note that the current version of the simulator can't be (easily) parallelized. We need to update in-flight HTLCs in channels, which are stored in Python's PriorityQueues inside each ChannelDirection. We use single-threaded functions to get and put elements in / out of the queue. Parallelizing the code would require us to correctly handle the cases where the same queue is updated at the same time from different threads.
We also use (single-threaded) priority queues in Schedule, but the task of creating a schedule doesn't need to be parallelized to begin with.
Further reading:

Benchmark of popular graph/network packages v2
What scalability issues are associated with NetworkX?
Opinions on #igraph vs #netwrokx in #python?
Working With Large Internal Link Graphs in Python
What is the maximum number of nodes and edges with attributes that graphs generated by NetworkX package can handle?

From a Reddit thread linked above:

Use NetworkX for smaller networks and dynamic networks. NetworkX is pure Python, well documented and handles changes to the network gracefully. iGraph is more performant in terms of speed and ram usage but less flexible for dynamic networks.

Topology-wise, our graph is fixed, but edge attributes (i.e., slot queues) change all the time. Is this considered dynamic?

Is this considered dynamic?

igraph developer here. Changing values of attributes is generally fast in igraph. It is only changing the graph topology (i.e. adding or removing edges or vertices) that is expensive.


This plugin slow down Homebridge

Describe The Bug:
In the console log of Homebridge this error is always displayed: This plugin slows down Homebridge (see the log below).
To Reproduce:
Just install the plugin, I've updated to 1.0.4 today.
Expected behavior:
No error messages and better homebridge speed. Now I had to create a child bridge to isolate this issue and don't slow down the whole system.
Logs:
[7/15/2021, 3:14:20 PM] [homebridge-samsung-air-conditioner-smart-things] This plugin slows down Homebridge. The read handler for the characteristic 'Current Heater-Cooler State' was slow to respond! See https://git.io/JtMGR for more info.
[7/15/2021, 3:14:20 PM] [homebridge-samsung-air-conditioner-smart-things] This plugin slows down Homebridge. The read handler for the characteristic 'Active' was slow to respond! See https://git.io/JtMGR for more info.
[7/15/2021, 3:14:20 PM] [homebridge-samsung-air-conditioner-smart-things] This plugin slows down Homebridge. The read handler for the characteristic 'Current Heater-Cooler State' was slow to respond! See https://git.io/JtMGR for more info.
[7/15/2021, 3:14:20 PM] [homebridge-samsung-air-conditioner-smart-things] This plugin slows down Homebridge. The read handler for the characteristic 'Target Heater-Cooler State' was slow to respond! See https://git.io/JtMGR for more info.
[7/15/2021, 3:14:20 PM] [homebridge-samsung-air-conditioner-smart-things] This plugin slows down Homebridge. The read handler for the characteristic 'Current Temperature' was slow to respond! See https://git.io/JtMGR for more info.
[7/15/2021, 3:14:20 PM] [homebridge-samsung-air-conditioner-smart-things] This plugin slows down Homebridge. The read handler for the characteristic 'Cooling Threshold Temperature' was slow to respond! See https://git.io/JtMGR for more info.

Plugin Config:
    {
        "name": "homebridge-samsung-air-conditioner-smart-things",
        "token": "XXXXXXXXXXXX",
        "platform": "HomebridgeSamsungACSmartThings",
        "_bridge": {
            "username": "XX:XX:XX:XX:XX:XX",
            "port": 57024
        }

Environment:

Plugin Version:
Homebridge Version: 1.3.4
Node.js Version: 10.19.0
NPM Version: 6.13.4
Operating System: Raspbian GNU/Linux Buster (10)

Hello @JackMorens , what temperature unit are you trying to use the plugin with C or F? Did it work for you before on version 1.0.3?

I use Celsius degree C°, this error also existed with version 1.0.3.
The temperature is displayed correctly:

@JackMorens  does it work to set the target temperature? Does it take a long time, a few seconds or minutes?

It works to set the target temperature, it takes a few seconds and it also works with Siri. But I had to set up a Child Bridge to isolate the plugin otherwise it didn't work and slowed down the whole system.

Ok, but I don't think it depends that much on that. There have been some changes made to homebridge since version 1.3.0 https://git.io/JtMGR
I found this thread that might help you understand the problem https://github.com/cbrandlehner/homebridge-daikin-local/issues/128

Hello @JackMorens, please try version 1.0.6 and let me know if you see any improvements. I've tried a fix that was suggested in the links that you provided. I'm not expecting any improvement regarding the speed but the warnings should disappear. Thanks!

Great! I've updated the plugin to version 1.0.6 and now there is no more error message in the log. I also deactivated the Child Bridge and reconfigured the AC as accessories of the main bridge and it works fine without slowing down the others plugins.


feat: eleventy

added eleventy
removed unnecessary files

recheckcla

I have read the CLA Document and I hereby sign the CLA

recheckcla


mobx doesn't render when I select

`@observer
class App extends React.Component {
@observable mode = "create";
@action
menuChange = (event) => {
    this.mode = event.target.value;
};

@action
render() {
    return (

{this.mode}

            <select onChange={this.menuChange}>
                <option value={"create"}>Create</option>
                <option value={"other"}>Other</option>
            </select>

    )
}

}`
It doesn't show "other" even though I chose it.
"mobx": "^5.0.3",
"mobx-react": "^5.2.3",

Oops be cause render has action.


Question: can one use dartlang/build with polymer?

Can one use https://github.com/dart-lang/build with polymer?

I guess https://groups.google.com/a/dartlang.org/forum/#!forum/misc would be a better place for such questions.

Not today, both the web_components and reflectable transformers overwrite files currently, which is not allowed in build. If they are tweaked to not do that then yes it could be possible.


Missing regional indicators emojis

Hi, it seems like regional indicators emojis are missing (ex: https://emojipedia.org/regional-indicator-symbol-letter-a/ )
I know they aren't supported by all the providers but is it possible to add them here?
Thanks.

Will there be any update on that issue?

Can this be fixed?


0.10 RC update ?

As the new RC is bringing assemblies with strong name, packages need to be generated against those 'new' references.

Thanks.
I spent time on search a way to work with both preview6 and rc1 ( (and preview1-5).
I was able to avoid wasting this time.
0.10.0-a5 work with RC1


Code cleanup - guard headers, CAN printing

Guard headers for header files prevent errors/warnings from redefining constants and redeclaring functions
Commented out debugging print statements for CAN because they clutter a lot of the UART output when using the CAN library

I think the CAN print statements can be safely removed.

I think that's fine as long as we don't use more than a couple of queues per repository. I think we had memory space problems while rushing to test the qual demo which had 5 queues in OBC. If we want to have more smaller queues, maybe change the size to 5?

Ok sounds good


fresh commit for ndpi project

Hi! U can also add fuzz_tls_certificate target.

@headshog, can you add new targets as @koltiradw suggested?

Yes, okay


Usage within packages

TestDummy currently cannot be used within packages easily for a number of reasons:
namespacing within DbTestCase.php refers to several items that are available only in the Laravel global namespace and available when testing from a package.
use TestCase, Artisan, DB;

Setting the $factoriesPath static attribute on Factory is not possible before the .../tests/factories/someFile.php is processed. Producing a Undefined variable: factory notice.
I may be approaching this wrong.

How did you end up fixing this @andrewmclagan?

Without going into too much detail look at one of my repos, specifically this class and the composer.json files:
https://github.com/Jiro-Commerce/Product/blob/master/tests/TestCase.php
https://github.com/Jiro-Commerce/Product/blob/master/composer.json


cn-north-1 rds and autoscaling describe_instances get stuck

rds.describe_db_instances() and autoscaling.describe_auto_scaling_groups() don't ever return in the region cn-north-1 with moto==2.0.5.
I need to run those two commands on all the regions discovered by ec2.describe_regions(). But whenever the code reaches the cn-north-1 region it get's stuck forever, preventing any further testing to happen.
I've mitigated it applying a timeout to the boto3 client, but it's slowing down a lot the test suite.
I expect moto to answer as quick as in the other regions.
Example code
import boto3
from moto import mock_autoscaling, mock_rds2

@mock_rds2
def test_rds_describe_instances():
    rds = boto3.client("rds", region_name="cn-north-1")
    rds.describe_db_instances()

@mock_autoscaling
def test_autoscaling_describe_instances():
    autoscaling = boto3.client("autoscaling", region_name="cn-north-1")
    autoscaling.describe_auto_scaling_groups()

Hi @lyz-code, this should be fixed with #3661.
Just as an FYI: Moto does not currently mock any calls to endpoints in China, so all boto3-requests will execute against AWS itself.
Not sure why it get's stuck forever though. Personally I don't have access to the Chinese regions, so I can't test this - I just get an 'Invalid security token' exception, after 1 or 1,5 second, when executing your example test.


goog.ui.Slider will continue to fire change events after the mouse is moved outside the window

Open a page with a slider on it.  It would be nice to open the demo page (http://closure-library.googlecode.com/git/closure/goog/demos/slider.html) but the link seems to be broken.
Click and drag the mouse on the thumb of the slider, drag your mouse outside the window and release the mouse button.
Move the mouse back over the window with the slider.
Result:
The change events continue to fire and the thumb moves with the mouse.
Expect:
If the mouse is no longer down it should end the drag and stop firing change events

This issue is being closed as a preparation step before archiving the repository.  See the README for more detail.


expect an arXiv preprint

Nice work on latent diffusion model, can you provide an arXiv preprint of your paper? thanks! ^ ^

Hi, @JunyaoHu , thanks very much for your interest! I will upload the arXiv paper after I finish the camera-ready version. Both paper and code will come soon.


Latent var only experiments error

I want to train model with Latent var only mode.
from issue #13 I changed train config but i got this Exception
Do you know what the problem is ?
======
Loading NuScenes tables for version v1.0-trainval...
23 category,
8 attribute,
4 visibility,
64386 instance,
12 sensor,
10200 calibrated_sensor,
2631083 ego_pose,
68 log,
850 scene,
34149 sample,
2631083 sample_data,
1166187 sample_annotation,
4 map,
Done loading in 20.600 seconds.
Reverse indexing ...
Done reverse indexing in 5.2 seconds.
Epoch (1/100)
Traceback (most recent call last):
File "train.py", line 38, in
trainer.train(num_epochs=int(args.num_epochs), output_dir=args.output_dir)
File "/media/han/289e8c3e-12db-47da-8b89-15b58bef567d/home/han/prediction_256/PGP/train_eval/trainer.py", line 109, in train
train_epoch_metrics = self.run_epoch('train', self.tr_dl)
File "/media/han/289e8c3e-12db-47da-8b89-15b58bef567d/home/han/prediction_256/PGP/train_eval/trainer.py", line 153, in run_epoch
predictions = self.model(data['inputs'])
File "/home/han/.local/lib/python3.7/site-packages/torch/nn/modules/module.py", line 550, in call
result = self.forward(*input, **kwargs)
File "/media/han/289e8c3e-12db-47da-8b89-15b58bef567d/home/han/prediction_256/PGP/models/model.py", line 35, in forward
outputs = self.decoder(agg_encoding)
File "/home/han/.local/lib/python3.7/site-packages/torch/nn/modules/module.py", line 550, in call
result = self.forward(*input, **kwargs)
File "/media/han/289e8c3e-12db-47da-8b89-15b58bef567d/home/han/prediction_256/PGP/models/decoders/lvm.py", line 57, in forward
raise Exception('Expected ' + str(self.num_samples) + 'encodings for each train/val data')
Exception: Expected 1000encodings for each train/val data
Thank you in advance.

My bad, there's one more change needed in the training config file for the latent var only experiments.
In decoder_args, agg_type should be 'combined'.
This is because without the graph traversals to selectively aggregate node encodings along sampled routes, the aggregator returns a single encoding of the entire scene.

I also remove  'pi_bc' in  'tr_metric' , 'val_metrics' and then It works
Thank you for your prompt response.


feature: move welcome message to the LlmChatView

then nobody has to jury rig the history
and we make sure only the first message is an llmWelcome message (at least until they start jury rigging the history, but then that's on them...)

need to integrate the suggestions with the welcome message:


Bug in comparison between inequality and !=

There seems to be an error when variable names are long
Example:
>>> comparator = Comparator()
>>>print(comparator.compare("stakingTokenBalances > stakingTokenBalances", "stakingTokenBalances != stakingTokenBalances"))
>>>The predicates are equivalent.
>>>print(comparator.compare("x > y" ,"x != y"))
>>>The first predicate is stronger.

Found another relevant case:
>>> comparator.compare("x > y", "x == y")
'The predicates are not equivalent and neither is stronger.'

Hi @Kasche153
Both results are deemed correct. Closing this and opening an issue for detecting logical tautologies.


Use new FacetedPlot variants

Fixes https://github.com/VEuPathDB/web-components/issues/259
A couple of outstanding tasks:

[ ] Center the modal plots better
[ ] Fix the broken modal close button icon

@bobular @dmfalke Do y'all see the close button icon or is it broken for you as well? Here's what it looks like for me:

I also noticed that the mosaic y-axis labels are overflowing their container again sometimes, after multiple attempts on my part to fix that. It'll have to be a separate ticket since I've already merged the web-components portion of this work.

@chowington Yes the close (X) marker is not shown for me neither, however, this works for me (use fa instead of fas)

Intentionally used fa-3x for checking it: you can use fa-lg, fa-2x, etc for sure :)

That's simple enough! Thanks, DK!

@chowington as for vertical centering, though there may be a better approach, one way is to add flex and align-items for the following div class,

so, like adding the following two css properties in there.
display: flex
align-items: center

This will make vertical center as screenshot below (worked at both chrome and firefox), but be caution that this may affect all react-modal without specifically pointing out the target as you know well :)

I didn't check it carefully but this means that perhaps it can be configured/controlled from Mike's FullScreenModal component ? I mean, since it utilizes react-modal, there may be a way to set vertical center: looks like customStyles at the module's example may also align horizontally and vertically ?

@chowington Sorry I forgot to say one additional change at FacetedPlot component in conjunction with above. Wrapping modalPlot with div as well. So like,
      {modalComponentProps && (
        <FullScreenModal visible={modalIsOpen}>
          <button
            onClick={() => setModalIsOpen(false)}
            style={{
              position: 'absolute',
              top: 30,
              right: 30,
              backgroundColor: 'white',
              cursor: 'pointer',
              border: 'none',
              zIndex: 2000,
            }}
            title="Close expanded plot"
          >

          </button>

 {/* DK: here */}
            {modalPlot}

 {/* DK: here */}
        </FullScreenModal>
      )}

Thanks DK! That worked really well

PR is ready for review! @dmfalke @bobular @moontrip

In this commit (https://github.com/VEuPathDB/web-eda/pull/771/commits/6af36b32458accacdcefad75f6c94746e1944543) I fixed some unrelated TS warnings in the same files, and in the process I noticed that adding some dependencies to dependency arrays as TS recommends actually breaks the viz. A couple of comments already in the code hinted at that. I only committed the changes that didn't seem to break the code, but if anyone else is more familiar please do review the changes I made.

Apart from the interactive thing discussed on slack, this looks great.
Do you intend the mosaic legend/axis labels to be all bunched up? I think they look better spaced out.
Also, I'm curious what DK's div wrapping suggestion did? @moontrip

@bobular They're bunched up because containerStyles.height = '100%'. I couldn't find a way to determine the plot height in px from non-px values, which is required to know how tall the not-legend can be, so the safe fallback is to not space them out at all

Hi @bobular 👋 I saw you called me 😄
So, when using display:flex, it consists of flex container (so-called parent) and child div(s). It is often obscure which ones should be flex container (parent) and children, especially when using library-based component in React. So, simply put, the  that wraps plotly plot is a sort of declaration/clarification that it is a child of a flex container.

@bobular How about my lastest commit? Does that work for you?

The faceted plot spacing isn't perfect, but this needs to go ahead and get merged. We can add another ticket for the plot spacing if we need to. Merging now.


update PR linter to allow reverts

The "Revert" button in GitHub opens a PR that looks like

Revert "fix(cli): don't build twice on contract changes"

But our linter doesn't like that format because it doesn't match conventional commit formats. We should update that to support reverts PRs of this format.

Hi! I can get this done.

@holic I need some help. I found two ways to go about this problem.
First, ignore the "Revert" word. The code is as follows:
{
  "extends": ["@commitlint/config-conventional"],
  "ignores": [
    (commit) => commit.includes('Revert')
  ]
}

Second, Include it in the rules. The code is as follows:
{
  "extends": ["@commitlint/config-conventional"],
  "rules": {
    "type-enum": [2, "always", ["feat", "fix", "chore", "revert", "docs", "style", "refactor", "version"]]
  }
}

Which code snippet do you believe would be most suitable? Please let me know. Thank you!

Got it. I'll make the PR in a bit.


Support all text stroke options

Support all text rendering modes via the stroke parameter. (Spec)
Examples:
doc.text(35, 25, "Octonyan loves jsPDF", {
    stroke: 0 // Fill text
});

doc.text(35, 25, "Octonyan loves jsPDF", {
    stroke: 1 // Stroke text
});

doc.text(35, 25, "Octonyan loves jsPDF", {
    stroke: 2 // Fill, then stroke text
});

doc.text(35, 25, "Octonyan loves jsPDF", {
    stroke: 3 // Neither fill nor stroke text (invisible).
});

It'd be good if we could pass names into this
{ stroke: 'fill' }

@MrRio
Close this please, as it is modified by PR #1401

Will be part of #1433


move_target for very very small movements doesn't complete.

Bot just does a never ending jig.   Add some extra slop to the 'are we
there yet' test.

Move target is not the place for that code at all, all move target guarantees is that the bot will move towards the target. Not that it won't overshoot. If you've overshot your target, its your job to stop calling move_target

Closing as cleanup. The Physics and pathfinding code is shifting for targeted movement anyway


fby4: sd: Change definitions of APML bus after EVT

Description

Change all definitions of APML bus from 14 to 10 after the EVT stage.

Motivation

Currently, some definitions of APML bus are missing change.

Test plan

Build code: Pass
Get CPU sensor: Pass

Log

Get CPU sensor on EVT SB. root@bmc:~# mfg-tool sensor-display
...
"MB_CPU_PWR_W_85_60": {
"max": 10485.75,
"min": 0.0,
"status": "ok",
"unit": "Watts",
"value": 42.730000000000004
},
...
"MB_CPU_TEMP_C_4_60": {
"critical": {
"high": 91.0
},
"max": 200.0,
"min": 0.0,
"status": "ok",
"unit": "DegreesC",
"value": 66.75
},

Get CPU sensor on DVT SB. root@bmc:~# mfg-tool sensor-display
...
"MB_CPU_PWR_W_85_30": {
"max": 10485.75,
"min": 0.0,
"status": "warning",
"unit": "Watts",
"value": 116.61,
"warning": {
"high": 0.0,
"low": 0.0
}
},
...
"MB_CPU_TEMP_C_4_30": {
"max": 200.0,
"min": 0.0,
"status": "warning",
"unit": "DegreesC",
"value": 46.5,
"warning": {
"high": 0.0,
"low": 0.0
}
},

Hi Jagpal,
Thanks for your comments.
Based on your suggestions to modify the code and force update this branch.
Please help review it again, thank you.


⚠ API - Lens has degraded performance

In 4871cbc, API - Lens ($LENS_API_URL) experienced degraded performance:

HTTP code: 503
Response time: 653 ms

Resolved: API - Lens performance has improved in 475b43e after 6 minutes.


[SILGen] Don't emit a temporary for guaranteed arguments for accessor functions.

If the argument being emitted is an address that will be passed to an @gauranteed_in parameter, we don't need to make a copy because the function will not write to that argument.
This improves SILGen. Even with optimizations, there are some improvements.

@swift-ci please benchmark.

Performance: -O

Regression
OLD
NEW
DELTA
RATIO

Data.hash.Empty
45
50
+11.1%
0.90x

Improvement
OLD
NEW
DELTA
RATIO

RemoveWhereMoveInts
11
7
-36.4%
1.57x

FindString.Loop1.Substring
636
490
-23.0%
1.30x

RandomShuffleLCG2
352
272
-22.7%
1.29x

FindString.Rec3.String
159
123
-22.6%
1.29x

RemoveWhereSwapInts
15
12
-20.0%
1.25x

Dictionary4
233
189
-18.9%
1.23x

FindString.Rec3.Substring
191
155
-18.8%
1.23x

CSVParsing.UTF16
73
63
-13.7%
1.16x (?)

CSVParsing.UTF8
58
54
-6.9%
1.07x (?)

Breadcrumbs.MutatedUTF16ToIdx.Mixed
204
190
-6.9%
1.07x (?)

Code size: -O

Improvement
OLD
NEW
DELTA
RATIO

CSVParsing.o
53667
52283
-2.6%
1.03x

StringMatch.o
5216
5088
-2.5%
1.03x

RemoveWhere.o
14483
14243
-1.7%
1.02x

ReversedCollections.o
8998
8894
-1.2%
1.01x

Performance: -Osize

Regression
OLD
NEW
DELTA
RATIO

SubstringComparable
9
11
+22.2%
0.82x

IterateData
866
995
+14.9%
0.87x (?)

UTF8Decode_InitFromBytes
158
173
+9.5%
0.91x (?)

Improvement
OLD
NEW
DELTA
RATIO

DropFirstAnyCollection
112
72
-35.7%
1.56x

DropWhileAnyCollection
121
81
-33.1%
1.49x

DropFirstAnySeqCRangeIterLazy
139
97
-30.2%
1.43x

DropFirstAnySeqCntRangeLazy
139
97
-30.2%
1.43x

PrefixAnySeqCRangeIterLazy
134
94
-29.9%
1.43x

PrefixAnySeqCntRangeLazy
134
94
-29.9%
1.43x

SuffixAnyCollection
45
32
-28.9%
1.41x

FindString.Loop1.Substring
649
505
-22.2%
1.29x

DropWhileAnyCollectionLazy
155
121
-21.9%
1.28x

PrefixWhileAnyCollection
153
121
-20.9%
1.26x

FindString.Rec3.String
182
146
-19.8%
1.25x (?)

RemoveWhereMoveInts
11
9
-18.2%
1.22x

FindString.Rec3.Substring
215
178
-17.2%
1.21x (?)

RandomShuffleLCG2
384
320
-16.7%
1.20x

PrefixWhileAnyCollectionLazy
110
94
-14.5%
1.17x

PrefixWhileAnySeqCRangeIterLazy
109
94
-13.8%
1.16x

CSVParsing.UTF16
74
64
-13.5%
1.16x

PrefixWhileAnySeqCntRangeLazy
108
94
-13.0%
1.15x

PrefixAnyCollection
101
88
-12.9%
1.15x

FlattenListFlatMap
2780
2461
-11.5%
1.13x (?)

StringMatch
5700
5100
-10.5%
1.12x (?)

Array2D
4832
4384
-9.3%
1.10x (?)

ArrayInClass
960
875
-8.9%
1.10x (?)

PrefixWhileSequence
226
206
-8.8%
1.10x (?)

Breadcrumbs.MutatedUTF16ToIdx.Mixed
206
192
-6.8%
1.07x (?)

Code size: -Osize

Improvement
OLD
NEW
DELTA
RATIO

StringMatch.o
4898
4802
-2.0%
1.02x

CSVParsing.o
49774
49158
-1.2%
1.01x

Performance: -Onone

Improvement
OLD
NEW
DELTA
RATIO

FindString.Loop1.Substring
762
491
-35.6%
1.55x

CSVParsing.UTF8
413
318
-23.0%
1.30x

CSVParsing.UTF16
378
300
-20.6%
1.26x

FindString.Rec3.Substring
539
438
-18.7%
1.23x

CSVParsing.Scalar
448
374
-16.5%
1.20x (?)

FindString.Rec3.String
525
439
-16.4%
1.20x

FindString.Loop1.Array
194087
169190
-12.8%
1.15x (?)

CSVParsing.Char
586
514
-12.3%
1.14x (?)

FindString.Rec3.Array
8368
7393
-11.7%
1.13x

ObjectiveCBridgeStubDateAccess
3521
3125
-11.2%
1.13x (?)

RemoveWhereMoveInts
2641
2355
-10.8%
1.12x (?)

RemoveWhereMoveStrings
3220
2901
-9.9%
1.11x (?)

RemoveWhereSwapInts
5730
5208
-9.1%
1.10x (?)

DataCountMedium
55
50
-9.1%
1.10x (?)

RemoveWhereSwapStrings
6626
6070
-8.4%
1.09x (?)

StringMatch
29100
26800
-7.9%
1.09x (?)

RandomShuffleLCG2
36992
34224
-7.5%
1.08x (?)

Code size: -swiftlibs

How to read the data
The tables contain differences in performance which are larger than 8% and
differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the
regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false
alarms. Unexpected regressions which are marked with '(?)' are probably noise.
If you see regressions which you cannot explain you can try to run the
benchmarks again. If regressions still show up, please consult with the
performance team (@eeckstein).

Hardware Overview
  Model Name: Mac mini
  Model Identifier: Macmini8,1
  Processor Name: 6-Core Intel Core i7
  Processor Speed: 3.2 GHz
  Number of Processors: 1
  Total Number of Cores: 6
  L2 Cache (per Core): 256 KB
  L3 Cache: 12 MB
  Memory: 64 GB

Friendly ping. This is a fairly simple/small patch.

Ideally, we wouldn't generate a copy for any indirectly passed argument with exclusivity.
Unfortunately, non-mutating self is non-exclusive:
rdar://33115142 ([Exclusivity] Consider making non-mutating method calls on value types borrow self)
So, SILGen can't just eliminate the copy. Maybe @rjmccall has more to add.
I assume your patch will break this test case. Sorry we apparently didn't have such a test. Would you care to add it?
struct MyStruct<T> {
  var t: T
  func doItAndGetT(f :()->()) -> T {
    f()
    return t
  }
}

func testNonMutatingSelfWithMutatingCapture<T>(_ x: inout MyStruct<T>, t: T)
-> T {
  return x.doItAndGetT { x.t = t }
}

func test() {
  var s = MyStruct<Int64>(t: 0)
  // This should print "0", not "1", with no exclusivity violation. Kind of crazy.
  print(testNonMutatingSelfWithMutatingCapture(&s, t: 1))
}

test()

@atrick I see what you're saying. For what it's worth, the example you gave still prints 0. It looks like a copy is made inside doItAndGetT. Let me think about this a bit more and try to convince myself you're right (I think you are but I want to keep thinking about it for a bit).
Also, I can't see that radar, unfortunately. I assume it just reiterates what you said in your comment.

I think the nuance here is that this patch only changes arguments of accessor functions (which I didn't mention in the title but should have-- my bad). I think accessor functions have exclusive self, is that known to be true? If so, I think this is a safe change.

Right, my test case won't hit the accessor SILGen path.
No, getter accessors aren't exclusive either. The best I can come up with to break your assumption is this. But I think SILGen will introduce copy x anyway before calling the accessor.
struct MyStruct<T> {
  var t: T
  var f: ()->() = {}
  var prop: T { get {
      f()
      return t
    }
  }
}

func testNonMutatingProp<T>(_ s: MyStruct<T>, t: T) -> T {
  var x = s
  x.f = { x.t = t }
  return x.prop
}

func test() {
  let s = MyStruct<Int64>(t: 0)
  // This should print "0", not "1", with no exclusivity violation. Kind of crazy.
  print(testNonMutatingProp(s, t: 1))
}

test()

The thing I don't like about optimizations that assume some semantics to break other semantics is that they don't compose. Optimization A assumes B holds to violate A, and optimization B assumes A holds to violate A. So if anyone decides to optimize away the box copy of x above with similar cleverness, then things break.
Nevertheless, it seems you might be able to get away with it. I'd be more comfortable with it if you add a test case like above, both after SILGen, and with -O... and if someone else, @slavapestov or @rjmccall should double check whether this SILGen cleverness is really sound.

And, of course, any "unnatural" correctness assumptions you're making here need to be commented.

No, getter accessors aren't exclusive either.

What about implicit accessors? I've updated the condition to only skip arguments given to implicitly defined accessors. The tests will probably fail but, I just want to see what the benchmarks look like (if most of the performance improvements come from implicit accessors then we should just do that if it's safe).

@swift-ci please benchmark

@swift-ci please benchmark

Performance: -O

Regression
OLD
NEW
DELTA
RATIO

DictionaryOfAnyHashableStrings_lookup
3744
4152
+10.9%
0.90x (?)

Improvement
OLD
NEW
DELTA
RATIO

FindString.Loop1.Substring
808
649
-19.7%
1.24x

StringFromLongWholeSubstringGeneric
6
5
-16.7%
1.20x

FindString.Rec3.Substring
271
231
-14.8%
1.17x

UTF8Decode_InitFromData_ascii_as_ascii
786
674
-14.2%
1.17x (?)

FindString.Rec3.String
236
205
-13.1%
1.15x

CSVParsing.UTF16
93
82
-11.8%
1.13x

RemoveWhereSwapInts
24
22
-8.3%
1.09x

EqualSubstringSubstring
42
39
-7.1%
1.08x (?)

EqualSubstringString
42
39
-7.1%
1.08x

LessSubstringSubstring
43
40
-7.0%
1.07x

EqualStringSubstring
43
40
-7.0%
1.07x (?)

LessSubstringSubstringGenericComparable
43
40
-7.0%
1.07x

RandomShuffleLCG2
480
448
-6.7%
1.07x

Code size: -O

Improvement
OLD
NEW
DELTA
RATIO

StringMatch.o
4394
4250
-3.3%
1.03x

CSVParsing.o
53691
52443
-2.3%
1.02x

RemoveWhere.o
14595
14419
-1.2%
1.01x

ReversedCollections.o
8918
8814
-1.2%
1.01x

FindStringNaive.o
8635
8539
-1.1%
1.01x

Performance: -Osize

Regression
OLD
NEW
DELTA
RATIO

StrComplexWalk
4780
5280
+10.5%
0.91x

StringWalk
2520
2720
+7.9%
0.93x (?)

Improvement
OLD
NEW
DELTA
RATIO

FlattenListFlatMap
6603
4192
-36.5%
1.58x (?)

FlattenListLoop
2473
1636
-33.8%
1.51x (?)

FindString.Loop1.Substring
811
634
-21.8%
1.28x

StringFromLongWholeSubstring
5
4
-20.0%
1.25x

StringFromLongWholeSubstringGeneric
6
5
-16.7%
1.20x

FindString.Rec3.Substring
272
229
-15.8%
1.19x

FindString.Rec3.String
235
203
-13.6%
1.16x

CSVParsing.UTF16
93
82
-11.8%
1.13x

DropFirstAnySeqCRangeIterLazy
252
228
-9.5%
1.11x

DropFirstAnySeqCntRangeLazy
252
228
-9.5%
1.11x

DropFirstAnyCollection
182
165
-9.3%
1.10x

LessSubstringSubstring
43
39
-9.3%
1.10x

LessSubstringSubstringGenericComparable
43
39
-9.3%
1.10x

PrefixWhileAnyCollectionLazy
194
176
-9.3%
1.10x

PrefixAnySeqCRangeIterLazy
194
176
-9.3%
1.10x

PrefixAnySeqCntRangeLazy
194
176
-9.3%
1.10x

PrefixWhileAnySeqCRangeIterLazy
194
176
-9.3%
1.10x

PrefixWhileAnySeqCntRangeLazy
194
176
-9.3%
1.10x

SuffixAnyCollection
65
59
-9.2%
1.10x

DropLastAnyCollection
65
59
-9.2%
1.10x

DropFirstAnySeqCRangeIter
199
181
-9.0%
1.10x (?)

DropFirstAnySeqCntRange
199
181
-9.0%
1.10x

PrefixAnyCollection
200
182
-9.0%
1.10x (?)

DropWhileAnyCollection
200
182
-9.0%
1.10x

DropWhileAnyCollectionLazy
271
247
-8.9%
1.10x

RemoveWhereSwapInts
24
22
-8.3%
1.09x

DropWhileAnySeqCRangeIterLazy
305
282
-7.5%
1.08x

DropWhileAnySeqCntRangeLazy
305
282
-7.5%
1.08x

EqualSubstringSubstring
43
40
-7.0%
1.07x

EqualSubstringSubstringGenericEquatable
43
40
-7.0%
1.07x (?)

EqualSubstringString
43
40
-7.0%
1.07x (?)

PrefixWhileAnyCollection
252
235
-6.7%
1.07x

Code size: -Osize

Improvement
OLD
NEW
DELTA
RATIO

CSVParsing.o
51710
50825
-1.7%
1.02x

StringMatch.o
4209
4145
-1.5%
1.02x

FindStringNaive.o
8230
8147
-1.0%
1.01x

Performance: -Onone

Improvement
OLD
NEW
DELTA
RATIO

FindString.Loop1.Substring
988
849
-14.1%
1.16x

StringBuilderWithLongSubstring
3710
3260
-12.1%
1.14x (?)

CSVParsing.UTF8
583
533
-8.6%
1.09x (?)

LessSubstringSubstring
50
46
-8.0%
1.09x (?)

CSVParsing.Char
913
846
-7.3%
1.08x (?)

Code size: -swiftlibs

How to read the data
The tables contain differences in performance which are larger than 8% and
differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the
regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false
alarms. Unexpected regressions which are marked with '(?)' are probably noise.
If you see regressions which you cannot explain you can try to run the
benchmarks again. If regressions still show up, please consult with the
performance team (@eeckstein).

Hardware Overview
  Model Name: Mac Pro
  Model Identifier: MacPro6,1
  Processor Name: 12-Core Intel Xeon E5
  Processor Speed: 2.7 GHz
  Number of Processors: 1
  Total Number of Cores: 12
  L2 Cache (per Core): 256 KB
  L3 Cache: 30 MB
  Memory: 64 GB

No, getter accessors aren't exclusive either.

What about implicit accessors? I've updated the condition to only skip arguments given to implicitly defined accessors. The tests will probably fail but, I just want to see what the benchmarks look like (if most of the performance improvements come from implicit accessors then we should just do that if it's safe).

Implicit accessors can't execute arbitrary code, so I think it's safe to optimize them. This comment is potentially ambiguous

"could introduce a possible exclusivity violation

I would just state clearly that, unlike arbitrary methods which can modify self via a capture, the implicit accessor has no way to modify self, so self is immutable within the call.

@atrick sounds good. Will do.

@atrick sorry for the long delay. I've updated this PR with your suggested changes.

Please update the base branch to main by Oct 5th otherwise the pull request will be closed automatically.

How to change the base branch: (Link)
More detail about the branch update: (Link)

@atrick even though this is a fairly specific optimization, I think there are some solid performance improvements. Any chance you have time to do a re-review?

@swift-ci please benchmark.

Build failed before running benchmark.

@swift-ci please benchmark.

@swift-ci please benchmark.

Performance: -O

Regression
OLD
NEW
DELTA
RATIO

LessSubstringSubstring
21
29
+38.1%
0.72x

EqualSubstringSubstring
21
29
+38.1%
0.72x (?)

EqualSubstringString
21
29
+38.1%
0.72x

LessSubstringSubstringGenericComparable
21
29
+38.1%
0.72x (?)

EqualStringSubstring
22
30
+36.4%
0.73x (?)

EqualSubstringSubstringGenericEquatable
22
29
+31.8%
0.76x (?)

Improvement
OLD
NEW
DELTA
RATIO

FlattenListLoop
1558
1387
-11.0%
1.12x (?)

NormalizedIterator_ascii
75
70
-6.7%
1.07x (?)

Code size: -O
Performance: -Osize

Regression
OLD
NEW
DELTA
RATIO

EqualSubstringSubstring
21
29
+38.1%
0.72x

EqualSubstringSubstringGenericEquatable
21
29
+38.1%
0.72x

EqualSubstringString
21
29
+38.1%
0.72x

LessSubstringSubstringGenericComparable
21
29
+38.1%
0.72x

LessSubstringSubstring
22
29
+31.8%
0.76x

EqualStringSubstring
22
29
+31.8%
0.76x

SuffixCountableRange
6
7
+16.7%
0.86x (?)

StringComparison_longSharedPrefix
326
364
+11.7%
0.90x (?)

Data.hash.Empty
45
50
+11.1%
0.90x (?)

ObjectiveCBridgeStringHash
61
66
+8.2%
0.92x (?)

Improvement
OLD
NEW
DELTA
RATIO

NormalizedIterator_ascii
76
69
-9.2%
1.10x (?)

Code size: -Osize
Performance: -Onone

Regression
OLD
NEW
DELTA
RATIO

ObjectiveCBridgeStringHash
61
67
+9.8%
0.91x (?)

EqualStringSubstring
78
85
+9.0%
0.92x (?)

Improvement
OLD
NEW
DELTA
RATIO

FindString.Loop1.Substring
629
477
-24.2%
1.32x

FindString.Loop1.Array
195024
177630
-8.9%
1.10x (?)

CSVParsing.UTF16
379
348
-8.2%
1.09x (?)

Code size: -swiftlibs

How to read the data
The tables contain differences in performance which are larger than 8% and
differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the
regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false
alarms. Unexpected regressions which are marked with '(?)' are probably noise.
If you see regressions which you cannot explain you can try to run the
benchmarks again. If regressions still show up, please consult with the
performance team (@eeckstein).

Hardware Overview
  Model Name: Mac mini
  Model Identifier: Macmini8,1
  Processor Name: 6-Core Intel Core i7
  Processor Speed: 3.2 GHz
  Number of Processors: 1
  Total Number of Cores: 6
  L2 Cache (per Core): 256 KB
  L3 Cache: 12 MB
  Memory: 64 GB

OK, I'm going to give up on this optimization. Even if I could construct the necessary conditions to make it safe, I doubt it would have a very large performance impact and it would make the codebase more complex.
There might be an extra copy in the load/copy pattern when loading the property, but I think this is a different patch (and that's assuming the optimization can be done at all).


[Bug] Smooth transition to {height: 'auto'}

First of all, thank you for this beautiful animation library!
I just tried to port a navigation menu from React to Solid, which uses Motion (Framer) in the React version and an animation from {height: '0px') to {height: 'auto'} works as expected.
Now that I use Motion for Solid in the new component, this transition is unfortunately no longer animated.
Here is a code sandbox to reproduce: https://codesandbox.io/s/transition-to-auto-f2nyfs?file=/App.tsx
Tested on the newes Version of Edge, Firefox and Safari on Monterey 12.5.1

Hey @mooxl! Although similar APIs, there's no expected feature parity between Framer Motion and the Motion One Solid/Vue apis. Browsers don't normally support this so Framer Motion does some "stuff" to support this feature that I probably won't be bringing over here. If I received a PR that added the functionality in a lightweight enough manner I'd consider putting it in but I'm closing this for now.


Recognize dates when importing data

Context
Please explain here below what you were doing when the issue happened
I was importing a CSV file via the Carto web interface.
Steps to Reproduce
Please break down here below all the needed steps to reproduce the issue

Import a new dataset from file

Current Result
Please describe here below the current result you got
Dates, for example 09/17/1993 00:00:00, were imported as strings.
Expected result
Please describe here below what should be the expected behaviour
It would be very helpful if the column were created as a TIMESTAMP.
Browser and version
What internet browser (Chrome, Firefox, etc) and version was you using and version
n/a
.carto file
Don't forget to rename .carto file to .zip file to be able to upload to github
n/a
Additional info
Please add any information of interest here below

cc @rafatower

Hey @rbrtmrtn thanks for your report.
Where the type guessing takes place is in the underlying CSV GDAL driver we use to import CSV files and many other formats. It is done through the AUTODETECT_TYPE option and IIRC the dates are meant to be in one of these formats to be recognised:

Date (YYYY-MM-DD), Time (HH:MM:SS+nn), DateTime (YYYY-MM-DD HH:MM:SS+nn)

(I think the rails side of things used to have some heurisitics for date/datetime recognisition that we removed in favor of gdal detection. See the Typecaster. Mind that that apporach is much slower than gdal approach)
@saleiva it is up to you whether we should push to support other types as a new feature/enhancement.

@rafatower guessing is a key part of our workflow. I'd love to keep advancing on this, but of course it really depends on the cost. Can we open an issue in the correct repo and keep talking there?

The right repo is this one: https://trac.osgeo.org/gdal
@rouault I tried to create a ticket there but I no longer have TICKET_CREATE privileges. Here's the content of the ticket I wanted to create:
Support more date and datetime formats for AUTODETECT_TYPE option

The `AUTODETECT_TYPE` option of the CSV driver does a great job figuring out the types of the columns of an input CSV file but can be improved by adding more formats to it.

At present and if I'm not mistaken, the algorithm for type detection only supports the ISO 8601 Notation.

Here are the types supported by PostgreSQL:
https://www.postgresql.org/docs/current/static/datatype-datetime.html#DATATYPE-DATETIME-DATE-TABLE

The algorithm could be tweaked to support those formats that do not have ambiguity with other types (integer or float), so that, for instance, the following CSV would recognise the column mydate as of type datetime:
{{{
id,mydate,value
1,09/17/1993 13:20:51,42
2,09/17/1994 13:27:40,43
}}}

I think the code implementing it is around these lines:
https://trac.osgeo.org/gdal/browser/trunk/gdal/ogr/ogrsf_frmts/csv/ogrcsvlayer.cpp?rev=37371#L1160

What do you think? we can keep the discussion about feasibility and estimates off this public repo

@rafatower Are you properly authenticated as 'rtorre' in Trac ? If so, you should have TICKET_CREATE privileges. Supporting more datetime format seems reasonable although that in the above example there might be an ambiguity if it was 02/03/1993 instead. Would it be month day year or day month year ? The link to the postgres doc mentions several modes YMD, DMY, MDY, so perhaps we should have an option to specify this date mode as well in case there are ambiguities ?

Thanks @rafatower @saleiva , makes sense now that the API (or GDAL) is expecting more of a well-known format. I could do a little munging to get those dates into ISO-8601, but just wanted to bring this up as a potential/future enhancement as it would make some of our workflows a bit easier.

@rouault thanks a lot for your comments, some answers in line:

Are you properly authenticated as 'rtorre' in Trac ? If so, you should have TICKET_CREATE privileges.

Yes. Basically I'm experiencing the exact same problem I had the last time: I can log in as rtorre, it let's me fill the new ticket form but when I submit it it returns a 403 Forbidden with the text "TICKET_CREATE privileges are required to perform this operation on Ticket #None. You don't have the required permissions." and I appear to be logged out.

Supporting more datetime format seems reasonable although that in the above example there might be an ambiguity if it was 02/03/1993 instead. Would it be month day year or day month year ? The link to the postgres doc mentions several modes YMD, DMY, MDY, so perhaps we should have an option to specify this date mode as well in case there are ambiguities ?

You're right. This is the most extreme case (from the postgres link above):
01/02/03	January 2, 2003 in MDY mode; February 1, 2003 in DMY mode; February 3, 2001 in YMD mode

@saleiva this kind of ambiguity cannot be solved without making risky assumptions or letting the user add a bit of metadata (format, locale, whatever). I see the following options here:

Leave it as it is and sick to current ISO 8601 (YYYY-MM-DD) (we should improve our docs a little in this regards)
Use ISO 8601 and assume MDY, or the machine locale, or any other configurable date style in the case of ambiguity (in our setups, postgres assumes MDY, and it is used when a column is cast from text to date/datetime).
Let the user add that metadata (format or locale). Or better let the user define the type of the columns and the format of the dates (types of columns are nicely covered by GeoCSV format, not format of dates though).This reminds me of this ticket https://github.com/CartoDB/cartodb/issues/4282

I'd love to hear your input before requesting any enhancement in GDAL.
@rbrtmrtn thanks for the feedback, much appreciated.

Yes. Basically I'm experiencing the exact same problem I had the last time: I can log in as rtorre, it let's me fill the new ticket form but when I submit it it returns a 403 Forbidden with the text "TICKET_CREATE privileges are required to perform this operation on Ticket #None. You don't have the required permissions." and I appear to be logged out.

How did we solve the issue last time ? Can't remember. Anyway I've explictly granted you TICKET_CREATE rights. Hopefully that should work

How did we solve the issue last time ? Can't remember. Anyway I've explictly granted you TICKET_CREATE rights. Hopefully that should work

You created a ticket for me and Sandro fixed it: https://trac.osgeo.org/osgeo/ticket/1745
Also I couldn't post comments in that ticket at the time, so I sent the contents of the comments I wanted to make through mail to you and Sandro, with the subject Re: [OSGeo] #1745: Authenticated user cannot create ticket on GDAL Trac.
I suggest to reopen and keep tracking trac issues there if needed (no pun intended).
I'm not opening any ticket in trac yet, until we figure out the requirements and scope. We can keep the discussion about "high level" (product) requirements here and once that's clear I can write up the requirements for gdal csv driver in a trac ticket.


Chinese characters being clipped on Edge/360Chrome

Attach (recommended) or Link to PDF file here:
1148.pdf
Configuration:

Web browser and its version: Microsoft Edge 42.17134.1.0 / 360Chrome <IP_ADDRESS> (based on Chromium 55.0.2883.87)
Operating system and its version: Windows 10 1803 / Windows 10 1607
PDF.js version: 2.0.493 / 1.9.426
Is a browser extension: No / No

Steps to reproduce the problem:

Open the attached pdf file with Microsoft Edge or 360Chrome browser

What is the expected behavior? (add screenshot)

(Chromium 55.0.2883.87)
What went wrong? (add screenshot)

(Microsoft Edge)

(360Chrome)
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):
N/A

I can workaround this issue by appending <script>pdfjsDistBuildPdf.PDFJS.disableFontFace = true;</script> after `
` in `viewer.html`, seems relates to font rendering.

Web browser and its version: Microsoft Edge 42.17134.1.0 / 360Chrome <IP_ADDRESS> (based on Chromium 55.0.2883.87)

@timvandermeij Given that all other IE Edge issues have now been closed and that we've never claimed to support 360Chrome, combined with the fact that this looks entirely like a platform/browser bug, should this issue just be closed as WONTFIX?


File doesn't uploading, if it is empty

I have rules:
return [             [['docFile'], 'file', 'skipOnEmpty' => false, 'extensions' => 'docx, doc, txt'],  ];
It's OK, if file is not empty. But if it is, Yii2 throws validation error. E.g., if extension of empty file is 'docx', it displays 'Only files with these extensions are allowed: docx, doc, txt.' I found, that FileValidator::validateExtension() return false, cause this conditions fulfills:
if (!in_array($extension, $extensionsByMimeType, true)) {          return false;  }
$mimeType in this case is inode/x-empty.
What can I do with this?

What do you mean by "empty"?

0 bytes size.

Do you really want to allow uploading such files?
mime type of empty file could not be determined since there's no content.

In current project it is not necessary, but what if I am a teacher and need to send just file sctructure (tabs, indents, etc.), in a students portal without any text? In source code I found, that checking MIME-type and ext is in the same function. If they were separated, the problem would disappear. But, maybe, u are right and it is not so great problem, which need resolving... :)

But I think, it is not correct to show extension error, if file is empty. I had to look at Yii core to understand, what problem occurs.

Tabs, indents, etc. means the file has some content and it will be recognized.

You could turn off mime validation if you truly want empty files to be uploaded or add inode/x-empty to the list.
Overall, I don't think it worth handling specially.

By tabs, etc. I meant not chars, but this:

Thanks, understood.