Copying gets broken on long text

I was testing nvim-osc52 with nvim (0.7.2) and patched konsole with with osc52 support, and noticed that copying gets truncated on certain input (konsole patch here).
For example, copying osc52.lua itself from the source code, produces only this when pasting:
-------------------- VARIABLES -----------------------------
local base64 = require('base64')
local fmt = string.format
local commands = {
  operator = {block = "`[\\<C-v>`]y", char = "`[

I'm not sure if it's an issue with plugin or with konsole's handling of osc52.

Author of the konsole patch here, and I'm pretty sure this issue has nothing to do with the way nvim-osc52 works, but with konsole's internal buffer for such OSC operations.

It seems an issue from Konsole indeed. I'm closing the issue for now, feel free to re-open it if it turns out it's the plugin's fault.


Arduino Due and ProgressBar does not work on J0 because of math.h

Hello,
There seems to be a conflict between the math.h and the Nextion Lib.
J0 and J1 are allready in use. I am not sure if this problem also exists for other devices.
CompProgressBar:22: error: 'NexProgressBar j0' redeclared as different kind of symbol
In file included from C:\Users\xxx\AppData\Roaming\Arduino15\packages\arduino\hardware\sam\1.6.4\cores\arduino/Arduino.h:26:0,
from C:\Users\xxx\Documents\Arduino\libraries\ITEADLIB_Arduino_Nextion/Nextion.h:20,
from CompProgressBar.ino:20:
c:\users\xxx\appdata\roaming\arduino15\packages\arduino\tools\arm-none-eabi-gcc\4.8.3-2014q1\arm-none-eabi\include\math.h:471:15: error: previous declaration of 'double j0(double)'
extern double j0 _PARAMS((double));
^
CompProgressBar.ino: In function 'void buttonUpPopCallback(void*)':
CompProgressBar:38: error: request for member 'getValue' in 'j0', which is of non-class type 'double(double)'
CompProgressBar:46: error: request for member 'setValue' in 'j0', which is of non-class type 'double(double)'
CompProgressBar.ino: In function 'void buttonDownPopCallback(void*)':
CompProgressBar:54: error: request for member 'getValue' in 'j0', which is of non-class type 'double(double)'
CompProgressBar:61: error: request for member 'setValue' in 'j0', which is of non-class type 'double(double)'
Multiple libraries were found for "Nextion.h"
Used: C:\Users\xxx\Documents\Arduino\libraries\ITEADLIB_Arduino_Nextion
Not used: C:\Users\xxx\Documents\Arduino\libraries\nextion-bborncr
'NexProgressBar j0' redeclared as different kind of symbol

Hello thomas0815,
I recieved my Nextion 2.8 display today and the conflict is still present. I confirm the conflict on a Teensy 3.x and Teensy LC.
In the specific math.h files for the ARM processors (same for the Ardino Due) the labels j0 and j1 are already in use and cause the redeclaration and following  errors.
My solution was to rename j0 to something != j0 (in the ino sketch and hmi file) and everythin worked.
Greetz


JTAppleDayViewCell not working in swift 3?

I'm trying to create a english calendar along with nepali calendar to display within a single cell using.
But still no use ... Urgent help
Regards,
Sunil Gurung

What version of the library are you using?
JTAppleDayViewCell exists in version 6 and below.
JTAppleDayCell exists in version 7 and above.
Have you looked at the video tutorials? -> https://cocoapods.org/pods/JTAppleCalendar

I'm using Version 7 but it stated as use of Undefined Types

Here is your file
calendarIOS-master.zip

issue resolved. closing


Mouse Position Example and Multiple Targets for Action State Driver

Problem
A lot of games require mouse position as an input in some way.  However, in games with multiple windows or screens, this is not a straight forward input to get, and how to transform from screen space to world space, or if you need to at all, is a bit dependent on the use case, so it's hard to have a one size fits all axis type.
Solution
This crates great design makes it relatively easy to drive a mouse position action from an ActionStateDriver, it just needs a quick example to get the ball rolling for how you can add the capability to your own game, which this PR adds.
This PR also makes a small change to ActionStateDriver to let it drive multiple entities instead of just one.  I think this will be a big win long term for games that will need mouse data, or other driven action data, on many entities.

Change log please :) Also the promised example appears to be missing?


Publish updates 06/28 for Autoruns, Process Explorer, RAMMap & Sysmon

Docs Build status updates of commit 8183c89:
:warning: Validation status: warnings

File
Status
Preview URL
Details

bread/toc.json
:warning:Warning

Details

toc.json
:warning:Warning

Details

sysinternals/downloads/autoruns.md
:white_check_mark:Succeeded
View

sysinternals/downloads/process-explorer.md
:white_check_mark:Succeeded
View

sysinternals/downloads/rammap.md
:white_check_mark:Succeeded
View

sysinternals/downloads/sysinternals-suite.md
:white_check_mark:Succeeded
View

sysinternals/downloads/sysmon.md
:white_check_mark:Succeeded
View

bread/toc.json

[Warning] Error happen when converting bread/toc.json to Pdf. Details: Could not find a part of the path 'T:\efin\bread\toc.json'.

toc.json

[Warning] Error happen when converting toc.json to Pdf. Details: Could not find file 'T:\efin\toc.json'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Accept spinning terribly

Found this trying to run some benchmarks, that wound up killing the performance... when closing a Listener, the underlying goroutine can get stuck in an infinite loop.
The problem is that we never tracked the closed state, which means that when the underlying socket is closed, we get back an error that we did not expect.

This was fixed in 6e0bb6bafcb907c955816badf543c5120c042b5c -- accidentally used the wrong bug ID in the commit comments.


BUG FormAction title property cannot be set if useButtonTag is false

I was trying to set a title property for my form action, then noticed the code wouldn't let you set it at all unless using a button tag.
This changes description to override title, but only if description is set to a non-empty value.

Created on wrong branch; Will just re-create sorry.


etcd-agent: fix data-dir path check

Need one more dash to match 'data-dir' flag.

@xiang90 Tested this and worked. After this merge, I will investigate hash discrepancy.

lgtm


[Immunization] Calculate DUE dates for dependent Tasks

Context

For FHIR core to implement correct Tasks dependencies we need to update the tasks' DUE dates in case the dependent tasks have a time constraint depending on the pre-requisite tasks.

Implementation

[ ] Write a function that does the following.

[ ] Accepts a task/tasks as input.
[ ] Determine its dependent tasks. This scoping piece defines how to identify the dependencies.
[ ] Updates the dependent tasks Task. executionPeriod.start to account for the constraint interval defined here.

[ ] This discussion explains how to update the dependent DUE dates

Acceptance criteria

[ ] The dependent tasks' DUE dates should be updated based on the pre-requisite date of administration.

Scoping details

https://github.com/opensrp/fhircore/discussions/2111

This was blocked due to some comments on the codes. It's now updated. @SebaMutuku feel free to add an LOE and implementation plan.

@dubdabasoduba @f-odhiambo this is the implemetation plan

refractor transitionTaskTo in class FhirCarePlanGenerator to a generic name (This is to centralize tasks logic in one place)
Create an extension function to handle this issue.

@dubdabasoduba  that's found it in this discussion https://github.com/opensrp/fhircore/discussions/2142

@dubdabasoduba do you mind sharing a sample generated task json file that I can use to test with?
Be sure to include task.input.value in days because the type  is listOf(Task.ParameterComponet)

@SebaMutuku The Task.input.value can hold different values https://www.hl7.org/fhir/task.html.

Thanks @dubdabasoduba

@SebaMutuku You are right. It's on the Observation created after extraction. Please feel free to leave comments on the discussion if something isn't clear.

@SebaMutuku After some discussion, this implementation will change. The date of Administration will now be stored on the Immunization resource. It will be stored on the Immunization.occurrenceDatetime attribute.
Please review this discussion item https://github.com/opensrp/fhircore/discussions/2142

@pld I will re-open this ticket since it's failing the engineering QA

How to replicate the bug.

Run the code on main pointing to the eCBIS preview server or the stage server using the configs here
Create a child of age 2 yrs.
The immunization schedule should be generated and immunization task statuses updated correctly.
The OPV 0 will have a due date in the year 2021.
Complete the tasks then wait for the OPV 1 task to become due.
OPV 1 dues date should be updated to 28 days after the Immunization date entered while completing the OPV 0 task.

e.g if OPV 0 was completed on 21/06/2022 then the OPV 1 due date should be updated to 19/07/2022

From our investigation with @SebaMutuku and @dubdabasoduba
The problem
The code for updating the due dates of the dependent Tasks is never called. Reason: the condition for hasPartOf is evaluating to false on this function ResourceExtension#updateDependentTaskDueDate. The code was implemented with the interpretation that the part-of property should be extracted from the parent resource. The property should be retrieved from the dependent Task instead.
The solution

Do a reverse search for Tasks that are part of the current task loaded on QuestionnaireSubmission. The filter would look like below:

 fhirEngine.search<Task> {
      filter(
          referenceParameter = ReferenceClientParam("part-of"),
          { value = id.asReference(ResourceType.Task).reference })
    }

Update the logic for modifying the dependent Tasks due date against the result of the query above

Still, work in progress


Make buildlog highlighting more helpful

/kind enhancement
What this PR does / why we need it:
Make buildlog highlighting more helpful by using regexes that match commonly used patterns in this github org (e.g. ginkgo failure output)

/lgtm


add sequence id to external processor's processing request

Description:
In order to properly reassemble streamed request and response bodies, we could add a sequential identifier than can be used to recreate the full payload in the correct order.
An EPS might defer processing and queue requests to reassemble them later. The EPS can use the request id and time to tag requests, but there is no guarantee that this would be effective in reassembling a payload due to network latency or the actual processing time of the request.
The sequence id could be added to the processing request or the body. Though perhaps adding it to the processing request might be useful for other things.

/cc @gbrail @snowp

That's an interesting idea. Would it mean, for example, that we'd add a counter to each "ProcessingRequest" that ext_proc sends to the external processor? That would not be difficult.
However, are you imagining that the processor would send back responses that used the same counter, allowing out-of-order reassembly of streamed payloads in the Envoy proxy? I don't think that'd work, because it'd require that the Envoy proxy hold the entire message body in memory, and in that case you're better off using the "BUFFERED" processing mode anyway.

i'm only thinking of the processing request. adding it to the processing response would not scale for the reason you mentioned.
i also thought that adding hints about the request body byte offsets may be useful as well if the information is available. adding the sequence id would basically provide ordering, and the assumption would be that we can recreate the body by appending the bytes in that order.

Is it possible that all you need is an "offset" in the message that we send
with each body chunk? That would be easy to calculate and also would solve
your problem I think.
On Tue, Nov 16, 2021 at 6:57 PM Marcos Mendez @.***>
wrote:

i'm only thinking of the processing request. adding it to the processing
response would not scale for the reason you mentioned.
i also thought that adding hints about the request body byte offsets may
be useful as well if the information is available. adding the sequence id
would basically provide ordering, and the assumption would be that we can
recreate the body by appending the bytes in that order.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/envoyproxy/envoy/issues/18905#issuecomment-971128544,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAD7I25ZJ3TDDWNTRLSTNELUMMK3DANCNFSM5HMOSUAA
.
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.

if there is an offset for the request and response body in the processing request, that would solve recreating the request and response body. it can also be a little bit tricky to determine when a request is done, though is there is an end of stream, i thought the sequence id would basically help with that. do the same for the response. what do you think?
processing request w/ request id seq 1 -> request headers
processing request w/ request id seq 2 -> request body offset 0
processing request w/ request id seq 3 -> request body offset 1024
processing request w/ request id seq 4 -> request body offset 2048 (end of stream)
processing request w/ request id seq 5 -> request trailers
processing request w/ request id seq 6 -> response headers
processing request w/ request id seq 7 -> response body offset 0 (end of stream)
processing request w/ request id seq 8 -> response trailers

any comments/updates on this issue @gbrail ?

@gbrail can we reopen this?


Content: [Support] Analysis of Slack messages

Follow on from #1282
Analysis of the Slack Q&As to determine application of the information collected:
What content can be rolled into existing guidance on the website?
What needs to be done to develop the content further, for the two types of Bots?
TIPS Bot, simple Q&A: providing base content for Jeff's initial bot to get started with the training
Identify conversation sequence patterns for future conversational bot

https://ibm.box.com/s/84zizbcm3sg5igsg9giqu3evya36vpoa


[WIP] Layer controls designs implementation and code refactor

References and relevant issues
Part of #5358
Description
Initial implementation of the designs being discussed at #5358 while taking into account possible future features that could affect the way the layer controls work/are instantiated (multi-layer selection and LayerGroup definition).
The current changes only cover the controls for the Shapes layer type. From the GUI you can see something like:

Windows
MacOS
Linux

Some of the elements that this PR changes:

Creates individual classes per widget control (QtWidgetControlsBase, QtOpacityBlendingControls, QtEdgeColorControl, QtEdgeWidthSliderControl, etc) that handle the layer attributes <-> widget values connections.
Defines methods to add buttons and widget controls (_add_radio_button_mode, _add_push_button_action,  add_annotation_widget_controls and add_display_widget_controls) in the base QtLayerControls class.
Move logic related to layer interactive mode and editable/visible widget controls handling to the base QtLayerControls class.
Update base controls class layout and napari style rules to start accomodating to the designs details at https://github.com/napari/napari/issues/5358#issuecomment-1699362809

Notes

~:warning: As mentioned, the current changes on the branch only make sure that the Shapes layer controls work so trying to use napari to create other layer types running from this branch will probably end up showing errors/failing to create the respective layer controls.~ To prevent errors/failing tests the old base layer controls class is still there for the controls of layer types still not changed. After moving all the control layer classes to use the new base definition it should be removed.
As mentioned at https://github.com/napari/napari/issues/5358#issuecomment-1726661372 the buttons order will be preserved here
It would be nice to first get some feedback on the implementation/code refactor done to see if that makes sense (that's why I only changed how things work for the Shapes layer controls for the moment). If the approach actually makes sense or after incorporating given feedback things look good (in terms of the implementation/code refactor), then I will continue doing here the changes for other layer types. So, although this is still WIP, feel free to comment here what do you think/other ideas to implement this!

As anticlimactic as it might be for a first review, I gave the QSS files a look and all looks correct to me so far! The screen shots (thank you for those!) are what I expect as well.
Thank you for getting this started and identifying the feedback you need. I will circle back as more changes go forward, but mostly I'm impressed to see the details percolating so clearly from the start.

@dalthviz This PR still has [WIP] in the title but I see only merging main activity. Did you forget to remove [WIP]?

I think they're waiting for feedback from us; for now, I haven't had time to dive in and anyways I was waiting for the v0.4.19 to land so folks have mroe time to discuss here.

Yep, waiting for feedback here as Lorenzo says. So basically, I left this as [WIP] since this still needs to replicate the changes done to the Shapes layer to the other types of layers. The thing is that, before doing the full refactor for other layers types, I would like to get general feedback about the refactor approach implemented. So to know first if there is something in the approach to improve or if there are any other ideas and in general if this approach is a good enough base for future features like multilayers selection or group layers (so future refactor/changes are smaller/more contained hopefully 🤞🏼 ).
I have been merging with latest main just to fix merge conflicts when they appear and check that the changes here are still compatible with latest main :)

Hey @dalthviz,
Are you looking for feedback on the code or on the functionality? We played around with this during the PR party and identified the following issues with the functionality:

love collapsing the "display" section
we didn't like that the controls scroll bar is always there, even if there is plenty of room. The scroll bar should disappear (and the full width used) if there is space.
when display is collapsed, the min height for the controls is too much — I can't actually make use of the collapsing to get more room for the layer list
the spacing between the buttons is too much now — it should be like the original, or the buttons can be bigger and fill up the space. Also the button arrangement should be the same — it's weird that the bring-to-front/send-to-back buttons are miles away from each other now. 😂

But maybe you are looking for code and not functional suggestions, in which case, hold please. 😅 🙏

Hi @jni ! Thank you for the feeback! Although a more code related review could be awesome (to see if the refactor approach I took makes sense), any feedback is appreciated! Checking the funtionality related feedback, maybe people would prefer things to look/work something like the following then?:

Pushed a commit with some changes in case someone wants to check things locally :)
Also, what do you think @isabela-pf ?

