Fix #57910 - Add setting for auto fetch timeout

Finishes the race condition when either setting is changed, and then if it wasn’t disabled creates a new timeout using the new value (instead of waiting for it to go through the loop again to update).

Changed the unit to seconds instead of minutes. Also cleaned up all that complexity of resetting the machine when that value changes. It's more than OK to just wait until the next auto fetch gets triggered to trigger a new one with the new delay.
Thanks! :fireworks:


How to insert empty array

When I insert empty array ( [] in Javascript ), it always throw NPE.

Javascript? What do you mean? How it's related to JDBC?

Please clarify or close. These common options are available to JDBC users:
Raw:
connection.createStatement().execute("INSERT INTO db.table (col) VALUES ([])");

Prepared statement using Object array directly:
PreparedStatement stmt = connection.prepareStatement("INSERT INTO tb.table (col) VALUES (?)");
stmt.setObject(1, new Integer[0]);
stmt.execute();

Prepared statement using JDBC Array mechanism (not very popular outside Oracle world, I think):
PreparedStatement stmt = connection.prepareStatement("INSERT INTO db.table (col) VALUES (?)");
stmt.setArray(1, connection.createArrayOf("Int32", new Integer[0]));
stmt.execute();


Turn posting to social media into a github action with a webhook

lambda function timeouts are too slow to wait for post to finish

@voodoohop heyhey, I was thinking about this issue and thought about what will happen if multiple users try to trigger post uploads at the same time. I started thinking maybe github actions are not the best for this. Maybe we can use the same server with IPFS for this task too?


Add satellite basemap

Overview
This PR adds the satellite basemap and implements dynamic switching with the basemap setting in state.
Closes #36
Notes
react-leaflet does not allow the url prop on TileLayers to be mutable. This PR implements custom basemap components that add/remove layers in sync with the React element lifecycle.
Testing Instructions

On welcome page:

[x] Ensure background basemap is unaffected

On draw map page:

[x] Switch between the two basemap types from the sidebar

Checklist

[ ] fixup! commits have been squashed
[ ] CHANGELOG.md updated with summary of features or fixes, following Keep a Changelog guidelines
[ ] README.md updated if necessary to reflect the changes
[ ] CI passes after rebase

Taking a look now

This works really well, nice job figuring out how to do it in a react-y way.
Since we have multiple pieces of information related to a given basemap, I think we should try to put them in a central place. Something like this perhaps:
diff --git a/src/app/src/components/Basemaps.js b/src/app/src/components/Basemaps.js
index 6c37fbc..eabcdbe 100644
--- a/src/app/src/components/Basemaps.js
+++ b/src/app/src/components/Basemaps.js
@@ -32,3 +26,21 @@ function Basemap({ url, attribution }) {
         };
     }, [map, url, attribution]);
 }
+
+export const BASEMAPS = {
+    default: {
+        component: (
+            <Basemap url={DEFAULT_BASEMAP_URL} attribution={ESRI_ATTRIBUTION} />
+        ),
+        maxZoom: 16,
+    },
+    satellite: {
+        component: (
+            <Basemap
+                url={SATELLITE_BASEMAP_URL}
+                attribution={ESRI_ATTRIBUTION}
+            />
+        ),
+        maxZoom: 18,
+    },
+};

diff --git a/src/app/src/components/DrawMap/DrawMap.js b/src/app/src/components/DrawMap/DrawMap.js
index 7a21e48..7c6609c 100644
--- a/src/app/src/components/DrawMap/DrawMap.js
+++ b/src/app/src/components/DrawMap/DrawMap.js
@@ -2,7 +2,7 @@ import { Button, Icon } from '@chakra-ui/react';
 import { useSelector } from 'react-redux';
 import { ArrowRightIcon } from '@heroicons/react/outline';

-import { DefaultBasemap, SatelliteBasemap } from '../Basemaps';
+import { BASEMAPS } from '../Basemaps';

 import Map from '../Map';
 import EditToolbar from './EditToolbar';
