Update sparklinegroup-object-excel.md

SparklineGroups.Add does not work when Application.ReferenceStyle = xlR1C1 !!!

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

VBA/Excel-VBA/articles/sparklinegroup-object-excel.md
:white_check_mark:Succeeded

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.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

VBA/Excel-VBA/articles/sparklinegroup-object-excel.md
:white_check_mark:Succeeded

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.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

VBA/Excel-VBA/articles/sparklinegroup-object-excel.md
:white_check_mark:Succeeded

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.


Can't change scroll type legend to plain type legend

Version
4.2.1
Reproduction link
https://gallery.echartsjs.com/editor.html?c=xp9j1rfiOF&v=1
Steps to reproduce
见链接
What is expected?
分页图例切回普通图例时生效
What is actually happening?
分页图例切回普通图例时不生效

Hi, it's work on my computer, see the following picture.

So I don't understand what your problem is? Please provide a more detailed message.

例子最下方我写了个定时器来更改legend，但似乎并不生效

应该是个 bug

Fixed in https://github.com/apache/incubator-echarts/pulls?q=is%3Apr+is%3Aclosed


eeRead() - OSError: exception: access violation reading 0x....

Describe the bug
While reading the EEPROM of a FT232RQ through eeRead() an exception occurrs on some chips.
Traceback:
File "update_eeprom_config.py", line 34, in update_eeprom eeprom_data = device.eeRead()
File ".venv\\lib\\site-packages\\ftd2xx\\ftd2xx.py", line 609, in eeRead call_ft(\_ft.FT_EE_Read, self.handle, c.byref(progdata))
File ".venv\\lib\\site-packages\\ftd2xx\\ftd2xx.py", line 176, in call_ft status = function(\*args)
OSError: exception: access violation reading 0x0000028690BF93A5

To Reproduce
Before calling eeRead() the following commands are called:

ftd2xx.listDevices()
ftd2xx.open()
getDeviceInfo()

Expected behavior
return EEPROM data without exception
Desktop:

OS: Windows
OS Version: Windows 10
Python Version: 3.10.2
FTDI driver version: ftd2xx 1.3.8

Additional context

the reported address is different each time
about 50% of the FT232RQ chips we have, fail with this exception type, even when retrying a hundred times
however, the affected chips are read and writable with FTDI FT_Prog Utility Tool
once programmed with the FT_Prog tool, it is readable again through ftd2xx eeRead()

Any idea?

Sorry, no clue! I do not have the device. It could be an issue in the FTDI library, a connection issue, or how this library is accessing the data from the C side. You'll need to use a debugger to find the source of the access violation.
I can take a closer look once a root cause is known.

Thanks for the response.
Unfortunately I dont have the time or knodwledge to debug it.
The workaround we are using for now is writing the default EEPROM data through FT_Prog. After that everything works flawlessly.
You can close the issue


Jet fails when you have a private channel

I have a private channel with a node, and running jet monitor fails with this error:
getNodesInfo: 035590592cefc01a34c82db9fcedb35af1b9d103a2033eb3c0befd7c8ea9af99b6, error: Error: 5 NOT_FOUND: unable to find node
/home/ubuntu/lightning-jet/lnd-api/utils.js:345
      peerInfo[p.node.pub_key] = p;

i also suspect other jet processes are blocked due to this error but I'm not sure how to check and see. Most other calls are failing with a similar error too

I'll test/verify it with private channels.
To check the logs of jet processes, run jet status, it'll show you the location of log files.

tested with a private channel, could not repro.  new repro detail - the peer was offline.  checked on amboss.space, the node with this id does not exist, which is what likely caused the issue.
fix: make sure that getNodesInfo does not exit if one node errors out.


Rename thread link to comments link

The sharing menu provides the option to share either the Link (story) or Thread link (comments). The HN API calls comments kids, but the website calls them comments. I think calling them comments in the share menu clarifies any ambiguity about which item is which.

Calling it a 'thread' was a deliberate decision because technically the thread can contain more than just comments (like poll options, which the API calls 'parts'!), but I'll concede that the naming isn't the clearest. Would renaming the regular 'Link' to 'Story link' help as well?

Oops, sorry for missing your response. I think renaming "Link" to "Story link" would be a good fix too.


Error invalid_grant when doing doRequest

Hello,
I'm following the documentation but I cannot make any doRequest, all I get is the following :
In Authenticator.php line 44:

  Authentication request failed.

In Promise.php line 127:

  Client error: `POST https://test.salesforce.com/services/oauth2/token` resulted in a `400 Bad Request` response:
  {"error":"invalid_grant","error_description":"authentication failure"}

In RequestException.php line 113:

  Client error: `POST https://test.salesforce.com/services/oauth2/token` resulted in a `400 Bad Request` response:
  {"error":"invalid_grant","error_description":"authentication failure"}

Here is my code :
        $client = new GuzzleAdapter(new Client([
            'base_uri' => 'https://test.salesforce.com/',
        ]));

        $securityToken = 'XXXXXX';

        $credentials = new Credentials(
            'MY_KEY',
            'MY_SECRET',
            'password',
            [
                'username' => 'MY_ACCOUNT',
                'password' => 'MY_PASSWORD'.$securityToken,
            ]
        );

        $authenticator = new Authenticator(
            $client,
            [new PasswordGrantRegenerateStrategy()]
        );

        $tokenGenerator = new TokenGenerator(
            $credentials,
            $authenticator,
            new RequestTokenStorage()
        );

        $salesforceClient = new SalesforceClient($client, $tokenGenerator, 'v37.0');

        // print_r($salesforceClient);

        $result = $salesforceClient->doRequest(new Query('SELECT Name FROM Account'));

I do not understand where the error come from, can you help me?

Of course I kindly solved my own problem a few minutes after this post...
I switched the base_uri to "https://login.salesforce.com/" and everything works great

Good to hear that :) I guess the issue can be resolved.


Construct the PU location via rucio considering MSTransferor locks

Fixes #9894
Status
not-tested
Description
Previous logic in WMAgent for resolving the pileup location (the pileupconf.json construction) was simply relying on the current block location, without considering who locked the data.
This PR changes that functionality to something similar to what is done at WorkQueue level, such that we only use data that has been locked by MSTransferor.
I also have two somehow unrelated changes here:

FileList will contain a flat list of file names (instead of {"logical_file_name": })
FileList is no longer sorted. I couldn't see any reason to sort it. Besides, at SetupCMSSWPSet level we shuffle all those files..

