Esmlab Design Document

HackMD note: https://hackmd.io/mwGPvXgXSu2f7iXGCO3m4A

I saw mention of indices here, so wanted to make sure you were aware of https://github.com/Ouranosinc/xclim

cc @maboualidev, @kmpaul

I can't edit that document directly, but wanted to make you aware of https://github.com/bradyrx/esmtools/ as well. I don't think these clash, since esmtools is really a repository for personal functions I use commonly with working with gridded output. It's a kitchen sink for really any sort of domain-specific or domain-agnostic functions for climate analysis.
There might be some things in there worth migrating or drawing from. Particularly functions related to our discussion in https://github.com/bradyrx/esmtools/issues/65. Between climpred and esmtools stats modules I have an rm_poly, rm_trend, fit_poly (returns the actual fit that was made), ACF, autocorr, corr and so on that can be applied to a grid. The native scipy and numpy functions can't of course just ingest gridded products. I have code snippets to update the functions to be optimized for dask per work with @andersy005 and @gelsworth

@bradyrx,

I can't edit that document directly,

Let me know whether https://hackmd.io/mwGPvXgXSu2f7iXGCO3m4A?edit doesn't work when you are signed in and I will fix this.

@maboualidev, @matt-long
I just updated the design document with some of information from our discussion this afternoon. When you get a chance in the coming days, please take a look at it, and add the bits that are missing.

Cc @dougiesquire

@andersy005
Hi, xclim dev here. I've gone through the list of issues in esmlab and it looks like we're sharing many objectives. In particular, I'd like to see weighted statistics supported natively by xarray, as well as support for time_bnds aware operations.
Originally, xclim was designed to be a library of climate indicators that are typically used for climate impact studies. We've added some utilities around it, but there's clearly a lot of overlap with other packages. We'd be happy for xclim to focus on climate indicators, include ocean and ice indicators,  and outsource other utilities (ensemble stats, clustering, subsetting) to other libraries such as esmlab.
Would it be useful to have an Earth System Modeling and Data Analysis project board somewhere (e.g. pydata) to coordinate efforts?

Looks good to me.
I just changed the link to https://github.com/coderepocenter/AxisUtilities
regards,
Moe
On Wed, Oct 30, 2019 at 11:47 PM Anderson Banihirwe <
<EMAIL_ADDRESS>wrote:

@maboualidev https://github.com/maboualidev, @matt-long
https://github.com/matt-long
I just updated the design document with some of information from our
discussion this afternoon. When you get a chance in the coming days, please
take a look at it, and add the bits that are missing.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NCAR/esmlab/issues/148?email_source=notifications&email_token=AF5OIB3VMBXBBYSGRRY25CLQRJWQ7A5CNFSM4IW2RVNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECWUG5Y#issuecomment-548225911,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF5OIB2GVUGA6H7RKJIFDUDQRJWQ7ANCNFSM4IW2RVNA
.

--
M. Abouali, Ph.D
Data Scientist,
Global Data Insight & Analytics (GDI&A)
Ford Motor Company
Cell:<PHONE_NUMBER>
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is
uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onterecht
ontvangt wordt u verzocht de inhoud niet te gebruiken en de afzender direct
te informeren.
The information contained in this message may be confidential and is
intended to be exclusively for the addressee. Should you receive this
message unrightfully, please do not use the contents herein and notify the
sender immediately by return e-mail.


http url ?

am using this application and set the url to point to my php page that read the post and insert it into mysql table, but i get 0 in latitude and longtitude !!? when i test the code on my ionic application it get the latitude and longtitude values and post them to the server but with delay like every 1 minute or around 800 m !! the setting am using in both my ionic app and on this application is the same
 desiredAccuracy: 0,

stationaryRadius: 30,
distanceFilter: 50,
locationUpdateInterval: 1000,
fastestLocationUpdateInterval: 1000,
activityRecognitionInterval:1000,
stopTimeout:0,
any help ?

Have you paid for the Premium version?
http://christocracy.github.io/cordova-background-geolocation/
On Monday, June 15, 2015, firaskudsy<EMAIL_ADDRESS>wrote:

am using this application and set the url to point to my php page that
read the post and insert it into mysql table, but i get 0 in latitude and
longtitude !!? when i test the code on my ionic application it get the
latitude and longtitude values and post them to the server but with delay
like every 1 minute or around 800 m !! the setting am using in both my
ionic app and on this application is the same
desiredAccuracy: 0,
stationaryRadius: 30,
distanceFilter: 50,
locationUpdateInterval: 1000,
fastestLocationUpdateInterval: 1000,
activityRecognitionInterval:1000,
stopTimeout:0,
any help ?
—
Reply to this email directly or view it on GitHub
https://github.com/christocracy/cordova-background-geolocation-SampleApp/issues/1
.

--
Snet from Gmail Mobile

no am using the free version, as i read the free version suppose to post the location, now i did another test, with multiple setting values , like distanceFilter = 10 , and do the test then change it to 50 and do the test , but the problem now is .. it post the location every one minute , i want it to post every 5 second or lest .. what the problem ? any help ?

But this SampleApp is designed for the Premium version.
On Monday, June 15, 2015, firaskudsy<EMAIL_ADDRESS>wrote:

no am using the free version, as i read the free version suppose to post
the location, now i did another test, with multiple setting values , like
distanceFilter = 10 , and do the test then change it to 50 and do the test
, but the problem now is .. it post the location every one minute , i want
it to post every 5 second or lest .. what the problem ? any help ?
—
Reply to this email directly or view it on GitHub
https://github.com/christocracy/cordova-background-geolocation-SampleApp/issues/1#issuecomment-111968791
.

--
Snet from Gmail Mobile

what about the plugin ?  https://github.com/christocracy/cordova-plugin-background-geolocation
am using this one in my ionic app, and i compare the functionality with the sample app. so how the plugin work ? the same as described ?

You cannot expect this App to work with the free version (especially on
Android).  The settings you see on the settings screen only exist in the
Premium version.  There are a few that are common to both, but the free
version is incompatible.
You must install the premium version for this app to work:
On Monday, June 15, 2015, Chris Scott<EMAIL_ADDRESS>wrote:

But this SampleApp is designed for the Premium version.
On Monday, June 15, 2015, firaskudsy<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:

no am using the free version, as i read the free version suppose to post
the location, now i did another test, with multiple setting values , like
distanceFilter = 10 , and do the test then change it to 50 and do the test
, but the problem now is .. it post the location every one minute , i want
it to post every 5 second or lest .. what the problem ? any help ?
—
Reply to this email directly or view it on GitHub
https://github.com/christocracy/cordova-background-geolocation-SampleApp/issues/1#issuecomment-111968791
.

--
Snet from Gmail Mobile

--
Snet from Gmail Mobile

dose this one minute a limitation for the free version ?

what are the setting for the free version and how oftern it send updates ?

i want to use the plugin in my ionic app , i want to use the free vesion.

I cannot answer question about your use of this Premium version SampleApp
with the incompatible Free version.
You should not use this repo unless you've paid for the Premium Version.
If you have questions about the Free version, you should use the free
version's sample app (detailed in its README) and post issues at the free
version repo.
On Monday, June 15, 2015, firaskudsy<EMAIL_ADDRESS>wrote:

dose this one minute a limitation for the free version ?
—
Reply to this email directly or view it on GitHub
https://github.com/christocracy/cordova-background-geolocation-SampleApp/issues/1#issuecomment-111970494
.

--
Snet from Gmail Mobile

ok i will change and post into the free version, many thanks


[FEATURE] allow developers to save jobs and display saved jobs

This PR introduces the concept of "bookmarks" to the system, or "saved jobs" as they're branded on the frontend.
I've gone slightly off the original specification by allowing any user to bookmark jobs – not just developers. This keeps the overall integration and data model a bit simpler, plus potentially offers more utility than we were anticipating – recruiters might find value in saving jobs, for example.
Jobs are also automatically saved when a user applies for them. If the user previously had that job saved, we only update "applied_at" column against it.
To avoid repeating code across many templates, in this PR I've also lifted some common HTML into two new templates:

static/views/header-template.html
static/views/apply-box-developer-template.html

Although I have suffered a bit of duplication when writing the relevant Javascript, but that's only across a few times.
The issue also asked for the saved jobs button to be added to company.html, but this is another one I've skipped. I've added the save button everywhere we show the apply button, but we don't show the apply button on company.html. Every job on that page just links to the relevant job page, which will have the save & apply buttons.
For the "Create a profile popup", I've had to introduce the popup to two new pages: job.html and landing.html. To give it the various variables it needs I've also had to update the various handlers, which then also required me to pass in *developer.Repository in many different places. You'll see that a lot in the diffs.
Finally, I've kept the save jobs page itself quite simple. It's a fairly boring table for now. We can adjust this as required.
Still to-do:

[x] Remove a job from the saved jobs list
[x] Joining applied jobs via apply_token table
[x] Have a proper review of the changes myself

Screenshots
Saved jobs page:

Save job button against a job advert on the landing page:

Save job button on a job page:

Solves #28
/claim #28

@rjackson thank you for the PR

what you did makes sense, can add the ability to remove "saved jobs", but if a job has been applied to, we dont allow them to remove it from the list
it's fine to join apply_token for now, it would be appropriate to automatically "bookmark" a job if someone applies to it. If you just join the tables we wont have to run any migrations. I can add some index to apply_token if the join gets slow
let me know when you added the "remove jobs" from bookmark so i will review.

Looks good overall

Alright ready for this to be reviewed @dm161 :)

thank you @rjackson looks good - merging now and testing in prod. There is only one thing missing, jobs that have been saved dont show as "saved" when you load the page, I will create an item to track this.

https://github.com/golang-cafe/job-board/issues/122


Anyway cancel all requests?

How can i cancel all my moya requests?

Hey @Natai ,
I doubt it's possible with Moya directly (need investigation). But as Moya is a layer of AF, you can do something like:
let sessionManager = Alamofire.SessionManager.default sessionManager.session.getTasksWithCompletionHandler { dataTasks, uploadTasks, downloadTasks in
    dataTasks.forEach {
        $0.cancel()
    }
    uploadTasks.forEach {
        $0.cancel()
    }
    downloadTasks.forEach {
       $0.cancel()
    }
}

This works only if you didn't override the AF manager used by your Moya instance, obviously.
But cancelling request by using Moya can be a good feature I think
Cheers


Chromecast Support

@ron666  A lot of players now includes Chromecast support

VideoJS: https://github.com/benjipott/video.js-chromecast
Flowplayer: https://flowplayer.electroteque.org/chromecast

Its a good feature, because in the case of Flowplayer is a pay plugin

@isantolin Thanks. I'll check this

Since I don't have a Chromecast device, what's the expected output for this?

When a Chromecast is configured on Browser, a Player with Chromecast support adds a Button to broadcast content to device.

If you dont have a Chromecast, you can use Cheapcast app to emulate

+1
While we are at it. How about adding AirPlay also?