Checking the funtionality related feedback, maybe people would prefer things to look/work something like the following then?:

Yes, that looks great!
I'll try to make some time this coming week for some code review. Thank you!

@dalthviz This works for me. Thank you for making the update! Thank you for the tag as well. Glad to see this getting some review!

Gentle ping to @jni (https://github.com/napari/napari/pull/6219#issuecomment-1986557866), if you have some time :pray:

Jut FYI I am taking a look at this slowly but it would be great to get other @napari/core-devs playing with it as well! @psobolewskiPhD surely this is up your alley 😛

@dalthviz I had a little play-around. Overall I really like it. I think it would be good to see Labels layer done next, as it's the first one that has the annotation box alongside the display box. A couple of points I've noticed (haven't yet looked at implementation sorry):

on Mac I can't seem to get the scrollbar on the layer controls to show up like in the screencap. Even if I minimize the display box, I can't expand the layerlist into that space (screenshot shows minimum size I can make the box on Mac). Ignore me if this hasn't been implemented yet in this PR, just wasn't sure if this should work.
I can't rename a layer from the layerlist anymore, I can only rename it from the top of the layer controls
Popping out the layer controls widget immediately takes me to the layer name edit mode (cursor showing) without me double-clicking on the name

Thanks @DragaDoncila for checking this and the feedback!
Regarding the behavior of not being able to see the scrollbar, I think that's caused due to the addition of a labels layer (the old controls style puts a min fixed height for the layer controls container which is not reversible even when you remove all the layers). As this PR is, if you check creating only Shapes layers I think you should be able to see the scrollbar/resize the layer controls area/dockwidget as seen over the preview GIF.
About the other behaviors, from a quick test, I was unable to reproduce being unable to remane the layers from the layers list on Windows :thinking:. However, I think I was able to reproduce the popping out/undocking causing to focus jumping to the layer controls title widget. Anyhow, I will give those behaviors a more in depth check over my macOS machine :+1:
Thanks again for checking this!

Last commit should fix the issue with the focus going to the layer name lineedit when undocking/popping up the controls dockwidget. Related with the layer rename from the layerlist, I was unable to reproduce the issue on macOS 🤔, maybe what is confusing now is that for you to be able to edit the name you need to double click while over layer controls name just clicking itis enough to trigger the edition?

Regarding the behavior of not being able to see the scrollbar, I think that's caused due to the addition of a labels layer

yep, you're right ignore that one!

About the other behaviors, from a quick test, I was unable to reproduce being unable to remane the layers from the layers list on Windows

Hmm it also seems fine for me now, so I don't know what I was doing before, but ignore it!

Last commit should fix the issue with the focus going to the layer name line edit when undocking/popping up the controls dockwidget

Yep, that is indeed fixed! Thanks ❤
I've played around some more and one thing I've noticed is that when first adding a layer, the layer controls remain at their minimum size. While this is nice for making sure the layerlist gets prioritsed space, I think it's a little strange and potentially confusing for users who are familiar with the original UI, because you can't actually see any controls before scrolling down.

I think it would be nice if the controls did expand a little, just enough to see the first control and maybe a little of the second:

But don't feel pressured to make that change now, perhaps others disagree.
I really like it overall though! It's very smooth ❤

I like this a lot! I think the collapsable properties are a real boon.
I also agree with @DragaDoncila 2nd point (the minimum size)--lets not make things too jarring vs. the existing layout, but I don't see the horizontal scroll bar.
One thing that I think will be nice in a followup is to split opacity and blending which are there for every layer from the Shape controls. See also comment here: https://github.com/napari/napari/issues/702#issuecomment-555098444
One could consider putting them in their own collapsable group or in their own fixed top group. I can see arguments for both.

but I don't see the horizontal scroll bar.

Oh neither do I, that's the beginning of the next control hahaha. So I guess, make the min size a little bit bigger than that 😆

One could consider putting them in their own collapsable group or in their own fixed top group. I can see arguments for both.

I think these are so "bread and butter" that maybe they should be fixed. Certainly they should be at the top in their own group.


TN-342 Update UserConsent model/api; omit withdrawn from TNUSA staff patients

https://jira.movember.com/browse/TN-342

added 'status' field to UserConsent model

restricted to ('consented', 'suspended', 'deleted') values
required; defaults to 'consented'
added to JSON methods

migration for new UserConsent.status field

defaults to 'consented'; sets to 'suspended' or 'deleted' depending on UserConsent.options or UserConsent.deleted_id

added new /user/<user_id>/consent/withdraw [PUT, POST] endpoint

only requires user_id (in path) and organization_id (in JSON) - similar to consent [DELETE]
replaces existing valid user/org consent with a matching one, minus the following changes:

status = 'withdrawn'
include_in_reports = True
send_reminders = False
staff_editable = False IF config['GIL'], else True

updated patients list to only include users whose consent.staff_editable is True
added new unit tests to test new functionality + new changes to existing functionality
minor pep8 fixes throughout relevant files

NOTE:
This should NOT be merged until @achen2401 has a chance to add her changes for https://jira.movember.com/browse/TN-404

@achen2401 There should already be a check there; look at https://github.com/uwcirg/true_nth_usa_portal/blob/develop/portal/models/user.py#L1140
user.check_role("edit", other_id=user_id) gets called during the /profile load (where user is the acting user, and user_id is the ID of the profile user). If user is Staff or StaffAdmin, and the profile user's consent does not have staff_editable, the check fails.
I haven't had a chance to actually test this though; if you're seeing different behavior in the portal, let me know, I can dig in and see why that's failing.

@achen2401 Please merge if you're satisfied 👍

@ivan-c Ivan, I think we are waiting for @pbugni Paul to look at these changes.  It would be great if he can have a peek.

@OptimusRhine adam, you are right, just tried this again.  I think it is working as intended  I realized I was trying that out using an staff account that has admin privilege.


docs(react-router-v4): update API

See #2020

@Haroenv: good catch for the bind. Also we don't have a preview of the recipes yet, so you will not be able to see it live through netlify :(

Should be ok now :)

awesome!

I'm seeing something bad:
Warning: Failed prop type: The prop `push` is marked as required in `Unknown`, but its value is `undefined`.

and makes sense, .push are not in props: https://reacttraining.com/react-router/#route-props
I didn't detect it in the past because browser cache 😭

this.props.push → this.props.history.push

You can do a pull request @Kikobeats <3


node-sass --watch outputting empty CSS files

NPM version (npm -v): 5.0.3
Node version (node -v): v8.1.2
Node Process (node -p process.versions):
{ http_parser: '2.7.0', node: '8.1.2', v8: '5.8.283.41', uv: '1.12.0', zlib: '1.2.11', ares: '1.10.1-DEV', modules: '57', openssl: '1.0.2l', icu: '59.1', unicode: '9.0', cldr: '31.0.1', tz: '2017b' }
Node Platform (node -p process.platform): Linux
Node architecture (node -p process.arch): x64
node-sass version (node -p "require('node-sass').info"):
node-sass       4.5.3   (Wrapper)       [JavaScript] libsass         3.5.0.beta.2    (Sass Compiler) [C/C++]
npm node-sass versions (npm ls node-sass):
<EMAIL_ADDRESS>/home/vagrant/halfpricebanners/angular4 ├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped └──<EMAIL_ADDRESS>

Recently, i've been experiencing valid code being outputted to my CSS file as 0 bytes, no data.
But sometimes, if I change a value of any property, it will output a the CSS fine.
node-sass --watch sass/basic-pages.scss css/basic-pages.css --output-style compressed

The SCSS:
basic-pages.scss.txt
I've ran this through many validators with no errors, shown colleagues for review if I missed something obvious, with no luck.
Please let me know your thoughts. Thanks!

Supplemental example
First State

Second State (Removed .img-background selector)

Further testing:
Seems that when I manually run node-sass sass/basic-pages.scss css/basic-pages.css --output-style compressed The output is fine, consistently.
This may be a problem with --watch flag.

Experiencing the same. Problem is intermittent. Only happens when using watch flag, manual compilation works fine.

I actually have issues even without --watch flag

No more updates on this issue? I'm getting blank css files as well. I tried to update everything, reboot and nothing. Looks like some files are ok and others don't. I'm trying to simulate some cenários.

To have a look at it, I'd like to have a small repository to reproduce the issue consistently.
Please also say what kind of Linux system is this exactly, it would be also good to know what kind of filesystem are you on. It can also be helpful to know what editor are you using to make the changes.
Watching a filesystem is not an easy issue, there are lots of moving parts.

I'm also experiencing issues with --watch flag, sometimes compiles into empty css, although is fine, when I run it manually.
However, I am using node-sass-chokidar.
I am using elementary OS 5.1.4 Hera and VSCode editor. filesystem - Ext4.
I am not using Vagrant.

The same issue is on Ubuntu 18.04.4 LTS,  ext4, Node v13.14.0

Can everybody affect confirm they are using Visual Studio Code?

Can everybody affect confirm they are using Visual Studio Code?

I am using Visual Studio Code

Experiencing this on an Ubuntu server edited remotely over SFTP (Panic Nova, not VS not that it would matter)

experiencing the same, i think its not vscode, just the watcher hang temporarily...how to handle it is just re-save  (ctrl + s) the scss file until it work normally

I am having the same issue. I'm in VS Code - MacOS Big Sur 11.1. Will work once or twice and then produce an empty css file more often than not.

I'm also experiencing this issue. This is the command I'm using:
sass --watch --no-source-map main.scss main.css

The first time I save it works great. Every subsequent save results in an empty main.css file. I'm saving files over SFTP using Panic's Nova editor. Switching to node-sass-chokidar did not fix it for me. I'm assuming this has something to do with the way Nova (and other editors) are saving files over SFTP...

The problem is also described here: https://stackoverflow.com/questions/35942340/sass-watch-command-compiles-scss-files-before-full-sftp-upload

This is because, when the file upload takes time, sass compiles the scss file (on the server) before it is fully uploaded to the remote folder. Thus, it only compiles part of the file, resulting in css errors.

I'm pretty sure this is what's going on. I think we need an option to add a delay to the watch to account for file upload time when working remotely over SFTP.

Any progress on this? Still happening. A delay on watch sounds like it would solve it, the theory that it is the latency between uploading the file contents to a remote server and the compilation seems likely.

Fixed with npm-watch and a delay with that for now :) https://www.npmjs.com/package/npm-watch