Is it backward compatible (if not, which system it affects?)
no, between old and new agents. But this isn't a valid use case.
Related PRs
none
External dependencies / deployment changes
none

@belforte Stefano, I should have implemented it yesterday. But in case it's not too late, I have made 2 useful utilitarian functions in the Rucio wrapper module. Check this PR out if you want.

thanks Alan. Not too late. I will adopt https://github.com/dmwm/CRABServer/issues/6165

@khurtado FYI, this PR will slightly change the format of our pileupconf.json data structure (FileList will be a flat list, instead of a list of dicts).

Unit test tests most of this functionality, a real test is still required though, once we have more data in Rucio int database


The term "Image" under "Workflows" on main page is not clear

The current behavior or issue
The current web page uses the term Image when it actually refers to "RGB Image". The term is too broad
The steps taken to reproduce the behavior or issue, or specify a location where the steps were recorded
To reproduce - navigate to the landing page
Expected behavior
The term should be clarified to indicate "RBG Image"
Screenshots

Add other supporting information that may be useful
N/A
Completion criteria
This is done when the text reads "RGB Image"

Change: https://github.com/AgPipeline/Atlana/commit/aea6fec2d40292550d7163b532cabfb7d39fb4ca


Generate JSON Schema for response types

Currently, we do not generate JSON Schema in DocService for response types. We only generate them for request types. Creating schemas for response types can benefit our users. I.e. we are trying to access the type of response to display a table with columns as fields of the response type.
This will also help #4713 as well. That way we will be able to have a complete schemas definition.

Sounds like a good idea to me. Are you going to look into this as well, @Dogacel ?


Interview Preparation: Barclays

I would like to contribute the detailed process and tips required for cracking Barclays as a fresher.
Please assign me this under Hacktober Fest 2022.
Thank You!

Hi, I would like to contribute to this issue.


Ad Hoc - Collection-to-BPTL Receipt by Location

Please generate four Collection-to-BPTL Receipt metrics tables:
(1) frequency and percent distribution of days from research collection to BPTL receipt by collection location
(2) frequency and percent distribution of days from clinical collection to BPTL receipt by clinic location
(3) descriptive statistics for time (hrs) from research collection to BPTL receipt by collection location
(4) descriptive statistics for time (hrs) from clinical collection to BPTL receipt by clinic location
For (1) & (2), there should be six columns, "1 Day", "2 Days", "3 Days", "4 Days", ">4 Days", & "Total", and the tables should have row percent totals (see mock-up for reference)
For (3) & (4), assume the BPTL time received is 11:30am ET; BioBPTL_DateRec_v1r0 (926457119) only populates a date, not a timestamp. Add footnote to tables to note this assumption (see mock-up for reference)
All locations should be included in the code, but it is okay if all do not populate in the tables (they may not be live yet; "UCM Pop-Up" for example).
Requestor(s): Domonique
Table or Figure title:

Table 1. Research Biospecimen Collection to Receipt at BPTL (in Days) by Collection Location
Table 2. Clinical Biospecimen Collection to Receipt at BPTL (in Days) by Clinic Location
Table 3. Time (in Hours) from Research Biospecimen Collection to Receipt at BPTL by Collection Location
Table 4. Time (in Hours) from Clinical Biospecimen Collection to Receipt at BPTL by Clinic Location

Metrics to be updated or created: Create new metric tables
Variables needed (include variable name and Concept ID):

BioSpm_Setting_v1r0 (650516960) - Collection setting (research or clinical)
RcrtES_Site_v1r0 (827220437) - Sites
BioBPTL_DateRec_v1r0 (926457119) - BPTL date/time received
BioRec_CollectFinalTime_v1r0 (556788178) - Research collection time
BioClin_ClinBloodTmBL_v1r0 (822274939) OR BioClin_ClinicalUrnTmBL_v1r0 (139245758) - Clinical collection time (use whichever is earliest if both blood and urine date/time are populated)
BioSpm_Location_v1r0 (951355211) - Research Locations

HealthPartners - 951355211 = 4
Henry Ford - 951355211 = 5, 6, 7
Marshfield - 951355211 1, 2, 3, 12, 13, 14, 15, 16, 18
Sanford - 951355211 = 8, 17
University of Chicago - 951355211 = 9, 10, 11, 12, 19, 20

BioClin_SiteBlLocation_v1r0 (185243482) OR 7.  Use the blood location ID or the urine location ID to get the location; it can be assumed that they are the same if both are present. If one is not populated, the other can be used.)

HP - 185243482
NSC = 1
Elk River = 2
Chanhassen = 3
HFH - 185243482
Macomb =<PHONE_NUMBER> OR<PHONE_NUMBER>
West Bloomfield =<PHONE_NUMBER> OR<PHONE_NUMBER> OR<PHONE_NUMBER>
Wyandotte =<PHONE_NUMBER>
Fairlane (Dearborn) =<PHONE_NUMBER>
Plymouth =<PHONE_NUMBER>
Royal Oak =<PHONE_NUMBER>
Troy =<PHONE_NUMBER>
K1 HFH Main =<PHONE_NUMBER> OR<PHONE_NUMBER>
Sterling Heights =<PHONE_NUMBER>
Columbus =<PHONE_NUMBER>
Livonia =<PHONE_NUMBER>
KPHI - 185243482
Oahu Clinics = 22, 24, 28, 33, 34, 35, 38, 40, 55, 71
Non-Oahu Clinics = 23, 26, 27, 32, 37, 49, 56, 69

Specify numerator and denominator by variable name where applicable:
Table 1
No. of Days = [BioBPTL_DateRec_v1r0 (926457119)] - [BioRec_CollectFinalTime_v1r0 (556788178)]

Use populated date only to calculate the number of days; disregard timestamp

Table 2
No. of Days = [BioBPTL_DateRec_v1r0 (926457119)] - [BioClin_ClinBloodTmBL_v1r0 (822274939) OR BioClin_ClinicalUrnTmBL_v1r0 (139245758)]

Use populated date only to calculate the number of days; disregard timestamp

Table 3
Time in Hours = [BioBPTL_DateRec_v1r0 (926457119)] - [BioRec_CollectFinalTime_v1r0 (556788178)]

Assume the BPTL received timestamp is 11:30am ET

Table 4
Time in Hours = [BioBPTL_DateRec_v1r0 (926457119)] - [BioClin_ClinBloodTmBL_v1r0 (822274939) OR BioClin_ClinicalUrnTmBL_v1r0 (139245758)]

