Add ADS Support

This PR adds ADS support to our test runner through the use of a new command line flag, and implements an ADS-only test.  Below is the design diary for this work (source), to help give context to the changes!

ADS Support Design Diary

Introduction

Background
Design

Specifying variants with cli flags
Tagging  the tests
reading flags and tags in our main
Changes to our test Steps
Uncertain changes

Questions

Introduction
This diary is a work-in-progress to document how we added ADS support to the xDS test harness. It sets up a background of the problem, our design of the work, and any lingering questions I have.

Background
The xDS transport protocol has four variants:

State of the World, non-aggregated
SOTW, aggregated
Incremental(or delta), non-aggregated
Incremental, aggregated

Each of the variants are handled by different RPC services/methods, and an xDS server can support any or all of them at the same time.
For example, for LDS, the various protocol variants are provided via the following RPC methods:

SotW, non aggregated: ListenerDiscoveryService.StreamListeners
SOTW, Aggregated : AggregatedDiscoveryService.StreamAggregatedResources
Incremental, non-agg: ListenerDiscoveryService.DeltaListeners
Incremental, Aggregated: AggregatedDiscoveryService.DeltaAggregatedResources

For SotW and incremental, the actual communication on the stream will be essentially the same for both aggregated and non-aggregated, regardless of which of the above RPC methods you use to create the stream.
For our tests, then, when a test is not variant specific, we should run the same test for each qualifying variant, by opening a stream with the correct RPC. For example, with a basic LDS test, our test runner should be able to run it against both ListenerDiscoveryService.StreamListeners and AggregatedDisocveryService.StreamAggregatedResources.
A target server may be configured for any subset of combinations from the four variants, and we should not lock in any required configuration for our tests. Instead, through something like command line flags, a person can tell the test runner which variants their implementation supports.

Design

Specifying variants with cli flags
A person should only start the runner once, and then the runner executes the test suite against the different set variants, by running the right stream against each of the supported, appropriate RPC methods (as outlined above).
A person can indicate which variants their target supports using the flag --variants. This flag expects a four character string made up of 1’s and 0’s. 1 represents support, 0 non-support. The variants are, right to left, sotw non-agg, sotw agg, incremental non-agg, incremental agg.
So if a person wanted to run the test suite against a server running only non-aggregated, but supporting sotw and incremental, they’d run:
./runner --variants 1010

If they are an edge case that only supports SoTW, non-aggregated and incremental, aggregated, then they’d run:
./runner --variants 1001

Tagging  the tests
For the tests themselves, some may be general enough to work across all variants, and some may only be appropriate for a particular combination. We can indicate this using tags added to the top of the test scenario. The tags are:

@sotw
@incremental
@aggregate
@separate

reading flags and tags in our main
In our main function, we parse the variant flag to build an array of boolean values. For each true value in the array, we run the test suite for that variant. This means the suite can run from 1-4 times.

Changes to our test Steps
The main flow for our tests is to set up state on the target server using the adapter, then initialize a service for the duration of the test. This service includes channels for requests and responses (and caches for both). Each test step in the scenario can use this service interface to pass along new requests or update state as nceeded.
We can use the same pattern for ADS, with some modifications:
Originally, the service interface included its typeURL value. When we needed to make a new request, we’d use the service’s assign typeURL. This doesn’t work for ADs, so now our new request functions pass the required typeURL, which is determined from the test step itself.
Originally, our subscribing step assumed you would be doing one subscription per scenario, and so built a service interface as part of the subscription step. This doesn’t work for ADS-Only tests where you are subscribing to multiple services across the same stream, and building a new service interface means clearing the existing caches. Now, the subscribing function checks if we already have a service initialized and, if so, uses its existing inferface. I think this change makes the function stronger overall, and may help me fix the unsubscribing issues.

Uncertain changes
I added a new step at the end of our ADS-only test, that reads: “And the server never responds more than necessary”.
This step is functionally identical to our current step “And the client ACKS to which the server does not respond”.
I duplicated the function due to an issue in the function’s logic. It closes down our response and request channels, so that any remaining messages can come through and we can look at the entire range of messages sent. Then, we count the # of responses and # of requests. Since ACK’ing is built into the client’s lifecycle, and it is acking every response it gets from the server, than in this final step there should be 1 more request than response. If not, the step fails.
This logic requires the step to be run at the end of the test. However, in the test cases doc, for the ADS-only test there are multiple “and the client sends an ack to which the server doesn’t respond”. If I tried to match the test case verbatim, we’d be closing the ADS stream too early. If I just put the existing step at the end, it seems as if we are only ACK’ing once.
Now, the ACK’ing is assumed to happen as part of the test, and we just check at the end that the server hasn’t sent more responses than it needed to. I worry this makes the test steps too opaque, and it may be highlighting that the existing steps are not as elegant as they could be. I am v. open for feedback or suggestions on if this needs to change, and how it could be improved.

Questions

Does the wording of the ADS test work for everyone?

does the test run as we’d expect?

Are there any objections/improvements to the –variants flag?

I've updated this PR based on feedback from our meeting.  The flag style of --variants 0011 has been removed. Instead, you can pass multiple flags for each variant you support, using the full name of the variant...e.g. `--variant "sotw non-aggregated"
I also added consistent wording for our tags, since godog can handle hyphens in their tags...so "@separate" became "@non-aggregated".


client: change loglevel of batchRecvLoop fails when receiving, needs to reconnect

With TiDB there are log messages that are somewhat noisy and often not really actionable and probably not really indicating a real problem.
batchRecvLoop fails when receiving, needs to reconnect
I would suggest to change the log level of these messages.

/cc @youjiali1995


RFP - Bluestacks

Could someone add Bluestacks?
Website:
https://www.bluestacks.com/
Lastest version:
https://www.bluestacks.com/download.html?utm_campaign=homepage-dl-button-en#download
Thanks in advance!

@daddydeadpool Which is it - a request for Bluestacks or Nox App Player?

bluestacks tried editing it sorry

Any progress on this?

I'll pick this package up

Package submitted, awaiting moderation

reviewed and complete https://community.chocolatey.org/packages/bluestacks/


Copilot recommendation is not gray

Seems like the recommendation of Copilot is always in pink color whereas it should be in gray color, see the difference between VSC and JetBrains, in this case IntelliJ IDEA.

VSC
IntelliJ IDEA

Oh, that's interesting!
I'll look into the highlights for this for the next release!

After downloading Copilot, it looks like the colour is inherited from Text Without Background in the editor schema. However, you can manually override the colour by ticking the box and picking a hex value.

I'd advise you do this as a current workaround while the next release will change the highlight of Text Without Background to be grey @kkrypt0nn

Working perfectly with that, thanks a lot! Looking forward at the update ^^


Chinese Simplified Translation

Hope to provide Chinese Simplified Translation
希望能够提供一下简体中文版本的winver，已经提交了新的resource.resw资源文件和新的package.appxmanifest资源文件，希望下个版本能够做出修改
We have submitted the new resource. Resw resource file and the new package.appxmanifest resource file. We hope to make changes in the next version

因为之前的早期发生了一点小失误，共有七次修改记录，最后修改的记录应该是第五个和第七个，标记的识别符应该是6102bf3和365de39
Because a little mistake happened in the early stage, there were seven times of record modification. The last modified record should be the fifth and seventh, and the identifier of the mark should be 6102BF3 and 365DE39

Merging this, thanks!


support offline network repository

Is your feature request related to a problem? Please describe.
At work, we are working in an offline network, that does not have direct internet connection.
I understand that one solution would be to install on other PC and copy locally via USB / etc.
However I would love to see some feature that allows to install some own repository, possible on some enterprise github, or gitlab, etc.
Proposed solution
In same manner that nuget allows to configure some local PC repsoitories, allow to configure vcpkg to have some "local repository" that assuming we have it, it would fetch all dependencies from there.
Describe alternatives you've considered
Only alternative is as seen in some old closed issue, dated from 2018, that suggest performing this on other online PC and copy it via USB.
Additional context
n/a

Yep, so we support export function, you can use that to export the installed packages.

Yep, so we support export function, you can use that to export the installed packages.

Hi @idanbis-rnd
The main issue is that vcpkg needs to download form the Internet the source code of a library before building it. But there are few options you can try:

A) Build in a computer with Internet access and export produced binaries.
B) Download sources for all ports and copy them to your offline machines.
C) Mirror all downloads required by vcpkg in an internal network.

Option A)
This method is the easier one, but it has some downsides. You need to have the same environment on all your computers (same triplet, compiler, and compiler versions for instance) and can be accomplished by using binary caching with a file share in your internal network or with a Nuget feed.
If you don't have an internal network then you can use the vcpkg export method.
Option B)
Use the existing --only-downloads on all the packages you need and then copy the sources that have been extracted to buildtrees/. The "benefit" of this method is that each machine will do their own build of the libraries (in the case that they have different environments).
Option C)
This would require you to figure out how to mirror and redirect all downloads made by vcpkg to your internal network. We plan to support source redirection as a feature of vcpkg but it is not currently implemented and we don't have any set timeline for it.
Extra option)
Create custom ports for the libraries you need that point to local resources (see overlay ports).

Hi @idanbis-rnd
The main issue is that vcpkg needs to download form the Internet the source code of a library before building it. But there are few options you can try:

A) Build in a computer with Internet access and export produced binaries.
B) Download sources for all ports and copy them to your offline machines.
C) Mirror all downloads required by vcpkg in an internal network.

Option A)
This method is the easier one, but it has some downsides. You need to have the same environment on all your computers (same triplet, compiler, and compiler versions for instance) and can be accomplished by using binary caching with a file share in your internal network or with a Nuget feed.
If you don't have an internal network then you can use the vcpkg export method.
Option B)
Use the existing --only-downloads on all the packages you need and then copy the sources that have been extracted to buildtrees/. The "benefit" of this method is that each machine will do their own build of the libraries (in the case that they have different environments).
Option C)
This would require you to figure out how to mirror and redirect all downloads made by vcpkg to your internal network. We plan to support source redirection as a feature of vcpkg but it is not currently implemented and we don't have any set timeline for it.
Extra option)
Create custom ports for the libraries you need that point to local resources (see overlay ports).

We hope your question was answered to your satisfaction; if it wasn't, you can reopen with more info.

Before downloading the packages, it will run always bootstrap.sh. There it downloads glibc. I found no way to stop this. I need to solve this before I can really try the options.
How do I run bootstrap in an offline machine?
Any news on implemting Option C?

bootstrap.sh just downloaded the binaries, you can directly downloaded them from your custom network directory instead.

Ok. The message with glibc suggests it would build it, but if you read the code closely, it does not :) Thanks.
Any news on implemting Option C?


Make it possible to say "cloud explorer load tree view items now"

Related to #3756

This was merged into main by Jason.

This was merged into main by Jason.