Error: Could not get HiyaCFW.

So I got version 3.0.2 but it still says that it can't find HiyaCFW. Any solutions?

I'm also using the .exe version btw.

Never mind... All I needed to do was to have the Windows folder as well!

Seems to be solved, closing issue


fix: enable cesu8 by default for hdb driver and encode entries streams

fixes: https://github.com/cap-js/cds-dbs/blob/da629d98192cf1b196cceb172cb01f4a39acd887/test/compliance/resources/db/basic/literals/basic.literals.string.js#L41
The tests run with hana-client inside the pipelines. Tested locally works as expected.

did the test also fail for plain string?


Added requirement for user to enter his old password when changing important settings.

Added requirement for user to enter his old password when changing his password, email or name.
I also included the AuthException class into Account.php to prevent an error on line 201.
#301

I added an option to the settings page but did not make use of the language files, yet.

@cbacon93 If you are interested in seeing this merged in (I know it has been a while), would you mind resolving the conflicts on your PR branch? :)

@cbacon93 I have finished off the functionality as per the review notes for you, as I was keen to see this feature implemented.


add manifest to fix source tarball

@jhamman you'll need this and a new release to make the recipe in https://github.com/conda-forge/staged-recipes/pull/9761 work. Files from 1-5 are missing in the PyPI sdist tarball.

Thanks @ocefpaf!

Thank you for helping me make a case for slide 14 :wink:


perf(event): quicker quit

nvim-notify causes hanging on quit, use silent to prevent hanging.

IMO this will lead to a potential problem. @CharlesChiuGit Can you test this for me?

First create a new autocmd that is triggered by VimLeave, such as:

:autocmd VimLeave * :sleep 2

Then :q to quit vim normally
If neovim works normally, there will be a 2 second delay before exiting.

If you call write instructions following silent, then the VimLeave event will be ignored in some cases.

IMO this will lead to a potential problem. @CharlesChiuGit Can you test this for me?

First create a new autocmd that is triggered by VimLeave, such as:

:autocmd VimLeave * :sleep 2

Then :q to quit vim normally

If neovim works normally, there will be a 2 second delay before exiting.

AFAIK If you call write instructions following silent, then the VimLeave event will be ignored in some cases.

will test as soon as i got home.

IMO this will lead to a potential problem. @CharlesChiuGit Can you test this for me?
* First create a new autocmd that is triggered by `VimLeave`, such as:

:autocmd VimLeave * :sleep 2

* Then `:q` to quit vim normally

* If neovim works normally, there will be a 2 second delay before exiting.

AFAIK If you call write instructions following silent, then the VimLeave event will be ignored in some cases.

I tested the case and the result is that neovim will quit quickly instead of sleep 2.

@jczhang02 thanks!
@Jint-lzxy then maybe remove "wall"?

@CharlesChiuGit Then what command will follow silent?
:sil[ent][!] {command}

maybe a format command?

@CharlesChiuGit My question is, why would notify hang on quit? Notify is only a part of the rendering component. If the entire neovim instance is asked to be closed, notify should not be the reason to prevent it from closing normally?

when one use ":wq" to quit nvim, the format_on_save will pop up a half-rendered notify. this will cause quitting to hanging. if only use ":q", then there will be no hanging.

Ahh I see. Maybe we can try to modify the render functions of notify. I will look into it tomorrow if I have time 👍

cool! that would be less "hack" then this solution!

@CharlesChiuGit I have just tested this problem in detail. The delay occurs only when we :wq on a modified file, but I think this may be caused by neovim itself writing files to the disk, not notify. Notify didn't even start its rendering in my test cases.

@CharlesChiuGit I have just tested this problem in detail. The delay occurs only when we :wq on a modified file, but I think this may be caused by neovim itself writing files to the disk, not notify. Notify didn't even start its rendering in my test cases.

You're probably right. Or maybe it's just that certain nightly build of neovim having this problem. After I updated neovim, quitting neovim feels snappy again. Closing this PR.


Fixing headers for the README file

Apparently everyone has made these pull requests...
These are all the same: #99, #98, #97, #96, #95, #94

Fixed by #93


Missing command - status?

I've started using helmfile, and after a couple of days of use, I am missing a way to do helm status on the repo's that the helmfile points to..

FYI, this is currently WIP in #70 thanks to @cmeury!
Btw, what is your use-case for this feature? I have never wanted to run helm status through helmfile myself. A short user-story would be welcomed!

Forgot to mention you - just adding it for your notice @xeor

@cmeury I'm still wondering how this would be implemented in its best form.
AFAICS, just repeating helm status <release> for each relevant release would result in multiplying something like:
$ helm status esteemed-magpie
LAST DEPLOYED: Tue Apr  3 17:30:13 2018
NAMESPACE: default
STATUS: DEPLOYED

RESOURCES:
==> v1/Secret
NAME                   TYPE    DATA  AGE
esteemed-magpie-mysql  Opaque  2     17s

==> v1/PersistentVolumeClaim
NAME                   STATUS  VOLUME                                    CAPACITY  ACCESS MODES  STORAGECLASS  AGE
esteemed-magpie-mysql  Bound   pvc-3ae0dfe4-3719-11e8-811a-080027e8f12b  8Gi       RWO           standard      17s

==> v1/Service
NAME                   TYPE       CLUSTER-IP    EXTERNAL-IP  PORT(S)   AGE
esteemed-magpie-mysql  ClusterIP  <IP_ADDRESS>  <none>       3306/TCP  17s

==> v1beta1/Deployment
NAME                   DESIRED  CURRENT  UP-TO-DATE  AVAILABLE  AGE
esteemed-magpie-mysql  1        1        1           0          17s

==> v1/Pod(related)
NAME                                    READY  STATUS           RESTARTS  AGE
esteemed-magpie-mysql-6887f4c88c-7zm6f  0/1    PodInitializing  0         17s

NOTES:
MySQL can be accessed via port 3306 on the following DNS name from within your cluster:
esteemed-magpie-mysql.default.svc.cluster.local

To get your root password run:

    MYSQL_ROOT_PASSWORD=$(kubectl get secret --namespace default esteemed-magpie-mysql -o jsonpath="{.data.mysql-root-password}" | base64 --decode; echo)

To connect to your database:

1. Run an Ubuntu pod that you can use as a client:

    kubectl run -i --tty ubuntu --image=ubuntu:16.04 --restart=Never -- bash -il