Assume the BPTL received timestamp is 11:30am ET

Mock-up table if applicable:
MOCK-UP_Collection-to-Received_Collection Location_Metrics.docx
Notes: N/A
Approved by:

Should 'BioBPTL_DateRec_v1r0 (926457119) - BPTL date/time received'  be the earliest of blood/urine/mouthwash for research and blood/urine for clinical? And should all collections be finalized?

@KELSEYDOWLING7 Yes, please use the earliest date available for BioBPTL_DateRec_v1r0.
For research, yes, the collections should be finalized (BioRec_CollectFinal_v1r0 - 410912345); they need to be finalized to populate a value for BioRec_CollectFinalTime_v1r0 (556788178) which is the most accurate collection date/time for research.
For clinical, yes, the collections should be finalized (BioRec_CollectFinal_v1r0 - 410912345), but use BioClin_ClinBloodTmBL_v1r0 (822274939) OR BioClin_ClinicalUrnTmBL_v1r0 (139245758) for the actual time calculation.

@HopkinsDC  Here's the updated report with those errors fixed. Unfortunately I still can't see my output report screen so let me know if anything still looks wonky
Ad-Hoc---Collection-to-BPTL-Receipt-by-Location.pdf

@KELSEYDOWLING7 This looks a lot better. Just a few edits:

Remove the second "Table #." in all of the titles

Table 2 and 4: the KP site and "location" for KPGA, KPNW, and KPCO aren't paired properly

Table 3 still has some negative values; can records with a negative time be excluded?

Table 3 and 4: give all the values one decimal place

Table 3 and 4: Add the following footnote - Note: BPTL receipt time is assumed to be 11:30am ET.

@HopkinsDC  I can finally see all my screens again so the location issue has been fixed! I also updated the decimals and added the footnote. But even after removing the urine and MW from the BioBPTL_DateRec_v1r0 list I'm still getting negative values for Table 3... Do you want me to remove any with hours under 0? If yes, do you want that done for table 1 also?
Ad-Hoc---Collection-to-BPTL-Receipt-by-Location.pdf

@KELSEYDOWLING7 Okay. Can you add the urine and MW back to Table 1 calculations (if they were removed)? I noticed a drop in some of the total counts, and it's important to have that be accurate in that table. Any changes we make to Table 3 shouldn't be applied to Table 1.
For Table 3, unfortunately, it is possible for a received date to be overridden from its original date due to some lingering data structure issues in the shipping dashboard. Can you run a check for any records when the collection date/time is after the date received?

@HopkinsDC  Ok I added MW and urine back into the research (table 1) and urine back into clinical (table 2).  For table 3 only do you want just all those with collection date/time after date received to be removed? There are  of them 34 of them

@KELSEYDOWLING7 This looks good from my first pass-through, so I'll share this version with the biospecimen team and follow up here if anything else is needed. Thank you!

@KELSEYDOWLING7 The biospecimen group reviewed these metrics, and Tables 1 and 2 are good as is.
For Tables 3 and 4, can you please add the "Perc. 90" and "Perc. 98" columns to both?

@KELSEYDOWLING7 Also, can you give me a list of the Collection IDs (or Connect IDs, whichever is easiest to get) of records that are above the 98th percentile for Tables 3 and 4?

@HopkinsDC  Sure thing.
Here's the report:
Ad-Hoc---Collection-to-BPTL-Receipt-by-Location.pdf
And here's the CIDs:
4662629387<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>
8936135492<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>
9784771819<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>
1913191978<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>
2250597955<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>
3161145870<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>
1336801547<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER> 1]<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>
2147112956<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>
6231438810<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>

@KELSEYDOWLING7 For Tables 3 and 4, most of the values are whole numbers, so it seems like only the date is being used in the calculations; can you confirm that autogenerated time is also being factored into the descriptive stats? The time of BPTL receipt can be assumed to be 11:30am (YYYY-MM-DDT11:30:00.000Z) for all received dates.
Also, for each of the sites, can you generate a scatterplot for hours from collection to BPTL receipt? These plots do not need to be by location. For Henry Ford and HealthPartners only, please stratify the data points by collection setting (research and clinical). A mock-up is included below as an example.

@HopkinsDC  Oh ok so I had made it that the calculated difference in hours for tables 3 and 4 were rounded to whole numbers, which is likely the problem. and then summary statistics (min, q1, median, ect.) has only one decimal place. I also had the time at 11:30 instead of 11:30:00.000Z
I've removed the rounding of the hours in the calculation portion and updated the timestamp, and now these are the CIDs above the 98th percentile
7604224276<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>
Here's the updated report with Tables 3 and 4 with that calculation update as well as these scatter plots.
Ad-Hoc---Collection-to-BPTL-Receipt-by-Location.pdf

@KELSEYDOWLING7 Please see my comments below:

Are the summary statistics being rounded as well? If yes, can you remove that too? The values in Tables 3 and 4 are the same as they were in the previous report.
The locations in Tables 3 and 4 aren't listed under the correct site; please correct this.
For all of the figures (which look good), please adjust the y-axis to have a max of 168 and number intervals of 24 (i.e., 24, 28, 72, etc.). It's okay if some data points are cut out; they are likely extreme cases that don't reflect an accurate collection-to-receipt time.
Can you reduce the CID list down to the CIDs above the 99th percentile?

@HopkinsDC  Yes, you'd requested that the summary statistics be rounded to one decimal place. I can remove it for this updated report, as well as rearrange the site locations to fit the correct site, and the y axis on all figures.
It looks like 12 (Rice Lake) is listed in the original request twice. Is that a Marshfield location or a UC location? And should UC-DAM be included in UC?
Connect IDs above the 99th percentile are the following (only in the research, not clinical):<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>
7253803204<PHONE_NUMBER>

@KELSEYDOWLING7 You can leave the descriptive stats at one decimal place; I think it's just odd for the bio group to see that most of them have a zero value for that decimal place, but I guess it does make sense since the sites mostly ship around the same time of day and we're using the same receipt time for all of them.
Rice Lake is a Marshfield Location. Sorry about the error in the original request; I've corrected it.
Yes, UC-DCAM should be included for UC (also corrected in the original request; I always forget that "0" can have a value too smh)
Let me know if I'm missing any other locations.