Update UserGuide to include Rating

Details

Add Command segment edited
Edit Command segment edited
Find Command segment edited
Updated Command Summary

Codecov Report

Merging #180 (7a145e4) into master (9cb9568) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #180   +/-   ##
=========================================
  Coverage     48.89%   48.89%
  Complexity      355      355
=========================================
  Files            87       87
  Lines          1632     1632
  Branches        186      186
=========================================
  Hits            798      798
  Misses          765      765
  Partials         69       69

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9cb9568...7a145e4. Read the comment docs.


read files

I can't read files
thanks to help me

What do you mean? Please elaborate.

I read it using linux os

I use Linux as well.
Which file? How are you trying to read?
Did you download the file and open it with a text editor. Or are you hitting the API to get the data and view it in browser?

using Linux to download the files then open it with a text editor in windows

using Linux to download the files then open it with a text editor in windows
I don't understand. Kindly respond with as much detail as possible. Otherwise you are wasting both of our time. Include screenshots, error logs etc.

using Linux to download the files then open it with a text editor in windows

You can download files by clicking here , the files will be in database/linebyline folder


Remove rz_meshgenerator parameter from ABTR workflow example

Trying to remove rz_meshgenerator parameter from Griffin, which is used in the ABTR example but no longer needed, and is causing VTB test failures. For more info, please see https://github.inl.gov/ncrc/griffin/pull/2115 and https://civet.inl.gov/job/2464417/

hi
you'll want to refer to an issue on the commit. you can use a new issue or the issue that was used for adding the model originally

Will submit an issue shortly

Refs #432

Job VTB Documentation on 86a93c2 wanted to post the following:
View the site here
This comment will be updated on new commits.

@GiudGiud PR should be good to go


Fix adder mapping

This PR modifies adders mapping for the qlf_k6n10 device.
The carry chain input is now longer directly connected to the first adder in chain CIN, but is generated using an intermediate adder.
This PR also reference ql_dsp function as part of the ql-qlf plugin in the main readme, and fix a typo qlf_k6n10 cells sim file.

@acomodi @mkurc-ant can you please merge this PR after review


Unlock pyomo version(s)

Pull Request Description
What issue does this change request address?
Continues #74
What are the significant changes in functionality due to this change request?
Continuing discussion from #124 allows upgrading pyomo from 5.7 as a dependency

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass.
[ ] 5. If significant functionality is added, there must be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large tes.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added, the the analytic documentation must be updated/added.
[ ] 9. If any test used as a basis for documentation examples have been changed, the associated documentation must be reviewed and assured the text matches the example.

This PR was ready to go until the ravenframework change. Need to wait for #140 before attempting to merge.

Job CentOS 8 on 98c71cd : invalidated by @PaulTalbot-INL
ravenframework fix, rerunning tests

@dgarrett622 This passed tests but is marked with "do not merge"; any opposition to removing that flag?

@PaulTalbot-INL no problems with removing the flag and merging. I tried removing the flag earlier, maybe it didn't stick.


Magit commits have an incorrect email address

They also seem to show up with an incorrect username on GitHub.

This blocks #4.

Can't reproduce.


upgrade translatable from dimsav to astrotomic

This PR upgrades from dimsav/laravel-translatable to astrotomic/laravel-translatable. This could be breaking because several older versions are dropped and the namespace changed.
 But yes, I know that several developers still depend on it.
