Add lock mechanism to image downloader and debug for jobs

Signed-off-by: Agnaldo Junior<EMAIL_ADDRESS>

Fixes #42


next_run gets calculated wrong for timezones that have daylight saving time (DST)

Hi, I found this fork of django q. Thanks for maintaining django-q!
I have got some problems using the scheduler and the calculated next_run in my timezone (germany), because we have daylight saving time.
I want to create a schedule that runs every day at 6am (german time). It will be stored as 2022-10-01 04:00 UTC in the database if I create that schedule in summertime (UTC+2).
Now its wintertime (UTC+1) the schedule should still run every day at 6am (german time), but instead it runs at 5am (german time), because the datetime in the database is still 2022-11-01 04:00 UTC (and not adjusted to 2022-11-01 05:00 UTC).
Django settings are the following:
TIME_ZONE='UTC'
USE_TZ=True

Changing the settings to TIME_ZONE='Europe/Berlin' does not fix the problem and django documentation also suggests that I should not change this setting.
Have you or anynone encountered such problem?

Thanks for reporting this!
Two questions:

Could you show me the schedule you are running? I am mainly curious if you are using any of the build-in schedules or if you are using the cronitor package in addition to this package.
Did you have the same issue with the old package? (if you ever used that)

Django-q (the old version) uses Arrow to calculate some of the datetimes. I have removed that package from this library, maybe that messed with the timezones a little.
Thanks!

Thanks for reply!

question: I am using the build-in schedules (WEEKLY)
question Yes, I encountered that problem in the old version also. I also found a related ticket to that topic in the old repo here: https://github.com/Koed00/django-q/issues/630

Sidequestion: Why did you remove the arrow package?

Okay thanks. This should be a fairly easy fix. Will get back to this in the next few days.

Sidequestion: Why did you remove the arrow package?

There were only two places where this library was used. It was easy enough to create two small functions that handled the things that Arrow handled for us in this library. In general, I like to keep things simple and not add more dependencies than absolutely necessary.

Oh, that's a good idea! Will do that!

Hey! First of all, Thanks a lot for your work on django-q2!

Have you or anynone encountered such problem?

Yes, We are having the same issue with running DAILY schedules in Germany. The suggested solution via Q_CLUSTER config works for us too and is very appreciated :)

@SebastianRehfeldt @Grayknife Sorry for the delay on this. I forgot how annoying dealing with timezones is, haha.
In any case, this fix has been released under v1.4.7.
See test here:
https://github.com/GDay/django-q2/blob/cf33275d92ecb510aa0a63ac1432dd92b06856ef/django_q/tests/test_scheduler.py#L87-L141
Docs: https://django-q2.readthedocs.io/en/latest/configure.html#time-zone

Feel you, i also hate timezones...
Thank you very much for your fix!


Built-in attribute max values

Attributes currently only have a base value, and you calculate the modified value by iterating over the modifiers from effects active on the AbilitySystem.
I'm debating whether to include a max_value on the AttributeResource itself (GAS does not do this, but rather treats the max value in a completely separate attribute (StaminaAttribute and MaxStaminaAttribute would be two separate attributes).

A draft max-clamping is in place; using separate Attributes like Unreal GAS.
Closing this for now, might rework further down the line.


Give our queues and topics much clearer names

Closer to “input” / “output” than the current somewhat messy state.

Done in https://github.com/wellcometrust/storage-service/pull/96


feat: inject parser and extendedExecutor wrapper into  flink

@aiwenmo look this desin, but not support flink-1.12, support for it will compatability.


No raw data for ImmutableDataHolder

Unlike DataHolder's setRawData, there is no withRawData method for "setting" raw data on ImmutableDataHolder.

Many immutable structures just don't support raw data or DataViews in general. Case in point: BlockState, FluidState, LocatableBlock. The ones that would technically support it are ItemStackSnapshot, FluidStackSnapshot, EntitySnapshot, and BlockSnapshot. The fun part is that BlockSnapshot already has a withContainer method, but it seems that we ended up missing that for EntitySnapshot when it was created.

I do feel like it should be some kind of superinterface that specifies such a method.

Fixed in API 8 with the Data API refactor.
SerializableDataHolder.Mutable#setRawData https://github.com/SpongePowered/SpongeAPI/blob/992ef50c171183070bede2d234379052613d830e/src/main/java/org/spongepowered/api/data/SerializableDataHolder.java#L81
SerializableDataHolder.Immutable#withRawData https://github.com/SpongePowered/SpongeAPI/blob/992ef50c171183070bede2d234379052613d830e/src/main/java/org/spongepowered/api/data/SerializableDataHolder.java#L112


Opportunities section card's content and buttons are not alligned

Can you please assign me will fix it

I would love to work on this issue, can you kidly assign me this issue?

Go for it @Arghya-Banerjee , please attach the screenshots after edits in the PR.

Go for it @Aman0786-git , please attach the Screenshots after edits in the PR.

Go for it @Aman0786-git , please attach the Screenshots after edits in the PR or you can join our discord for better connection.

Sure ;-)

Please assign this task to mee

@DeveloperAshish8 Can you please add hactoberfest label so that it can be counted and also I am not able to join your discord server I dont know is the link broken ?

https://github.com/DeveloperAshish8/CodeChamp-s-Website/pull/57#issue-1393468654
PR review @DeveloperAshish8

@DeveloperAshish8 PR Check

Whats the status, can I pick up this?

Whats the status, can I pick up this? Also please add hacktober label to this issue too!

I've made the changes waiting for the review


Azure Web Bot App Scoring System, is there a way to get confidence score which exactly using inside qnamaker? currently bot only returns prediction score.

This repo is currently only taking Design Change Requests (DCR) issues. For submitting bug fixes and feature requests, please go to the following repo Botbuilder-CognitiveServices.


eShop challenge update

Hi,
Would it be possible to please change the eShop challenge to include an example other than beer,
https://github.com/microsoft/CopilotHackathon/tree/main/challenges/eshop
Thanks,

Closed by #41


Add a simple control panel similar to Pronterface

Add a pronterface like basic control panel that allows user to simply move in X, Y and Z axis using a few buttons.
User is also able to home axis separately and all at once.
A log console has also been added to this panel in order to be able to see the Gcode we send and receive from the machine.

Cool work!
Thanks a lot!
I will try to make a release in the next day ;-)
greetings
Patrick

you rock!
Le 01/04/2015 10:16, pknoe3lh a écrit :

Cool work!
Thanks a lot!
I will try to make a release in the next day ;-)
greetings
Patrick
—
Reply to this email directly or view it on GitHub
https://github.com/pknoe3lh/cncgcodecontroller/pull/20#issuecomment-88388991.


migration path from version 6 dss files to version 7

There is no support for version 6 dss files, so what is the recommended way to move to version 7 files from existing version 6 files?

The recommended technique for converting between dss 6 to dss 7 is using our standalone application DSS-Vue.
https://www.hec.usace.army.mil/software/hec-dssvue/
@ktarbet - feel free to add more context

I guess a scripting approach would be to use the jython in hecdssvue then. Thanks

There is actually a built in tool under the tools tab that will automatically convert to your choses version of DSS

@oskarhurst I prefer scripting solutions rather than having to click around on UIs. So I am looking for a script or a command line tool to help convert. Thanks

To script it in jython you would use hec.heclib.dss.HecDSSUtilitiesconvertVersion(String fileName).
You can see it used at line 1032 of https://github.com/HydrologicEngineeringCenter/DSSVue-Example-Scripts/blob/master/src/DssConverter.py


Implement filtering and details on gatewayd info API

Today, gateway-cli info returns high level information on all connected federations. Consider supporting filters on gatway info api, so we can use cli or api call to get information about a specific federation served by the gateway.
Proposal:

gateway-cli info continues to return high level info about all connected federations
gateway-cli info <federation-id> should return detailed info about the federation identified.

Details might include balance, summary of transactions, etc

Hi @okjodom, I am interested in this. Can you please assign this to me so that I can try working on it?

Go for it :)

However, I recommend you wait for #1718  to land so you have a clean starting point requiring you to implement changes in one place only

You could also just branch off #1718 and then make a PR based on that. Should be compatible once #1718 gets merged.

Sure, I will follow everything and then raise a PR. Thanks!

Go for it! There should be no blockers for tacking this issue right away.
Afaik (assumption), @kushalnl7 dropped their interest in this issue by removing their own assignment. Go ahead and claim this issue, @oleonardolima.
And yes, there's tons of other good first issues in this space, so we won't run out of room to contribute :)

@okjodom Great! I'll start working on it then 🚀

Cool! I'll follow this path then

why, what are your thoughts?
Ah, because by the other approach, I was thinking it could be multiple calls to existing routes, instead of passing a query parameter, that would need to handle and combine the data on cli client and I guess wouldn't be that great 😅

@okjodom I got myself with two questions related to the tests:

the specific tests for gateway-cli are those in cli-test.sh ?
there are no tests yet related to the ln-gateway and rpc-client (besides the one for auth) ?

I was wondering at which place would be appropriate to add some tests related to the change 🤔, am I missing something ?

We have no specific tests for the gateway-cli.
cli-test.sh is meant to test the fedimint-cli, and not gateway-cli. However, you might find an instance where gateway-cli is applied in the course of testing fedimint cli.

Opinion: I don't think we wan't a shell test for gateway-cli.

You probably noticed that gateway-cli uses an instance of this RpcClient to interact with Gatewayd API. Now a similar instance of RpcClient is used in existing gatewayd athentication_tests thus there's already some coverage on the APIs from that angle. I'm proposing an extensive gatewayd test suite that would excersise  RpcClient API even further.

Gap: Given RpcClient api surface is naturally tested by it's application in gatewayd tests, If we needed tests for gatewayd-cli, we'd scope them to testing of the CLI option parsing and error handling only.

Here is another related WIP, simplifying the gateway test structure

the specific tests for gateway-cli are those in cli-test.sh ?

In the next week the way we test the CLIs is going to change a lot. We'll replace the cli-test.sh with some tests in Rust that call out the the shell. At that point would be a good time to write some tests for the gateway-cli. @Maan2003 working on this migration here FYI -> https://github.com/fedimint/fedimint/pull/1910.

I potentially good first step in this direction would be to allow naming gateways. Then you could do commands with gateway-cli info <name> where name is something you can remember. Pasting federation IDs isn't fun!