@HopkinsDC  No problem! Sorry the sites' orders keep moving. This should be correct now
Ad-Hoc---Collection-to-BPTL-Receipt-by-Location.pdf

Hi @KELSEYDOWLING7 ,
Michelle and I reviewed this report this morning and have a few other questions/comments.  Since Domonique is out until Jan 8th, Michelle and I will work with you on this (I'm also out Jan 2-4).

Tables 3 and 4 - please drop the "Max" column
Tables 3 and 4 - we are still a bit confused about the values. Are they in hours or in days?  For example, the min is 24 hours for most sites.  I know all samples have the same assumed receipt time of 11:30 am, but they should all have different collection times.  So if a sample was collected at 10:30 am Eastern time, its value would be 25 hours.  But if it was collected at 12:30 pm, its value would be 23 hours.  A sample in Detroit that was collected in the afternoon, say 3pm, should have a value of 20.5 hours. So it is odd that all sites have a min of either 24.0 or 48.0 hours.
for the figures it is the same question, the values should not all be on exactly the 24 or 48 hour line.
once we have the above worked out, we would like you to add this to the Biospecimen Weekly Report.  Please add these after Figure 15, before the deviations lists.

Let me know if you have any questions.
Thanks,
Stephanie

Hi @StephanieWeinstein  Ah, ok so I found what was happening. Somehow when I was coding it to calculate the difference in hours it was rounding to the nearest day, then converting THAT to hours. This now looks accurate.
Ad-Hoc---Collection-to-BPTL-Receipt-by-Location.pdf

Hi @KELSEYDOWLING7 , thank you!  It looks great now!  A lot of useful information.  Please go ahead and add it the the Biospecimen weekly reports.  Much appreciated!
Stephanie

@StephanieWeinstein  Can do! Do you want just the scatterplots? Or both the tables and the scatterplots?

@KELSEYDOWLING7 , everything please.  all the tables and all the scatter plots

@StephanieWeinstein   Ok can do. Is there a particular location in the report you'd like them? Or just at the end of the tables, before Figure 6?

Hi @KELSEYDOWLING7 , I am back in the office. Yes, before Figure 6 is good.

@StephanieWeinstein  Perfect, that'll be reflected in Monday's report

Hi @KELSEYDOWLING7 ,
In reviewing my notes from the biospecimen team meeting, for Tables 1 and 2 it was also requested that we show a total for each site (especially the sites that have multiple locations).  If you are not able to do that easily in Tables 1 and 2, then could you create two new tables that just show the total numbers for each site?  Sorry for this late request, it is ok if it does not make it into Monday's report!
Thanks,
Stephanie

@KELSEYDOWLING7 Hi Kelsey, per Stephanie's request above, please add a "Total" sub-row under each site for Tables 1 and 2, using the format used in #87's Table 1.2?

@StephanieWeinstein  I apologize for overlooking this! I had spoken to Domonique about having issues previously with those types of totals but forgot to reiterate that here. I was able to resolve it on Tables 1.1 and 1.2 but these are a bit different. I also think the total collections per day with a 100% would get confusing with the total with a 100% for each site location, so maybe separate tables are for the best. Please let me know how these looks.

Unfortunately I'm not able to get that on today's report, but I will be sure to do so on the next automation update on the 19th.

Hi Kelsey,
I am fine with separate tables.  KPNW is missing from Table 29a.
thank you!
Stephanie

@StephanieWeinstein  Thank you for catching that! I apologize

@KELSEYDOWLING7 , looks good, thanks!

@KELSEYDOWLING7 Hi Kelsey, thank you for working on this. Can you also add the percentages to the "Total" rows of Tables 28a and 29a?
Also, for figures 6 through 14, can you stratify the data points by day of the week collected (Monday, Tuesday, Wednesday, etc.) and add legends to each? The day of the week should be determined by the collection date (x-axis). I know HP and HFH are already stratified by collection setting (research or clinical), so is it possible to distinguish that stratification another way other than color, like different data marker types (e.g., circles and squares, X's and O's, etc.)?

@HopkinsDC  Here are 28a and 29a with the percentage totals.

I'll keep working on the Figures 6-14 updates

@HopkinsDC  For Figure 6 I think the shapes are a bit hard to distinguish when there's lots of data points grouped together.

I thinking maybe instead of shapes I could due a hue of colors? Or keep the shape distinction and also the hue of colors? So for example Figure 6 might have only the 'Blues' hues shown here, where each weekday is a different shade of blue. And then Figure 13 could have the 'Blues' hues for clinical collection weekdays and 'Reds' for research collection week days.

@KELSEYDOWLING7 Yes, that's what I meant in my initial request; use the colors for the days of the week and use the shapes to distinguish between research and clinical for Figures 8 and 9 since they have both collection settings. I'm sorry if I wasn't clear; I was thinking through as I was typing it out, so it's probably not the best explanation haha

@HopkinsDC  My mistake! I definitely misread. Please let me know how these look

Hi @KELSEYDOWLING7 Kelsey,
I think this will work, but the colors are t0o similar.  For example, Wed, Thurs, and Fri are all blue and Sun & Tues are both green.  can you get more variety in there?
Thanks!
Stephanie

@StephanieWeinstein  Of course! Figure 6-12 have been updated as well so that the days of the week have uniform colors accross all the figures

@KELSEYDOWLING7 The updated colors look good to me.
@StephanieWeinstein Does it look better to you?

yes, let's go with this and we can circle back if any other changes are needed.  Can you post the final figures here for now?
Thank you!

@StephanieWeinstein  Sure!

@KELSEYDOWLING7 Hi Kelsey, can you post the figures with the updated color scheme?

@HopkinsDC Oh I'm sorry! I was looking at the wrong output version.

@KELSEYDOWLING7 Thanks!

@KELSEYDOWLING7 Hi Kelsey, for the research setting time calculations only, can you please use BioCol_ColTime_v1r0 (678166505) instead of BioRec_CollectFinalTime_v1r0 (556788178) and repost the weekday stratified figures here?
Can you also apply this variable change to:

#110 (the needle-to-receipt time calculation in column D and the variable data in column I)
Tables 28a, 28b, & 30, and Figures 6, 7, 8, 13, & 14 in the weekly biospecimen report's automation code. (The figures in the report can remain as is (not stratified by weekday); just update the variable in the research time calculation)

@HopkinsDC

Hi Kelsey,
The figures look nice.  Once you have finalized everything with Domonique could you post the figures in a PDF somewhere so I can share them with the biospecimen team? We will probably incorporate them into the automated report but I'll confirm after we receive feedback.
Thanks,
Stephanie

@KELSEYDOWLING7 Per Stephanie's comment above, you can re-run the Ad-Hoc---Collection-to-BPTL-Receipt-by-Location PDF document and post it here so everything is in one place. Please use the figures that are stratified by weekday. Thank you!

@StephanieWeinstein  @HopkinsDC  Good morning, please see below
Ad-Hoc---Collection-to-BPTL-Receipt-by-Location.pdf

@StephanieWeinstein  @HopkinsDC  The automation for the Biospecimen Report will be updated tomorrow. Would we like the figures to be updated as shown above? Or left as is?

Thanks @KELSEYDOWLING7 , yes, the figures can be updated to the color coded versions with day of the week.

Tables and figures successfully updated in 1/22 biospecimen metrics report.


mysql数据库表字符串主键格式生成规则变动导致分片失败

Describe the bug
When using cdc for data synchronization，One of our business table，Because the generation rules of the string primary key id in the early stage and the id in the later stage are different，when cdc sharding，Using ObjectUtils.compare(chunkEnd, max) does not return the expected value correctly，cause sharding to fail，All data is centralized in one shard
pre id format ：logistics2018092521000003
post id format ：ORLOGIAP202111041130281601000001
Environment :

Flink version :  1.3.2
Flink CDC version: 2.1.0
Database and version: 5.7

To Reproduce
Steps to reproduce the behavior:

Thes test data :
min : logistics2018092521000003  max ORLOGIAP202111041130281601000001 chunkEnd: logistics2018111811000003

Could you use English for better communication? feel free to reopen once updated the description.

OK, I have edited the problem description


Include SparkPost Transport

Updating listings for transports to include SparkPost now that we have a public NPM for nodemailer-sparkpost-transport available.

Thanks!


added ui for summarization and backend code for it

Created UI for selecting OpenAI model, inputting API key, and summarization text, and displaying the result

can i know what was the problem with the code
i was able to run the project locally

Hi @Anash3,
Thanks for your contributions and for taking the time to create the UI for summarization and its backend code! It's awesome to see first-time contributors diving right in.
To address your query about the code, running the following commands should highlight any issues:
pip install ruff
cd sec-parser
ruff check --fix sec_parser/

🚀 These commands will check for errors and attempt to fix them automatically.
Looking forward to your response!
Best,
Elijas

Thank you @Elijas for the help
i have ran the given commands and solved all the issue
can you review the code and let me know the feedback

Hi @Anash3,
First of all, thank you for your valuable contributions and the effort you've put into enhancing sec-ai, especially as a first-time contributor. Your code and approach look promising.
However, our team is currently laser-focused on a different but critical component of the project: sec-parser. As a result, we are deferring new features and enhancements outside of this scope for the time being.
Please note that deferring the PR doesn't mean it won't be useful in the future; it might become relevant once our current objectives are met. For guidelines on how you can contribute to the sec-parser project, feel free to visit our Contribution Guidelines.
We appreciate your understanding and look forward to potentially revisiting your contributions when the time is right.
Feel free to reach out if you have any questions or concerns. Thank you for your understanding, and we look forward to your continued interest in the project.
Thanks,
Elijas

Hey, would you consider revisiting this solution to solve
https://github.com/alphanome-ai/sec-ai/issues/39

PR closed due to 1 month of inactivity. Please, consider reopening this PR with this Github Issue in mind: https://github.com/alphanome-ai/sec-ai/issues/39


Most tasks use "JDK Architecture" but the Java Tool Installer calls it "JDK Arch Type"

Can the Java Tool Installer use "JDK architecture" to match the other tasks (Ant, Gradle, Maven)?

Fixed in commit 955620487dd557b15642348da99bb62fefa3592c


Consider compatibility with Streams/Observables as per ES8 proposal

There's a standards proposal for ES8 (https://github.com/tc39/proposal-observable) which takes the bare bones of the observer/subscriber pattern from most.js, rxjs, xstream, zen-observable etc. to provide some compatibility in the same way Promises became standardised.
I don't think KO's observer/subscriber pattern is very far away from the suggested standard and it would be cool if KO observables could interop.
As an example of how these libraries work, I found this tutorial helpful :) https://gist.github.com/staltz/868e7e9bc2a7b8c1f754
As you can see, where the tutorial talks about streams of DOM events or subscribers updating the DOM, KO could slot in very neatly :)