@@ -25,14 +25,11 @@ export default function DrawMap() {
 function Basemap() {
     const basemapType = useSelector(state => state.map.basemapType);

-    switch (basemapType) {
-        case 'default':
-            return <DefaultBasemap />;
-        case 'satellite':
-            return <SatelliteBasemap />;
-        default:
-            throw Error(`Invalid basemap type: $basemapType`);
+    if (!(basemapType in BASEMAPS)) {
+        throw Error(`Invalid basemap type: ${basemapType}`);
     }
+
+    return BASEMAPS[basemapType].component;
 }

 function SaveAndBackButton() {
diff --git a/src/app/src/components/DrawMap/MapFeatures.js b/src/app/src/components/DrawMap/MapFeatures.js
index fe825d6..794ca1d 100644
--- a/src/app/src/components/DrawMap/MapFeatures.js
+++ b/src/app/src/components/DrawMap/MapFeatures.js
@@ -2,6 +2,7 @@ import { useEffect } from 'react';
 import { useSelector } from 'react-redux';
 import { useMap } from 'react-leaflet';

+import { BASEMAPS } from '../Basemaps';
 import useEditingPolygon from './useEditingPolygon';

 export default function MapFeatures() {
@@ -16,12 +17,8 @@ function useSetMaxZoomLevel() {
     const map = useMap();

     useEffect(() => {
-        switch (basemapType) {
-            case 'default':
-                map.setMaxZoom(16);
-                break;
-            default:
-                map.setMaxZoom(18);
+        if (basemapType in BASEMAPS) {
+            map.setMaxZoom(BASEMAPS[basemapType].maxZoom);
         }
     }, [basemapType, map]);
 }

This looks odd though:
diff --git a/src/app/src/pages/Welcome.js b/src/app/src/pages/Welcome.js
index 73563f0..9b5e48d 100644
--- a/src/app/src/pages/Welcome.js
+++ b/src/app/src/pages/Welcome.js
@@ -1,14 +1,12 @@
 import Map from '../components/Map';
 import WelcomeModal from '../components/WelcomeModal';
-import { DefaultBasemap } from '../components/Basemaps';
+import { BASEMAPS } from '../components/Basemaps';

 export default function Welcome() {
     return (
         <>
             <WelcomeModal />
-            <Map>
-                <DefaultBasemap />
-            </Map>
+            <Map>{BASEMAPS['default'].component}</Map>
         </>
     );
 }

so perhaps this approach can't be taken all the way, and there is still value in having DefaultBasemap be a component.
Any thoughts on this arrangement?

Any thoughts on this arrangement?

It's not an approach I'm familiar with, but it seems like it would work. When the BASEMAPS object is imported, it doesn't render those components, right? I would assume just the function reference is imported and it won't be run until the virtual DOM finds it.
Alternatively, we could incorporate the zoom level into the <Basemap /> component as a prop:
export function DefaultBasemap() {
    return (
        <Basemap
            url={DEFAULT_BASEMAP_URL}
            attribution={ESRI_ATTRIBUTION}
            maxZoomLevel={16}
        />
    );
}

export function SatelliteBasemap() {
    return (
        <Basemap
            url={SATELLITE_BASEMAP_URL}
            attribution={ESRI_ATTRIBUTION}
            maxZoomLevel={18}
        />
    );
}

function Basemap({ url, attribution, maxZoomLevel }) {
    useSetMaxZoomLevel(maxZoomLevel);
    const map = useMap();

    useEffect(() => {
        const layer = L.tileLayer(url, { attribution });
        map.addLayer(layer);

        return () => {
            if (map.hasLayer(layer)) {
                map.removeLayer(layer);
            }
        };
    }, [map, url, attribution]);
}

Adding the zoom level parameter to useMaxZoomLevel should be simple.

I like the approach you outlined above. Let's try that.

I like the approach you outlined above. Let's try that.

aa0337f

The code looks good. What is the source of the new green "Default" map thumbnail? It doesn't look like the gray basemap.

What is the source of the new green "Default" map thumbnail? It doesn't look like the gray basemap.

It's what Gates sent in the slack channel. I think it's closer to what the ideal basemap would look like.


"preferredFormat" property does not return correct formats

If I feed the picker an array of RGBA color values it will correctly interpret the colors however will later feed them back as a hex value even if the color was not changed.

I suspect the problems is these lines:
var updateFunction = function(newColor) {
  self.set('color', newColor.toHexString());
};

I'll look into it.

I changed the above code to respect the specified preferredFormat or the format inferred from the initial value as of 0.1.0. Let me know if that fixes your problem.

That worked! The only caveat is that it will convert a rgba with an "a" value of 1 to it's basic rgb equivalent. so 'rgba(51,160,44,1)' gets returned/updated as 'rgb(51,160,44)' which is the same color however if you're expecting an rgba later for color manipulation it can screw things up.
Probably still fair to close the issue though.

Thanks for the feedback! Rgba with an alpha of 1 getting converted into the rgb value is would be an issue with spectrum.js itself I think. Anyway, thanks again for bringing up this issue!


Added env path in debugger

Related Issue

[docs]: adding env path in debugger

Issue: keploy/keploy#1574

Describe the changes you've made
Incorporating the addition of the "env" field in the debugger configuration to specify the path to the Go binary.
Type of change

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

Please let us know if any test cases are added
NA
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
NA
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] New and existing unit tests pass locally with my changes.

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

Hey @Ajeett01 thanks for creating the PR but the issue has been solved by PR https://github.com/keploy/docs/pull/337. Do checkout other issues! Looking forward to your contributions

Hey @Ajeett01 thanks for creating the PR but the issue has been solved by PR #337. Do checkout other issues! Looking forward to your contributions

Ok , I will look for other issues.


Fixes issues #177 and #178

I haven't been able to build it or test because I'm already on VS2017. I don't want to go upgrading your projects.

Thanks for this PR, will have a look at it. Yes, this is still VS2015-, project.json-based and it will probably stay like that for now (integrating with VS2017, of course, is another thing).

Heads up: putting together a couple of tests for issues you found, to also confirm fixes.

Collectively, this PR should fix issues #176, #177 and #178


build: update CSI_IMAGE_VERSION in deploy.sh

update deploy.sh to use correct CSI_IMAGE_VERSION from the build.env.
Signed-off-by: Madhu Rajanna<EMAIL_ADDRESS>

v3.2.0 build is failing to push the helm charts this Fix is needed see https://travis-ci.org/github/ceph/ceph-csi/builds/748529032

Merging this one to unblock release

@mergifyio backport release-v3.2


[Metaschedule] Add utility API to ease using manual schedules

As discussed in https://github.com/apache/tvm/pull/10856#discussion_r840324560, add a utility under meta_schedule/testing/utils.py to clean up the database boilerplate. Also using DummyDatabase instead of JsonDatabase for further clean up, as suggested by @junrushao1994 .
@junrushao1994 @zxybazh

@junrushao1994 ready for review.


full_name function broken

julia> full_name(Species("He"))
ERROR: DimensionError: 2 and 0 e are not dimensionally compatible.
 Also changing the name of the function to nameof would be in keeping with the naming of the other functions.

Very odd. In my environment it works for everything. Nameof is also exported by Julia.base, so full_name is an easier choice.

On Dec 12, 2024, at 2:20 PM, David Sagan @.***> wrote:
@rot4te https://github.com/rot4te full_name still is broken for atomic species (but sub-atomic is OK). Also changing the name of the function to nameof would be in keeping with the naming of the other functions.
—
Reply to this email directly, view it on GitHub https://github.com/bmad-sim/AtomicAndPhysicalConstants.jl/issues/107#issuecomment-2539829184, or unsubscribe https://github.com/notifications/unsubscribe-auth/APVF2CGXE3534IHP66A6QB32FHOZJAVCNFSM6AAAAABTAWTFLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZZHAZDSMJYGQ.
You are receiving this because you were mentioned.

Yes, and I fixed that (by species.charge.val == -1) locally, and thought it was included in my push. Guess I’ll check it again.

On Dec 12, 2024, at 3:23 PM, David Sagan @.***> wrote:
@rot4te https://github.com/rot4te Looks like the problem is that in the full_name function something like:
elseif species.charge == -1
is trying to compare species.charge which has units with -1 which does not have units.
—
Reply to this email directly, view it on GitHub https://github.com/bmad-sim/AtomicAndPhysicalConstants.jl/issues/107#issuecomment-2539946175, or unsubscribe https://github.com/notifications/unsubscribe-auth/APVF2CA2C5DPEXOERM4L3C32FHWFPAVCNFSM6AAAAABTAWTFLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZZHE2DMMJXGU.
You are receiving this because you were mentioned.


Black screen only on Android devices

**UE Version: **
UE 5.1.1
**Frontend Version: **
UE5.1
Description
Hello everyone. I have a project that I play in streaming from editor by using the external Pixel streaming Signalling server available from this repository.
It works from pc and IOS devices, but from Android devices it does not work as expected. When I click on "Click to start" then play button it remains on black screen.
I tried to start the "Start_WithTURN_SignallingServer" but nothing changed.
I tried with the last version of PixelStreamingInfrastucture, and it goes stuck on "WEBRTC CONNECTED, WAITING FOR VIDEO" display.
It does not work neither from the same network nor other networks.
I can give you additional information if you need.
Thank you.
UPDATE
Tried with Android 10 version and it works, it does not work with Android 12 and 13 (11 not tested)

I have tested with a Samsung Galaxy S21 on Android 13 using editor streaming and "Start_WithTURN_SignallingServer" with no issues. This was on a local network.
Is there any further information on the Android device you are using? The black screen issue usually means the streamer is unable to make a connection to the browser. Perhaps there's some kind of fire walling going on or the network configuration is different?


GH-2171 AST nodes now determine if node is scope change

GitHub issue resolved: #2171
Briefly describe the changes proposed in this PR:

TupleExprBuilder uses this to build algebra tree with correct settings
GraphPatternGroupable renamed to VariableScopeChange
easier to distinguish corner cases at correct abstraction level
added regression test for handling of values clause and named graphs

PR Author Checklist:

[x] my pull request is self-contained
[x] I've added tests for the changes I made
[x] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change
[x] every commit has been signed off

Note: we merge all feature pull requests using squash and merge. See RDF4J git merge strategy for more details.

There are apparently issues with Github Actions at the moment, which is probably why the CI build is not starting.

Fwiw I've ran the complete build verification locally on this branch, and it was green.

Btw. You've added a new interface without default methods, so I don't think think this is backwards compatible.

Also there are test failures on develop now.
And some of the plans in the QueryPlanRetrievalTest have changed performance.

Btw. You've added a new interface without default methods, so I don't think think this is backwards compatible.

The only implementation of the interface is our own AbstractValueNode, which of course has implementations, so this is not incompatible.

Also there are test failures on develop now. And some of the plans in the QueryPlanRetrievalTest have changed performance.

Taking a closer look at the failing tests now.

select ?a where {
    ?a ?b ?c,?d.
    FILTER(?c != ?d)
    ?d ?e ?f.
}

Projection (resultSizeActual=2)
   ProjectionElemList
      ProjectionElem "a"
   Join (HashJoinIteration) (resultSizeActual=2)
      StatementPattern (costEstimate=3, resultSizeEstimate=12, resultSizeActual=12)
         Var (name=a)
         Var (name=b)
         Var (name=d)
      Filter (resultSizeActual=140)
         Compare (!=)
            Var (name=c)
            Var (name=d)
         Join (JoinIterator) (resultSizeActual=144)
            StatementPattern (costEstimate=2, resultSizeEstimate=12, resultSizeActual=12)
               Var (name=a)
               Var (name=b)
               Var (name=c)
            StatementPattern (costEstimate=5, resultSizeEstimate=12, resultSizeActual=144)
               Var (name=d)
               Var (name=e)
               Var (name=f)

Seems that FILTER is always introducing a new scope now.

New PR up with a fix. See #2178


added linking instructions

Added notes to developing.md  outlining how to link / unlink the package during development.

Thanks for the contribution, @lklepner


Feature: iCloud Drive and Photos namespace detection

Resolved / Related Issues
Items resolved / related issues by this PR.

Changes iCloud Drive to use namespace detection, so it can detect a moved iCloud Drive location.
Changes "iCloud" to "iCloud Drive" for consistency. (Drive is a service within iCloud and not the entirety of the service)
Closes #10805

Validation
How did you test these changes?

[x] Built and ran the app
[ ] Tested the changes for accessibility

Screenshots (optional)

LGTM


[Storybook - Async Examples] Cannot read source code or how to use

Hello,
I want to see how the data table can be used in an Async environment.
However, the source code of the Async examples cannot be displayed. The following is an example:
https://imballinst.github.io/react-bs-datatable/?path=/story/controlled--async-pokemon
Can you help me?
Thank you!

Hello @twlai, apologies for the late reply!
Here is the source for the Async Pokemon one:
https://github.com/imballinst/react-bs-datatable/blob/59e1fbe617b0a184b6149fa868289bedf8084a84/src/__stories__/01-Controlled.stories.tsx#L43-L70
The AsyncTable is also implemented in the same file, which fires the fetchFn every time the page changes (unfortunately I think the API doesn't support text filter and sort):
https://github.com/imballinst/react-bs-datatable/blob/59e1fbe617b0a184b6149fa868289bedf8084a84/src/__stories__/01-Controlled.stories.tsx#L213-L324
The fetchFn function is implemented at the end of the file:
https://github.com/imballinst/react-bs-datatable/blob/59e1fbe617b0a184b6149fa868289bedf8084a84/src/__stories__/01-Controlled.stories.tsx#L326-L343


Help in integrating with editors (newlines are handled weirdly)

I am trying to use euporie-console to have a nice graphical interactive python repl next to my editor (neovim).
I tried to use the Kitty terminals kitty @ send_text to send selected code to the terminal that euporie-console is running in, but I am having some problem with newlines. sending \r acts like hitting enter which starts running the code but the next line is already sent and simply gets appended to the current line. And somehow euporie ends up trying to run this concatenated line, resulting in a syntax error
import numpy as np
from matplotlib import pyplot as plt

ends up being sent as
import numpy as npfrom matplotlib import pyplot as plt
                  ^ lost newline

Is it possible to have newlines in a long sequence of text be handled properly? Text after a \r but before the current line has actually started finished executing should go into a new line, ideally in the same chunk

Hello,
That sounds like a pretty cool workflow!
You'll need to use bracketed paste to get this working:

Send \cc to clear euporie's input box before sending anything
Send \x1b[200~ before your code;
Send your code;
Send \x1b[201~ after your code;
Send \x1b[13;5u to run the code (Ctrl-Enter).

\x1b[13;5u will always run whatever is entered, whereas \r will only run what is entered if it passes the kernel's code-completeness check.
For example:
kitty @ send-text --all --exclude-active '\cc\x1b[200~print(123)\nprint(456)\x1b[201~\x1b[13;5u'

I hope that you get it working!

Thanks for the tip about bracketed paste! that works great.
You seem pretty knowledgeable so can I ask, is there a good utility/library for converting keypresses into those csi/escape codes? or somewhere to learn all the details necessary to make one myself?

The VT100 user guide always makes a nice bit of light reading:
https://vt100.net/docs/vt100-ug/chapter3.html#S3.3
There's also a wikipedia page on control-codes which might be a bit more accessible:
https://en.wikipedia.org/wiki/C0_and_C1_control_codes
You might want to read the wikipedia page on ansi escape sequences first for a bit of background:
https://en.wikipedia.org/wiki/ANSI_escape_code#Fe_Escape_sequences
Here's a couple of pages on modern terminal keyboard input:
http://www.leonerd.org.uk/hacks/fixterms/
https://sw.kovidgoyal.net/kitty/keyboard-protocol/
If you run stty raw -echo; cat -v, your terminal will print escaped key-press escape sequences.


-webkit-overflow-scrolling:touch breaks dragging on iOS

Problem:
When a draggable container has overflow:auto and the container or any parent container has -webkit-overflow-scrolling:touch, the dragged ghost element is constrained to the drag container.
A reproducer is not possible at this time since this bug is masked by #1671.

As pointed out by @owen-m1 , fallbackOnBody:true avoids this problem, though presumably you still shouldn't set -webkit-overflow-scrolling:touch on body.


Show tcp remote address when it is a client

resolves https://github.com/reaktivity/command-log.java/issues/11

@dpwspoon please do a catch-up merge and also follow the approach used by http extension metadata processing for tcp extension metadata processing.

TCP extension metadata now available when verbose.


Debug the fact that Verilator is taking a while

I used flamegraph, attaching the result here.

It seems like it has to do with the use of threads by Verilator. I bet we could just disable threads and it would help a lot.

I'm really confused why there's any threading activity happening at all! It doesn't really make sense to me.

https://stackoverflow.com/questions/67335512/multithreaded-simulation-orders-of-magnitude-slower-than-single-threaded
This makes me think that it is possible to entirely disable threading, somehow. Am I seeting VL_THREADED somewhere? I feel like I am.

Asking a question here: https://github.com/verilator/verilator/issues/4526

Wilson's suggestions:

Use numactl. This seems annoying to have to do -- it seems weirdly machine-specific and hand-optimized given that I'm just trying to get Verilator simulations to run at their single-threaded max performance.
Don't share VerilatedContexts. I'm already not doing this.

I also considered doing everything inside of a Verilog testbench, i.e. not using a C++ testbench. This now runs into the issue of needing to use the --timing flag, which then requires a certain C++ compiler, and now I can't figure out how to make Verilator use Clang...what a mess.
I feel like the easiest solution would just be to figure out how to make the C++ run faster, ideally not using numactl.

The other short term and very non-ideal solution is to just to run fewer simulations.
We could also downgrade Verilator, because I'm pretty sure this was not a problem in previous versions.

Okay, so I put everything in a Verilog testbench and it's much faster. Had to force it to use a more recent compiler with
make -B simulate_new CXX=g++-10

Makefile lines:
simulate_new: /home/gus/lakeroad-evaluation/out/robustness_experiments/mult_0_stage_signed_8_bit/lakeroad_xilinx_ultrascale_plus/verilator/testbench_new /home/gus/lakeroad-evaluation/out/robustness_experiments/mult_0_stage_signed_8_bit/lakeroad_xilinx_ultrascale_plus/verilator/testbench_inputs.txt
	/home/gus/lakeroad-evaluation/out/robustness_experiments/mult_0_stage_signed_8_bit/lakeroad_xilinx_ultrascale_plus/verilator/testbench_new < /home/gus/lakeroad-evaluation/out/robustness_experiments/mult_0_stage_signed_8_bit/lakeroad_xilinx_ultrascale_plus/verilator/testbench_inputs.txt

/home/gus/lakeroad-evaluation/out/robustness_experiments/mult_0_stage_signed_8_bit/lakeroad_xilinx_ultrascale_plus/verilator/testbench_new: testbench.sv /home/gus/lakeroad-evaluation/robustness-testing-verilog-files/generated/mult_0_stage_signed_8_bit.sv ../lakeroad_result.sv
	$(VERILATOR) --cc --build --exe --timing --main \
	  -I/home/gus/lakeroad-evaluation/lakeroad-private/DSP48E2 \
		-DXIL_XECLIB -Wno-UNOPTFLAT -Wno-LATCH -Wno-WIDTH -Wno-STMTDLY -Wno-CASEX -Wno-TIMESCALEMOD -Wno-PINMISSING \
		-CFLAGS -std=c++2a \
    $^
	cp obj_dir/Vtestbench $@

I'm thinking the problem is likely due to the fact that we're remaking the context/module in a loop. I think that's probably slow.
If we go the Verilog route, then we'll use the same module the whole time, which I'm not sure how I feel about. It's probably fine if we're assuming intermediate outputs shouldn't matter/existing state shouldn't matter.

Note that this issue led to another that i'm working on first:
https://github.com/uwsampl/lakeroad/issues/372

Done! The eval still runs slowly (see #124) but Verilator is much faster.


Top section of web browser doesn't get taps

Hi All,
Ignacio asked me to take a look at this issue:
https://jasonette.slack.com/archives/C2PUV4Z99/p1572273132053100?thread_ts=1563782847.002700&cid=C2PUV4Z99
When I did I noticed that there's a recyclerview that's created to use when the 'items' in the json of the body are defined.  If there are no items as in Ali's script, the recyclerView still takes up a default space, even though it's got nothing in it.
I noticed that where the list of items is set (JasonViewActivity.java:setup_sections():2191) if we hide the listview when the list size is zero, the problem goes away.
I'm a complete jasonette newbie, so I don't know if this will cause folks any trouble, and so should be taken with a huge grain of salt.
I forked the repo, and have crated a PR called bug/ZeroItemsBlockFix.  I have tried to create a PR for what seems appropriate branches.  Again, a total newbie here.  I'm not even sure if it can be seen (I can't see it from my PoV.
Feedback gratefully accepted.
-Ken

Hello, please make this in the @jasonelle repository. since this repo is not maintained anymore :) thanks.

The pull request made it into jasonelle, but (and perhaps this is a permissions issue), I cannot see an 'issue' tab in jasonelle/jasonette-android.

@kcorey yes. all the issues should be put inside https://github.com/jasonelle/jasonelle repo so is easier to track all the components in a single repo :) thanks.


What is the future of virtual-dom?

I, and I think many others, are looking to put virtual-dom in production as a much smaller but equally efficient implementation of the virtual DOM concept React made popular.
That said, it's hard to find information on the future of this package. It would be nice to have some assurance this package is under continual maintenance with plans for the future.
Some specific questions are:

What are the vdom and vtree packages on NPM? They appear to be by the same author. Will they ever be maintained?
Will submitted pull requests with bug fixes get merged?
Is this package considered stable? The README says experimental and it also says the build is failing.
Could a new contributor be added? Maybe @staltz or someone else with experience who could help review PRs?

See also #332

+1 for this. Additionally, I'm part of a minority who prefer es5 and would like to know --will virtual-dom remain es5-compatible?

Will, sure, will.


Dynamic setters are now shared between types

Following up on #65, this PR makes dynamic setter methods shared between all types.
My first try at implementing this kept creating the setters type in PropertyAssignmentEmitter, but this posed several problems:

The setters type must be "top level enough" to be accessible by all compiled types. Thus it can't be a sub type of the current type (potentially nested private). Defining one directly at the assembly level seemed wrong since only the compiler caller knows where it wants the types to be created.
It was hard to define when to call CreateType (effectively building the type for SRE) on the setters type, since it needs to be shared between several compilation calls.

Instead, this implementation requires the caller to define the setters type itself and pass it to the compiler. The caller can define the type as it sees fit and controls its sharing between calls and its final creation. This is very similar to what Avalonia already does for its extra generated XAML types (XamlIlHelpers, XamlILTrampolines, etc.).
The only downside is that this type can be seen as an implementation detail: another non-IL backend emitter might not need it. I think the pros outweigh the cons, and that a potential other implementation might still want to use this type to define its setters.
After this PR, Avalonia.Themes.Fluent without fonts goes from 815 KB (337 setters) to 774 KB (19 setters).

Defining one directly at the assembly level seemed wrong since only the compiler caller knows where it wants the types to be created.

We could provide a callback, so it shouldn't be a problem.

It was hard to define when to call CreateType (effectively building the type for SRE) on the setters type, since it needs to be shared between several compilation calls.

Setter sharing is only required in Cecil mode, with SRE we are free to call CreateType after a particular XAML file is finished.
I haven't read the code yet, but how do you handle "XAML references a private nested type" scenario?

We could provide a callback, so it shouldn't be a problem.

I thought about it, but it doesn't solve the lifetime problem as one might want the setters to be shared between all compiler calls, some calls only, not at all... The callback can of course provide the type, but then the compiler has no idea when it should build it. Nothing unsolvable (it was my first approach after all), I felt it was cleaner and easier for the caller to control the setters type. Happy to discuss and change if needed :)
Note that I'm talking about XamlX as a general purpose compiler here since it's very generic (great work by the way, when I started looking at the code, I really didn't expect XamlX to be so nicely separated!), not for Avalonia specific cases, which are well defined and scoped.

I haven't read the code yet, but how do you handle "XAML references a private nested type" scenario?

I don't, sorry if I wasn't clear, the "nested private type" I was talking referred to a setter being generated first in a private class (closure), then being incorrectly reused from another type. This doesn't happen here since the caller is responsible for providing an accessible type that will hold the setters.
In general since you mention referencing private types from XAML files, I don't think XamlX does any visibility check, whether that's using private types or private members?
For example:
public class C { private string P { get; set; } }

<C xmlns='test' P='foo' />

compiles, but fails at runtime with attempt by method 'Populate' to access method 'C.set_P(System.String)' failed.

This doesn't happen here since the caller is responsible for providing an accessible type that will hold the setters.

Consider the following scenario:
class MyControl : UserControl
{
    private object Foo {...} // avalonia property
}

<UserControl x:Class="MyControl" Foo="{DynamicResource Bar}" />

For the user control itself the Foo property is accessible, but it's not accessible for a separate class where dynamic setters are cached. Same with private nested types.

but then the compiler has no idea when it should build it

CreateType is a no-op for Cecil backend (or any backend that would emit code ahead of time), it's only required for System.Reflection.Emit backend where we don't need setter reuse anyway.

For the user control itself the Foo property is accessible, but it's not accessible for a separate class where dynamic setters are cached. Same with private nested types.

Good one! Indeed that would break currently.
I'll add tests covering this case and rework the PR completely since one shared type obviously isn't a solution.

CreateType is a no-op for Cecil backend (or any backend that would emit code ahead of time), it's only required for System.Reflection.Emit backend where we don't need setter reuse anyway. Even if we did reuse types, we'd still need to call CreateType before consuming any compilation results.

I know about CreateType only being useful for SRE (Avalonia doesn't bother to call it when using Cecil), but setters reuse already happens even for SRE, eg.:
<Grid>
  <Border Background="{StaticResource Foo}" />
  <Border Background="{StaticResource Foo}" />
<Grid>

One compilation, twice the same setter. Anyways, point well understood :) Since I'm reworking this I'll add some options/callbacks so the emitter and caller can work together to determine whether a cache is needed and which type should be used.

Pass 3!
A new interface IXamlDynamicSetterContainerProvider has been added, which provides the type into which dynamic setters are generated for a given property and context.
The default implementation of this interface, DefaultXamlDynamicSetterContainerProvider, can accept a type used to share the setters between different compiled types. If a shared type isn't specified (which is the default) or if the property to set isn't publicly accessible, there's no sharing: the current type is used and a private method is generated.
In Avalonia, the Cecil compiler can define a shared setters type before compiling and pass it to the DefaultXamlDynamicSetterContainerProvider. SRE can simply use the default since setters sharing isn't needed here.

I'm terribly sorry for my inactivity, it was caused by covid and then recent events. Hopefully I would either merge this or provide feedback in a week or two.

I'm terribly sorry for my inactivity, it was caused by covid and then recent events. Hopefully I would either merge this or provide feedback in a week or two.

No worries, take your time :) Thank you for letting me know.

I just rebased this PR onto master and resolved conflicts, if you happen to have some time to review :)

@kekekeks can it be merged?


Ctrl+e conflicts with vscode "Go to File"

Ctrl+e conflicts with vscode "Go to File" and I don't wanna change it. Is there a way to set Ctrl+E to other shortcut instead?

You can always change It in your editor to anything else. This shortcut is there since the beginning, I don't think worth changing now. So since vscode has a way to do that individually, I'll close this issue for now

While I see where you're coming from, I do think it offers a bad user-experience to override default shortcuts in Visual Studio Code with no warning.
I think it makes sense to either:

Change the shortcut.
At least use an info message or prompt to ask the user on first usage if they'd like their shortcuts overridden.

Or at least, anything but doing it silently where the user has to figure out why CTRL + E isn't doing what it's expected to, especially given it's such a frequently used shortcut. ^-^'


fix(Button menu):button menu accessibility issue - 3519

Contributes to #3519
Follow a11y guideline about "accessible label should contain or match the visible labels) or allow overrides
What did you change?
Provide the menuAriaLabel prop to be passed to the Button menu component. This optional label should contain or match the visible labels or it will automatically take button label
How did you test and verify your work?
Verified in the storyboard using IBM Equal Access Accessibility Checker.

There appear to be some lint issues, running yarn format should resolve this for you.
@matthewgallo
I have resolved as advised

I do like the simplicity of just using the label as the ariaLabel however, it can be a node which I don't think is a valid value to pass to aria-label. You might consider the approach that @devadula-nandan made recently in the Tearsheet where if there is an ariaLabel prop passed in (in your case menuAriaLabel) we use that, otherwise we try to set it to the text content of the label prop since it could be a node.

I do like the simplicity of just using the label as the ariaLabel however, it can be a node which I don't think is a valid value to pass to aria-label. You might consider the approach that @devadula-nandan made recently in the Tearsheet where if there is an ariaLabel prop passed in (in your case menuAriaLabel) we use that, otherwise we try to set it to the text content of the label prop since it could be a node.

I have used getNodeTextContent , so that it will either take from menuAriaLabel prop or take the text content of the label.


Better  tf.contrib.estimator.early_stopping (Feature request)

System information
N/A
Describe the problem
The current early stopping code doesn't take into account any trends in the loss, and therefore can be thrown off by a single low loss. It would be better to use an exponential moving average of the loss to compute the lowest loss, as that will be less likely to be thrown off by a single very low loss.

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce
Mobile device

Have I written custom code: Yes
OS Platform and Distribution: Linux
TensorFlow installed from: pip,
TensorFlow version: 1.8.0
Bazel version: 0.11.1
CUDA/cuDNN version: 9.0
GPU model and memory: GTX 950 M
Exact command to reproduce:N/A
Mobile deviceN/A
In tensorflows stop if no increase hook, https://www.tensorflow.org/api_docs/python/tf/contrib/estimator/stop_if_no_increase_hook, I find it gives inconsistent results. If there is a single very low loss, then the training will stop too early. What I found worked better was to maintain a running average of the loss, with and stop if that didn't increase beyond a certain number of steps, because that also takes into account trends in the loss.

We currently don't have anybody working on this. It would be great if you could help us by working on this and submitting a PR. Let us know if you need further clarification. Thanks!

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

No, I don't have time to work on this now.
On Fri, Sep 14, 2018, 3:47 PM Alfred Sorten Wolf<EMAIL_ADDRESS>wrote:

It has been 14 days with no activity and the awaiting response label was
assigned. Is this still an issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/21555#issuecomment-421345917,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AG0BV1XMJ-mFM4bvd4SWRg94hvarkQcqks5ua6VcgaJpZM4V5jvx
.

As this issue has invited community support, please remove the assignee. Otherwise, remove the community support label. Thank you.

As this issue has invited community support, please remove the assignee. Otherwise, remove the community support label. Thank you.

Hi, I would be happy to try implementing this.
Is this still relevant? @facaiy @bignamehyp

It is still relevent. I would love if you would try implementing it.
On Sat, Nov 3, 2018, 7:23 PM Eyal Zakkay<EMAIL_ADDRESS>wrote:

Hi, I would be happy to try implementing this.
Is this still relevant? @facaiy https://github.com/facaiy @bignamehyp
https://github.com/bignamehyp
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/21555#issuecomment-435605234,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AG0BV0dgoe0o2hdVAA224ls14ozTsHDmks5urdD7gaJpZM4V5jvx
.

I would be happy to. However, I want to wait for a response from one of the TF members so I will know I'm not working on something irrelevant in the project's perspective...

Contrib has been depreciated here in Tensorflow repo and moved to tensorflow/addons , please reopen the issue in https://github.com/tensorflow/addons/issues if this exists in latest version. Thank you


[ALL][EPIC] Architecture rework

Switch to a nodeJS backend and a proper UI framework on client side.
So that the API could be invoked with different clients (own web UI, magic mirror module, mobile app....)
Planned features/stories:

Preparing

[x]  Rename current repo to cool-updown-legacy
[x] Create new mono repo (cool-updown-nxt)
[ ] Migrate tasks and features to new repo

Migrate current 'services' to JSON REST API

[ ] Persist state to disk to handle services shutdown or restarts
[ ] Implement polling to backend and API will just query the internal state
[ ] DEBUG mode as env variable?

Create a front-end with Vite (choose framework:  React, Vue ..... ?)

[ ] PWA

Create a magic mirror 2 module (new github repository)
Documentation update

[ ] GH repo update (description etc)

TBC https://github.com/djey47/cool-updown-nxt/issues/1


Wrap JSON.parse to trap an print exception details upon parse failure.

Thanks for writing this tool. It is largely what we were looking to do ourselves for translations export/import. Although, when trying it for the first time on our project, I found that it was exiting silently when JSON.parse ran into an error.
It ended up being that we have comments and also some trailing commas in our translations.json. What we have in our .js file is indeed valid javascript, but not fully valid JSON.
Though it would be better to use a full JavaScript parser, having an error giving some indication of why the export bombed out would be very helpful.
Feel free to offer suggestions, if desired. Thanks!

Are you ok with it not being a reversible transaction? Once you go to CSV then back to JS, your comments will be gone, and it will be perfectly formatted.

Yeah, that would be fine.
Sent from my iPhone

On Oct 4, 2016, at 1:04 PM, Kelly Selden<EMAIL_ADDRESS>wrote:
Are you ok with it not being a reversible transaction? Once you go to CSV then back to JS, your comments will be gone, and it will be perfectly formatted.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I am happy to help getting these changes rolled in, even if you need help getting tests updated/added. I am not sure what to make of the invalid references from the Travis CI build though.

I think a start would be verify you can run npm test and have the tests pass before any of your changes. Then incrementally make your changes and run the tests again until you see what is breaking them.

I do like the idea of not relying on JSON.parse though, because comments in the files are definitely useful.


docs: bug fix merge type update

We need to merge bug fixes with "squash commit" option so we don't have duplicate commit messages when new release is created.

:tada: This PR is included in version 4.16.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Create Count number of ways to cover a distance

Given a distance ‘dist’, count total number of ways to cover the distance with 1, 2 and 3 steps.

Hi Dear @deepak7336
Great code
Thanks for your contribution......
Show your support on my youtube channel web Pixar(The institute of coding)
like , share , subscribe
youtube - https://youtu.be/5qnQjgdpFPg
telegram-channel - https://t.me/WebPixar
join our telegram channel for more goodies , swag packs


Rename package (#121597): Mojang.MinecraftLauncher.Legacy

Related #121597 .

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.5 schema?
[x] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

New installer type (*.exe) of Minecraft Launcher is not packaged by a well-known packager. It MAY not support any switches. Unable to create a valid manifest for it.
For the above reason, it's no need renaming Mojang.MinecraftLauncher to a new identifier.

This pull request can be closed unmerged.


Automatic re-submission of jobs with no error reports(Exit code 993030/99400/99401)

Having the workflows coming into assistance-manual with no error report (exit code 99303/99400/99401) has no value as the result is to run a blind ACDC.
May be this can be automated from the agents' side and resubmit the jobs which have this exit code in order to have a valuable output that can be read, interpreted and taken appropriate action. Also, this helps in reducing manual work.
@amaltaro I think this is something that could help us a lot from PnR point of view. @thongonary FYI

2 cents :

there is always a condor log available somewhere (if not on the unified report directly) that can give hints of what is going on. https://cms-unified.web.cern.ch/cms-unified//report/pdmvserv_task_SMP-RunIIFall18wmLHEGS-00093__v1_T_181130_043458_1233

"no job report" is a rather catastrophic event, often due to something rather nasty happening at the site. if that job has only one possible location, chances are that it's going to be resubmitted to fail again.

I am actually surprises, picking on pdmvserv_task_SMP-RunIIFall18wmLHEGS-00093__v1_T_181130_043458_1233 example that the job was a job failing with 99303 was not retried, even though it was only the second trial on that job.
Job Name: c6cbb008-0c8f-480b-aaf3-9aac63c7ebef-5
WMBS job id: 3384144
Workflow: pdmvserv_task_SMP-RunIIFall18wmLHEGS-00093__v1_T_181130_043458_1233
Task: /pdmvserv_task_SMP-RunIIFall18wmLHEGS-00093__v1_T_181130_043458_1233/SMP-RunIIFall18wmLHEGS-00093_0/SMP-RunIIAutumn18DRPremix-00076_0/SMP-RunIIAutumn18DRPremix-00076_1
Status: jobfailed
Input dataset:
Site: T2_US_Purdue
Agent: vocms0251.cern.ch
State Transition
jobcooloff: 2019/1/25 (Fri) 08:01:25 UTC, T2_US_Vanderbilt
jobfailed: 2019/1/30 (Wed) 01:47:49 UTC, T2_US_Purdue
Exit code: 99303

There is no surprise, this agent is in SpeedDrain.

@amaltaro indeed :-(
from
"NoRetryExitCodes": [
    70,
    73,
    8001,
    8006,
    8009,
    8023,
    8026,
    8501,
    50660,
    50661,
    50664,
    71102
  ],

the request in this GH issue is already full-filled

Ok, closing as nothing to be done here.


docs(readme): add npm ver badge

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

v1.1.2
npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Package capture harvest

This PR aims to alleviate some of the time consumed by package data collection in the connect cycle.  Instead of collecting all modules used in the application at startup, the agent uses the fast harvest cycle to incrementally collect this data and sends it though the update_loaded_modules endpoint instead of the connect endpoint (through the "environment" key).
Note: despite the term "Jars" not being used by Python to refer to packages/modules, this is the exact string the endpoint needs in order to process the data.

Codecov Report
Attention: Patch coverage is 96.15385% with 1 line in your changes missing coverage. Please review.

Project coverage is 71.43%. Comparing base (3a001b0) to head (a5faab6).

Files with missing lines
Patch %
Lines

newrelic/core/application.py
94.73%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1228      +/-   ##
==========================================
- Coverage   81.23%   71.43%   -9.80%
==========================================
  Files         197      197
  Lines       21643    21662      +19
  Branches     3782     3784       +2
==========================================
- Hits        17581    15474    -2107
- Misses       2919     5032    +2113
- Partials     1143     1156      +13

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


Captured this may outlive object

Multiple methods in blocknet capture this in calls to direct_routing::async_send_block, which calls peer_manager::async_send
peer_manager::async_send also captures this
Destruction of node may happen while async operations are queued
Destruction of chainContext may also happen while async operations are queued

The easiest solution is to stop chainContext and the http server which will prevent any further callbacks from being executed.

Actually, only the http server needs to be stopped. If the main thread exits is obviously no longer running callbacks for chainContext.


improve error handling

Closes #25

Hello
Thank you for creating this PR but it looks like this issue is already fixed.
I am going to close this PR if you don't mind.


SQL Autocompletion wrong results

I don't know if this has been reported already, sorry if it's a dupe.
I'm encountering errors in the SQL editor, where the autocompletion intelligence doesn't work while editing in a subselection, and doesn't suggest names within scope. For instance:
SELECT * FROM (     SELECT [my_input] FROM EMPLOYEE) T1
The field [my_input] won't suggest entities in EMPLOYEE unless I write EMPLOYEE.<CTRL+Space>.

What is your database?
Because as I see this works ok in MySQL and PostgreSQL..

MS SQL Server 2014 and 2016 produce this error. Prepending the table promptly shows the correct results, but directly typing the field name will only display table names in another table specified out of this subquery, i.e. out of scope.

For me autocomplete is not working with joined tables like:
SELECT *
FROM table1 INNER JOIN table2 ON field1= field2

Could not autocomplete fields from table2 in both SELECT fields and ON clause fields. CTRL+SPACE shows only table1 fields.

@OMG-Abaddon is issue still actual for you?

Original issue is resolved, but not autocomplete in JOIN ... ON clause on second table fields https://github.com/dbeaver/dbeaver/issues/2230#issuecomment-333371082.

@SylwesterZarebski , in case issue is still actual for you, feel free to create new issue.
Original issue closed


add ISession.ChangeKeyspaceAsync

I've added an ExecuteAsync(string cqlQuery) overload, as well as an async version of ChangeKeyspace.
ExecuteAsync I can implement as an extension method, but ChangeKeyspaceAsync cannot as ISession.set_Keyspace is not exposed.

I don't know if we should add the ExecuteAsync(string) overload method, the java driver has it but it was never added to the C# driver.
I think having the sync method ExecuteAsync(string) is good for newbies but we should encourage users to use statements (query / queryid + parameters + consistency + ...) instead.
I will let @al3xandru call this one.
About the ChangeKeyspaceAsync() it makes sense for me to have it as we have a blocking counter part, even though users should not be changing keyspaces regularly within a session.
About the code, besides the small comment to avoid create a new Continue() method, looks good to me.

Removed the TaskHelper.Continue overload.

@al3xandru can this be merged?  If ExecuteAsync(string) is undesirable I can create a separate pull request with just ChangeKeyspaceAsync - that is the method that is truly necessary since it can't be implemented externally.

@collinsauve firstly thanks for the PR (and sorry for completely missing the notifications about the questions)
As both of these are API additions, I'd like to better understand where/how they'd be useful.

while ExecuteAsync is present in a similar form in the Java driver, I find its usage really limited and thus I'd probably suggest not extending the API (it's also easily achievable with the existing API)
in the same vein in the above, I'm not sure I see where an async keyspace change is useful (and if I'm not mistaking that could also be done using the existing API if really needed)

Hi @al3xandru, thanks for getting back to me.

The ExecuteAsync(string) is as useful as Execute(string), except in an async context.  You are correct that this is easily achievable with the existing API.
The ChangeKeyspaceAsync(string) is necessary when you which to change keyspaces in an async context.  Unlike the above, this cannot be achieved with the existing API since there is no public setter on ISession.Keyspace.

If it would help I can rework/resubmit the PR with only ChangeKeyspaceAsync(string).

@collinsauve I was under the impression that all ChangeKeyspace does is execute a USE keyspace statement. A quick check confirmed the first part, but also the fact the the ISession implementation maintains a reference to the keyspace.
Going back for a second to my previous question, could you give me the shortest example of where changing the keyspace asynchronously would be used? (basically what I'm trying to answer is how this method would be really used as to me it seems a bit weird in the sense that it can non-deterministically change the keyspace upon which non-fully qualified queries are getting executed---on the other hand it's kind of late on my side and I might be missing something)

We only need to use it in a very small part of our app - during deployments we execute schema changes in serial.   Since they are serial, we are not concerned with parallel queries being interfered with.
Perhaps I am misunderstanding, but are you implying that the non-Async ChangeKeyspace does not have a similar problem of interfering with parallel queries?
Since async is contagious, we do almost everything in an async context.

As you convert synchronous code to asynchronous code, you’ll find that it works best if asynchronous code calls and is called by other asynchronous code—all the way down (or “up,” if you prefer). Others have also noticed the spreading behavior of asynchronous programming and have called it “contagious” or compared it to a zombie virus. Whether turtles or zombies, it’s definitely true that asynchronous code tends to drive surrounding code to also be asynchronous. This behavior is inherent in all types of asynchronous programming, not just the new async/await keywords.

I've actually already modified some of our infrastructure to allow synchronous blocking functions higher in our stack in order to deal with the lack of an async Connect function.
I could do the same for our schema changes.  Also this conversation has given me an idea, perhaps.  We could fully-qualify our schema changes.

I'm +1 for adding ChangeKeyspaceAsync() even though is just a wrapper to ExecuteAsync(new SimpleStatement("USE ksname")).
I'm -1 for ExecuteAsync(string): We have to point users to use statements, specially BoundStatement and having an additional overload that accept a string is not a good idea. I think the reason that Execute(string) exists is to give users a "quick start" method to use.

Modified PR to drop ExecuteAsync(string) and only include ISession.ChangeKeyspaceAsync.
For what its worth, I've changed our code to fully-qualify table names where we need to change keyspaces.

Based on @jorgebay's vote and your explanations I'm going +1 too (with the only addition that it's still not extremely clear to me how the async keyspace change is actually useful, but I'm OK with going with the assumption I'm missing something)

If it is the case that the implementation doesn't need to set the Session.Keyspace, then this PR isn't really necessary as changing the keyspace asynchronously can already be performed externally using the existing API.

I've pushed an additional commit that removes the line that sets the Session.Keyspace.

Hi @collinsauve, I've noticed this PR hasn't had any activity in a while... Are you still interested in going forward with this PR? If so, please update your branch to force a build on travis.

Although this change makes sense since we already have a synchronous version of this method, it's still technically a breaking change and I'm worried that there are users out there creating fake classes that implement ISession for their tests.

If that's a concern then I only see a couple of ways forward:

Interface segregation
Extension methods
Don't add this at all

Allow me to bring up an old conversation on this PR:
@jorgebay:

You can safely remove the setting of the keyspace as this is done by RequestExecution class, after a set_keyspace response.

@collinsauve:

If it is the case that the implementation (of a given ChangeKeyspaceAsync function) doesn't need to set the Session.Keyspace, then this PR isn't really necessary as changing the keyspace asynchronously can already be performed externally using the existing API.

After learning that, my work-around is just to do this externally.  I've been using this solution for a couple of years now.  I kept this PR because I believe the interface should keep async counterparts to its sync methods, but you will have to decide.
P.S. Maybe if C# 8 ends up getting default interface methods (and old CLRs support it) that could be helpful.

Although this change makes sense since we already have a synchronous version of this method, it's still technically a breaking change and I'm worried that there are users out there creating fake classes that implement ISession for their tests.

If that's a concern then I only see a couple of ways forward:
1. [Interface segregation](https://en.wikipedia.org/wiki/Interface_segregation_principle)

2. Extension methods

3. Don't add this at all

I generally agree with the first option but I don't think that is a solution here to prevent a breaking change.
I'm +1 for 2. I don't generally like extension methods too much but I think that this is a scenario where an extension method fits nicely.

P.S. Maybe if C# 8 ends up getting default interface methods (and old CLRs support it) that could be helpful.

Yeah default interface methods would solve this issue but since they might require a change to the runtime (last I checked) I'm not too sure if the target frameworks that this driver supports will support that feature (especially the net452 target).

Okay, I'll be fine with whatever you decide then.  I'm willing to re-write as an extension method, or close the PR if that's what you want to go with.  If you want interface segregation that's sounds like something I'd let you design :) LMK

Seeing that you found a work-around for this issue and that you are okay with closing this for now, we can wait for the next major version of the driver to introduce this method. Thanks for the nice discussion regardless!


[FEATURE] Dark mode?

Other than just an AMOLED theme. If possible.

Thanks*

I'll be redoing the entire theme soon, the black background is definitely going.

I'll be redoing the entire theme soon, the black background is definitely going.

Perfection


fix: solving compilation warning and issues in multiple target architectures

What type of PR is this?
/kind bug
/kind cleanup
Any specific area of the project related to this PR?
/area plugin-sdk
What this PR does / why we need it:
This fixes a bunch of compilation issues currently arising when compiling the SDK on some architectures. Most of these were caused by unsafe integer casting.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: accf61ab29b8630e1489618fdbecaaba054a4398

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


[Feat] Enable streaming in tool calls when using vllm

#1208

This is a non-intrusive commit, and the control flow of the original functionality has not been modified in any way
I'm writing necessary tests.

Hi @zhanghx0905, i checked out you pull request since I'm eager to get it to work with langchain/opengpts. Are your changes "part of" the OpenAI API compatibility or only for the Xinference llm langchain adapter? I indeed do not get a "streaming not supported" message anymore for both qwen-chat and qwen1.5-chat, however, get the following seemly truncated llm output (might be a streaming end mistake):

And i used "standard" langchain tool binding.

update: action string is complete with Tavily Search tool
Thought: I need to use the tavily_search_results_json API to get information about the weather in Hamburg.
Action: tavily_search_results_json
Action Input: {"query": "weather in hamburg"}

with params:
    _type: "openai-chat"

    model: "qwen-chat"

    model_name: "qwen-chat"

    n: 1

    stop: null

    stream: true

    temperature: 0

    tools

        0: {
          "type": "function",
          "function": {
            "name": "tavily_search_results_json",
            "description": "A search engine optimized for comprehensive, accurate, and trusted results. Useful for when you need to answer questions about current events. Input should be a search query.",
            "parameters": {
              "type": "object",
              "properties": {
                "query": {
                  "description": "search query to look up",
                  "type": "string"
                }
              },
              "required": [
                "query"
              ]
            }
          }
        }

update: action string is complete with Tavily Search tool

I haven't used this part of langchain's functionality, maybe you can provide me with a more detailed reproduction of the steps considering my unfamiliarity.
I am working on this PR mainly for fastgpt tools compatibility as I need it. OpenAI REST API compatibility is of course an important goal.
This PR is still under development, it lacks testing and some details still need to be discussed, so feel free to leave a comment!

You're right, that part of the React agent design pattern. Here you have you that that is actually done by "prompt engineering" (tools description in context) instead of using the function calling api of the llm. It's seems to be come a standard. Here you see how it is used in Langchain which makes it easier to create all sorts of other agent design pattern besides React. Just fyi

You're right, that's part of the [React agent design pattern]

Based on my understanding, there is no conflict between the React-based Tool Call pattern and the OpenAI API. The keypoint lies in whether the model correctly initiates a tool call following "Observation".
I am also considering filtering out all tokens before outputting the "Final Answer:" for the Qwen model in the token stream, which should offer a better interaction experience for users.
Regardless, this PR targets only the Qwen and ChatGLM3 models, while the former significantly outperforming the latter.

Based on my understanding, there is no conflict between the React-based Tool Call pattern and the OpenAI API. The keypoint lies in whether the model correctly initiates a tool call following "Observation".

The api documentation of OpenAI's tool-choice (click in the functions in the right pane) shows that function specifications has become part of the API parameters instead of part of the messages parameter ("system of prompt"). Both request and response are now well defined structures (usually json). This strategy has been adapted by others like e.g. llama function calling, mistral.ai function calling, where the structured request functions specifications and structured response are similar. Since the response is structured, there is no needs for a "stop sequence" like e.g. "observation" to intercept/detect function calling. In addition, for this purpose some of these llms are explicitly set to a "json mode".
My understanding is that some React agent implementations (e.g. langchain react agent) use function specifications and instructions as part of the system message/prompt and not using the function calling api parameter. Part of those instructions is to respond in a thought, action, observation format ("unstructured" non-json/xml). Althought, it is still imaginable that the llm service like e.g Xorbits Inference tool "injects" these instructions, but usually it's done on application level. So with respect of not using the OpenAI function calling api, you're right that it will not conflict with the OpenAI api.
This is my interpretation and I trying to learn, please let me know of there are flaws in my reasoning and assumptions.

@weipienlee
I've filtered out Qwen ”React“ intermediate thought process, and now the feature should be much closer to what you'd expect. You can try it.

My excuses @zhanghx0905, I think we have a misunderstanding. I was not aiming for changing the "React" agent design pattern, rather, for an extra "OpenAI function calling/tool_choice mode/api". Having something "in the middle" might not beneficial for anybody.
E.g. I tested your code commit hash:5e712b127809aae887ef54c85195ef3867c1c7bf with a React agent design pattern in streaming mode and that works perfectly for non-quantized Qwen-chat 1.8B and Qwen1.5-chat 0.5B pytorch models. I'm using the OpenAI rest API via LangChain ChatOpenAI class.
Once using any quantized models, however, Orbits Inference does not adhere to the stop sequence. I tried:

"\nObservation" (default)
'Observation'
'Observation:'

but this might a be another bug.
I can test your last commits but I have to figure out how to checkout/see you last commits in my clone

My excuses @zhanghx0905, I think we have a misunderstanding. I was not aiming for changing the "React" agent design pattern, rather, for an extra "OpenAI function calling/tool_choice mode/api". Having something "in the middle" might not beneficial for anybody (worried about breaking existing code).

I must remind you that the so-called function calling or tool calling is actually nothing more than prompting to drive LLM to output a JSON object. "React" is one way of organizing prompts. An LLM must be fine-tuned and aligned before it can correctly output this kind of json object and understand prompt. This is why very few open source models have "tool" capabilities (almost only Qwen series).
The larger the number of parameters of the model, the greater its ability to follow instructions, select the right tools, and generate the correct json payload. The number of model parameters of 0.5B and 1.8B is too small for a LLM. Their capabilities are actually very limited, let alone their quantified versions.

I tested commit hash 17df51595f08c7be2a0b84cfb132f44282251797 and seems not much changed, but it is still working. So I'm not sure what the goal was. Using the OpenAI api with React design pattern LangChain ChatOpenAI class:
was (result of another day, commit hash 5e712b127809aae887ef54c85195ef3867c1c7bf)
llm tool call:
I should use the duckduckgo_search tool to find out the current weather in Hamburg.
Action: duckduckgo_search
Action Input: "current weather in Hamburg
llm final anwers:
I now know the current weather in Hamburg.
Final Answer: The current weather in Hamburg is mostly cloudy with a chance of showers throughout the day. The temperature is ranging from 10°C to 14°C, with a light breeze coming from the north-west. There is no precipitation expected for the next 10 days.
current
llm tool call:
I should use the duckduckgo_search tool to find out the current weather in Hamburg.
Action: duckduckgo_search
Action Input: "current weather in Hamburg
llm final answer:
I now know the current weather in Hamburg.
Final Answer: The current weather in Hamburg is currently clear with a low chance of precipitation. The temperature is 6°C and feels like 4°C. There is a light breeze from the north east with gusts at 6 m/s. The long-range 12-day forecast shows that there is a high chance of precipitation near 90%. You can check the latest weather information by visiting the website or app of the city of Hamburg.

My excuses @zhanghx0905, I think we have a misunderstanding. I was not aiming for changing the "React" agent design pattern, rather, for an extra "OpenAI function calling/tool_choice mode/api". Having something "in the middle" might not beneficial for anybody (worried about breaking existing code).

I must remind you that the so-called function calling or tool calling is actually nothing more than prompting to drive LLM to output a JSON object. "React" is one way of organizing prompts. OpenAI's tool call API is just a layer of encapsulation on top of it. This is the purpose of this PR.
An LLM must be fine-tuned and aligned before it can correctly output this kind of json object and understand prompt. This is why very few open source models have "tool" capabilities (almost only Qwen series).
The larger the number of parameters of the model, the greater its ability to follow instructions, select the right tools, and generate the correct json payload. The number of model parameters of 0.5B and 1.8B is too small. Their capabilities are actually very limited, let alone their quantified versions.

Ok, understood and thanks for the effort to handle my feedback @zhanghx0905. I will try larger models as well, but have the aforementioned remaining end-sequence adherence problem with quantized models. Do you know if this this also due to the size of model (quantized degraded behaviour) or an actual "bug?

Another unrelated question @zhanghx0905, is there a way to run an Inference checkout without building an egg and install it first?

My excuses @zhanghx0905, I think we have a misunderstanding. I was not aiming for changing the "React" agent design pattern, rather, for an extra "OpenAI function calling/tool_choice mode/api". Having something "in the middle" might not beneficial for anybody (worried about breaking existing code).

I must remind you that the so-called function calling or tool calling is actually nothing more than prompting to drive LLM to output a JSON object. "React" is one way of organizing prompts. OpenAI's tool call API is just a layer of encapsulation on top of it. This is the purpose of this PR.
An LLM must be fine-tuned and aligned before it can correctly output this kind of json object and understand prompt. This is why very few open source models have "tool" capabilities (almost only Qwen series).
The larger the number of parameters of the model, the greater its ability to follow instructions, select the right tools, and generate the correct json payload. The number of model parameters of 0.5B and 1.8B is too small. Their capabilities are actually very limited, let alone their quantified versions.

Ok, understood and thanks for the effort to handle my feedback @zhanghx0905. I will try larger models as well, but have the aforementioned remaining end-sequence adherence problem with gguff quantized models. Do you know if this this also due to the size of model (quantized degraded behaviour) or an actual "bug? I already tried e.g. 7B quantized as well but also failing. Maybe still not big enough?

This PR only supports vllm, if you don't use vllm you should get an 400 error and shouldn't get any output. There does seem to be a problem, thanks for the feedback!

i see, tnx

I used llama.cpp to run quantized models and Inference is using it. Is support on the roadmap?

Although fastgpt uses the tool without reporting errors, the content of the answer is incorrect

Although fastgpt uses the tool without reporting errors, the content of the answer is incorrect

我只为 vllm backend 实现了该功能，其它的 backend 仍然返回 400 error，这个在最新的 commit 中应该已经保证了。


Localization Tutorial Does Not Show How to Initialize If you are only using API

The .NET Core Localization Document (otherwise, excellent), does not include instruction for how to instantiate the localization if you are using ONLY API functionality - it focusses solely on projects with MVC views.
I have just lost hours trying to work out why ResourceNotFound (from Microsoft.Extensions.Localization.LocalizedString) would always be true in an HTTP API GET request, no matter what I did.
The eventual answer was here.
In the startup.cs code, I needed to do the following, which I could not find in the documentation, or in the sample:
var localizeOptions = app.ApplicationServices.GetService<IOptions<RequestLocalizationOptions>>();
app.UseRequestLocalization(localizeOptions.Value);

The document and sample code only state the following (which does not seem to work for API requests):

app.UseRequestLocalization(new RequestLocalizationOptions
{
    DefaultRequestCulture = new RequestCulture("en-US"),
    // Formatting numbers, dates, etc.
    SupportedCultures = supportedCultures,
    // UI strings that we have localized.
    SupportedUICultures = supportedCultures
});

Please could the documentation be updated to include this?
If you would like me to create a PR and suggest an edit, I will be happy to do so.

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

ID: d1833676-ff1b-c587-cc9c-81afffa8ef68
Version Independent ID: ad989395-3f49-4d55-521e-cf6fe56281ee
Content: Globalization and localization in ASP.NET Core
Content Source: aspnetcore/fundamentals/localization.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@ryanbrandenburg  quick review of proposal please. cc @hishamco

There are two ways to configure UseRequestLocalization() the one that you pointed is already there in the Localization.StarterWeb
This is only needed if you configure the RequestLocalizationOptions in the ConfigureServices using the following code:
services.Configure<RequestLocalizationOptions>(options =>
{
    ...
});

@hishamco but the document is controller with views focused. Don't we need to add something to the doc for REST APIs?

Strange!! why it doesn't work, @HockeyJustin could please create a repo to reproduce the issue you are facing?

@hishamco  . Thanks for getting back to me. The project I used this on was a work one, so I would need to create something completely separate. I don't think it's needed in this case.
You have correctly identified the key point that I am utilising services.Configure<RequestLocalizationOptions>(..).
The sample you reference does indeed include the correct setup, but that isn't detailed or referenced from this document.
The documentation includes services.Configure<RequestLocalizationOptions>(..) ,but does not include the corresponding UseRequestLocalization needed to make a working solution if services.configure was used. Hence, I believe the document is lacking a vital piece of information that would save a developer hours of debugging/ hunting for the solution online.
To be clear: This is not a coding issue. The issue is that the referenced document does not provide adequate information for a developer to get set up when using services.Configure<RequestLocalizationOptions>(..) as part of their setup.

To be clear: This is not a coding issue. The issue is that the referenced document does not provide adequate information for a developer to get set up when using services.Configure(..) as part of their setup.

Agree but I think the Configuration & Options patterns should have somethings related, because this not for localization only

Thanks for contacting us, @HockeyJustin.
We recommend using the same mechanisms as you would in non-API application.
Given that configuring localization in web-api only applications is not a common scenario we don't plan to modify the docs to reflect on this.


[Question] Are SonarQube fixes welcome?

Hi,
I'm found the project on SonarCloud, and I'm willing to contribute with fixes for some kind of issues. Is that something of interest for the project? If so, should I just submit pull requests? (I'm aware of the necessity of signing off commits and also providing a changelog entry).
Thanks!

Hi, sorry for the late answer.
The core team is now working on RiotX (https://github.com/vector-im/riotX-android).
SonarCloud issue fixes (by PRs) will be more appreciated for RiotX :)
RiotX sonarcloud project: https://sonarcloud.io/dashboard?id=vector.android.riotx
Please note that I will trigger an analysis because the last one is from April
Thanks
Benoît


404not found.html

Purpose

Create custom error page for Python docs #1411
Remarks

PR introduces (a) breaking change(s): no
PR introduces (a) deprecation(s): no

@Anurag-modgil thanks for your contribution 🙏🏼
You have overwritten the main.html file but you need to overwrite the 404.html file like it is described here: https://squidfunk.github.io/mkdocs-material/customization/#extending-the-theme
You can verify your changes by running make livedoc to view the docs in the browser (this command works only for macOS and Linux afaik)

Is a duplicate of https://github.com/apache/streampipes/pull/1451


incorporate feedback from starter CTE branch

Describe your changes
Issue number
Closes #51
Checklist before requesting a review

[ ] Performed a self-review of my code
[ ] Formatted my code with pkgmt format

:books: Documentation preview :books:: https://ploomber-sql--56.org.readthedocs.build/en/56/

Hi @TegveerG
Incorporated your suggestions from initial PR

When I try to run the notebook in colab it's not able to find the banking module

NameError                                 Traceback (most recent call last)
[<ipython-input-3-27f639b47bb6>](https://localhost:8080/#) in <cell line: 6>()
      4 #import banking  # noqa: E402
      5
----> 6 _ = banking.BankingData("https://tinyurl.com/jb-bank", "bank")
      7 _.extract_to_csv()

NameError: name 'banking' is not defined

We can also add a section on how we use CTEs in JupySQL using --save

Thank you @neelasha23 for adding feedback!
Will address the comments. Thank you for trying the Google colab.
It looks like the import is commented out.
Typo - will rerun jupytext and ensure it isn't caused by the formatting

You are right - from Google colab the notebooks fail :(.
Will spend a bit more time troubleshooting this

Hi @neelasha23
Addressed comments, added a fix to execute the notebooks from colab, tested the branch and it works


MRGT pruning

The MRGT needs to be able to prune the glossarydir. This feature is already specified in the specs.
The idea is to add an option -p or --prune, that discards all files mrg.<something>.yaml if such a file contains an MRG that is not (typically: no longer) specified in the SAF as containing a curated terminology.
In github actions, this should also be reflected in the original repo.

When MRG's are imported/non-local scope MRG's are within the glossarydir, the SAF of this external scope would be needed to determine which MRG's are still maintained. The MRGT does not currently have access to this information (only the mrg-importer does). I suppose 'prune' could become a function within the mrg-importer instead if we want to prune the imported scopes as well. In the case of the MRGT, we could only really prune the local scoped MRG's as we only have access to these maintained vsn and altvsntags.


The 6-digit positive code should expire in 1 hour, not 24 hours

NYS is making the call that the 6-digit positive code should expire in 1 hour, not 24 hours (as it is today) or 10 mins.

@rgormley I believe this is code_lifetime_mins in the infrastructure deploy terraform.
cc/ @dgonzalez to double check.

It is. That configures the timeout of the code.

I am making this change now.

This change has been pushed and is live in nys-dev, nys-qa and nys-prod.

I just generated a code through Postman and it came with an expiry timestamp of<PHONE_NUMBER>, which is still 24 hours. How do I validate this?

I'll review this with @dgonzalez this morning.

We may need to restart the push api ECS instances so that they pick up the setting. I believe it's only read at startup.


[Quest] Update Sync mechanism to Rely on Composition or Sync by  Strategy

We may need  to update the Sync mechanisms to
Non Patient data to be synced via Composition

Binary
Questionnaire
Structure Maps

Patient Data to be synced via Sync by Strategy

Condition
Observations
Encounters
PlanDefinitions
CarePlans
ServiceRequest
QuestionnaireResponse

Sync by Strategy defined here https://github.com/opensrp/fhircore/discussions/746
Pre-requisite

Documentation of what composition resource would hold
What data will be synced/tagged  based on the user assignment
How can we give a user feedback on what is being synced / configured  - do we need a new progress bar (UX to be discussed with design team)

There are further details on this we discussed today, I'm going to convert this to a discussion until this is ready for assignment.
Let's call the non-patient data the config data. We also want to split the config  data into blocking and non-blocking, non-blocking data for sync we can background. So the process looks something like this with time from top to bottom:

Sync blocking config data

Composition
Linked Binaries
Linked Questionnaires, linked Structure maps

[app is now usable]

Background sync non-blocking config data

Measures
Libraries needed for measures
[Anything else?]

[all configs sync, data not synced]

Sync patient data

Show progress bar on Registers, @rowo we need design teams input on whether we want to do this and wait until sync is complete, or also show the patient data we have so far in Register as it comes w/some notice it's still loading, or something else


feat: fix the mitm vulnerability of starknet client

Describe the Feature Request
For some reason it's possible to mitm attack https requests to starknet provider with mitmproxy.
And this is not possible when using starkli for example, which uses the same libs but returns nice error. Here is dbg version of it:
Err(
    Other(
        TransportError(
            Reqwest(
                reqwest::Error {
                    kind: Request,
                    url: Url {
                        scheme: "https",
                        cannot_be_a_base: false,
                        username: "",
                        password: None,
                        host: Some(
                            Domain(
                                "starknet-goerli.g.alchemy.com",
                            ),
                        ),
                        port: None,
                        path: "/v2/XXXXXXXXXXXXXXXXXXXX",
                        query: None,
                        fragment: None,
                    },
                    source: hyper::Error(
                        Connect,
                        Custom {
                            kind: Other,
                            error: Custom {
                                kind: InvalidData,
                                error: InvalidCertificate(
                                    UnknownIssuer,
                                ),
                            },
                        },
                    ),
                },
            ),
        ),
    ),
)

It looks like  updating dependencies will fix that. I guess hyper-rustls handle this cert check

@sergey-melnychuk Hi! Yeah, maybe it's not vulnerability, please rename which would be correct!
So, tried updated version - no difference.
and starkli give same result starkli2.2 block 0x718f8a6849da9b69cf1acbbc7e9815f3a4d82880bc111b8e9b2443aee8d0b5f Error: error sending request for url (https://starknet-mainnet.g.alchemy.com/v2/iVVSuDAoGhsy4xrFjSJl8yL4HI0SOgA9): error trying to connect: invalid peer certificate: UnknownIssuer
So mitm install is basic one. And certs copied to /usr/local/share/ca-certificates/extra/mitmproxy-ca-cert.crt
I run it like this
sudo -u mitmproxyuser -H bash -c '$HOME/.local/bin/mitmproxy --mode transparent --showhost --set block_global=false -s /mitm-scr/*'


[CI] Improve coverage config

Summary of changes
Currently there is a lot of noise and problems when running coverage in the CI.
This is an attempt to improve the configuration and clean the coverage output.
Closes
Pull Request Checklist

[ ] Changes have tests
[ ] News fragment added in changelog.d/.
(See documentation for details)

Thank you very much @jaraco and @webknjaz for the kind reviews. I tried to address some straight-forward changes as proposed, but others are a bit more complicated.
In the latest commits, I tried to simplify the configuration by removing the [paths] section I had previously added. In general this section is important for testing installed packages, but since setuptools is tested via usedevelop=True, it should not impact too much (the reason why I added it in the first place was because I was doing some experiments to remove usedevelop=True).
Unfortunately I did not find a way of not specifying explicitly the package name in the configuration and still obtain clean output (without explicitly specifying the package names there is a lot of warnings and noise in the output).

Shouldn't this configuration be merged into pyproject.toml?

Shouldn't this configuration be merged into pyproject.toml?

I haven't yet had a chance to write a blog post about it. Combining all the config into a single file is problemmatic because it conflates concerns and increases the possibility of conflicts as projects share config and have divergent concerns. Let's keep the concerns separated for now. If you think the files should be combined, please file the report at jaraco/skeleton and I can discuss it further there.


coqPackages.vcfloat: init at 2.1.1

Sorry everyone about #257959 -- the pings really snuck up on me, I had no idea that was going to happen. It was also inconsiderate to have not gotten the commit squash/messaging stuff right initially.
Description of changes
Closes https://github.com/NixOS/nixpkgs/issues/257548
VCFloat: A Unified Coq Framework for Verifying C Programs with Floating-Point Computations
Metadata

homepage URL: https://verinum.org/
source URL: https://github.com/VeriNum/vcfloat
license: LGPL3

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

(@wegank sry about keeping the word version in there-- I read it directly from CONTRIBUTING.md)
@Zimmi48 @vbgl (I was told on Zulip that these are the people to tag)

@ofborg build coqPackages.vcfloat coqPackages.vcfloat.passthru.tests

@quinn-dougherty if you want, you can test this in the Coq Nix toolbox: https://github.com/coq-community/coq-nix-toolbox#testing-coqpackages-updates-in-nixpkgs


Adding tests for incremental compilation.

Feature motivation
I have a feeling that having incremental compilation tested will help to track some tricky bugs and provide some common ground for performance discussions. Also, I would like to try to do some more improvements on incremental compilation, but without tests around it I really feel uncomfortable changing anything...
Feature description
I've written a simple code generator. With it I can generate a codebase of arbitrary size. Then I've spent some time to see if it is possible to write tests around webpack in watch mode and it seems to be doable (latest improvements in the test code are really helpful, btw!).
Feature implementation
If this would be useful, I would be happy to write a few proper tests, but I would like to get some feedback first.
Also there is a question regarding performance testing: is it possible to integrate performance testing to any existing CI/CD flow, despite its random-ish nature? Or is there some tool which can provide results from the tests as a metric, (like in version 1 test was taking 1s, in version 2 it is taking 0.8s)

From taking just a glimpse at it, that code generator looks like a lot of dark magic - very interesting :+1:
Generally speaking, performance tests would be great. But I also have some doubts:

in the current CI, our test suite takes between 5 and 7 minutes, so we have a big deviation there. I'm not sure if we can counteract that. Maybe by calling time on the command line which counts actual CPU time? I'm not sure how that works in a VM. Is there any prior art?
generated code bases can be one way of doing that, and if we pin the seed somehow and solve the CI-divergence-problem, they can be reproducible. But I'm not sure if they can simulate real use cases (I haven't really looked at the code generator yet though, those are just my first thoughts!).
Maybe, in addition we could look for some reference projects and simulate file changes between compiles by jumping from one commit to the next?
Of course, that wouldn't catch everything too, but having some known (and easy-to-compile) TS projects to test on could be double useful.

I've tried so find some real-life repos we could use.
So far, these are what I've got: https://github.com/phryneas/fork-ts-checker-performance/tree/master/repos
I'll play around with compiling & measuring those a bit, but feel free to do your own tests on them :)

I will close it as there is no activity :)


ability to select and copy text

maybe this is my terminal emulator making me look silly, but the one thing i'm missing so far is that i can't copy text out. :-) i was using this earlier for viewing crates, but when i want to copy setup out i couldn't. this project is great and so much faster than any other browser lol. haven't been able to get sound to work yet, but i have only been using the container and probably my fault there too.

Probably your terminal emulator. Does holding shift down help?

Probably your terminal emulator. Does holding shift down help?

that saved me here, thanks alot!!


Publish 05/20/2021, 3:30 PM

Docs Build status updates of commit 86f1770:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUserAndContentMoveState.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


论文投递

亲爱的朋友
这篇预印版的论文已经投递了吗，方便透露一下进度吗

Thank you very much for your interest!
For your information, our work has been accepted by RECOMB-2022: https://recomb2022.net/accepted-papers/

Congratulations ！
It is really a wonderful job! I do the research about metagenomic binning too . And our team developed a metagenomic binning tool and i want to reproduce CLMB for comparing. Would you like to share your new dataset's intermediate results ,just like the contigs and abundance information ?

Thank you!
We are currently preparing for the journal version of the paper. We will let you know when we are ready to share the intermediate results.