We have no specific tests for the gateway-cli.
cli-test.sh is meant to test the fedimint-cli, and not gateway-cli. However, you might find an instance where gateway-cli is applied in the course of testing fedimint cli.

Oh, I misunderstood it, thanks for the explanation. Yes, that was it I saw the usage of gateway-cli and inferred that 😅

I'm https://github.com/fedimint/fedimint/pull/1702 that would excersise RpcClient API even further.

Good! I'll take a look at it.
--

In the next week the way we test the CLIs is going to change a lot. We'll replace the cli-test.sh with some tests in Rust that call out the the shell ...

Thanks, I'll check it and I'll give it a try on a test the change only for the Gatewayd API for now.

A potentially good first step in this direction would be to allow naming gateways...

Good point, this seems really interesting 🤔

@okjodom I'm not yet well aware of what info would be a must, should I focus on the balance and summary of transactions for now?
FYI: I'm hoping to open the PR later today (tonight) 😁

@okjodom I'm not yet well aware of what info would be a must, should I just focus on the balance and summary of transactions for now?
BTW: I'm hoping to open the PR later today (tonight) grin

ATM I'm only keen on seeing the filtering capacity.

gateway-cli info continues to return high level info about all connected federations. Info should include:
    - list of federations.
    - each federation in list should show federation id
gateway-cli info <federation-id> should return detailed info about the federation identified. Info should include:
    - federation id
    - balance held in federation

We will then build out these API further in future. For example, when we build transaction history and accounting within a federation, we might want to show that in the detailed gateway-cli info <federation-id>

Dup of the already fixed #3815.


why there is no sgd-style implementation？

why there is no sgd-style implementation or experiments？
（lemma 1 in the paper)

Hi, @brisker,
The reformulated AGD in Lemma 1 is equivalent to the original AGD (GD with Nesterov momentum). In fact, most SGD implementations, e.g., that in PyTorch,  support the Nesterov-type momentum.
In the experiments, for fairness, we use the timm codebase to compare baselines, which is one of the most widely used codebases to train deep models. To train ResNet50/101, we directly adopt the SGD in timm, which uses Nesterov momentum in default for acceleration.

@XingyuXie
I read the pytorch source code here, but  the implementation there seems different from Lemma 1 in your paper. I can not see the (g_k - g_k-1) formula there, but it is in Lemma 1.

If two algorithms are equivalent, especially if their outputs are the same after convergence, we do not think they will behave very differently in practice. Therefore, we naturally believe that the performance of various AGDs (including SGD with Nesterov momentum) should not differ too much.
If you are interested in the reformulated AGD, we may test its performance on ViT. We have not tried it in practice before, and it is only the intermediate product of derivation.

Back to Adan，why do you add the （g_k-g_k-1) item？ I cannot find specific explaination or motivation in the paper，but in my view，this item seems to be the crucial point of Adan. So I am a little confused by this. （Bsides，why there is only Adan，but no sgd-Adan，which is already discussed above，but still，I wonder if that item also works for sgd.)  @XingyuXie

How to get grad difference $(g_k-g_{k-1})$ is shown in Lemma 1. It is not a heuristic term, and it comes from the reformulation of the classical AGD. You may treat the grad difference as a correction term like the extrapolation in classical AGD or wish it provides higher-order information since the grad difference connects to the local hessian. Bzw, we cannot name the reformulated AGD as sgd-Adan since it is indeed the AGD.
If we remove the grad difference from the reformulated AGD in Lemma 1, it will degenerate to the classical heavy-ball acceleration (HBA). Hence, your question may become Whether AGD is better than HBA?. This is a question that has been discussed for a long time. In theory, AGD seems better in several cases. But in practice, it is hard to choose the winner. For DNN training,  whether to enable Nesterov momentum in SGD depends on the situation. The default choice in Pytorch is False; however, Timm chooses to open it. Bzw, Nesterov momentum is seldom mentioned for the adaptive optimizers.

So， the main contribution of the paper may be ，to include the gradient difference item into adaptive optimizer， which convert Adam into Adan？
in the Nestro implementation  code here ，I can not see the specific grad difference item ，I am a little confused. Is that an approximation？
@XingyuXie

the contribution of Adan may refer to the paper. The comparison between Adan and Adam from theory to practice can be found there.
The grad difference comes from AGD. AGD can be implemented and rewritten in a variety of ways. Not every implementation has the explicit calculation for grad difference—Bzw, how to get the update formula of Nesterov momentum in your link (https://github.com/pytorch/pytorch/blob/master/torch/optim/sgd.py#L241). Please refer to On the importance of initialization and momentum in deep learning.
A large learning rate has many advantages, such as improving generalization and accelerating convergence. A heuristic reason that allows Adan to use a large learning rate is the introduced grad diff in the second-order moment term n_k, which can slow down the update when the grad is not too consistent and accelerate the update when the grad direction is clear.
For more questions about the derivation of Adan rather than code, you may add me by WeChat (xyxie_joy). We may make things more clear by showing more mathematical details.

Hi, @brisker
I found that the Nesterov implementation you mentioned is only equivalent to the original Nesterov momentum method when the objective is quadratic. Otherwise, their implementation is more like classical momentum (a.k.a. heavy-ball method).


Fetching Data from localhost not working

Environment
Kirby Setup:

Kirby Headless Starter
Kirby ^3.9.4
Running locally with PHP 8.0.12 Development Server (I also tried MAMP the error stays the same)
Works on a remote Server

Nuxt Setup:

Nuxt ^3.5.1
Nuxt Kql ^0.26.3

Reproduction
Hey Johann
First – thank you so much for your stellar work!
I'm running into the following problem and I can't track the error:
I try to fetch data with Nuxt3 / nuxt-kql from a locally hosted  kirby-headless-starter backend.
I run Kirby on localhost:8000 using PHP 8.0.12 Development Server.
Describe the bug
It all works fine, with the exact setup, if I deploy the backend to my shared host.
I don't get anything back if I run it locally though.
Additional context
Do you have any ideas what the problem could be?
Many thanks! Samuel
Logs
No response

Can you share your (masked) environment configuration? Are you using IP v4 or v6? Make sure the local backend URL matches your Nuxt configuration.

I'm using IPv4.
Kirby env

Nuxt env

Configuration seems correct. It's probably a misconfiguration on your machine. Since I don't have access, I can't help you any further, unfortunately. You could provide a minimal reproducible examples, tho.
Have you verified the KQL API endpoint is accessible? Please try a POST request via Postman or something like that to: http://localhost:8000/api/kql. No body needed.

Hey Johann! Many thanks for your help. Yes, I guess it must be a misconfiguration on my machine. Just thought I overlooked something. But as I said, it all works fine if I deploy the exact kirby backend to a remote shared host (with new KIRBY_BASE_URL in local frontend) – I also could access http://localhost:8000/api/kql with a POST request via Insomnia and followed the bearer token authentication guide. That all seems to be correct, since otherwise it won't work remote, I guess..

You could provide a minimal reproducible examples, tho.
Not sure how to do that, since it all works fine remote. :-/

Will try it with one of your starter kits.

Sounds like a plan! If you invite me to your repo, I could take a look. Maybe there is something missing code-wise. But due to the limited context provided, I can't help you any further here. Sorry. 🙂


Reactive selector of meteor-tabular never stops “reloading”

I use a simple session variable passed via template helper to tabular tables.
{{> tabular table=TabularTables.Languages selector=languageSelector}}

languageSelector: function () {
    return Session.get('languagesListFilter');
}

The problem is the subscription which is "killed" again and again.

Visually you can see the rows background flickering.
Anybody had the same issue?

So finally it turned out this pull request fixed the bug / problem:
https://github.com/aldeed/meteor-tabular/pull/182/commits
I leave this issue open as it seems to be a bug.


feat: build incoming services

Building of incoming services

[x] Un-archive and build Cargo projects coming in
[x] Create marker files in preparation of loading
[x] Delete old build if any
[x] Unit testing

Marker Files
The work around that C came up with to avoid the fact that linked libraries were not being properly reloaded was to give each new .so file a random name and then use a well-known 'marker file' to indicate the name of the linked library .so file.
Looking at the code of libloading (dependency that handles .so loading for us), the dlopen is likely the cause of the issue. The man pages state:

The cache file /etc/ld.so.cache (maintained by ldconfig(8)) is checked to see whether it contains an entry for filename.

I'm trying to figure out an a way of either not add a library to the cache or otherwise ignore it.
Notes

Possibility of (minor) merge collisions based on changes to error module.
Introduces new dependencies for un-archiving .tar.gz data (flate2 and tar) and for creating random .so file names (rand).

Task linked: CU-2h84xfe Building of incoming services

Many thanks, @chesedo !


Allow users to resend verification emails

We currently store an email_verification_count that isn't used for anything(?)

resolved with 49d8c691cb3f8bdcd822af0f8e076a31f6f35107 and related commits


[BUG] vSphere RKE2 node driver windows cluster with cloud provider enabled fails to bring windows worker node to active state.

Rancher Server Setup

Rancher version: v2.6-head
Installation option (Docker install/Helm Chart): Docker

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc):

Information about the Cluster

Kubernetes version: v1.23.10+rke2r1
Cluster Type (Local/Downstream): Downstream

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): vSphere Node Driver

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom) Admin

Describe the bug

vSphere RKE2 node driver windows cluster with cloud provider enabled fails to bring windows worker node to active state.
To Reproduce

Create a rancher server v2.6-head.
Provision an RKE2 node driver cluster, v1.23.10+rke2r1 with cloud provider enabled to vSphere with following configuration.

1cp - Linux OS (focal-server-cloudimg-amd64 template in data center)
1etcd - Linux OS (focal-server-cloudimg-amd64 template in data center)
1 Worker - Linux OS (focal-server-cloudimg-amd64 template in data center)
1 Worker - Windows (windows-server-2022)

Once the vsphere cloud provider is selected, add CPI-CSI details in Add-On Config in Cluster Configuration.
Once all the details are correctly filled, create a cluster.
Create a deployment along with storage with default PVC.

Result
All the linux nodes come in an active state, except the windows worker node.
However, the deployment with storage get created successfully with default PVC.
Expected Result

Windows worker node should also become active.

note that this was closed, however QA never tested it. So could possibly be a regression: https://github.com/rancher/windows/issues/127

I was unable to reproduce this on v2.6-head

I'm able to reproduce this again on 2.7.11 and 2.8.3-rc2