Thanks !  This is was just reported on the tko repo too - can't get to link but will try later.
Great link 👍


Add support for Philips Hue Centura

Add support for Philips Hue Centura (5045148P7,<PHONE_NUMBER>01,<PHONE_NUMBER>01)

Hi marc, awesome job.
Few things I notice.
What is the difference between these 3 models as they are all called Hue Centura? Aren't they similar and just need to be aliased?
0.05 can't be correct for Hue lights. When you are unable to measure it could help to connect multiple to your powermeter and just divide the power reading by the amount of lights. The measure tool also provides functionality for that.
When you are still not able to measure we can guesstimate, I would say 0.25 is a good estimation for these kind of Hue lights.

Did you copy paste the csv files or did 3 measurement sessions? Because they look identical to me ;-).
Anyway, yes you can just add the aliases to the model.json and remove the other folders.

Thanks for the contribution.
Btw you don't have to modify supported models next time. This file is auto generated and will be overwritten after the PR is merged.

I tested 5045148P7 and the<PHONE_NUMBER>01, almost identical results. I removed the other 2.

Any idea when the next version will be released? I'm running measurements on some other philips hue lights now.


v.4.1.3 source code file contains 4.0.x branch's class file.

I'm not sure if this was intended or not, but the v.4.1.3 source code file contains class files from v.4.0.3.
The class mentioned above is shown below.
4.1.x branch - SmartCompositeMessageConverter
4.0.x branch - SmartCompositeMessageConverter
I'm guessing this is because the class in the 4.1.x branch was committed a month ago, and the 4.1.3. release was about 4 months ago, is that correct?  If that's correct, I'd like to make sure that the 4.1.4 release contains this commit.

I am not sure what are you asking. Can you please clarify? SmartCompositeMessageConverter is one of the core components of the framework, so it's in all branches

I wanted to say that the source code for the SmartCompositeConverter in the 4.1.3 version is not from the 4.1.x branch, but from 4.0.x. I also wanted to make sure that this was because a commit was made to the SmartCompositeConverter code in the 4.1.x branch after the 4.1.3 release, and I wondered if the 4.1.4 release would reflect that commit.