By the way: There is a Web Presentation API ( https://developer.mozilla.org/en-US/docs/Web/API/Presentation_API ) which is already supported by Chrome (seems to be for Chromecast) with an experimental Polyfill which should work without Chromecast ( https://mediascape.github.io/presentation-api-polyfill/ ). What about using that?

How about this example, is with mediaelement.js, isn't?
http://amoravhad.com/projects/vCast-jQuery/index.html

Would like something more internal support rather then having some plugin. Casting is something that everyone would want

Hi @jimmywarting
Thanks for your reply.
I'm sorry, it was only a reference that uses mediaelement.js.
The demo app CastVideos-chrome should help with the code as well.

The vCast-jQuery uses a lot from CastVideos.js

Thanks all for your comments. I'll check the documentation about this and start working on it. I'll try to include AirPlay. This ticket should be logged in mediaelement-plugins repo BTW

videojs also has plugin for casting
https://github.com/benjipott/video.js-chromecast
https://github.com/jgubman/videojs-airplay

The advantage with presentation api vs chromecast is that you can also cast to some TV's with DIAL (discovery and launch)

This issue was moved to mediaelement/mediaelement-plugins#23


Lenovo ThinkPad E14

Init profiles for the Lenovo ThinkPad E14.
This is mostly based on the L14 and not completely ready yet, it already seems to work quite well, but I haven't tested all details yet. I put it here for feedback and keeping track of the progress.
Disclosure: I only have an E14 with AMD, not with Intel.

evaluation on master is fixed again.

Thank you! This fixed the backlight issue for me. (E14 with AMD)


IE8 and FlashAudioPlugin - Object doesn't support this property or method this.AbstractPlugin_constructor();

Trying to use FlashAudioPlugin as fallback for IE8, but got following error:
Object doesn't support this property or method  flashaudioplugin-0.6.0.combined.js?body=1, line 1180 character 3
function FlashAudioPlugin() {
this.AbstractPlugin_constructor();
Any ideas how to fix it?

huh, thats no good.
Thanks for bringing this to our attention, I'll take a look into it and let you know when I have a solution.

This issue is related to the new inheritance model that does not play nicely with IE8 (affects preload, tween, and sound). We are looking at solutions already. In the mean time, I suggest using Preload v 0.4.1.
Cheers

This is not going to be addressed moving forward. For projects that require IE8 fallback, please use version 0.5.2, which fully supports IE8.


[Feature request]: Deploy applications using PHP 8.x

Discussed in https://github.com/devopness/devopness/discussions/843

Resolved. PHP 8.x applications can be deployed with Devopness, since Jan/2024.


Foreign Key name need to be origin table name

Not sure it's an requirement from PostgreSQL or if it's a bug from the provider...
I recently had issue with the select telling that the value doesn't exist when foreign key doesn't have the same name as the original table name. I fixed the issue by changing the name to be the same and doing a new migration :
This database was working fine one Entity Framework with MSSQL but i switched to EF Core PostgreSQL and now i have this little issue. So is this a bug from the provider or just a PostegreSQL convention.
        {
            migrationBuilder.DropForeignKey(
                name: "FK_RespawnMapType_Map_DefaultMapId",
                table: "RespawnMapType");

            migrationBuilder.RenameColumn(
                name: "DefaultMapId",
                table: "RespawnMapType",
                newName: "MapId");

            migrationBuilder.RenameIndex(
                name: "IX_RespawnMapType_DefaultMapId",
                table: "RespawnMapType",
                newName: "IX_RespawnMapType_MapId");

            migrationBuilder.AddForeignKey(
                name: "FK_RespawnMapType_Map_MapId",
                table: "RespawnMapType",
                column: "MapId",
                principalTable: "Map",
                principalColumn: "MapId",
                onDelete: ReferentialAction.Restrict);
        }

        protected override void Down(MigrationBuilder migrationBuilder)
        {
            migrationBuilder.DropForeignKey(
                name: "FK_RespawnMapType_Map_MapId",
                table: "RespawnMapType");

            migrationBuilder.RenameColumn(
                name: "MapId",
                table: "RespawnMapType",
                newName: "DefaultMapId");

            migrationBuilder.RenameIndex(
                name: "IX_RespawnMapType_MapId",
                table: "RespawnMapType",
                newName: "IX_RespawnMapType_DefaultMapId");

            migrationBuilder.AddForeignKey(
                name: "FK_RespawnMapType_Map_DefaultMapId",
                table: "RespawnMapType",
                column: "DefaultMapId",
                principalTable: "Map",
                principalColumn: "MapId",
                onDelete: ReferentialAction.Restrict);
        }

The issue description isn't very clear - can you please post some code and some actual error messages, and explain exactly what the problem is?

i tried to reproduce this issue on a small clean project and didn't got it... Maybe a configuration issue i had so i will close the issue. Maybe an old migration had an issue on index or something like this...


Fixing inconsistent IRAM_ATTR definitions across compilation units (IDFGH-9403)

The IRAM_ATTR preprocessor definitions depend on the GCC __COUNTER__ preprocessor macro that automatically increments itself after being used in code. Using this feature is a bad design decision inside of headers since they can be included prior to other __COUNTER__ uses, making the definitions that use __COUNTER__ different across compilation units (only fixed in the C++20 modules design). This is causing confusing compiler warnings in latest GCC 11.2.0 from Xtensa and I guess many developers added the -Wno-attributes flag to their building process because of it.
This pull request fixed the issue. All of the depending projects (Arduino Core for example) would have those annoying build warnings. And, oh boy, is our world connected. I suggest you to backport this fix (4.4.3).

C:/Users/digit/.platformio/packages/framework-arduinoespressif32/tools/sdk/esp32/include/freertos/port/xtensa/include/freertos/portmacro.h:613:48: warning: ignoring attribute 'section (".iram1.24")' because it conflicts with previous 'section (".iram1.22")' [-Wattributes]
613 | static inline bool IRAM_ATTR xPortCanYield(void)

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

Thanks for your contribution.

I think the solution we would like to have is to remove IRAM_ATTR from function declarations in the header file, except for the static inline definitions (which don't have this attribute mismatch issue). Would that work for you?

Wait, i have just realized that you are trying to compile IDF v4.4.3 (via the Arduino project?) with GCC 11.2. That's probably not going to work, as IDF v4.4.x is not compatible with the new GCC 11 based toolchain. We have already fixed all the attribute related warnings in IDF v5.0, which does support the GCC 11 based toolchain.

Wait, i have just realized that you are trying to compile IDF v4.4.3 (via the Arduino project?) with GCC 11.2. That's probably not going to work, as IDF v4.4.x is not compatible with the new GCC 11 based toolchain. We have already fixed all the attribute related warnings in IDF v5.0, which does support the GCC 11 based toolchain.

How has IRAM_ATTR been fixed if __COUNTER__ is still being used?
https://github.com/espressif/esp-idf/blob/release/v5.0/components/esp_common/include/esp_attr.h
Do you really think that merely removing the functions now will fix this broken design decision? Are you sure that future developers will not fall into the same pitfall, making the warning reappear? Are you sure devs won't be ignorant by simply using -Wno-attributes?

You are completely right that removing IRAM_ATTR from the function declarations doesn't prevent future developers from accidentally adding it back again. For ESP-IDF and other projects maintained by Espressif, we make sure that such issues will be discovered by running CI builds with additional warnings-as-errors flags enabled.
Of course, a developer of another project might encounter a -Wattributes warning and decide to disable this warning instead of fixing it. (Which may happen for any other useful compiler warning, right?)

Also you mentioning this word "trying" does not 100% reflect the reality.

I apologize for misrepresenting what you are doing! I didn't realize this when I made the comment, now I have read the linked PR and I think I understand what you are doing. Indeed, if ESP-IDF v4.4.x is already pre-compiled (via the arduino-esp32 project) then building other code with GCC 11 and linking it to these pre-compiled libraries will work fine.
On the topic of the PR itself, unfortunately compiling a "blink" example with your PR branch currently results in several errors:
In file included from /Users/ivan/e/esp-idf/components/hal/include/hal/adc_types.h:13,
                 from /Users/ivan/e/esp-idf/components/ulp/ulp_common/include/ulp_adc.h:9,
                 from /Users/ivan/e/esp-idf/components/ulp/ulp_common/ulp_adc.c:8:
/Users/ivan/e/esp-idf/components/esp_common/include/esp_attr.h:189: warning: "EXT_RAM_ATTR" redefined
  189 | #define EXT_RAM_ATTR _Pragma ("GCC warning \"'EXT_RAM_ATTR' macro is deprecated, please use `EXT_RAM_BSS_ATTR`\"")
      |
In file included from /Users/ivan/e/esp-idf/components/hal/include/hal/adc_types.h:13,
                 from /Users/ivan/e/esp-idf/components/ulp/ulp_common/include/ulp_adc.h:9,
                 from /Users/ivan/e/esp-idf/components/ulp/ulp_common/ulp_adc.c:8:
/Users/ivan/e/esp-idf/components/esp_common/include/esp_attr.h:94: note: this is the location of the previous definition
   94 | #define EXT_RAM_ATTR
      |

After fixing the duplicate definitions in esp_attr.h, I get:
/Users/ivan/e/esp-idf/components/spi_flash/spi_flash_chip_generic.c:51:41: error: 'esp_flash_encryption_default' causes a section type conflict with 'spi_flash_chip_generic_timeout'
   51 |
    static spi_flash_encryption_t esp_flash_encryption_default __attribute__((__unused__)) = {
      |                                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/ivan/e/esp-idf/components/spi_flash/spi_flash_chip_generic.c:72:41: note: 'spi_flash_chip_generic_timeout' was declared here
   72 | const DRAM_ATTR flash_chip_op_timeout_t spi_flash_chip_generic_timeout = {
      |                                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

To debug this, I have ran just the preprocessor on this file. The relevant part is:
__attribute__((section(".dram1" "." "__ESP_COUNTER__"))) static spi_flash_encryption_t esp_flash_encryption_default __attribute__((__unused__)) = {
    .flash_encryption_enable = spi_flash_encryption_hal_enable,
    .flash_encryption_disable = spi_flash_encryption_hal_disable,
    .flash_encryption_data_prepare = spi_flash_encryption_hal_prepare,
    .flash_encryption_done = spi_flash_encryption_hal_done,
    .flash_encryption_destroy = spi_flash_encryption_hal_destroy,
    .flash_encryption_check = spi_flash_encryption_hal_check,
};

Basically it looks like the section name gets expanded to .dram1.__ESP_COUNTER__, not to the actual counter value. Could you please check this? If you get a chance to fix this, please ping me and I'll take a look at the PR again.

If I'm not mistaken, one way to solve this without changing IRAM_ATTR and other definitions would be to use them only in function definitions (i.e. in *.c files). In the declarations in header files you would have to remove them and add extern keyword instead.
For example, cache_utils.c remains the same, i.e.:
...
void IRAM_ATTR esp32_spiflash_start(void)
{
    ....

But in cache_utils.h it changes to:
...
extern void esp32_spiflash_start(void);
...

I close this PR for now because it does not fit IDF, it makes several errors compiling a "blink" example (https://github.com/espressif/esp-idf/pull/10773#issuecomment-1434343718). Feel free to update it or open a new one.
Thanks.

You are completely right that removing IRAM_ATTR from the function declarations doesn't prevent future developers from accidentally adding it back again. For ESP-IDF and other projects maintained by Espressif, we make sure that such issues will be discovered by running CI builds with additional warnings-as-errors flags enabled.
Of course, a developer of another project might encounter a -Wattributes warning and decide to disable this warning instead of fixing it. (Which may happen for any other useful compiler warning, right?)

Also you mentioning this word "trying" does not 100% reflect the reality.

I apologize for misrepresenting what you are doing! I didn't realize this when I made the comment, now I have read the linked PR and I think I understand what you are doing. Indeed, if ESP-IDF v4.4.x is already pre-compiled (via the arduino-esp32 project) then building other code with GCC 11 and linking it to these pre-compiled libraries will work fine.
On the topic of the PR itself, unfortunately compiling a "blink" example with your PR branch currently results in several errors:
In file included from /Users/ivan/e/esp-idf/components/hal/include/hal/adc_types.h:13,
                 from /Users/ivan/e/esp-idf/components/ulp/ulp_common/include/ulp_adc.h:9,
                 from /Users/ivan/e/esp-idf/components/ulp/ulp_common/ulp_adc.c:8:
/Users/ivan/e/esp-idf/components/esp_common/include/esp_attr.h:189: warning: "EXT_RAM_ATTR" redefined
  189 | #define EXT_RAM_ATTR _Pragma ("GCC warning \"'EXT_RAM_ATTR' macro is deprecated, please use `EXT_RAM_BSS_ATTR`\"")
      |
In file included from /Users/ivan/e/esp-idf/components/hal/include/hal/adc_types.h:13,
                 from /Users/ivan/e/esp-idf/components/ulp/ulp_common/include/ulp_adc.h:9,
                 from /Users/ivan/e/esp-idf/components/ulp/ulp_common/ulp_adc.c:8:
/Users/ivan/e/esp-idf/components/esp_common/include/esp_attr.h:94: note: this is the location of the previous definition
   94 | #define EXT_RAM_ATTR
      |

After fixing the duplicate definitions in esp_attr.h, I get:
/Users/ivan/e/esp-idf/components/spi_flash/spi_flash_chip_generic.c:51:41: error: 'esp_flash_encryption_default' causes a section type conflict with 'spi_flash_chip_generic_timeout'
   51 |
    static spi_flash_encryption_t esp_flash_encryption_default __attribute__((__unused__)) = {
      |                                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/ivan/e/esp-idf/components/spi_flash/spi_flash_chip_generic.c:72:41: note: 'spi_flash_chip_generic_timeout' was declared here
   72 | const DRAM_ATTR flash_chip_op_timeout_t spi_flash_chip_generic_timeout = {
      |                                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

To debug this, I have ran just the preprocessor on this file. The relevant part is:
__attribute__((section(".dram1" "." "__ESP_COUNTER__"))) static spi_flash_encryption_t esp_flash_encryption_default __attribute__((__unused__)) = {
    .flash_encryption_enable = spi_flash_encryption_hal_enable,
    .flash_encryption_disable = spi_flash_encryption_hal_disable,
    .flash_encryption_data_prepare = spi_flash_encryption_hal_prepare,
    .flash_encryption_done = spi_flash_encryption_hal_done,
    .flash_encryption_destroy = spi_flash_encryption_hal_destroy,
    .flash_encryption_check = spi_flash_encryption_hal_check,
};

Basically it looks like the section name gets expanded to .dram1.__ESP_COUNTER__, not to the actual counter value. Could you please check this? If you get a chance to fix this, please ping me and I'll take a look at the PR again.

Does removing "IRAM_ATTR" mean that the function can only run in Flash and not RAM?


Azov Regiment is also neo-nazi

I don't see the point of fighting "Russia nazi" by supporting a neo-nazi regiment.
The Azov Regiment has participated in torture and war crimes, but now incorporated into the national guard of ukraine.
The Ukrainian government is standing with nazi now, and if you say that you are against this, I support you.

I don't see the point of fighting "Russia nazi" by supporting a neo-nazi regiment.
The Azov Regiment has participated in torture and war crimes, but now incorporated into the national guard of ukraine.
The Ukrainian government is standing with nazi now, and if you say that you are against this, I support you.

Where is the tag "typical-ukrainian-nazi"?

I don't think Ukraine with Nazi troops can accuse Russia of Nazi behavior.

Well @cristaloleg, you reacted with thumbs down emoji under every comment from me.
What do you mean?
Do you support the Ukrainian nazi?
Ukraine is not going to do you any favors for having Ukraine as your father.

Downvoting 'cause most of ukrainians nazi posts are forced by pro-russian media. I'm not going to poke dead horse here.
Simple check: if all all or most of the ukrainian forces are nazi, why do Israel help Ukraine?

There's nothing to discuss here.


Lower the Bid Min Boundry

Lower the bid min boundry from 50 gold to 10 gold

you could right click slide bar for unlimited range

you could right click slide bar for unlimited range

I didn't know this function, will close this PR, thanks.


Alternative implementation of Jedis Cluster commands using Java Proxy

I wrote a small app to set N string keys to a constant value using the existing JedisCluster and my new ClusterInvocationHandler.  This was very limited testing, but with 10,000 and 50,000 keys the new implementation performed as well (+/- 100ms) as the current implementation; sometimes a bit faster, sometimes a bit slower.

wrong implementation at processing JedisAskDataException .


Assets has a equivalent in dollars (the equivalent that matches beam)

When we open the receive screen and select assets - under  amount tab has equivalent in dollars
https://user-images.githubusercontent.com/85252690/134137223-2361cf36-a695-467d-969b-b7a9d3530486.mp4

Checked


chore: bump zio, zio-test, zio-test-sbt from 2.1.7 to 2.1.8

About this PR
📦 Updates

dev.zio:zio
dev.zio:zio-test
dev.zio:zio-test-sbt

from 2.1.7 to 2.1.8
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

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

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

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 67.90%. Comparing base (876c282) to head (70ee69c).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #289   +/-   ##
=======================================
  Coverage   67.90%   67.90%
=======================================
  Files          79       79
  Lines        1087     1087
  Branches      126      126
=======================================
  Hits          738      738
  Misses        349      349


Completion of error handling

Would you like to add more error handling for return values from functions like the following?

fopen ⇒ blacklist_load
malloc ⇒ favorites_init
strdup ⇒ print_selection_row

@elfring Yes, this should be definitely improved.

How do you think about to improve static source code analysis also for this software?

Are you interested to apply aspect-oriented software development?
Would you like to encapsulate error detection and corresponding exception handling as a reusable aspect in this software?

I used aspects in complex Java apps, …

This is good to know. - Would you like to reuse these software development experiences for the programming language “C” (and/or “C++”)?
How do you think about to tackle exception handling by aspect-oriented programming?


Waste management missing json

As mentioned in #151 I did work out some of the missing json example and schemas for the existing models. These are the one for WasteContainerIsle and WasteContainerModel.

LGTM but before merging, please could you rebase this PR so that it includes only the concerned commit and not pulls or merges ?
thanks!

@chicco785 waiting for your updated content

I was a bit sick, today I will check all your comments
iFede - Fede's mobile edition

Il giorno 17 ott 2017, alle ore 08:22, Jose M. Cantera<EMAIL_ADDRESS>ha scritto:
@jmcanterafonseca commented on this pull request.
needs a rebase
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

rebased


"Cannot run blog from a remote URL." error when initing the proejct

Hi. I followed the process on<EMAIL_ADDRESS>there's the result on my CLI:

I'm excited to get Deno running on a real app (my personal blog), but the friction is too big to deal with. almost giving up and getting a node/next alternative or something.
can you give me a hand here?
I've tried with both deno 1.46.3 and deno +2 versions.

Try Deno 1.45.3. Seems like the same problem as this: https://github.com/denoland/deno_blog/issues/151.

I faced the same issue and latest commit of this repository contains solution but there is no new version released yet to point new changes in deno.land. So you need to import deno code from github manually until new version released.
Below solution worked for me. ✅
deno 2.1.4 (stable, release, aarch64-apple-darwin).
Check this solution


Migrate from go dep to go mod to generate dependencies

Fixes #
Proposed Changes

Run export GO111MODULE=on.
Run go mod init knative.dev/operator.
Create tools.go under hack.
Run go mod tidy mutiple times, adding one line in replace section in go.mod file each time till we find them all.
Run go mod vendor.
Modify the file update-deps.sh under hack.
Run ./hack/update-deps.sh.
Remove Gopkg.lock and Gopkg.toml.

Release Note

/retest

@googlebot rescan

/lgtm
Thanks @houshengbo .


ObjectMappingException getMessage() return null

Hello,
I'm a runnig on spongevanilla 7.1.0-BETA-120 and I'm facing a problem.
Maybe it's an error in my code but when I catch ObjectMappingException and i try to display the message with getMessage() it return null

Need some more details, what is throwing an error? What is your code? What is the stack trace? What are you trying to do?

I'm sorry,
I posted my problem too early.
the error is on my side.
thank you for your support.


JavaScript VM: bytes memory not writeable

The JavaSript VM (JSVM) is getting stuck when writing to a bytes type in memory.
The writeLocalByte() function should return "0: bytes: 0x61" but it returns "0: bytes: 0x". On close investigation with the REMIX debugger it turns out the execution doesn't reach return and gets stuck on a BYTE call at local[0].
When deployed on a local chain it works fine.
To reproduce, add following code in REMIX,
create the contract in the JSVM, call writeLocalBytes().
Contract:
pragma solidity ^0.4.22;

contract BytesTest {

    bytes global = new bytes(1);

    function writeGlobalBytes() public {
        global[0] = ('a');
    }

    function getGlobalBytes() public view returns(bytes) {
        return global;
    }

    function writeLocalBytes() public pure returns(bytes) {
        bytes memory local = new bytes(1);
        local[0] = ('a');
        return local;
    }
}

Tested on:
Solidity version: 0.4.22+commit.4cb486ee.Emscripten.clang
Google Chrome Version 65.0.3325.181
Mozilla Firefox 59.0.2 (64-bit)
Windows 10 Pro

Thanks for the report. That is going to be fixed pretty soon. the fix is already pushed
@axic @holgerd77 @jwasinger

remix.ethereum.org has been updated with latest ethereumjs-vm version, that should be ok now


Error when trying to print: No destination host name supplied by cups-browsed for printer

I have Ubuntu 20.04 with cups-browsed and cups-filter at 1.27.4-1.
When I try to print, the printer pauses.
Looking into localhost:631 the error message is
"No destination host name supplied by cups-browsed for printer<EMAIL_ADDRESS>is cups-browsed running?"

A few logs:
# When printer is not connected to the network
$ lpstat -v
device for<EMAIL_ADDRESS>implicitclass://HP040E3C6003BF_HP_Color_Laser_150_%40HP040E3C6003BF.local/

# When printer is connected to the network
$ lpstat -v
device for HP040E3C6003BF_HP_Color_Laser_150_: implicitclass://HP040E3C6003BF_HP_Color_Laser_150_/
device for<EMAIL_ADDRESS>implicitclass://HP040E3C6003BF_HP_Color_Laser_150_%40HP040E3C6003BF.local/

I am kind of confused why the local is available even with an offline printer.
 In case of
# contradicting settings the setting defined in the configuration file
# will get used.

# Unknown directives are ignored, also unknown values.

# Where should cups-browsed save information about the print queues it had
# generated when shutting down, like whether one of these queues was the
# default printer, or default option settings of the queues?

# CacheDir /var/cache/cups

# Where should cups-browsed create its debug log file (if "DebugLogging file"
# is set)?

# LogDir /var/log/cups

# How should debug logging be done? Into the file
# /var/log/cups/cups-browsed_log ('file'), to stderr ('stderr'), or
# not at all ('none')?

# Note that if cups-browsed is running as a system service (for
# example via systemd) logging to stderr makes the log output going to
# the journal or syslog. Only if you run cups-browsed from the command
# line (for development or debugging) it will actually appear on
# stderr.

# DebugLogging file
# DebugLogging stderr
# DebugLogging file stderr
# DebugLogging none

# Which protocols will we use to discover printers on the network?
# Can use DNSSD and/or CUPS and/or LDAP, or 'none' for neither.

BrowseRemoteProtocols dnssd cups

# Which protocols will we use to broadcast shared local printers to the network?
# Can use DNSSD and/or CUPS, or 'none' for neither.
# Only CUPS is actually supported, as DNSSD is done by CUPS itself (we ignore
# DNSSD in this directive).

# BrowseLocalProtocols none

# Settings of this directive apply to both BrowseRemoteProtocols and
# BrowseLocalProtocols.
# Can use DNSSD and/or CUPS and/or LDAP, or 'none' for neither.

# BrowseProtocols none

# Only browse remote printers (via DNS-SD or CUPS browsing) from
# selected servers using the "BrowseAllow", "BrowseDeny", and
# "BrowseOrder" directives

# This serves for restricting the choice of printers in print dialogs
# to trusted servers or to reduce the number of listed printers in the
# print dialogs to a more user-friendly amount in large networks with
# very many shared printers.

# This only filters the selection of remote printers for which
# cups-browsed creates local queues. If the print dialog uses other
# mechanisms to list remote printers as for example direct DNS-SD
# access, cups-browsed has no influence. cups-browsed also does not
# prevent the user from manually accessing non-listed printers.

# "BrowseAllow": Accept printers from these hosts or networks. If
# there are only "BrowseAllow" lines and no "BrowseOrder" and/or
# "BrowseDeny" lines, only servers matching at last one "BrowseAllow"
# line are accepted.

# "BrowseDeny": Deny printers from these hosts or networks. If there
# are only "BrowseDeny" lines and no "BrowseOrder" and/or
# "BrowseAllow" lines, all servers NOT matching any of the
# "BrowseDeny" lines are accepted.

# "BrowseOrder": Determine the order in which "BrowseAllow" and
# "BrowseDeny" lines are applied. With "BrowseOrder Deny,Allow" in the
# beginning all servers are accepted, then the "BrowseDeny" lines are
# applied to exclude unwished servers or networks and after that the
# "BrowseAllow" lines to re-include servers or networks. With
# "BrowseOrder Allow,Deny" we start with denying all servers, then
# applying the "BrowseAllow" lines and afterwards the "BrowseDeny"
# lines.

# Default for "BrowseOrder" is "Deny.Allow" if there are both
# "BrowseAllow" and "BrowseDeny" lines.

# If there are no "Browse..." lines at all, all servers are accepted.

# BrowseAllow All
# BrowseAllow cups.example.com
# BrowseAllow <IP_ADDRESS>
# BrowseAllow <IP_ADDRESS>/24
# BrowseAllow <IP_ADDRESS>/<IP_ADDRESS>

# BrowseDeny All
# BrowseDeny printserver.example.com
# BrowseDeny <IP_ADDRESS>
# BrowseDeny <IP_ADDRESS>/24
# BrowseDeny <IP_ADDRESS>/<IP_ADDRESS>

# BrowseOrder Deny,Allow
# BrowseOrder Allow,Deny

# The interval between browsing/broadcasting cycles, local and/or
# remote, can be adjusted with the BrowseInterval directive.

# BrowseInterval 60

# Browsing-related operations such as adding or removing printer queues
# and broadcasting are each allowed to take up to a given amount of time.
# It can be configured, in seconds, with the BrowseTimeout directive.
# Especially queues discovered by CUPS broadcasts will be removed after
# this timeout if no further broadcast from the server happens.

# BrowseTimeout 300

# Filtering of remote printers by other properties than IP addresses
# of their servers

# Often the desired selection of printers cannot be reached by only
# taking into account the IP addresses of the servers. For these cases
# there is the BrowseFilter directive to filter by most of the known
# properties of the printer.

# By default there is no BrowseFilter line meaning that no filtering
# is applied.

# To do filtering one can supply one or more BrowseFilter directives
# like this:

# BrowseFilter [NOT] [EXACT] <FIELD> [<VALUE>]

# The BrowseFilter directive always starts with the word
# "BrowseFilter" and it must at least contain the name of the data
# field (<FIELD>) of the printer's properties to which it should
# apply.

# Available field names are:

#   name:    Name of the local print queue to be created
#   host:    Host name of the remote print server
#   port:    Port through which the printer is accessed on the server
#   service: DNS/SD service name of the remote printer
#   domain:  Domain of the remote print server

# Also all field names in the TXT records of DNS-SD-advertised printers
# are valid, like "color", "duplex", "pdl", ... If the field name of
# the filter rule does not exist for the printer, the rule is skipped.

# The optional <VALUE> field is either the exact value (when the
# option EXACT is supplied) or a regular expression (Run "man 7 regex"
# in a terminal window) to be matched with the data field.

# If no <VALUE> filed is supplied, rules with field names of the TXT
# record are considered for boolean matching (true/false) of boolean
# field (like duplex, which can have the values "T" for true and "F"
# for false).

# If the option NOT is supplied, the filter rule is fulfilled if the
# regular expression or the exact value DOES NOT match the content of
# the data field. In a boolean rule (without <VALUE>) the rule matches
# false.

# Regular expressions are always considered case-insensitive and
# extended POSIX regular expressions. Field names and options (NOT,
# EXACT) are all evaluated case-insensitive. If there is an error in a
# regular expression, the BrowseFilter line gets ignored.

# Especially to note is that supplying any simple string consisting of
# only letters, numbers, spaces, and some basic special characters as
# a regular expression matches if it is contained somewhere in the
# data field.

# If there is more than one BrowseFilter directive, ALL the directives
# need to be fulfilled for the remote printer to be accepted. If one
# is not fulfilled, the printer will get ignored.

# Examples:

# Rules for standard data items which are supplied with any remote
# printer advertised via DNS-SD:

# Print queue name must contain "hum_res_", this matches
# "hum_res_mono" or "hum_res_color" but also "old_hum_res_mono":

# BrowseFilter name hum_res_

# This matches if the remote host name contains "printserver", like
# "printserver.local", "printserver2.example.com", "newprintserver":

# BrowseFilter host printserver

# This matches all ports with 631 int its number, for example 631,
# 8631, 10631,...:

# BrowseFilter port 631

# This rule matches if the DNS-SD service name contains "@ printserver":

# Browsefilter service @ printserver

# Matches all domains with "local" in their names, not only "local" but
# also things like "printlocally.com":

# BrowseFilter domain local

# Examples for rules applying to items of the TXT record:

# This rule selects PostScript printers, as the "PDL" field in the TXT
# record contains "postscript" then. This includes also remote CUPS
# queues which accept PostScript, independent of whether the physical
# printer behind the CUPS queue accepts PostScript or not.

# BrowseFilter pdl postscript

# Color printers usually contain a "Color" entry set to "T" (for true)
# in the TXT record. This rule selects them:

# BrowseFilter color

# This is a similar rule to select only duplex (automatic double-sided
# printing) printers:

# BrowseFilter duplex

# Rules with the NOT option:

# This rule EXCLUDES printers from all hosts containing "financial" in
# their names, nice to get rid of the 100s of printers of the
# financial department:

# BrowseFilter NOT host financial

# Get only monochrome printers ("Color" set to "F", meaning false, in
# the TXT record):

# BrowseFilter NOT color

# Rules with more advanced use of regular expressions:

# Only queue names which BEGIN WITH "hum_res_" are accepted now, so we
# still get "hum_res_mono" or "hum_res_color" but not
# "old_hum_res_mono" any more:

# BrowseFilter name ^hum_res_

# Server names is accepted if it contains "print_server" OR
# "graphics_dep_server":

# BrowseFilter host print_server|graphics_dep_server

# "printserver1", "printserver2", and "printserver3", nothing else:

# BrowseFilter host ^printserver[1-3]$

# Printers understanding at least one of PostScript, PCL, or PDF:

# BrowseFilter pdl postscript|pcl|pdf

# Examples for the EXACT option:

# Only printers from "printserver.local" are accepted:

# BrowseFilter EXACT host printserver.local

# Printers from all servers except "prinserver2.local" are accepted:

# BrowseFilter NOT EXACT host prinserver2.local

# Use BrowsePoll to poll a particular CUPS server

# BrowsePoll cups.example.com
# BrowsePoll cups.example.com:631
# BrowsePoll cups.example.com:631/version=1.1

# LDAP browsing configuration
# The default value for all options is an empty string. Example configuration:

# BrowseLDAPBindDN cn=cups-browsed,dc=domain,dc=tld
# BrowseLDAPCACertFile /path/to/server/certificate.pem
# BrowseLDAPDN ou=printers,dc=domain,dc=tld
# BrowseLDAPFilter (printerLocation=/Office 1/*)
# BrowseLDAPPassword s3cret
# BrowseLDAPServer ldaps://ldap.domain.tld

# Use DomainSocket to access the local CUPS daemon via another than the
# default domain socket. "None" or "Off" lets cups-browsed not use CUPS'
# domain socket.

# DomainSocket /var/run/cups/cups.sock
# DomainSocket None
# DomainSocket Off

# Set HTTP timeout (in seconds) for requests sent to local/remote
# resources Note that too short timeouts can make services getting
# missed when they are present and operations be unneccessarily
# repeated and too long timeouts can make operations take too long
# when the server does not respond.

# HttpLocalTimeout 5
# HttpRemoteTimeout 10

# Set how many retries (N) should cups-browsed do for creating print
# queues for remote printers which receive timeouts during print queue
# creation.  The printers which are not successfuly set up even after
# N retries, are skipped until the next restart of the service.  Note
# that too many retries can cause high CPU load.

# HttpMaxRetries 5

# Set OnlyUnsupportedByCUPS to "Yes" will make cups-browsed not create
# local queues for remote printers for which CUPS creates queues by
# itself.  These printers are printers advertised via DNS-SD and doing
# CUPS-supported (currently PWG Raster and Apple Raster) driverless
# printing, including remote CUPS queues. Queues for other printers
# (like for legacy PostScript/PCL printers) are always created
# (depending on the other configuration settings of cups-browsed).

# With OnlyUnsupportedByCUPS set to "No", cups-browsed creates queues
# for all printers which it supports, including printers for which
# CUPS would create queues by itself. Temporary queues created by CUPS
# will get overwritten. This way it is assured that any extra
# functionality of cups-browsed will apply to these queues. As queues
# created by cups-browsed are permanent CUPS queues this setting is
# also recommended if applications/print dialogs which do not support
# temporary CUPS queues are installed. This setting is the default.

# OnlyUnsupportedByCUPS Yes

# With UseCUPSGeneratedPPDs set to "Yes" cups-browsed creates queues
# for IPP printers with PPDs generated by the PPD generator of CUPS
# and not with the one of cups-browsed. So any new development in
# CUPS' PPD generator gets available. As CUPS' PPD generator is not
# directly accessible, we need to make CUPS generate a temporary print
# queue with the desired PPD. Therefore we can only use these PPDs
# when our queue replaces a temporary CUPS queue, meaning that the
# queue is for a printer on which CUPS supports driverless printing
# (IPP 2.x, PDLs: PDF, PWG Raster, and/or Apple Raster) and that its
# name is the same as CUPS uses for the temporary queue
# ("LocalQueueNamingIPPPrinter DNS-SD" must be set). The directive
# applies only to IPP printers, not to remote CUPS queues, to not
# break clustering. Setting this directive to "No" lets cups-browsed
# generate the PPD file. Default setting is "No".

# UseCUPSGeneratedPPDs No

# With the directives LocalQueueNamingRemoteCUPS and
# LocalQueueNamingIPPPrinter you can determine how the names for local
# queues generated by cups-browsed are generated, separately for
# remote CUPS printers and IPP printers.

# DNS-SD (the default in both cases) bases the naming on the service
# name of the printer's advertised DNS-SD record. This is exactly the
# same naming scheme as CUPS uses for its temporary queues, so the
# local queue from cups-browsed prevents CUPS from listing and
# creating an additional queue. As DNS-SD service names have to be
# unique, queue names of printers from different servers will also be
# unique and so there is no automatic clustering for load-balanced
# printing.

# MakeModel bases the queue name on the printer's manufacturer and
# model names. This scheme cups-browsed used formerly for IPP
# printers.

# RemoteName is only available for remote CUPS queues and uses the
# name of the queue on the remote CUPS server as the local queue's
# name. This makes printers on different CUPS servers with equal queue
# names automatically forming a load-balancing cluster as CUPS did
# formerly (CUPS 1.5.x and older) with CUPS-broadcasted remote
# printers. This scheme cups-browsed used formerly for remote CUPS
# printers.

# LocalQueueNamingRemoteCUPS DNS-SD
# LocalQueueNamingRemoteCUPS MakeModel
# LocalQueueNamingRemoteCUPS RemoteName
# LocalQueueNamingIPPPrinter DNS-SD
# LocalQueueNamingIPPPrinter MakeModel

# Set DNSSDBasedDeviceURIs to "Yes" if cups-browsed should use
# DNS-SD-service-name-based device URIs for its local queues, as CUPS
# also does. These queues use the DNS-SD service name of the
# discovered printer. With this the URI is independent of network
# interfaces and ports, giving reliable connections to always the same
# physical device. This setting is the default.

# Set DNSSDBasedDeviceURIs to "No" if cups-browsed should use the
# conventional host-name/IP-based URIs.

# Note that this option has only influence on URIs for printers
# discovered via DNS-SD, not via legacy CUPS broewsing or LDAP.
# Those printers get always assigned the conventional URIs.

# DNSSDBasedDeviceURIs Yes

# Set IPBasedDeviceURIs to "Yes" if cups-browsed should create its
# local queues with device URIs with the IP addresses instead of the
# host names of the remote servers. This mode is there for any
# problems with host name resolution in the network, especially also
# if avahi-daemon is only run for printer discovery and already
# stopped while still printing. By default this mode is turned off,
# meaning that we use URIs with host names.

# Note that the IP addresses depend on the network interface through
# which the printer is accessed. So do not use IP-based URIs on systems
# with many network interfaces and where interfaces can appear and
# disappear frequently.

# This mode could also be useful for development and debugging.

# If you prefer IPv4 or IPv6 IP addresses in the URIs, you can set
# IPBasedDeviceURIs to "IPv4" to only get IPv4 IP addresses or
# IPBasedDeviceURIs to "IPv6" to only get IPv6 IP addresses.

# IPBasedDeviceURIs No
# IPBasedDeviceURIs Yes
# IPBasedDeviceURIs IPv4
# IPBasedDeviceURIs IPv6

# The AllowResharingRemoteCUPSPrinters directive determines whether a
# print queue pointing to a remote CUPS queue will be re-shared to the
# local network or not. Since the queues generated using the BrowsePoll
# directive are also pointing to remote queues, they are also shared
# automatically if the following option is set. Default is not to share
# remote printers.

# AllowResharingRemoteCUPSPrinters Yes

# The NewBrowsePollQueuesShared directive determines whether a print
# queue for a newly discovered printer (discovered by the BrowsePoll directive)
# will be shared to the local network or not. This directive will only work
# if AllowResharingRemoteCUPSPrinters is set to yes. Default is
# not to share printers discovered using BrowsePoll.

# NewBrowsePollQueuesShared Yes

# Set CreateRemoteRawPrinterQueues to "Yes" to let cups-browsed also
# create local queues pointing to remote raw CUPS queues. Normally,
# only queues pointing to remote queues with PPD/driver are created
# as we do not use drivers on the client side, but in some cases
# accessing a remote raw queue can make sense, for example if the
# queue forwards the jobs by a special backend like Tea4CUPS.

# CreateRemoteRawPrinterQueues Yes

# cups-browsed by default creates local print queues for each shared
# CUPS print queue which it discovers on remote machines in the local
# network(s). Set CreateRemoteCUPSPrinterQueues to "No" if you do not
# want cups-browsed to do this. For example you can set cups-browsed
# to only create queues for IPP network printers setting
# CreateIPPPrinterQueues not to "No" and CreateRemoteCUPSPrinterQueues
# to "No".

# CreateRemoteCUPSPrinterQueues No

# Set CreateIPPPrinterQueues to "All" to let cups-browsed discover IPP
# network printers (native printers, not CUPS queues) with known page
# description languages (PWG Raster, PDF, PostScript, PCL XL, PCL
# 5c/e) in the local network and auto-create print queues for them.

# Set CreateIPPPrinterQueues to "Everywhere" to let cups-browsed
# discover IPP Everywhere printers in the local network (native
# printers, not CUPS queues) and auto-create print queues for them.

# Set CreateIPPPrinterQueues to "AppleRaster" to let cups-browsed
# discover Apple Raster printers in the local network (native
# printers, not CUPS queues) and auto-create print queues for them.

# Set CreateIPPPrinterQueues to "Driverless" to let cups-browsed
# discover printers designed for driverless use (currently IPP
# Everywhere and Apple Raster) in the local network (native printers,
# not CUPS queues) and auto-create print queues for them.

# Set CreateIPPPrinterQueues to "LocalOnly" to auto-create print
# queues only for local printers made available as IPP printers. These
# are for example IPP-over-USB printers, made available via
# ippusbxd. This is the default.

# Set CreateIPPPrinterQueues to "No" to not auto-create print queues
# for IPP network printers.

# If queues with PPD file are created (see IPPPrinterQueueType
# directive below) the PPDs are auto-generated by cups-browsed based
# on properties of the printer polled via IPP. In case of missing
# information, info from the Bonjour record is used asd as last mean
# default values.

# If queues without PPD (see IPPPrinterQueueType directive below) are
# created clients have to IPP-poll the capabilities of the printer and
# send option settings as standard IPP attributes. Then we do not poll
# the capabilities by ourselves to not wake up the printer from
# power-saving mode when creating the queues. Jobs have to be sent in
# one of PDF, PWG Raster, or JPEG format. Other formats are not
# accepted.

# This functionality is primarily for mobile devices running
# CUPS to not need a printer setup tool nor a collection of printer
# drivers and PPDs.

# CreateIPPPrinterQueues No
# CreateIPPPrinterQueues LocalOnly
# CreateIPPPrinterQueues Everywhere
# CreateIPPPrinterQueues AppleRaster
# CreateIPPPrinterQueues Everywhere AppleRaster
# CreateIPPPrinterQueues Driverless
# CreateIPPPrinterQueues All

# If cups-browsed is automatically creating print queues for native
# IPP network printers ("CreateIPPPrinterQueues Yes"), the type of
# queue to be created can be selected by the "IPPPrinterQueueType"
# directive. The "PPD" (default) setting makes queues with PPD file
# being created. With "Interface" or "NoPPD" the queue is created with
# a System V interface script (Not supported with CUPS 2.2.x or
# later). "Auto" is for backward compatibility and also lets queues
# with PPD get created.

# IPPPrinterQueueType PPD
# IPPPrinterQueueType NoPPD
# IPPPrinterQueueType Interface
# IPPPrinterQueueType Auto

# The NewIPPPrinterQueuesShared directive determines whether a print
# queue for a newly discovered IPP network printer (not remote CUPS
# queue) will be shared to the local network or not. This is only
# valid for newly discovered printers. For printers discovered in an
# earlier cups-browsed session, cups-browsed will remember whether the
# printer was shared, so changes by the user get conserved. Default is
# not to share newly discovered IPP printers.

# NewIPPPrinterQueuesShared Yes

# If there is more than one remote CUPS printer whose local queue
# would get the same name and AutoClustering is set to "Yes" (the
# default) only one local queue is created which makes up a
# load-balancing cluster of the remote printers which would get this
# queue name (implicit class). This means that when several jobs are
# sent to this queue they get distributed between the printers, using
# the method chosen by the LoadBalancing directive.

# Note that the forming of clusters depends on the naming scheme for
# local queues created by cups-browsed. If you have set
# LocalQueueNamingRemoteCUPS to "DNSSD" you will not get automatic
# clustering as the DNS-SD service names are always unique. With
# LocalQueueNamingRemoteCUPS set to "RemoteName" local queues are
# named as the CUPS queues on the remote servers are named and so
# equally named queues on different servers get clustered (this is how
# CUPS did it in version 1.5.x or older). LocalQueueNamingRemoteCUPS
# set to "MakeModel" makes remote printers of the same model get
# clustered. Note that then a cluster can contain more than one queue
# of the same server.

# With AutoClustering set to "No", for each remote CUPS printer an
# individual local queue is created, and to avoid name clashes when
# using the LocalQueueNamingRemoteCUPS settings "RemoteName" or
# "MakeModel" "@<server name>" is added to the local queue name.

# Only remote CUPS printers get clustered, not IPP network printers or
# IPP-over-USB printers.

# AutoClustering Yes
# AutoClustering No

# Load-balancing printer cluster formation can also be manually
# controlled by defining explicitly which remote CUPS printers should
# get clustered together.

# This is done by the "Cluster" directive:

# Cluster <QUEUENAME>: <EXPRESSION1> <EXPRESSION2> ...
# Cluster <QUEUENAME>

# If no expressions are given, <QUEUENAME> is used as the first and
# only expression for this cluster.

# Discovered printers are matched against all the expressions of all
# defined clusters. The first expression which matches the discovered
# printer determines to which cluster it belongs. Note that this way a
# printer can only belong to one cluster. Once matched, further
# cluster definitions will not checked any more.

# With the first printer matching a cluster's expression a local queue
# with the name <QUEUENAME> is created. If more printers are
# discovered and match this cluster, they join the cluster. Printing
# to this queue prints to all these printers in a load-balancing
# manner, according to to the setting of the LoadBalancing directive.

# Each expression must be a string of characters without spaces. If
# spaces are needed, replace them by underscores ('_').

# An expression can be matched in three ways:

# 1. By the name of the CUPS queue on the remote server
# 2. By make and model name of the remote printer
# 3. By the DNS-SD service name of the remote printer

# Note that the matching is done case-insensitively and any group of
# non-alphanumerical characters is replaced by a single underscore.

# So if an expression is "HP_DeskJet_2540" and the remote server
# reports "hp Deskjet-2540" the printer gets matched to this cluster.

# If "AutoClustering" is not set to "No" both your manual cluster
# definitions will be followed and automatic clustering of
# equally-named remote queues will be performed. If a printer matches
# in both categories the match to the manually defined cluster has
# priority. Automatic clustering of equally-named remote printers is
# not performed if there is a manually defined cluster with this name
# (at least as the printers do not match this cluster).

# Examples:

# To cluster all remote CUPS queues named "laserprinter" in your local
# network but not cluster any other equally-named remote CUPS printers
# use (Local queue will get named "laserprinter"):

# AutoClustering No
# Cluster laserprinter

# To cluster all remote CUPS queues of HP LaserJet 4050 printers in a
# local queue named "LJ4050":

# Cluster LJ4050: HP_LaserJet_4050

# As DNS-SD service names are unique in a network you can create a
# cluster from exactly specified printers (spaces replaced by
# underscors):

# Cluster hrdep: oldlaser_@_hr-server1 newlaser_@_hr-server2

# The LoadBalancing directive switches between two methods of handling
# load balancing between equally-named remote queues which are
# represented by one local print queue making up a cluster of them
# (implicit class).

# The two methods are:

# Queuing of jobs on the client (LoadBalancing QueueOnClient):

# Here we queue up the jobs on the client and regularly check the
# clustered remote print queues. If we find an idle queue, we pass
# on a job to it.

# This is also the method which CUPS uses for classes. Advantage is a
# more even distribution of the job workload on the servers
# (especially if the printing speed of the servers is very different),
# and if a server fails, there are not several jobs stuck or
# lost. Disadvantage is that if one takes the client (laptop, mobile
# phone, ...) out of the local network, printing stops with the jobs
# waiting in the local queue.

# Queuing of jobs on the servers (LoadBalancing QueueOnServers):

# Here we check the number of jobs on each of the clustered remote
# printers and send an incoming job immediately to the remote printer
# with the lowest amount of jobs in its queue. This way no jobs queue
# up locally, all jobs which are waiting are waiting on one of the
# remote servers.

# Not having jobs waiting locally has the advantage that we can take
# the local machine from the network and all jobs get printed.
# Disadvantage is that if a server with a full queue of jobs goes
# away, the jobs go away, too.

# Default is queuing the jobs on the client as this is what CUPS does
# with classes.

# LoadBalancing QueueOnClient
# LoadBalancing QueueOnServers

# With the DefaultOptions directive one or more option settings can be
# defined to be applied to every print queue newly created by
# cups-browsed. Each option is supplied as one supplies options with
# the "-o" command line argument to the "lpadmin" command (Run "man
# lpadmin" for more details). More than one option can be supplied
# separating the options by spaces. By default no option settings are
# pre-defined.

# Note that print queues which cups-browsed already created before
# remember their previous settings and so these settings do not get
# applied.

# DefaultOptions Option1=Value1 Option2=Value2 Option3 noOption4

# The AutoShutdown directive specifies whether cups-browsed should
# automatically terminate when it has no local raw queues set up
# pointing to any discovered remote printers or no jobs on such queues
# depending on AutoShutdownOn setting (auto shutdown mode). Setting it
# to "On" activates the auto-shutdown mode, setting it to "Off"
# deactiivates it (the default). The special mode "avahi" turns auto
# shutdown off while avahi-daemon is running and on when avahi-daemon
# stops. This allows running cups-browsed on-demand when avahi-daemon
# is run on-demand.

# AutoShutdown Off
# AutoShutdown On
# AutoShutdown avahi

# The AutoShutdownOn directive determines what event cups-browsed
# considers as inactivity in auto shutdown mode. "NoQueues" (the
# default) means that auto shutdown is initiated when there are no
# queues for discovered remote printers generated by cups-browsed any
# more. "NoJobs" means that all queues generated by cups-browsed are
# without jobs.

# AutoShutdownOn NoQueues
# AutoShutdownOn NoJobs

# The AutoShutdownTimeout directive specifies after how many seconds
# without local raw queues set up pointing to any discovered remote
# printers or jobs on these queues cups-browsed should actually shut
# down in auto shutdown mode. Default is 30 seconds, 0 means immediate
# shutdown.

# AutoShutdownTimeout 30

$ avahi-resolve --version
avahi-resolve 0.7

The bug appear to be in  cups-browsed.
You can try adding the printer manually after uninstalling the cups-browsed and then check if it prints or not.
Uninstall the cups-browsed.
sudo apt-get purge --autoremove cups-browsed
Now add the printer manually.
Check if the printing works now.

@abergmeier, could you try the newest release of cups-filters, 1.28.6? I have done some performance improvements on cups-browsed. Does this work for you?

I installed 1.28.6 from hirsute.
Then did:
service cups-browsed restart
service cups restart

Afterwards it for now seems to works.

I installed 1.28.6 from hirsute.
Then did:
service cups-browsed restart
service cups restart

Afterwards it for now seems to works.

And it breaks again.
So the temporary workaround is:
service cups-browsed restart
service cups restart

1.28.6 did not fix it.

And it breaks again.
So the temporary workaround is:
service cups-browsed restart
service cups restart

1.28.6 did not fix it.

Getting this quite often.  Used to restart the entire system; but now, the systemd restart commands noted above seem to work - for a little while.
Pop!_os 21.10 (about to upgrade soon; but, it's newer cups than posted above - and same issues).
cups-browsed/impish,now 1.28.10-2 amd64 [installed,automatic]
cups-bsd/impish-security,impish-updates,now 2.3.3op2-7ubuntu2.1 amd64 [installed,automatic]
cups-client/impish-security,impish-updates,now 2.3.3op2-7ubuntu2.1 amd64 [installed,automatic]
cups-common/impish-security,impish-security,impish-updates,impish-updates,now 2.3.3op2-7ubuntu2.1 all [installed,automatic]
cups-core-drivers/impish-security,impish-updates,now 2.3.3op2-7ubuntu2.1 amd64 [installed,automatic]
cups-daemon/impish-security,impish-updates,now 2.3.3op2-7ubuntu2.1 amd64 [installed,automatic]
cups-filters/impish,now 1.28.10-2 amd64 [installed,automatic]
cups-filters-core-drivers/impish,now 1.28.10-2 amd64 [installed,automatic]
cups-ipp-utils/impish-security,impish-updates,now 2.3.3op2-7ubuntu2.1 amd64 [installed,automatic]
cups-pk-helper/impish,now 0.2.6-1ubuntu4 amd64 [installed,automatic]
cups-ppdc/impish-security,impish-updates,now 2.3.3op2-7ubuntu2.1 amd64 [installed,automatic]
cups-server-common/impish-security,impish-security,impish-updates,impish-updates,now 2.3.3op2-7ubuntu2.1 all [installed,automatic]


asls: 0.4.0 -> 0.4.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/saulecabrera/asls/releases.
meta.description for asls is: "AssemblyScript Language Server"
meta.homepage for asls is: "https://github.com/saulecabrera/asls"
meta.changelog for asls is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.4.2 with grep in /nix/store/gqmpcn1gy7y88sglfgl1i5amqn1fnpw1-asls-0.4.2

directory tree listing: https://gist.github.com/469d2cdbaf35bf062e092889b508b1c9

du listing: https://gist.github.com/cd4687ba0110aee513fbb85531e0e967

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
asls

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gqmpcn1gy7y88sglfgl1i5amqn1fnpw1-asls-0.4.2 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A asls https://github.com/r-ryantm/nixpkgs/archive/447c94f40c9820ca2eff28fd3cc415660732dfd2.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gqmpcn1gy7y88sglfgl1i5amqn1fnpw1-asls-0.4.2
ls -la /nix/store/gqmpcn1gy7y88sglfgl1i5amqn1fnpw1-asls-0.4.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package built:

asls

Maintainer pings
cc @saulecabrera for testing.

/marvin opt-in

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/201


Some images not showing

I'm using a data template to show different images in android. They are all png's in the Resources/drawable folder, and I use the same source call to implement them, but only two of them show up. Are there any hidden requirements about what the image needs to be? All of them are 512x512, the same color and everything. The only difference is that the image is different

@sirwes please use Help > Send Feedback > Report a Problem in Visual Studio to submit issues and bug reports to the developer community site. This feedback is intended for dealing with issues in the docs, thanks.


SampleSet.to_pandas_dataframe fails for record arrays with fields of more than one dimension

https://github.com/dwavesystems/dimod/pull/963 was an attempt to fix this issue, but that approach fails. More investigation needed.
Failing examples
        samples = dimod.SampleSet(
            np.rec.array([([0.], 1., 1,  True, [])],
                         dtype=[('sample', '<f8', (1,)), ('energy', '<f8'),
                                ('num_occurrences', '<i4'), ('thing1', '?'),
                                ('thing2', '?', (0,))]),
            ['a'], {}, 'INTEGER')

        samples = dimod.SampleSet(
            np.rec.array([([0.], 1., 1,  True, []), [([0.], 1., 1,  True, []), [([0.], 1., 1,  True, [])],
                         dtype=[('sample', '<f8', (1,)), ('energy', '<f8'),
                                ('num_occurrences', '<i4'), ('thing1', '?'),
                                ('thing2', '?', (0,))]),
            ['a'], {}, 'INTEGER')

Note that even pandas.DataFrame.from_records fails for this case.


chore: bdd-spring-1584971734 to 0.0.1

chore: Promote bdd-spring-1584971734 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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


[No-code] Write an article on "Roadmap to Cybersecurity"

Hey please assign this to me

@AdityaShaw1 you still up for this?

hii please assign me

Yes I m submitting by today only

@jay-io

Have you made a PR?

@Debdeep1 can I work on it? I'd love to write a article on cybersecurity

@Debdeep1 can I work on it? I'd love to write an article on cybersecurity

Please assign it to me, I'll raise a PR ASAP

@rudrakshkarpe Today is the last day for hacktoberfest plz raise the pr before 7pm IST.

Sorry for delay I'll raise a PR within next 1 HR

Sorry for the delay I'll raise a PR within the next 1 HR

As my exams are going around I could raise a tentative PR before12 which will be considered under Hacktoberfest I guess
I'll make the required changes with commits in the same PR
I truly apologize for the inconvenience caused

@rudrakshkarpe I hope it's Greenwich time. Thank you for contributing!


[TOPIC-GPIO] drivers: stellaris: update to use new GPIO API

Update driver code and board files to use new GPIO configuration flags
such as GPIO_ACTIVE_LOW. Also add implementation of new port_* driver
API as well as gpio_pin_interrupt_configure function.
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

AFAICT this platform exists only as a basis for qemu_cortex_m3, which says:
.. note::
   This board configuration makes no claims about its suitability for use
   with an actual ti_lm3s6965 hardware system, or any other hardware system.

Why are we keeping this?

Seems like this PR was rebased but no changes to the driver code were applied.

Seems like this PR was rebased but no changes to the driver code were applied.

should be fixed now.

It seems like it's again the same version, no changes.

Line 194 should be changed.  That was the only review comment that was made.

I've opened the PR in another browser, just in case, still the line 194 is written as
	sys_write32(GPIO_RW_MASK_ADDR(base, GPIO_DATA_OFFSET, value), mask);

which is the original. I believe it should be written as
	sys_write32(value, GPIO_RW_MASK_ADDR(base, GPIO_DATA_OFFSET, mask));

since
void sys_write32(u32_t data, mem_addr_t addr);

Apart from line 194 also gpio_stellaris_configure function should also be updated.

I've opened the PR in another browser, just in case, still the line 194 is written as
	sys_write32(GPIO_RW_MASK_ADDR(base, GPIO_DATA_OFFSET, value), mask);

which is the original. I believe it should be written as
	sys_write32(value, GPIO_RW_MASK_ADDR(base, GPIO_DATA_OFFSET, mask));

since
void sys_write32(u32_t data, mem_addr_t addr);

Apart from line 194 also gpio_stellaris_configure function should be updated.

Gotcha, sorry bit a little while since I worked on the driver.  Should now hopefully be fixed correctly.

It worked. However, we also need to update gpio_stellaris_configure function. It contains old interrupt configuration code and is using deprecated masks, like GPIO_DIR_IN.

It worked. However, we also need to update gpio_stellaris_configure function. It contains old interrupt configuration code and is using deprecated masks, like GPIO_DIR_IN.

Should now be updated.

Not sure I follow where in the code we should handle 'disconnected' mode.
Was thinking we'd have:
if (flags & INPUT)
...
else if (flags & OUTPUT)
...
else
/* disconnect */


Feature request: Print the date of the last tile update in the information screen.

As per the feateure request title. On top of giving the 'users' a bearing on when the next run of tile updates will be it will doubtlessly also reduce the senseless Crtl+F5 to refresh the fetched data.
(if already somewhere, apologies for missing to discover this info snip).

Introduced in today's update, thank you for the suggestion.


matchResponseProperty incorrect asynchronous responses shown

Hi,
I have started using the autocomplete on my new site and I have found a problem where the incorrect results for the entered search term are shown. The matchResponseProperty does not correctly work. The issue can be recreated by making two remote requests for data and having the first request response after the second. For example make two requests for "Tes" and "Test", if "Test" responses first the autocomplete will show the correct results. However when the response for "Tes" arrives after, these results are shown, this is incorrect as the input box contains "Test". This issue particularly affects mobile connections with slow connections.
The error comes about because the inputPhrase is captured before the ajax request and is not reread from the input box on the ajax response. I have replaced this functionality with a simple counter "remoteRequestCount". The counter is captured into a local variable and then rechecked against the state. This also has the befits of not having the users having to include matchResponseProperty in there servers response.
I am sorry but I have only altered the source files. I am an expired developer but not in the javascript world and could not get my grunt build going in the time I had.
Thank you
Dan

I am also facing this bug, I think it is better if EasyAutoComplete can cancel previous requests, if another request is created. Just like this library: http://autocomplete-js.com/


Support for storybook for web based react

Is it possible to use your plugin with non-react native storybook?
If not, do you have plans to add such support, i think that feature would make sense to be implemented?

Isolated development of components in web already works with storybook. Unless I'm missing the point?


[propose] More independent e2e test.

Issue Description
Let me describe the way how we start e2e tests for sealer.

Request ecs from alicloud.
Run tests over the ecs.

There are some major problems for such approach of test, and there are some drawbacks in our way of testing.

High cost: this is dependent on the resource from alicloud extremely.
Absense of local test: Developers can only had their changes tested after the code gets pushed.
Test context is not independent: Take test apply as a example. In this test, sealer will pull an online image(registry.cn-qingdao.aliyuncs.com/sealer-io/kubernetes:v1.19.8) to execute apply. But I guess the image in test should be basical context, which means we'd better build a image before going to apply.

Describe what feature you want
I hope we can abandon the dependency for resource of alicloud.
At every e2e test, we start a registry, start some vms(contaienrs). There are basical context for sealer test.
And we build/apply/run over the vms. I think this job is not hard, and there are many available open source tools could help us out.

@zhy76 How about taking this work?
And I will split some todos to help you get this whole work done.

OK！

@zhy76
Here are my considerations for spilting the work.
There could be some steps to do probably.
Test context infra
Currently, the test context infra is launching ecs from alicloud. I hope to remove the dep.

[ ] Set up nodes: We could launch a set of contaienrs to simulate nodes for cluster deploying. So we could provide a basic ability in sealer, that is setting up test context with containers in standalone. You could create a pkg test/testinfra or something else in sealer/pkg. And in this pkg, we are able to launch test context. (We can learn from kind to know how they set up containers. Be aware of that what kind can do is deploying cluster in containers, but what we need is setting up containers to provide a test environment in standalone.)
[ ] Details: (1) Docs: Requirements for sealer e2e test. (like install docker...) (2) Containers network configuration.

E2e test context switching
When you finish the Test context infra, we could start to switch the current context to your implementation. The community will help you do this job. Your major responsiblity is Test context infra, which is important to sealer.
/cc @sealerio/sealer-maintainers @sealerio/sealer-reviewers


Decide how best to map types of MAT vacancies onto current vacancy model

Background
MAT Vacancies can be at the trust head office, multiple schools or just a single school.  Need to work out how to best model this simply in the current vacancy model.
Further details to follow. Not for refinement yet.
(TEVA-757) (TEVA-680)

Superseded by #1731


:rainbow:, pos_logout

Handled tour of module functionality;

Travis says there are wrong version numbers in readme
Add licences for test files

Travis says there are wrong version numbers in readme
Add licences for test files

I approve to merge it now


"Signature: PackageIsUnreadable" error when attempting to install extension

Current editor / operating system information:
Version: 1.77.0-insider
Commit: 155cd6db223feb1f8c734ca70e108b9efec7b054
Date: 2023-03-02T12:46:14.548Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 22.3.0
Sandboxed: Yes
Steps to reproduce:

Open the extensions tab
Click the Install button

Errors
Here's the relevant log messages:
2023-03-02 15:38:05.570 [info] Getting Manifest... ms-azuretools.vscode-azurefunctions
2023-03-02 15:38:06.160 [info] Installing extension: ms-azuretools.vscode-azurefunctions
2023-03-02 15:38:06.592 [info] Getting Manifest... ms-vscode.azure-account
2023-03-02 15:38:07.170 [info] Getting Manifest... ms-azuretools.vscode-azureresourcegroups
2023-03-02 15:38:07.372 [info] Installing extension: ms-vscode.azure-account ms-azuretools.vscode-azurefunctions
2023-03-02 15:38:07.373 [info] Installing extension: ms-azuretools.vscode-azureresourcegroups ms-azuretools.vscode-azurefunctions
2023-03-02 15:38:08.419 [error] Error while installing the extension: ms-vscode.azure-account
2023-03-02 15:38:08.423 [error] Failed to install extension. ms-azuretools.vscode-azurefunctions
2023-03-02 15:38:08.424 [error] Signature: PackageIsUnreadable
    at ki.download (/vscode/vscode-server-insiders/bin/linux-x64/155cd6db223feb1f8c734ca70e108b9efec7b054-insider/out/vs/server/node/server.main.js:153:468)
    at async Q.x (/vscode/vscode-server-insiders/bin/linux-x64/155cd6db223feb1f8c734ca70e108b9efec7b054-insider/out/vs/server/node/server.main.js:153:20769)
    at async Q.h (/vscode/vscode-server-insiders/bin/linux-x64/155cd6db223feb1f8c734ca70e108b9efec7b054-insider/out/vs/server/node/server.main.js:153:18910)
2023-03-02 15:38:09.431 [error] Signature: PackageIsUnreadable
    at ki.download (/vscode/vscode-server-insiders/bin/linux-x64/155cd6db223feb1f8c734ca70e108b9efec7b054-insider/out/vs/server/node/server.main.js:153:468)
    at async Q.x (/vscode/vscode-server-insiders/bin/linux-x64/155cd6db223feb1f8c734ca70e108b9efec7b054-insider/out/vs/server/node/server.main.js:153:20769)
    at async Q.h (/vscode/vscode-server-insiders/bin/linux-x64/155cd6db223feb1f8c734ca70e108b9efec7b054-insider/out/vs/server/node/server.main.js:153:18910)

I see that you're running VS Code-Insiders, could you please try reproducing this with the VS Code stable release and let us know if it resolves your issue?  We suspect this is related to the Insiders update.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


WIP Signature test

Description

Testing instructions

Types of changes

Checklist

[ ] Prefix PR title with [WIP] if necessary.
[ ] Add tests to cover changes as needed.
[ ] Update documentation as needed.

sorry, accidently sent this, please reference https://github.com/TrustWallet/wallet-core/pull/107

Resolving merge conflicts...


expect_spaceship() tests

closes #68

Adding them anyway, in addition to the generated ones. One of the benefit is that this is easier to iterate with them.


Adding Weapon Sounds

Pew pew!

Check out SpreadEagle weapon, it has a demo for adding a sound in latest commit.


No provider for Location

On a fresh angular-cli project, after you get everything to work, if you use Location from @angular/common the bootstrap will fail with the message 'No provider for Location!` which doesn't happen on a regular angular-cli web app.
Thanks In advance.

Closed because this is probably a by-product of #23

Fixed here, note new repo and install:
https://github.com/wwwalkerrun/nativescript-ngx-magic


[Question] Connect-PnPOnline only works with PnPManagementShell?

Will this version of PnP-PowerShell only work with the PnPManagementShell? Or own custom App registration?
For my organization tenants I  am not allowed to add the PnPManagementShell permissions to my account in Azure AD.
So we just want to use an account that is SharePoint administrator.

you can use custom app registrations, no problem at all.

So an app registration or the PnPManagementShell is a must? Username password is no longer supported?


Better output format from WinRM shell

WinRM communicator appears to send output back periodically to Vagrant in an ugly XML format. Make this nicer so output back to the user is sensible.

Can we do something like this? http://msdn.microsoft.com/en-us/library/aa384351(v=vs.85).aspx

Possibly, from memory it was difficult to get access to the XML due to the way it was being slurped by the WinRM communicator. I'll investigate (it does bug me!).

Commit fd01df558738935d402e5f8c198695f62887744b fixes this. New version v1.0.5 of gem released.


Extension Compatability support

Hello! So I heard that this extension is Firefox Compatible. I was wondering how I could install this extension for Firefox?

You need a signed .xpi file. You can make one yourself or use the one I've uploaded here. Then, go to about:addons, click the gear icon, select "Install from file" and finally select the xpi.

You need a signed .xpi file. You can make one yourself or use the one I've uploaded here. Then, go to about:addons, click the gear icon, select "Install from file" and finally select the xpi.

Ah thx, I'm not too good with building stuff from scratch! Thanks ^^


tables_initializer

sess_id.run(graph_id.get_operation_by_name("MyGraphID/init_all_tables"))
I did not find a way to achieve this in C ++. what should I do？

@tianhongbao
This question is better asked on StackOverflow since it is not a bug or feature request. There is also a larger community that reads questions there and provide better and faster support for such issues. Thanks!

I am closing the issue as this issue not related to bug/performance.Please, ask this question in StackOverflow. Thanks!


Exception when search for model which user is meta-llama

Hello, when searching for meta-llama, I'm having an exception.
Version used:  @huggingface/hub - 0.8.5
Here's the link for example: https://codesandbox.io/s/determined-black-t6plln?file=/src/App.tsx:812-1369
    const listAllModels = async () => {
      const username = "meta-llama";
      const result: Record<string, unknown> = {};
      const limit = 3;
      var curr = 0;
      console.log(`Fetching ${username}`);
      for await (const model of listModels({
        search: { owner: username },
      })) {
        const fileMap = await listFilesByName(model.name);
        result[model.name] = {
          model,
          fileMap
        };

        curr++;
        if (curr >= limit) break;
      }
      console.log("Result: ", username, result);
    };

thank you!


How to use config files for tools?

When using tools like ruff, mypy, pytest etc., I am using config files, such as ruff.toml or dedicated sections in pyproject.toml file.
If installing these tools via uv tool install, where am I supposed to put the respective configurations?
Also, I need to make sure that all team members do have the same settings, which is probably not as easy as putting them into a concrete project repo, isn't it?

It depends on the tool. Ruff, for example, supports user-level configuration: https://docs.astral.sh/ruff/faq/#how-can-i-change-ruffs-default-configuration. So you'd put it at ~/.config/ruff/ruff.toml. Or, you can put a ruff.toml at the root of each project (or anywhere on the filesystem really) and Ruff will discover it when checking those files.
MyPy almost always needs to be installed into the virtual environment that it's type-checking, so it generally doesn't make sense to install as a tool.
(I'm not certain on how pytest configuration works, but again, it probably makes sense for that to be a project dev dependency rather than a tool.)

For people who end up here I want to give an example. If you want to configure ruff you can just add some dedicated sections [tool.ruff*] to your pyproject.toml created by uv like so
[project]
name = "example"
version = "0.1.0"
description = "Add your description here"
readme = "README.md"
authors = [
    { name = "anonymous", email =<EMAIL_ADDRESS>}
]
requires-python = ">=3.11"
dependencies = [
    "python-dotenv>=1.0.1",
]

[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"

[dependency-groups]
dev = [
    "pytest>=8.3.4",
    "ruff>=0.8.1",
]

[tool.ruff]
target-version = "py311"
line-length = 120

[tool.ruff.lint]
extend-select = ["E", "F"]

Then you can just run ruff
uv run ruff check

and it will pick up your configuration from the pyproject.toml.
See also

https://docs.astral.sh/ruff/configuration/


Elastic listens to attribute set as false

This will allow an element to be used in a template without having to specify the element twice using a ng-switch.

Any reason that this hasn't been merged? @monospaced

Hi thanks for the contribution :+1:
Sorry, I'm not clear on the use case for this, could you explain it for me?
Thanks.

currently you are only able to set an attribute to be attached to the directive if you want Elastic on however, if you want to be able to disable currently it's not possible and instead allows setting as true or false dynamically.


Support YAML output

The YAML swagger is easier to read and less lines so let's offer that as an option.

Turns out there's a problem with this. It converts the JSON bodies of the example responses into YAML. I think they should probably be stored as strings.


[FFmpeg-QSV][Decode][ICL][YUY2] undefined behaviour occurs due to GetFramePointerChecked

CMDLINE:
ffmpeg -hwaccel qsv -hwaccel_device /dev/dri/renderD128 -v verbose -c:v hevc_qsv -load_plugin hevc_hw -i ./422-uf.hevc -vf hwdownload,format=yuyv422 -pix_fmt yuyv422 -vsync passthrough -vframes 50 yuy2.yuv
Current work around patch in ffmpeg to enable YUY2 decode:
https://github.com/fulinjie/ffmpeg/commit/95d386dd4f340c65d7bae067726aba0012320d3b
Error Message:
AVHWFramesContext @ 0x1d478c0] Error synchronizing the operation: -16
[hwdownload @ 0x1b7c2c0] Failed to download frame: -1313558101.
Error while filtering: Unknown error occurred
Failed to inject frame into filter network: Unknown error occurred
Error while processing the decoded data for stream #0:0
Analysis:
In VAAPIVideoCORE::DoFastCopyExtended, GetFramePointerChecked is called to check Data and pitch for pSrc and pDst.
https://github.com/Intel-Media-SDK/MediaSDK/blob/b1c624e14660e3fa33302f98f84915cef4fee4e3/_studio/shared/src/libmfx_core_vaapi.cpp#L1144
However, for YUY2 format, only Data.Y is needed, but all Y && U && V is checked in:
https://github.com/Intel-Media-SDK/MediaSDK/blob/b1c624e14660e3fa33302f98f84915cef4fee4e3/_studio/mfx_lib/shared/src/mfx_common_int.cpp#L477
And the pitch can be empty, so this could also block the decode:
https://github.com/Intel-Media-SDK/MediaSDK/blob/b1c624e14660e3fa33302f98f84915cef4fee4e3/_studio/mfx_lib/shared/src/mfx_common_int.cpp#L956
Current work around in MSDK to make the decode success:
https://github.com/fulinjie/MediaSDK/commit/13488cc60f2caccb5fb8fec89fd569a63f03e8ca
Ps:
These PRs are temporal, and only used to describe this issue better and the possible way to fix this. Will be refined.

It seems that these issues could be work around at FFmpeg level when map frame to surface:
https://github.com/intel-media-ci/ffmpeg/pull/43
Closed.


Using term dwc:vitality on the IPT

I'm working with a dataset of wildlife strandings, I just found that the vitality term was adopted I tried to update our strandings dataset but while mapping the Occurrence Core there wasnt a Vitality term on the IPT.
Maybe there is another Core in which this term should be mapped?

Thank you for contacting us.
As far as I know dwc:vitality is not yet supported by GBIF.
@MattBlissett

The IPT definitions have not yet been updated to contain the 2023 changes of DwC. I can't see why this should not be done immediately so they become available in IPTs even if GBIF doesn't support all new terms yet.
There apparently is an open pull request to do so: https://github.com/gbif/rs.gbif.org/pull/111

So what is the right way to ask for the pull request to be approved?

If it helps to know, we're preparing the GBIF UAT environment now to support all terms and we'll prepare some test datasets to verify everything works. That will remain in test for around 4 weeks because we're heading into a very busy time with TDWG and the GBIF governing board, and because it includes changes to the date range interpretation . In early November, we anticipate GBIF.org and IPTs being fully up to date with the latest DwC.
It may be possible to release the IPT schemas to production earlier, but we need to verify if those changes will break anything in the existing GBIF ingestion.

Thank you for the update.

related https://github.com/gbif/pipelines/issues/926

Hi all,
The new terms are now ready for use in the IPT, and will be interpreted and shown on GBIF.org and in the API.


Meta test improve

Meta test improve

Codecov Report

Merging #1039 (5e19a33) into main (8350cf0) will increase coverage by 6.09%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #1039      +/-   ##
============================================
+ Coverage     42.71%   48.81%   +6.09%
  Complexity      149      149
============================================
  Files           146      146
  Lines         23726    25049    +1323
  Branches        422      422
============================================
+ Hits          10135    12227    +2092
+ Misses        12280    11474     -806
- Partials       1311     1348      +37

Impacted Files
Coverage Δ

pkg/chunk/utils_unix.go
53.33% <0.00%> (-20.01%)
:arrow_down:

pkg/meta/interface.go
51.72% <0.00%> (+2.58%)
:arrow_up:

pkg/meta/redis.go
74.63% <0.00%> (+5.34%)
:arrow_up:

cmd/mount.go
6.86% <0.00%> (+6.86%)
:arrow_up:

pkg/meta/tkv.go
82.60% <0.00%> (+10.07%)
:arrow_up:

pkg/meta/dump.go
80.79% <0.00%> (+11.00%)
:arrow_up:

pkg/meta/sql.go
78.30% <0.00%> (+11.97%)
:arrow_up:

pkg/meta/openfile.go
92.59% <0.00%> (+15.74%)
:arrow_up:

pkg/fs/fs.go
76.02% <0.00%> (+54.56%)
:arrow_up:

pkg/meta/metrics.go
100.00% <0.00%> (+100.00%)
: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 8a385ff...5e19a33. Read the comment docs.


Add an Info Sheet/Cover Page for exports to explain colored text

Description
Colored text is unclear to users.  An info sheet or cover letter is needed to explain what the color(s) signify
Describe the solution you'd like
Create sheet with table explaining colors used in text
Describe alternatives you've considered
A table within the existing templates could also be used, but the concern is that users might easily overlook the table.  By using an entire sheet there is a higher chance of the user reading the text
Additional context
Feedback from Tomasz' DMP class.

Draft of the cover sheet text for the FWF template:

@ValentinFutterer, please check if the examples given are still valid.

Draft looks good, it covers everything important.
DELETE II can be removed, since the table is being already deleted and we can do the same for the green text.

Thanks. And what about deleting the FWF guide (part 2 in Delete III), is this still an open issue in DAMAP?
Are you planning to add such an information page to the DAMAP FWF template soon, or should we do this in the TU Wien DMP Tool template?

Good point: We should be able to do it this sprint, if you want. Then it will be in the next DMP Tool release.


BREAKING CHANGE(web): Enhance custom height and max height options of ModalDialog #DS-1134

Description

Custom height and custom max height can be set individually on all breakpoints now.
The --modal-preferred-height-mobile and --modal-preferred-height-tablet custom properties were renamed.

Additional context

Issue reference
https://jira.almacareer.tech/browse/DS-1134

coverage: 79.967%. remained the same
when pulling b2e7e00952aebb2b2bbfd3bcd4c9b48e3023f98d on bc/modal-custom-height
into cf7db9c45404a10f47ce6829fce84887962b04ff on bc/modal-scrolling.