Rename ba2 to ba package

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

Project coverage is 100.00%. Comparing base (8e686fb) to head (3c9cf53).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #649   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           28        28
  Lines         2375      2375
  Branches       343       343
=========================================
  Hits          2375      2375

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


Error during Verify

Error during contract verification:
Error while trying to verify contract: Fail - Unable to verify
zos version: 2.4.2
Smart contract:

Operations:

Hi @euazzo,
I previously had an issue with verify, that I resolved by explicitly compiling with optimizer disabled:
https://github.com/OpenZeppelin/openzeppelin-sdk/issues/1183#issuecomment-521953370
You may also want to upgrade to @openzeppelin/cli.
For support questions it is generally best to ask in the OpenZeppelin Community Forum as then the entire community can help answer your question rather than just those watching the repository:
https://forum.openzeppelin.com/

Hi @abcoathup,
I have tried to disable the optimizer and now it works.
Thank you for the support.


Question: siamMask  can track multi person at same time

select multi ROI?

I would be interested in such a scenario also...


Create example Harness workflow file

This pull request introduces a new codeql-scan.yaml configuration file for setting up a CodeQL analysis workflow in a Harness pipeline. The configuration is tailored for a Python application and includes steps for setting up the environment, downloading the CodeQL bundle, creating a database, analyzing the database, and uploading the results to GitHub.

Is it really necessary to create the virtual environment in Harness? You're not specifying any version of python, so it'll be whatever is on the VM or container, right? Virtual environments are great for development environments where you want to keep your dependencies from colliding with other project dependencies, but if you're running it in a CI platform, it is usually the only thing that runs in that environment.
There's nothing really gained or lost for using a virtual environment in this case, but that might because I am missing something in how Harness works. I was reading the docs, and it seems like Harness works with ephemeral VMs and containers, so I am not sure what benefit there would be for virtual environments.


feat(pubsublite): add reservations samples

Add samples for Pub/Sub Lite reservations

Thanks for adding these samples!


Package is not Download From Github Link in Unity

Step 0: Is this a new bug?
Make sure to check our
troubleshooting
and issues pages before submitting your bug report.
Please delete this section when posting a bug report.
Step 1: Environment
[REQUIRED]

Computer OS: [e.g. Windows, macOS]
Unity Editor Version: [e.g. 2021.3.1f1]
Appodeal Unity Plugin Version: [e.g. 3.0.1]
Bug Repro Rate: [e.g. 100%, 25%]

[OPTIONAL] (if applicable)

Xcode Version: [e.g. 13.3.1]
CocoaPods Version: [e.g. 1.11.3]
Device Model: [e.g. Pixel 6 Pro, iPhone 13]
Device OS Version: [e.g. Android 13, iOS 15.4.1]

Step 2: Describe the bug
A clear and concise description of what the bug is, including device logs, Unity Editor logs, and stack traces if available.
Step 3: How to reproduce
Describe here step by step how to reproduce this bug.
[e.g. 1. Initialize SDK. 2. Call Appodeal.Show(AppodealAdType.Mrec);. 3. See error.]
Step 4: Expected behavior
A clear and concise description of what you expected to happen.
Step 5: Screenshots
If applicable, add screenshots to help explain your problem.
Step 6: Additional context
Add any other context about the problem here.
If you have a downloadable sample project that reproduces the bug you're reporting, you will likely receive a faster response on your issue.

Hi Team
I want Use Your Plugin In unity But I follow Step in your documation copy
link and paste in Unity Package Manager (Install Package From Git URl) not
Working
On Tue, Mar 12, 2024 at 4:09 PM Vladimir @.***> wrote:

Hi @Meet-BVM https://github.com/Meet-BVM,
Please provide more info regarding the issue according to our template
(steps described above).
—
Reply to this email directly, view it on GitHub
https://github.com/appodeal/appodeal-unity-plugin-upm/issues/50#issuecomment-1991330748,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BGOUW7ZMZVBZDUNA35VJHLLYX3LNBAVCNFSM6AAAAABERZMVC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJRGMZTANZUHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

And Also After i Build Game Then Show Me Gradle Error Also Please Guide Me
To Solve it
Thank You
On Tue, Mar 12, 2024 at 5:16 PM Meet Sondagar @.***>
wrote:

Hi Team
I want Use Your Plugin In unity But I follow Step in your documation copy
link and paste in Unity Package Manager (Install Package From Git URl) not
Working
On Tue, Mar 12, 2024 at 4:09 PM Vladimir @.***> wrote:

Hi @Meet-BVM https://github.com/Meet-BVM,
Please provide more info regarding the issue according to our template
(steps described above).
—
Reply to this email directly, view it on GitHub
https://github.com/appodeal/appodeal-unity-plugin-upm/issues/50#issuecomment-1991330748,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BGOUW7ZMZVBZDUNA35VJHLLYX3LNBAVCNFSM6AAAAABERZMVC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJRGMZTANZUHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

And One More Thing I Already Integration in unity But Also Show me Error
Please Check
On Tue, Mar 12, 2024 at 5:16 PM Meet Sondagar @.***>
wrote:

Hi Team
I want Use Your Plugin In unity But I follow Step in your documation copy
link and paste in Unity Package Manager (Install Package From Git URl) not
Working
On Tue, Mar 12, 2024 at 4:09 PM Vladimir @.***> wrote:

Hi @Meet-BVM https://github.com/Meet-BVM,
Please provide more info regarding the issue according to our template
(steps described above).
—
Reply to this email directly, view it on GitHub
https://github.com/appodeal/appodeal-unity-plugin-upm/issues/50#issuecomment-1991330748,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BGOUW7ZMZVBZDUNA35VJHLLYX3LNBAVCNFSM6AAAAABERZMVC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJRGMZTANZUHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

We cannot see attachments in GitHub. Please, try to check troubleshooting pages and provide detailed information according to our template if you still haven't found a solution.
We need detailed information regarding steps to reproduce the issue and the used environment.

Dear Appodeal Team,
I hope this email finds you well. I am writing to confirm our scheduled
AnyDesk session for integrating Appodeal into my Unity project.
Session Date: 13 - 3 - 2024
Session Time: 2:00 PM Indian Standard Time (IST)
I am looking forward to our session and am eager to learn the necessary
steps to seamlessly integrate Appodeal into my Unity project. Please let me
know if there are any preparations I should make beforehand to ensure a
smooth session.
Additionally, if there are any specific materials or resources you
recommend reviewing prior to our session, please do not hesitate to share
them with me.
Thank you very much for your assistance, and I appreciate your time and
expertise in guiding me through this integration process.
Best regards,
Meet

Message ID: <appodeal/appodeal-unity-plugin-upm/issues/50/1992151397@

github.com>

Hello @Meet-BVM,
We do not offer integration sessions. I have to close this issue because you didn't provide the requested information.
Don't hesitate to check our documentation and ask the support team<EMAIL_ADDRESS>for help.
If you found an issue in the SDK, please follow our template during the issue creation.


issue #786 #787 #807 BulkimportJob enhancements

(1) changed to use nano time instead of system.currentmillise when calculating job duration.
(2) Enhanced COSFileBreaker tool to be able to get certain number of distinct FHIR resources from COS object, using the generated files with distinct resource IDs in the multiple javabatch job partitions can avoid the deadlock issue.
(3) added FHIR resource validation support to bulkimportjob.

made some comments throughout.

Iet me refactor the 4/2 cases in my eclipse.


Select active env as fallback, disable remote dbg

If we don't have a default remote controller, then fallback to the active interpreter instead of falling back to a random controller
When debugging against remote kernel, notify user this isn't possible

This partially fixes the issue where you shutdown your remote jupyter server while VS Code is opened & launch IW.
partially because there are some more fixes to come

Codecov Report

Merging #9833 (f6702d7) into main (b649d71) will increase coverage by 0%.
The diff coverage is n/a.

@@         Coverage Diff          @@
##           main   #9833   +/-   ##
====================================
  Coverage    63%     63%
====================================
  Files       203     203
  Lines      9810    9810
  Branches   1556    1556
====================================
+ Hits       6213    6217    +4
+ Misses     3100    3093    -7
- Partials    497     500    +3

Impacted Files
Coverage Δ

src/platform/errors/errorHandler.ts
66% <0%> (-2%)
:arrow_down:

...rc/platform/common/dataScienceSurveyBanner.node.ts
70% <0%> (+5%)
:arrow_up:


Pulsar events have timeline gaps in Windows 10

Hubble 2.4.7 on Windows 10 with no active downloads.
When parsing the event data from the sqlite returner time line gaps between record sets of a variable amount are occurring.
That is the last entry from record "A" may be up to a minute earlier than the first entry in record "B".
And, this seems to vary by the length of the record set. The larger number of events to process the greater the gap.
Suspect that current time is being used instead of last record entry time when reentering the data collection.
(Understand I am a novice and I am only guessing.)

I'm not 100% sure that I understand the question, but this might be expected behavior. Pulsar on windows runs with less frequency than on linux, and I think the events will be timestamped from collection, not from change time. Can you perhaps show some sample data with expected vs actual behavior?

Attached is a tab delimited file that can be opened in Excel. (Did the best I could at parsing the three records.)
In the middle record set you see where I created a new file. That was followed within the time frame of the middle record set with a rename and then a deletion. Neither of which showed up.
To show the gaps I will have to schedule some time to run tests where C:\Users*\AppData\Roaming* is re-enabled.
To elaborate my "sense" of things (gap-wise) The gaps shown between records is quite small in this data-set.
However, when there is a lot of information to gather, parse, format and deliver the gaps seem to enlarge.
This makes me think that when Pulsar kicks off at time x gathers data up to time y then finishes processing at time z it goes back into the event logs starting at time z instead of time y.
More information is in issue #656
Grid_Data.txt

That's a pretty solid hypothesis, actually. This isn't code I wrote but I have vague familiarity with it. You can see where it reads the NTFS journal here: https://github.com/hubblestack/hubble/blob/c0c0598864c9ca183fed2d61ff0e6baa3aedf35c/hubblestack/extmods/modules/win_pulsar.py#L175-L181
In this case, it seems to be keeping track of actual record identifiers (usn?), which would make me think your hypothesis was incorrect. (Identifiers should be independent of time)
However, there's also some file mtime comparisons above those lines around the file being out of date? Perhaps this is where things are going wrong? If pulsar were running less often than that threshold, then it would just reset the next usn as the current usn, which could result in lost data. But that threshold is pretty high so I doubt that's what's going on.
Sorry for my rambling. We recently lost our primary windows dev and he wrote this code. =\

