Bump dependencies in cli crate

Which issue does this PR close?

Closes #.
Rationale for this change

What changes are included in this PR?

Bump datafusion-cli dependencies

use stabilized version aws-sdk 1.x.x (https://www.infoworld.com/article/3711271/aws-delivers-aws-sdk-for-rust.html)
use latest clap version

Are these changes tested?
yes

Are there any user-facing changes?

Thanks @satyakommula96  -- it seems like there are a few test failures on this PR. Can you please resolve them?


Map control scale bar

Optionally add a map control scale bar to any MapViz with custom position and styling.  Closes #143.
Usage example:
import os
from mapboxgl.viz import *

# Create the viz from the dataframe
viz = CircleViz('../data/healthcare_points.geojson',
                access_token=os.getenv('MAPBOX_ACCESS_TOKEN'),
                center=(-95, 40),
                zoom=2.5,
                scale=True,
                scale_unit_system='imperial',
                scale_position='top-left',
                scale_border_color='#6e6e6e',
                scale_background_color='#eee',
                scale_text_color='#131516')

# Show the viz
viz.show()

Sure thing! I had added one example to https://github.com/akacarlyann/mapboxgl-jupyter/blob/map-scale/examples/notebooks/scale-annotation.ipynb before opening the PR. @ryanbaumann Which notebook should I integrate this into?

I'd recommend adding to https://github.com/mapbox/mapboxgl-jupyter/blob/master/examples/notebooks/point-viz-types-example.ipynb

@ryanbaumann sounds good.  Added in 57f9014.

Looks good - ready to merge if you are @akacarlyann

@ryanbaumann It's ready!


Non integer problem numbering

I'd like to be able to have exercises numbered as 2.1, 2.2, .... I've tried using \problemnumber{2.1}, but this doesn't seem to work because of the period. I even tried \problemnumber{2\.1}, but again same problem.
Perhaps this isn't possible, but would be good to verify.

I don't know a nice way of doing this unfortunately, since the problem environment gets its numbering behavior from amsthm's theorem-like environments. As a result, \problemnumber expects an integer. This is the line to blame:
https://github.com/artemmavrin/latex-homework/blob/1173aa780847175fcc0adde63cf06d6773469e50/homework.cls#L152

One hacky workaround would be to add the following to the preamble of your .tex file:
\makeatletter
\numberwithin{@problem}{section}
\makeatother

This makes the problem numbers depend on the current section number. Then you can set the section number to, e.g., 2 in the body of your .tex file:
\setcounter{section}{2}

The problems will be numbered 2.1, 2.2, etc, and you can still use \problemnumber to set the n in 2.n. Also, you can switch to a different prefix by changing the section counter again.

Here's a minimal working example:
\documentclass{homework}

\name{Name}
\course{Course}
\term{Term}
\hwnum{\#}

\makeatletter
\numberwithin{@problem}{section}
\makeatother

\begin{document}

\setcounter{section}{2}

\begin{problem}
A problem.
\end{problem}

\begin{solution}
A solution.
\end{solution}

\begin{problem}
Another problem.
\end{problem}

\begin{solution}
Another solution.
\end{solution}

\end{document}

Hope this helps!

This worked perfectly. Thanks for your detailed answer with an example. I'll leave this open, but feel free to close it.

Hey another question related to this. I now have a homework starting with question 3.14. I've tried setting the subsection counter, but that's not working either. In short, I can't figure out a way to start the counter from 3.14.
This may be a larger question than just this package and if that's the case no worries, I'll keep looking elsewhere, but thought I'd ask if this is possible.

You can use \problemnumber{14} before the first question to set the problem number.

Great, thanks so much for your help again!


Expose SetSDKForStruct and SetResourceForStruct in templates

Description of changes:
Makes setSDKForStruct and setResourceForStruct public, so that they are accessible for other parts of the generator. Exposes SetSDKForStruct as GoCodeSetSDKForStruct and SetResourceForStruct as GoCodeSetResourceForStruct in the generator, and includes SDKAPI as a template variable to allow querying of API shapes to use with parameters in the new template methods.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/approve

/lgtm


Add AboutUs page

Add skeletal Project Portfolio Page (PPP) for the team
Add avock's PPP
Add avock's profile picture
Update avock's info in AboutUs

Codecov Report
Base: 72.15% // Head: 72.15% // No change to project coverage :thumbsup:

Coverage data is based on head (3dce535) compared to base (ae4fd0a).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master       #6   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

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

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


Add support for Cocoapods

I added support for Cocoapods in order to import it into a framework of my own.
I left instructions in the README, so this commit will need an edit to remove the aforementioned instructions after the publish command has been written.

CocoaPods support should hit main shortly


Added details related to functional programming in JS

This Pull Request is...

[ ] Edit typos or links
[ ] Inaccurate information
[ ] New Resources

Description
(say something...)

The classification is not correct


Error when sending transactional template when the text or html keys are not defined.

Hello @thinkingserious,
When I use this code to send a transacational template , I get a success response but nothing is really sent. Nothing is received in the inbox and nothing in the activity section of SendGrid.
Sendgrid.setApiKey(SENDGRID_API_KEY);

const email =
{
    to<EMAIL_ADDRESS>    from: SENDGRID_SENDER,
    subject: 'Test',
    template_id: 'd-128e110d98e040c6b81f4694d04e0572',
    dynamic_template_data: {
        subject: 'Coucou :)',
        club_name: 'VTR School',
    },
};

Sendgrid.send(email)
    .then(m => {
        console.log('Mail sent');
    })
    .catch(error => {

        //Log friendly error
        console.error(error.toString());

        //Extract error msg
        const { message, code, response } = error;

        //Extract response msg
        const { headers, body } = response;
    });

However, all is fine when I use
text: 'and easy to do anywhere, even with Node.js',
or
html: 'and easy to do anywhere, even with Node.js',
Do you have any idea for which reason?
Thanks
Originally posted by @milottit in https://github.com/sendgrid/sendgrid-nodejs/issues/444#issuecomment-503319989

Hello @milottit,
Could you please verify what version of this library you are using? npm sendgrid --version
Thanks!
Elmer


[BUG] Support all exposed message headers/properties from ServiceBusReceivedMessage in ServiceBusMessageConverter

When converting ServiceBusReceivedMessage to a Spring Message in ServiceBusMessageConverter, currently not all message headers/properties are converted, the ones belong to AmqpMessageHeader which is a component of AmqpAnnotatedMessage are ignored.
We should contain all exposed message headers/properties to avoid miss any message information.

Resolved in #27675


was not declared in this scope

g++ -o radmin3_bf -O3 radmin3_bf.c -lssl -lcrypto -lpthread.
radmin3_bf.c: In function ‘int custom_exp2(BIGNUM*, BIGNUM*, BIGNUM*, BIGNUM*, BN_CTX*, BN_MONT_CTX*)’:
radmin3_bf.c:169:44: error: ‘BN_bn2binpad’ was not declared in this scope
BN_bn2binpad(xc, (unsigned char )&idx, 4);
^
radmin3_bf.c: In function ‘void process_batch(void*)’:
radmin3_bf.c:281:20: error: ‘pthread_exit’ was not declared in this scope
pthread_exit(dummy);
^
radmin3_bf.c: In function ‘int main(int, char**)’:
radmin3_bf.c:309:45: error: ‘OPENSSL_hexstr2buf’ was not declared in this scope
salt = OPENSSL_hexstr2buf(SALT_HEXSTR, NULL);
^
radmin3_bf.c:364:45: error: ‘pthread_join’ was not declared in this scope
pthread_join(threads[thread_num],&dummy);
^
radmin3_bf.c:390:66: error: ‘pthread_create’ was not declared in this scope
pthread_create(&threads[thread_num], NULL, process_batch, arg);
^
radmin3_bf.c:401:44: error: ‘pthread_join’ was not declared in this scope
pthread_join(threads[thread_num], &dummy);
^

fix,
i see, openssl is old.


Open Email Draft Nonfunctional

Describe the bug
when i click to "open email draft", it takes me to a blank page with this image in my address bar
To Reproduce
Steps to reproduce the behavior:

Go to Bills Page
Click on Individual Bill Page
Write a Testimony
When prompted to email, click "open email draft"

Expected behavior
Open Gmail with the body and address bar filled out
Screenshots
Takes me to a blank page and this address bar

refreshing doesn't help
Desktop (please complete the following information):

OS: Windows 11
Browser Chrome

Added a help link after users click send email


Config Path by Setting

I am using Atom to run NodeJs in a portable environment. In the portable environment, I cannot change the environment path variable.
Is there any config files or settings that I can change the path variable? Or How could I set the node.exe path.

Hi.
Script - > Run with options -> fill first field as you like

@nixel2007 Is it under Menu, Package -> Script
I cannot find this option in my Atom.
My Atom version: 1.11.2
Script version: 3.13.0
I finally set the environment in the Init Script.
process.env.PATH = [, process.env.PATH].join(";");

@imben1109 , so I'm not too sure what I've done here and why your suggestion worked.
I am running everything portable (Atom and python) via a USB drive on windows.
Obviously if I'm running portable then python won't be in my path, so I wanted to tell Script where to look for the python.exe.
Without knowing what I was going I copied the following into my init.coffee script in Atom.
process.env.PATH = ["\\program_files\\python_<IP_ADDRESS>\\python-3.6.0.amd64"] which is the path to my python.exe
And now Script will run .py files fine. Great!
But how does this actually work?
How do I add more paths, for example to python2.7? (which incidentally is \\program_files\\python_<IP_ADDRESS>\\python-2.7.10.amd64
And how do I get Script to run python2 over python3 in this scenario?

@jackjameshoward
process.env.PATH = ["\program_files\python_<IP_ADDRESS>\python-3.6.0.amd64"] is similar to set the System Path. Therefore, the python command can be executed in atom environment.


store.js is not valid in ES5 strict mode

I am getting this error when minifying store.js with Google's closure compiler with language_in=ECMASCRIPT5_STRICT:
ERROR - functions can only be declared at top level or immediately within another function in ES5 strict mode

The problem is in this line:
function ieKeyFix(key)

You could either move that function up, or declare a var instead:
var ieKeyFix = function(key)

You can see a clumsy workaround in gulpfile.js of my repo:
https://github.com/bparadie/react-flux-typescript-todomvc
Removing that workaround will exhibit the problem.

Closing due to inactivity and no longer relevant for version 2

Store.js v2.0 has been released!
If you update to the latest version you will automatically get this functionality plus a bunch more :)


Invalid cql-json and expression is parsed into "wrong" ast

I cannot find any description of how pygeofilter is supposed to behave when it meets invalid filters. The issue is written assuming that pygeofilter should fail when parsing invalid filters.
Example 1 where pygeofilter silently ignores invalid and expression:
>>> import pygeofilter.ast
>>> from pygeofilter.parsers.cql_json import parse as parse_json
>>>
>>> cql_json = { "intersects": [ { "property": "geometry" }, { "type": "Point", "coordinates": [ 10.4064, 55.3951 ] } ], "and": [ {"eq": [ { "property": "direction" }, "east" ] } ] }
>>> print(pygeofilter.ast.get_repr(parse_json(cql_json)))
INTERSECTS(ATTRIBUTE geometry, Geometry(geometry={'type': 'Point', 'coordinates': [10.4064, 55.3951]}))

Example 2 where pygeofilter parses invalid and into a simple comparison:
>>> import pygeofilter.ast
>>> from pygeofilter.parsers.cql_json import parse as parse_json
>>>
>>> cql_json = { "and": [ {"eq": [ { "property": "direction" }, "east" ] } ] }
>>> print(pygeofilter.ast.get_repr(parse_json(cql_json)))
ATTRIBUTE direction = 'east'

Needless to say it would be a better user experience if both these examples would fail with some meaningful message.

@AsgerPetersen
Thanks for reporting this issue. The JSON based parsers are indeed rather simple and will ignore extra attributes of the identified node. But I agree, extra arguments should not be silently ignored but reported as errors. Contributions are welcome.
Regarding the and with only a single item: I concur, we should add a check to mark these cases as errors!

Thank you both. Unfortunately I there isn´t enough time for me to participate actively in all the great projects I use. I try to my best to take the time to at least write decent bug reports.
@bitner that makes sense, but doesn´t the spec require at least 2 items? So other parsers would probably behave differently.

Unfortunately I there isn´t enough time for me to participate actively in all the great projects I use. I try to my best to take the time to at least write decent bug reports.

Your contribution in the form of bug reports is very much appreciated! I did not mean to impose further work on you, but rather something I don't have the resources to fix right now. So if anyone wants to step up and take this over, I'd be very grateful!

@bitner that makes sense, but doesn´t the spec require at least 2 items? So other parsers would probably behave differently.

That is indeed true, the spec mandates at least 2 items

On Wed, Jun 8, 2022, 5:42 AM Asger Skovbo Petersen @.***>
wrote:

I cannot find any description of how pygeofilter is supposed to behave
when it meets invalid filters. The issue is written assuming that
pygeofilter should fail when parsing invalid filters.
Example 1 where pygeofilter silently ignores invalid and expression:

import pygeofilter.ast
from pygeofilter.parsers.cql_json import parse as parse_json
cql_json = { "intersects": [ { "property": "geometry" }, { "type": "Point", "coordinates": [ 10.4064, 55.3951 ] } ], "and": [ {"eq": [ { "property": "direction" }, "east" ] } ] }
print(pygeofilter.ast.get_repr(parse_json(cql_json)))
INTERSECTS(ATTRIBUTE geometry, Geometry(geometry={'type': 'Point', 'coordinates': [10.4064, 55.3951]}))

This example does look like the wrong behavior.
Example 2 where pygeofilter parses invalid and into a simple comparison:

import pygeofilter.ast
from pygeofilter.parsers.cql_json import parse as parse_json
cql_json = { "and": [ {"eq": [ { "property": "direction" }, "east" ] } ] }
print(pygeofilter.ast.get_repr(parse_json(cql_json)))
ATTRIBUTE direction = 'east'

In this case, the and is perfectly valid (just useless and so it
semantically drops out).

Needless to say it would be a better user experience if both these
examples would fail with some meaningful message.
—
Reply to this email directly, view it on GitHub
https://github.com/geopython/pygeofilter/issues/47, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABIHXHDN4PH5ABBKOVRMTLVOB2HVANCNFSM5YGBXMIQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


zram-reloader.service broken by security.lockKernelModules

Now that I'm using the hardened profile, which enables
security.lockKernelModules, whenever I run nixos-rebuild switch,
I'm told that the systemd unit zram-reloader.service failed with the
error "Operation not permitted" while trying to unload the zram
kernel module.
I'm not saying this is a bug — it seems to be the lockKernelModules
feature working as intended — but it's a bit annoying and I wonder
whether something could be done about it.

Explicitly specifying the kernel modules required by zram.

The zram module is loaded; the "problem" is that the
zram-reloader.service unit tries to unload and reload the module
(to, I'd guess, ensure that the module's parameters match what's been
specified in the NixOS configuration).

I think the best you can do is order the unit before locking occurs, so that it at least has an opportunity to work once (at boot), but it will fail on all subsequent reloads. That's just how the feature works, I'm afraid.

I was more thinking that zram-reloader.service could just be
disabled if security.lockKernelModules is enabled, which would at
least prevent nixos-rebuild from always complaining about it, but
having it run once before modules are locked does sound better.

Another idea is to make the reload service bail early if the lock is engaged or, equivalently, condition its execution on whether the locking unit is active. This combined with proper ordering should make using the reloader smoother. Ideally, it'd work once and then not bother trying after that.

still important to me


Storefront not accessible trough IP in Shopware 6

Description
I have installed a fresh Shopware 6 installation using the Dockware Docker container on my Ubuntu server. I'm using the following config in my docker-compose.yml file:
version: "3"

services:

    shopware:
      # use either tag "latest" or any other version like "6.1.5", ...
      image: dockware/dev:latest
      container_name: shopware
      ports:
         - 80:80
         - 3306:3306
         - 22:22
         - 8888:8888
         - 9999:9999
      volumes:
         - "db_volume:/var/lib/mysql"
         - "shop_volume:/var/www/html"
      networks:
         - web
      environment:
         # default = 0, recommended to be OFF for frontend devs
         - XDEBUG_ENABLED=1
         # default = latest PHP, optional = specific version
         - PHP_VERSION=7.4

volumes:
  db_volume:
    driver: local
  shop_volume:
    driver: local

networks:
  web:
    external: false

Everything in the admin panel works fine, but I can't access the storefront trough ip. It throws an 500 internal server error when being accessed, and I can't find any logs in the Shopware admin panel. The IP/admin route works fine though.
Why does this not work? Does shopware not allow the storefront to be directly accessed by IP? I don't have a domain at the moment to test this theory with.
Someone also made a ticket on this error on the Shopware forum.

It's normal. The 500 error is because there is no active sales channel found with the request name. Add the IP address as 'domain' for your sales channel, and it will work again.

channel

Short question I have the same problem how do I add the IP address as 'domain' for my sales channel without having access to my /admin page

channel

Short question I have the same problem how do I add the IP address as 'domain' for my sales channel without having access to my /admin page
When I Try to use the admin page

That's a different problem that I can't 'debug' without seeing the actual server error. The /admin will always be available, also when the sales channel is not set up yet.

channel

Short question I have the same problem how do I add the IP address as 'domain' for my sales channel without having access to my /admin page
When I Try to use the admin page

That's a different problem that I can't 'debug' without seeing the actual server error. The /admin will always be available, also when the sales channel is not set up yet.

First THX for the quick answer. I keep you up to date for now. I'm trying the non docker version for the production system first then we will see 👍

I guess this has been solved here. If not feel free to write

I guess this has been solved here. If not feel free to write

It's normal. The 500 error is because there is no active sales channel found with the request name. Add the IP address as 'domain' for your sales channel, and it will work again.

Can you go into detail how am i supposed to do this?


Slow rendering of CameraRoll images since 0.4.0

Hi,
Images from the CameraRoll are very slow to render since 0.4.0 (up to a minute). Downgrading to 0.3.11 solves the issue.
This can be reproduced in a brand new app, or in the UIExplorer for example. I can attach some sample code to the issue if needed.
Thanks

That would be helpful - thanks!

To reproduce
react-native init TestImagesLoadingTime

then replace the contents of index.ios.js with this : https://gist.github.com/VonD/a530d21a53499a085080
Below are the captures of the same code with react-native 0.3.11 and 0.4.0 (sorry, the second one is quite heavy)

I can confirm the issue - the Image component appears to specifically be slow with CameraRoll images.

+1 @rt2zz

+1

+1

Here's a work-around: http://stackoverflow.com/a/29903737/2313477

@scottdixon that may be a seperate issue, but I just tested on 0.4.1 and loading the lower quality image does not solve the delay issue.
I did some debugging through the obvious image code, and everything is returning fast, RCTImageLoader.m loadImageWithTag which returns to RCTStaticImageManager.m RCT_CUSTOM_VIEW_PROPERTY(imageTag, NSString, RCTStaticImage) are are both running with minimal latency, yet there still is a lag of ~5s before the actual image renders to screen.

I have cameraroll on a tab and it is very slow to render the images, but if i click another tab straight away and come back quickly then the images are shown. Seems like the image does not trigger a loaded event, but once cached it works immediately

possibly related xcode logging about assetsd?
2015-04-30 11:39:42.464 ...[1274:189831] Connection to assetsd was interrupted or assetsd died
2015-04-30 11:39:42.637 ...[1274:190017] Communications error: <OS_xpc_error: <error: 0x19caaba80> { count = 1, contents =
	"XPCErrorDescription" => <string: 0x19caabe78> { length = 22, contents = "Connection interrupted" }
}>

I have developed a quick fix for this issue at https://github.com/aroth/react-native. The slow load times can be resolved by wrapping the asset callback in a dispatch_async call:
dispatch_async(dispatch_get_main_queue(), ^{
    callback(nil, image);
});

Secondly, loading a large number of images will trigger memory warnings and/or OOM crashes. Using the thumbnail method of the ALAsset class can help remedy this (especially useful when iterating over images from the camera roll). I have updated image loading code to take in a representation string:  full, screen or thumbnail. The default is 'full' if not provided.
<Image
  source={asset.node.image}
  representation={'thumbnail'}
  style={imageStyle}
/>

Full pull request pending.

@aroth thanks! dispatch_async definitely fixes the load time

@aroth - nice one :smile:

@aroth thanks!
About the image representation property : RN docs mention that the Image component already picks the most efficient representation (http://facebook.github.io/react-native/docs/image.html#best-camera-roll-image) : does your implementation do something different/more about it ?
About your PR : what's the status on that ?

@aroth You might want to remove npm-debug.log from your https://github.com/aroth/react-native/commit/453064b743f7417b6c969ab135442a08eccacb04 commit.

I've created a pull request at https://github.com/facebook/react-native/pull/1263 to address the slow CameraRoll image load issue only.
As for asset representation (fullScreen, fullResolution, or thumbnail)  -- I would like to address that concern separately in another Issue/PR. As is, even with this PR, loading several full resolution CameraRoll images will cause memory to spike and the app will likely crash. Thumbnail versions should be accessible and used when appropriate.
@vonD - I may be wrong, but it appears that the docs are a bit misleading. If you review RCTImageLoader.m you will see that the full resolution image is loaded for any image passed into loadImageWithTag: with an assets-library prefix.
UIImage *image = [UIImage imageWithCGImage:[representation fullResolutionImage] scale:1.0f orientation:(UIImageOrientation)orientation];

My previous implementation did not automatically handle this. Instead, it required passing in a representation string (full, screen or thumbnail). I'm looking into the issue further to see if it can be handled in a more efficient way.

@aroth thanks for the clarification. Have you been able to make progress on making the representation configurable ? That would indeed be very useful. Should I open an issue for that ?
Also, if the reprensentation is configurable, the orientation should be too, to avoid, e.g. displaying an upside down thumbnail.

The fix for this has been merged!

@VonD - if the fix doesn't solve all of your issues, it would be great if you could open another issue! :smile:

@brentvatne Thanks, this was merged internally by @nicklockwood a couple of weeks ago.
@VonD We still need support for configurable representation and orientation of ALAssets/PHAssets.
https://github.com/facebook/react-native/blob/master/Libraries/Image/RCTImageLoader.m#L81
https://github.com/facebook/react-native/blob/master/Libraries/Image/RCTImageLoader.m#L82
Another issue should be opened. I will try to involve myself this week. Thanks again.

@brentvatne @VonD CameraRoll in 0.6.0 is still dog slow for me.
Any thoughts on this note from the ALAssetRepresentation documentation?

IMPORTANT
The Assets Library framework is deprecated as of iOS 9.0. Instead, use the Photos framework instead, which in iOS 8.0 and later provides more features and better performance for working with a user’s photo library. For more information, see Photos Framework Reference.
In the Photos framework, the PHAsset and PHImageManager classes provide functionality for fetching an asset’s image or video data.

The issue about the image representation can be found here : #1567


wait for dispatch

I am using redux-connect to load initial data.
When using thunks, I can simply do:
const resolve = [{
  promise: ({params, store}) => store.dispatch(init(params.layout))
}];

store.dispatch returns a promise.
What's the proper way to implement it in redux-logic?
Below is my solution, but I think there should be more elegant way to do it.
const resolve = [{
  promise: ({params, store}) => {
    const defer = {};
    defer.promise = new Promise((res, rej) => {
      defer.resolve = res;
      defer.reject = rej;
    });
    store.dispatch(init(params.layout, defer));
    return defer.promise;
  },
}];

The logic handler calls defer.resolve() before calling done().
init() is a simple action creator.

@lsentkiewicz Thanks for asking the question. I haven't seen redux-connect but it is pretty neat.
I have been meaning to write up some guides (recipe books) on how to do various things especially with regards to loading data and such.
Typically what I have been doing is to have redux-logic that listens for an action pertaining to the route, like R:/foo/bar/baz.
So I trigger those actions as the route changes and thus the logic gets run whenever it is needed.
On the server then one can just do something like
store.dispatch({ type: 'R:/foo/bar/baz' });

// store.logicMiddleware.whenComplete waits for any
// in-flight async logic processing to complete before returning
store.whenComplete(() => {
  // state is ready for rendering
  ReactDOM.renderToString(...)
});

I need to create a formal example that explains all of this.
I'll also look closer at redux-connect and your idea of how to possibly use that.

I think it should work:
const resolve = [{
  promise: ({params, store}) => {
    store.dispatch(init(params.layout));
    return store.whenComplete();
  }
}]

The wrapped component won't be rendered until the promise is resolved.
But I am not sure if #54 (infinite logic) can cause any issues.
I am not using server-side rendering in my app.

I had a typo in previous example which I fixed. store.whenComplete should be store.logicMiddleware.whenComplete since I manually attach logicMiddleware to store after creating it so that it is available for later use.
Yes, infinite logic (by its definition) would not complete so the whenComplete would never be called, but if you don't have situation then it should be fine. The only other thing that might cause similar issues is if one has anything that is timer based that continues to dispatch, that might keep whenComplete open longer than desired otherwise it should work.


Using the TSQL method will take some time for the TSQL command to return, but ...

... when it returns and says its completed, its actually not completed. The job is still running often time.
If this is intended to be non-blocking, it should not take more than a few seconds to initiate and report back success.  The command actually processes for 10+ minutes before stating its complete, and often times the copy process needs another hour or four to complete.
Can these commands please either block or run async and not mix the two? Its confusing.

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

ID: fc3f1726-f5b5-e504-33c4-8ceefa5b02f7
Version Independent ID: baf2eb27-05bf-8d85-2a34-2f6c0ef739b1
Content: Copy an Azure SQL database
Content Source: articles/sql-database/sql-database-copy.md
Service: sql-database
Sub-service: data-movement
GitHub Login: @stevestein
Microsoft Alias: sahsan

@StingyJack Thank you very much for the detailed feedback. If there are specific product features or functionality you would like to suggest, the Azure SQL Feedback Forum (link) is best for a dialog directly with the product group.
With regard to the documentation, there is additional detail on monitoring the progress of the copy activity (link).
I went looking for an sql script that could serve as an example, where instead of just passing the CREATE DATABASE... T-SQL you would include a clause that reports on the state_desc value from sys.databases and when a state of ONLINE is reached...the script can report success.
Please let me know if I have missed something with your request.

We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


webhook: fix non-matching webhook secrets not being rejected

Fixes an issue which allowed webhooks to be processed with an incorrect webhook secret.
This adds a case to return a 401 when the verify function returns false. The verify function also always returns false as it is being passed in JSON from a WorkflowJob webhook object instead of the request body (which is how GitHub generates it's signitures) meaning the signatures will never match (see https://github.com/yanyongyu/githubkit?tab=readme-ov-file#webhook-verification).

I am not familiar with FastAPI at all so if there is a better way of getting the request body without having to add async that you know of I am happy to change it :)


Show a random funny warning message if already turned off guns are tried to be turned off again

Rejected because of the following reasons:

See the explanation in #1.
Calling the same command twice should be disabled once #15 is implemented.


Replace currying and and uncurrying functions with dynamic implementa…

…tions.
Description of the change
Replaces mkFn/runFn FFIs with more scalable dynamic implementations.

Checklist:

[ ] Added the change to the changelog's "Unreleased" section with a reference to this PR (e.g. "- Made a change (#0000)")
[x] Linked any existing issues or proposals that this pull request should close
[x] Updated or added relevant documentation
[ ] Added a test for the contribution (if applicable)

Thanks for the PR, but what's the thinking behind this - just to cut down on the "dumbness" of the implementation, or does it perform better than the explicit implementations? If so, can you provide a benchmark please. 🙂

Thanks for the PR, but what's the thinking behind this - just to cut down on the "dumbness" of the implementation, or does it perform better than the explicit implementations? If so, can you provide a benchmark please. 🙂

@garyb mainly just to reduce LOC. I'm not sure if it's optimal but i can look into benchmarking and optimisation.

@garyb mainly just to reduce LOC. I'm not sure if it's optimal but i can look into benchmarking and optimisation.

@garyb some simple benchmarking with alternative implementations: https://gist.github.com/yangzai/5fd62a13c9281b76878659a1b94d4885. I don't think the performance drop can be justified so I should probably close this.

Thanks for following up! Yeah, I think we'll keep them as they are then - this is potentially a slightly performance-sensitive area. Mostly the intended use case for these is when the runFn stuff is fully saturated and the compiler optimises the intermediate calls away, but when that's not the case we'd still want minimal overhead.


Typo: the the -> the in docs and comments

I noticed that in a lot of places it says the the instead of the.
So often I wasn't sure if maybe it's actually meant to say e.g. List all the objects in the the path. But then there's places with sentences like If so, it extracts the the private key which definitely sounds wrong.
I ran a global s/the the/the/ over all files in the repo. Hope this makes sense.

Thanks for that!
I've dropped the changes in vendor as those aren't really my code!
Merged in 5894c02a346a511b516a8463be083edccc77dd36
Thanks for your contribution
Nick


Fixed Optional Spelled Incorrectly in Docs #172

See #172

We've just released LumX v1.0.0rc1. This new version fixes the issue, so I'm closing your PR. Thank you!


chore: semantic-release config update

semantic-release config update

@megheaiulian is this a recent addition to the semantic-release tool? We should update all components with this bit.

@cristinecula It seems the default preset is angular which does not use ! for a breaking change and has a few other differences.  If we lint commit using conventionalcommits format we should also use it for semantic-release. Maybe the default has changed between versions?

Probably...

Or should we just switch to gitmoji? :D

:sparkles:


Metal compile fixes when compiling with MacOS SDK 14 (Xcode 15)

Description
Update wrapped protocols to match MacOS SDK 14 declarations

Replaced by https://github.com/baldurk/renderdoc/pull/3068


DataTable/DataColumn - distinct

have a way to fetch distinct values of a table/column

implemented in 6f243e89bd8464087699f9cc2b1188563b914edd


[Document] - Frontend Version 5.3 How to run on mac?

**UE Version: **
E.g. UE 5.1.1
**Frontend Version: **
E.g. UE5.3-0.3.0
How to run on mac locally? Is there any specific guide guide for it?

Thank you for raising the issue @rahulcs1988.
We are currently internally tracking an enhancement request to add mac support and will provide an update when we have one, as well as accompanying documentation.

Hey @rahulcs1988,
As we've already shipped the release for UE5.3, we won't be adding more features to it. That being said, we've added the required functionality to UE5.4 and master branches, as seen here.
The scripts work the same as they would for any other platform so you should be good to go.
Cheers


allow perMessageDeflate socket config for azure

Sails version: 0.12.14
Node version:8.9.2
NPM version:5.6.0
DB adapter name: N/A
DB adapter version: N/A
Operating system:Ubuntu

I just spun up my dockerized sails app in Azure Web Apps for Containers. Sadly, websockets are not working.
Happily, the Microsoft FAQ has a suggestion for getting it to work:
var io = require('socket.io')(server,{
  perMessageDeflate :false
});

https://docs.microsoft.com/en-us/azure/app-service/containers/app-service-linux-faq
There's some indication that this attribute is in fact a thing:
https://socket.io/blog/socket-io-1-4-0/
Ideally, I'd be able to add this setting to my socket config file and have it get passed into initialization.
Sadly, perMessageDeflate is not one of the attributes that are effectively whitelisted as possible inputs to the socket initialization:
https://github.com/balderdashy/sails-hook-sockets/blob/b78a0bc907d171f04fc43124066188da49d0760f/lib/initialize.js#L65
The easiest solution would just be to add another conditional to pass this attribute into the initialization options, and I'd be happy to open a PR for that on the sails-hook-sockets repo.

I can confirm that by hacking in the fix as I envisioned it:
if (app.config.sockets.perMessageDeflate === false) {
  opts.perMessageDeflate = app.config.sockets.perMessageDeflate;
}

I've now got websockets working on Azure Web Apps for Containers.

@shackbarth thanks!  I'll take a look ASAP.

https://trello.com/c/otrar7f4

What I did was to add
sed -i 's/if (app.config.sockets.transports) {/if (app.config.sockets.perMessageDeflate === false) {\nopts.perMessageDeflate = app.config.sockets.perMessageDeflate;\n}\nif (app.config.sockets.transports) {/g' node_modules/sails-hook-sockets/lib/initialize.js

into a postinstall step, and then I added
    perMessageDeflate: !process.env.DISABLE_SOCKET_DEFLATE,

into sockets.js,
and then I added DISABLE_SOCKET_DEFLATE=true as an application variable in Azure App Service.
I'm anticipating that when this issue is resolved I'll be able to get rid of the sed hack. If your application is only on azure you can just hardcode
    perMessageDeflate: false,

in sockets.js


Fix password checking in 'SELECT'.

We currently could bypass the password by simply give use "" as password
<IP_ADDRESS>:12345> SELECT thedisk
OK
<IP_ADDRESS>:12345> SET a 1
(error) Namespace is in read-only mode
<IP_ADDRESS>:12345> SELECT thedisk ""
OK
<IP_ADDRESS>:12345> SET a 1
"\x04\x00\x00\x00"

The length given to strncmp should be length of the stored
password, not length of given password.

The latest patches fix exact matching strings issue and a wrong reloaded password when reloading zdb


Unify error handling behavior for subscriptions.

The error handling behavior between persistent and non-persistent subscriptions is inconsistent and partly erroneous:

Persistent subscriptions do not handle the "requires leader" case.
Non persistent subscriptions call onError() twice in the case of NotLeaderException

This pull requests unifies the behavior and avoids duplicate calls to the error listener.

Nice catch by the way


Finnish translation

Finnish translation for tagging plugin. Tested in my Discourse installation and worked quite nicely.

Thanks!


Do not use the Kotlin JVM plugin in a Gradle plugin

If I understand this correctly, the Kotlin JVM plugin is applied to the plugin, which is not recommended, actually the kotlin-dsl plugin should be applied instead, this way you can actually use the Kotlin DSL in plugins

the Kotlin JVM plugin is applied to the plugin, which is not recommended

I'm applying the Kotlin JVM plugin because I want to give the opportunity to write the plugin in Kotlin. Can you elaborate on why this is not reccomended?

actually the kotlin-dsl plugin should be applied instead, this way you can actually use the Kotlin DSL in plugins

You apply java-gradle-plugin and kotlin-jvm, instead you should use kotlin-dsl

actually the kotlin-dsl plugin should be applied instead, this way you can actually use the Kotlin DSL in plugins

You apply java-gradle-plugin and kotlin-jvm, instead you should use kotlin-dsl

Can you elaborate on why?

As the Gradle API is kotlin, there is some magic going on for the Kotlin DSL

That's exactly the "magic" I don't like. I know kotlin-dsl generates accessors and makes 'easier' to use Kotlin in Gradle scripts. It's my personal preference to don't use it.
Ultimately this is a template and it's up to you to decide if you want to customize it or not.

That's exactly the "magic" I don't like. I know kotlin-dsl generates accessors and makes 'easier' to use Kotlin in Gradle scripts. It's my personal preference to don't use it.

So you rather want to make it less type-safe? I am not sure if I understand why you don't want to use accessors. However, okay your decision, however that also blocks users from using the Kotlin Extension functions that they come to know from using a Kotlin DSL buildscript, which now means that your example and the code in the plugin has different semantics, whilst they should be identical, which can be very confusing


Updates to re-pull code

Hey Caitlin!
I decided to break up what I thought was the first PR into two - just to make things easier to review. It looks bigger than it is, I promise.
Changes here are tweaks to the re-pull for the volunteer locations. Specifically, we added a few QA summaries to the reducer for each of the missions to help with our assessment of data quality in scripts that you'll see in the next PR.
This should be pretty short-and-sweet (like hopefully less than 30 mins), with the bulk of the 'review' in the eePlumB/2_data_ingestion/re_pull_functions.py script. Though I'm just seeing that I didn't add docstring to all of the functions - hopefully they are straightforward. I created #84 so I remember to come back to it.
We are storing data in this repository, since they are small files and it works better for outside collaborators.
This is when I need you to wear your GEE hat. Is my bit logic correct? Did I convert from DN correctly? Basically, rudimentary check to make sure I don't add unnecessary error into the pipeline!
This is progress on #42, #75 and #77.

Rockstar. Thank you @ccmothes! I'll have another one incoming today or tomorrow.


Removed --sslv3 due to poodle vulnerability

SSLV3 has been disabled by default on majors servers. Unify server doesn't support anymore sslv3.

Thanks! Merged..


Simple Design Idea/Request (on diaper requests page)

Hi all!
Every time I open the diaper requests page, I secretly wish that the pending requests "stuck out" in some way, to be able to more easily visually differentiate them from those that have been fulfilled. Maybe just changing the font some how? Or, better yet, maybe the same colored box system that is used on the agency request page?? This would certainly better maintain design consistency throughout the application. :)
Thanks!

We currently have this pattern in partner agencies that can be used as an example.

I can take this!


RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:1 and cuda:0! (when checking argument for argument index in method wrapper_CUDA__index_select)

我使用llama 65b 在多GPU A100 infer.py推理的时候报了错误， 在finetune.py没有问题

/slurm/home/yrd/shaolab/daiyizheng/.conda/envs/llama/lib/python3.10/site-packages/bitsandbytes/cuda_setup/main.py:136: UserWarning: /slurm/home/yrd/shaolab/daiyizheng/.conda/envs/llama did not contain libcudart.so as expected! Searching further paths...
warn(msg)
/slurm/home/yrd/shaolab/daiyizheng/.conda/envs/llama/lib/python3.10/site-packages/bitsandbytes/cuda_setup/main.py:136: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('/run/user/80104/vscode-git-4b808d81bf.sock')}
warn(msg)
/slurm/home/yrd/shaolab/daiyizheng/.conda/envs/llama/lib/python3.10/site-packages/bitsandbytes/cuda_setup/main.py:136: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('/run/user/80104/vscode-ipc-0b328df5-e364-494a-b230-9f7e99271b5b.sock')}
warn(msg)
/slurm/home/yrd/shaolab/daiyizheng/.conda/envs/llama/lib/python3.10/site-packages/bitsandbytes/cuda_setup/main.py:136: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('() {  eval /usr/bin/modulecmd bash $*\n}')}
warn(msg)
The tokenizer class you load from this checkpoint is not the same type as the class this function is called from. It may result in unexpected tokenization.
The tokenizer class you load from this checkpoint is 'LLaMATokenizer'.
The class this function is called from is 'LlamaTokenizer'.
The model weights are not tied. Please use the tie_weights method before using the infer_auto_device function.
Loading checkpoint shards:   0%|          | 0/81 [00:00<?, ?it/s]
Loading checkpoint shards:   1%|          | 1/81 [00:00<01:08,  1.16it/s]
Loading checkpoint shards:   2%|▏         | 2/81 [00:01<01:11,  1.11it/s]
Loading checkpoint shards:   4%|▎         | 3/81 [00:02<01:13,  1.07it/s]
Loading checkpoint shards:   5%|▍         | 4/81 [00:03<01:10,  1.09it/s]
Loading checkpoint shards:   6%|▌         | 5/81 [00:04<01:09,  1.09it/s]
Loading checkpoint shards:   7%|▋         | 6/81 [00:05<01:09,  1.08it/s]
Loading checkpoint shards:   9%|▊         | 7/81 [00:06<01:10,  1.05it/s]
Loading checkpoint shards:  10%|▉         | 8/81 [00:07<01:07,  1.08it/s]
Loading checkpoint shards:  11%|█         | 9/81 [00:08<01:08,  1.05it/s]
Loading checkpoint shards:  12%|█▏        | 10/81 [00:09<01:06,  1.07it/s]
Loading checkpoint shards:  14%|█▎        | 11/81 [00:10<01:05,  1.06it/s]
Loading checkpoint shards:  15%|█▍        | 12/81 [00:11<01:04,  1.08it/s]
Loading checkpoint shards:  16%|█▌        | 13/81 [00:12<01:02,  1.08it/s]
Loading checkpoint shards:  17%|█▋        | 14/81 [00:13<01:02,  1.07it/s]
Loading checkpoint shards:  19%|█▊        | 15/81 [00:14<01:03,  1.05it/s]
Loading checkpoint shards:  20%|█▉        | 16/81 [00:15<01:02,  1.04it/s]
Loading checkpoint shards:  21%|██        | 17/81 [00:16<01:02,  1.02it/s]
Loading checkpoint shards:  22%|██▏       | 18/81 [00:16<01:01,  1.03it/s]
Loading checkpoint shards:  23%|██▎       | 19/81 [00:17<01:00,  1.03it/s]
Loading checkpoint shards:  25%|██▍       | 20/81 [00:18<00:59,  1.02it/s]
Loading checkpoint shards:  26%|██▌       | 21/81 [00:19<00:58,  1.02it/s]
Loading checkpoint shards:  27%|██▋       | 22/81 [00:20<00:57,  1.02it/s]
Loading checkpoint shards:  28%|██▊       | 23/81 [00:21<00:57,  1.01it/s]
Loading checkpoint shards:  30%|██▉       | 24/81 [00:22<00:55,  1.04it/s]
Loading checkpoint shards:  31%|███       | 25/81 [00:23<00:52,  1.07it/s]
Loading checkpoint shards:  32%|███▏      | 26/81 [00:24<00:51,  1.07it/s]
Loading checkpoint shards:  33%|███▎      | 27/81 [00:25<00:50,  1.07it/s]
Loading checkpoint shards:  35%|███▍      | 28/81 [00:26<00:49,  1.06it/s]
Loading checkpoint shards:  36%|███▌      | 29/81 [00:27<00:48,  1.08it/s]
Loading checkpoint shards:  37%|███▋      | 30/81 [00:28<00:47,  1.07it/s]
Loading checkpoint shards:  38%|███▊      | 31/81 [00:29<00:45,  1.09it/s]
Loading checkpoint shards:  40%|███▉      | 32/81 [00:30<00:45,  1.07it/s]
Loading checkpoint shards:  41%|████      | 33/81 [00:31<00:44,  1.09it/s]
Loading checkpoint shards:  42%|████▏     | 34/81 [00:31<00:42,  1.10it/s]
Loading checkpoint shards:  43%|████▎     | 35/81 [00:32<00:42,  1.09it/s]
Loading checkpoint shards:  44%|████▍     | 36/81 [00:33<00:40,  1.10it/s]
Loading checkpoint shards:  46%|████▌     | 37/81 [00:34<00:38,  1.13it/s]
Loading checkpoint shards:  47%|████▋     | 38/81 [00:35<00:38,  1.12it/s]
Loading checkpoint shards:  48%|████▊     | 39/81 [00:36<00:37,  1.12it/s]
Loading checkpoint shards:  49%|████▉     | 40/81 [00:37<00:37,  1.08it/s]
Loading checkpoint shards:  51%|█████     | 41/81 [00:38<00:36,  1.11it/s]
Loading checkpoint shards:  52%|█████▏    | 42/81 [00:39<00:34,  1.11it/s]
Loading checkpoint shards:  53%|█████▎    | 43/81 [00:40<00:34,  1.10it/s]
Loading checkpoint shards:  54%|█████▍    | 44/81 [00:41<00:34,  1.08it/s]
Loading checkpoint shards:  56%|█████▌    | 45/81 [00:42<00:33,  1.08it/s]
Loading checkpoint shards:  57%|█████▋    | 46/81 [00:43<00:33,  1.06it/s]
Loading checkpoint shards:  58%|█████▊    | 47/81 [00:43<00:31,  1.07it/s]
Loading checkpoint shards:  59%|█████▉    | 48/81 [00:44<00:30,  1.09it/s]
Loading checkpoint shards:  60%|██████    | 49/81 [00:45<00:29,  1.08it/s]
Loading checkpoint shards:  62%|██████▏   | 50/81 [00:46<00:29,  1.07it/s]
Loading checkpoint shards:  63%|██████▎   | 51/81 [00:47<00:27,  1.07it/s]
Loading checkpoint shards:  64%|██████▍   | 52/81 [00:48<00:27,  1.05it/s]
Loading checkpoint shards:  65%|██████▌   | 53/81 [00:49<00:27,  1.03it/s]
Loading checkpoint shards:  67%|██████▋   | 54/81 [00:50<00:25,  1.04it/s]
Loading checkpoint shards:  68%|██████▊   | 55/81 [00:51<00:26,  1.00s/it]
Loading checkpoint shards:  69%|██████▉   | 56/81 [00:52<00:24,  1.02it/s]
Loading checkpoint shards:  70%|███████   | 57/81 [00:53<00:23,  1.02it/s]
Loading checkpoint shards:  72%|███████▏  | 58/81 [00:54<00:22,  1.04it/s]
Loading checkpoint shards:  73%|███████▎  | 59/81 [00:55<00:20,  1.06it/s]
Loading checkpoint shards:  74%|███████▍  | 60/81 [00:56<00:19,  1.06it/s]
Loading checkpoint shards:  75%|███████▌  | 61/81 [00:57<00:19,  1.05it/s]
Loading checkpoint shards:  77%|███████▋  | 62/81 [00:58<00:18,  1.05it/s]
Loading checkpoint shards:  78%|███████▊  | 63/81 [00:59<00:17,  1.04it/s]
Loading checkpoint shards:  79%|███████▉  | 64/81 [01:00<00:15,  1.06it/s]
Loading checkpoint shards:  80%|████████  | 65/81 [01:01<00:14,  1.07it/s]
Loading checkpoint shards:  81%|████████▏ | 66/81 [01:01<00:13,  1.08it/s]
Loading checkpoint shards:  83%|████████▎ | 67/81 [01:02<00:12,  1.10it/s]
Loading checkpoint shards:  84%|████████▍ | 68/81 [01:03<00:12,  1.08it/s]
Loading checkpoint shards:  85%|████████▌ | 69/81 [01:04<00:10,  1.10it/s]
Loading checkpoint shards:  86%|████████▋ | 70/81 [01:05<00:10,  1.09it/s]
Loading checkpoint shards:  88%|████████▊ | 71/81 [01:06<00:09,  1.07it/s]
Loading checkpoint shards:  89%|████████▉ | 72/81 [01:07<00:08,  1.09it/s]
Loading checkpoint shards:  90%|█████████ | 73/81 [01:08<00:07,  1.05it/s]
Loading checkpoint shards:  91%|█████████▏| 74/81 [01:09<00:06,  1.07it/s]
Loading checkpoint shards:  93%|█████████▎| 75/81 [01:10<00:05,  1.08it/s]
Loading checkpoint shards:  94%|█████████▍| 76/81 [01:11<00:04,  1.09it/s]
Loading checkpoint shards:  95%|█████████▌| 77/81 [01:12<00:03,  1.08it/s]
Loading checkpoint shards:  96%|█████████▋| 78/81 [01:13<00:02,  1.05it/s]
Loading checkpoint shards:  98%|█████████▊| 79/81 [01:14<00:01,  1.06it/s]
Loading checkpoint shards:  99%|█████████▉| 80/81 [01:15<00:00,  1.06it/s]
Loading checkpoint shards: 100%|██████████| 81/81 [01:15<00:00,  1.21it/s]
Loading checkpoint shards: 100%|██████████| 81/81 [01:15<00:00,  1.07it/s]
Traceback (most recent call last):
File "/slurm/home/yrd/shaolab/daiyizheng/nlp/Huatuo-Llama-Med-Chinese/infer.py", line 132, in
fire.Fire(main)
File "/slurm/home/yrd/shaolab/daiyizheng/.conda/envs/llama/lib/python3.10/site-packages/fire/core.py", line 141, in Fire
component_trace = _Fire(component, args, parsed_flag_args, context, name)
File "/slurm/home/yrd/shaolab/daiyizheng/.conda/envs/llama/lib/python3.10/site-packages/fire/core.py", line 475, in _Fire
component, remaining_args = _CallAndUpdateTrace(
File "/slurm/home/yrd/shaolab/daiyizheng/.conda/envs/llama/lib/python3.10/site-packages/fire/core.py", line 691, in _CallAndUpdateTrace
component = fn(*varargs, **kwargs)
File "/slurm/home/yrd/shaolab/daiyizheng/nlp/Huatuo-Llama-Med-Chinese/infer.py", line 118, in main
infer_from_json(instruct_dir)
File "/slurm/home/yrd/shaolab/daiyizheng/nlp/Huatuo-Llama-Med-Chinese/infer.py", line 105, in infer_from_json
model_output = evaluate(instruction)
File "/slurm/home/yrd/shaolab/daiyizheng/nlp/Huatuo-Llama-Med-Chinese/infer.py", line 87, in evaluate
generation_output = model.generate(
File "/slurm/home/yrd/shaolab/daiyizheng/.conda/envs/llama/lib/python3.10/site-packages/peft/peft_model.py", line 731, in generate
outputs = self.base_model.generate(**kwargs)
File "/slurm/home/yrd/shaolab/daiyizheng/.conda/envs/llama/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
File "/slurm/home/yrd/shaolab/daiyizheng/.conda/envs/llama/lib/python3.10/site-packages/transformers/generation/utils.py", line 1611, in generate
return self.beam_search(
File "/slurm/home/yrd/shaolab/daiyizheng/.conda/envs/llama/lib/python3.10/site-packages/transformers/generation/utils.py", line 2982, in beam_search
model_kwargs["past_key_values"] = self._reorder_cache(model_kwargs["past_key_values"], beam_idx)
File "/slurm/home/yrd/shaolab/daiyizheng/.conda/envs/llama/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 762, in _reorder_cache
reordered_past += (tuple(past_state.index_select(0, beam_idx) for past_state in layer_past),)
File "/slurm/home/yrd/shaolab/daiyizheng/.conda/envs/llama/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 762, in
reordered_past += (tuple(past_state.index_select(0, beam_idx) for past_state in layer_past),)
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:1 and cuda:0! (when checking argument for argument index in method wrapper_CUDA__index_select)

我规范的解决方案：


Rename batchChange module/controller/service to dnsChange

Fixes https://github.com/vinyldns/vinyldns/issues/873
Changes in this pull request:

Renames module, controllers, service and directive in modules/portal/public/lib/dns-change/ from BatchChange to DnsChange
Updates their uses and references.

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

Thanks for the contribution @JoshKessler!

@mitruly, I've updated the missed reference. I thought I'd both pushed the change with my non-Comcast GH account and signed the CLA with that one. When I tried to access the CLA just now and made sure to sign in with my personal account, it says "You have signed the CLA for vinyldns/vinyldns." If it stil looks wrong on your end, I may need some guidance with that.

@JoshKessler I believe this is due to your e-mail address in your ~/.gitconfig not matching your open source Github account. Can you try the following steps:

Correct your email in ~/.gitconfig
Rebase with master and push your branch so the new settings will get recognized.


Implement Spanned to retrieve source locations on AST nodes

This PR adds a new trait Spanned to retrieve source spans on AST nodes, see #161 , by recursively traversing the AST and combining spans. This approach is in contrast to the one taken in #839 and #790 by trying to minimise the amount of breaking changes for downstream users, by avoiding wrapping everything in WithSpan<T>.
Main Changes

Spanned trait and Span type added
TokenWithLocation now stores Span, instead of Location
Ident now stores a source span (omitted from Partial/-EQ for compatibility and tests)
Some AST nodes store source tokens where not intrusive
Parser::parse_keyword_token added

The general philosophy of the PR is to be "good enough" without breaking things. As a result certain expressions will have broken or incorrect spans. I imagine these can be cleaned up in future PRs (which might require breaking changes).
f.e. many expressions do not include keywords in their span i.e.
<expr> IS NOT NULL
|....|

will have it's source span simply reported as <expr>::span and there is many such cases, some of which are easier to fix than others. For expressions we can't generate spans for, I use Span::EMPTY as a sort of sentinel value to indicate missing information.
With this approach the only downstream changes a user should have to do to upgrade, should be adding additional fields when matching on AST nodes.
Future Work

Store spans for ast::value::Value. This seems like a breaking change to me, which would require a WithSpan<T> like type
Store keyword TokenWithLocation for expressions that currently don't have them
Implement spans for the rest of the AST, namely Statements. I focused on getting Queries done.

@alamb Hey, we've started using this functionality internally with pretty great success so far. It's still a draft for now, because of the missing todo!'s, but I would appreciate feedback on the overall design and if you think this can get merged in the foreseeable future once issues are addressed. 😄

Thanks @Nyrox  -- I'll try and take a look over the next few days
cc @lovasoa @iffyio and @jmhain

How is this PR going? is it going to merge or what?

Alright, I have now gotten rid of all the todo!s and warnings and un-drafted the PR. There is a lot of missing implementations of spans and I have documented those (in hindsight maybe a derive macro would have been the way to go here, someone better at writing those than me is free to take a shot at it 😅 ).

Bump 😅

Hi @Nyrox!
Thanks for this PR and pushing locations support further!
We had an internal discussion to try to upstream the location changes we use in SYNQ. I found some time to finish rebase today and then noticed your PR. (https://github.com/apache/datafusion-sqlparser-rs/pull/1480)
I like your suggested changes, as they are very noninvasive for the downstream consumers. If this could be included in the main, that would be absolutely amazing. Having location inside every Ident is probably best. In my PR, I wrapped all Idents with location, but our fork uses them only when we need them. Having it always available inside of Indent sounds much better.
It would also be good to design and include wrapping of nodes. It is essential, especially for enum cases where adding location to each of the enum cases would be too verbose. Also in some places those "smaller" locations just don't make much sense. In my PR, I'm using https://github.com/apache/datafusion-sqlparser-rs/pull/1480/commits/fc8e44afd66c3a5100a6546d8edba36c65870315#diff-fc6a8d66b8cb6bd48a119a70e489cbcef82e7f551e7cf08e8e972ef4e774ef49R12259-R12308 to align captured span to a non-whitespace portion of the query based on token indexes.

Hi @lustefaniak, thanks I remember seeing your fork when initially researching this 😅
I agree something like a WithSpan<T> type will probably be needed to improve spans, especially in the case of enums as you said. I think for now the focus, as by the discussions with @alamb was mostly on just reducing the breaking surface as much as we can and get something in. Maybe in a future PR we can start thinking about wrapping all the enums, but then at least we have a gradual roll out 😃

Hey all, think we've gotten quite far here - is there anything actively blocking this from getting approved? Are there any actions I can take to help you guys or do you just need the time to get to this item? 😊

@Nyrox sorry for the delay in getting to this
I don't have any major comments regarding the impl and it seems to align with previous discussions so I'm suspecting this is close.
One aspect I'm not super clear on is how accurate/comprehensive we'll look to be regarding this feature going forward (primarily as it pertains to testing affected code paths), i.e. whether as a best effort, or similar to the other parser functionality (which expectedly requires more effort from PR authors when adding/updating features in the codebase) in order to properly power use cases like @lustefaniak mentions in #1480, or somewhere in-between.
In any case, I would wait for @alamb for when time allows to take a look and provide any thoughts/feedback on the overall approach!

Thanks @Nyrox and @iffyio -- i will try and find time this weke to review this propsoal

@alamb that's really appreciated 🙌

Sorry for my silence / inability to find time to review this PR in depth. I am struggling with too many thing
TLDR I I think we should:

Get the tests passing on this PR and merge it in (if not all AST nodes have spans initially, we can file tickets to add the information over the next few releases)
Add some documentation explaining what is happening and how downstream consumers need to change (I think basically by ignoring the newly added fields

@iffyio  and I spoke about this a bit -- basically in my opinion adding source locations to sqlparser-rs is one of the last major remaining features it is missing.
However, it also has the potential to be very disruptive to downstream consumers.
It seems to me the requirements for this change are:

Any changes required by users of this crate should be mechanical
We should clearly document what changes are needed on upgrade (ideally with examples)

An example of a mechanical change might be adding
match node {
  ast::Query {
    field1,
    field2,
    location: _,  // add a new line to ignored location
}

An example of a non mechanical change might be wrapping all AST nodes in some other struct so the structure of the match no longer works
I looked at this PR and I think it basically satisfies 1 for me so I think we should proceed. Would it be possible to write up something, perhaps in the README that explains  that we are adding new spans to the code and how we will handle them?

Okay, I wrote some documentation and fixed up the tests so CI should pass now (I hope :P )
Let me know what you think of the docs, I wasn't quite sure what to write so I hope it's decent.
@iffyio I ended up running into the problem we discussed further up about comparing queries. It slipped by me that Tokens store the raw string in addition to the Keyword enum, causing select 5 and SELECT 5 to compare as unequal. I have added a new wrapper type IgnoreField to work around this issue and make sure the tokens actually do not impact semantics. I am not exactly sure if this is the best fix, but I think if we want queries to compare as semantically equal rather than syntactically then this is a decent solution for now. lmk what you think

Thanks for the great review. I was definitely a bit sloppy yesterday (Monday 🤮).
I merged main again if you want to give that a quick review as well. :)

I started looking over this PR -- and it is looking great. I took the liberty of merging up from main and fixing clippy/fmt.
I am going to test out the implications of this change by making a PR to DataFusion and test out the documentation.

I plan to merge this PR tomorrow unless there are any other comments

Did we run some benchmarks (e.g. cargo bench)?

Did we run some benchmarks (e.g. cargo bench)?

No, I did not (it is not clear to me we have such a thing). Let me look

cd sqlparser_bench
cargo bench
git remote add Nyrox https://github.com/Nyrox/sqlparser-rs.git
git fetch Nyrox
git checkout Nyrox/main

Here is the benchmark result (it appears to be about 10%-15% slower according to the benchmark):
sqlparser-rs parsing benchmark/sqlparser::select
                        time:   [3.1255 µs 3.1265 µs 3.1276 µs]
                        change: [+15.235% +17.353% +19.853%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 3 outliers among 100 measurements (3.00%)
  3 (3.00%) high severe
sqlparser-rs parsing benchmark/sqlparser::with_select
                        time:   [21.672 µs 21.683 µs 21.694 µs]
                        change: [+11.446% +11.549% +11.653%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 7 outliers among 100 measurements (7.00%)
  4 (4.00%) high mild
  3 (3.00%) high severe

Thanks, looks great. I think 15% degradation is fully worth it (and might be gained back if someone looks at optimizing sqlparser-rs) :)

Yeah, I was looking at the flamegraph and there are a bunch of obvious things to improve performance (like changing next_token not to copy each token)

I filed a ticket to discuss improving performance:

https://github.com/apache/datafusion-sqlparser-rs/issues/1557

I also noticed that there is a bunch of calls to <Location as Display>::fmt which seems quite strange to me. Not sure what the test is doing, but I don't think the parser should be calling that on a non-error path? :p

I also noticed that there is a bunch of calls to ::fmt which seems quite strange to me. Not sure what the test is doing, but I don't think the parser should be calling that on a non-error path? :p

I agree -- it is strange that Parser::expected woud show up so much. One place I see it used is generating errors 🤔
https://github.com/apache/datafusion-sqlparser-rs/blob/2e90e105a74bf9f50f2bad6c22992759ddb06880/src/parser/mod.rs#L3424-L3429

Amusingly when I ran with the fixed benchmarks the result is basically the same (15% slower)
sqlparser-rs parsing benchmark/sqlparser::select
                        time:   [6.5723 µs 6.5856 µs 6.6010 µs]
                        change: [+14.669% +15.020% +15.364%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 12 outliers among 100 measurements (12.00%)
  11 (11.00%) high mild
  1 (1.00%) high severe
sqlparser-rs parsing benchmark/sqlparser::with_select
                        time:   [32.234 µs 32.253 µs 32.277 µs]
                        change: [+14.270% +14.402% +14.538%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 10 outliers among 100 measurements (10.00%)
  5 (5.00%) high mild
  5 (5.00%) high severe

fixed-flamegraph

I am more convinced than ever that we could make a huge performance improvement by doing something like:

https://github.com/apache/datafusion-sqlparser-rs/issues/1558

🚀  -- thanks again @Nyrox @iffyio @lovasoa @lustefaniak @mkarbo @Dandandan  and @yuyang-ok  for helping push this along. It is pretty amazing we'll finally get new things
cc @ankrgyl  it's finally happening

Amazing!!!

BTW if anyone has time to help review another PR, this one adds a bunch of documentation and examples for this feature:

https://github.com/apache/datafusion-sqlparser-rs/pull/1549


Account Details and Leave Table headers don't render

They are defined:
Leave Balances
<TableHead>
                                        <TableRow className={classes.leaveTableRow}>
                                            <TableCell align="left" padding={'none'}><Typography variant={'body3'} component={'div'}>{intl.formatMessage({id: 'LeaveBalance.type'})}</Typography></TableCell>
                                            <TableCell align="left" padding={'none'}>{intl.formatMessage({id: 'LeaveBalance.taken'})}</TableCell>
                                            <TableCell align="left" padding={'none'}>{intl.formatMessage({id: 'LeaveBalance.accrued'})}</TableCell>
                                            <TableCell align="right" padding={'none'} style={{"textAlign": "right"}}>{intl.formatMessage({id: 'LeaveBalance.balance'})}</TableCell>
                                        </TableRow>
                                    </TableHead>

but never render.
Account Balances Header isn't even defined.

@lylehenderson I am not following. The TableHead does render the text for the column headers.

Account Balances doesn't use a table header.
Bret

Maybe because you don't have data? Line 176 only renders the table is there is data.
I bet this is the case. It looks like it renders nothing if the data is returned with no transactions. It needs an empty view.
Bret

[image: image.png]
no headers on either card.
The pages show them properly, but nothing on the cards.
Thanks,
Lyle
On Mon, Oct 16, 2023 at 2:59 PM Bret Hansen @.***>
wrote:

@lylehenderson https://github.com/lylehenderson I am not following. The
TableHead does render the text for the column headers.
[image: Screenshot 2023-10-16 at 2 57 04 PM]
https://user-images.githubusercontent.com/7442142/275659099-d533ac70-68d8-447f-99eb-89108e3e21b7.png
Account Balances doesn't use a table header.
Bret
—
Reply to this email directly, view it on GitHub
https://github.com/ellucian-developer/experience-ethos-examples/issues/29#issuecomment-1765342213,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIGB7CFTOGTRQRW3CEJHXOTX7WU4BAVCNFSM6AAAAAA6CU7ES2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRVGM2DEMRRGM
.
You are receiving this because you were mentioned.Message ID:
@.***
com>

Actually I figured out the defect... too many options displaying.
As soon as I removed all zero balance types from the card. the headers
started working.
PS.. note i did swap out the avail date for activity date.
[image: image.png]
Thanks,
Lyle
On Mon, Oct 16, 2023 at 3:01 PM Bret Hansen @.***>
wrote:

Maybe because you don't have data? Line 176 only renders the table is
there is data.
I bet this is the case. It looks like it renders nothing if the data is
returned with no transactions. It needs an empty view.
Bret
—
Reply to this email directly, view it on GitHub
https://github.com/ellucian-developer/experience-ethos-examples/issues/29#issuecomment-1765344301,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIGB7CF2ROKT43SRGEZ7TADX7WVDZAVCNFSM6AAAAAA6CU7ES2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRVGM2DIMZQGE
.
You are receiving this because you were mentioned.Message ID:
@.***
com>

Hmm none of my screenshots make it to these comments.
I did update the issue title to match the defect found.
I resolved this by:
if (data && Array.isArray(data)) {             const leaves = data.filter(leaves => { return leaves.totalBalance !== '0' });
Removed any zero balance records from the Card preview. Not sure that is the best course of action, but it works.


Cannot read .raw image: LibRawNonFatalError - Unsupported file format

I'm trying to use rawpy.imread to load some .raw images
X = rawpy.imread('Run100000001.raw')

But I get an error saying that the format is not supported or it's not RAW file
_rawpy.pyx in _rawpy.RawPy.open_file (_rawpy.cpp:2457)()
_rawpy.pyx in _rawpy.RawPy.handle_error (_rawpy.cpp:7344)()
LibRawNonFatalError: b'Unsupported file format or not RAW file'

The images can be processed as RAW file using Matlab

Your file format is not supported. There is no RAW camera format called "RAW". rawpy is probably not the library you're looking for. FastRawViewer uses the same underlying library. Try to open your image there. If it works, please re-open this issue.


Dynamic XML Badge not working

Are you experiencing an issue with...
shields.io
🐞 Description
I put in the URL pointing to my pom.xml on GitHub and the XPath for the Spring Boot version. The tool didn't return anything.
pom.xml URL: https://raw.githubusercontent.com/Washingtonwei/hogwarts-artifacts-online/main/pom.xml
XPath:
/project/parent/version
./project/parent/version
.//project/parent/version
Tried all three.
Thanks!
🔗 Link to the badge
https://img.shields.io/badge/dynamic/xml?url=https%3A%2F%2Fraw.githubusercontent.com%2FWashingtonwei%2Fhogwarts-artifacts-online%2Fmain%2Fpom.xml&query=.%2Fproject%2FmodelVersion
💡 Possible Solution
No response

I think this is a duplicate of https://github.com/badges/shields/issues/4250
A working badge URL that achieves what you are trying to do would be
https://img.shields.io/badge/dynamic/xml?url=https%3A%2F%2Fraw.githubusercontent.com%2FWashingtonwei%2Fhogwarts-artifacts-online%2Fmain%2Fpom.xml&query=%2F*[local-name()%3D'project']%2F*[local-name()%3D'parent']%2F*[local-name()%3D'version']

Thanks! It would be great if this can be put in the document.

Yep reasonable point. I've submitted https://github.com/badges/shields/pull/9798 which makes some improvements to the documentation for this badge.


Migrate to Helm Chart

Migrate to Helm Chart for several reasons:

Better leverage our ecosystem projects like skywalking-kubernetes and skywalking-swck, which are recommended for our users and they are more realistic in real use case, and thus reduce duplicate works to replicate the same features in pure Kubernetes resources.
More flexible because we can have fine-grained conditions in the resources with Helm Chart templates.
Don't rely on users' local installation (version) of tools such as istioctl, the only requirement is Helm.
Easy to add features that are supported in our official eco-system projects, such as, adding new storage options (such as postgresql), will be much more easier.

I'm running the postgresql demos in my environment and will merge this when I think it's ready

@innerpeacez welcome to try this and advice

I love this idea. Using helm/operator is much better than writing all these again.
BTW, we should consider a new helm release as many changes have been made.

BTW, we should consider a new helm release as many changes have been made.

You mean skywalking-kubernetes repo right?

You mean skywalking-kubernetes repo right?

Yes, that.

How do we lock the version of helm repo? I can't find the relative changes of make.in in the root.

@innerpeacez welcome to try this and advice

WOW!!! looking forward to this.


Shortcut checkpoint after a fallback

since the fallback is PBFT, we can simply set the checkpoint already

requires info regarding sigs of the checkpoint from other replicas, which will be stored on the rep for further checkpoint. Such info will be generated on each rep only after fallback is finished so it probably requires one round of agreement, not really helping perf that much..


Multiple NullPointerException in com.facebook.react.uimanager

[X] Review the documentation: https://facebook.github.io/react-native
[X] Search for existing issues: https://github.com/facebook/react-native/issues
[] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment
OS: macOS High Sierra 10.13.6
Node: 8.11.3
Yarn: 1.7.0
npm: 5.6.0
Watchman: Not Found
Xcode: Xcode 10.1 Build version 10B61
Android Studio: 3.1 AI-173.4819257
Packages: (wanted => installed)
react: 16.4.2 => 16.4.2
react-native: 0.55.4 => 0.55.4
Description
We are using RN in brown field development mode.
A RN view is instantiated in activity at runtime using ReactInstance Manager and added to the layout. We are seeing odd issues where our android mobile app is crashing in production because of NPE in uimanager.
LOCATION:  com.facebook.react.uimanager.NativeViewHierarchyOptimizer.removeNodeFromParent()
MESSAGE
Attempt to invoke interface method 'com.facebook.react.uimanager.ReactShadowNode com.facebook.react.uimanager.ReactShadowNode.getNativeParent()' on a null object reference
LOCATION:
com.facebook.react.uimanager.UIImplementation.updateViewHierarchy()
MESSAGE
Attempt to invoke interface method 'int com.facebook.react.uimanager.ReactShadowNode.getReactTag()' on a null object reference
Reproducible Demo
We don't have a good repro step for this. We are not able to repro this locally.
Our APM tool is reporting this in production.

Hey @GurpreetAhluwalia, we typically do not track this type of issue here. As we do not have access to your application, contributors to React Native are not in a great position to debug the issue.
If you are able to investigate this a bit further, and are able to solidly repro, please feel free to open a new issue with details. We'd also prefer if you test this on the latest version as well. Thanks!


Chapter 9 Async Refresh Token

When I make more than one async request to the backend and token is expired I get an error 401 for each request, this causes the creation of a token per request in the table because a request follows the previous one.
There is some way to control this behavior?

Hello there,
thank you for purchasing the book.
The issue you are referring to has been fixed on January 2018 with a book update:
https://github.com/PacktPublishing/ASP.NET-Core-2-and-Angular-5/issues/8
https://github.com/PacktPublishing/ASP.NET-Core-2-and-Angular-5/issues/15
You can already find the updated source code on this GitHub repo. Please let me know if that's enough to fix your scenario as well.


re-enable lint unnecessary_const

Original PR #19342 reverted by #19423

@Hixie

If the performance regresses again, we will have to revert.

Feel free to revert on performance issue (I don't think I have access to the performance dashboard to see if this PR make performances regress)

Sorry, but I'm gonna revert this because Fuchsia has not yet fully migrated to Dart 2 (something I'm working on fixing).  I'll re-apply once it's ready.

@tvolkert is it good now to reland this? (re. https://github.com/flutter/plugins/pull/682#issuecomment-409449988)

Yep, this can re-land now.  Thanks!


Facing Issue "DB" not connected

What would you like to share?
I am facing this issue while installing all the reqiured dependencies. Steps I have followed to start the project locally:

npm ci
npm run dev

Does that mean I have to create mongodb cluster or something like that to connect with database because I have not connected with database.
Additional information
Screenshots:

Do you have mongo running? Have you looked at the docs about running the project locally https://linkfree.eddiehub.io/docs/environments/local-development

Discussion moved to Discord, so I will close this


Feature request: Make title specification possible via spec-File

Feature request:
Make the title (optional) part of the spec-file. Of course, it is possible to write a script, which takes the title from the filename, but not every useful attribute of a title is fine as filename. We like filenames to be short, but titles might sometimes be more verbose. If I work in an editor like Geany, I can configure it, so that it will produce a PNG when I hit the compile button, but the title has to be set manually, which makes it a less productive workflow.
The implementation might use an additional, optional key-value notation in the file, to keep all old spec files compatibel, or use an annotation in the comment section, to create a title.

@Stefan-Wagner  see https://atp-mipt.github.io/jsyntrax/#_titles


Might as well move  to outside of  in README.md

In Migration guide, I found <script /> are defined outside of <dom-module />. We might as well move <script /> to outside of <dom-module /> in README.md.

We are encouraging putting <script> inside the <dom-module> now for readability.  Either way works, and there may be a mix of examples using both syntax, so we'll try and clean that up.
@arthurevans could you do a sweep and make sure the docs are consistent in this respect?  Thanks.

When script is now again inside dom-module would it then be possible to get rid of the is: property where the dom-module name needs to be repeated. It seems that I frequently forget to change one of them when I copy and rename a component. But maybe it's just me.

This issue was moved to Polymer/docs#1124

Thank you for discussed and moved the issue.


Implement Support Traits

tl;dr

Grouped duplicate code into a collection of support traits (configs, URLs, auth)
Added support to more easily highlight a header / sidemenu menu item from the template data.

ts;wm
Changes:

Added Support namespace
Added AdminTrait to handle dev mode, admin config, and app config
Added BaseUrlTrait to handle site URLs and admin URLs
Added SecurityTrait to handle conditional auth checks
Added "current_item" implementation to SidemenuWidget and SidemenuGroupTrait
Added "header_menu_item", "side_menu_item", and "system_menu_item" to AdminTemplate

Coverage decreased (-5.4%) to 2.833% when pulling 5c404f14c71901f2071bc66733ce92711a7224ea on mcaskill-patch-16 into 187c3c10c2e4b8059b83a07e0a3adab7162fc664 on master.

Coverage decreased (-5.3%) to 2.815% when pulling f99679aac0e4e415d451a248a5d09b44db63e3fc on mcaskill-patch-16 into 1f0668ef2150853cf3d565705be0c02e1120c5bb on master.

Coverage decreased (-6.1%) to 2.563% when pulling 0e0e8471348fd7b173e6e88acd1cd89d3ae269c6 on mcaskill-patch-16 into a5cdeeb3d074fb0f6befc0ab4376bab2a8108c24 on master.

Coverage decreased (-7.0%) to 3.105% when pulling 0e5834a453007c031a603c4d4ff6ac9d120bee01 on mcaskill-patch-16 into 4ed0fdc11970711d76626fb99748e6eec749e1bc on master.

Coverage decreased (-7.0%) to 3.105% when pulling 0e5834a453007c031a603c4d4ff6ac9d120bee01 on mcaskill-patch-16 into 4ed0fdc11970711d76626fb99748e6eec749e1bc on master.


Moving FAQ  Purging dataset

Hi!
I am moving FAQ Purging dataset

Hi @Nurzhamalyrys! Thanks for the contributions. Could you add yourself to the contributors file? https://github.com/galaxyproject/training-material/blob/main/CONTRIBUTORS.yaml

Hi @Nurzhamalyrys! Thanks for the contributions. Could you add yourself to the contributors file? https://github.com/galaxyproject/training-material/blob/main/CONTRIBUTORS.yaml

Hi! I want to inform you that I added myself as a contributor in another pull request #3359

thank you @Nurzhamalyrys!!


fix: 5145 - bold style for unknown ingredients in KP

What

Applied an ad-hoc bold CSS style to unknown ingredients in KP
Example of html code for

a known ingredient: raisins secs
an unknown ingredient: raisins de sultane

Screenshots
Example on "raisins de sultane" for<PHONE_NUMBER>678.

before
after

Fixes bug(s)

Fixes: #5145

Impacted files

pubspec.lock: wtf
pubspec.yaml: added a needed dependency to html (already implicitly there anyway because of flutter_widget_from_html_core)
smooth_html_widget.dart: specific "bold" effect for css class name unknown_ingredient

Codecov Report
Attention: Patch coverage is 0% with 3 lines in your changes are missing coverage. Please review.

Project coverage is 9.51%. Comparing base (4d9c7fc) to head (d0dca2f).
Report is 66 commits behind head on develop.

Files
Patch %
Lines

...smooth_app/lib/generic_lib/smooth_html_widget.dart
0.00%
3 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           develop   #5149      +/-   ##
==========================================
- Coverage     9.54%   9.51%   -0.03%
==========================================
  Files          325     327       +2
  Lines        16411   16557     +146
==========================================
+ Hits          1567    1576       +9
- Misses       14844   14981     +137

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

That would be very useful!!! Will it work for dark mode as well?

That would be very useful!!! Will it work for dark mode as well?

@jusdekiwi It works in dark mode too:

amazing! Thank you so much!

Thank you @teolemon @jusdekiwi for your review and comments!

this could be mistaken for an allergen

Indeed, but "bold" was the initial requirement. Which other CSS style would you suggest?

worst case scenario, we change the name of the class, and it all disappears.

Indeed. The only solution would be for the server to provide the KP with an inline css, assuming that we're able to interpret it in flutter.


Using system font causes flash of Times New Roman

Xcode 14.1, iOS 16.1
When the TOMSMorphingLabel is set to use the system font, there is a flash of a serif font (looks like Times New Roman) during the animation. Workaround is setting a custom font.

Thank you for reporting this issue accompanied by a workaround! Unfortunately, I am not currently working actively with iOS and don't feel confident I'd be able to fix the issue myself. Could you look into this issue and try to resolve it? I'd happily accept a PR accordingly :slightly_smiling_face:


fix: reserved instance output

what

Fix the output

why

It does not need to be a join with a [*] this will cause error, just referring to it with the resource name will output everything as one object.
references
See the Terraform provider docs https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/rds_reserved_instance#attribute-reference

/terratest


Update Submit your research url

Only to be merged in after the pubpub pages are available under the reverse proxy on journal.


Mb/get csv

Created QueryWriteCSV() method that sends output from a database query directly into a CSV file on the local filesystem.
I think I put QueryWriteCSV() methods into every DBer interface, but not certain about that.
Also had some issues where it wanted to import from the original version rather than the forked version. I think I eliminated those, at least got to the point where it worked locally for me, but again, not certain.

Ready for re-review, all issues resolved to the best of my knowledge.


⚠ Bofrost.at has degraded performance

In fe285ae, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1727 ms

Resolved: Bofrost.at performance has improved in e52e4dd after 307 days, 14 hours, 4 minutes.


Segmentation fault on Intel CPU

I am testing clFFT on my laptop. I  have 2 OpenCl Device / Platforms ( intel and nvidia, more see below).
When I choose the Intel CPU Platform with clFFT as cl device (e.g. with clFFT-callback-client or my own software ) as device  I get the following segmentation fault:
$ clFFT-callback-client -p 1
Running FFT for length 1024 and batch size 1
Stack dump:
0.	Running pass 'Intel OpenCL Vectorizer' on module 'Program'.
1.	Running pass 'Intel OpenCL VectorizerCore' on function<EMAIL_ADDRESS>2.	Running pass 'PacketizeFunction' on function<EMAIL_ADDRESS>Segmentation fault (core dumped)
Can anyone verify this problem?
Regards,
Roland
------ List of devices
num platforms: 2
platform index: 0:
platform id: 0x151c2e0
platform vendor: Intel(R) Corporation
platform name: Intel(R) OpenCL
platform num devices: 1
device index: 0
device id: 0x151d3b8
device type: 2
global memory size: 15979MB
local memory size: 32KB
global cache size: 256KB
global cacheline size: 64
max memory alloc size: 3994MB
max compute units: 8
max workgroup size: 8192
max workitem dimensions: 3
max workitem sizes: 8192 8192 8192
device name: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
opencl c version: OpenCL C 1.2
opencl device version: OpenCL 1.2 (Build 92)
frequency MHz: 2400
platform index: 1:
platform id: 0x15285c0
platform vendor: NVIDIA Corporation
platform name: NVIDIA CUDA
platform num devices: 1
device index: 0
device id: 0x1528690
device type: 4
global memory size: 2047MB
local memory size: 48KB
global cache size: 32KB
global cacheline size: 128
max memory alloc size: 511MB
max compute units: 2
max workgroup size: 1024
max workitem dimensions: 3
max workitem sizes: 1024 1024 64
device name: GeForce GT 740M
opencl c version: OpenCL C 1.2
opencl device version: OpenCL 1.2 CUDA
frequency MHz: 1032

closing this old issue


Merges Master to Live. See commits for details.

Docs Build status updates of commit 6da05ba:
:clock10: Full build: the average full build time is 16 min(s) 55 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 6da05ba:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsOnlineLisSwitch.md
:white_check_mark:Succeeded
View (skype-ps)

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

Docs Build status updates of commit 5c1fa82:
:clock10: Full build: the average full build time is 16 min(s) 55 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 5c1fa82:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsOnlineLisSwitch.md
:white_check_mark:Succeeded
View (skype-ps)

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

Docs Build status updates of commit d9a5203:
:clock10: Full build: the average full build time is 16 min(s) 57 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit d9a5203:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsOnlineLisSwitch.md
:white_check_mark:Succeeded
View (skype-ps)

whiteboard/whiteboard-ps/whiteboard/whiteboard.md
:white_check_mark:Succeeded
View (whiteboard-ps)

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


Does not launch ios simulator automatically on the Xcode 9.1

Description

iOS simulator does not be launched automatically on the Xcode 9.1

Steps to Reproduce

node_modules/.bin/mocha e2e --opts e2e/mocha.opts --configuration YOUR_CONFIGULATION_NAME

Detox, Node, Device, Xcode and macOS Versions

Detox: 6.0.0
Node: 8.9.1
Device: iOS Simulator 11.0
Xcode: 9.1
macOS: 10.12.6

Solution

<EMAIL_ADDRESS>have a change where xcode >= 9 boots simulator by xcrun simctl boot ...  in the https://github.com/hayanmind/detox/blame/master/detox/src/devices/AppleSimUtils.js#L197.
But, I checked that xcrun simctl boot ... does not launch the ios simulator on the xcode 9.1. (I din't check that on the xcode 9.0)
I suggests the following code to fix this issue

async boot(udid) {
  const device = await this.findDeviceByUDID(udid);
  if (_.isEqual(device.state, 'Booted') || _.isEqual(device.state, 'Booting')) {
    return false;
  }
  await this.waitForDeviceState(udid, 'Shutdown');
- await this._bootDeviceByXcodeVersion(udid);
+ await this._bootDeviceMagically(udid);
  await this.waitForDeviceState(udid, 'Booted');
}

This is not a bug, it works as intended. With Xcode 9 simulator runtime, it is now possible to boot runtimes without opening the UI. The test still runs. If you want to see what's going, open the simulator app yourself, and when Detox boots the runtime, you will see a window open.


Review solid-auth package

Description
Review the current API and propose new API that will support common SOLID authentication operations.
Why
So that we can have a simplified interface to make it really easy for the flutter app developer to authenticate a user's WebID to a SOLID server.

In the Login page, https://github.com/anusii/podnotes/blob/e48573840617fd55ebaabbcd531d3b1129172876/lib/login/screen.dart#L180-L259


Add 1.20.5/6 compatibility

This plugin currently doesn't load in 1.20.5/6 versions of the game. Since Geyser's latest supported version at time of writing is 1.20.6, it would only make sense that this project should be updated to support it as well. Especially since some fixes included here are NOT included in the main Geyser project.

Looks like the pointed dripstone hack still works, but the bamboo one does not. A fix will happen.

Fixed with de9ade8.


PostgresConnectionSource should pass server hostname when connecting to database

PostgresNIO connection already can accept server hostname to perform TLS hostname verification: PostgresConnection+Connect.swift#L8
But PostgresKit doesn’t seem to use it: https://github.com/vapor/postgres-kit/blob/8f6d4fa648c5aa1d6ecdefea4d7fe25f97e599d0/Sources/PostgresKit/PostgresConnectionSource.swift#L18

Fixed in #182


Update snakeyaml to 1.32

Updates org.yaml:snakeyaml from 1.29 to 1.32.
Release Notes - Release Notes - Release Notes - Release Notes - Release Notes - Release Notes - Release Notes - Release Notes - Release Notes - Release Notes - Release Notes - Release Notes - Changelog - Changelog - Changelog - Changelog - Changelog - Changelog - Changelog - Changelog - Changelog - Changelog - Changelog - Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.yaml", artifactId = "snakeyaml" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.yaml", artifactId = "snakeyaml" }
}]

labels: library-update, commit-count:1

Superseded by #415.


I want to know how to put tag

Hi,
I want to know how to put tags.

Thank in advance.

@mrtortong  - you don't add tags in "Tags" navigation menu.
To add a tag:

go to document
select what document you want to tag (by clicking once)
actions menu (that one with lighting on it) select "tag"

You can see adding tags "in action" in this video.

@ciur Thanks for helping.


Create a C++ interface

Maybe be C++26 proof and implement this: https://en.cppreference.com/w/cpp/header/stacktrace


amtool silence query -q fail to return silence id

What did you do?
$ amtool silence add instance=test
d384fb5f-52de-4be2-8f69-d2d3f11dd0ad

$ amtool silence query -q instance=test
0xc000501df0

Note: instead of propoer silence id d384fb5f-52de-4be2-8f69-d2d3f11dd0ad there is some string 0xc000501df0
Query without -q parameter works fine:
# amtool silence query instance=test
ID                                    Matchers       Ends At                  Created By  Comment
d384fb5f-52de-4be2-8f69-d2d3f11dd0ad  instance=test  2019-06-09 20:40:43 UTC  user

What did you expect to see?
$ amtool silence query -q instance=test
d384fb5f-52de-4be2-8f69-d2d3f11dd0ad

What did you see instead? Under which circumstances?
$ amtool silence query -q instance=test
0xc000501df0

Environment

System information:
insert output of uname -srm here

Alertmanager version:
0.17.0

Prometheus version:
2.10.0

Thanks for reporting! It was a quick fix and has already been merged.


Minor improvements to Jupyter displays.

This PR fixes an issue with sorting basis state labels for more than 3 qubits, and formats resources estimates into tables:

I'm marking this as "Request Changes" for the DataTable think I'm suggesting. If you feel strongly about the current approach, stop by and we can discuss it.

Makes sense! I did strongly consider the DataTable approach before taking this, but the main trouble I ran into is that DataTable alone doesn't tell us that it's the particular data table returned by ResourcesEstimator. We could perhaps have the encoder check if it's a datatable with the right column headers, but then that would make writing the JsonConverter a bit harder. I also tried making a class that just wraps an IDictionary with extra metadata that could be used to format the table, but that wound up being a lot heavier-weight than what seemed reasonable. Happy to go back to DataTable, though, and look at how to make the JsonConverter work.

Why do you need to check if the DataTable is one generated by the ResourceEstimator... there is nothing special about the ResourcesEstimator data table. You can figure out the name of the columns from the .Columns field and then you can iterate on the Rows.
See how we do it on the ToTSV method if you need some inspiration.

Sorry for the delay. I came up with what I think is a fairly elegant solution: convert DataTable instances to instances of Table<DataRow> and use the existing table formatting logic for arbitrary data tables. This should now be good to go, hopefully.


finally clause with noImplicitReturns yields "Not all code paths return a value."

In Visual Studio Tools 2015 1.8.4, an error occurs on:
function theAnswerToLifeTheUniverseAndEverything(): number {
  try {
    return 42;
  } finally {
    console.log('Returned the answer to life the universe and everything.');
  }
}

When noImplicitReturns: true is set. Error is Not all code paths return a value..
A finally clause is not capable of returning anything anyway, this code should be correct.

Fix should be in tonight typescript@next


Data migration to fix submitted/rejected state

The Editions in this data migration have all been unpublished and then submitted (and in some cases subsequently rejected). This results in them 404-ing instead of redirecting in production currently and in them not republishing correctly when being migrated.
There is no valid transition from these states to draft but setting them to draft will cause all of the correct behaviour with no side effects so... data migration.

👍


Add pkg-config file

Install a pkg-config file to help library users find the library at compile time.

I'm adding a meson build system right now, so this should pop out automatically.

It turns out we were both working on Meson conversions in parallel.  We discussed this OOB and I'm going to post a PR soon.


React Native v0.36 peer dependency warning

Issue: https://github.com/kadirahq/react-storybook/issues/589

Fixed with #106

Released v2.1.5


Make a Contact Us section look like the Mockup

The current Contact Us section doesn't look like the mockup. I am taking this to make it look like the mockup.

The contact Us page has already been implemented , you can check Contact Us page
You can add this in the homepage though.

The contact Us page has already been implemented , you can check Contact Us page
You can add this in the homepage though.

I am working on the homepage contact us section. Is it okay?

The contact Us page has already been implemented , you can check Contact Us page
You can add this in the homepage though.

I am working on the homepage contact us section. Is it okay?
There are already issues raised by others for this
#158
#82

Check it here, https://i.ibb.co/JR48YKY/Screenshot-2020-10-02-191909.png. I am working on this part.

Check it here, https://i.ibb.co/JR48YKY/Screenshot-2020-10-02-191909.png. I am working on this part.

ok then.

Both of the pr's that are associated with this issue have conflicts present in them. Remember to run git pull upstream master before pushing your changes. @nemo0 and @chetas411 could you update the status of this issue?

Both of the pr's that are associated with this issue have conflicts present in them. Remember to run git pull upstream master before pushing your changes. @nemo0 and @chetas411 could you update the status of this issue?

I am done with the contact section. But each time I pull before pushing, I get issues. Resolving the issues results a broken site. Maybe I am doing something wrong. I'll try again.

Both of the pr's that are associated with this issue have conflicts present in them. Remember to run git pull upstream master before pushing your changes. @nemo0 and @chetas411 could you update the status of this issue?

I am done with the contact section. But each time I pull before pushing, I get issues. Resolving the issues results a broken site.

Try this it may help:
first add the original repo as a remote upstream in your local forked one:
git remote add upstream [upstream.git]
then,
git checkout master
git fetch --all
git pull --rebase upstream master
git push origin master

Yes, try what chetas mentioned @nemo0 and please finish out this issue before creating new ones.

Are one of you still working on this? Closing out the other issue.

Yeah , I guess @nemo0  is still working on it, if he faces some problem then I won't mind doing this one.

Thanks @chetas411 for the tip. Are you working on the master branch itself? Or creating a new branch?

@brittneypostma right now there are many issues related to visibility of many elements on the website and there are multiple contact us section and multiple css files have been changed , by the way you mentioned to come up with a new mock up for the site , I am waiting for it then would start the work for renovating the site .


Added AttachThreadInput to User32 namespace.

Added the DllImport and api signature to the User32 namespace.

Thanks for the PR !
Just a few formatting fixed and it's all good for me 😉