2. Install the mysql client:

    $ apt-get update && apt-get install mysql-client -y

3. Connect using the mysql cli, then provide your password:
    $ mysql -h esteemed-magpie-mysql -p

To connect to your database directly from outside the K8s cluster:
    MYSQL_HOST=<IP_ADDRESS>
    MYSQL_PORT=3306

    # Execute the following commands to route the connection:
    export POD_NAME=$(kubectl get pods --namespace default -l "app=esteemed-magpie-mysql" -o jsonpath="{.items[0].metadata.name}")
    kubectl port-forward $POD_NAME 3306:3306

    mysql -h ${MYSQL_HOST} -P${MYSQL_PORT} -u root -p${MYSQL_ROOT_PASSWORD}

which seems like too verbose(for me).
Probably we should at least omit NOTES: from the output while merging RESOURCES so that it would look more like the status of the whole releases managed by the helmfile.yml?
Also, I guess it should better be consistent with #68

How using the [JSON output option] https://docs.helm.sh/helm/#Helm-status) and reformatting?

@cmeury Sounds great! I'm now wondering the scope of #70. Would you be willing to submit a separate PR on top of #70 for further enhancement? If so, I'll merge it as-is, if it helps.
@sstarcher You seem to be interested in this feature, too? Any comment on how the output would ideally look like?

I'm really only interested in a exit code of all good or something not so good.  I general ignore the helmfile output as it's extremely verbose and hard to follow.

The plan:

Merge @cmeury's awesome work #70
According to @sstarcher's suggestion, reduce output to include release names and status codes only.

helm status -o json/yaml returns code in int so we need to map one to human-readable status name as defined in the proto def

According to my suggestion, implement helmfile status -o json to output json representation of releases

WDYT? @sstarcher @cmeury @xeor

sounds like a good idea to me.  In the future it would likely be nice to extend the -o to the other outputs.

@sstarcher Thx for the confirmation. Yeah. I'm not intended to extend it so much right now, but at least yaml after helm's yaml output would make sense.


APU 1636:1002 Vega 7

Hello, first I congratulate by this incredible work. The AMD Ryzentosh don't work without this project. I buy I cheap laptop in Brazil with very good Ryzen 7 4800H 8 core ASUS M1502IA. I managed install Ventura on it that recognised the processors, battery manager, etc. But I had very difficult to config the APU 1636:1002 Renoir Vega 7. When Ii putt the kext WhateverGreen don't recognized acceleration and some apps open with very low 7mb vram.  When I use Nootedred I get acceleration, metal support, everythings good excepted the VM memory =0 that crash most of apps.
Next post i Will send the errors.

Please bring your issue up in the AMD OS X Discord or with the NootedRed team instead.

Ok
Sorry
Em seg, 18 de dez de 2023 15:20, Alyx Ferrari @.***>
escreveu:

Please bring your issue up in the AMD OS X Discord or with the NootedRed
team instead.
—
Reply to this email directly, view it on GitHub
https://github.com/AMD-OSX/AMD-OSX-FAQ/issues/9#issuecomment-1861252434,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANSMU54BT6BUHK5POUMVIF3YKCCNZAVCNFSM6AAAAABAZQVVS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRRGI2TENBTGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Not support wsl2

show error:
platform is not supported

I use vim-plug for plugin manager, and I install this branch by Plug 'ekickx/clipboard-image.nvim', { 'branch': 'feat_WSL' }
But same error again

clipboard-image: require("clipboard-image.health").check()
Checking dependencies

ERROR: platform is not supported

additional info:
when run uname -a in wsl, the output is Linux W00573115 <IP_ADDRESS>-microsoft-standard-WSL2 #1 SMP Wed Mar 2 00:30:59 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

and the content of /proc/version is Linux version <IP_ADDRESS>-microsoft-standard-WSL2 (oe-user@oe-host) (x86_64-msft-linux-gcc (GCC) 9.3.0, GNU ld (GNU Binutils) <IP_ADDRESS>00220) #1 SMP Wed Mar 2 00:30:59 UTC 2022

when just run uname, the output is Linux

{ "Linux version <IP_ADDRESS>-microsoft-standard-WSL2 (oe-user@oe-host) (x86_64-msft-linux-gcc (GCC) 9.3.0, GNU ld (GNU Binutils) <IP_ADDRESS>00220) #1 SMP Wed Mar 2 00:30:59 UTC 2022" }

Ok just to make sure, can you show me the output of this command
:lua print(vim.inspect(vim.fn.readfile("/proc/version")))

{ "Linux version <IP_ADDRESS>-microsoft-standard-WSL2 (oe-user@oe-host) (x86_64-msft-linux-gcc (GCC) 9.3.0, GNU ld (GNU Binutils) <IP_ADDRESS>00220) #1 SMP Wed Mar 2 00:30:59 UTC 2022" }

I just pushed a new change. Can you try it now?

It shows powershell is not installed, but I already add powershell.exe into PATH.
Maybe need change powershell to powershell.exe?

Hmm weird 🤔. In check_package_installed, I use vim.fn.executable to check for powershell.exe. Maybe you can do
:lua print(vim.fn.executable("powershell.exe"))

If the output is not 1 then there is something wrong

the output is 1

Oh, maybe the path is wrong, powershell is ok now

It shows There is no image data in clipboard

yes, i copied the image in win10, and want to paste in WSL2

Can you try it now?

It's OK now！

Really thx for your efforts!


When creating a new disk, setting allocation policy to pre-allocated policy is ignored

When creating a new disk for an existing VM and setting allocation policy/disk type field to "preallocated", then disk is still created with Thin provision policy.
For some reason, setting the policy to "pre-allocated" is ignored.

It seems that this issue is solved and not reproduced anymore so closing


[v4 css] inverted table styling

When inverting a table style using the table-inverse class (demo):

Striping
With a "table-striped" class, the stripes are not discernibly different. In the css, the definition is the same as for the non-inverted row styling:
.table-striped tbody tr:nth-of-type(odd) {
  background-color: rgba(0, 0, 0, .05); /* $table-bg-accent; */
}

Borders
The border styling of the non-inverted tables is a very subtle, using a border color of #eceeef. On inverted tables, we see #fff! It's way to bright!
.table-inverse td,
.table-inverse th,
.table-inverse thead th {
  border-color: #fff; /* $body-bg */
}

Hover
Hovering isn't as bad when no stripe is applied to the table; but when a stripe is applied, the hover is only slightly more discernible than the row color (demo)!
.table-hover tbody tr:hover {
  background-color: rgba(0, 0, 0, .075) /* $table-bg-hover */
}

This may not seem like a big deal to some of you young 'uns out there, but for elderly and visually impaired users, it would make a difference.

I agree with @Mottie.
Regarding the striping, maybe we should change $table-bg-accent: rgba($black,.05) to $table-bg-accent: rgba($gray-light,.075).
Regarding the borders, maybe we need a new variable called $table-inverse-border-color and set it's default value to lighten($table-inverse-bg, 15%).
Regarding the hover, maybe we should change $table-bg-hover: rgba($black,.075) to $table-bg-hover: rgba($gray-light,.075).
I tested these new settings and it looked good (on two completely different monitors) but would appreciate your feedback.  I also experimented with changing $table-inverse-bg to different values and that worked out well too.
So to recap, I'm proposing the following changes in _variables.scss (under the $table-inverse-color variable):
$table-inverse-border-color:    lighten($table-inverse-bg, 15%) !default;

$table-bg-accent:               rgba($gray-light,.075) !default;
$table-bg-hover:                rgba($gray-light,.075) !default;

And the following changes in _tables.scss:
.table-inverse {
  color: $table-inverse-color;
  background-color: $table-inverse-bg;

  th,
  td,
  thead th {
    border-color: $table-inverse-border-color;
  }

  &.table-bordered {
    border: 0;
  }
}

What do you guys think?

Fixed by #22217.


V0.1.14 - Added add-routeset command

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 96.18574% with 23 lines in your changes missing coverage. Please review.

Project coverage is 97.61%. Comparing base (24f77bd) to head (5ba463f).
Report is 2 commits behind head on main.

Files with missing lines
Patch %
Lines

zentra_api/cli/commands/add.py
91.86%
10 Missing :warning:

zentra_api/cli/main.py
52.63%
9 Missing :warning:

zentra_api/cli/builder/routes.py
66.66%
2 Missing :warning:

zentra_api/cli/constants/enums.py
96.87%
1 Missing :warning:

zentra_api/cli/constants/routes.py
99.36%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main       #2      +/-   ##
==========================================
+ Coverage   96.77%   97.61%   +0.83%
==========================================
  Files          27       31       +4
  Lines         930     1423     +493
==========================================
+ Hits          900     1389     +489
- Misses         30       34       +4

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


Leaked instances on exit

For some reason, the plugin doesn't clean itself and its resources even if I free it at exit.
This may be due https://github.com/godotengine/godot/issues/45512 (wich will be fixed on 4.0) but I'm not sure. For now it's not generating a major problem, but I should keep track of this.

Update: for some unknow reason, i managed to solve this. I really don't know how I did it

Another Update: Translations inspector added this bug again. Maybe the plugin inspector can't be free at exit since someone is still holding it's reference?
Annotation: maybe i should use weakref to editor plugins

v0.1.4 added this issue again, with a misterious PanelContainer that appears randomly

Apparently, drag & drop function causes this

v0.2.0 update: The issue is gone.
I'm not closing this just in case.

v0.3 update: Still no leaked instances
Pro tip: Be sure to free any unused instance.

More information: https://github.com/godotengine/godot/issues/21461

v1.0 update: No leaked instances.
Another tip: Use signals to avoid orphan nodes.


feat: add sync setting parameter to index

User description
New implementation at startup to synchronize the local index with the remote index based on the specified mode.
Modes:

error: Raise an error if local and remote are not synchronized.
remote: Take remote as the source of truth and update local to align.
local: Take local as the source of truth and update remote to align.
merge-force-remote: Merge both local and remote taking only remote routes utterances when a route with same route name is present both locally and remotely.
merge-force-local: Merge both local and remote taking only local routes utterances when a route with same route name is present both locally and remotely.
merge: Merge both local and remote, merging also local and remote utterances when a route with same route name is present both locally and remotely.

Can be tested with basic code like the following:
from semantic_router import Route
from semantic_router.encoders import OpenAIEncoder
from semantic_router.index.pinecone import PineconeIndex
from semantic_router.layer import RouteLayer

politics = Route(
    name="politics",
    utterances=[
        "isn't politics the best thing ever",
        "why don't you tell me about your political opinions",
        "don't you just love the president",
    ],
)

chitchat = Route(
    name="chitchat",
    utterances=[
        "how's the weather today?",
        "how are things going?",
    ],
)

routes = [politics, chitchat]

encoder = OpenAIEncoder(openai_api_key=openai_api_key)

pc_index = PineconeIndex(
    api_key=pinecone_api_key,
    region="us-east-1",
    index_name="alai-clearwater-routes-input-intent",
    sync="local",
)