Yes

What I was confused about at first

Why does the 4.1.3 version source zip file have a class source code in the 4.0.x branch?

What I guessed

The commit added to the 4.1.x branch seems to have not been reflected because it was added after the date 4.1.3 was released.

What I wanted to ask

If so, will the class file with that commit be released in the next release?

It's pretty obvious that this will be in the next release, but I wanted to ask just to be sure.
Thanks. You can close this issue.

I am still confused about what you are asking and what source.zip you are referring to.
The fix has been added to 4.1.x - https://github.com/spring-cloud/spring-cloud-function/commit/6dee668e3ec20710460b0384a8b6afe53d078633 as well as 4.2.x https://github.com/spring-cloud/spring-cloud-function/commit/571783ffae5f24df9fbc0cc08a2e3838c97b58ae
So yes they will be included in the next release.
4.1.x will be released on November 12


Multilanguage support in Run

Description of the new feature / enhancement
For all people having multiple keyboard layouts there is problem when user is typing something in one language meaning to use different language. I suggest adding auto-transliteration (hope that what its called). All browsers do that and this is very convienent.
What i mean by that:
Sometimes i need to launch Word using Run. I start typing "word" but because layut is wrong in search field will appear цщкв, and i wont get any results:

Example in firefox:

In google:

Scenario when this would be used?
This will make using run faster as user will not have to worry what layout is currently on. And will be usefull for any non-english countries which there are planty of.
Supporting information
No response

Yes, please :) something like "Multilanguage text suggestions" in Windows 11 Settings would be super great :)


Update jackson-core, jackson-databind to 2.18.0

About this PR
📦 Updates

com.fasterxml.jackson.core:jackson-core
com.fasterxml.jackson.core:jackson-databind

from 2.17.2 to 2.18.0
Usage
✅ Please merge!
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 = "com.fasterxml.jackson.core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.fasterxml.jackson.core" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #463.


feat: Enable Fjord L1 data cost function

Follow-up to #8268, adding support for the Fjord hardfork to both the l1_tx_data_fee and l1_data_gas methods on RethL1BlockInfo.
Note: this currently depends on an unmerged revm commit, but will be cleaned up prior to merging. The associated revm changes can be tracked at https://github.com/bluealloy/revm/pull/1420 for now

Closing in favour of : https://github.com/paradigmxyz/reth/pull/8448


BetaUniformMixtureModel (BUM)

Based on the MixtureModel type from Distributions which gives many
essential functions, such as rand, pdf, cdf, moments and more for
free.
Introduces Distributions as a new dependency.

#10

Nice, I think it really is time to add a Distributions.jl dependency! Two questions/comments:

This definition of BetaUniformMixtureModel here is a bit more general than BUM as implemented in the π0 estimator. Do we want to make this more consistent? (either by restricting  BetaUniformMixtureModel or at least making the defaults match). Also, since Distributions.jl does not provide a fit method for mixture models afaik, do we want to provide a fit method again based on the existing implementation for the the π0 estimator?

I guess one of the main reasons this has been implemented is for the simulation benchmarks, right? If so, once we start benchmarking FDR/FWER controlling methods, we will need to also know from which component of the mixture a given p-value has been drawn (i.e. if it is from the null or the alternative), so the Distributions.jl rand will not work for that straight out of the box. Do you have any elegant ideas for that?

I guess one of the main reasons this has been implemented is for the simulation benchmarks, right? If so, once we start benchmarking FDR/FWER controlling methods, we will need to also know from which component of the mixture a given p-value has been drawn (i.e. if it is from the null or the alternative), so the Distributions.jl rand will not work for that straight out of the box. Do you have any elegant ideas for that?

This should be straightforward with a MixtureModel, as it stored the individual distributions as components. For this case, we can simply call rand on each component:
bum = BetaUniformMixtureModel(0.2)
rand(mm.components[1]) ## Beta
rand(mm.components[2]) ## Uniform

This definition of BetaUniformMixtureModel here is a bit more general than BUM as implemented in the π0 estimator. Do we want to make this more consistent? (either by restricting BetaUniformMixtureModel or at least making the defaults match).

Can you elaborate what you mean by that?

... Also, since Distributions.jl does not provide a fit method for mixture models afaik, do we want to provide a fit method again based on the existing implementation for the the π0 estimator?

A general fitting of mixture models could be possible with MixtureModels.jl. Integrating the model and a fit method may be interesting in general, but I don't consider this within the scope of this PR - I wanted to focus primarily on providing a framework for simulations.

Can you elaborate what you mean by that?

Just that when we fit the BUM pi0 estimator (fit(BUM(), pvalues)), we actually fit a BUM model but with alternative component Beta(α,1) where 0 < α < 1. So it is a special case, of the BetaUniformMixtureModel you defined here with β=1 and  0 < α < 1. Nevertheless, it still basically provides a specialized fit for "free", i.e. we could have fit(BetaUniformMixtureModel, pvalues) which basically just runs the BUM pi0 fit, extracts the null proportion and α and finally returns the distribution object!

Setting β=1 as the default in BetaUniformMixtureModel could be a first step to harmonise this, as the defaults are chosen fairly arbitrary anyway.

The fitting may be worth to look at. I feel it may help us to revisit this once we have more simulation models, as we can then better decide on a generalised, common interface.

Ok, cool, I think we can already merge this then! And as you said, we can figure out the best interface along the way.


warnings while using nbdev_clean

Hello,
I created a fresh repo with nbdev_new and when I run the nbdev_clean command, I get these user warnings. I'm not sure, why I get them. This was done on a fresh install of WSL2 on windows 10, setup with fastsetup.
with a python version: 3.10.6
nbdev version: 2.2.10
fastcore: 1.5.24
execnb: 0.1.3
/home/deven/mambaforge/lib/python3.10/site-packages/nbdev/clean.py:110: UserWarning: Failed to clean notebook
  warn(f'{warn_msg}')
/home/deven/mambaforge/lib/python3.10/site-packages/nbdev/clean.py:111: UserWarning: clean_ids
  warn(e)
/home/deven/mambaforge/lib/python3.10/site-packages/nbdev/clean.py:111: UserWarning: clean_ids
  warn(e)

@deven367 any chance you can share a minimal example that we can use to reproduce the issue?

Sure, here is the repo