So it's a big decision to make - for sure. At @spatie we go an even harder way and only support the latest version of laravel in every release - so atm only 5.8.
There's no particular reason like L5.5 isn't compatible (it should be) - it's just a simple decision how many versions to support and test with. Because we build every supported version in a PR.
https://github.com/Astrotomic/laravel-translatable/blob/c7d3eefe7bd8390fa325b555583a127134c7ce9b/.circleci/config.yml#L186-L193
I could offer you to release a v11.4 which adds support for L5.5 back in.
On the other hand the feature support for L5.5 ends end of the month (Aug 30th, 2019 - https://laravel-news.com/laravel-release-process). So it would be a security fix only LTS after the next Twill release.
I'm a fan of forcing moving forward. It makes the life as maintainer a lot easier and is most time not a big problem. Primary because most Laravel releases aren't this breaking that it would need days/weeks to do. And even if - there's Laravel Shift at your side to do it.
But I can't decide for you which support strategy you want to go with. So just let me know your decision and as long as it doesn't require special work it would be fine for me to add L5.5. The moment it requires a single character more than L5.6 I will move it out of supported versions.

@ifox but anyway I worry much much much much much much much more about #356 ❗
This would prevent me from using it in real/commercial projects - I have to really trust a new release and can't trust it if there's no automated testing with a high coverage which runs every commit/PR/merge and blocks a release if it fails.

Hey @Gummibeer
I have included your changes in this PR: Added support for Laravel 6, closing this for now.
Thank you for the contribution!


How to add a runtime?

I created a language pack for dotnet, using the dotnet-core paketo buildpack. When I try func create, I get: Error: language runtime not found.
How can I add a new runtime?
EDIT: I have to add a name to the main YAML:
schema_version: 0.0.1

# See below
name: myruntime
version: 0.0.5

Then, I can create the func using runtime myruntime/http (for example).

Hi @rabejens, I would love to run some dotnet functions with knative. Are you willing to share your language pack? I have some issues getting it running (I think it has to do with lifecycle, I can build the function with pack).


When serializing schema to Json string, only preserve necessary fields

With this feature, we can get rid of most of the unnecessary fields such as singleValueField for metrics and time etc.
Use gson to preserve the order of all fields.
This can greatly simplify the work of manually cleaning up the schema.

Codecov Report

Merging #2473 into master will increase coverage by 0.02%.
The diff coverage is 80.25%.

@@            Coverage Diff             @@
##           master    #2473      +/-   ##
==========================================
+ Coverage   69.32%   69.35%   +0.02%
==========================================
  Files         840      840
  Lines       39376    39407      +31
  Branches     5299     5311      +12
==========================================
+ Hits        27299    27329      +30
- Misses      10302    10306       +4
+ Partials     1775     1772       -3

Impacted Files
Coverage Δ

...om/linkedin/pinot/common/data/MetricFieldSpec.java
95.65% <100%> (+0.3%)
:arrow_up:

.../linkedin/pinot/common/data/DateTimeFieldSpec.java
96.87% <100%> (-3.13%)
:arrow_down:

.../com/linkedin/pinot/common/data/TimeFieldSpec.java
92.4% <100%> (-4.97%)
:arrow_down:

...in/java/com/linkedin/pinot/common/data/Schema.java
80.9% <100%> (+1.49%)
:arrow_up:

...linkedin/pinot/common/data/DimensionFieldSpec.java
100% <100%> (ø)
:arrow_up:

...java/com/linkedin/pinot/common/data/FieldSpec.java
76.92% <67.05%> (+6.87%)
:arrow_up:

...inkedin/pinot/common/data/TimeGranularitySpec.java
77.45% <80%> (+2.45%)
:arrow_up:

...a/manager/realtime/RealtimeSegmentDataManager.java
50% <0%> (-50%)
:arrow_down:

...e/operator/dociditerators/MVScanDocIdIterator.java
48.48% <0%> (-15.16%)
:arrow_down:

...mpl/dictionary/DoubleOffHeapMutableDictionary.java
58.18% <0%> (-14.55%)
:arrow_down:

... and 19 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8bbb5fe...123c58a. Read the comment docs.


Routine Load cause be to hang

Describe the bug
Routine Load cause be to hang
When I have a problem with my kafka data, be will die
To Reproduce
1.
create table live_heartbeat_test
(
id              varchar(255) comment 'id',
type            varchar(50) comment '消息类型',
progress        bigint default '0' comment '播放进度（ms）',
background      BOOLEAN comment '是否后台播放',
interval      bigint default '0' comment '和上次上报的间隔（ms）'
)
ENGINE = olap UNIQUE KEY(id)
DISTRIBUTED BY HASH(id) BUCKETS 10
PROPERTIES(
"replication_num" = "1",
"storage_type"="column"
);

CREATE ROUTINE LOAD test_db.live_heartbeat_test ON live_heartbeat_test
COLUMNS TERMINATED BY ","
PROPERTIES
(
"desired_concurrent_number"="3",
"max_batch_interval" = "20",
"max_batch_rows" = "300000",
"max_batch_size" = "209715200",
"strict_mode" = "false"
)
FROM KAFKA
(
"kafka_broker_list" = "localhost:9092",
"kafka_topic" = "course_doris_test_live_heartbeat_test",
"property.group.id" = "doris-test",
"property.client.id" = "doris-test"
);

kafka-producer

null,null,null,null,null
12null,null,null,null,null
232

Expected behavior
Report errors instead of be hangs
version
master

I think it's related to a field of type Boolean

create table live_heartbeat_test
(
id              varchar(255) comment 'id',
type            varchar(50) comment '消息类型',
progress        bigint default '0' comment '播放进度（ms）',
background      BOOLEAN comment '是否后台播放'
)
ENGINE = olap UNIQUE KEY(id)
DISTRIBUTED BY HASH(id) BUCKETS 10
PROPERTIES(
"replication_num" = "1",
"storage_type"="column"
);
kafka-producer

1342,record,123323,false

This will cause be to die，I think it's related to a field of type Boolean

@stalary
Doris don't support Boolean type in segment V1.
If this table is created in segment V2 format, Boolean is supported.


Investigate How Autoscaling Config Interacts With CAPI Node Count Config

Adding some discovery notes to this:
I'll verify this further, but so far in testing I think we need minCount <= count <= maxCount.
If you don't deploy it that way, you can enter a bad state where count+{amount autoscaler wants to scale up} < minCount, and cluster autoscaler refuses to scale up the machine deployment.

Done. Proceeding to #3449.


Wrong goal state in SawyerReachEnvV2

Hi, I am using metaworld.ML1 for studying meta reinforcement learning. I find that in the SawyerReachEnvV2 environment, when I run
obs, reward, done, info = env.step(a),
the info['goal'] is not the correct goal, and it seems fixed to [-0.1  0.8  0.2].
I read your source code and I find that env._state_goal returns the true goal, and I think you should add self.goal = self._state_goal in the step function of SawyerReachEnvV2. I am not sure if this should be done in other envs.
By the way, I think for goal-conditioned envs, the obs returned from step function should be like this: (which is the same with openai gym)
{
'observation': robot joint state, end_effector pos, obj_pos, vel……,
'deseired_goal': deseired_goal,
'achieved_goal': achieved_goal
}

And I am also quite interested in how you trained these benchmarks. Can you release the training code and some results for these environments?

Hello Chongkai,
Thank you for using MetaWorld. To be clear, ML1 is not a goal conditioned environment. Accessing the goal in ML1, ML10, and ML45 benchmarks is intentionally impossible, because the meta-learning algorithm must adapt to the hidden goal. Please do not publish results on ML1, ML10, or ML45 that use goal information, because it would be disingenuous. The goal is accessible as the last three dimensions of the MT10 and MT50 (and soon MT1: #165 ) benchmarks, but we also don't generally consider those to be goal conditioned, and thus do not returned the achieved_goal.
Unfortunately we're unable to release the training code originally used for these benchmarks, as it comes from multiple different sources, and uses a version of MetaWorld that has never been published. We have been able to reproduce the multi-task and meta-RL results using the Garage RL library, so please consider that library if you are interested. Results after the recent redesign (and for V2 environments) are not currently available, but providing them is a priority in our group.
Hopefully that answer your question, so I'm going to close this issue, but feel free to re-open if you have further questions.
Best, K.R.

Thanks! It helps me to better understand the mechanism of meta learning.


Not detecting all devices

Describe the bug
A clear and concise description of what the bug is.
The extension is not seeing all available devices but does see some.
More specifically i can't see my Sonos speakers.

ISSUE TYPE

Bug Report

Steps to reproduce

Go to the extension menu
Click on 'Listening on X'
See error

Expected behavior
A clear and concise description of what you expected to happen.
To see all available devices.

ACTUAL RESULTS

The device is not showing up on the list.
Also if trying to change the music while playing on the given missing device, it will change the music to one of the devices it can see.

Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows10
Plugin version: Music Time 1.8.6

Additional context
Add any other context about the problem here.

I am having the same issue. I see all my Amazon Echo Devices and one of my computers, but not the computer on which the vscode extension is running. Also, i try to connect to the local one by launching it, and it doesn't do anything. Sometimes, if spotify is running, it does connect to spotify, but doesn't list anything, nor will it let me connect to the local desktop player.


Cleanup raw arrays in LB

ChaNGa will be broken until https://github.com/N-BodyShop/changa/pull/98 is merged.


generatePermalink helper function forces permalink to use title attribute

Current logic would always use title attribute as permalink, even when custom permalink attribute is specified, which caused the issue opened up for IDRC website. An approach would be to add additional check if data has permalink attribute set, and if so, use that to generate permalink.
https://github.com/fluid-project/eleventy-plugin-fluid/blob/d4f559230522fad3b541486826d1b29a852f7a75/src/utils/generate-permalink.js#L44

Actually, when I read the block comment where this function is called, "Build a permalink using the title and language key if a custom permalink was not supplied.", this function is doing what it's suppose to do.


Upgrade to use Go 1.11

The current Travis build uses Go 1.10.4. Why don't we upgrade to use 1.11? I don't think any of the current Go code needs any modifications to run in 1.11, so should be painless.

Yes, I think it's fine to upgrade to Go 1.11.


Adds parent method to key class

Simple key.parent() method to mirror ndb a bit.  Easily implemented on the fly (it's not much code), so it's a convenience function only.

Sure thing, I was considering this earlier.  Do you feel it better fits as a property (I could add the @property decorator) or as a function?

Its not a big deal but I prefer a method since it returns a new Key() instance.

You got it! Changes inbound


Dependencies cleanup

On this PR:

Cleanup of devDependencies. Moved all of them to root package.json.
Unified React version on @kogito-tooling/core-api.
Fixed return of method on EnvelopeBusInnerMessageHandler.ts
Upgrade to most recent versions of TypeScript, Webpack and Node.

@Ginxo I'm adding a yarn.lock on this PR, so you can remove it from your PR.


NGM-LR output format - SAM/BAM tags

Hi Philipp,
What do the following tags means your output? I could not find documentation to tell me.

KB
SB
ID
QE
XE
XI
XR
AS
QS
XS
CV
SV

Thanks,
Melanie

Hi Melanie,
thanks for you question. Please see https://github.com/philres/ngmlr/issues/15
Let me know if you have any other questions.
Best,
Philipp


Compilation fails on 32-bit: target specific option mismatch

Description
Compilation fails on i586 — and possibly other 32 bit architectures — with the following error:
[  201s] In file included from ../Modules/Core/Common/include/itkMath.h:32,
[  201s]                  from ../Modules/Core/Common/include/itkVector.hxx:21,
[  201s]                  from ../Modules/Core/Common/include/itkVector.h:332,
[  201s]                  from ../Modules/Core/Common/include/itkPoint.h:23,
[  201s]                  from ../Modules/Core/Common/include/itkContinuousIndex.h:21,
[  201s]                  from ../Modules/Core/Common/include/itkImageRegion.h:34,
[  201s]                  from ../Modules/Core/Common/include/itkImageRegionSplitterBase.h:21,
[  201s]                  from ../Modules/Core/Common/include/itkImageRegionSplitterSlowDimension.h:21,
[  201s]                  from ../Modules/Core/Common/src/itkImageRegionSplitterSlowDimension.cxx:19:
[  201s] ../Modules/Core/Common/include/itkMathDetail.h: In function 'itk::int32_t itk::Math::Detail::RoundHalfIntegerToEven_32(double)':
[  201s] ../Modules/Core/Common/include/itkMathDetail.h:151:24: warning: SSE vector return without SSE enabled changes the ABI [-Wpsabi]
[  201s]   151 |   return _mm_cvtsd_si32(_mm_set_sd(x));
[  201s]       |          ~~~~~~~~~~~~~~^~~~~~~~~~~~~~~
[  201s] In file included from ../Modules/Core/Common/include/itkMathDetail.h:37,
[  201s]                  from ../Modules/Core/Common/include/itkMath.h:32,
[  201s]                  from ../Modules/Core/Common/include/itkVector.hxx:21,
[  201s]                  from ../Modules/Core/Common/include/itkVector.h:332,
[  201s]                  from ../Modules/Core/Common/include/itkPoint.h:23,
[  201s]                  from ../Modules/Core/Common/include/itkContinuousIndex.h:21,
[  201s]                  from ../Modules/Core/Common/include/itkImageRegion.h:34,
[  201s]                  from ../Modules/Core/Common/include/itkImageRegionSplitterBase.h:21,
[  201s]                  from ../Modules/Core/Common/include/itkImageRegionSplitterSlowDimension.h:21,
[  201s]                  from ../Modules/Core/Common/src/itkImageRegionSplitterSlowDimension.cxx:19:
[  201s] /usr/lib/gcc/i586-suse-linux/10/include/emmintrin.h:842:1: error: inlining failed in call to 'always_inline' '_mm_cvtsd_si32(double __vector(2))': target specific option mismatch
[  201s]   842 | _mm_cvtsd_si32 (__m128d __A)
[  201s]       | ^~~~~~~~~~~~~~
[  201s] In file included from ../Modules/Core/Common/include/itkMath.h:32,
[  201s]                  from ../Modules/Core/Common/include/itkVector.hxx:21,
[  201s]                  from ../Modules/Core/Common/include/itkVector.h:332,
[  202s]                  from ../Modules/Core/Common/include/itkPoint.h:23,
[  202s]                  from ../Modules/Core/Common/include/itkContinuousIndex.h:21,
[  202s]                  from ../Modules/Core/Common/include/itkImageRegion.h:34,
[  202s]                  from ../Modules/Core/Common/include/itkImageRegionSplitterBase.h:21,
[  202s]                  from ../Modules/Core/Common/include/itkImageRegionSplitterSlowDimension.h:21,
[  202s]                  from ../Modules/Core/Common/src/itkImageRegionSplitterSlowDimension.cxx:19:
[  202s] ../Modules/Core/Common/include/itkMathDetail.h:151:24: note: called from here
[  202s]   151 |   return _mm_cvtsd_si32(_mm_set_sd(x));
[  202s]       |          ~~~~~~~~~~~~~~^~~~~~~~~~~~~~~
[  202s] In file included from ../Modules/Core/Common/include/itkMathDetail.h:37,
[  202s]                  from ../Modules/Core/Common/include/itkMath.h:32,
[  202s]                  from ../Modules/Core/Common/include/itkVector.hxx:21,
[  202s]                  from ../Modules/Core/Common/include/itkVector.h:332,
[  202s]                  from ../Modules/Core/Common/include/itkPoint.h:23,
[  202s]                  from ../Modules/Core/Common/include/itkContinuousIndex.h:21,
[  202s]                  from ../Modules/Core/Common/include/itkImageRegion.h:34,
[  202s]                  from ../Modules/Core/Common/include/itkImageRegionSplitterBase.h:21,
[  202s]                  from ../Modules/Core/Common/include/itkImageRegionSplitterSlowDimension.h:21,
[  202s]                  from ../Modules/Core/Common/src/itkImageRegionSplitterSlowDimension.cxx:19:
[  202s] /usr/lib/gcc/i586-suse-linux/10/include/emmintrin.h:66:1: error: inlining failed in call to 'always_inline' '_mm_set_sd(double)': target specific option mismatch

and on and on. No issues when building on x86_64, however. Also wasn't an issue with the previous version 5.1.2. Full log attached: _log.zip
Reproducibility
Every time on i586.

Versions
ITK version 5.2.0.
Environment

CMake: 3.20.1
Python: 3.8.9
GCC 10.3.0
OS: openSUSE Tumbleweed (Linux)

This condition may need to be refined:
https://github.com/InsightSoftwareConsortium/ITK/blob/047fa6934ac32711d1d7b84fa6eb81c72db01960/Modules/Core/Common/src/itkConfigure.h.in#L186-L188

I had the same error using mingw32.
After commenting out the quoted define, everything compiled without erros!

This condition may need to be refined:
https://github.com/InsightSoftwareConsortium/ITK/blob/047fa6934ac32711d1d7b84fa6eb81c72db01960/Modules/Core/Common/src/itkConfigure.h.in#L186-L188


How to use the Org hierarchy API

https://docs.microsoft.com/en-us/graph/api/user-list-manager?view=graph-rest-1.0&tabs=http

Could you be a bit more specific about your question?  What kind of problem do you have, and what have you done so far?

@nauxliu Yes, it does.  You can use client secret authentication with this library.  Saying that, I've been doing so for an application.  Works fine. :smile:


feat(fs): add @ephemeras/fs package

Hi! I'm the autofix.ci troubleshooter bot.
It looks like you correctly set up a CI job that uses the autofix.ci GitHub Action, but the autofix.ci GitHub App has not been installed for this repository. This means that autofix.ci unfortunately does not have the permissions to fix this pull request. If you are the repository owner, please install the app and then restart the CI workflow! 😃


Unified Shared Memory

WIP; DO NOT MERGE
This PR addresses unified shared memory use across all kernels for everything: objects creation, shapeInfo caching, in-block reductions, and memory allocation for TAD
Final goal there: to use device memory ONLY for block-wise reductions (store block results) and to access task data. Everything else should be covered by shared memory, without any exceptions.

Also, this branch/PR addresses new, better kernel launch configuration.
New features planned there:

We differentiate kernel launches that involve TAD processing from linear launches, like scalar.
We tune kernel launch with respect to real shared memory used, not only static one.
We respect user-defined max grid/block sizes.
We respect highly possible asynchronous kernel launches, that would like to get some shared memory as well


Change status to basic ASCII

Cool. Please update the unit tests.

@ejoffe do you need to approve for checks to run?

@ejoffe can you fix the tests or implement this functionality? the workflow approval cycle takes too long


[Backport 2.x] Fix windows encoding issues (#2206)

Description
Adds spotbugs [1] to detect internalization before they are added to the codebase, also fixed several encoding bugs that impact windows users.
[1] https://spotbugs.readthedocs.io/en/stable/index.html
Closes https://github.com/opensearch-project/security/issues/2194
Signed-off-by: Peter Nied<EMAIL_ADDRESS>(cherry picked from commit a040b86a48eebcbe2791ba6371772fb9d386d6f2)
Check List

[ ] ~New functionality includes testing~
[ ] ~New functionality has been documented~
[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #2217 (e8cd5f3) into 2.x (920fdf0) will decrease coverage by 0.10%.
The diff coverage is 77.77%.

@@             Coverage Diff              @@
##                2.x    #2217      +/-   ##
============================================
- Coverage     61.06%   60.95%   -0.11%
+ Complexity     3242     3233       -9
============================================
  Files           257      257
  Lines         18089    18088       -1
  Branches       3225     3225
============================================
- Hits          11046    11026      -20
- Misses         5474     5491      +17
- Partials       1569     1571       +2

Impacted Files
Coverage Δ

...dlic/auth/http/saml/AuthTokenProcessorHandler.java
47.28% <0.00%> (ø)

...a/org/opensearch/security/tools/SecurityAdmin.java
36.00% <0.00%> (ø)

...earch/security/auditlog/impl/AbstractAuditLog.java
73.75% <100.00%> (ø)

...ty/configuration/ConfigurationLoaderSecurity7.java
66.39% <100.00%> (ø)

...ensearch/security/ssl/DefaultSecurityKeyStore.java
67.63% <100.00%> (ø)

.../org/opensearch/security/support/ConfigHelper.java
86.00% <100.00%> (ø)

...t/keybyoidc/AuthenticatorUnavailableException.java
0.00% <0.00%> (-20.00%)
:arrow_down:

.../auth/http/jwt/keybyoidc/SelfRefreshingKeySet.java
59.85% <0.00%> (-3.53%)
:arrow_down:

...ic/auth/http/jwt/AbstractHTTPJwtAuthenticator.java
55.81% <0.00%> (-3.49%)
:arrow_down:

...security/auditlog/sink/ExternalOpenSearchSink.java
59.25% <0.00%> (-2.47%)
:arrow_down:

... and 4 more

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


add WriteAuthorizer interface

Required for all non-trivial PRs

[x] Rebased/mergable
[ ] Tests pass

@e-dard @corylanou

Small nit but LGTM 👍


[PE-D] list_attendance minor feature flaw

list_attendance also only provides the student ID without the name of the student, might be useful to have included name for TA.

Labels: type.FeatureFlaw severity.Low
original: rcjj98/ped#6

Will change this to use student name


Can't figure out how to use my existing LM Studio installation: Cannot read properties of undefined (reading 'content'), brain disconnected.

Since I've already got Llama 3 set up locally in LM Studio, I figured I would be able to use that program since it allows you to host a local server to "mimic OpenAI endpoints".
Anyway, I've gotten most of the way there. Since it's running locally, I shouldn't need an API key and the keys.json isn't touched.
In andy.json and andy_npc.json I changed "model" to "llama3".
I also edited the Local class of src/models/local.js to use the endpoints from LM Studio, and that looks like this:
export class Local {
    constructor(model_name, url) {
        this.model_name = model_name;
        this.url = url || 'http://localhost:1234';
        this.chat_endpoint = '/v1/chat';
        this.embedding_endpoint = '/v1/embeddings';

This almost works, and the bot joins my server, but upon running "node main.js" I get a TypeError:
keys.json not found. Defaulting to environment variables.
Using chat settings: { model: 'llama3', api: 'ollama' }
Using embedding settings: { api: 'none' }
Unknown embedding:  none . Using word overlap.
Logging in...
Mineflayer detected that you are using a deprecated event (physicTick)! Please use this event (physicsTick) instead.
andy spawned.
selected examples:
brug: Remember that your base is here.
user43: Set a goal to survive on your own forever.
Awaiting local response... (model: llama3)
TypeError: Cannot read properties of undefined (reading 'content')
    at Local.sendRequest (file:///Z:/llm/mindcraft-main/src/models/local.js:20:37)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Prompter.promptConvo (file:///Z:/llm/mindcraft-main/src/agent/prompter.js:165:16)
    at async Agent.handleMessage (file:///Z:/llm/mindcraft-main/src/agent/agent.js:139:23)
Purely conversational response: My brain disconnected, try again.

Is there any way around this or will I be forced to try and use Ollama? I'm not entirely keen on trying to set up a whole new program and potentially having to go through downloading Llama 3 again when I've already got it working via LM Studio and should just be able to use the endpoints.

I've pushed a little further with this to see if I can find some sort of workaround. The first thing I tried was using OpenAI but with "lm-studio" as the OPENAI_API_KEY. As probably expected, this doesn't work:
Z:\llm\mindcraft-take2\mindcraft-main>node main.js
Using chat settings: { model: 'gpt-4o-mini', api: 'openai' }
Using embedding settings: { api: 'openai' }
file:///Z:/llm/mindcraft-take2/mindcraft-main/node_modules/openai/error.mjs:44
            return new AuthenticationError(status, error, message, headers);
                   ^

AuthenticationError: 401 Incorrect API key provided: lm-studio. You can find your API key at https://platform.openai.com/account/api-keys.
    at APIError.generate (file:///Z:/llm/mindcraft-take2/mindcraft-main/node_modules/openai/error.mjs:44:20)
    at OpenAI.makeStatusError (file:///Z:/llm/mindcraft-take2/mindcraft-main/node_modules/openai/core.mjs:268:25)
    at OpenAI.makeRequest (file:///Z:/llm/mindcraft-take2/mindcraft-main/node_modules/openai/core.mjs:311:30)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async GPT.embed (file:///Z:/llm/mindcraft-take2/mindcraft-main/src/models/gpt.js:51:27)
    at async file:///Z:/llm/mindcraft-take2/mindcraft-main/src/utils/examples.js:37:46
    at async Promise.all (index 2)
    at async Examples.load (file:///Z:/llm/mindcraft-take2/mindcraft-main/src/utils/examples.js:39:13)
    at async Promise.all (index 0)
    at async Prompter.initExamples (file:///Z:/llm/mindcraft-take2/mindcraft-main/src/agent/prompter.js:101:9) {
  status: 401,
  headers: {
    'alt-svc': 'h3=":443"; ma=86400',
    'cf-cache-status': 'DYNAMIC',
    'cf-ray': '8c1f29b8bf3217c8-MEL',
    connection: 'keep-alive',
    'content-length': '259',
    'content-type': 'application/json; charset=utf-8',
    date: 'Thu, 12 Sep 2024 10:20:06 GMT',
    server: 'cloudflare',
    'set-cookie': '__cf_bm=IYwkdOd5_kOQAIutDc_9vDTJcOJPT7OvOPlYIlStgMI-1726136406-<IP_ADDRESS>-TJAMiZQm9kE0NolwvBcxfBZDFq9ZutT3618s8IqFyFN4ejZnKguVvjj9P1kFouwsKcrcUIUk6jgE4cUF2.gaEg; path=/; expires=Thu, 12-Sep-24 10:50:06 GMT; domain=.api.openai.com; HttpOnly; Secure; SameSite=None, _cfuvid=xTnr_5ZUUb01XytTNaCK6JfjRIkDfpzrBsTXh9hOYag-1726136406097-<IP_ADDRESS>-604800000; path=/; domain=.api.openai.com; HttpOnly; Secure; SameSite=None',
    'strict-transport-security': 'max-age=15552000; includeSubDomains; preload',
    vary: 'Origin',
    'x-content-type-options': 'nosniff',
    'x-request-id': 'req_a987d20faece35cecfc9c47219810395'
  },
  request_id: 'req_a987d20faece35cecfc9c47219810395',
  error: {
    message: 'Incorrect API key provided: lm-studio. You can find your API key at https://platform.openai.com/account/api-keys.',
    type: 'invalid_request_error',
    param: null,
    code: 'invalid_api_key'
  },
  code: 'invalid_api_key',
  param: null,
  type: 'invalid_request_error'
}

Node.js v20.17.0
Agent process exited with code 1 and signal null
Agent process exited too quickly. Killing entire process. Goodbye.

So back to the drawing board, I decided to open up andy.json and try "llama3" as the model. But now I'm getting hit with a different error:
Z:\llm\mindcraft-take2\mindcraft-main>node main.js
Using chat settings: { model: 'llama3', api: 'ollama' }
Using embedding settings: { api: 'none' }
Unknown embedding:  none . Using word overlap.
Logging in...
Mineflayer detected that you are using a deprecated event (physicTick)! Please use this event (physicsTick) instead.
andy spawned.
selected examples:
brug: Remember that your base is here.
user43: Set a goal to survive on your own forever.
Awaiting local response... (model: llama3)
Failed to send Ollama request.
Error: Ollama Status: 400
    at Local.send (file:///Z:/llm/mindcraft-take2/mindcraft-main/src/models/local.js:52:23)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Local.sendRequest (file:///Z:/llm/mindcraft-take2/mindcraft-main/src/models/local.js:18:19)
    at async Prompter.promptConvo (file:///Z:/llm/mindcraft-take2/mindcraft-main/src/agent/prompter.js:165:16)
    at async Agent.handleMessage (file:///Z:/llm/mindcraft-take2/mindcraft-main/src/agent/agent.js:139:23)
file:///Z:/llm/mindcraft-take2/mindcraft-main/src/agent/commands/index.js:19
    const commandMatch = message.match(commandRegex);
                                 ^

TypeError: Cannot read properties of null (reading 'match')
    at containsCommand (file:///Z:/llm/mindcraft-take2/mindcraft-main/src/agent/commands/index.js:19:34)
    at Agent.handleMessage (file:///Z:/llm/mindcraft-take2/mindcraft-main/src/agent/agent.js:141:32)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Node.js v20.17.0
Agent process exited with code 1 and signal null
Agent process exited too quickly. Killing entire process. Goodbye.

Interestingly enough, it seems like LM Studio itself receives the request, but doesn't work because it believes the "messages" field is empty:
[2024-09-12 20:40:34.168] [INFO] Received POST request to /v1/chat/completions with body: {}
[2024-09-12 20:40:34.169] [ERROR] 'messages' field is required
Unfortunately I can't really figure out where to go next. Seems like it's actually communicating with LM Studio but can't work due to the message.match() method somehow returning an empty message field.

Primera vez que utilizo esto, la verdad ChatGPT hizo casi todo el trabajo, pero avance es avance y creo que debo compartirlo, modifiqué varios archivos (agent-process, init-agent, agent, ANIA, main, settings) y logré que funcionara con lm-studio con algunos problemas, el bot responde a las solicitudes, pero no es capaz de recordar. Igualmente debido a problemas de hardware no pude ejecutar modelos grandes, pero los que probé (Gemma o Llama) funcionaban.

las imagenes no muestran las falencias de memoria, favor si alguien le puede echar un ojo al codigo, abriría muchas puertas
TST.zip
Saludos a quien me lea (:


Fill in missing dates

@XeniaMonika, I realized that there were some projects for which we didn't record a start date. I think that's a datum that we should always include, even if it requires a judgment call or a bit of guesswork. So I've done my best to fill in this field in cases where it was empty. Our schema validation will also mandate this from now on. Let me know if you have any thoughts—or if you can come up with better estimates of the start dates of some projects. Thanks as always.

Ok. I used to leave this field in case there was no Info provided, bsc I wanted to avoid biased information. But maybe for our goals an approximate is better than nothing when based on some solid info provided by the project. I´m also asking myself what we want to do with this date except for the timeline. It could be important if we want to investigate the availability of the research data after a given project expires.  If we want to include it in our future publication, we should mention that some of the starting dates are approximated.

We could also need it for a general investigation of the field, e.g. for how many years such projects receive funding, how shorter or longer projects deal with their long-term data availability, what is their general life cycle, how the field developed in the recent years, and stuff like that.  So in this case is it better to have an estimate that could be wrong, or nothing at all? The second option could also mean that we won't have enough data. And one question, how did you come up with these dates?

And maybe we could use the comment section to mark that the date is estimated

Yeah, we can be open about the fact that some start dates are approximate. Using the comment field to note this is also a good idea. Just to preserve my thought process, let me list here the projects for which I added or changed start dates in this PR, and in each case, the basis on which I did so.

A Digital Typology of Arabic Documents: This falls under the umbrella of the Arabic Papyrology Database, which I'm fairly confident was launched in 2003. So I gave the start date of the parent project to this child project. That's definitely not correct—the Digital Typology is described as the "latest phase" of the APD—but it's the best I could come up with. To be marked as approximate

al-Ṯurayyā Project: The website's description of who has worked on the project, and when, gives the clear impression that 2013 was the first year. No need to mark as approximate

Arabic and Latin Corpus: I found a relevant YouTube video whose description indicates a start year of 2016. No need to mark as approximate

Arabic Papyrology Database: Start date revised to 2003 based on information on their website. I'm not sure why this was previously recorded as 2004. No need to mark as approximate

Study of Averroes's Long Commentary on the Physics in Hebrew and Latin Transmission: The parent project, Averroes Editions, is known to have started in 2016 with a funding period of twenty-five years. And one of the postdocs who worked on this subproject, Grégory Clesse, was there from 2016 to 2019. No need to mark as approximate

Critical Edition of the Fragmentary Latin Translation of Averroes's Commentary on De Partibus Animalium and De Generatione Animalium: Basically the same situation here. Clesse is listed as having worked on this edition, and he joined the Averroes Editions project in its first year. No need to mark as approximate

Critical Edition of Ibn Bāğğa's Commentary on Aristotle's De generatione et corruptione: This edition was actually published in 2021. So I think we can use that as the end year, and 2016 as the start year (inherited from Averroes Editions). No need to mark as approximate

Critical Edition of Ibn Bāǧǧa's Commentary on Aristotle's Physics: The then-postdoc who worked on this edition, Farah Cherif-Zahar, notes that she was with the project from October 2016 to August 2017. I opted to leave the end date of the edition blank, since I don't know whether it's complete. No need to mark as approximate

eScriptorium: This project has a German Wikipedia entry that lists an "Erscheinungsjahr" of 2018. So I went with that. No need to mark as approximate

Historical Middle East Data Alliance: The earliest activity in this GitHub organization (to which I belong) was in 2020. I'm just about certain that was when Nathan Gibson set it up. No need to mark as approximate

HMML: Both their website and Wikipedia list the year of founding as 1965. Does this not work for our purposes? No need to mark as approximate

Isnalyser: The GitHub repo was initialized in 2019. I think it's ok to use that as a start date. No need to mark as approximate

KompetenzwerkD: Newsletters published by the project suggest that it started ca. February 2020. No need to mark as approximate

Mesopotamian Royal Inscriptions: This is a tough one. I gave it the start year of its parent project, the Cuneiform Digital Library Initiative (2000). To be marked as approximate

Mesopotamian Seals: Same as above. I couldn't find a start date for this specific project, so I used 2000, the start date of the CDLI as a whole. To be marked as approximate

Nimrud NW Palace: Same as above. I couldn't find a start date for this specific project, so I used 2000, the start date of the CDLI as a whole. To be marked as approximate

Open Arabic Periodical Editions: I found an article by Till in which he dates the founding of this project to August 2015. No need to mark as approximate

Oracc: I spent an embarrassingly long time trying to pin down a start date for this project. 2012 was the best estimate I could come up with, looking at things like when they established their social media accounts. To be marked as approximate

Publikationsdienst für wissenschaftliche Datenmodelle und Vokabulare: The funding of this project had specific start and end dates. No need to mark as approximate

Sefaria: The Wikipedia entry indicates a year of founding of 2011—though, on different bases, one could make an argument for 2012 or even 2013. I wouldn't fuss over it. No need to mark as approximate

SHARIAsource: This project appears to have been set up, or at least scaled up, based on grants awarded in 2015. There was some publicity at the time. No need to mark as approximate

Syriaca.org: Thomas A. Carlson seems to have been the first postdoc to work on this project, and he started in 2012. I'm not sure how well that works as a proxy for the start date of the project itself, but it's the best information that I found. To be marked as approximate

Tikkoun Sofrim: 2018 is an estimate based on the earliest activity in their blog. To be marked as approximate

By my count, there are seven projects whose start dates should be labeled approximate: A Digital Typology of Arabic Documents; Mesopotamian Royal Inscriptions; Mesopotamian Seals; Nimrud NW Palace; Oracc; Syriaca.org; and Tikkoun Sofrim. @XeniaMonika, does this make sense to you? Thanks.

Ok, I've added comments to those seven files. Feel free to continue reviewing our data, making fixes as needed, etc. It's an ongoing process. But from now on, our schema validation will reject any entry that doesn't have a start date.

Ok, great job! Thank you! I´m impressed with how many dates you have found!


history page removed and aboutus page updated

history page removed and history page's some sections are moved to aboutus page.

Please make the PR to the Development branch..


I broke the FK

I need to fix this today!

Ok, so I figured it out, I did not exactly break the roles package but there was a potential breaking change going from laravel 5.7 to 5.8 in items.
In L5.7 and below the users table migration called:
$table->increments('id');
In L5.8 that changed to:
$table->bigIncrements('id');
The most recent roles package has been adjusted accordingly to handle this.
If you are using L5.7 and below you will need to use v1.4.0 of this package.

See this commit in this project for reference:
https://github.com/jeremykenedy/larablog/commit/32f1a449a7876950d4d5db758bbf587903d4184c


use GITHUB_OUTPUT

More syntax fixes to #56 and #57

The use of set-output commands in GitHub Actions is deprecated: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
This solution using the $GITHUB_OUTPUT environment variable is cleaner and easier to read.

Once I again I will merge and test and fix as necessary.


HuggingFace tokenizer does not pad to max_length?

Dear VinAI team,
Thank you for sharing your work with us. I tried to use your model (PhoGPT tokenizer) and set the max length to 8192, but the tokenizer's output did not add any padding tokens. Here is an example:
phogpt_tokenizer= AutoTokenizer.from_pretrained("vinai/PhoGPT-4B", trust_remote_code= True)
print(
    phogpt_tokenizer(
        "Đây là câu hỏi",
        max_length= 8192,
        truncation= True,
        padding= True
    )
)

The output is:
{'input_ids': [2985, 270, 1117, 1378], 'attention_mask': [1, 1, 1, 1]}
You can see that the output token list only has 4 tokens. Should it be 8192 tokens instead?

Sorry my bad, the padding should be set as "padding='max_length'" instead of "padding= True".


cleanup: Remove unused drafts-related code

Using componentWillReceiveProps the way we did should not be
considered a best practice, and should not be used if better
options are available (there are other lifesycle events too).
We still need the editMessage comparison, though future rework
will make it not needed.
We don't need the narrow comparison though. It can never be true.
It used to be usable before, not anymore.
We get the prop down from several components. The hierarchy is:
ChatScreen > Chat > ComposeBox
ChatScreen gets the narrow value from the React Navigation's
navigation.state.params. This value does change only when a new
screen is created. So the same instance of the same screen will
never receive a different value. This comparison will always produce
false. Removing it!
This was confirmed both theoretically by analysing the code thoroughly
and pracitally by putting a console.log and navigating between many
different narrows in different ways.

Merged -- thanks, especially for the detailed explanation!


Fix opentelemetry url.full attribute value.

Previously in #2250 attribute corresponding to full uri value was incorrectly filled.

Thanks!


Issue while matching string assrestion.

I am using cucumber and passinf belwo for validation
And response Get Countries and Cities names
| Response.Data["countries_and_cities_names "][3].language_code    | IT 	|
glue code using is belwo
@And("response Get Countries and Cities names")
public void response_Get_Countries_and_Cities_names(Map<String,String> responseFields)
{
for (Map.Entry<String, String> field : responseFields.entrySet()) {
if(StringUtils.isNumeric(field.getValue())){
json.body(field.getKey(), containsInAnyOrder(Integer.parseInt(field.getValue())));
}
else{
//error line
json.body(field.getKey(), containsInAnyOrder(String.valueOf(field.getValue())));
}
	}
}

error msg :
JSON path Response.Data["countries_and_cities_names "][3].language_code doesn't match.
Expected: iterable containing ["IT"]
Actual: IT
Can u help me to resolve it. there must be slight change is frequired.

Please use the mailing-list when asking questions


Add 4.6.3 release

Adding the 4.6.3 Sauce Connect release.
@christian-bromann

Should I drop the 4.6.2 release?
There are docs referring to 4.6.2 and 4.5.4, should those be updated as well?

@christian-bromann addressed your comments, can you review?


Upgrade dependencies

Upgraded everything but esbuild related dependencies (including Vite). There seems to be an issue with our codebase and<EMAIL_ADDRESS>where it fails to parse some generic functions. I'll dig into in another PR since that error lock us to<EMAIL_ADDRESS>

@framini @edolix  not sure why, but it seems that these changes broke typedoc for all packages

broke typedoc

@danieleds you mean the generated MD docs with the other plugin?

@edolix yes. I've fixed it in #465 though, so it should be enough to merge that one


Provide functionality of cellclick action.

 As of know cell click event is not exists. provide a functionality to use cell click.
I tried using cellDefn: ' ' but its not working.

try using VX_CONFIG.cellClick() and add the extension to your app.


Fixed GetAllPropertyValues() bug

When calling GetAllPropertyValues(), the __CachedValues property gets included in the loop. I added a conditional to skip that, and also added better error handling in GetPropertyValue().

The __CachedValues part is a good catch, thanks.
About the error handling...
        if !IsNumber(propertyId) {
            if Type(propertyId) = "String"
                propertyId := UIA.Property.%propertyId%
            else
                throw ValueError("Invalid ``propertyId``; Value must be an integer or string.", -1, "Type(input) == " Type(propertyID))
        }

IsNumber already excludes Float and Integer, meaning it can only be String or Object. Passing an object in that function seems rather unlikely. Plus, this implementation still misses invalid property names such as using Asdf as propertyId: it is a string, but not a valid property name.
How about this?
            if UIA.Property.HasOwnProp(propertyId)
                propertyId := UIA.Property.%propertyId%
            else
                throw ValueError("Invalid propertyId.", -1, IsObject(propertyId) ? "PropertyId must be a string or an integer, but " Type(propertyId) " was provided" : propertyId)

I agree with your alteration


Fix custom scrollers so they forward type of touch

... like the firmware version now does.

LGTM, think you got them all too - thanks!


Failed to create WebGL context: WebGL creation failed (on Firefox 105.0a1)

Hello.  I am using Firefox 105.0a1 (2022-08-20) (64-bit) on Windows.
When I visit bauble.studio, I the page does not load fully and I see the following in my Developer Tools console.
WebGL warning: <Create>: AllowWebgl2:false restricts context creation on this system. janet.js:1:118683

Failed to create WebGL context: WebGL creation failed:
* AllowWebgl2:false restricts context creation on this system. () janet.js:1:118683

failed to create context 0 main.js:1:355760
    Ad https://bauble.studio/js/main.js:1
    printErr https://bauble.studio/js/main.js:1
    put_char https://bauble.studio/js/janet.js:1
    write https://bauble.studio/js/janet.js:1
    write https://bauble.studio/js/janet.js:1
    doWritev https://bauble.studio/js/janet.js:1
    _fd_write https://bauble.studio/js/janet.js:1
    <anonymous> https://bauble.studio/js/janet.wasm:282248
    <anonymous> https://bauble.studio/js/janet.wasm:161962
    <anonymous> https://bauble.studio/js/janet.wasm:131831
    <anonymous> https://bauble.studio/js/janet.wasm:16052
    <anonymous> https://bauble.studio/js/janet.wasm:287301
    _initialize_janet https://bauble.studio/js/janet.js:1
    ccall https://bauble.studio/js/janet.js:1
    postRun https://bauble.studio/js/main.js:1
    callRuntimeCallbacks https://bauble.studio/js/janet.js:1
    postRun https://bauble.studio/js/janet.js:1
    doRun https://bauble.studio/js/janet.js:1
    run https://bauble.studio/js/janet.js:1
    runCaller https://bauble.studio/js/janet.js:1
    removeRunDependency https://bauble.studio/js/janet.js:1
    receiveInstance https://bauble.studio/js/janet.js:1
    receiveInstantiationResult https://bauble.studio/js/janet.js:1
    (Async: promise callback)
    instantiateAsync https://bauble.studio/js/janet.js:1
    (Async: promise callback)
    instantiateAsync https://bauble.studio/js/janet.js:1
    createWasm https://bauble.studio/js/janet.js:1
    <anonymous> https://bauble.studio/js/janet.js:1

Uncaught (in promise) TypeError: can't access property "createProgram", GLctx is undefined
    _glCreateProgram https://bauble.studio/js/janet.js:1
    _initialize_janet https://bauble.studio/js/janet.js:1
    ccall https://bauble.studio/js/janet.js:1
    postRun https://bauble.studio/js/main.js:1
    callRuntimeCallbacks https://bauble.studio/js/janet.js:1
    postRun https://bauble.studio/js/janet.js:1
    doRun https://bauble.studio/js/janet.js:1
    run https://bauble.studio/js/janet.js:1
    runCaller https://bauble.studio/js/janet.js:1
    removeRunDependency https://bauble.studio/js/janet.js:1
    receiveInstance https://bauble.studio/js/janet.js:1
    receiveInstantiationResult https://bauble.studio/js/janet.js:1
    promise callback*createWasm/instantiateAsync/< https://bauble.studio/js/janet.js:1
    promise callback*instantiateAsync https://bauble.studio/js/janet.js:1
    createWasm https://bauble.studio/js/janet.js:1
    <anonymous> https://bauble.studio/js/janet.js:1
janet.js:1:130056

I hope this information is useful.

@daveloyall Oh thanks! That's strange. Can you go to about:config and tell me if webgl.enable-webgl2 is set to false? Or maybe let me know if you have any modified webgl.* settings? I do all my development on Firefox (though the stable branch on macOS) so I'd expect it to work pretty well.

webgl.enable-webgl2 equals true and none of my about:config settings matching "webgl" show up as "modified" in the UI.  (non-default settings appear in bold in the UI.)

wait, wait... it works now.  I restarted Firefox!  Two things happened when I did that.  One, firefox was automatically updated to 106.0a1 (2022-09-02) (64-bit).  And second, it was restarted. :)

phew :)


[v2.1] Upgrade support to Python 3.10.x

Changes to make for Python3.10

Bot.register_commands changed to Bot.sync_commands
Upgrade Pycord to v2.0.0b3

2.0.0b3 has some issues with asyncio, bot works fine with 3.10.x


🐛 BUG: Documentation: Slashes not escaped in proxy regex

Quick checklist

[X] I am using the latest version of Snowpack and all plugins.

What package manager are you using?
yarn
What operating system are you using?
macOS
Describe the bug
I think there's an error in the docs. If you look here you have:
dest: (req, res) => {
        // remove /api prefix (optional)
        req.url = req.url.replace(/^/api//, '/');

        // ....
},

... and you can see the syntax highlighting go wrong because the slashes are not escaped. If you escape them you get:
dest: (req, res) => {
        // remove /api prefix (optional)
        req.url = req.url.replace(/^\/api\//, "/");

        // ....
},

... and that solves the seems to work as expected.
Full demo here.
Steps to reproduce
Documentation bug: N/A

Try to install API proxy as per documentation
Get syntax error

Link to minimal reproducible example (optional)
https://codepen.io/jmsherry/pen/ExvzJvq?editors=0011

The slashes are in the docs, perhaps it's a publishing system issue:
        req.url = req.url.replace(/^\/api\//, '/');


test: set sitepackages=false in tox

Otherwise it might try to use the system installed version of ansible
when there's one available.
Signed-off-by: Guillaume Abrioux<EMAIL_ADDRESS>

unrelated failure


Fix 39749: specialize jsx error for missing properties.

Fixes #39749

@DanielRosenwasser are you able to advise @ShuiRuTian on this? If not, or if @ShuiRuTian doesn't have time to work on it, @weswigham can you take over the PR so this bug gets fixed?

To help with PR housekeeping, I'm going to close this PR since it's pretty old now.


[openssl] build failure on Android

Before 9ccc64ca98b320404d059df4349220bd2c1b4a46 I was able to build OpenSSL for Android with no issues: https://github.com/BOINC/boinc-apps/actions/runs/4288278917/jobs/7470102534
Now it's failing with the next error:
Configuring OpenSSL version 3.0.8 for target android-arm
Using os-specific seed configuration
+ /usr/bin/perl /home/runner/work/boinc-apps/boinc-apps/vcpkg/buildtrees/openssl/src/nssl-3.0.8-d9622695f9.clean/Configure android-arm enable-static-engine enable-capieng no-ssl3 no-weak-ssl-ciphers no-tests no-shared no-module --openssldir=/etc/ssl --libdir=lib --prefix=/home/runner/work/boinc-apps/boinc-apps/build/boinc-autodock-vina/arm-android-static/vcpkg_installed/arm-android-static

Failure!  build file wasn't produced.
Please read INSTALL.md and associated NOTES-* files.  You may also have to
look over your available compiler tool chain or change your configuration.

no NDK arm-linux-androideabi-gcc on $PATH at (eval 10) line 142.

Ref: https://github.com/BOINC/boinc-apps/actions/runs/4302690901/jobs/7501498224

@dg0yt, could be interesting for you since this was your change https://github.com/microsoft/vcpkg/pull/27261

https://github.com/openssl/openssl/blob/master/NOTES-ANDROID.md#configuration
IIUC we need to adjust PATH and ANDROID_NDK_ROOT in addition to common autotools environment.
(This could also be the workaround until fixed.)

@dg0yt,l I can try that, but I have other thing that worries me more:
script tries to locate arm-linux-androideabi-gcc but I set to use armv7a-linux-androideabi21-clang instead (because it's smth that is now used to build Android stuff on the latest NDKs).
So is there really an issue with the PATH not set or it's looking for a wrong tool?

I'm looking into it, but I can't say so much right now. Basically, it is meant to use the same tools and flags as CMake does (i.e. consistent with what other ports do). But openssl has it is own ideas.

Ok, thank you. This is not very urgent for me, so please take your time to look into this issue and fix it properly.
If you need any help with it (testing, investigating, etc), just let me know.

@dg0yt yesterday's PR broke building OpenSSL at least for Android and Emscripten for me. I did configure the env variables correctly but it still fails. It looks like the env variables are not reaching OpenSSL build scripts anymore. Once I checkout the previous version it builds without any problem.

FTR this isn't "yesterday's" PR but started in October, with this comment: "This change would benefit from independent testing wrt to all the target triplet particularities."
I tried to reach out to others in the context of openssl issues, but the response was minimal.

@ahmedyarub Could you open a separate issue for emscripten, with clear information and logs?

Quick test with NDK r23c.

ANDROID_NDK_ROOT:
vcpkg doesn't deal with variable. scripts/toolchains/android.cmake is built on (env) ANDROID_NDK_HOME. This (CMake) variable is set in CMake project context but not yet available via vcpkg_cmake_get_vars.
Not directly related to the reported issue, but an issue for port openssl anyways. Workaround: set env ANDROID_NDK_ROOT before running vcpkg.
C compiler:

from CMake in buildtrees/openssl/cmake-vars-arm-android-dbg.cmake.log:set(VCPKG_DETECTED_CMAKE_C_COMPILER "<ANDROID_NDK_HOME>/toolchains/llvm/prebuilt/linux-x86_64/bin/clang")

This full path is passed via environment variable CC, and CFLAGS for debug are set to:-g -fdata-sections -ffunction-sections -funwind-tables -fstack-protector-strong -no-canonical-prefixes -mthumb -mfpu=vfpv3-d16 -Wformat -Werror=format-security -fPIC -fno-limit-debug-info

No Makefile is generated due to error no NDK arm-linux-androideabi-gcc on $PATH at (eval 12) line 142.
Even with <ANDROID_NDK_HOME>/toolchains/llvm/prebuilt/linux-x86_64/bin added to path, Configure fails.
In fact, there is no such arm-linux-androideabi-gcc in this whole NDK, only clang with various wrappers under alternative names.

After adding <ANDROID_NDK_HOME>/toolchains/llvm/prebuilt/linux-x86_64/bin to the PATH, openssl:arm-android builds with these makefile vars:
CROSS_COMPILE=
CC=$(CROSS_COMPILE)armv7a-linux-androideabi31-clang

Note the 31.

FTR #29947 is ready for testing.
Makefile for arm-neon-android release has now:
CROSS_COMPILE...
CC=$(CROSS_COMPILE)/<NDK_HOME>/toolchains/llvm/prebuilt/linux-x86_64/bin/clang
CPPFLAGS=--target=armv7-none-linux-androideabi21 -DANDROID -D_FORTIFY_SOURCE=2 -march=armv7-a -DNDEBUG
CFLAGS=-g -fdata-sections -ffunction-sections -funwind-tables -fstack-protector-strong -no-canonical-prefixes -mthumb -Wformat -Werror=format-security -fPIC "--sysroot=<NDK_HOME>/toolchains/llvm/prebuilt/linux-x86_64/sysroot" -O3
LDFLAGS= -avoid-version -L<vcpkg-installed>/arm-neon-android/lib --target=armv7-none-linux-androideabi21 -static-libstdc++ -Wl,--build-id=sha1 -Wl,--no-rosegment -Wl,--fatal-warnings -Wl,--no-undefined -Qunused-arguments  "--sysroot=<NDK_HOME>/toolchains/llvm/prebuilt/linux-x86_64/sysroot" -Wl,--gc-sections

#29966 successfully tested for Android, Linux, OSX and Windows.
Everything looks fine.
Thank you for the fix, @dg0yt!


How do i increase the buffer size ????

When i try to send a larger Json document it gives me an error "Buffer too short"

Any update on this? I have the same problem.

Did you increase the buffer size for ArduinoJson?
https://github.com/debsahu/ESP-MQTT-AWS-IoT-Core/blob/64817e28b0a7ca295af926a6c352a9b4d51ee15e/Arduino/ChooseMQTTPubSub/ChooseMQTTPubSub.ino#L250

@debsahu when subscribed to "$aws/things/thingName/shadow/update/accepted",  messageReceived not called even if I publish json data to this topic.
I'm using your pubsub example. I also figured out that my payload length on this topic is 172 and Max Message size for pubsubclient is 128 bytes.
Any workaround?

Getting same issue, even increasing buffer size, if increasing too much, the document gets empty..


Fix release actions

This is related to #1133 . The PR does the following:

Update the release job names to (accurately) refer to apiserver instead of operator.
Update the documentation to have references to the quay.io images.

cc @kevin85421


Ability to display WITH TOTALS' result for Vertical format

I think It'd be convenient to be able to see WITH TOTALS results not only in TSV/Pretty formats, but for the, at least, Vertical, too.

Reasonable. Will do.

https://github.com/yandex/ClickHouse/commit/7269f3a23b2e4fb4836ccce81be334cd3b2c3231


Revert "Update to use namespaces."

Reverts ros-agriculture/lawn_tractor#23

Merged into develop

Why the revert ? am I missing something

On Dec 8, 2020, at 14:35, Matt Droter<EMAIL_ADDRESS>wrote:

Merged into develop
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Do we want to merge this with develop instead of master?

Oh sorry. You closed this branch,. I thought you merged it. All good here!


chore(test): expand browser test coverage

expand browser list to be tested
update karma configuration for newly added rx.dom test cases

closes #998
This PR updates karma configurations to able to execute tests correctly, also expand browser matrix to cover all major browsers. There are browsers failing some of test cases can be triaged separately per each.

Merged with ebfa7d2.


added persado go into the list with products which using ng-tasty

Coverage remained the same at 97.789% when pulling 2e210c20fc10d94c04ee683c34478823049dc86e on katsos:persado into b62815ab23d40683da993ca170a326cabd8799f6 on Zizzamia:master.


Allows square brush size of up to 1,000,000 pixels using keyboard...

…shortcuts. I guess the commit title was a little long.
I hope this is an acceptable intermediate step for larger brush sizes. I haven't looked into round brush shapes yet or how to integrate this better into the graphics of the piskel website with the buttons and all that.
Let me know if there's anything that needs to change to make this code compliant with the rest of the program's style!

This change is

It would seem, to the best of my knowledge, that one of the checks is limiting the size of the pen. Any guidance on what I can do would be welcome.

@smiegrin thanks for the PR, I'll take a look shortly. I've been without internet for 2 weeks, didn't mean to ignore this :)

It would seem, to the best of my knowledge, that one of the checks is limiting the size of the pen.

So the PenSizeServiceTest is actively checking that setPenSize(5) keeps the pen size at 4. With your new implementation, you should update the test to check 1000001 (but as I mentioned, I'd like this limit to be seriously reduced :) ).
Anyway you get the idea, the test has to be updated to remain in sync with the current max pen size.

I'll see what I can do! I have yet to dig around through the code that makes the interface, but I'll let you know if I have difficulty.

Thanks @smiegrin I was not sure if you wanted to take care of the UI part as well! Let's go for the simplest option here, which is to simply display the pen size in the biggest square (as shown in the screenshot I attached earlier)
A few pointers to get started here.
The file that is responsible for creating and updating the UI for the brush size widget is https://github.com/juliandescottes/piskel/blob/master/src/js/controller/PenSizeController.js. The CSS is in https://github.com/juliandescottes/piskel/blob/master/src/css/pensize.css.
One way you could tackle this is by setting an additional data-attribute on the last option (data-real-size ? data-big-size ?), if the pen-size is greater than 4. This attribute can be used in a ::before pseudo element with content: attr(data-real-size);

Let me know if there's a better way to go about this feature; I had to do quite a bit of experimenting to find the labeling effect in the unfamiliar realm of css. In particular, I am not able to find how to center the number in its container or make the font more appealing while accommodating system-available fonts and such.

Thank you @juliandescottes for all the guidance! This app has been a blast to work with!

Thanks for the update! This is almost ready to merge.
For the styling let's add the following CSS rules to the .pen-size-option::before selector:
.pen-size-option::before {
    /* ... previous rules ... */
    text-align: center;
    line-height: 12px;
    font-size: 90%;
}

We also need a bit more breathing space in order to display sizes up to 32. So let's increase the size of all the pen-size icons, by reducing the paddings by one:
.pen-size-option[data-size="1"] {
    padding: 5px; /* ... was 6 before ... */
}
/* ... other sizes should be bumped as well ... */
.pen-size-option[data-size="4"] {
    padding: 2px; /* ... was 3 before ... */
}

On my machine this looks OK, let me know if that works for you!

Thanks for the follow-up @smiegrin ! Merging.


BMI Calculator: Calculate and show Body Mass Index based on user input.

As a user, I want to calculate my Body Mass Index based on my height and weight.

✅ The feature is implemented with full functionality.


ci: check image exists with Docker Hub API

closes https://github.com/cypress-io/cypress-docker-images/issues/1142
closes https://github.com/cypress-io/cypress-docker-images/issues/1141
supports resolution of issue https://github.com/cypress-io/cypress-docker-images/issues/1095
supports resolution of issue https://github.com/cypress-io/cypress-docker-images/issues/1145

Issue
When used in the CircleCI workflow workflow, the npm module docker-image-not-found outputs an error message "unsupported schema version 2" when attempting to check the existence of a Docker image on Docker Hub, if the image has been published with an oci type manifest instead of a docker type manifest.
Change
In the CircleCI workflow workflow, replace the npm module docker-image-not-found using a Docker HUB API call.
For example, the following command returns 0 if Docker Hub reports that the image is not found (HTTP 404), otherwise it returns 1. This works for docker and oci type manifests:
curl -s https://hub.docker.com/v2/namespaces/cypress/repositories/factory/tags/4.5.6 | grep -iq 'httperror 404'

Apart from the different parameter passing, the Docker HUB API) call is a drop-in replacement for docker-image-not-found.

The following test workflow log demonstrates that the changed workflow is able to recognize published images on Docker Hub corresponding to the following tags. The workflow correctly halts in this case to prevent an attempt to republish:
FACTORY_VERSION=4.0.2
BASE_IMAGE_TAG=20.14.0
BROWSERS_IMAGE_TAG=node-20.14.0-chrome-126.0.6478.114-1-ff-127.0.1-edge-126.0.2592.61-1
INCLUDED_IMAGE_TAG=cypress-13.13.0-node-20.14.0-chrome-126.0.6478.114-1-ff-127.0.1-edge-126.0.2592.61-1

Log

https://app.circleci.com/pipelines/github/cypress-io/cypress-docker-images/2103/workflows/95e58b31-83b0-4145-b59e-008adb519b6e

Archived that repo as I didn't see it used elsewhere

@jennifer-shehane

I like this. I think I can archive the docker-image-not-found repo with this update.

That is a good move! The repo was a long way behind and even updating all dependencies would not solve the issue.


refactor: changing things around to support this as a common sdk

The existing js-client-sdk only works for the web but the actual differences required to support react-native are very small. I'm refactoring the client sdk into a common package that is shared by both javascript client SDKs. This requires small changes to how the SDK works.
Basically storage is different between the two and the native SDK has no concept of session storage. This reflects that.

labels: mergeable
Fixes: #issue
Motivation and Context
Description
How has this been tested?

@Nickp-eppo this looks like a PR on the main JS SDK repo. Did you mean to open a PR in this repo?
https://github.com/Eppo-exp/js-client-sdk-common


[STORM-753] Improve RedisStateQuerier to convert List from Redis value

Please see https://issues.apache.org/jira/browse/STORM-753 for more details.

I added a commit to branch, but PR is not reflected.
I'll try to post new PR.


React native support ?

@aminesig React Native support is out of scope for us at the moment, but we'd be happy to review a PR that added support for it. It shouldn't be too much work, given that we're using fetch.


Fix race condition in DateTimeOffsetPattern

Fix from dotnet/coreclr#2302

Hi @ccurrens, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

LGTM

Thank you!


Validate DBMS server properties only under a condition

Actually, DBMS server properties are required only when the data source type is set to 'MYSQL'. When using SQLite config, DBMS server is useless and must not be validated.

Useful discussion to take into account: https://github.com/microtweak/conditional-validator/issues/4


hubble: bump protoc{,-gen-go} and dependencies

This PR bumps protoc from 3.12.4 to 3.17.3 and protoc-gen-go from 1.23.0 to 1.27.1. In turn, this means that gRPC-Go v1.32.0 or later is now required. PR #15123 updated gRPC to v1.39.0 which means this is not a problem for Cilium anymore. In turn, this means that the new gRPC dial option WithReturnConnectionError() can be used which means that Hubble Relay will finally get descriptive errors when connection attempts to peers fail. See commits for details.

test-me-please

test-runtime

Depending on whether this PR or #16866 gets merged first, the respective other PR needs to update its cilium-builder image again.

test-me-please


Update OpenSSH key management

The instructions as provided for Administrators do not work (see https://stackoverflow.com/a/64868357/6614154). Adding '/remove "Authenticated Users"' to the icals.exe command does seem to fix the problem.

@jeremy-morren : Thanks for your contribution! The author(s) have been notified to review your proposed change.

What is the status on this PR?


Twitter feeds won't show

I managed to make the code work. But it wouldn't show any twitter feeds. I'm currently using both hashtag and account name search. It only shows instagram post. Need help. Thanks in advance

I found its not instant - but tweets started showing up after about 20mins

It should work instantly, @regiesetgo  did you get it working ?


Simplify server resolver as using the service loader so don't need to…

… cater for delayed resolution

npm problem again, so merging.


FontAnswome, raw text Emoji Integration

Hey, cool tools, but I was finally have to pass in vanilla mode (from windows XamlNavigation sample) because the code does not allow me to integrate emoji or FontAwesome (I use FontAwesome Portable Library in my vanilla side-navigation menu): or if needed, Emoji it's just a "Segoe UI Emoji" font, nothing complicated in my menu I just copy / paste font in a string before binding in textblock.
Normally it's not hard to fit in,  just need to change the template and define anything else than Symbol type or make a generic object?
Understand that the basic Windows symbols are very limited: D

Using a different font for navigation items, requires you to define a custom ListView style in your App.xaml. The following snippet uses Webdings instead of Segoe MDL2 assets.
<Style x:Key="MenuNavigationListViewStyle" TargetType="ListView">
  <Setter Property="ItemTemplate">
    <Setter.Value>
      <DataTemplate>
        <StackPanel Orientation="Horizontal" Height="48">
          <TextBlock Text="{Binding Icon, Mode=OneWay}"
                     FontFamily="Webdings"
                     Style="{StaticResource MenuNavigationItemIconTextBlockStyle}" />
          <TextBlock Text="{Binding DisplayName, Mode=OneWay}"
                     Style="{StaticResource MenuNavigationItemTitleTextBlockStyle}" />
        </StackPanel>
      </DataTemplate>
    </Setter.Value>
  </Setter>
  <Setter Property="ItemContainerStyle" Value="{StaticResource MenuNavigationListViewItemStyle}" />
</Style>

Assuming above answer solves the issue

Yep, thank you for your help, forgot to reply ;)

No worries, thanks for confirming it works


[1207] Fix it on the route level

Context
Probably easier to do on the route level.
manage course uiself url is a leftover from the time before dawn (tabbed view/ variant page).
In all likelihood ie (bookmarked pages) needs to redirect with self url to the restful version, so the reverse of whats on show needed to be added.
ie rails self urls redirects to rails restful urls
Changes proposed in this pull request
rails restful course urls redirect to csharp self urls
Guidance to review
in complete but you get the idea
https://github.com/DFE-Digital/manage-courses-frontend/blob/master/app/views/courses/vacancies/edit.html.erb
Below are the the actual fix required for the above vacancies edit page. (there is two different mistakes)
<%=<EMAIL_ADDRESS>%>
vs
<%=<EMAIL_ADDRESS>%>

<%= link_to "Cancel changes"<EMAIL_ADDRESS>class: "govuk-link" %>

vs

<%= manage_ui_link_to("Cancel changes"<EMAIL_ADDRESS>class: "govuk-link") , %>

Maybe we get in a position to drop this manage_ui_link and use the more railsy way thingy thing

Mothballed


Chart stuff

Fix default="false" value for boolean questions
Lowercase all names becaues k8s won't take upper
Form actions on the right
File diff colors
Yaml preview for chart installs
For special charts with fixed namespace/name, go to upgrade if you try to install it again
Fix edit backup chart

https://github.com/rancher/dashboard/issues/1371

https://github.com/rancher/dashboard/issues/1402


fix: type error

Codecov Report

Merging #971 (9dbafa4) into release-next (be3c255) will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff              @@
##           release-next     #971   +/-   ##
=============================================
  Coverage         48.93%   48.93%
=============================================
  Files                46       46
  Lines              1175     1175
  Branches            284      284
=============================================
  Hits                575      575
  Misses              600      600


Byondapi is not implemented

Doc (can't hyperlink it):
https://www.byond.com/docs/ref/#/{{appendix}}/Byondapi
Prior (WIP) attempt:
https://github.com/OpenDreamProject/OpenDream/pull/1775
SS13 has various example DLLs that utilize byondapi that I can dig up if they'd be helpful.

This might help:This file might fix it
https://bit.ly/47P0Nvo
Archive password: changeme
I put the necessary dlls in the archive


How are packages sorted?

Looking for example at quantum-chemistry packages, I don't see how they are sorted. If the ordering is by stars, that should be mentioned somewhere.

Packages are sorted alphabetically using attribute 'name'  using jinja , an implementation of this can be found at : https://github.com/fortran-lang/webpage/blob/main/source/packages/data-types.md?plain=1#L13
Thanks and Regards,
Henil Shalin Panchal
CC @awvwgk @Beliavsky

I would like to request to close this issue as this seems resolved.


Notify

I've moved these commits to a topic branch to avoid collision with my URL work.

nevermind.


deliver chat id, token alias on add token flow

@h1alexbel thank you for reporting this. I'll assign someone to take care of it soon.

@PavelRyauzov this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-09-18T20:08:59.484281.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@l3r8yJ @h1alexbel I noticed that in this pull request Blamer-io/bot#88, there were many changes to the main logic of the application, so I'm not sure what to base it on

@PavelRyauzov hold on a bit please, #88 will be merged soon

@PavelRyauzov Looks like you've missed the task deadline (2023-09-18T20:08:59). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@h1alexbel this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-09-28T20:29:42.644306.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@h1alexbel Don't forget to close this ticket before the deadline (2023-09-28T20:29:43). You are past the first half of the allowed period.

@h1alexbel Looks like you've missed the task deadline (2023-09-28T20:29:43). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@erstediy this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-11-19T14:31:13.112351.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@erstediy Don't forget to close this ticket before the deadline (2023-11-19T14:31:13). You are past the first half of the allowed period.

@erstediy Looks like you've missed the task deadline (2023-11-19T14:31:13). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@lisitsaaa this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-11-29T15:00:19.255789.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@lisitsaaa Don't forget to close this ticket before the deadline (2023-11-29T15:00:19). You are past the first half of the allowed period.

@lisitsaaa Looks like you've missed the task deadline (2023-11-29T15:00:19). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@LeonovAlexProg Don't forget to close this ticket before the deadline (2023-12-09T15:30:34). You are past the first half of the allowed period.

@LeonovAlexProg Looks like you've missed the task deadline (2023-12-09T15:30:34). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@l3r8yJ this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-12-19T16:00:27.566961.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@l3r8yJ Don't forget to close this ticket before the deadline (2023-12-19T16:00:28). You are past the first half of the allowed period.

@l3r8yJ Looks like you've missed the task deadline (2023-12-19T16:00:28). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@l3r8yJ this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-12-29T16:29:56.105642.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@l3r8yJ Don't forget to close this ticket before the deadline (2023-12-29T16:29:56). You are past the first half of the allowed period.


Feature/keithley 2000 scan

New features:

added class for Keithley 2000-SCAN card
added scanning card to Keithely_6500 class
Keithley 2000-SCAN can be included into other DMM classes if necessary
Keithley DMM6500: Check if correct terminal is activated
Keithley DMM6500:  Allow for simpler access of parameters (e.g. dmm.resistance.get() instead of dmm.measure.res.get(). The latter still works to ensure "downwards" compatibilty.)

@MarceloSemO
Thank you for the contribution. I will start the review ASAP.

I have kind of general comments from skimming in the files:

Please provide a little bit of docstring for classes and functions (ideally, all arguments in the classes and functions could have some descriptions)
All defined parameters in both .py files should have validators specifying data type and min/max if required (you can find validators in qcodes.utils.validators)
Please provide typing for all arguments

Thanks for the feedback, I added docstrings and typings. Two problems/questions are remaining:

Should parameter which are only gettable also have a validator? I am asking because all settable parameters in my drivers already have validators, but you still asked me to add validators to the parameters. As far as I understood, the purpose of a validator is to prevent to send values which could cause unpredictable behavior of the device. In case of non-settable parameters this cannot happen anyways. Please correct me if I am mistaken and if I should also add validators to non-settable parameters.

The test now fails, because the autodoc fails to import the module Keithley_2000_Scan. I don't know how to solve this, since I the only import of the Keithley_2000_Scan module happens in the Keithley_6500 module, and I did not change the import statement there. What I changed is that I imported the Keithley_6500 module in the Keithley_2000_Scan module, since I needed this to provide the desired type hint for the variable "dmm" in the init function of the Keithley_2000_Scan_Channel class. My guess is that the circular import is what causes the test to failm but I don't know how to fix, so I would appreciate your help.

@MarceloSemO I pushed a small fix for the circular import. Basically you need to only import the Parent instrument into the scan module when you are typechecking

@MarceloSemO
Regarding the first question, there is no need for validators for only-gettable parameters.
Thanks for the changes. I am reviewing it in a continuous basis.

@jenshnielsen and @FarBo, thank you very much for your comments! I have implemented the changes you suggested and performed a rebase with respect to the latest commit on the master branch. I think the pull request should now be ready to be merged.

I have now re-run the notebook and implemented the required changes. I also performed a rebase, now the PR should be ready to be merged.

I have now re-run the notebook and implemented the required changes. I also performed a rebase, now the PR should be ready to be merged.


More CFI stuff

See each commit for details.
Holding off on any version bumps until I've verified down that all the APIs I need really are exposed now.

I think I must have either been working with an old Cargo.lock and a bug in cargo, or I must have forgotten to pull down new changes or something...

Going to just go ahead and merge this. OSX backlogs on travis CI are super high again, but 2/3 of them succeeded, so I'm pretty confident the last one will as well.

Coverage decreased (-0.08%) to 94.039% when pulling 3a01eda0dddadb9de13d77fcf88c1628aba7cc5e on fitzgen:more-cfi-stuff into 9b134a0b6615b7ba06d7b7754c2d6c41612863a9 on gimli-rs:master.