I believe the root cause of this was due to how we were generating Windows vSphere templates. The templates did not properly utilize cloudbase init when setting the hostname, resulting in the hostname, vm name, and dns name differing on initial provisioning. This caused lookup errors in the CPI and as a result the windows nodes never became available.
I've fixed the templates and uploaded them to the vSphere 8 environment, located in the hostbusters-windows-development-library. We should retest this using those templates to confirm if this is a misconfiguration in our environment or a genuine bug.


Please provide for download

Please provide it for download on https://github.com/nlordell/aseprite-appimage/releases, thank you.

This is not permitted by the Aseprite license.
From the EULA:

You may not distribute copies of the SOFTWARE PRODUCT to third parties.

And from the Aseprite FAQ:

No. From August 2016 you cannot redistribute compiled versions of Aseprite. We have replaced the General Public License (GPLv2) with the new Aseprite EULA. The only way to redistribute Aseprite is with an special educational license.
Anyway this does not restrict most users: You can still compile the source code, and use the program to create your assets for commercial games. You can also make contributions to Aseprite or modify its source code for your personal purposes.

We have replaced the General Public License (GPLv2) with the new Aseprite EULA.

Sorry, I wasn't aware of this. Hope the original author will put out an AppImage.


How HCS and HNS tests are integrated to Windows build process?

I would like to understand that if HCS and HNS integration tests from this project are run as part of Windows build process before new cumulative updates are released?
Based on my ~5 years experience with Windows containers and what I have discussed with other the most problematic part is that over time HNS networks get broken and that each cumulative update needs to be tested very carefully to be sure that they do not break environment.
Example last year there was this very ugly bug on cumulative update which why users was forced to skip half year security patches https://github.com/moby/moby/issues/40998 and looks that there is still one open bug which is waiting for update to Windows https://github.com/moby/moby/issues/41354#issuecomment-810516446
I assume that it would be possible to catch those issues earlier by including more tests here but that does not help unless those tests really run as part of Windows build process.

I can't speak for the HNS tests, but afaik none of the tests in this repo are run as part of windows builds. There are other tests that internal teams have to test out the core functionality of containers, etc and our team validates that our e2e WCOW and LCOW containers with cri-containerd work with new windows updates.
@Keith-Mange for info on HNS and for visibility of the feedback here.

There's also an effort to bring the cri-containerd test suite online for Windows at https://github.com/containerd/containerd/pull/5163. I'm not sure if it covers networking setup though, as I've never looked at the test suite. CRI's network interaction is probably not to the level of HNS testing @olljanat is looking for.


Bootstrap 4 fixes

I wouldn't add the .idea directory to this repository

@bitterdev is this PR still applicable?

I think it probably is – it's true we use Bootstrap 5 in the core but our new Concrete CMS theme used on translate.concretecms.org is still Bootstrap 4


test-manf undefined?

I noticed there are pre-defined ValueSets for the test-manf field, but I don't seem to find a descriptor for those options anywhere. Am I missing something?

So you have the value lists in the DCG*schema.json - and you have the lookup tables here: https://github.com/ehn-digital-green-development/ehn-dgc-schema/blob/main/Lookup-tables/DGC-valueset-lookup.json -- that is not what you are looking for ?

I am looking for descriptors for the numbers below. They don't seem to be defined on the valueset lookup.
 "test-manf": {
      "description": "EU eHealthNetwork: Value Sets for Digital Green Certificates. version 1.0, 2021-04-16, section 2.8",
      "type": "string",
      "enum": [
        "1232",
        "1304",
        "1065",
        "1331",
        "1484",
        "1242",
        "1223",
        "1173",
        "1244",
        "1360",
        "1363",
        "1767",
        "1333",
        "1268",
        "1180",
        "1481",
        "1162",
        "1271",
        "1097",
        "1489",
        "344",
        "345",
        "1218",
        "1343"
      ]
    },

Ah - sorry my bad - I assumed that the values in Lookup-tables/DGC-RAT-lookup.jso were what you where looking for ??
{
  "1232": {
    "display": "Abbott Rapid Diagnostics, Panbio COVID-19 Ag Test",
    "lang": "en",
    "active": true,
    "system": "https://covid-19-diagnostics.jrc.ec.europa.eu/devices",
    "version": "2021-04-22 02:23:55 CET",
    "valueSetId": "covid-19-lab-test-manufacturer-and-name"
  },
  "1304": {
    "display": "AMEDA Labordiagnostik GmbH, AMP Rapid Test SARS-CoV-2 Ag",
    "lang": "en",
    "active": true,
    "system": "https://covid-19-diagnostics.jrc.ec.europa.eu/devices",
    "version": "2021-04-22 02:23:55 CET",
    "valueSetId": "covid-19-lab-test-manufacturer-and-name"
  },

Nice! Thank you!
If you want to see where we are using it: https://github.pathcheck.org/eu.dgc.html

Issue resolved - expanded data information in the appropriate lookup table.


Coordinates: leading zeros or not?

current: E 009° 5.123
I think we should use the leading zeros in a consistend way:
E 9° 5.123
or
E 009° 05.123
What do you think about this?

E 9° 5.123 looks strange to me - i prefer the fixed sized format (with leading zeros)

Leading zeros at GC.com : N 48° 49.345 E 002° 02.512
Leading zeros for minutes (and seconds) but not for degrees at Wikipedia (French) : 51° 28′ 44″ Nord 0° 00′ 38″ Ouesthttps://github.com/cgeo/c-geo-opensource/issues/812/close
I prefer the leading zeros form over the no leading zeros one.

I'm for leading zeros as well to make the output a bit more consistent (and it also resembles the user interface of typical GPS devices more closely).

I'd prefer leading zeros as well and support bullets as seperator.

Some commits ago I removed the pipe completely. I have never seen such a seperator outside of c:geo.


Handle nonexistent repos in gh sponsors, match tidelift in more cases and update return value

So the tests now fail for georgetown-cset/funder-finder because we now have tidelift in our README. :) How do you want to handle this? If we think many funded repos will just mention tidelift in their readme without a link we should keep the current behavior and change the test to another unfunded repo. Or if we think that most funded repos will include a link to tidelift, we could update the string to tidelift.com. Or we could switch over completely to this https://github.com/georgetown-cset/funder-finder/issues/35, although we might lose some repos that way

On the tests failing: Let's keep the current behavior and change the test case. Perhaps another CSET repo?

Nice! Ship it!


Failed to determine version of "something" while parsing a yarn.lock - please report this!

I don't know, where i may report about this. Report here.
yarn.lock.txt

Thanks, this is the right place to report this - I'll have a look tomorrow morning, but in the meantime it would be useful to know more about your project to better understand why your yarn.lock is structured as it is (assuming it's not just invalid).
Could you also confirm that running yarn install doesn't change the lock at all?

before yarn install
please report this.txt
After yarn install no errors found. Sorry for that

@AxetNord good to know, though it looks like this happened because your yarn.lock has properties quoted e.g.:
<EMAIL_ADDRESS>  "integrity" "sha512-Hz/mrNwitNRh/HUAtM/VT/5VH+ygD6DV7mYKZAtHOrbs8U7lvPS6xf7EJKMF0uW1KJCl0H701g3ZGus+muE5vQ=="
  "resolved" "https://registry.npmjs.org/word-wrap/-/word-wrap-1.2.3.tgz"
  "version" "1.2.3"

Instead of:
<EMAIL_ADDRESS>  integrity "sha512-Hz/mrNwitNRh/HUAtM/VT/5VH+ygD6DV7mYKZAtHOrbs8U7lvPS6xf7EJKMF0uW1KJCl0H701g3ZGus+muE5vQ=="
  resolved "https://registry.npmjs.org/word-wrap/-/word-wrap-1.2.3.tgz"
  version "1.2.3"

which is something that should be very easy to support but it would be useful to know how your yarn.lock got like that first - initially I wondered if it was because of the earlier versions of yarn but I've tried all the way back to v0.15.3 with no success.


Variable workspace tensor sizes

Currently, we are unable to do the following:
from salina import Workspace
ws = Workspace()
batch_size = 5
ws.set("obs", 0, torch.zeros(batch_size, 3))
ws.set("obs", 1, torch.zeros(batch_size, 5))

due to
https://github.com/facebookresearch/salina/blob/10d09bb80f78e05ddd7de58e9e24ff0f302877fb/salina/workspace.py#L45
Since tensors from sequential timesteps are stored as lists, I suspect variable-sized features should be possible. This would be immensely useful in multiagent systems as well as recurrent models (e.g. building/expanding a map as the agent explores).

A workspace is storing tensors of size TxBx[...] i.e T timesteps, B.= batch_size and [...] is the size of the information you want to store (for instance [...]=3x28x28 for atari games).  The Workspace.set function is just a way to fill this TxBx[...] tensor over a temporal slice (and possibly to automatically adapt the size of the tensor if this corresponds to a new temporal index). What is the use-case where you want to write tensors of different sizes at different timesteps in the same variable ?
What is the use case that would need to have variable observation sizes ?

Ok, I think I better understand your point in the multiagent case.  If the 'assert' is removed, the problem is that the workspace["obs"] function will not work since it concatenates the list of tensors to return a TxBx[...] tensor. It will have consequences on the RemoteAgent for instances (that are using TxBx[...] tensors in shared memory) and certainly other consequences...
I see two options:

the first one would be to have 'larger' tensors (for instance workspace["obs"} and workspace["obs_size"]) but it will consume more memory
the second one would be to remove the assert, but to take care not to use any method that needs 'full' tensors

I am specifically interested with using graph representations. Unfortunately, a fixed adjacency matrix of say 50,000 by 50,000 takes 10GB of memory, even if mostly empty. Using a fixed-shape torch.sparse_coo_tensor is significantly more efficient, but under the hood it holds variable-length tensors of indices and values.
Perhaps I could create a separate workspace to place these "non-full" tensors, so I could still use full tensor methods elsewhere.

I think other potential reasons for variable-sized tensors could be additional agents coming online or going offline throughout an episode. We could mask them using a fixed-size tensor, but if agents are short-lived or we do not know how many agents we will have ahead of time, then variable-sized tensors could be beneficial.

Ok, the Slice tensor in workspace can handle variable-sized tensors. So the adaptation just needs to prevent the user to merge sliced tensor if there are not composed of tensors of the same size. I put it on the todo list and will try to come back with a solution in the next days. In the meantime,  if you remove the assert, does it works for your use case ?