@deven367 what if you try upgrading all the tools
echo fastcore ghapi execnb nbdev | xargs -n1 -I {} pip install -Uq git+https://github.com/fastai/{}.git

@deven367 Actually I believe the best way to solve this is to set
clean_ids = True in settings.ini

clean_ids = True in settings.ini for the time being, until we cut a new release

This fixes the issue I'm having. Thanks @hamelsmu

Great!


Clarification, easier to follow example

on the nonclustered index creation example change the table name from t1 to match the table in the previous example for clarification
CREATE INDEX zipCodeIndex ON t1 (zipCode);
to
CREATE INDEX zipCodeIndex ON myTable (zipCode);

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

ID: 4635ce5c-c6b4-0401-8aec-19f06923c4ef
Version Independent ID: 948d6df0-be68-b791-d7b3-aefea32dbd8d
Content: Indexing tables in SQL Data Warehouse
Content Source: articles/sql-data-warehouse/sql-data-warehouse-tables-index.md
Service: sql-data-warehouse
GitHub Login: @barbkess
Microsoft Alias: barbkess

@msc1504 Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@msc1504 Thanks for sending this issue.  I created a pull request to fix it.  It should show up later today or tomorrow.


Inconsistent String Literal Type Propagation

TypeScript Version:  2.3.0 RC
I'm observing some strange type behavior. Consider the following snippet.
type myType = "MY_TYPE";
const myType: myType = "MY_TYPE";

const foo = myType;
const bar = {
  baz: foo
};

The type of foo and baz are both "MY_TYPE" as expected.
However using this strEnum function as described here which, based on my understanding, should be doing the same thing as the above code, results in something different:
function strEnum<T extends string>(o: Array<T>): {[K in T]: K} {
  return o.reduce((res, key) => {
    res[key] = key;
    return res;
  }, Object.create(null));
}

const myTypeEnum = strEnum(["MY_TYPE"])

const foo = myTypeEnum.MY_TYPE;
const bar = {
  baz: foo
};

Here, foo is detected to be type "MY_TYPE", but baz is recognized as type string
Am I doing something wrong? Is this expected behavior?

This is working as intended. In the call strEnum(["MY_TYPE"]), the "MY_TYPE" literal has a widening literal type (see #11126) because it was never given an explicit type through a type annotation or a type assertion. You get the desired result if you explicitly assert a type:
const myTypeEnum = strEnum(["MY_TYPE" as "MY_TYPE"])

I'm left a bit surprised by the type widening here. In a project using react-redux, I'm having to declare types that I would expect the compiler to be able to infer.
In all of the following examples, I would expect the code to compile.  The widening between example 2 and 3 in particular threw me off.

Are all these situations truly as intended?

Consider a slight variant:
const DEFAULT_COLOR = 'RED';
const style = {
  background: DEFAULT_COLOR;
};
if (user.useNeatBackground) {
  // Error? Cannot convert "BLUE" to "RED" ?
  style.background = 'BLUE';
}

Without explicit intent, it's very tricky to infer literal types. You can quickly find yourself issuing errors on code that is extremely unsuspicious.

Thanks for the clarification! I'm going to close.

Hmm... that case certainly makes sense. I don't know if it's prohibitively expensive to do this, but could the compiler avoid widening the type within a certain scope if it can guarantee that an object is never mutated? Though even in that case
Another possible alternative here that might be nice would be to introduce a keyword in the type layer called literal.
const SUBMIT_COMMENT_SUCCEEDED: literal = 'SUBMIT_COMMENT_SUCCEEDED';

It expresses intent clearly, and avoids the triple repetition that we currently have to do:
const SUBMIT_COMMENT_SUCCEEDED: 'SUBMIT_COMMENT_SUCCEEDED' = 'SUBMIT_COMMENT_SUCCEEDED';

Would this be a proposal that might be considered? Or are there downsides to this?


Full Stack Implementation - PrimeFlix

Description: I am taking on the ambitious project of creating a full stack application called "PrimeFlix" that aims to clone both the frontend and backend of Amazon Prime Video. This comprehensive endeavor will allow me to enhance my web development skills across the entire stack.
PrimeFlix will replicate the visually appealing user interface, seamless user experience, and robust functionalities of Amazon Prime Video. It will include features such as user authentication and account management, video browsing and searching, video streaming with player controls, personalized recommendations, and a responsive layout for various devices.
For the frontend, I will utilize HTML, CSS, and JavaScript to design and implement the user interface, ensuring it closely resembles the original Amazon Prime Video. The frontend will focus on delivering an intuitive and immersive viewing experience for users.
On the backend, I will employ a suitable framework such as Node.js with Express.js to build the server-side logic and handle API requests. For data storage, I will integrate a database management system like MongoDB to store user information, video metadata, and other relevant data.
Screenshots: (Optional)
If applicable, I will include screenshots to showcase the progress and key aspects of the frontend during its development.
Additional Context: (Optional)
If there are any specific challenges, constraints, or requirements related to the frontend implementation, I will provide additional context to address them accordingly.

@U-DAY-333 go ahead.


Option for LiveReload

Using LiveReload is pretty easy, in conjunction with the "watch" Gruntfile task. Should we ask the user if they want to enable this?

So the grunt task would use something like grunt-inject to inject the live reload script into the app's index.html like this example?


pull request for e2e test at 12/11/2016 02:45:02

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

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.


Can sombody share the Pretrained features?

I used Chrome to download the features, but the speed is lower than 50kb/s and when downloading 50~100MB, it would interupt and when I redownload it will start from the begining.....
I feel helpless...

me too！

There is now an alternative download using google cloud storage that is very fast, but it is user pays - you need a google cloud storage account.


ci: remove not needed workflow

This PR removes not needed golang and nodejs workflows.
This change will optimize github actions runtime.
Thanks to this and this lines the file I just removed will not be created here by bot again.

/rtm


Two Hikvision DS-2CV2026G0-IDW - can't add second camera

Hello!
I love idea with such a simple solution - alarmserver - thank you!
I am using alarmserver from new docker image.
Unfortunately I have problem with "adding" second camera - it always fails.

WEBHOOK BUS INITIALIZED
STARTED HISILICON SERVER
HIK: Adding camera cam1: http://<IP_ADDRESS>/ISAPI/
HIK: USING DIGEST AUTH
HIK: Adding camera cam2: http://<IP_ADDRESS>/ISAPI/
HIK: BAD STATUS 401HIK: ERROR: Camera cam2 does not seem to support event streaming
            Is it a doorbell? Try adding rawTcp to its config!
HIK: Closed connection to camera cam2
HIK: USING DIGEST AUTH
HIK: BAD STATUS 401HIK: ERROR: Camera cam2 does not seem to support event streaming
            Is it a doorbell? Try adding rawTcp to its config!
HIK: Closed connection to camera cam2
STARTED HIKVISION SERVER

If I swap addresses:
hikvision:
  enabled: true
  cams:
    cam1:
      address: <IP_ADDRESS>
      https: false
      username: admin
      password: bothCamHaveSamePass
      rawTcp: false
    cam2:
      address: <IP_ADDRESS>
      https: false
      username: admin
      password: bothCamHaveSamePass
      rawTcp: false

Again problem with second camera:
Initializing Webhook bus...
WEBHOOK BUS INITIALIZED
STARTED HISILICON SERVER
HIK: Adding camera cam1: http://<IP_ADDRESS>/ISAPI/
HIK: USING DIGEST AUTH
HIK: Adding camera cam2: http://<IP_ADDRESS>/ISAPI/
HIK: BAD STATUS 401HIK: ERROR: Camera cam2 does not seem to support event streaming
            Is it a doorbell? Try adding rawTcp to its config!
HIK: Closed connection to camera cam2
HIK: USING DIGEST AUTH
HIK: BAD STATUS 401HIK: ERROR: Camera cam2 does not seem to support event streaming
            Is it a doorbell? Try adding rawTcp to its config!
HIK: Closed connection to camera cam2
STARTED HIKVISION SERVER

Configuration with single camera, alike <IP_ADDRESS> and <IP_ADDRESS>, works well.

Hey thank you for detailed bug report!
This indeed looks like a bug. I will have a look once I have some spare time.

Have you checked this?

My configuration is:

As I wrote: configuration with single camera works well.

If is set both cams to digest/basic it works :)