rl = RouteLayer(encoder=encoder, routes=routes, index=pc_index)

PR Type
Enhancement

Description

Added sync parameter to BaseIndex, LocalIndex, and PineconeIndex classes.
Introduced _sync_index method with various synchronization modes in BaseIndex and implemented it in PineconeIndex.
Modified add method in PineconeIndex to handle synchronization.
Added _get_routes_with_ids method in PineconeIndex.
Enabled synchronization in RouteLayer's _add_routes method.

Changes walkthrough 📝
Relevant filesEnhancement

base.pyAdd sync parameter and synchronization logic to BaseIndex

semantic_router/index/base.py
Added sync parameter to BaseIndex class.  Introduced _sync_index method with various synchronization modes.

+21/-1

local.pyAdd sync parameter to LocalIndex add method

semantic_router/index/local.py

Added sync parameter to add method.

+5/-1

pinecone.pyAdd sync parameter and synchronization logic to PineconeIndex

semantic_router/index/pinecone.py
Added sync parameter to PineconeIndex class.  Implemented _sync_index method for PineconeIndex.  Modified add method to handle synchronization.  Added _get_routes_with_ids method.

+125/-1

layer.pyEnable synchronization in RouteLayer's _add_routes method

semantic_router/layer.py

Updated _add_routes method to enable synchronization.

+1/-0

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

@Vits-99 I made some small changes to keep the qdrant index supported — wdyt to removing the sync parameter from the add method in the index objects

@jamescalam fixed the _get_all method ordered return bug for ids and metadata and added an _add_and_sync method to replaced the usage of the add method. I also adjusted the Qdrant index accordingly. Waiting for your feedback on this. If everything is fine I think we can merge it to main.


No output but also no errors

Hi all,
Im giving wp-cli a go and after the install I can run wp without errors but it stays totally quiet even with for instance "wp help". And I'm in a clean wordpress install. I'm really looking forward to using this.
Anybody a clue where to start digging?
Some specs:
wp-cli: latest from github
OS: Ubuntu 10.04.3 LTS (on intell)
PHP: PHP 5.3.2-1ubuntu4.14 with Suhosin-Patch (cli) (built: Feb 11 2012 06:50:46)
Wordpress: 3.3.1
Thanx a lot!
Regards,
Gerard.

Is it a WordPress Network install?

Hi Andreas,
I'm not sure what you mean by network install. It is a non-multisite setup. Downloaded the latest stable, untarred it on the local filesystem, settings are out-of-the-box-ish, in other words no setup customizations yet. And I already ran the regular browser based wordpress ".../wp-admin/install.php setup so it does have DB access.
Does that answer your question? :)
Regards,
Gerard.

Try adding define( 'WP_DEBUG', true ); to your wp-config.php file.

Googling the output it seems wordpress related. Anybody any clues?
PHP Notice:  Undefined index: HTTP_HOST in /home/testuser/temp/testdomain.com/wp-includes/functions.php on line 3765
Notice: Undefined index: HTTP_HOST in /home/testuser/temp/testdomain.com/wp-includes/functions.php on line 3765
PHP Notice:  Undefined index: SERVER_PROTOCOL in /home/testuser/temp/testdomain.com/wp-includes/functions.php on line 1672
Notice: Undefined index: SERVER_PROTOCOL in /home/testuser/temp/testdomain.com/wp-includes/functions.php on line 1672
PHP Warning:  Cannot modify header information - headers already sent by (output started at /home/testuser/temp/testdomain.com/wp-includes/functions.php:3765) in /home/testuser/temp/testdomain.com/wp-includes/pluggable.php on line 866
Warning: Cannot modify header information - headers already sent by (output started at /home/testuser/temp/testdomain.com/wp-includes/functions.php:3765) in /home/testuser/temp/testdomain.com/wp-includes/pluggable.php on line 866