It currently crashes when removing the assert, but I think with your fix it will be perfect!

Ok, let me take a look by the end of the weed-end

Although variable-sized tensors do not work, it seems everything "just works" with the torch.sparse_coo class! Any variable-length tensor should be realisable as a sparse tensor! For example, we can store the variable length tensor var_len_tens as follows using the dummy idx tensor:
var_len_tens = torch.tensor([1, 4, 9, 16])
idx = torch.tensor([0]).expand(1, var_len_tens.shape[0]) #Expand is zero-copy, so this doesn't take extra memory
torch.sparse_coo_tensor(indices=idx, values=var_len_tens, size=(int(1e10),))

>>> tensor(indices=tensor([[0, 0, 0, 0]]),
       values=tensor([ 1,  4,  9, 16]),
       size=(10000000000,), nnz=4, layout=torch.sparse_coo)

If we modify my original example, the following works without removing the assert:
import torch
from salina import Workspace
ws = Workspace()
batch_size = 5

s0 = torch.sparse_coo_tensor(indices=[[0, 1, 2], [0, 1, 2]], values=[1, 1, 1], size=(batch_size, 1000))
s1 = torch.sparse_coo_tensor(indices=[[3, 4], [3, 4]], values=[2, 2], size=(batch_size, 1000))

ws.set("obs", 0, s0)
ws.set("obs", 1, s1)
ws["obs"]

>>> tensor(indices=tensor([[0, 0, 0, 1, 1],
                       [0, 1, 2, 3, 4],
                       [0, 1, 2, 3, 4]]),
       values=tensor([1, 1, 1, 2, 2]),
       size=(2, 5, 1000), nnz=5, layout=torch.sparse_coo)


Hackathon Work

Most of the work we have done as part of this project.

@hooperben Can you explain what is happening in the PR in its description? It will really help me review it.
Especially because I don't know about Celestia or anything it seems related too. So you also will have to explain what all this about. Sorry :)
Also,, can you rebase and push from the latest commit?


paper trading in sandbox env?

RE: paper trading in sandbox env?
There seems to be a sandbox env for api, how can we make use of it to paper trade? or at least test out the API before live trading?
https://developer.schwab.com/user-guides/apis-and-apps/test-in-sandbox

I have heard of the sandbox enviroment. But I believe it refers to the testing that you can perform on the website: "Sandbox testing provides visibility of inputs/outputs, or requests/responses, of data for each call. The data is rendered and persists within this module's UI until the next call is run. " And I don't think that the sandbox can be used for paper trading.
I have, however, been considering several approaches to a paper trading capable client.

You could email them and ask


libdaisy submodule 404 error

The libdaisy submodule points to a non-accessible Github URL: https://github.com/andrewikenberry/ES_libdaisy/ - thus the builds are failing.

@ggsubs the libdaisy repo is going to be going live very shortly.
I'll comment again when its live!

Alright! @ggsubs
the link to libdaisy has been fixed, and the repo is live!
Should be good to go! (The blink example mentioned in the Wiki's Getting Started section is also now in this repo in case you were following along with that guide).


Automated cherry pick of #2730: Fix panic bug in Antrea Policy

Cherry pick of #2730 on release-1.3.
#2730: Fix panic bug in Antrea Policy
For details on the cherry pick process, see the cherry pick requests page.

Codecov Report

Merging #2757 (974f4d8) into release-1.3 (62e25bf) will decrease coverage by 18.00%.
The diff coverage is 70.00%.

@@               Coverage Diff                @@
##           release-1.3    #2757       +/-   ##
================================================
- Coverage        59.35%   41.35%   -18.01%
================================================
  Files              285      158      -127
  Lines            23029    19274     -3755
================================================
- Hits             13670     7971     -5699
- Misses            7899    10553     +2654
+ Partials          1460      750      -710

Flag
Coverage Δ

kind-e2e-tests
?

unit-tests
41.35% <70.00%> (+0.36%)
:arrow_up:

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


Feature: Import & export friends list

I have created a feature for exporting and importing the list of friends.
This should be helpful in cases where people work in the same company and have similar friends.
This was also requested in #1
I opened it as a draft so we could discuss the feature and change things if needed.

Hi, great PR, I forked and adjusted the extension to recent Cibus and Wolt changes, and cherry-picked your change.
The fork:

https://github.com/michael-maltsev/cibusplitter-reborn
https://chromewebstore.google.com/detail/cibusplitter-reborn/pilnigkcdmgdadikndefiainijkegojn

One thing that I noticed is that if you cancel the import prompt, it wipes the friends list. I fixed it.


Kibana is not available via proxy

I have followed documentation on https://microk8s.io/docs/addon-fluentd, but Kibana is not working via proxy with default configuration. The error is the following:

Inspection Report
inspection-report-20210620_142636.tar.gz

@s12v as mentioned in your PR we updated the docs to reflect the change in the way to access kibana.
Setting SERVER_BASEPATH seems to allow us to access the kibana dashboard via kubectl proxy but not with port forwarding.
Thank you for reporting this and giving us the opportunity to clarify this point.


[SPARK-37203][SQL] Fix NotSerializableException when observe with percentile_approx

What changes were proposed in this pull request?
Currently,
val namedObservation = Observation("named")

val df = spark.range(100)
val observed_df = df.observe(
   namedObservation, percentile_approx($"id", lit(0.5), lit(100)).as("percentile_approx_val"))

observed_df.collect()
namedObservation.get

throws exception as follows:
15:16:27.994 ERROR org.apache.spark.util.Utils: Exception encountered
java.io.NotSerializableException: org.apache.spark.sql.catalyst.expressions.aggregate.ApproximatePercentile$PercentileDigest
	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
	at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
	at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
	at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
	at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1378)
	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174)
	at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
	at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
	at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
	at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
	at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
	at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
	at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
	at org.apache.spark.scheduler.DirectTaskResult.$anonfun$writeExternal$2(TaskResult.scala:55)
	at org.apache.spark.scheduler.DirectTaskResult.$anonfun$writeExternal$2$adapted(TaskResult.scala:55)
	at scala.collection.Iterator.foreach(Iterator.scala:943)
	at scala.collection.Iterator.foreach$(Iterator.scala:943)
	at scala.collection.AbstractIterator.foreach(Iterator.scala:1431)
	at scala.collection.IterableLike.foreach(IterableLike.scala:74)
	at scala.collection.IterableLike.foreach$(IterableLike.scala:73)
	at scala.collection.AbstractIterable.foreach(Iterable.scala:56)
	at org.apache.spark.scheduler.DirectTaskResult.$anonfun$writeExternal$1(TaskResult.scala:55)
	at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:23)
	at org.apache.spark.util.Utils$.tryOrIOException(Utils.scala:1434)
	at org.apache.spark.scheduler.DirectTaskResult.writeExternal(TaskResult.scala:51)
	at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1459)
	at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1430)
	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
	at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
	at org.apache.spark.serializer.JavaSerializationStream.writeObject(JavaSerializer.scala:44)
	at org.apache.spark.serializer.JavaSerializerInstance.serialize(JavaSerializer.scala:101)
	at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:616)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

This PR will fix the issue.
Why are the changes needed?
Fix NotSerializableException when observe with percentile_approx.
Does this PR introduce any user-facing change?
Yes. PercentileDigest extends Serializable.
How was this patch tested?
New tests.

Test build #144873 has started for PR 34474 at commit 1eacf82.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49343/

Test build #144875 has started for PR 34474 at commit a2f1fbb.

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49343/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49345/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49343/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49345/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49345/

Test build #144873 has finished for PR 34474 at commit 1eacf82.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/144873/

Test build #144875 has finished for PR 34474 at commit a2f1fbb.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/144875/

Looking at the implementation, it's never meant to be serialized by Java or Kryo, but is serialized 'manually' and internally by Spark. I think it must be related to observe() here, that somehow this object gets caught up in what is returned? I don't know a lot about observe().
It's possible the answer is that observe() should do something different, but not sure.
We can make this Serializable, but then need to implement methods for the Java serializer that would reuse the existing serializer code. That seems plausible.

Test build #144898 has started for PR 34474 at commit 6c2f71c.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49368/

Test build #144899 has started for PR 34474 at commit 84f9657.

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49368/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49368/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49369/

Test build #144898 has finished for PR 34474 at commit 6c2f71c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49369/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/144898/

Test build #144903 has started for PR 34474 at commit 5e7afac.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49373/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49373/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49373/

Test build #144899 has finished for PR 34474 at commit 84f9657.

This patch fails from timeout after a configured wait of 500m.
This patch merges cleanly.
This patch adds no public classes.

Test build #144903 has finished for PR 34474 at commit 5e7afac.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/144899/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/144903/

Test build #144913 has started for PR 34474 at commit acddbf3.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49384/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49384/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49384/

Test build #144913 has finished for PR 34474 at commit acddbf3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/144913/

@beliefer can you update the PR description? Yes. PercentileDigest extends Serializable. this is wrong now.

@beliefer can you update the PR description? Yes. PercentileDigest extends Serializable. this is wrong now.

OK

Yes. This PR let AggregatingAccumulator uses serialize and deserialize of TypedImperativeAggregate.

Is it a user-facing change?

Yes. This PR let AggregatingAccumulator uses serialize and deserialize of TypedImperativeAggregate.

Is it a user-facing change?

No

@cloud-fan Thanks for your hard work！@srowen @MaxGekk @hvanhovell ， thank you for review.

thanks, merging to master/3.2/3.1!


can i transform docs to chinese and publish a website for chinese developers ?

i like ionic very much and i want more chinese developers use it,can i transform docs to chinese and publish a website for chinese developers?

i can help with you
make a pull request for ionic-website repository.
the doc files are in there


occasional error on ikea remote device, missing null

Problem from #110 still continues.
Log message says:
[error] TypeError: Cannot read property 'replace' of null
at MqttSubscription.callback (/data/node_modules/node-red-contrib-zigbee2mqtt-devices/dist/nodes/devices-ikea.js:90:51)

so, in your last fix missing null in condition:
if (message.action === undefined || message.action === "") {
https://github.com/Dirnei/node-red-contrib-zigbee2mqtt-devices/blob/0.19.3/src/nodes/devices-ikea.js#L85

Published a new release right now! Should be available for update in node-red soon! Thanks again for your help :)

Published a new release right now! Should be available for update in node-red soon! Thanks again for your help :)