Concerning the gaps. You can see that gaps exist by comparing the gird_data.txt time at around line 47 with the journal.txt data.
This may actual be by design, though I can't think of a reason why to use the presence or absence of "close" to delimit whether a record is kept or trashed.
https://github.com/hubblestack/hubble/blob/c0c0598864c9ca183fed2d61ff0e6baa3aedf35c/hubblestack/extmods/modules/win_pulsar.py#L252
and also at line #272
If I've done this right?
Grid_Data.txt
journal.txt

If I'm reading the journal right, it looks like it fires three events on a rename:
Usn               :<PHONE_NUMBER>4
File name         : F006DD91832A2B34E90C1F99AC25C059FFE5391E
File name length  : 80
Reason            : 0x00001000: Rename: old name
Time stamp        : 6/19/2019 15:27:09
File attributes   : 0x00002020: Archive | Not content indexed
File ID           :<PHONE_NUMBER>00000000650000000173b2
Parent file ID    :<PHONE_NUMBER>000000004100000000076b
Source info       : 0x00000000: *NONE*
Security ID       : 0
Major version     : 3
Minor version     : 0
Record length     : 160

Usn               :<PHONE_NUMBER>8
File name         : 25164
File name length  : 10
Reason            : 0x00002000: Rename: new name
Time stamp        : 6/19/2019 15:27:09
File attributes   : 0x00002020: Archive | Not content indexed
File ID           :<PHONE_NUMBER>00000000650000000173b2
Parent file ID    :<PHONE_NUMBER>00000000e0000000007615
Source info       : 0x00000000: *NONE*
Security ID       : 0
Major version     : 3
Minor version     : 0
Record length     : 88

Usn               :<PHONE_NUMBER>0
File name         : 25164
File name length  : 10
Reason            : 0x80002000: Rename: new name | Close
Time stamp        : 6/19/2019 15:27:09
File attributes   : 0x00002020: Archive | Not content indexed
File ID           :<PHONE_NUMBER>00000000650000000173b2
Parent file ID    :<PHONE_NUMBER>00000000e0000000007615
Source info       : 0x00000000: *NONE*
Security ID       : 0
Major version     : 3
Minor version     : 0
Record length     : 88

It looks like most of the major events do have a | Close on them. The exception is Rename: old name. It doesn't have a | Close. So, I'm guessing that code you linked is filtering out everything that doesn't have a | Close except for the Rename: old name which never has a | Close. Does that sound right? And now that you've dug into this journal stuff a bunch, do you think it's the correct behavior?


PR for issue #85

This should theoretically fail.
Also, sorry for the large file in fixtures, haven't been able to reproduce the problem 100% with other files.
This PR has been opened for https://github.com/OSSystems/compress-tools-rs/issues/85

@DumbMahreeo thanks for looking at this. Could you try to produce a smaller tarball? I'll try to look at the issue.

@otavio unfortunately even though in the past I've managed to actually to this, trying again didn't work, so then only way to reliably reproduce the error is with this bulky file. If I'll manage to reproduce it with a smaller tarball I'll update the PR

Solved in #87.


The zip of origin video data has broken. Is there other download path？

I don't understand what do your mean by 'broken'?
To my best knowledge, the original video data can be download and unzipped.

Sorry for not expressing it clearly last time. I noticed that a certain number of answers of the same video in 'QA.zip'  are all -1, but the answer number are between 0-4 in the other question-answer pairs.

-1 indicate the test QA，we haven't release this part of answers to prevent someone adjust hyper-parameter on test set.You can evaluate the test set in CodaLab.Best wishes！Jiangtong Li在 2023年6月22日，23:01，sdjhshbswp @.***> 写道：
Sorry for not expressing it clearly last time. I noticed that a certain number of answers of the same video in 'QA.zip'  are all -1, but the answer number are between 0-4 in the other question-answer pairs.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>


Henrhoi/json query api

@bratseth @jonmv Lagt inn endringene fra møtet og kommentarer 🙂

LGTM!

Anything more that you want to be changed in this PR?

Now we need doc. That's in vespa-engine/documentation.
I think you need to change search-api.html to say that parameters can be sent either as get parameters or posted as json, and give a json query example + check if search-api-reference needs to mention this (not sure as it mostly documents each parameter).
You should also write a short blog post on this, but perhaps we can wait until after you have created a json alternative for the query (yql) parameter.


[1.0] accordion in modal, the little scrolling problem.

for example:

every item in accordion collapsed, no scroll bar
expand the items to let the content exceed the viewport, the scroll bar does not appear
call .modal('refresh'), the scroll bar appears
collapse every item, the scroll bar disappears
expand the items to let the content exceed the viewport , the scroll bar appears
the scroll bar works expectedly.

I'd like to be in step 6 when initialized when the initial content does not need scrollbars, I tried to call .modal('refresh') after step 1, no effect. The problem is that if I want to be in step 6, I have to be through step 3. Any guide?

I tried to add 'scrolling' class as in 'ui scrolling modal', no difference.

Here is another related problem:

let the scroll bar appear
let the viewport be larger so that the scroll bar disappear
let the content exceed the viewport
The problem is that after step 3, the scroll bar does not appear.

I consider to do .modal('refresh') when it is possible to do something with the scroll bars, but the modal may jump not as expected

I just found 1.0.0 release has been released, and tried it, the scroll bars never appears any more.

Had same problem. as @jlukic suggested Try
$('.ui.accordion').accordion({onOpen: function(){$('.ui.modal').modal('refresh')}}); The modal will refresh and allow scrolling but I do not like the re-positioning effect.. I am not sure if there's a better workaround

Thanks!


[uuf-client] Add a loading animation to the zone until the fragment is rendered

If the network connection is slow, until the fragment is loaded, there is no indication of something is happening. So we need to add a loading animation to the zone until the the fragment is rendered.

UUF Client cannot provide a loading animation as it doesn't know about the UX requirements of the web app. What UUF Client can provide is a callback. UUF Client can get two callbacks onSuccess, onFail (similar to jQuery AJAX) as parameters and invoke those callbacks.


allMmr.js is a valid js module or not?

I didn't saw other js requires allMmr.js.
Function generateJob doesn't have 'mmr' type in options.
Just wonder is this used somewhere?

Files in dev are one-off scripts and not run regularly. I keep them around in case they might come in useful in the future.

Thank you for responding so quickly.I'll close this.


Add head code to prevent Declare JS Vars bug

Tested locally. Passes npm run test-challenges. Closes #7806. Crude fix but it works.

Would this also fix #7890? The code in that issue passes even though a is undefined. This happens when a is previously assigned the value of 7 and that value is stored in memory when tests are run.

@alistermada I couldn't replicate even problem on my local instance so I figured I'd test it on the live site whenever my changes get pushed.

@erictleung So many PR's!! Thanks!


added more scraped data

https://worldofbuzz.com/
https://fiksyenshasha.com/
https://inreallife.my/

wooooooooooh!


compiler limit: object file size cannot exceed 4 GB

✍ Bug Description
Compiling saucer triggers a compilation error on MSVC: error C1605: compiler limit: object file size cannot exceed 4 GB
🔁 Steps to reproduce
Run cmake -B build && cmake --build --config MinSizeRel on Windows, it will error
C:\CodeBlocks\saucer>cmake -B build
-- Building for: Visual Studio 17 2022
-- Selecting Windows SDK version 10.0.22621.0 to target Windows 10.0.19045.
-- The CXX compiler identification is MSVC 19.42.34435.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.42.34433/bin/Hostx64/x64/cl.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- [saucer] Avoiding local packages as 'saucer_prefer_remote' is ON
-- [saucer] Backend is 'Defaut', using WebView2
-- Performing Test has_jthread
-- Performing Test has_jthread - Success
-- Performing Test has_move_only_function
-- Performing Test has_move_only_function - Success
-- Performing Test has_expected
-- Performing Test has_expected - Success
-- CPM: Adding package<EMAIL_ADDRESS>(v3.0 to D:/cpm_cache/lockpp/49c2e18a94651f34aa3dcec6c758680e3259fd94)
-- CPM: Adding package boost_callable_traits@ (boost-1.86.0 to D:/cpm_cache/boost_callable_traits/722bc7f1dc041f67609395e9ccadac415f3a2444)
-- CPM: Adding package<EMAIL_ADDRESS>(v4.3 to D:/cpm_cache/ereignis/445e2961b9e1df570b63142f08e5c72791a8938b)
-- CPM: Adding package<EMAIL_ADDRESS>(11.0.2 to D:/cpm_cache/fmt/491054599cbd63fc844546a7daa753ee63243d36)
-- {fmt} version: 11.0.2
-- Build type:
-- CPM: Adding package<EMAIL_ADDRESS>(v4.0.0 to D:/cpm_cache/glaze/3e0e44e76f40fc7eddc5fc6fea88b5d4c2054c9b)
Glaze is being compiled with AVX2 instructions. Set glaze_ENABLE_AVX2 to OFF if you wish to disable this.
-- Performing Test COMPILER_SUPPORTS_AVX2_FLAG
-- Performing Test COMPILER_SUPPORTS_AVX2_FLAG - Success
-- Performing Test AVX2_CODE_COMPILES
-- Performing Test AVX2_CODE_COMPILES - Success
-- Glaze: using AVX2 intrinsics. Set glaze_ENABLE_AVX2 to OFF to avoid use.
-- CPM: Adding package<EMAIL_ADDRESS>(v3.0 to D:/cpm_cache/flagpp/b83fc8ed44d145696ba52b6dc58f76ce85574080)
-- CPM: Adding package<EMAIL_ADDRESS>(v3.0.0 to D:/cpm_cache/rebind/a6a5e7a56622cfd3720e502a58329ed09d2af830)
-- CPM: Adding package boost_preprocessor@ (boost-1.86.0 to D:/cpm_cache/boost_preprocessor/ba1cddf35d8a75d03588f48fd6046f69a103dd6c)
-- CPM: Adding package<EMAIL_ADDRESS>(v3.0.0 to D:/cpm_cache/poolparty/703b5284b73bc46a2f7894d42591ea4e38487123)
-- [NuGet] Downloading Package: Microsoft.Web.WebView2 [1.0.2592.51]
-- [NuGet] NuGet-CLI not found, downloading...
-- [NuGet] Found at: C:/CodeBlocks/saucer/build/nuget/nuget.exe [<IP_ADDRESS>]
-- Configuring done (51.3s)
-- Generating done (0.2s)
-- Build files have been written to: C:/CodeBlocks/saucer/build