Update card design after istio chart is deployed

[ ] Match the styling of istio to be similar to what is implemented for monitoring

Text under Kiali should be
"Visualization of services within a service mesh and how they are connected"

rancher/rancher:master-head 6319706

Deploy Rancher
Navigate to dashboard view
Install v2 Istio
Navigate to Istio Overview
Kiali card is shown in the correct style


About vagrant

Have you checked:
https://github.com/mstorsjo/msvc-wine/
Is that one going to install msvc without vagrant?

I think that buildtools 2019 Is also available in winetricks:
https://github.com/Winetricks/winetricks/blob/master/src/winetricks


[REQUEST] Count of blocks (permission)

Hey guys! Does the plugin give the possibility to add permissions "block counts".
In griefprevention I added extra count of blocks (for claims) for some groups. I really need this possibility :)

Yes, https://github.com/bloodmc/GriefDefender/wiki/Options-(Meta)#global-options


Conversion Tool: Custom KeyBindings Stripped

Godot version
4.0
System information
MacOS 13.2.1/M2
Issue description
Any custom key bindings are stripped after running the conversion tool on a v3.5.1 project imported with v4.0.
Steps to reproduce
Run a v3.5.1 project with custom key bindings through the v4.0 conversions tool.
Minimal reproduction project
N/A

Do you mean the keyboard codes? For example arrow keys?

Yes, keyboard codes. I had set some keys like "A" and they are not "bound".

Then it should be fixed by #74237, if you mean the action map.

Thank you!

If you are able to compile the engine please confirm that this fixes it, otherwise you should attach a MRP to make this easier to test, this goes for most of your issues relating to the conversion.

MRP attached...
ConversionToolBugs.zip

Fixed by #74237.

Cool...


autoxtrabackup --partial traceback error

when mysql not installed or down, autoxtrabackup --partial gives traceback error:
lpiexam@lpiexam-VirtualBox:/$ autoxtrabackup --partial
Traceback (most recent call last):
  File "/usr/local/lib/python3.4/dist-packages/mysql_connector_python-2.0.3-                       py3.4.egg/mysql/connector/network.py", line 469, in open_connection
ConnectionRefusedError: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/bin/autoxtrabackup", line 9, in <module>
    load_entry_point('mysql-autoxtrabackup==1.0', 'console_scripts', 'autoxtrabackup')()
  File "/usr/local/lib/python3.4/dist-packages/click-4.0-py3.4.egg/click/core.py", line 664, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/click-4.0-py3.4.egg/click/core.py", line 644, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.4/dist-packages/click-4.0-py3.4.egg/click/core.py", line 837, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.4/dist-packages/click-4.0-py3.4.egg/click/core.py", line 464, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/mysql_autoxtrabackup-1.0-    py3.4.egg/autoxtrabackup.py", line 38, in all_procedure
  File "/usr/local/lib/python3.4/dist-packages/mysql_autoxtrabackup-1.0-py3.4.egg/partial_recovery/partial.py", line 32, in __init__
  File "/usr/local/lib/python3.4/dist-packages/mysql_connector_python-2.0.3-py3.4.egg/mysql/connector/__init__.py", line 162, in connect
  File "/usr/local/lib/python3.4/dist-packages/mysql_connector_python-2.0.3-py3.4.egg/mysql/connector/connection.py", line 129, in __init__
  File "/usr/local/lib/python3.4/dist-packages/mysql_connector_python-2.0.3-py3.4.egg/mysql/connector/connection.py", line 454, in connect
  File "/usr/local/lib/pyt6hon3.4/dist-packages/mysql_connector_python-2.0.3-py3.4.egg/mysql/connector/connection.py", line 417, in _open_connection
  File "/usr/local/lib/python3.4/dist-packages/mysql_connector_python-2.0.3-    py3.4.egg/mysql/connector/network.py", line 472, in open_connection
mysql.connector.errors.InterfaceError: 2003: Can't connect to MySQL server on 'localhost:3306'     (111 Connection refused)
Exception ignored in: <bound method PartialRecovery.__del__ of     <partial_recovery.partial.PartialRecovery object at 0x7f711aaae2b0>>
Traceback (most recent call last):
  File "/usr/local/lib/python3.4/dist-packages/mysql_autoxtrabackup-1.0-    py3.4.egg/partial_recovery/partial.py", line 37, in __del__
AttributeError: 'PartialRecovery' object has no attribute 'cnx'

Thank you for report.
For using --partial recovery option, MySQL server must be running.
i will fix it and add informative error message indicating this condition.

Fixed as:
Added connection try:except for connection state checking.