Cross compile tries to compile module with unsupported Scala version

steps
sbt version: 1.2.8, 1.3.0-RC2
I've created minimalistic project to demostrate the issue:
https://gist.github.com/limansky/eb8f2917245abd69e7904665f6a8fdf5

run sbt
++2.11.12 -v
verify that moduleB is excluded because it doesn't support Scala 2.11
compile

problem
sbt tries to resolve dependencies for moduleB and to download core_2.12-0.1-SNAPSHOT
expectation
I expect that it do nothing with moduleB since it doesn't support specified Scala version.

I think this is an expected behavior.
You'd either have to do ++2.11.12 compile or +compile, I think.

@eed3si9n  ++2.11.12 compile works fine. Only thing I had to change, since I'd like to pass it as a parameter, is to put it into quotes like `sbt "++2.11.12 compile". Thanks.
BTW, what is the difference between ++2.11.12 compile and ++2.11.12 and then compile?

What I'm trying to achieve is to have different sub-builds in Travis for different Scala versions. This is the script I'm using: https://github.com/limansky/mongoquery/blob/master/scripts/travis-build.sh , and now, I'm not sure if the script is fine.


Updated documentation with new message, medias and polls specifications

Description
Updated docs with new MsgAnswerPoll description and specs and with medias and polls specs.
Also fixed some small bugs around docs.
Checklist

[x] Targeted PR against correct branch.
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote unit tests.
[ ] Wrote integration tests (simulation & CLI).
[x] Updated the documentation.
[ ] Added an entry to the CHANGELOG.md file.
[x] Re-reviewed Files changed in the Github PR explorer.

Codecov Report

Merging #95 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #95   +/-   ##
=======================================
  Coverage   75.14%   75.14%
=======================================
  Files          25       25
  Lines        1344     1344
=======================================
  Hits         1010     1010
  Misses        312      312
  Partials       22       22

Impacted Files
Coverage Δ

x/posts/internal/types/post_media.go
85.71% <ø> (ø)
:arrow_up:

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 f461a22...e898d58. Read the comment docs.


3.4.0

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_1ezbmmp2b8/clone/recipe/meta.yaml:10: missing_hash: The recipe is missing a sha256 checksum for a source file
ERROR: /tmp/abs_1ezbmmp2b8/clone/recipe/meta.yaml:28: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
ERROR: /tmp/abs_1ezbmmp2b8/clone/recipe/meta.yaml:28: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
ERROR: /tmp/abs_1ezbmmp2b8/clone/recipe/meta.yaml:34: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, closest match: MTLL
WARNING: /tmp/abs_1ezbmmp2b8/clone/recipe/meta.yaml:918: missing_license_file: The recipe is missing the about/license_file or about/license_url key.
ERROR: /tmp/abs_1ezbmmp2b8/clone/recipe/meta.yaml:918: http_url: http://eigen.tuxfamily.org/ is not https
Errors were found


Adapt to API changes in gurobipy

Description
APIs for adding constraints has changed with gurobipy version 10, this PR has the necessary updates.  Also I removed references to a non-documented API in gurobipy version 8.1.1, which is no longer supported.
Type of change

[ ] New feature (backwards compatible)
[ ] New feature (breaking API changes)
[ ] Bug fix
[x] Other (Documentation, CI, ...)

Contribution checklist

[ ] Add our license to new files.
[x] Check that your code adheres to our coding style.
[ ] Write unittests.
[x] Run the unittests and check that they’re passing.
[x] Run the benchmarks to make sure your change doesn’t introduce a regression.

LGTM. I will backport to 1.1 and 1.2 as well.


backup deletes files before uploading them onto dropbox

[2012/01/24 01:04:54][warning] [DEPRECATED] Backup::Storage::Dropbox.timeout=
[2012/01/24 01:04:54][warning]   is deprecated and will be removed at some point.
[2012/01/24 01:04:54][message] Performing Backup for 'Description for database (database)'!
[2012/01/24 01:04:54][message] [ backup 3.0.21 : ruby 1.8.7 (2009-06-12 patchlevel 174) [x86_64-linux] ]
[2012/01/24 01:04:54][message] Database::MySQL started dumping and archiving 'dbase'.
[2012/01/24 01:04:54][message] Using Compressor::Gzip for compression.
[2012/01/24 01:04:55][message] Packaging the backup files...
[2012/01/24 01:04:55][message] Using Encryptor::GPG to encrypt the archive.
[2012/01/24 01:04:55][message] Splitter configured with a chunk size of 250MB.
[2012/01/24 01:04:55][message] Packaging Complete!
[2012/01/24 01:04:55][message] Cleaning up the temporary files...
[2012/01/24 01:04:55][message] Storage::Dropbox started transferring '2<IP_ADDRESS>.04.54.database.tar.gpg'.
[2012/01/24 01:04:55][error] ModelError: Backup for Description for database (database) Failed!
[2012/01/24 01:04:55][error]   An Error occured which has caused this Backup to abort before completion.
[2012/01/24 01:04:55][error]   Reason: Errno::ENOENT
[2012/01/24 01:04:55][error]   No such file or directory - /root/Backup/.tmp/2<IP_ADDRESS>.04.54.database.tar.gpg

Well, it not deleting the file in question before it's transferred. The Packaging stage creates the 2<IP_ADDRESS>.04.54.database.tar.gpg file by tar-ing the .tmp/database directory. It's this directory that's being removed after Packaging is complete.
So, what is apparently happening is the packaging is failing, but the command is not returning a non-zero exit status and causing an error. Try removing (commenting out) your Encryptor from your backup model and see if you get an unencrypted tar file transferred. The encryption portion of the packaging command is the only thing I can think would be failing. If you can figure out why it's failing, I'd like to know, since it really should be causing a packaging failure.
Are you able to manually encrypt files with your key? Does gpg --list-keys look ok? You'll have to investigate this a little, since this would probably be difficult to attempt to duplicate :)

You are right, it's gpg exitting with 0 but not encrypting anything, I was able to upload an unencrypted archive to dropbox without issues!! Thanks !


A better name?

Maybe even something that doesn't contain "term" ?  ;)

tic
stic
stuc
xtic   - could be read as "exotic", with some motivation :)


Prepare 3.0 version

PHP 8+ : large use of new PHP 8 features and functions
Bump dependencies
Refactor tag constructors : refactor tag constructors to avoid unsafe instantiations. Now Psalm analysis is green at level 1 (the more strict level)
Refactor TagFactory : now, to add a new tag it's enough to create the class and put it into src/tags directory
Documentation Api : remove the script to create the documentation api locally, since sami does not support PHP 8. Add a Github Actions workflow to create and deploy it into the repository Github Pages (@gossi please, add a personal token to this repository secrets, called DOCBLOCK_TOKEN, to allow the deployment)
Update tags docblock comments : update tags comments and link to the official references, to correctly create the documentation api

I added the token, hope that was the correct one.

About the api generation workflow: imho it could be better to trigger it when publishing a new release, instead of when push on master branch. What do you think about?

yeah, makes sense.


problem with show services in client reception. history forms

            {% for i in filter.form.service.field.queryset %}

should use filter.


Possibility of using Cython?

Earlier I did a proof of concept wrapper for hecdss with Cython which allowed much tighter integration. repository link is given below

https://github.com/nzahasan/pyheclib

@ktarbet if you are interested in this I might be able to assist in this regard.

Thanks @nzahasan for sharing your repository!
@jeffsuperglide has also been testing hec-dss with Cython.
One goal of this hec-dss-python test - is to use the new hecdss.dll and API   https://github.com/HydrologicEngineeringCenter/hec-dss/blob/master/heclib/hecdss/hecdss.c (as a layer between potential future implementations of DSS).   Perhaps Cython would be easier.   I do like that the Ctypes is loosely coupled to DSS, nothing needs to be compiled, and doesn't seem to be tied to specific python versions.

I tried one experiment with SWIG https://github.com/swig/swig .  It looks powerful.

if we can read time-series data as pandas dataframe/numpy array it would be a good user experience for this I am really inclined to use Cython.

Thanks again for your feedback!    Yes, we need to provide some support for pandas/numpy.
Here are some design ideas below; from the updated readme.

Feature
What
Why

hecdss.dll/libhecdss.so
cross platform (Linux,Windows,Mac), cross language (.net, Python, Java)  essential API
decouple from underlying HEC-DSS Fortran/C Library  (allow future DSS versions without C and Fortran backend)

Support only DSS 7
encourage migration from version 6
HEC is moving to DSS version 7 in 2023-2024.

Easy transition from Jython
HEC products use an existing Java/Jython API.  We will loosely follow that design
simplify porting from Jython

hec_dss_native.py
native binding layer
isolate interactions with low level library(if performance is an issue this Ctypes layer can be replaced )

hec_dss.py
Programmer entry point ; Python API
Hides interactions with hec_dss_native, seek to be simple user experience

Pandas_Series_Utilities.py future
NumPy/pandas support
provide features such as dataframes, separate from hec-dss.py; can be developed by different/parallel developers

Easy to get started
nothing to install, just copy python files and shared library
require minimal privileges to install


This PR is to resolve [TB] Add pre-commit hook to enforce prettier, linting #960

ABOUT:
This pull request is created to add the pre-push hook to enforce prettier,linting.
Discussion:
As discussed in #960 Instead of pre-commit hook pre-push hook is added in this PR.
Husky along with lint-staged, prettier, and eslint is implemented such that the staged files are  formatted using prettier and eslint fails only in the case of error not on warnings.
It is implemented whenever the developer push to the repository.

@aaronreed708 please check this solution i provided for the issue #960  and thank you very much for giving an opportunity to contribute in this repository.

@budhathokipramin First, thank you for your contribution!  But am I missing something here?  When I try out this code, it doesn't work.  It doesn't fix non-pretty code nor lint at all on a push.  I believe that this is because pre-push is using lint-staged which only looks at staged files.  When pushing code, there are no staged files so I believe that it just ignores and continues.
Please let me know if I'm not understanding something correctly.  Also, I'm sorry that it took me this long to review your code.  If you ever feel that you are waiting too long for a review, feel free to ping me in the PR or on Slack to give me a nudge.  Thanks!

@aaronreed708 i will fix it and reply to you.

@aaronreed708 i have fixed the pre-push hook as discussed in the meeting. Please feel free to review the changes to the #960 solution. Note: The last commit was done automatically after the push was done to the dev branch.