It seems the aformentioned VARS normally come from the client (the browser) .. When I explicitly set them in wp-cli.php (like below) the errors are gone but so is my output. Still at a loss :(
$_SERVER['HTTP_HOST'] = "foo";
$_SERVER['SERVER_PROTOCOL'] = "HTTP/1.1";

After digging some more .. I was in a wordpress installation for which I did not finish the install-by-url yet ... It works now! .. Thanx all for putting me in the right direction.
Regards,
Gerard.


x/tools/gopls: duplicated analysis work

The following log events were observed in a single run of "gopls check" (with staticcheck and nilness enabled) that was instrumented to report start/end calls to Analyze:
	t0 := time.Now()
	log.Println("Analyze start", analyzers, pkgs, t0)
	defer func() {
		log.Println("Analyze end", analyzers, pkgs, t0, time.Since(t0)) // repeat t0 so we can tie start/end together
	}()

Observe that two concurrent Analyze calls request that the same package be analyzed with two different sets of analyzers.
ec2$ (cd ~/w/xtools && go build -o x ./gopls ) && time ~/w/xtools/x --profile.cpu=prof check ./internal/customizations/unit_test.go

2023/07/21 11:38:11 Analyze start [structtag stdmethods lostcancel unusedresult unusedparams copylocks unusedwrite timeformat buildtag bools embed shift sortslice loopclosure simplifyslice useany cgocall errorsas simplifyrange printf fieldalignment atomicalign unsafeptr assign testinggoroutine nilness ifaceassert composites nilfunc unmarshal directive stringintconv atomic simplifycompositelit deepequalerrors httpresponse unreachable asmdecl shadow tests QF1012 SA9002 S1007 ST1019 ST1021 ST1003 SA9005 SA1015 QF1010 SA9004 SA1029 SA4006 ST1000 QF1005 SA1019 SA1021 ST1013 SA1026 QF1002 ST1005 SA4030 SA9007 S1034 SA4016 SA1014 SA5002 SA1007 SA4021 SA4005 SA5001 SA1025 S1035 S1010 SA5000 SA1024 S1011 SA4014 SA6005 SA6001 S1018 SA2001 SA4009 SA5008 ST1016 S1028 S1006 QF1007 SA9003 SA4010 ST1012 QF1003 SA1000 S1005 ST1022 SA5004 S1000 S1023 QF1011 S1029 SA4024 SA1020 S1009 SA2002 SA4011 SA1030 SA4022 QF1006 S1038 SA4000 SA5007 S1020 S1031 S1021 S1032 SA1010 QF1004 ST1001 SA4029 SA1001 SA1012 S1016 SA1013 SA4012 SA4025 ST1023 S1003 SA1008 SA4013 S1017 SA4019 SA1023 SA4026 QF1008 SA9008 S1037 SA6003 SA1016 SA4008 ST1011 ST1018 SA1003 SA4001 QF1001 ST1017 S1002 S1040 SA1028 SA4018 SA1027 SA1004 SA3001 SA5003 S1039 SA1017 S1036 S1024 QF1009 ST1020 S1008 SA4015 SA2003 S1001 SA4003 SA4028 SA1006 SA4023 SA1011 SA5005 SA5010 S1030 SA6000 S1004 SA4017 SA9006 SA4004 SA2000 SA1002 SA6002 SA5012 SA1005 SA9001 SA3000 ST1008 SA1018 S1033 ST1006 SA4031 SA4020 ST1015 S1019 S1012 SA4027 S1025 nonewvars noresultvalues undeclaredname unusedvariable fillreturns] map[github.com/aws/aws-sdk-go-v2/service/ec2/internal/customizations_test [github.com/aws/aws-sdk-go-v2/service/ec2/internal/customizations.test]:{}] 2023-07-21 11:38:11.38853 -0400 EDT m=+0.728676834

2023/07/21 11:38:12 Analyze start [bools embed shift sortslice loopclosure simplifyslice unsafeptr useany cgocall errorsas simplifyrange printf fieldalignment atomicalign assign testinggoroutine nilness ifaceassert composites nilfunc unmarshal directive stringintconv atomic simplifycompositelit deepequalerrors httpresponse unreachable asmdecl shadow tests structtag stdmethods lostcancel unusedresult unusedparams copylocks unusedwrite timeformat buildtag SA4000 SA5007 S1020 S1031 S1021 S1032 SA1010 QF1004 ST1001 SA4029 SA1001 SA1012 S1016 SA1013 SA4012 SA4025 ST1023 S1003 SA1008 SA4013 S1017 SA4019 SA1023 SA4026 QF1008 SA9008 S1037 SA6003 SA1016 SA4008 ST1011 ST1018 SA1003 SA4001 QF1001 ST1017 S1002 S1040 SA1028 SA4018 SA1027 SA1004 SA3001 SA5003 S1039 SA1017 S1036 S1024 QF1009 ST1020 S1008 SA4015 SA2003 S1001 SA4003 SA4028 SA1006 SA4023 SA1011 S1030 SA6000 S1004 SA4017 SA9006 SA4004 SA5005 SA5010 SA2000 SA1002 SA6002 SA5012 SA1005 SA9001 SA3000 S1033 ST1006 SA4031 SA4020 ST1015 S1019 ST1008 SA1018 S1012 SA4027 S1025 SA9002 S1007 ST1019 ST1021 ST1003 SA9005 QF1012 SA1015 QF1010 SA9004 SA1029 SA4006 ST1000 QF1005 SA1019 SA1021 ST1013 SA1026 QF1002 ST1005 S1034 SA4016 SA1014 SA5002 SA1007 SA4021 SA4030 SA9007 SA4005 SA5001 SA1025 SA5000 SA1024 S1011 SA4014 SA6005 SA6001 S1035 S1010 SA4009 SA5008 ST1016 S1028 S1006 QF1007 S1018 SA2001 ST1012 QF1003 SA1000 S1005 ST1022 SA5004 SA9003 SA4010 S1000 S1023 SA4024 SA1020 S1009 SA2002 SA4011 SA1030 QF1011 S1029 SA4022 QF1006 S1038 noresultvalues undeclaredname unusedvariable fillreturns nonewvars] map[github.com/aws/aws-sdk-go-v2/service/ec2/internal/customizations_test [github.com/aws/aws-sdk-go-v2/service/ec2/internal/customizations.test]:{}] 2023-07-21 11:38:12.39064 -0400 EDT m=+1.730787501

2023/07/21 11:38:14 Analyze end [] map[github.com/aws/aws-sdk-go-v2/service/ec2/internal/customizations_test [github.com/aws/aws-sdk-go-v2/service/ec2/internal/customizations.test]:{}] 2023-07-21 11:38:11.38853 -0400 EDT m=+0.728676834 3.175811292s

2023/07/21 11:38:14 Analyze end [] map[github.com/aws/aws-sdk-go-v2/service/ec2/internal/customizations_test [github.com/aws/aws-sdk-go-v2/service/ec2/internal/customizations.test]:{}] 2023-07-21 11:38:12.39064 -0400 EDT m=+1.730787501 2.341551917s

The different sets arise from the two calls to source.Analyze, from diagnosePkg and codeAction, providing different values of the "includeConvenience" boolean, which varies the set. However, the facty subset of both sets is the same, so in principle they should be able to work synergistically.
Even if the flag is always true, the concurrent calls both create a DAG of analysisNodes for a batch of work, and execute it in parallel, and both encounter the slow ec2 package (1s, see #61506), so both make cache misses, even though they want the same computation. The only sharing is of completed analysis summaries via the file cache; there is no de-duplication of inflight requests (i.e. the first thread doesn't "lick the cookie"). This is problematic for large packages like ec2 because they are expensive to recompute, and more likely to be recomputed because their inflight duration is longer, increasing the odds of a concurrent request.
One solution would be to dedup using singleflight or a promise cache, but the logic could be tricky. Another would to somehow stagger the requests (codeAction and diagnosePkg) during initial indexing to make concurrent requests for large packages less likely; once the cache is populated subsequent operation is fast.
It's worth noting that this causes at worst a factor of 2x slowdown, which is a lot, but still much less than the current difference between actual and ideal performance of buildssa (see #61506).

I'm eliminating the codeAction call to analysis.


Missing file under 'matching' mode

Hi authors,
I tried to study matching, and so I set 'rl_mode' to 'matching' in config.py.
Now, when I start to run python3 simulator/main.py, an error popped out
Traceback (most recent call last):
  File "simulator/main.py", line 256, in <module>
    pickle.dump(simulator.record,open("output3/order_record-1103.pickle","wb"))
FileNotFoundError: [Errno 2] No such file or directory: 'output3/order_record-1103.pickle'

It seems that an important file is missing for running matching. Could you please check?

It suggests that the directory output3 for file dumping does not exist. You can simply create a directory called output3 or modify any code segments related to file I/O to resolve FileNotFoundErrors.


Add TELEPORT_TYPE EventContext for Enderman and /teleport teleportations

The only remaining TELEPORT_TYPE I see is #1629 after #1741 and this PR.

Fix your commits, no need for the merge with bleeding commit.

@gabizou I cleaned the commits, first time I did it, hope I didn't missed something.


How to repreduce the results or use the weights to process my own datas?

The weights are not available, you should download the datasets and the train the model again.


Ability to change the default settings

We're using this page in a screensaver, and therefore we don't have the ability to click on the cogwheel icon to change how the page is displayed (all we can do is log in via basic auth).
As such, it would be incredibly handy if we could change the default settings through the frontend somehow, so that our screensaver could use those instead of the current defaults.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/29837692-ability-to-change-the-default-settings?utm_campaign=plugin&utm_content=tracker%2F580790&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F580790&utm_medium=issues&utm_source=github).

Haha, that's a cool idea! :smile:
Would the approach described in #54 solve the problem?

Yep, that would solve it too, and probably in a slightly better fashion.

Cool, cheers. I'll close this ticket then and if you could +1 #54 that would be great, thanks!


PIP Install of Python Wheels fails for CUDA 10.1

The current lastest stable release in the CUDA 10 link seems to be 0.3.2 however the linux pip-install indicates it is 0.3.0. It should be noted that this version also does not seem to work.
Download the Python wheel file (For Python 3.6):
Stable:
    CUDA9.0 - linux_x86_64
    CUDA10 - linux_x86_64
    CUDA9.0 - linux_ppc64le
    CUDA10 - linux_ppc64le
Bleeding edge (changes with every successful master branch build):
    CUDA10.0 - linux_x86_64
    CUDA10.0 - linux_ppc64le

Start a fresh pyenv or virtualenv session.
Install the Python wheel file. NOTE: If you don't use a fresh environment, this will overwrite your py3nvml and xgboost installations to use our validated versions.
pip install h2o4gpu-0.3.0-cp36-cp36m-linux_x86_64.whl

Following Linux Error is thrown:
ERROR: h2o4gpu-0.3.2-cp36-cp36m-linux_x86_64.whl is not a supported wheel on this platform

What linux distributive do you use?

And Python version?

`python -m pip install h2o4gpu
Collecting h2o4gpu
ERROR: Could not find a version that satisfies the requirement h2o4gpu (from versions: none)
ERROR: No matching distribution found for h2o4gpu
python --version
Python 3.7.4
hostnamectl
Static hostname: brodyserver
Icon name: computer-desktop
Chassis: desktop
Machine ID: 1118f9219be1442887bd33cfb6286293
Boot ID: c920c6b4ba754d93afc73281c6bd4ea9
Operating System: Ubuntu 18.04.3 LTS
Kernel: Linux 5.0.0-32-generic
Architecture: x86-64
`

You need to use python 3.6.
https://github.com/h2oai/h2o4gpu/issues/808


Taco

Hi,
first awesome job, i was in the process of trying to do a tool like that, but you did real good.
Also, can Taco Be added then ? with at least these 2 POI packs
http://tekkitsworkshop.net/index.php/gw2-taco/download
https://www.heinze.fr/taco/?lang=en (it has DE,FR and EN, would be awesome to be able to select lang)
Regards

TaCO has its own installation process and isn't a plugin/addon for the game, rather an external application that interfaces with it, so it's not really in scope for now. I'm not ruling it out for the future, but it's unlikely to be added.

Yup, i just saw on reddit you said the same.
It's only tedious to keep taco updated, and POI too
I've forked your project, and will see if time and skill allow me to add that =)
Cause it is only a matter of checking taco version diff from PC and Site, and for POI use taco://URI using the taco.exe

Best of luck!

I'd like to +1 this. TaCO integration along with Tekkit would be amazing.


An example in the README is incorrect

Please correct the readme. The write method requires a callback. Without it, it will fail randomly returning "Error: EBADF: bad file descriptor, write"
fs.write(info.fd, myData, function (err) {
  fs.close(info.fd, function(err) {
    exec("grep foo '" + info.path + "' | wc -l", function(err, stdout) {
      util.puts(stdout.trim());
    });
  });
});

@sithmel could you create a PR?

@UziTech Mind creating a PR for this and i'll merge it tonight?

Issue has been resolved.


[bug] RestrictToTopic validator occurs when disable_classifier is False and disable_llm is True

Describe the bug
When disable_classifier is False and disable_llm is True, the _inference_local method returns error on
candidate_topics = model_input["valid_topics"] + model_input["invalid_topics"]

The error message is
TypeError: unsupported operand type(s) for +: 'set' and 'set'

It is because
        valid_topics = set(metadata.get('valid_topics', self._valid_topics))
        invalid_topics = set(metadata.get('invalid_topics', self._invalid_topics))

return two sets and + operator cannot form a new array
To Reproduce
Steps to reproduce the behavior:
restrictToTopic = RestrictToTopic(
    valid_topics=["environment"],
    invalid_topics=["conspiracy", "food", "entertainment", "politics", "religion", "violence", "hate"],
    disable_classifier=False,
    disable_llm=True,
    on_fail=OnFailAction.EXCEPTION
)

result = restrictToTopic.validate(value="Large corporations should act responsibly socially and environmentally.  They should reduce carbon emission. One way to monitor their behavior is by reading their ESG Report.")
print(result.outcome)

Expected behavior
The _inference_local should return a found_topics array.
Library version:
Version 0.5.2
Additional context
Add any other context about the problem here.

Good catch.
I think I might have fixed this incidentally as a side effect with this PR: https://github.com/tryolabs/restricttotopic/pull/23

@JosephCatrambone  Thank you.  Do you know when guardrails will have a new release?   I am evaluating guardrails and LLM guards. While guardrails ai has more broken validators and missing validators (e.g., prompt refusal), it has more validators for detecting hallucinations and better error messages.  Both are very good for me.

Hi @railsstudent -- the PR got approved and merged yesterday, though I don't know if it's in the private pypi repo yet.

Apologies and thanks for the patience.  Assigning self again.  Going to need to push an 0.1.1.

I'm going to close this as resolved since the test in the first is passing, but if there's still a problem please feel free to reopen this ticket and I'll take another swing at it.  Thanks again for reporting the issue.


Policy

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 73596bc3-21bd-8511-2710-be93358b729a
Version Independent ID: 6d7e9716-265a-fdbd-163f-807cdcdcd4f2
Content: Microsoft identity platform app-only access scenario - Microsoft Entra
Content Source: articles/active-directory/develop/app-only-access-primer.md
Service: active-directory
Sub-service: develop
GitHub Login: @omondiatieno
Microsoft Alias: jomondi

@charlykt
Could you please elaborate the query for better understanding. So, we can assist you further.


Add missing downloads for SDK 2.0.0-preview1

There were entries for win/x86 and win/x64 named "dotnet-sdk-win-x86/x64.zip", but they pointed to the executable installers.
This corrects their name, and adds the correct links to the zip packages.
(Created directly on GitHub, so I have no control over the apparent addition of a final newline)

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: Zastai sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Add strike trough text style

:tada: This issue has been resolved in version 0.12.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Adding support for EKS Fargate

Hey.  I'm planning to build on the EKS endpoints I added recently with Fargate support.  I'm running into a bump and don't know how else to get in touch.
What should the responses.py entry look like to convert the selectors object back into something usable?  The scaffolding wrote it as selectors = self._get_list_prefix("selectors.member") and I am looking at other examples trying to find one that matches, but can't seem to get it to parse.
I've tried a bunch of things but the best I've managed to get out of it is an empty list. The API docs list it as non-required, but in reality create_fargate_profile() requires selectors to either have a namespace or between 1 and 5 labels so I wanted to add that check in the mock.
https://docs.aws.amazon.com/eks/latest/APIReference/API_CreateFargateProfile.html

Resolved by looking at it under a new sun.    Apologies for the churn.

Stepping through the code I have, selectors is being parsed fine in responses using
selectors = self._get_param("selectors")

and I can trace it is maintaining the value throughout creating the object but fails somewhere in processing/generating the response?  Here is the trace:
/Users/ferruzzi/.pyenv/versions/moto/bin/python "/Applications/PyCharm CE.app/Contents/plugins/python-ce/helpers/pydev/pydevd.py" --multiproc --qt-support=auto --client <IP_ADDRESS> --port 58756 --file "/Applications/PyCharm CE.app/Contents/plugins/python-ce/helpers/pycharm/_jb_pytest_runner.py" --target test_eks/test_eks.py::test_me
Testing started at 3:47 p.m. ...
   Regarding a wip branch, I'm int he habit of working locally until I have a working product to prevent sharing/spreading broken code, but in the future I can do that when I ask for help.  Sorry about that.
For posterity, it ended up having nothing ta all to do with the selectors; in my FargateProfile model I was defaulting tags to an empty list and it should have been an empty dict.

All good @ferruzzi - happy it's working now :)

closed by https://github.com/spulec/moto/pull/4185


Update gce zones 8 12

Change Overview
Adding Asia-south2 region and zone
Pull request type
Please check the type of change your PR introduces:

[ ] :construction: Work in Progress
[ ] :rainbow: Refactoring (no functional changes, no api changes)
[x] :hamster: Trivial/Minor
[ ] :bug: Bugfix
[ ] :sunflower: Feature
[ ] :world_map: Documentation
[ ] :robot: Test

Added zone updates for azure and aws as well


chore(document): change type hint for tags in docarray.document.data.…

…DocumentData
Goals:

see #732: this PR changes definition of tags in docarray.document.data.DocumentData to tags: Optional[Dict[str, Any]] = None
[ ] check and update documentation, if required. See guide

Codecov Report
Base: 88.29% // Head: 54.90% // Decreases project coverage by -33.39% :warning:

Coverage data is based on head (8515311) compared to base (f4b16ef).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #735       +/-   ##
===========================================
- Coverage   88.29%   54.90%   -33.40%
===========================================
  Files         134      133        -1
  Lines        6648     6655        +7
===========================================
- Hits         5870     3654     -2216
- Misses        778     3001     +2223

Flag
Coverage Δ

docarray
54.90% <100.00%> (-33.40%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Change default for bearer-token-propagation

To false for backwards compatibility
Fixes #1641

Which problem is this PR solving?

Short description of the changes

cc) @objectiser @jpkrohling


--host=<IP_ADDRESS> not usable across network

I am running elm-live on a server and accessing the result from a laptop. In order to do this I used --host=<IP_ADDRESS>. However, in the rendered HTML I then see:

Hey @p-salido, thanks for reporting this! Sorry for the delay in getting back to you.
Up till now I’ve treated elm-live purely as a development server – never suspected people would want to run it on a server. Is this just a multi-machine development setup that you’ve described? Or is it a server setup that you want to open up for public access?

@tomekwi I have a development server on a different machine from the laptop I use for interactive work.

OK got it @p-salido – makes sense. Does your server have an IP address that you can specify instead? I remember working on a similar setup before between my development machine and a phone on the same network. The way I managed to set things up was to use a static internal IP address of my development machine as the --host.

@tomekwi IP address is a workaround that works across the network, however the server maps its own hostname to <IP_ADDRESS> in the hosts file as is standard practice hence e.g. curl http://server/... from the server itself does not work, as the application listens on the network IP but not on loopback.

Oh right, I see. Do you have an idea how to solve this?
Unfortunately the LiveReload script is served from a different port by budo – the server that we use under the hood. I looked into the possibility of referencing the port kinda relatively, without specifying the host. Turns out there’s no straightforward solution: https://stackoverflow.com/questions/6016120/relative-url-to-a-different-port-number-in-a-hyperlink.
Before we set out on covering this use case (we’d probably need to make some noise upstream in the budo repo), I’m still thinking if your problem could be addressed differently. Have you thought of setting up a new record in your /etc/hosts which points at the server’s IP both on your server (myapp.local <IP_ADDRESS>) and on your laptop (myapp.local <the IP address of your server as reachable from your laptop>)?
You could then start elm-live with --host=myapp.local and have your app accessible at http://myapp.local.
Think it makes sense?

I believe webpack uses two ports in a similar fashion, perhaps looking at how it works can be instructive.
The most sensible way to go I can presently think of is to look at the value of http Host header and use the same host specified there. If no Host header is specified then use the listen address as currently happens.

Just updated to 0.19 version of plugin that should fix this issue. If that is not the case please open a new issue! :)