C:\CodeBlocks\saucer>cmake --build build --config MinSizeRel
MSBuild version 17.12.12+1cce77968 for .NET Framework

  1>Checking Build System
  Building Custom Rule D:/cpm_cache/fmt/491054599cbd63fc844546a7daa753ee63243d36/CMakeLists.txt
  format.cc
  os.cc
  Generating Code...
  fmt.vcxproj -> C:\CodeBlocks\saucer\build\_deps\fmt-build\MinSizeRel\fmt.lib
  Building Custom Rule C:/CodeBlocks/saucer/CMakeLists.txt
  app.cpp
  window.cpp
  webview.cpp
  smartview.cpp
  requests.cpp
  serializer.glaze.cpp
  win32.app.cpp
  win32.app.impl.cpp
  win32.desktop.cpp
  win32.icon.cpp
  win32.utils.cpp
  win32.window.cpp
  win32.window.impl.cpp
  wv2.navigation.cpp
  wv2.scheme.cpp
  wv2.webview.cpp
  wv2.webview.impl.cpp
  Generating Code...
C:\CodeBlocks\saucer\src\serializer.glaze.cpp(1,1): error C1605: compiler limit: object file size cannot exceed 4 GB [C:\CodeBlocks\saucer\build\saucer.vcxproj]

❔ Expected behavior
No response
👀 Screenshots
No response
🛸 Saucer Version
master
🖥 Operating System
Windows 10
🧰 Compiler
MSVC 14.42.34433
📦 Environment
WebView2, whatever is the default
🖥 Distribution
No response
✅ I confirm that...

[X] I have collected all the required information and read all the comments in this document
[X] I searched for an existing bug report for this issue
[X] the problem does occur with the reproduction steps I provided
[X] what I described is indeed a problem

This is a MSVC compiler bug triggered by glaze [the default serializer used] (see https://github.com/stephenberry/glaze/issues/1448).
The current workaround would be to either use the latest MSVC compiler preview (should be in a stable release soon) or clang-cl.

As a workaround I'm implementing another serializer backend one can switch to - I plan to make a new release with this in the following days

Happy new year! The new serializer is now implemented in very-experimental and can be used by setting saucer_serializer to "Rflpp" (set(saucer_serializer "Rflpp")


update to reply to channel scenario

Pull Request Test Coverage Report for Build 84964

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 76.25%

Totals

Change from base Build 84935:
0.0%

Covered Lines:
8418

Relevant Lines:
11040

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.5.3


remove erroneous code

This fixes #4 on my machine.

@mjrodgers Is there anything I need to do to get this merged?

Strange, I seem to have not received any notification of this pull request. I will try to look it over and merge (and push a new version) this evening.


[Server] Generate Components for a given Kubernetes Cluster once

<@U026RU3009Y> as one of many users on Playground, this shouldn’t occur for me (only for the first user)
Slack Message

@zakisk I'm afraid doing so is more than I have time for.

Then can you please tell me which api endpoint I check, and all the clues to make me able to get the issue and solution.

The lack of "help wanted" label is intentional, knowing that this isn't easy and requires a contributor with thorough understanding of Meshery.
Yes, I'll grab the area of code / API of concern.

Here's one of the areas of concern: https://github.com/meshery/meshery/pull/8132/files#diff-c9f0fd2985523c81296d5a3b0b745ef02fa9d539a883a799977e0f4cb73f45e1


Unable to import ol/format/MVT

Unable to import ol/format/MVT in rollup project
Getting  error:
Error: 'default' is not exported by node_modules/pbf/dist/pbf.js, imported by node_modules/ol/format/MVT.js

@sunishkumar I am getting the same issue - could you please explain what the solution was or any other relevant details for working around it?


[Bug] Connecting remote pacs as modality with Orthanc

Describe the Bug
I want to connect SANTE PACS SERVER to my Orthanc running in docker container. My basic intention is to use SANTE PACS as modality for Orthanc so that data is available from SANTE to Orthanc PACS.
remote pacs will act as modality(client) and orthanc as server.  You can download it from google link : https://santesoft.com/downloads.html
Run Sante PACS as administrator and set orthanc as peer server

The current behavior
On Orthanc UI http://localhost:8042/  data from sante_pacs should be available on orthanc

The expected behavior
E1126 12:14:37.846266          HTTP-15 OrthancException.cpp:62] Error in the network protocol: DicomAssociation - connecting to AET "SANTE": TCP Initialization Error: Operation now in progress (Timeout)
Connection timeout error
OS
Windows 11
Node version
22
Browser
Chrome

I'm not sure what is SANTE PACS SERVER? Why you need that? isn't Orthanc enough as your server?

I want to access the pacs of lets's say some hospital and access its data within my orthanc server.
I am trying to build functionality i which i can connect to pacs of other system.
So i was trying to make an peer to peer connection using orthanc.
Is there any other way around?

SANTE PACS is online free pacs. I am using SANTE locally to test SANTE server as modality for orthanc to imitate my aforementioned task.

What happened? did you solve it? what is the solution?


Feature request: Make table header row "sticky"

Like #5 but for table header rows. That way, when I scroll down, I don't have to memorize what column is what.

implemented in 4d150a2a723fc7dcd801658c2fa186fe369dfd9a, tested on chrome and safari


Sanketshevkar/revert deps pr

Closes #

Revert update deps PR merge commits
Changes

Flags

Screenshots or Video

Related Issues

Issue #
Pull Request #

Author Checklist

[ ] Ensure you provide a DCO sign-off for your commits using the --signoff option of git commit.
[ ] Vital features and changes captured in unit and/or integration tests
[ ] Commits messages follow AP format
[ ] Extend the documentation, if necessary
[ ] Merging to main from fork:branchname

coverage: 98.762%. remained the same
when pulling 02185017be63eb0f1c0d1a28db9a81a763a0f000 on sanketshevkar:sanketshevkar/revert-deps-pr
into 449af6ce5c334d3fb05818abd9223ea67045f452 on accordproject:main.


Allow Cleaner use with forms=False

The LXML cleaner will strip all form elements by defaults. For my use case, this is quite annoying as radio/check boxes and select fields are quite useful as real-world form elements. In fact, I wonder if explicitly stripping of  and handling the rest as normal tags wouldn't serve the purpose better. Alternatively, making the forms value optional and defaulting to True would work as well for me.

Hmm, where do the <form> elements come from? Do you have users creating forms in rich text editors? What is the specific use case?
We only sanitize HTML entered by users (and staff, of course, but those are users of the CMS); forms don't qualify because most often they also require backend support and so are different anyway. If users should be able to build forms themselves, I use https://github.com/feincms/form_designer
(I'm not necessarily opposed to adding forms, but I don't see the use case yet.)

I don't care about <form> at all, but the same option also filters all <input>, <button> and <select> tags. I do care about certain <input> types and <select>. CKEditor has a plugin for editing them and I use that as part of an editor for common text fragments. The normal users just have the option of inserting such a fragment and ticking the boxes / selecting options. E.g. consider a paper form like:
( ) Choice 1
( ) Choice 2

Representing this as actual <input type="radio"> fields has the advantage that it provides sane space etc.

I see!
Form tags' contents aren't preserved: https://github.com/lxml/lxml/blob/4507da6f8f8e7fd6d68c6b7ec2e37b1b0a7f214f/src/lxml/html/clean.py#L360
Right now the sanitizer does not have a list of tags to kill but only to remove. Otherwise we could just pass forms=True (and maybe also embeds, etc.) and handle everything via our own whitelists...

Fixed by #6.


Big calendar doesn't recognize tasks in notes that are not daily note

Dear Quorafind,
I do not manage to use your excellent plugin with tasks placed outside daily notes. While if I write a task in daily notes it immediately appears on the calendar, when I do the same thing in a normal note the plugin does not seem able to scan and identify it.
Could you please help me to understand how it works with tasks?
Many thanks

Now big calendar treat all tasks in daily notes as default tasks, and in 0.4.0 will add the dataview tasks and so on in to big calendar again.

Thanks for your answer, so it is normal that the big calendar does not recognize tasks in notes that are not daily notes?

No, I think normal tasks work on big Calendar 4.0

Many thanks, I will wait for the next release


NIFI-9181 Prevent unwanted test artifacts in Windows builds

Description of PR
Prevents unwanted test artifacts being added to the repository during Windows builds.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically main)?