@aaronreed708 pinging you so that you check this update. Thank You.

Hi @budhathokipramin!  So I tried this out on Friday and again on Saturday.  I seem to be breaking still in the no-upstream scenario.  If I run the script from the command line, it seems to process correctly.  However, when this script runs when I am trying to push, I get an error 128.  When I add some debugging to the script, it seems to be failing because there is no upstream branch.  And this error occurs when the script is trying to determine if there is an upstream branch.
I wonder if we could maybe not test if there is an upstream branch but rather test if this branch is specifically in the finos/a11y-theme-builder repo?  If I get some time early this week I'll try that out here locally.

@budhathokipramin also, please fix conflicts.  Looks like you probably need to update your dev branch.  Thanks!


Simplify Dagger setup

Use delegate modules and Dagger dependencies instead of delegating each method manually

This PR was released with 0.22.1


Single status update doesn't work on Bulk status update flag

Describe the bug
Single status update doesn't work on Bulk status update flag

Part of #8811


position: fixed + overflow:hidden causing issue

With the recent changes in PR #68 where position: fixed  was added alongside the calculation to negative margin (top) of the page to prevent jumping.
The issue I'm facing is with position: fixed where on browser. This would happen.

before modal opens

after modal opens
As you can see the <body> element which i'm highlighting doesn't take the full width of the page unless I add left: 0; right: 0; to the class .tingle-enabled
Secondly, with the existing overflow:hidden rule set with the new changes to adding top: -(margin) the content outside of the body's height will get clipped off as I've illustrated in my screenshot.

before modal opens

after modal opens. the content dissappears.
I understand it is because of overflow: hidden because if I switch it to overflow: visible it would work. but may cause problems that I've yet to run into.
Also I know this issues doesn't occur on the demo site so I'm just wondering if there's a way around this. Cheers!
Thoughts? @robinparisi @Shurelia

Hi @xavianaxw,
Could you post a link to a demo and specify which browser version you're using?

https://xavianaxw.github.io/shopify/
Here is a demo site.
I'm currently on Google Chrome Version 63.0.3239.132 (Official Build) (64-bit) and I'm working on  MacOS High Sierra v10.13.3

It's because when the modal is opened and tingle-enabled is added to the <body> element, the dimensions of <body> would be 1024px x (height of screen)
For example if the page height is 800px. Everything below 800px of the page gets hidden because of overflow:hidden on the <body> element.
You can replicate this easily by scrolling down pass the top banner / hero area.
Cheers

Ok, I've got it now. The problem is that @Shurelia did theses changes in order to fix a problem on iOS and since I do not have any iOS device, it's difficult for me to test this part.

But I noticed the changes does not affect the demo site?

@xavianaxw Working on it, I will release a new version as soon as possible.

awesome! Hope to hear the good news soon!

@xavianaxw I just release a new version.
On your demo, you're using overflow-y: scroll on the html element and it's because of this your content has been cut off. By removing height: auto, it seems that the calculated height is better handled.
I also added left: 0 and right: 0 to properly manage the width.


Upgrade to latest DataFusion

I pushed another commit now that the type coercion rule has been merged into DataFusion, so we can delete our copy.


Complete rewrite

Resolves #18

I think this is as far as I want ot get just now. Comments welcome.

Remaining non-critical issues

non-default fonts in SVG output will lead to an error because MathJax will still load the TeX fontdata (and fail). Not problematic but annoying.
TeX input \require throws processing errors (but the macros from an extension work fine)

Critical issues

MathML+SVG is broken.

MathML+SVG is broken.

The main problem is in the order of the font files.  You need to load the Main.js file before any of the other ones for a particular font family.  For example, you currently have
            '/jax/output/SVG/fonts/TeX/Typewriter/Regular/BasicLatin.js',
            '/jax/output/SVG/fonts/TeX/Typewriter/Regular/CombDiacritMarks.js',
            '/jax/output/SVG/fonts/TeX/Typewriter/Regular/Main.js',
            '/jax/output/SVG/fonts/TeX/Typewriter/Regular/Other.js'

but it should be
            '/jax/output/SVG/fonts/TeX/Typewriter/Regular/Main.js',
            '/jax/output/SVG/fonts/TeX/Typewriter/Regular/BasicLatin.js',
            '/jax/output/SVG/fonts/TeX/Typewriter/Regular/CombDiacritMarks.js',
            '/jax/output/SVG/fonts/TeX/Typewriter/Regular/Other.js'

(indeed, you cold move all the Main.js files to the top of the list if you wanted).
There is a second issue, which is that the fontdata.js itself, already includes a number of the Main.js files, so loading them again overwrites the data already there, and that can cause problems.  In the case of SVG with TeX, the two are
        '/jax/output/SVG/fonts/TeX/Main/Regular/Main.js',

and
        '/jax/output/SVG/fonts/TeX/Math/Italic/Main.js',

so these should be removed from the list.  Which files are included varies from font to font (and output jax to output jax), so you will need to look to see which ones are int he fontdata.js files for the different fonts.  You can recognize these based on the presence of lines such as
  SVG.FONTDATA.FONTS['MathJax_Main'] = {
    directory: 'Main/Regular',

for the TeX/Main/Regular/Main.js file.
Note that for HTML-CSS STIX, the only Integral font used is IntegralD, so no need to load the other versions (SM, Up, etc).

Thanks so much, Davide!

so you will need to look to see which ones are in the fontdata.js files for the different fonts.

FWIW, I didn't find any other fontdata.js files (using SVG.FONTDATA.FONTS\['(.*)'\] = \{ to find them).

It looks like the other web fonts for SVG don't pre-include any of the data (like the hand-made ones for STIX and MathJax TeX fonts).  But the CommonHTML and HTML-CSS output jax do have preloaded ones for their MathJax TeX and STIX fonts.  (Substitute CHTML or HTMLCSS for the SVG.)

Thanks! I'll take another look.

For the time being, I think this is ready to go.


Consider removing ~/resources audience from access tokens

and add flag to add it back in for legacy scenarios

yes please, so i was in a middle of migrating from spring framwork Oauth2 to IS4 (java to .net)
in the spring framework version looks like they have remove all the Nbf,Aud, iss etc
but i could not find a setting to hide those value, could you please consider this?
thank  you!

I stumbled on this issue after wondering why this audience was on my client_credentials token all the time.
It got me curious, so if it's not much trouble to answer: in what scenarios is this audience useful?
Feel free to direct me to some documentation if this should be obvious.

It's a legacy/migration feature from IdentityServer3.

I gather that it's superfluous for a from-scratch deployment using IdentityServer4, then?
If so, 👍

yea, in short you can ignore it

You only use the aud(ience) when your OP is creating an ID Token that is targeted to a particular audience, like, for example, one particular client.

Sure, I know what the aud value in the token is for.
But this particular audience (~/resources) seems to be included in all tokens, despite what scope I request from the auth server-- It's why I was lead to this issue. If it's a holdover from older implementations, I'm satisfied.

@brockallen
I would like IdSrv4 to omit this audience, too. Even more than that - I'm investigating which changes are needed to accomplish this here
Just to double-check: Are you sure it's necessary to introduce the flag and extra conditional statements in order to remain backwards-compatible in this case. As you said before, the /userinfo endpoint can validate the issuer and who else would expect this audience to be present?
The reason I'm asking is, just in general, I would prefer to avoid these extra conditionals whenever possible to keep the code simpler/cleaner.
Thank you

Could somebody merge @tspringr changes? I don't want to sign CLA so even can't create merge request.

OK. Done for 3.0


Example for general testing Steps

For on-boarding new project members, detailed steps in a MR/PR description on how to test a new feature are pretty useful. They should describe how someone with hardly any prior knowledge can execute and verify the new feature.
Example:

pull the branch xyz
execute the following command via CLI: foo bar
the following should happen: asdfqwerty

A real world example from the TIDO project: https://gitlab.gwdg.de/subugoe/emo/tido/-/merge_requests/130#tests.

@paulpestov Is there something missing? :)

Seems ok to me in general. The question is whether its possible to perform local testing of the changes in a reasonable way.

@mweidling can you implement the templates please?

@krvoigt Sure. I wasn't aware that this issue has been considered as "reviewed and accepted".

@krvoigt Can this ticket be closed? I added a "Tests" section to the PR template.

See https://github.com/OCR-D/zenhub/commit/f6dce6f699b29b8073e97f10bf87e122ba8104e2.

@kba @krvoigt Since I've provided the examples I'll remove myself from the list of assignees. Feel free to re-add my if there's something I could/should do.


crash in case regenerating spritesheet