Updates from lantern

should we just go ahead and merge ones like this @oxtoacart?

In this particular case, I think we actually want to keep the other code, so I'm going to close it.


the Accessibility section of the documentation is not well defined can you please help

Accessibility section of the .net api not well defined it only has one definition for all of the members

the rest of the documentation is pretty good

@dend @mairaw Can you take a look at this suggestion?

Do you mean this section https://docs.microsoft.com/en-us/dotnet/api/accessibility, @goswamineelim?

@goswamineelim - could you please clarify where the documentation is not complete?


Fix build with tokio 0.2

I got this to run with minor changes.
Hope this helps!
Cheers
r

@sticnarf I am having a hard time setting up the test env on my machine to reproduce the CI failures. Could you let me know if these are actually my fault? Then I could try to put more effort into finding the problem :)

I'm also confused about it. The test works quite well on my computer.

Once I thought there was something wrong with the CI environment. So I try GitHub actions and nothing changes.
Finally I find the problem is that necessary tokio features are not enabled. I enable full features of tokio in https://github.com/sticnarf/tokio-socks/pull/13 and it passes the tests.
You can try how to minimize the features.

yep, I can confirm that my branch works with full, I'll try and see which feature messes things up when it goes missing.

Ok, I got it down to just my original features + "rt-threaded" in dev-dependencies.

It still fails on travis (in beta, with "Connection refused") but I suspect that's an issue with the test setup.
My branch does not contain the deactivation of parallel tests and of connect_no_auth.

The deactivation of parallel tests and of connect_no_auth is only for my debug :)
I will replace travis with github actions so I will ignore the travis failure. If it fails frequently on GitHub actions, I will try to make it more stable then.

Sure!
Will you create a release from this?


Move latexblock.tmLanguage.json to vscode/extensions/markdown-basics

We had better move latexblock.tmLanguage.json to vscode/extensions/markdown-basics. It should be a part of the built-in extension markdown-basics.
https://github.com/jlelong/vscode-latex-basics/blob/915dddf9753639b0d35332253d5f6326340544ec/syntaxes/latexblock.tmLanguage.json
https://github.com/jlelong/vscode-latex-basics/blob/915dddf9753639b0d35332253d5f6326340544ec/package.json#L185-L195

That would indeed make sense as the markdown grammar already defines fenced code block for many other languages. I guess we should make a PR on https://github.com/microsoft/vscode-markdown-tm-grammar.

See the PR at microsoft/vscode-markdown-tm-grammar#99


Error generating aliases in Edge 115

Extension works fine in FF, installed it in Edge. Configuration is ok, getting an alias E-Mail in this menu. But no alias is generated in normal mode.

Thank you for using the extension. I haven't tested Edge but I found a similar bug when using Chrome. I think the issue is that it's not possible to copy stuff to the clipboard because of Manifest V3. I think it is possible to clone the repo, compile a MV2 version, and install that. I am currently not home but when I get back I will try to fix the issue.

In my understanding, your extension should generate and listing aliases that are transfered to mailcow. The transfer of the examples to the list in mailcow works in FF. But not in the edge extension.


Updated to 0.4.3 and causing issues on iOS and iPadOS

Updated Dataview, and immediately had Obsidian crashing on iOS and iPadOS (phone is on latest non-beta and iPad on 15 public beta). Desktops and laptops okay (1 intel iMac and the other M1 Air).
Disabled all other plugins and themes, reinstalled both Dataview and Obsidian, and still crashing...
Any ideas?

I'm not super familiar with how Electron works on mobile devices - do you see any errors anywhere? It seems wierd that a plugin can just crash Obsidian like that (perhaps a permission issue)/

Can confirm this bug, unfortunately I have had to disable DataView for now. iOS/iPadOS 15.0 Public Beta 6, Obsidian Mobile 1.0.4 and DataView Plugin 0.4.5

I don't have any apple devices to verify this on or see debug output; do you see anything in the developer console / in crash logs?

Not sure what has changed, but 0.4.10 seems to be working fine. iPadOS Developer Beta 8, Obsidian Mobile 1.0.4

Hmm... I'm also not sure what would have changed in between those versions. @socialchap have you seen improvement on the latest version?

I have indeed! Just updated and seems to work perfectly now 👍

Well, I'm not entirely sure what changed, but I'l take it!


Mac build_tests failing on PRs

Pull requests appear to be blocked right now due to an issue with the Mac Build_tests shard.
Some sample runs:
https://ci.chromium.org/ui/p/flutter/builders/try/Mac build_tests/4927/overview
https://ci.chromium.org/ui/p/flutter/builders/try/Mac build_tests/4926/overview
Some affected PRs:
https://github.com/flutter/flutter/pull/72833
https://github.com/flutter/flutter/pull/72829
Also reported by @darrenaustin as blocking additional PRs.

Other example PRs:
#72792
#72838

The problem with those builders have been fixed. Please retry the build on the failing PRs

This was fixed by using xcode 12.3 version.

This was fixed by using xcode 12.3 version.


Long callbacks triggered multiple times when running with multiple processes

Hi there,
we're testing the long_callback to issue somewhat long (several seconds) running SQL queries.
When running with gunicorn with multiple workers I noticed that the queries are started/sent multiple times, from different workers when the polling-requests are routed to a worker which hasn't started the callback in the first place.
A tiny sample that reproduces the issue:
import logging
import os
import sys
import time
import dash
import dash_bootstrap_components as dbc
import dash_core_components as dcc
import dash_html_components as html
import dash_labs
import diskcache
from dash_labs import Input, Output
from dash_labs.plugins import DiskcacheCachingCallbackManager
import multiprocessing

# workaround issues with spawn method on macos
multiprocessing.set_start_method("fork")

worker_pid = os.getpid()

cache = diskcache.Cache("./dash-cache")
app = dash.Dash(
    plugins=[
        dash_labs.plugins.FlexibleCallbacks(),
        dash_labs.plugins.HiddenComponents(),
        dash_labs.plugins.LongCallback(DiskcacheCachingCallbackManager(cache)),
    ]
)
wsgi_app = app.server

app.layout = html.Div(
    [
        dbc.Button(id="button-id", children="Run Query!", n_clicks=0, color="primary"),
        html.P(id="paragraph", children="Click the button")
    ]
)

@app.long_callback(
    output=Output("paragraph", "children"),
    args={"n_clicks": Input("button-id", "n_clicks")},
)
def callback(n_clicks):
    if n_clicks == 0:
        return "Click the button"

    print(f"Starting query on worker {worker_pid}")
    time.sleep(5)
    print(f"Query done on worker {worker_pid}")
    return f"Query done on worker {worker_pid}"

if __name__ == "__main__":
    app.run_server(port=8000, debug=True)

Running that with
gunicorn long_callback_test:wsgi_app --access-logfile - --capture-output --log-file - -w 4 -b :8000

produces something like this:
<IP_ADDRESS> - - [13/Aug/2021:12:11:18 +0200] "POST /_dash-update-component HTTP/1.1" 200 344 "http://localhost:8000/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Safari/537.36"
Starting query on worker 59201
<IP_ADDRESS> - - [13/Aug/2021:12:11:29 +0200] "POST /_dash-update-component HTTP/1.1" 200 326 "http://localhost:8000/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Safari/537.36"
Starting query on worker 59203
<IP_ADDRESS> - - [13/Aug/2021:12:11:30 +0200] "POST /_dash-update-component HTTP/1.1" 200 326 "http://localhost:8000/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Safari/537.36"
Starting query on worker 59202
<IP_ADDRESS> - - [13/Aug/2021:12:11:31 +0200] "POST /_dash-update-component HTTP/1.1" 200 326 "http://localhost:8000/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Safari/537.36"
<IP_ADDRESS> - - [13/Aug/2021:12:11:32 +0200] "POST /_dash-update-component HTTP/1.1" 200 326 "http://localhost:8000/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Safari/537.36"
Starting query on worker 59197
<IP_ADDRESS> - - [13/Aug/2021:12:11:33 +0200] "POST /_dash-update-component HTTP/1.1" 200 326 "http://localhost:8000/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Safari/537.36"
Query done on worker 59201
<IP_ADDRESS> - - [13/Aug/2021:12:11:34 +0200] "POST /_dash-update-component HTTP/1.1" 200 344 "http://localhost:8000/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Safari/537.36"
Query done on worker 59203
Query done on worker 59202
Query done on worker 59197