[x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
~[ ] Have you written or updated unit tests to verify your changes?~
[x] Have you verified that the full build is successful on JDK 8?
[x] Have you verified that the full build is successful on JDK 11?
[~ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?~
~[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?~
~[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?~
~[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?~

For documentation related changes:

~[ ] Have you ensured that format looks appropriate for the output in which it is rendered?~

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Could be because I was running on Windows 11 (preview), that may have
confused the Assume. As I've only that version of Windows to build from
(normally I build from ubuntu), I don't have any other way to test. I
imagine the GitHub CI run could be leaving the artefact and noone notices
because then things get thrown away?
It was, however, a brand new clone of the repo and first run through of the
tests (after initially building with -DskipTests)
On Mon, 6 Sep 2021, 16:30 exceptionfactory, @.***>
wrote:

@.**** commented on this pull request.
In
nifi-nar-bundles/nifi-groovyx-bundle/nifi-groovyx-processors/src/test/java/org/apache/nifi/processors/groovyx/ExecuteGroovyScriptTest.java
https://github.com/apache/nifi/pull/5355#discussion_r702976979:

@@ -105,7 +105,7 @@ public static void setupBeforeClass() throws Exception {
Assume.assumeTrue("Test only runs on *nix", !SystemUtils.IS_OS_WINDOWS);
FileUtils.copyDirectory(new File("src/test/resources"), new File("target/test/resources"));
//prepare database connection

   System.setProperty("derby.stream.error.file", "target/derby.log");

   System.setProperty("derby.stream.error.file", "target" + File.separator + "derby.log");

According to line 105, this test class does not run on Windows. Is there
some other possible cause of derby.log being created in the
nifi-groovyx-processors directory?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/nifi/pull/5355#pullrequestreview-747319931,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC4YQHUFVNXZ6VOKBARX2MTUATNA7ANCNFSM5DCUTLIQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Could be because I was running on Windows 11 (preview), that may have confused the Assume. As I've only that version of Windows to build from (normally I build from ubuntu), I don't have any other way to test. I imagine the GitHub CI run could be leaving the artefact and noone notices because then things get thrown away? It was, however, a brand new clone of the repo and first run through of the tests (after initially building with -DskipTests)

Thanks for the reply, @ChrisSamo632, that's interesting regarding Windows 11. Using File.separator() seems reasonable either way, so the changes look good.


Supervisor list api with states and health

Fixes #5538
This PR adds a query parameter to the supervisor list API:
/druid/indexer/v1/supervisor?state=true

to enable 'at a glance' status to be cheaply included with a list of supervisors through the state and health provided by #7428. Response is a list of the form:
[{"id":"somesupervisor","state":"RUNNING","detailedState":"RUNNING","healthy":true}...]
Additionally, these fields are also added to
/druid/indexer/v1/supervisor?full

so they are available in addition to the spec.

This fixes https://github.com/apache/incubator-druid/issues/5538

👍


docs: More robust solution to Safari dev cache bug

Description 📖
Safari had an annoying bug where it will ignore changes to CSS files, breaking the developer's hot-reload experience. The Vite Ruby troubleshooting guide recommends moving CSS into the JS entrypoint as a workaround.
However, in Safari 17.5, the problem is now even worse: the bug now affects JS files as well. That means the previously documented workaround is no longer a solution for the entire scope of Safari HMR issues.
Background 📜
Ultimately, the problem is a known bug in Safari where it aggressively caches JS and CSS files that are marked rel=preload.

If a request is preloaded, Safari will always retrieve it from the cache, regardless of the cache headers for that request.

https://bugs.webkit.org/show_bug.cgi?id=193533
The Fix 🔨
Update the Vite Ruby troubleshooting guide with a more robust workaround: disable the rel=preload Link header in development. This completely solves the issue for me.
FWIW, I'm running:
macOS 14.5 (23F79)
Safari 17.5 (196<IP_ADDRESS>.6)

Looks like there is a global way to disable rel=preload that is supported all the way back to Rails 6.1. I'll revise my PR to recommend this approach instead.

Looks great, thanks Matt!


Support for multiple k8s versions

Currently many flags/changes we introduce mean that a certain kube-aws version can only be used with some minimum version of Kubernetes. For example we add a flag to apiserver only supported after some version.
I'd like to start documenting those versions somewhere to be clear what versions we tried and/or endorse for each kube-aws version. I also wonder if/how we could consider properly supporting multiple Kubernetes versions.
I did something basic in https://github.com/kubernetes-incubator/kube-aws/pull/1286 but I think something slightly more configurable would be good, maybe even storing each unit file/bootstrap YAML separately against a version or set of versions and then combining it for the final render.

It also should be applied to the documentation versioning.

Thanks for raising this!
I'm wondering if it would be enough/feasible to support at least two Kubernetes versions for each kube-aws release. For example, k8s v1.9.x and v1.10.x for kube-aws v0.11. Support for v0.11.x(alpha,beta,rc) to kube-aws v0.11 should be done in a manner that doesn't break v1.9.x compatibility.

@mumoshu I think that's more than enough. We could also add an allowed list so at least other versions produce a warning (but do not block).


fix: type incompatibility with Vue 2.7 (fix #1993)

What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the dev branch.
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] All tests are passing: https://github.com/vuejs/vue-test-utils/blob/dev/.github/CONTRIBUTING.md#development-setup
[ ] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:
Fixes #1993

I had to upgrade TypeScript to v4 since the types in vue/types/jsx.d.ts use index signature with template string pattern introduced in TypeScript 4.4.0.
However the tests are now broken and the issue will be resolved in Vue v2.7.9 since https://github.com/vuejs/vue/pull/12727 has been merged.
I'm leaving this PR open until this version is released

2.7.9 has been released. Would be great to get this fix in so we can start using the vue-tsc for type checking 🙃

Vue 2.7.10
The typing issues are still there when using mount or shallowMount @GrtDev

I have a solution for mount & shallowMount but I cant make a PR on this repo becuase Im on mac arm64 and some binareis arent supported.
We can add 2 overrides with the defineComponent api
export declare function mount<V extends Vue> (component: DefineComponent<V>, options?: ThisTypedMountOptions<V>): Wrapper<V>
export declare function shallowMount<V extends Vue> (component: DefineComponent<V>, options?: ThisTypedShallowMountOptions<V>): Wrapper<V>


luis import throws error resource is missing

Tool
Name: [LUIS]
Version: 2.4.0
Describe the bug
I am trying to import a JSON file into an existing empty luis app, it keeps generating the error resource is missing.  The json file does  have entities in it. I tried upgrading the version in the command line or json file but that didn't help.
To Reproduce
Steps to reproduce the behavior:

Export an existing luis model using luis export into a json file
Import that file into a different app

It should just get imported. Which resource is missing. Below is the command I am using:
luis import --appId "44d7xxxx-xxxx-xxxx-8a4b-a01173eef092" --authoringKey "ea1a280b11454b5aaf3e842cd088a477"   --versionId "0.1" -in c:\source\model.json
Any help is appreciated.
Best,
Rakesh

hi @bumblebee333
The resource in question is either a LUIS application, or a version. You need to either specify that you are importing a new application or a new version (to an existing app). For example:
luis import application
OR
luis import version
For you, sounds like you want the latter. Here are more full examples on what you could use:
luis import application --in c:\source\model.json --appName "NewAppNameBeingCreated" --region westus --authoringKey <YOURAUTHORINGKEY>
luis import version --in c:\source\model.json --appId <EXISTINGAPPID> --authoringKey <YOURAUTHORINGKEY>  --versionId "0.2"
Please find more information in the LUIS readme:
https://github.com/Microsoft/botbuilder-tools/blob/master/packages/LUIS/readme.md

Closing this as it should be answered/resolved. Please reopen if still having the issue.


resilio: fix loaOf deprecation warning

Fixes the warning on nixos-rebuild when the resilio service is enabled:

trace: warning: In file nixos/modules/services/networking/resilio.nix
a list is being assigned to the option config.users.groups.
This will soon be an error as type loaOf is deprecated.

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

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

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

Ping @domenkozar @thoughtpolice @cwoac


Demo kdf

Add demo code for PBKDF2 using SHA256 and SCRYPT.
Fixing #14107 and #14108.
Test vectors from RFC 7914.

Merged, thanks for the review.


High CPU usage with v0.0.7

We observed a huge increase in CPU usage between version v0.0.6 and v0.0.7 using the following config:
    # Logs from systemd-journal for interesting services.
    <source>
      type systemd
      filters [{ "_SYSTEMD_UNIT": "docker.service" }]
      pos_file /var/log/gcp-journald-docker.pos
      read_from_head true
      tag docker
    </source>
    <source>
      type systemd
      filters [{ "_SYSTEMD_UNIT": "kubelet.service" }]
      pos_file /var/log/gcp-journald-kubelet.pos
      read_from_head true
      tag kubelet
    </source>

It looks like there was only a single commit between those versions: https://github.com/reevoo/fluent-plugin-systemd/commit/bcbd53ed42b85df5e8ec9b42410bf43a4d0c2683
See https://github.com/kubernetes/kubernetes/issues/42515 for more background on how the issue manifested in our setup.
I'm happy to provide more details or repro steps if it would help.

Thanks for the report @timstclair I will take a look and hopefully get a fix out in a few hours

Also found this today. Looking at bbf9333, wouldn't journal.wait(1_000_000) work just as well as the sleep 1?

It would, but the issue is we are now monitoring the responses to journal.wait in order to get notifications of when the journal has been rotated. I spent a few hours trying to work out a solution that would:
a) fix the issue
b) not cause the journal rotation bug to re-occur
c) not cause the automated tests to become much more complicated
As we are using the timer helper in the mainline branch and don't have to deal with this stuff directly this seems like the simplest solution for now, that didn't involve huge changes to the code / tests.
Feel free to have a go at doing something better though, I am happy to accept a contribution :)

@timstclair I have just pushed version 0.0.8, it would be great if you would able to test this version in your environment?

I confirmed I'm not seeing the issue with 0.0.8.  Thanks!

I am experiencing this issue with 0.3.0. However, we do exports hundreds of log entries per second. Syslog exporter seems to cope just fine.   journald-upload (which we are using currently for log aggregation) doesnt mind either. but this plugin ends up using 100% CPU

I did a strace in one of our live systems. and 99% of the time it's calling the futex syscall

Hi @arianvp this is not the same bug since we replaced the wait code with a fluentd timer a while ago.
Could you open a new issue with the exact versions of fluentd + systemd you are using...


[Portable] Extensions not loading on second window

VSCode Version: 1.25.1 Portable
OS Version: Windows 10 Build 17134

Steps to Reproduce:

Open one folder with VS Code from File Explorer
Open second folder with VS Code from File Explorer

The 1st window has all the extensions enabled, while the second doesn't. When switching on the developer console I got the following message when reloading the window:
no standard startup: not a new window
Does this issue occur when all extensions are disabled?: Yes/No
The problem is with extensions so I'm not disabling them ;)

@jlanza how do you get steps 1 and 2 to work? You have a portable install, i.e. one that installs with unzip but you use context menu actions in Window's File Explorer to open folders in VS Code. How did you setup the context menu actions?

I have the system configured manually. I have used this configuration when there wasn't an official VSCode version and I've been using --user-data-dir "userdata" --extensions-dir "extensions". At that moment VSCode was not my main IDE but now it is so I am properly configuring it ;)
@echo off
SET vscodePath=VSCODE_EXE_PATH

rem add it for all file types
@reg add "HKEY_CLASSES_ROOT\*\shell\Open with VS Code"         /t REG_SZ /v "" /d "Open with VS Code"   /f
@reg add "HKEY_CLASSES_ROOT\*\shell\Open with VS Code"         /t REG_EXPAND_SZ /v "Icon" /d "%vscodePath%,0" /f
@reg add "HKEY_CLASSES_ROOT\*\shell\Open with VS Code\command" /t REG_SZ /v "" /d "%vscodePath% \"%%1\"" /f

rem add it for folders
@reg add "HKEY_CLASSES_ROOT\Folder\shell\Open with VS Code"         /t REG_SZ /v "" /d "Open with VS Code"   /f
@reg add "HKEY_CLASSES_ROOT\Folder\shell\Open with VS Code"         /t REG_EXPAND_SZ /v "Icon" /d "%vscodePath%,0" /f
@reg add "HKEY_CLASSES_ROOT\Folder\shell\Open with VS Code\command" /t REG_SZ /v "" /d "%vscodePath% \"%%1\"" /f

rem add it for inside a folder (background)
@reg add "HKEY_CLASSES_ROOT\Directory\Background\shell\Open with VS Code"         /t REG_SZ /v "" /d "Open with VS Code"   /f
@reg add "HKEY_CLASSES_ROOT\Directory\Background\shell\Open with VS Code"         /t REG_EXPAND_SZ /v "Icon" /d "%vscodePath%,0" /f
@reg add "HKEY_CLASSES_ROOT\Directory\Background\shell\Open with VS Code\command" /t REG_SZ /v "" /d "%vscodePath% \"%%V\"" /f

I have noticed that if I open a VSCode window and then File->New Window the extensions are properly loaded. Is there anyway I can set the registry entries to open a new window instead of a new instance of VSCode.

I think I found the error.... it was my fault :( I still have the --extension and --user-data arguments on the command line I defined in the registry.
Sorry for the inconveniences. I'm closing and will reopen in case I found something strange.


Added GDP Calculator

Fixes Issue🛠

Closes #1117
Description👨💻

Added GDP calculator which uses the Expenditure approach for calculating GDP.

Type of change📄

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

How this has been tested✅

Deployed and tested using Vercel.
Checklist✅

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added demonstration in the form of GIF/video file
[x] I am an Open Source Contributor

Screenshots/GIF📷

Video Preview

Pls rename your folder to GDP-Calculator, and make the changes accordingly by making the new commits in this same PR!
Also add README.md file for the calculator in your folder.
Do the changes in this same PR, don't close this!! @AnandK-pm

Rename your folder correctly, C should be capital @AnandK-pm

Can you please check now ??


Distinct Statistics shows only 50 rows max

@stoch what does the invalid tag mean ? is this not a bug ?

False alarm. Issue closed.


Short-circuit tags

It would be nice if tags such as .and and .or would short-circuit and not parse extra tags when not necessary.
For example
<server.flag[check_if_ten_entities_are_looking_at_y_value_78].exists.and[<server.worlds.parse[entities].combine.parse[cursor_on].filter[y.equals[78]].size.is[or_more].than[10]>]>

is slightly inefficient when the flag doesn't exist because of the extra parsing.
For now, there are workarounds available using tern for these two operations but it is obviously less clear
For and: <tern[false].pass[<expensive_tag>].fail[false]>
For or: <tern[true].pass[true].fail[<expensive_tag>]>

done via https://github.com/DenizenScript/Denizen-Core/commit/1f3e75c0e01172cfab982a5c60b5d0e8a2bb8bc9


The v9 is for Brianna Ghey

On 11 February 2023, Brianna Ghey, a 16-year-old British transgender girl from Birchwood in Warrington, Cheshire, England, was killed in Culcheth Linear Park in Culcheth, Warrington. Two accused teenagers, a boy and a girl both aged 15, are in police custody, having been charged with murder four days after the incident. A motive has not been established and police are investigating "all lines of inquiry", including investigating the killing as a possible hate crime

https://en.wikipedia.org/wiki/Killing_of_Brianna_Ghey
Closes #820

🚀  v9.0.0-beta1 released, tag beta

🚀  v9.0.0-beta2 released, tag beta

🚀  v9.0.0-beta3 released, tag beta

Now I wanna do a cleanup and refactoring of Endpoint and remove createApiResponse()

🚀 v9.0.0-beta4 released, tag beta


Fix build error with gcc 4.9.2

GCC 4.9.2 errors out:
test/rsa_test.c:349:5: error: 'key' may be used uninitialized in this function [-Werror=maybe-uninitialized]
     RSA_free(key);

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

Isn't this already fixed by #14204?

Isn't this already fixed by #14204?

Looks like it, yes.

Isn't this already fixed by #14204?

Yes, thank you @levitte ! I didn't see that PR... I just knew my builds were breaking!

Yes, thank you @levitte ! I didn't see that PR... I just knew my builds were breaking!

It was a pretty rapid affair after I stumbled upon it, so I can see how that flew under anyone's radar.


Update detects code.exe instances from other users with seperate install folders

Two users on the same Windows machine each with their own version of VS Code installed in different folders.
Both users run VS Code, the update now button is pressed by one user and that user closes his VS Code to finish update.
Error message pops up saying that VS Code is still running, although all instances of that user's VS Code are terminated.
Confirmed that the each user's instances all originate from their own user's install folder.
Expected Results:
Users in multiple user environment with separate install folders can update normally, by checking only for running instances of code.exe that originate from the respective install location.

Is there any progress on this? Is there an ETA for when this will be fixed?

The problem still exists, and it is also still annoying. Especially in connection with terminal server installations, it makes the daily work very unpleasant, because there are a lot of updates, and that always leads to this conflict. It is a pity that Microsoft has not developed a solution for this for 2 years now.

Copying from my duplicate issue: (https://github.com/microsoft/vscode/issues/128266)

This is quite annoying as I need to close/reopen VSCode multiple times in a day, and this happens every time I close VSCode. It also blocks me from opening VSCode until it finishes failing to update. I recommend that this either fails silently, or only try once per day. I don't think interrupting my coworkers to close their IDE is a good solution.

I was able to work around this issue with the setting from the following documentation, but I set it to "manual": https://code.visualstudio.com/docs/supporting/FAQ#_how-do-i-opt-out-of-vs-code-autoupdates

To modify the update mode, go to File > Preferences > Settings (macOS: Code > Preferences > Settings), search for update mode and change the setting to none.
If you use the JSON editor for your settings, add the following line:
"update.mode": "none"

This issue was incredibly difficult to find, and similar issues are difficult to find too, because everyone who reports it specifies a different part of the error message. So to improve this issue's visibility:
---------------------------
Visual Studio Code
---------------------------
There was an error while attempting to kill any running Code.exe processes:

Failed to open process: Access is denied.

Please verify there are no Visual Studio Code processes still executing.
---------------------------
Retry   Cancel
---------------------------

And just to make sure this will not be forgotten... can I somewhere vote this up?


Speedup syncing and listing content

In the current implementation of syncing pod, directories and files, we sync one item at a time. So we get metadata of the items one by one making the sync time longer.
To reduce it, we will introduce a queue to process data. This means we will put items in the queue and start n number of workers to get item metadata. Depending on the mode, n will change. Therefore, while running on Server mode, we will assign less number workers to each user. Similarly in Solo mode we assign more workers, as the fairOS instance will be running for a single user.
fairOS has a directory object that keeps the metadata of all dirs and files cached after it is loaded from bee.
So it makes sence to add the SyncManager to the Directory class.
We can use https://github.com/plexsysio/taskmanager for SyncManager.
SyncManager will work on SyncTasks roughly described below
type SyncTask struct {
    d *Directory
    path string
}

func NewSyncTask(d *Directory, path string) *SyncTask {
    return &{
        d: d,
        path: path,
    }
}

func (st *SyncTask) Execute() {
    st.d.file.LoadFileMeta(st.path)
}

In SyncDirectory we will create SyncTask for each file and push them into SyncManager and wait for all the files to sync, then return.
This will speed up the syncing process as the loading is concurrent.
In directory ls, rather than syncing all items in the directory, we will allow pagination. This will be good for UX.

sync manager added in edef403f60719cf359625599c17e90010a5224fd


RFC: Validation

I am investigating adding validation support to Endpoints. I'd love some feedback!
First, a high level overview of Endpoints (example implementation here). Second, please read this exchange between @ashleygwilliams  and @bmac.
Endpoints.Application
A container for your API. All resources are registered with it, and all route handlers for your API should be created using it. This is mainly for making it possible to generate self-documentation. Something in the Endpoints stack needs to be aware of every resource/route created in the API. Further down the road, this could be used to do all sorts of magical convention-based stuff like creating admin interfaces, interactive API documentation, etc.
For a more comprehensive explanation, see the README.
Endpoints.Source
This is a thin wrapper for any ORM. Typically you will never interact with a Source directly. It presents a standardized, callback-based API that can communicate with Endpoints.Controller. There is currently only one implementation: Endpoints.BookshelfSource.
Currently, this does NOT support interop with Bookshelf's built in lifecycle hooks for validation, but it will. Validations like "does this email already exist in the database" should happen here. All ORMs provide support for this--those APIs will be normalized here.
For a more comprehensive explanation, see the README.
Endpoints.Controller
This provides methods for generating CRUD request handling functions. Each controller is associated with a single Source instance. The API is very simple, providing create, read, update, & destroy methods, each of which can be configured with an options object.
For a more comprehensive explanation, see the README.

Option One: No Route Validation Support + Source#model validation
In this model, Endpoints is agnostic to any request validation, instead deferring to the user to provide their own solution. For implementors using hapi, this will be fine, as hapi has robust support for dealing with validation on routes (some interception of these validations will likely need to occur so that the error format can be made json-api compliant). For implementors using express-like http servers, request validation would probably occur in a middleware before the endpoints handler was called, with something like this:
var controller = new Endpoints.Controller({
  source: new Endpoints.BookshelfSource({
    model: require('path/to/bookshelf/model')
  })
});

app.post('/resource', [
  controller.myValidationMiddleware,
  controller.create()
]);

This option makes it difficult to support robust automatic documentation because there is no standard/declarative way to specify how a request should be validated.
Option Two: Route Validation Support In Controller + Source#model validation
In this model, Endpoints provides hooks for validation in a similar fashion to Hapi. You can customize how the route handling function is specified by using a validate hook. For implementer using express, this might be great, if they want to use it. They might want to stick with their own middleware solution as well. For implementors using hapi, this is redundant, and could possibly be ignored.
var controller = new Endpoints.Controller({
  source: new Endpoints.BookshelfSource({
    model: require('path/to/bookshelf/model')
  })
});
app.get(controller.create({
  method: 'customCreateMethod',
  validate: function (request) {
    // do whatever sync operation you want to do here
    // manual checking, use [joi], etc
    // throw with errors? return errors?
  }
});

Depending on how the validate hooks were defined, this could be used for self-documentation.
Option Three: All Validation in Endpoints
In this scenario, Endpoints takes responsibility for both request validation and data validation. No matter which type of Source you use, the underlying model is dumb. Data validation that previously occurred on the model now occurs in the source. Route validation happens as described in option two. This gives us lots of control (and responsibility), but makes it so that all interactions with the models (even internal ones) probably need to be routed through their source. I think it's clear this is a terrible idea, but I'm including it just so we are all aware this sort of thing is possible.
var controller = new Endpoints.Controller({
  source: new Endpoints.BookshelfSource({
    model: require('path/to/bookshelf/model'),
    validate: function (params, cb) {
      // do data validations here, can be async
    }
  })
});
app.get(controller.create({
  method: 'customCreateMethod',
  validate: function (request) {
    // do whatever sync operation you want to do here
    // manual checking, use [joi], etc
    // throw with errors? return errors?
  }
});

I like #2 because you have more options on how you'd like to handle things.   Is there any sort of security benefit from having the validation support in the controller?

Hmm, I don't think so, I think we'd have the same level of security regardless of where the validation happens.
Maybe I'm not understanding what you mean by security benefit?

Lol, no, you're not confused, I am just confused about why # 2 would be preferred to # 1 other than giving people more options.

Looks like number 2 has the most flexibility, allowing route validation, but not requiring it. Makes sense to me, unless I'm missing something.

I'm just reticent to add features that are basically re-implementing what hapi already provides. Maybe Endpoints the framework should drop support for express? You'd still be able to use Endpoints.Controller and Endpoints.Source with express.

Initially I was in favor of option 2 because of the flexibility if appears to offer.
However, the more I think about it the more I am in favor of option 1. @tkellen mentioned that he thinks hapi developers will be unlikely to use the validate hook and will instead be likely to favor hapi's built in config.validate object. I suspect express end up sounding like a similar story. Most of the existing express validator libraries are designed to be plugged in as middleware (express-validator, express-validation, express-validate, express-joi).
The one benefit for a validate in the public api seems to be the potential for self-documentation. I'm a little suspicious of how easy it will be to generate this documentation if the api is just a function for the validate hook.

I'm pretty sure I'm going with #1.  Going to attempt a proof of concept switching us from express to hapi today. I expect it'll be pretty easy, save for dealing with authentication.

It's decided.  Definitely going to go with option 1. Users of Endpoints can use the routeBuilder hook to turn any kind of declarative configuration into what they need. For people using express that will look like integration with some middleware as routes are generated, for people using hapi--they can just use the existing hooks.


[SR-2503] Implement subtraction for CharacterSet

This is a PR that parallels apple/swift#5201.
Execution is interrupted when CharacterSet.subtracting(_:) is invoked. The underlying reason is that subtracting(_:) is a default implementation that calls symmetricDifference(_:), but CharacterSet.symmetricDifference(_:) invokes subtracting(_:). This PR implements CharacterSet.subtracting(_:) and CharacterSet.subtract(_:).
A new test has been added for this code; however, as reported in SR-2509, CharacterSet.union(_:) is not currently working in corelibs-foundation, so the test must be disabled in this repo until that entirely separate issue is resolved.
Resolves SR-2503.

I didn't mention it in the other review, but thanks for finding/fixing this @xwu.

Seems like we should get to the bottom of SR-2509 before merging this, so we can have the test enabled.

@parkera I agree that'd be preferable.
SR-2509 is tricky, though, because it's probably related to another bug (SR-2510) about NSMutableCharacterSet in corelibs-foundation. It seems that it's generally borked: try to invert an instance of NSMutableCharacterSet and execution is interrupted; ask if "abc" is a superset of "cde" and you get true. I'm not getting anywhere fixing that one.

Well at least that one is easy to repro. Looks like we are failing to initialize the right callback into Swift. I'll take a closer look.

I talked about this with @phausler and he has a fix for 2510 planned soon.

@parkera With the new year and SR-2509/10 being still unresolved, any thoughts on maybe merging this first? While it's true the tests would stay disabled, arguably there's value in aligning with changes already merged in the apple/swift repo?

Sure.

@swift-ci test and merge

I have some changes for CFCharacterSet pending which will help with some extant struct CharacterSet bugs as well.


🌱 Add IP reuse e2e tests

Add e2e test for IP reuse feature

/test-ubuntu-e2e-integration-main

/test-ubuntu-e2e-integration-main

/test-ubuntu-e2e-integration-main

/test-ubuntu-e2e-integration-main

/test-ubuntu-e2e-integration-main

/test-ubuntu-e2e-integration-main

/test-ubuntu-e2e-integration-main

Interesting CI failure:
[38;5;9m[FAILED] Expected success, but got an error:
      <*meta.NoKindMatchError | 0xc000d57940>:
      no matches for kind "IPPool" in version "ipam.metal3.io/v1alpha1"
      {
          GroupKind: {
              Group: "ipam.metal3.io",
              Kind: "IPPool",
          },
          SearchedVersions: ["v1alpha1"],
      }

What comes to my mind now is, can we try with updating the kubebuilder markers for ippool object the same way as here:
https://github.com/metal3-io/cluster-api-provider-metal3/blob/main/controllers/metal3datatemplate_controller.go#L57-L58?

Interesting CI failure:
[38;5;9m[FAILED] Expected success, but got an error:
      <*meta.NoKindMatchError | 0xc000d57940>:
      no matches for kind "IPPool" in version "ipam.metal3.io/v1alpha1"
      {
          GroupKind: {
              Group: "ipam.metal3.io",
              Kind: "IPPool",
          },
          SearchedVersions: ["v1alpha1"],
      }�[0m

What comes to my mind now is, can we try with updating the kubebuilder markers for ippool object the same way as here: https://github.com/metal3-io/cluster-api-provider-metal3/blob/main/controllers/metal3datatemplate_controller.go#L57-L58?
Edit: found the exactly what we want to try: https://github.com/metal3-io/ip-address-manager/blob/6570a96b8eee4df1be4f1e0362f79081f8b8dcd4/controllers/ippool_controller.go#L53-L54

Yes this should be enough rbac verbs.
Interestingly with a simple local test I was able to list ippools from capm3 e2e test without an issue so still not sure what is wrong in the PR

Yes this should be enough rbac verbs.

I don't get that, I was asking to add them to m3datetemplate controller since rules for ippool is missing there, can you please update the PR with ^ suggestion and run the tests again?

Yes this should be enough rbac verbs.

I don't get that, I was asking to add them to m3datetemplate controller since rules for ippool is missing there, can you please update the PR with ^ suggestion and run the tests again?

I tested that here https://github.com/metal3-io/cluster-api-provider-metal3/pull/931 but did not help

Yes this should be enough rbac verbs.

I don't get that, I was asking to add them to m3datetemplate controller since rules for ippool is missing there, can you please update the PR with ^ suggestion and run the tests again?

I tested that here #931 but did not help

Yeah, but seems you missed to run "make generate" there to have that rules applied in the crds (proper rbac rules for ippools)..

Yes this should be enough rbac verbs.

I don't get that, I was asking to add them to m3datetemplate controller since rules for ippool is missing there, can you please update the PR with ^ suggestion and run the tests again?

I tested that here #931 but did not help

Yeah, but seems you missed to run "make generate" there to have that rules applied in the crds (proper rbac rules for ippools)..

Oops yeah! but same though

/keep-test-ubuntu-integration-release-1.4

/keep-test-ubuntu-integration-release-1-4

/test-ubuntu-e2e-integration-main

/test-ubuntu-e2e-integration-main

/test-ubuntu-e2e-integration-main

/keep-test-ubuntu-e2e-integration-main

/keep-test-ubuntu-e2e-feature-main

/keep-test-ubuntu-e2e-feature-main

/keep-test-ubuntu-e2e-feature-main

/keep-test-ubuntu-e2e-feature-main

/keep-test-ubuntu-e2e-feature-main

/keep-test-ubuntu-e2e-feature-main

/keep-test-ubuntu-e2e-feature-main

/keep-test-ubuntu-e2e-feature-main

/keep-test-ubuntu-e2e-feature-main

/keep-test-ubuntu-e2e-feature-main

/keep-test-ubuntu-e2e-feature-main

/keep-test-ubuntu-e2e-feature-main

/keep-test-ubuntu-e2e-feature-main

/keep-test-ubuntu-e2e-feature-main

/keep-test-ubuntu-e2e-feature-main

/keep-test-ubuntu-e2e-feature-main

/test-ubuntu-e2e-feature-main

/test-ubuntu-e2e-feature-main

/assign @furkatgofurov7

/test-ubuntu-e2e-feature-main

/assign @furkatgofurov7

@mboukhalfa thanks for cc, will take a look ASAP

/test-ubuntu-integration-main
/test-centos-e2e-integration-main

/test-ubuntu-e2e-feature-main

/test-ubuntu-e2e-feature-main

/test-ubuntu-e2e-feature-main

/test-ubuntu-e2e-feature-main

/test-ubuntu-integration-main
/test-centos-e2e-integration-main

/test-ubuntu-e2e-feature-main

/keep-test-ubuntu-e2e-feature-main

/test-ubuntu-e2e-feature-main

/test-ubuntu-e2e-feature-main

/lgtm


Using cloud config to serve certificate and log4j in simple way, such as:

Can we use cloud config to serve certificate and log4j in simple way, such as:
server.ssl.key-store=cloudconfig:/{app}/{profile}/{label}/{path}?
or
server.ssl.key-store=cloudconfig-server-url-w-cred:/{app}/{profile}/{label}/{path}?
Thanks a lot,

Not currently

Then is there any sample code to pull certificate and log.properties and inject into spring boot code.
Thanks a lot,

I don't know of any


No images in distributed package

need to include (at least) the recOrder logo and colormap
likely a quick build fix

It wasn't completely obvious how to include data files from outside the main recOrder/recOrder package directory.
I ended up adding docs/__init__.py to make setuptools think that docs is a package so that it will be included in the wheel.
This discussion gives an alternative solution---move necessary images+data in the recOrder folder:
https://stackoverflow.com/questions/4519127/setuptools-package-data-folder-location
This way is easier than changing the directory structure, but it has the slight disadvantage of making > import docs work. Setuptools already thinks examples is a package, though, so > import examples also works (for better or worse).


snpEff database address is incorrect

When installing a genome, bcbio is trying to grab the snpEff database from the wrong address... snpEff should be v4_1, not v4_12.
Updating rn5 genome resources configuration
Installing snpEff database Rnor_5.0.78 in /packages/bcbio/v0.8.8/genomes/Rnorvegicus/rn5/snpeff
Traceback (most recent call last):
  File "/packages/bcbio/v0.8.8/anaconda/bin/bcbio_nextgen.py", line 207, in <module>
    install.upgrade_bcbio(kwargs["args"])
  File "/packages/bcbio/v0.8.8/anaconda/lib/python2.7/site-packages/bcbio/install.py", line 98, in upgrade_bcbio
    upgrade_bcbio_data(args, REMOTES)
  File "/packages/bcbio/v0.8.8/anaconda/lib/python2.7/site-packages/bcbio/install.py", line 260, in upgrade_bcbio_data
    _upgrade_snpeff_data(s["fabricrc_overrides"]["galaxy_home"], args, remotes)
  File "/packages/bcbio/v0.8.8/anaconda/lib/python2.7/site-packages/bcbio/install.py", line 319, in _upgrade_snpeff_data
    subprocess.check_call(["wget", "-c", "-O", dl_file, dl_url])
  File "/packages/bcbio/v0.8.8/anaconda/lib/python2.7/subprocess.py", line 540, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['wget', '-c', '-O', 'snpEff_v4_12_Rnor_5.0.78.zip', 'http://downloads.sourceforge.net/project/snpeff/databases/v4_12/snpEff_v4_12_Rnor_5.0.78.zip']' returned non-zero exit status 8
Checking required dependencies
Installing isolated base python installation
Installing bcbio-nextgen
Installing data and third party dependencies
Traceback (most recent call last):
  File "bcbio_nextgen_install.py", line 275, in <module>
    main(parser.parse_args(), sys.argv[1:])
  File "bcbio_nextgen_install.py", line 46, in main
    subprocess.check_call([bcbio["bcbio_nextgen.py"], "upgrade"] + _clean_args(sys_argv, args, bcbio))
  File "/packages/python/python-2.7.10/lib/python2.7/subprocess.py", line 540, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/packages/bcbio/v0.8.8/anaconda/bin/bcbio_nextgen.py', 'upgrade', '--tooldir=.', '--isolate', '--genomes', 'rn5', '--aligners', 'star', '--data']' returned non-zero exit status 1

It looks like bcbio might build the web address from the version number in brew-packages.yaml...
snpeff:
  name: snpeff
  version: 4.1l_2

A recent commit in homebrew-science adds a revision number (2) in the snpEff recipe, which might be getting pulled into bcbio and breaking things.
Hope I got somewhere close to diagnosing this... I'll leave the fix to the brains of the operation.

Matt;
Thanks much for the heads up and the detailed investigation. You're right that we weren't handling the revisions in brew correctly here. I pushed a fix to cloudbiolinux to correctly write version manifests without revisions, so if you do a:
bcbio_nextgen.py upgrade --tools

you should then be able to run a data upgrade cleanly. Sorry about the problem and thanks again for the report.


Guess or configure primary key

Part of:

#1

By default, uses id as primary key if that column exists. But you can also configure the primary key in a file called tablename.config.json or tablename.config.yaml (or .yml) which specifies pk: name-of-column.

I implemented the first version of id guessing here: https://github.com/datasette/datasette-build/blob/bb6a4ef885c1fa3c6c9bafae140974293462758f/datasette_build/cli.py#L33-L39


Allow void return from ControlledEditorOnChange

Thank you for opening this PR.
I have a note about this change you have made. I think instead of undefined | void we can just write void. So, the whole line should look like this:
) => string | void;
Thank you!

Thank you for opening this PR.
I have a note about this change you have made. I think instead of undefined | void we can just write void. So, the whole line should look like this:
) => string | void;
Thank you!

totally agree 👍

@chaseholdren I just publish the new version (1.2.2) with your change.


platforms / env: AnsibleUndefinedVariable: 'dict object' has no attribute 'iteritems'"

Issue Type

Bug report

Molecule and Ansible details
$ ansible --version && molecule --version
ansible 2.8.3
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/xavier/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/xavier/.local/lib/python3.7/site-packages/ansible
  executable location = /home/xavier/.local/bin/ansible
  python version = 3.7.3 (default, Apr  3 2019, 05:39:12) [GCC 8.3.0]
molecule, version 2.20.2

Molecule installation method (one of):

pip3

Ansible installation method (one of):

pip3

Desired Behavior
molecule.yml:
platforms:
  - name: instance
    image: centos:7
    env:
      foo: bar

I expect foo=bar to be passed during Docker build. Used to work for a long time.
Actual Behaviour
env seems to not work at all, whatever the variable type and value. Always crashes:
TASK [Create Dockerfiles from image names] *************************************
    task path: /home/xavier/.local/lib/python3.7/site-packages/molecule/provisioner/ansible/playbooks/docker/create.yml:21
    <<IP_ADDRESS>> ESTABLISH LOCAL CONNECTION FOR USER: xavier
    <<IP_ADDRESS>> EXEC /bin/sh -c 'echo ~xavier && sleep 0'
    <<IP_ADDRESS>> EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo /home/xavier/.ansible/tmp/ansible-tmp-1564143768.866613-11304981205851 `" && echo ansible-tmp-1564143768.866613-11304981205851="` echo /home/xavier/.ansible/tmp/ansible-tmp-1564143768.866613-11304981205851 `" ) && sleep 0'
    <<IP_ADDRESS>> EXEC /bin/sh -c 'rm -f -r /home/xavier/.ansible/tmp/ansible-tmp-1564143768.866613-11304981205851/ > /dev/null 2>&1 && sleep 0'
    failed: [localhost] (item={'name': 'instance', 'image': 'centos:7', 'env': {'foo': 'bar'}}) => {
        "ansible_loop_var": "item",
        "changed": false,
        "item": {
            "env": {
                "foo": "bar"
            },
            "image": "centos:7",
            "name": "instance"
        },
        "msg": "AnsibleUndefinedVariable: 'dict object' has no attribute 'iteritems'"
    }

Apparently the problem does not occur using Python2:
ansible 2.8.3
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/home/xavier/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /home/xavier/.local/lib/python2.7/site-packages/ansible
  executable location = /home/xavier/.local/bin/ansible
  python version = 2.7.13 (default, Sep 26 2018, 18:42:22) [GCC 6.3.0 20170516]
molecule, version 2.20.2

There is no iteritems in molecule codebase.

@ssbarnea can you please be more specific before closing the issue?
I don't even know what you are talking about.
Do you mean it's related to Ansible ?

My goal is to inject http_proxy environment settings.

Nevermind, just found the iteritems in the custom Dockerfile.j2 I'm using.
Seems like it's not working with python3, I will investigate.

iteritems is a python2-only dict method. It is very rare that iteritems is needed instead of just items, which exists in both python2 and python3 with basically the same interface (for key, value in dict_object.items(): ...).

This is what I did, I was not aware of the iteritems in the Dockerfile but after replacing with items it works. Good thing if it's python2 and python3 compatible, thank you @seandst


Top activity bar items overflow early

demonstration:
https://github.com/drcika/apc-extension/assets/58827198/dc871862-1ac4-416a-a08c-7cb2070ca387

Looks like this even happens after uninstalling the extension


[4.9.x] Upgrade Jackson Databind and Guava

Purpose
Upgrade Jackson to 2.15.2
Upgrade Guava to 32.1.1.jre

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6414416273

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/6414416273
Status: success


crypto: Add Poseidon and expose Base64UrlUnpadded

experimental feature

closing since this is merged to openid-zkp branch


Allow deletion of pods etc even if network policy got deleted

[!warning]
This is a public repository, ensure not to disclose:

[ ] personal data beyond what is necessary for interacting with this pull request, nor
[ ] business confidential information, such as customer names.

What kind of PR is this?
Required: Mark one of the following that is applicable:

[ ] kind/feature
[x] kind/improvement
[ ] kind/deprecation
[ ] kind/documentation
[ ] kind/clean-up
[ ] kind/bug
[ ] kind/other

Optional: Mark one or more of the following that are applicable:

[!important]
Breaking changes should be marked kind/admin-change or kind/dev-change depending on type
Critical security fixes should be marked with kind/security

[ ] kind/admin-change
[ ] kind/dev-change
[ ] kind/security
[ ] kind/adr

What does this PR do / why do we need this PR?

...

Fixes #

Information to reviewers

Checklist

[ ] Proper commit message prefix on all commits

Change checks:

[x] The change is transparent
[ ] The change is disruptive
[x] The change requires no migration steps
[ ] The change requires migration steps
[ ] The change upgrades CRDs

Metrics checks:

[ ] The metrics are still exposed and present in Grafana after the change
[ ] The metrics names didn't change (Grafana dashboards and Prometheus alerts are not affected)
[ ] The metrics names did change (Grafana dashboards and Prometheus alerts were fixed)

Logs checks:

[ ] The logs do not show any errors after the change

Pod Security Policy checks:

[ ] Any changed pod is covered by Pod Security Admission
[ ] Any changed pod is covered by Gatekeeper Pod Security Policies
[ ] The change does not cause any pods to be blocked by Pod Security Admission or Policies

Network Policy checks:

[ ] Any changed pod is covered by Network Policies
[ ] The change does not cause any dropped packets in the NetworkPolicy Dashboard

Audit checks:

[ ] The change does not cause any unnecessary Kubernetes audit events
[ ] The change requires changes to Kubernetes audit policy

Falco checks:

[ ] The change does not cause any alerts to be generated by Falco

Bug checks:

[ ] The bug fix is covered by regression tests

Config checks:

[ ] The schema was updated

Closing since unable to reproduce #2073


Some questions about the evalution metrics

Hi,
I notice that you used a buffer of 4 pixels in your evaluations in your paper. And I noticed that there is function called "relaxed_f1". However, I find you do not use the  "relaxed_f1"  function in your main training or test stage (i.e., train_mtl.py).
So my question is that the results reported in your paper used "the bufffer evalution" or not? It confused me.

Thanks @henanjun for raising this question. I used the buffer size of 4 as mentioned in the paper, however, I specifically used the "realxed_f1" function to compute the metrics on validation set after training is completed using the best saved model. There are two IoU (relaxed and accurate) metrics are reported and relaxed uses buffer of 4 pixels while accurate IOU is simple pixel based.
I hope it helps!
Regards
Anil

I see, Thank you very much for your kind reply.

Closing this issue as you are able to find the solution. Thanks!


⚠ Bofrost.lu has degraded performance

In fbeef06, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 881 ms

Resolved: Bofrost.lu performance has improved in ffd5a9d.


cmd/compile: simple generics are not inlined

What version of Go are you using (go version)?

1.19

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
amd64/windows
Even the simplest one-line generic helpers are not inlined, which essentially kills the generic-based modularization approach. The compiler fails to inline and then strength-reduce the resulting code and generates the most generic variant instead. Not only will it severely impact performance, if the helper is called from the inner loop, but can blossom with all sorts of myths regarding Go generics, preventing their further adoption. The latter suggests the issue is more critical than it might initially appear.

What did you do?
package testcase

type C interface { ~uint | ~uint32 | ~uint64 }

func isAligned[T C](x, y T) bool {
    return x % y == 0
}

func foo(x uint) bool {
    return isAligned(x, 64)
}

Compile with:
go tool compile -S t1.go
What did you expect to see?
TEST $3f, AX
What did you see instead?
caller:
      0x0014 00020 (t1.go:11) MOVQ    AX, BX
      0x0017 00023 (t1.go:11) MOVL    $64, CX
      0x001c 00028 (t1.go:11) LEAQ    <unlinkable>..dict.isAligned[uint](SB), AX
      0x0023 00035 (t1.go:11) PCDATA  $1, $0
      0x0023 00035 (t1.go:11) CALL    <unlinkable>.isAligned[go.shape.uint_0](SB)
      0x0028 00040 (t1.go:11) MOVQ    24(SP), BP
      0x002d 00045 (t1.go:11) ADDQ    $32, SP
      0x0031 00049 (t1.go:11) RET

callee:
<unlinkable>.isAligned[go.shape.uint_0] STEXT dupok nosplit size=46 args=0x18 locals=0x8 funcid=0x0 align=0x0
        0x0000 00000 (t1.go:6)  TEXT    <unlinkable>.isAligned[go.shape.uint_0](SB), DUPOK|NOSPLIT|ABIInternal, $8-24
        0x0000 00000 (t1.go:6)  SUBQ    $8, SP
        0x0004 00004 (t1.go:6)  MOVQ    BP, (SP)
        0x0008 00008 (t1.go:6)  LEAQ    (SP), BP
        0x000c 00012 (t1.go:6)  FUNCDATA        $0, gclocals·g2BeySu+wFnoycgXfElmcg==(SB)
        0x000c 00012 (t1.go:6)  FUNCDATA        $1, gclocals·g2BeySu+wFnoycgXfElmcg==(SB)
        0x000c 00012 (t1.go:6)  FUNCDATA        $5, <unlinkable>.isAligned[go.shape.uint_0].arginfo1(SB)
        0x000c 00012 (t1.go:6)  FUNCDATA        $6, <unlinkable>.isAligned[go.shape.uint_0].argliveinfo(SB)
        0x000c 00012 (t1.go:6)  PCDATA  $3, $1
        0x000c 00012 (t1.go:7)  TESTQ   CX, CX
        0x000f 00015 (t1.go:7)  JEQ     40
        0x0011 00017 (t1.go:7)  MOVQ    BX, AX
        0x0014 00020 (t1.go:7)  XORL    DX, DX
        0x0016 00022 (t1.go:7)  DIVQ    CX
        0x0019 00025 (t1.go:7)  TESTQ   DX, DX
        0x001c 00028 (t1.go:7)  SETEQ   AL
        0x001f 00031 (t1.go:7)  MOVQ    (SP), BP
        0x0023 00035 (t1.go:7)  ADDQ    $8, SP
        0x0027 00039 (t1.go:7)  RET
        0x0028 00040 (t1.go:7)  PCDATA  $1, $0
        0x0028 00040 (t1.go:7)  CALL    runtime.panicdivide(SB)

This will be fixed with unified IR. Inlining in this case was disabled to fix a bug. See CL 395854. Closing as a dup of that issue.

Actually, not closed, but will be fixed soon.

I think the issue is we severely limited inlining after having so many issues with inlining, shape types, and the non-unified frontend: https://github.com/golang/go/blob/57d05512feebed4fbe1e7a19305c8722a4ac627f/src/cmd/compile/internal/inline/inl.go#L725
I'll look into getting this working with unified IR after CL 421821 lands. I think that code probably just needs to be skipped for unified IR mode.


doc(basics): add section 'Multiple validation controllers'

Based on a use case I worked out for myself, which I imagine people might find interesting. It illustrates some advanced techniques for controlling validation on a fine-grained level.
For a working example of the template and view model see https://gist.run/?id=c533e53e62cb348cc96aa9445bae612a

thanks!


New release for LoRA support?

Hello! I would like to make a simple feature request: a new release so that LoRA support is available through the precompiled wheels. In v0.2.2 this feature is not supported yet. Those updated wheels would be very useful for https://github.com/oobabooga/text-generation-webui/.

+1

Hi, really sorry for the long waiting. I will release 0.3.0 late of this week. 🥂

This feature would be much appreciated.

You mean the gptq not supported lora-ed model now ?


Consistency on postback payload behavior: text.greetings, text.help, and case sensitivity

Currently postbacks are not compared to DEFAULT_GREETINGS_REGEX to see if the payload matches a greeting. The DEFAULT_GREETINGS_REGEX covers get started and thus, with the current implementation, the SDK could diverge on behaviors for the postback that comes from a user tapping the Get Started button versus typing get started. The payload for the Get Started button can be changed by the application developer, but this does not alleviate the possibilty of different behavior on a postback versus text message.
Additionally, the same issue exists for text.help, which is a common item in persistent menus. Clicking on persistent menus trigger postbacks and this a menu item with help as the payload will be emitted as text instead of text.help.
Lastly, postback payloads are also not converted to lower case, which is inconsistent with how text messages are treated when their content is emitted with events.
These can be broken out into separate issues if need be but I thought it useful to start with a larger scoped issue that covers the inconsistencies observed when debugging a bot using the SDK.
CC for comment: @crccheck @nosamanuel @tswicegood

Can this be solved at the regex level by using the case-insensitive flag (/i)?
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp

The default regex for both greetings and help have the case-insensitive flag:
const DEFAULT_GREETINGS_REGEX = /^(get started|good(morning|afternoon)|hello|hey|hi|hola|what's up)/i;
const DEFAULT_HELP_REGEX = /^help\b/i;

The part about case-sensitivity in the summary refers to this:
this.emit('text', {event, senderId, session, source: 'text', text: text.toLowerCase().trim()});

The .toLowerCase().trim() modification establishes the expectation that string comparisons in the application for the text event can make certain assumptions:
messenger.on('text', ({senderId, text, source}) => {
  if (text === 'something') { // don't need any toLowerCase or trim here!
    return messenger.send(senderId, new Text('a reply'));
  }
  if (text === 'something else') { // or here!
    return messenger.send(senderId, new Text('another reply'));
  }
});

However, with postbacks, this expectation falls over:
onPostback(event, session) {
  this.emit('text', {event, senderId, session, source: 'postback', text: payload});
}

Essentially what I'm proposing is to bring that in line, simply:
onPostback(event, session) {
  this.emit('text', {event, senderId, session, source: 'postback', text: payload.text.toLowerCase().trim()});
}

The payload is set by the application developer, so this could be over-engineering, but it creates consistency.

this is something I've been thinking about. I think there should be a distinction between the simplified text and the original text Right now, I'm essentially doing text.toLowerCase().toLowerCase() because I'm not sure what comes in. This reminds me of the api talk where he said if you have to constantly look at the docs, something is wrong.
So perhaps there should be a text and inputText or parsedText or cleanText

I was looking at https://data.world/data-society/the-simpsons-by-the-data and they used "name" and "normalized_name", which sounds good to me. So there could be text and normalizedText

Going to take a crack at this with the input from the comments.

would cause backward compatibility issues

This is where semver is iffy. I agree it's a backwards incompatible change. But in practice, we were applying .toLowerCase twice to everything anyways because it was ambiguous what text meant. At this stage, I'd rather not worry too much about preserving backwards compatibility. I added backwards compatibility to #49 at the cost of some tech debt, but mostly because the change was additive.
For naming things, that's just always painful. I'm not even sold on text normalizedText originalText. I think we should get more opinions. The one opinion I have is that since text is the shortest, that should be the variable that's the most "useful".

Ok, I think I have a decent solution in the works. I'll get a PR going and we can see what we prefer.


Manager Ready: Remove Time Selection From Job Poster Creation Form

Description
Time selection should be removed from the open/close dates on the job poster builder to avoid confusion. This means that jobs should open and close at the start/end of the day respectively in PST.
Criteria

[ ] Job poster creation forms no longer have time select inputs for open/close dates.
[ ] Job posters open at 12:00AM PST on the date selected.
[ ] Job posters close at 11:59PM PST on the date selected.
[ ] This task requires a unit test.

Resolved by #841


update for v1.9.0-up.1 release

Signed-off-by: Steven Borrelli<EMAIL_ADDRESS>Description of your changes
Update makefile for v1.9.0-up.1 release.
I have:

[ ] Read and followed Upbound's contribution process.
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR, as appropriate.

How has this code been tested

@stevendborrelli You'll need to run make reviewable to get it all re-generated.


parse error with bang patterns

{-# LANGUAGE BangPatterns #-}

module Foo where

data Foo = Foo { foo :: Int }

bar :: Foo -> Int
bar Foo { foo = !i } = i

foo.hs:8:17: Error: Parse error
Found:
    bar :: Foo -> Int
  > bar Foo { foo = !i } = i

1 hint
% hlint --version                                                                                ~/trader/rc.200
HLint v2.1.12, (C) Neil Mitchell 2006-2018

I guess that's also haskell-src-exts

Yep, very likely haskell-src-exts too.

Confirmed works with HEAD that doesn't use HSE for parsing, so fixed in the next release.