In spritesheet.js, there is a confused variable called 'sprite'
One is
6	sprite = require('node-sprite')
108	sprite.sprite(sheetName, spriteOptions, function(err, globalSprite) {

The other is
121	sprite = lodash.find(sprites, {filename: filename})

One of the two should be renamed.
Thanks for your contribution.

Fixed and published<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS>--save


feat: add numericpattern143.cpp

Pattern required:

Solution:

Do mention the issue number in all future PRs so I can easily close those issue whose PRs are successfully merged. I will review the code and merge soon


What do we need to make this work with Windows?

I could dedicate some of my time to try to implement what is needed to make this work on Windows as well, I just want to know if there are any technical limitations on why this extension doesn't support it or if it simply wasn't implemented.

Sorry, I realized I didn't even test the extension before creating this issue.
The description says it works only on macOS but it works perfectly fine on Windows too.
I am closing this.
Side note: does it work with Linux though? ;)

fixed the documentation here c861fe0


blog linked

linked blog to the main page and also fixed the home link in blog file to link it with index.html(main page)

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


The show_result_pyplot() function using the newer version of MMdet has missing parameters.

Hello, dear developers. I have a pressing problem now.I am a beginner in this field, and I have the following problems when running demo:
The following are tips：
E:\Coding\workbench\test14\mmdetection\mmdet\models\builder.py:50: UserWarning: train_cfg and test_cfg is deprecated, please specify them in model
  warnings.warn(
E:\Coding\PyEnv\test14\lib\site-packages\mmcv\utils\misc.py:333: UserWarning: "out_size" is deprecated in `RoIAlign.__init__`, please use "output_size" instead
  warnings.warn(
E:\Coding\PyEnv\test14\lib\site-packages\mmcv\utils\misc.py:333: UserWarning: "sample_num" is deprecated in `RoIAlign.__init__`, please use "sampling_ratio" instead
  warnings.warn(

load checkpoint from local path: epoch_36.pth
The model and loaded state dict do not match exactly

unexpected key in source state_dict: bbox_head.0.fc_cls.weight, bbox_head.0.fc_cls.bias, bbox_head.0.fc_reg.weight, bbox_head.0.fc_reg.bias, bbox_head.0.shared_fcs.0.weight, bbox_head.0.shared_fcs.0.bias, bbox_head.0.shared_fcs.1.weight, bbox_head.0.shared_fcs.1.bias, bbox_head.1.fc_cls.weight, bbox_head.1.fc_cls.bias, bbox_head.1.fc_reg.weight, bbox_head.1.fc_reg.bias, bbox_head.1.shared_fcs.0.weight, bbox_head.1.shared_fcs.0.bias, bbox_head.1.shared_fcs.1.weight, bbox_head.1.shared_fcs.1.bias, bbox_head.2.fc_cls.weight, bbox_head.2.fc_cls.bias, bbox_head.2.fc_reg.weight, bbox_head.2.fc_reg.bias, bbox_head.2.shared_fcs.0.weight, bbox_head.2.shared_fcs.0.bias, bbox_head.2.shared_fcs.1.weight, bbox_head.2.shared_fcs.1.bias, mask_head.0.convs.0.conv.weight, mask_head.0.convs.0.conv.bias, mask_head.0.convs.1.conv.weight, mask_head.0.convs.1.conv.bias, mask_head.0.convs.2.conv.weight, mask_head.0.convs.2.conv.bias, mask_head.0.convs.3.conv.weight, mask_head.0.convs.3.conv.bias, mask_head.0.upsample.weight, mask_head.0.upsample.bias, mask_head.0.conv_logits.weight, mask_head.0.conv_logits.bias, mask_head.1.convs.0.conv.weight, mask_head.1.convs.0.conv.bias, mask_head.1.convs.1.conv.weight, mask_head.1.convs.1.conv.bias, mask_head.1.convs.2.conv.weight, mask_head.1.convs.2.conv.bias, mask_head.1.convs.3.conv.weight, mask_head.1.convs.3.conv.bias, mask_head.1.upsample.weight, mask_head.1.upsample.bias, mask_head.1.conv_logits.weight, mask_head.1.conv_logits.bias, mask_head.2.convs.0.conv.weight, mask_head.2.convs.0.conv.bias, mask_head.2.convs.1.conv.weight, mask_head.2.convs.1.conv.bias, mask_head.2.convs.2.conv.weight, mask_head.2.convs.2.conv.bias, mask_head.2.convs.3.conv.weight, mask_head.2.convs.3.conv.bias, mask_head.2.upsample.weight, mask_head.2.upsample.bias, mask_head.2.conv_logits.weight, mask_head.2.conv_logits.bias

missing keys in source state_dict: roi_head.bbox_head.0.fc_cls.weight, roi_head.bbox_head.0.fc_cls.bias, roi_head.bbox_head.0.fc_reg.weight, roi_head.bbox_head.0.fc_reg.bias, roi_head.bbox_head.0.shared_fcs.0.weight, roi_head.bbox_head.0.shared_fcs.0.bias, roi_head.bbox_head.0.shared_fcs.1.weight, roi_head.bbox_head.0.shared_fcs.1.bias, roi_head.bbox_head.1.fc_cls.weight, roi_head.bbox_head.1.fc_cls.bias, roi_head.bbox_head.1.fc_reg.weight, roi_head.bbox_head.1.fc_reg.bias, roi_head.bbox_head.1.shared_fcs.0.weight, roi_head.bbox_head.1.shared_fcs.0.bias, roi_head.bbox_head.1.shared_fcs.1.weight, roi_head.bbox_head.1.shared_fcs.1.bias, roi_head.bbox_head.2.fc_cls.weight, roi_head.bbox_head.2.fc_cls.bias, roi_head.bbox_head.2.fc_reg.weight, roi_head.bbox_head.2.fc_reg.bias, roi_head.bbox_head.2.shared_fcs.0.weight, roi_head.bbox_head.2.shared_fcs.0.bias, roi_head.bbox_head.2.shared_fcs.1.weight, roi_head.bbox_head.2.shared_fcs.1.bias, roi_head.mask_head.0.convs.0.conv.weight, roi_head.mask_head.0.convs.0.conv.bias, roi_head.mask_head.0.convs.1.conv.weight, roi_head.mask_head.0.convs.1.conv.bias, roi_head.mask_head.0.convs.2.conv.weight, roi_head.mask_head.0.convs.2.conv.bias, roi_head.mask_head.0.convs.3.conv.weight, roi_head.mask_head.0.convs.3.conv.bias, roi_head.mask_head.0.upsample.weight, roi_head.mask_head.0.upsample.bias, roi_head.mask_head.0.conv_logits.weight, roi_head.mask_head.0.conv_logits.bias, roi_head.mask_head.1.convs.0.conv.weight, roi_head.mask_head.1.convs.0.conv.bias, roi_head.mask_head.1.convs.1.conv.weight, roi_head.mask_head.1.convs.1.conv.bias, roi_head.mask_head.1.convs.2.conv.weight, roi_head.mask_head.1.convs.2.conv.bias, roi_head.mask_head.1.convs.3.conv.weight, roi_head.mask_head.1.convs.3.conv.bias, roi_head.mask_head.1.upsample.weight, roi_head.mask_head.1.upsample.bias, roi_head.mask_head.1.conv_logits.weight, roi_head.mask_head.1.conv_logits.bias, roi_head.mask_head.2.convs.0.conv.weight, roi_head.mask_head.2.convs.0.conv.bias, roi_head.mask_head.2.convs.1.conv.weight, roi_head.mask_head.2.convs.1.conv.bias, roi_head.mask_head.2.convs.2.conv.weight, roi_head.mask_head.2.convs.2.conv.bias, roi_head.mask_head.2.convs.3.conv.weight, roi_head.mask_head.2.convs.3.conv.bias, roi_head.mask_head.2.upsample.weight, roi_head.mask_head.2.upsample.bias, roi_head.mask_head.2.conv_logits.weight, roi_head.mask_head.2.conv_logits.bias

E:\Coding\workbench\test14\mmdetection\mmdet\datasets\utils.py:64: UserWarning: "ImageToTensor" pipeline is replaced by "DefaultFormatBundle" for batch inference. It is recommended to manually replace it in the test data pipeline in your config file.
  warnings.warn(
E:\Coding\PyEnv\test14\lib\site-packages\torch\nn\functional.py:2970: UserWarning: Default upsampling behavior when mode=bilinear is changed to align_corners=False since 0.4.0. Please specify align_corners=True if the old behavior is desired. See the documentation of nn.Upsample for details.
  warnings.warn("Default upsampling behavior when mode={} is changed "
E:\Coding\workbench\test14\mmdetection\mmdet\models\dense_heads\rpn_head.py:191: UserWarning: In rpn_proposal or test_cfg, nms_thr has been moved to a dict named nms as iou_threshold, max_num has been renamed as max_per_img, name of original arguments and the way to specify iou_threshold of NMS will be deprecated.
  warnings.warn(

The displayed result is the original image.
After querying the data and browsing the code of the display result function, I found that the show_result_pyplot() function in MMDetection 1.2.0/MMDET/APIs/Influence.py used in master has a class_names parameter, but the mmdetection2.12.0 I used does not have this parameter. I don't know what to do next to make the demo display the correct result. It may not be just the problem of this function, but the pre-training model uses the specified epoch_36.pth. ..
I hope you can take the time to guide me.
The following is my configuration environment：
PC:windows11
mmdetection:v2.12.0
mmvc:1.4.0
torch:1.5.0
torchvision==0.6.0
cuda:10.1
pillow:9.4.0

In addition, this is the code I used.
from mmdet.apis import init_detector, inference_detector, show_result_pyplot
import mmcv
# Load model
config_file = 'CascadeTabNet/Config/cascade_mask_rcnn_hrnetv2p_w32_20e_v2.py'
checkpoint_file = 'epoch_36.pth'
model = init_detector(config_file, checkpoint_file, device='cuda:0')

# Test a single image
img = "CascadeTabNet/Demo/demo.png"

# Run Inference
result = inference_detector(model, img)
# Visualization results
show_result_pyplot(model,img, result,score_thr=0.85)

Do I need to retrain the data set in this environment?
But the previous pre-training model can't be used!

Hello, I have encountered the same problem as you. Have you solved it now？


Specifications of the .dat file formats

Could you please provide some description/specification on the file formats of the data/*.dat files, especially what the fields are supposed to stand for, and which of them are mandatory? I'd have specifications on several libraries currently not covered. Currently I "overlay" those data in my "wrapper" when evaluating the JSON result. But I'd find it much better to integrate it here (and of course send you a corresponding PR then), if I could do that.
EDIT:
To give you an example, I've identified
{
 "pn": "com/getjar/sdk/vending/billing/',
 "lib": "pa;GetJar Billing;http://www.getjar.com/",
 "dn": 906,
 "cpn": "com/android/"
}

What does cpn stand for? A package Getjar depends on ("called package name")? OK, that's not needed for the .dat file. But for that it seems I'd need the values for bh (B_Hash), btc (B_Total_Call) and btn (B_Total_Number). How to identify those? Or could I simply substitute a 0 for missing values (those 3 are numeric)?
From the couple of test runs done, I could currently contribute 10 library identifications. As I'm planning to use LibRadar a bit longer, more might show up. Would be great if others could benefit from that.

I'm sorry for not specifying these descriptions earlier. I didn't want to release LibRadar other than http://radar.pkuos.org/ at the beginning, but after several weeks, the website turned out to be slow and the API I provided for the website seems difficult to use, so I set LibRadar public again in Github. In the very beginning, LibRadar returns readable sentences and I changed them into json for Node.js, but I forgot to describe what every symbol means after the modification.
I have given a new description in README.md. If you have more questions, please let me know.
Thanks a lot for your suggestion!

Thanks, that fills some gaps! But I'm still confused on adding new entries (my list meanwhile contains more than 50 libraries I could add, some with 10 entries or more). After inserting
                    "bh": self.libs_feature[mid][0],
                    "btn": self.libs_feature[mid][1],
                    "btc": self.libs_feature[mid][2],

before line 319 in detect.py I get all values reported for the "missing/unknown" library. But adding a corresponding line at the end of data/tgst5.dat – in my example,
{"dn": 177, "lib": "da;EBookDroid;https://github.com/mortenpi/ebookdroid/", "sp":"org/ebookdroid/ui/library/tasks/", "bh": 32868, "btc": 22, "btn": 7, "pn":"org/ebookdroid/ui/library/tasks/"}

and running LibRadar again, it's still not recognised. Values I've got reported:
{"dn":177,"p":[],"sp":"org/ebookdroid/ui/library/tasks","cpn":"org/ebookdroid/ui/library/tasks\/","btc":22,"pn":"org/ebookdroid/ui/library/tasks/","btn":7,"bh":32868}

So where am I going wrong here?

BTW: While waiting for your response to my PR, I wanted to proceed on my project – which is using PHP. I wrote a "wrapper class" which calls the (unmodified) LibRadar main.py, evaluates the results, and allows to "append" additional values (i.e. where LibRadar had a match but no details). The latter can be done with "exact matches" and also with "wildcard matches" (i.e. specifying "pn":"org/foobar/" would match any org/foobar/* hits). Specifications use a similar structure as your .dat files do (just fewer fields, as it doesn't do any "binary matching").
If you're interested, I could add that (incl. a short description) as separate directory (e.g. php/*) with another PR – once #2 is closed.

Thanks a lot for your effort, and it really helps. You know, it must be a tough work to tag so many libraries in database.
I wrote a script for tagging and filtering the libraries before. Every library would go through a 5-level pipeline before it appeared in tgst5.dat.  PS: 'tg' means Tagged and 'st' means Stage. =)

Yeah. I checked each line manually. Not being an Android dev (and hence not having the corresponding environment set up), I couldn't do any "binary checks". What I did was checking the project I matched whether it had the given module. And I only picked the "obvious ones". Hence some "Spongy Castle" (org/spongycastle/*) entries remained unmatched, as I couldn't find the module (pn) in the project tree.
Thanks for the merge! Do you want to have my PHP library added to your project (I'd then of course maintain that, as I'm using it myself)?

Hi, Izzy.
I'm glad to inform you that LibRadar Version2 is ready, which has better hashing algorithm, full and convincing API list, incremental database, partial match support, using dex other than apktool to analyse apps, etc.

Cool! And good to see you're still on it. Will take a look as soon as time permits (am quite busy with several other projects at the moment). If there are any hints concerning updating from the previous version, and what has changed (so I don't break my stuff), they are welcome – e.g. have there been changes in the output format (the QuickStart.md looks like it switched from JSON to some plain-text format, and no longer contains the permissions), or the way it has to be called. And is redis a (new) hard requirement now – or can LibRadar still be used stand-alone?
Any progress on adding new libraries? Maybe even detecting "possible unknown libraries" and reporting them? You remember: while I've updated a ton of entries, I wasn't able to add new ones – e.g. where I knew a certain library was used by a given app but not reported by LibRadar.

Very constructive suggestions! Thanks!
I've change all the code and rebuild this project to support "incremental data set", and that's why I use redis as my database. Now I could add new apps any time as a source for detecting new libraries. It is feasible to add a certain new library of a given app in this system. However it have not been implemented so far. I will add this functionality later.
Redis database is used as a giant hash-table. It's an important part for incremental data set support. I have the plan to create a Lite version without database.
JSON and permission support will be added soon.

Thanks for the update! As lack of JSON and permissions would break my current scripts, I'll have to wait at least until that is implemented. Redis ships from the repos as far as I could see (packages redis-server and redis-tools), so it shouldn't be too hard to meet that requirement if I must :) However, with the changed structures it's not yet clear to me how to contribute library updates then. Maybe that will become clear once I've installed the updates.
So fingers crossed and heads-up for your ongoing work!

Yeah, it shouldn't be hard to install and config Redis. ^_^


[Tables] Updates styling of mobile tables on a default desktop screen

@catchamonkey Should be the last one..!

[TD padding] Updates top and bottom to 5px

👍


Share SurfaceView

Hi,
Is there any way to publish SurfaceView on stream in Android?
Actually i want to share my game screen that is develop in unity and unity player render game in SurfaceView.

Hi @zabi90 ,
Please, could you confirm what do you mean with "share surfaceView" ? Do you want to render the publisher/subscriber view on SurfaceView? Or do you want to publish the content of a SurfaceView?
Best,
Marina

Hi @zabi90,
I think you could try to create your own VideoCapturer to get a Bitmap representation of the content of your view, and then passing it in the buffer.
You can find an example of CustomVideoCapturer here: https://github.com/opentok/opentok-android-sdk-samples/blob/master/Custom-Video-Driver/CustomVideoDriverLib/src/main/java/com/example/tokbox/CustomVideoDriverLib/CustomVideoCapturer.java
Best,
Marina


Fix(#911): Scrolling issue caused by editor height

The height of the editor was being set improperly using a css 'calc'. This PR fixes the issue by using flexbox to set the editor to take up however much room is left on the window
Description
This shows a before and after
https://github.com/usebruno/bruno/assets/20603515/69bb724e-c78b-4778-b82b-438e382ad83c
Contribution Checklist:

[x] The pull request only addresses one issue or adds one feature.
[x] The pull request does not introduce any breaking changes
[x] I have added screenshots or gifs to help explain the change if applicable.
[x] I have read the contribution guidelines.
[x] Create an issue and link to the pull request.

Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.
Publishing to New Package Managers
Please see here for more information.

Merged!
Thanks for taking of care of this @NickBoyadjian !


Launch stopped VMs on login

Hi Josh, nice project you have here!
It is possible to start a vm when the user select the VM required?

Yes i just read the source code and found this on vmaction function, sorry for opening the issue
and thanks again for a great job


Improve code boilerplate

improve the examples that showcase sc development and test.
Task: change all files in https://github.com/massalabs/massa-sc-toolkit/tree/main/commands/init/assembly

@Thykof do I need to test (and how)? :)

@longgamma-massa you can read the changes here https://github.com/massalabs/massa-sc-toolkit/pull/72/files and see if its correct


Make XPM "Target" Configurable

The Page TBB relies on the term "Staging" to generate the XPM markup.
As discussed in: Tridion Reference Implementation - Experience Manager button does not show, we talked about making this configurable. For example, the Target Type might be called "Preview" instead.
Bart also noted the XPM settings might change in the next release.

fixed in DXA 1.1 https://community.sdl.com/developers/tridion_developer/m/mediagallery/852


build: macOS does not include Python anymore

Checklist

[x] commit message follows commit guidelines

Description of change

macOS stopped bundling python, this attempts to bring back travis tests on macOS

Thanks for doing this but please use pyenv install Python on Travis CI.  It is way faster and supports all Python versions including Python 3.8 which homebrew is still struggling to support.  Try pyenv install --list to see all the versions available.

So Travis is dropping matrix: for jobs: so let's do this around line 4...
addons:
  homebrew:
    update: true
    packages:
    - npm
    - pyenv
jobs:

~matrix:~
This will ensure that all macOS jobs have acccess to the latest npm and pyenv.

@cclauss got it working, cleaning up. For pyenv to work the PATH needs to be changed and for python modules to work they need the python -m prefix

@cclauss ready for review :)

I've force pushed out the HEAD commit on master, c392a175f0, so it's in the list of commits here too to be reviewed, edited (needs test: as the prefix) and have metadata attached.

I've force pushed out the HEAD commit on master, c392a17, so it's in the list of commits here too to be reviewed, edited (needs test: as the prefix) and have metadata attached.

reworded commit names, is this what you meant?

Is it me or the python3.5 test is flaky?

reworded commit names, is this what you meant?

No, sorry, it's not your commit, we'll deal with it when merged but if you rebase onto master then you'll be without it. I think it comes from work @cclauss was doing for #1980 but got pushed to master prematurely?

Do you know why the python 3.5 test is failing? Can it be removed?

nope, will wait for @cclauss' input on that

@cclauss got any suggestions on the 3.5 failure here?

On the 3.5 tests, those seem to be diff tests and my sense is that all the same data is there but not necessarily in the right order.  Perhaps those tests need to look at smaller chunks or sort things before looking at them.
I will study that output in the next few hours...

What is that flag for? Is it related to using python -m pytest vs pytest? I know one difference is that the first one sets the current working directory as the PYTHONPATH while the second one does not.

The 3.5 failure is not related to this PR, so I think this should land when ready.
I saw the 3.5 failure when working on https://github.com/nodejs/node-gyp/pull/1961, but it went away on a second run. That points to something like a difference in Travis runners or a broken cache.
@targos (since I saw you enabled Travis here, but other org owners can also do this) can you clear the Travis cache? Thanks!

@joaocgreis sure, what should I remove (I don't know anything about Travis caches):

@targos please delete all repository caches (top right corner). Thanks!
I believe nodejs/node uses the cache to actually make the build possible because of timing issues, but here it should be ok to just delete everything.

@joaocgreis it's done

I restarted https://travis-ci.com/nodejs/node-gyp/jobs/261487549 after the cache was cleared but it still failed.

@rvagg anything pending for merging? I saw #1982 and it looks promising but I don't understand the distinction between travis and gh actions.

d6a7e0e1fb9ba4 - @cclauss' commit
345c70e56d2b - the rest, I had a bit of trouble coming up with a summary but I think I got the gist if ot in there

still dealing with linux 3.5 failures https://travis-ci.com/nodejs/node-gyp/builds/141142728, fwiw

See #1995 for more on Python 3.5 failures...


Node 11 in CI

What kind of change does this PR introduce?

Did you add tests for your changes?

Does this PR introduce a breaking change?

What needs to be documented once your changes are merged?

We want to test against WebAssembly.Global which is available in Node 11.
This PR allows webpack to be tested against arbitrary Node nightly.

Some stat tests are failing, we should probably fix them first. I don't get how allow_failures works, I tried to match on the env, see https://github.com/webpack/webpack/pull/8182/commits/a7159c96ba10f8b9d26de3add3b15eab9cf539a1.

@xtuc Can we just configure the CI to run wasm related tests in nodejs11? That might reduce the surface area of random failures.

@sendilkumarn good point! What should I pass, something like jest -t wasm right?

yeah something similar to that

Interesting, this version of Node changed the OOM detection I guess. I can try to increase the memory a wasm module can allocate (I'm on the phone sorry).

I think it's a memory leak in the test suite. I try to address it in a separate PR.

Thanks :tada