I that a known issue/limitation with the diskcache or am I doing something wrong here?
Would using the celery backend solve this?

Thanks for the report and example @sebbegg. We'll get this fixed before long_callback is integrated into Dash for Dash 2.

@jonmmease - was this fixed?

@T4rk1n would you please test this and verify whether it's still an issue?

I confirm this is fixed.


Comparison of by-ref single-variant nullary tag does not work

tag chan {
    chan_t;
}

fn wrapper3(i: chan) {
    log_err i;
    assert i == chan_t;
}

fn main() {
    wrapper3(chan_t);
}

log displays a number that looks like garbage and the assert fails. Possibly the same issue as #1034

Actually, I don't know whether i is passed by-ref, but I remember when I changed the passing convention it worked.


build: move -c functionality to aur-chroot, add --addpkg

Some preliminary steps for aur-chroot:

Run as root. For compatibility with previous command-lines, use exec sudo ... (cf. https://gitlab.archlinux.org/archlinux/devtools/-/blob/master/lib/archroot.sh#L13-22).
Remove the unprivileged packagelist functionality. Replace with an option that prints the path to the container makepkg.conf. Then this path can be checked by aur-build.

From a user perspective, having chroot builds as an extra -c flag in aur-build is quite convenient. This makes aur-build a higher-level tool that calls aur-chroot. However, from a technical perspective I wonder if it shouldn't be the other way around: aur-chroot calls all necessary devtools commands, and runs aur-build for unprivileged tasks (local repository updates, gpg signing, and other possible tasks like running namcap). aur-build would then have no special distinctions (or options) for the container case, resulting in more general code overall.
One difficulty is how to call aur-build without it building anything. Package signing (and other potential parts of the transaction, such as running namcap) should still be handled and cannot be skipped like in #839.
Originally posted by @AladW in https://github.com/AladW/aurutils/issues/907#issuecomment-1055780519

Splitting off pieces from aur-build made me realize the failings of moving aur build -c to aur chroot. First, too much functionality needs to be replicated  (e.g. makepkg --pkglist, gpg signing, queue handling) that is useful for both makepkg and makechrootpkg builds.
A separate helper didn't help with this, apart from an aur-build--pkglist as a faster version of makepkg --packagelist which, like makepkg, can be run with setpriv (#907).
A flag like --addpkg may still be useful and could be implemented relatively easily:
# ensure main loop is only run once if a list of packages is supplied
if [[ -v queue ]] && [[ ! -v package_queue ]]; then
    exec {fd}< "$queue"
else
    exec {fd}< <(printf '\n')
fi

...
pkglist = ()
if [[ -v package_queue ]]; then
    mapfile -t pkglist < "$package_queue"
elif (( ! overwrite )); then
    unset exists
...

An additional consideration is that package paths may either be in the local repository root, elsewhere, or both. I think it's better to implement these kinds of distinctions in a dedicated tool like repo-addpkg (see https://github.com/AladW/repoutils).


SapiEmitter, additional cases for not sending content length

If there's Transfer-Encoding header, 1xx, 204, 304 response code or when request type is CONNECT (we may ignore this one) - don't send Content-Length.

I suggest replacing the $withoutBody parameter with the $request object parameter in the EmitterInterface::emit() method.
https://github.com/yiisoft/yii-web/blob/13b097a1afa6c1b18ac53ab1ef327bee3b929c45/src/Emitter/EmitterInterface.php#L12-L17

Why? It's not required for any of the conditions above.

Why? It's not required for any of the conditions above.

Could be a separate issue theme rather. If ignore the method condition, then obviously it would not be necessary.

when request type is CONNECT (we may ignore this one)

Defining the interface is weird, as it outsources the decision power from sapi to work properly with the data included in the request eg. HEAD or CONNECT methods. Instead, you have to rely on the $withoutBody parameter, which I don't know how it will function if, for example, I use my own non-standard method (eg API server LIST method).

Fixed by #175


bcc/bpftrace tools for throughput numbers

Would be a nice feature to include tools that measure parameters like throughput, iops, etc.

Hmm, isn't most of that information available via procfs already? Gonna need more specifics here to do anything actionable.


Create load balancer for service in same project as cluster

I created a Kubernetes cluster using Terraform. Since the DigitalOcean Terraform provider does not yet support the urn attribute for the digitalocean_kubernetes_cluster resource, I manually moved the cluster and droplets to a different project. Afterwards I created an nginx ingress via Terraform and its Helm provider. The load balancer that the DigitalOcean cloud provider created for the type: LoadBalancer service of the nginx ingress Helm chart appeared in the default project.
It would be nice if the load balancer was created in the same project as the cluster, ideally following the cluster when it is moved through projects.
An alternative new feature would be to allow specifying the project as an annotation to the nginx ingress service (which I can set via the Helm chart -- I already do that for service.beta.kubernetes.io/do-loadbalancer-name, cf. https://docs.digitalocean.com/products/kubernetes/how-to/configure-load-balancers/) This could be a new service.beta.kubernetes.io/do-loadbalancer-project-name: "my-project-name" annotation.
Another alternative would be to create the load balancer using the digitalocean_loadbalancer Terraform resource, which does support the urn attribute and can thus be moved to a specific project. Afterwards I could set the kubernetes.digitalocean.com/load-balancer-id annotation on the nginx ingress service to make it use the existing load balancer instead of creating a new one. However, this would require me to configure a forwarding_rule for this resource, which would conflict with the configuration set by the cloud provider.

Hey @devurandom 👋
The LB should be assigned the same project as the cluster on creation (assuming it is created through Kubernetes based mechanisms). It should also move with the cluster to the new project it gets assigned to. You will not be able to view or modify an LB via Projects (cloud webpage for your project or doctl) since it is a resource for a DOKS cluster and is expected to be interacted with through Kubernetes.
If the cluster owned LB isn't moving over and/or the LB is being created for your cluster but the LB gets assigned to the default project instead of the correct one. This is a bug. Can you please file a support ticket with this information and any screenshots you may have? Thank you very much for bringing this to our attention!

Closing this one out assuming it's been addressed. If not, then please file a support ticket as requested.


upgrade go verstion 1.21 to fix CVE-2024-24790

resolved #433
What type of PR is this?

/kind bug
What this PR does / why we need it:
fix CVE-2024-24790
Which issue(s) this PR fixes:
Fixes #433
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

+1

/lgtm
thx your contribution

trriger

/approve

/approve

/approve

/lgtm /force


Security Issue: Request for contact

Hello,
The GitHub Security Lab team has found a potential vulnerability in your project. Please create a Security Advisory and invite me in to further disclose and discuss the vulnerability details and potential fix. Alternatively, please add a Security Policy containing a security email address to send the details to.
Kind regards,
A

Hi @pwntester !
Thank you so much for contacting me! Sorry about the late response; I've been struggling a lot during the pandemic.
I'd love to hear the details about this at<EMAIL_ADDRESS>, and added a security policy.
(I don't have admin rights to make security advisories on the repo as I no longer work at Khan Academy, but I continue to be the maintainer for this project)

Hi @pwntester !
Thank you so much for contacting me! Sorry about the late response; I've been struggling a lot during the pandemic.
I'd love to hear the details about this at<EMAIL_ADDRESS>, and added a security policy.
(I don't have admin rights to make security advisories on the repo as I no longer work at Khan Academy, but I continue to be the maintainer for this project)

Thanks, just sent you the report

Thanks, just sent you the report

Fixed in #95 / version 0.7.3
Thanks again @pwntester !

Fixed in #95 / version 0.7.3
Thanks again @pwntester !


[resoto][chore] Bump 3.3.2

Description
Bump 3.3.2
Code of Conduct
By submitting this pull request, I agree to follow the code of conduct.

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (86f18d1) 88.95% compared to head (5d551c6) 88.95%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1534   +/-   ##
=======================================
  Coverage   88.95%   88.95%
=======================================
  Files          77       77
  Lines       12117    12117
=======================================
  Hits        10779    10779
  Misses       1338     1338

Flag
Coverage Δ

resotocore
88.95% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

resotocore/resotocore/__init__.py
100.00% <100.00%> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Negative numbers issue

I tried to compile the following program:
package main

import "external"

func main() {
	foo := -4
	external.Printf("foo is = %d\n", foo)
}

It failed with the following panic
2019/03/23 19:40:45 unable to handle default: 16 - {Type:OPERATOR, Val:-, Line:6}
panic: unable to handle default: 16 - {Type:OPERATOR, Val:-, Line:6}

Wow, I’m surprised to have a user of this program!
Thanks for the bug report. 🙂


PersistentBottoomSheet default content provider and make styles configurable

Current Bottomsheet requires layout to be written by consumer end. Adding a default and configurable layout source just by applying list if Items.

Default content builder has been added - https://github.com/microsoft/fluentui-android/blob/fbf5e5bc5b613c5b3aa2ae5f5416368f0b70d2f2/fluentui_drawer/src/main/java/com/microsoft/fluentui/persistentbottomsheet/PersistentBottomSheet.kt#L373C5-L397C34
Hence closing this issue! Thanks!
cc: @Dhoot


Remove feature flag to tag documents to taxonomy

This commit reverts https://github.com/alphagov/govuk-puppet/pull/5361
We no longer need this feature flag.
Depends on https://github.com/alphagov/whitehall/pull/3138 before it gets merged.
Trello:
https://trello.com/c/dBDSxqtJ/497-make-tagging-to-taxons-mandatory-with-special-cases-for-parenting-and-corporate-information

This can now be merged and deployed


Add an integration test for the /search route

The SearchAPI class was exploding a bit, so here it is covered by an integration test with WebMocked data. This should ensure a smoother upgrade path for the GdsApiAdapters.
The unit test was mainly testing a complex system of mock objects, so that's gone.

The fixture files are pretty massive and hard to read. Would it be possible to reduce those to more toy-like examples so it's clearer what to watch out for in the tests?

Will anyone ever want to read the fixture json?

Nice! Merging


feat(readme): ✨ Add ability to generate a readme file

Background
Short description of issue being resolved or a feature being added.
Problems Encountered / Decisions Made / Potential Solutions Abandoned
Any problems you had when working on the PR and what decisions or trade-offs you had to make.
Check List

[ ] Added tests for all new code.
[ ] Added comments and documentation for new code.

Superseeded by https://github.com/daveshepherd/projen-modules/pull/32


Do you plan to create a NavigationBarPage ?

Do you plan to create a NavigationBarPage for the NavigationBar that appeared in Flutter 3.0?
I hope it can be used like TabPage or CupertinoTabPage.

Hello, good news, there's no need for one 😁
NavigationBar doesn't require a controller, so you can use the existing IndexedPage.
I've added an example: https://github.com/tomgilder/routemaster/tree/main/example/navigation_bar