Schema mismatch for read only open async.

When an app opens a sync Realm with asyncOpen, it receives the initial schema with the
initial download from the server.
If the app has a schema with extra columns compared to the server's schema, the app will
add the extra columns and upload them to the server.
If the permission to the server Realm is read-only, this chain of events lead to a permission dnied error from the server.
A better behavior would be that the client issues a "schema mismatch" error. This behavior would make it easier for the app developer to debug the problem.
In summary: Issue a "schema mismatch" error after async open returns if the Realm is read-only and the app schema contains extra columns.
See the issue
https://github.com/realm/realm-object-server/issues/259#issuecomment-348319532
for an example.

Moved to https://github.com/realm/realm-core/issues/4610


feat: credential branding update

Update with new branding assets and bundle configurations

Hold merging until mediator update is complete


Fix game processes being in a zombie state when exiting

This fixes the game processes going into a zombie state when they exit on Unix systems.
We weren't properly waiting for their exit so this goes and fixes that.
The thread spawning approach may not be the best, but it works for this and we can think of an other solution if needed at some point.

Should be better now, sorry about the little mess ups!


Added fn to select data loader (instead of Mnist hardcoded in train.py)

Hi,
Created initial proposal for selecting data loader in configuration file.
Overview:

User can select data loader in configuration file
New data loaders are (for now*) written in 'data_loader.data_loaders.py'
Currently, the function 'get_data_loader' needs to be manually when adding new loaders (in addition to writing the loader class)

I propose this as a first step that we can build further on**.
Comment:
*: I guess we over time can implement functionality to load loaders from new files inside the 'data_loader' module (if someone prefers to create 'data_loader/my_new_loader.py')
**: I plan to implement another data loader that potentially can work as another example in the template. Will post when this is done.

Hi @victoresque ,
Sure, I can update the README. I guess the three bullets I wrote above are more or less sufficient?
Additional question:
I began looking at adding a data loader and realized that I actually do not need a data loader, but only a dataset class. I may use the torch built in data loader (at least as a start).
Where are custom dataset classes intended to be placed? Currently the folder 'datasets' is intended to contain actual data...
Two alternatives I see:

Place both datasets and loaders into 'dataloader' folder
Make the standard folder for data a new folder 'data', then use the 'datasets' folder the place to place custom dataset classes

What do you think?

Hi,
I prefer the second alternative, since the name data is more general than datasets
If data loaders are not needed to be re-implemented (use torch built-in), maybe you can put datasets and data_loader into a folder data_utils?
Then the folder structure would be somewhat similar to:
...
├── data_utils/ - data utilities
│   ├── data_loaders.py
│   ├── datasets.py
│   └── your_custom_dataset.py
├── data/ - default data folder
...

or even simpler:
...
├── data_utils/ - data utilities
│   ├── data_utils.py
│   └── your_custom_dataset.py
├── data/ - default data folder
...

You can try to figure out the better way among these options, thanks

Hi,
If you merge this pull request, I can do the requested update of the README.md separately (easier workflow for me, as I merged from my master branch).
Hope this is ok with you.

OK, I'll do that

Thank you @SunQpark. Next pull request sent (updating loss.py).


build error on windows10

I tried built it on debain10,it woirks.
but on wondows10,it seems have problem,the following files in my C:\ta-lib :
C:\ta-lib

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d-----        2021/11/18     16:33                c
d-----        2021/11/18     16:33                dotnet
d-----        2021/11/18     16:33                excel
d-----        2021/11/18     16:33                java
d-----        2021/11/18     16:33                swig
-a----         2007/9/12     14:12            965 CHANGELOG.TXT
-a----         2007/9/12     14:12           3938 HISTORY.TXT
-a----         2007/1/27     23:19           1509 LICENSE.TXT
-a----         2007/1/27     23:19           4086 LICENSE_EXCEL.TXT
-a----         2007/1/27     23:31           1392 README.TXT
-a----          2007/9/8     18:37         184912 ta_func_api.xml
-a----         2007/2/11     17:25          11526 ta_func_api.xsd
-a----          2007/9/8     18:37           7003 ta_func_list.txt

After I run go build, the terminal shows:
# github.com/d4l3k/talib
xxx\go\pkg\mod\github.com\d4l3k\talib@v0.0.0-20180425021108-1b10e6a1ad95\generated.go:4:11: fatal error: ta-lib/ta_libc.h: No such file or directory
    4 | // #include "ta-lib/ta_libc.h"
      |           ^~~~~~~~~~~~~~~~~~
compilation terminated.

I tried move C:\ta-lib\c to C:\ta-lib,the error  is the same.I found ta_libc.h in dir ta-lib\c\include,maybe I made a mistake with the C code dir.
Thank you.

I've never used cgo on windows so I'm not sure how to fix this, sorry! Will
accept any fixes though
On Thu, Nov 18, 2021, 00:47 deviceGT @.***> wrote:

I tried built it on debain10,it woirks.
but on wondows10,it seems have problem,the following files in my C:\ta-lib
:
C:\ta-lib
Mode                 LastWriteTime         Length Name

d-----        2021/11/18     16:33                c
d-----        2021/11/18     16:33                dotnet
d-----        2021/11/18     16:33                excel
d-----        2021/11/18     16:33                java
d-----        2021/11/18     16:33                swig
-a----         2007/9/12     14:12            965 CHANGELOG.TXT
-a----         2007/9/12     14:12           3938 HISTORY.TXT
-a----         2007/1/27     23:19           1509 LICENSE.TXT
-a----         2007/1/27     23:19           4086 LICENSE_EXCEL.TXT
-a----         2007/1/27     23:31           1392 README.TXT
-a----          2007/9/8     18:37         184912 ta_func_api.xml
-a----         2007/2/11     17:25          11526 ta_func_api.xsd
-a----          2007/9/8     18:37           7003 ta_func_list.txt
After I run go build, the terminal shows:
github.com/d4l3k/talib
@.***\generated.go:4:11: fatal error: ta-lib/ta_libc.h: No such file or directory
4 | // #include "ta-lib/ta_libc.h"
|           ^~~~~~~~~~~~~~~~~~
compilation terminated.
I tried move C:\ta-lib\c to C:\ta-lib,the error is the same.I found
ta_libc.h in dir ta-lib\c\include,maybe I made a mistake with the C code
dir.
Thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/d4l3k/talib/issues/7, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAG56MGXFBRX7XRTWDK4TZLUMS4TPANCNFSM5IJA4GMQ
.

Maybe I should work on linux until this project done:)


Update StackOverflow link to kentico-kontent

Motivation
Correct the link to StackOverflow to use the kentico-kontent tag rather than the kentico-cloud tag.
Checklist

[ ] Code follows coding conventions held in this repo
[ ] Automated tests have been added
[ ] Tests are passing
[x] Docs have been updated (if applicable)
[ ] Temporary settings (e.g. variables used during development and testing) have been reverted to defaults

How to test
Click the links through to see tagged items in StackOverflow:

Original kentico-cloud tag
New kentico-kontent tag

The original tag no longer has any associated questions.

Nice catch! Actually, you've discovered wrong link because this repository has no relation to Kentico Cloud/Kontent. It's designed for Kentico EMS. So in the bullet list there should be links to SO with different tags.


Add basic types for IO related protocols.

https://github.com/zapatacomputing/z-quantum-core/pull/212#discussion_r582108810


Add CONTRIBUTING.md file

There is a small section already in this project, but as a good practise a CONTRIBUTING.md file should be added.
You can find info about good practise to write it in Github open source guide

I have added it and linked with readme.md Please review it

Closed by #49 and #41


Stateless Post Feedback

Some random fixes for the stateless post.

Drop the public -> private and we're good 👍

Thank!


Navigation Backstack

Navigation BackStack not cleared in any navigation actions leading to multiple sets of each destination in the stack.
Specify app:popUpTo and app:popUpToInclusive in the action.

updated


Add url config for day/month/year pickers

daypicker/monthpicker/yearpicker now accept alternate template url on datepickerPopupConfig

This needs documentation and tests

This feature is already in master via 1f65d87fc3c8bb30c4f579ea492778e987b84236 - this currently can be used with a custom datepicker template that specifies the custom templates for each of the *picker directives with the template-url attribute.


Feature Request/Discussion: return to ground control station (RT_GCS)

There is an easy way to do that, but probably not the best one.
Px4/QGC already supports follow-me mode, which uses number #144 as mavlink message.  However, the logic in the mc_pos_controller_main.cpp is already broken to some extend (for instance. the velocity demand here will never pass the velocity controller).
Therefore, it makes sense to fix it and maybe even extend it such that the same message can be used for the RT_GCS feature.
I was discussing this feature with @dogmaphobic who mentioned that further modification might be required:

the code would need to check if it's using a high latency link (Iridium satellite) for instance and control the frequency of updates to a significant lower rate. It would also need UI asking the user if this is to be enabled or not and the desired frequency

Any suggestions are welcomed.

Could you describe high level how you'd expect this to function keeping in mind the existing HOME position and RTL behaviour?
For example would you simply want to have the home position automatically updated to the location of the ground control station if it's available? Keeping in mind the ramifications for failsafes and mission items with relative altitudes.
Alternatively we could handle it as the actual ground control station location. Then "return to ground station" and "return to home" would be distinct things.
I would initially try to think this through separately from the existing follow-me mode, although some of the pieces could probably be shared later on.

I think this is a neat idea and probably would have use with certain types of precision landing systems and other applications.
As the number of  different "Return" functions increase, it would be nice to keep an organized framework, if possible.  I don't contribute code, but I'll contribute my thoughts from a user perspective as separate entries below.

There is already some messages and a (psuedo?) mode type referred to as "Return to Ground station" or "RTGS".  I believe it triggers in certain loss of RC situations.
https://github.com/PX4/Firmware/blob/0caa4dc1712771faec3ca57756998dedfd29bea7/msg/vehicle_status.msg#L22
The terminology, descriptions, code comments, and functionality is wrong may be somewhat broken.  What occurs when this triggers is basically a Return to Home type functionality.  It shows up as "Return to Ground station" in the Qgroundcontrol UI.
If a true "return to ground station" function was implemented, this old and wrong code should get cleaned up and removed to avoid confusion.

In my mind this is what the Return framework looks like:

Terminology can get out of control (already is).  for example:
acronyms used: RTL, RTH, RTGS, RT_GCS
terminology used: Return to Land, Return to Launch, Return to Home, Return to Groundstation, Return to Ground Control Station, Smart RTL, Mission RTL, etc...
I find it useful to think of just one "Return" flight mode.  "Return" mode can have a number of parameter selectable behaviors.  I can't tell you what variable names to use in your code, but from a user perspective things should be kept simple and organized with just one "Return" flight mode and user selectable sub behaviors.
There is a param called "RTL_LAND_TYPE" (which might soon change to "RTL_TYPE").  This is one method to handle the various sub behaviors.

@Antiheavy FYI current documentation is setting on only Return - though  sometimes with aliases - e.g. Return mode (a.k.a. Return to launch - RTL, Return to home - RTH) etc). I completely agree with your sentiments above. This should also integrate in a user friendly way with precision landing.
I LOVE your diagram above. Once this round of work is done on return, lets get a modified version of that into the docs. Do you have a shareable link that we can use for editing when that happens (I like docs to have a link so we can edit things later).


Wrong years on the footer

Is your feature request related to a problem? Please describe.
The years are in the footers need to be updated.
Describe the solution you'd like
Update the years.

I'am working on it


Build Assets

How to build the assets folder?
I have these errors:
uno-zen panagorn$ gulp
[23:37:43] Failed to load external module coffee-script/register
[23:37:43] Failed to load external module coffee-script
[23:37:43] Local gulp not found in ~/Documents/myblog/content/themes/uno-zen
[23:37:43] Try running: npm install gulp

i fix it with npm install & bower install

perfect 👍


Add init script to do intialiazation of submodules and installation to R and Python paths

I added a small init script and a new cell to the index notebook to run it.
Note that the script cannot just be run via !bash init.sh in the notebook because this will run in the wrong conda env.
The script requires the conda-build package which has to be added to the env definition in the env repo.
This is not a nice solution, but for now it is pragmatic one that will make the binder version of the repo easily usable.

The binder button above is still not correct.
This link should work (using main of env repo and my branch of this PR)

Unfortunately this does not work as expected

it is not pretty 🙈 , but it works


feat: New Pizza Fun Facts

Description
The 'Pizza Fun Facts' section of the 'pizza-facts-&-trivia.md' file in the 'pizza-verse' repository has been updated with new additions
What type of PR is this? (check all applicable)

[x] ☝ Add a pizza fact or trivia
[ ] 🧑🍳 Add a pizza recipe
[ ] 🗺 Add a regional pizza
[ ] 🍴 Add a traditional food
[ ] 📝 Documentation Update

Related Tickets & Documents
Relates to #36
Added to documentation?

[ ] 📜 README.md
[x] 🙅 no documentation needed

[optional] What GIF best describes this PR or how it makes you feel?

@adiati98 Hi, I did it :).


feat: manage database migration

Fixes #685
Key changes

Move MySQL migration to Batch service. [1] [2]

New gRPC API Added in Batch service.

CurrentMigrationVersion: used to query current migration version
Migrate: execute up/down migration, there is a steps param in request which mean how many version we want to migrate.

There is a usecase of calling those API in Makefile:

CurrentMigrationVersion
Up
Down

Add helm hook to Batch service chart. [1]

The hook will be executed when user do helm install or upgrade.

Other changes

Add migrate CLI tool installation to Makefile local-deps target. [1] [2]

When we create the migration file, we should use NAME=some_name make create-mysql-migration to create the file, the NAME env is the the name of the migration.
The created file will under pkg/batch/migration/mysql, file's name follow rule.

Add migration target to Makefile which help developer checking database changes in local environment.
Usage example:

# check current migration version
WEB_GATEWAY_HOST=https://web-gateway.bucketeer.org SERVICE_TOKEN_PATH=tools/dev/cert/service-token make migrate-version

# migrate up one version
WEB_GATEWAY_HOST=https://web-gateway.bucketeer.org SERVICE_TOKEN_PATH=tools/dev/cert/service-token make migrate-up

# migrate down one version
WEB_GATEWAY_HOST=https://web-gateway.bucketeer.org SERVICE_TOKEN_PATH=tools/dev/cert/service-token make migrate-down

@Ubisoft-potato migration pod has "helm.sh/hook": post-install, post-upgrade annotation. This means that the migration is executed after all k8s resources are updated, does it?
This causes errors because services of the new version expect the new schema.
IMO, it would be better to run migration before helm upgrades.

@Ubisoft-potato migration pod has "helm.sh/hook": post-install, post-upgrade annotation. This means that the migration is executed after all k8s resources are updated, does it? This causes errors because services of the new version expect the new schema.
IMO, it would be better to run migration before helm upgrades.

@kentakozuka Currently, the database migration API is implemented in the Batch service, so we can only wait for the Batch service to be deployed and then send the migration request to it.So I am using "helm.sh/hook": post-install, post-upgrade.
Let me check if we can make sure Batch service chart could be deployed first when we install or upgrade Bucketeer Helm Charts.

@Ubisoft-potato, as we spoke, we might achieve our goal of upgrading new schemas without causing downtime by running the migration process outside the Bucketeer app. We could use a script or container deployed temporarily and terminated after upgrading.
This guide seems a good solution to our problem.
https://atlasgo.io/guides/deploying/helm#using-helm-lifecycle-hooks

@Ubisoft-potato, as we spoke, we might achieve our goal of upgrading new schemas without causing downtime by running the migration process outside the Bucketeer app. We could use a script or container deployed temporarily and terminated after upgrading.
This guide seems a good solution to our problem. https://atlasgo.io/guides/deploying/helm#using-helm-lifecycle-hooks

Let's eliminate migration in the batch service.
First, I will create our GitHub workflow for creating migration images using atlasgo. Then, I will add a pre-install helm hook for Bucketeer Charts.

@Ubisoft-potato

First, I will create our GitHub workflow for creating migration images using atlasgo. Then, I will add a pre-install helm hook for Bucketeer Charts.

Sounds good to me!

@Ubisoft-potato Thanks! How do we rollback a migration if the migration succeeded but we want to revert it?

@kentakozuka This PR does not include the rollback migration implementation. We will address it in a new PR due to the complexity of the down atlas migration.

Closing this in favor of https://github.com/bucketeer-io/bucketeer/pull/1060


Implement too-small bot

report when the size of the repo is smaller than the threshold
report text The repo is too small (LoC is 123)
set meta marker once reported
don't report anymore, while the meta marker is present
report and remove the marker if the size of the repo is above the threshold
report text The repo is not small anymore (LoC is 456)
the threshold is 5K LoC

[x] implement the bot
[x] cover by tests
[x] append project README

@iakunin 5 puzzles #130, #131, #132, #133, #134 are still not solved.

Done

@iakunin 4 puzzles #130, #131, #132, #134 are still not solved; solved: #133.

@iakunin 3 puzzles #131, #132, #134 are still not solved; solved: #130, #133.

@iakunin the puzzle #134 is still not solved; solved: #130, #131, #132, #133.

@iakunin all 5 puzzles are solved here: #130, #131, #132, #133, #134.


lightkurve installation from channel conda-forge causes downgrading

Problem description
Currently, lightkurve is not in the default conda channel.  Hence, one follows the documented method of installing lightkurve with conda:
conda install --channel conda-forge lightkurve

Unfortunately, to push ahead one must accept downgrading of certain packages:
The following packages will be DOWNGRADED:

    cryptography:         2.4.2-py27h1ba5d50_0                --> 2.3.1-py27hdffb7b8_0    conda-forge
    curl:                 7.63.0-hbc83047_1000                --> 7.63.0-h74213dd_0       conda-forge
    libarchive:           3.3.3-h5d8350f_5                    --> 3.3.3-h823be47_0        conda-forge
    libcurl:              7.63.0-h20c2e04_1000                --> 7.63.0-hbdb9355_0       conda-forge
    libssh2:              1.8.0-h1ba5d50_4                    --> 1.8.0-h5b517e9_3        conda-forge
    openssl:              1.1.1a-h7b6447c_0                   --> 1.0.2p-h470a237_1       conda-forge
    python:               2.7.15-h9bab390_6                   --> 2.7.15-h33da82c_4       conda-forge
    qt:                   5.9.7-h5867ecd_1                    --> 5.9.6-h8703b6f_2

There is a similar warning about adds and upgrades.  This could be very undesirable.
Environment:

platform: Xubuntu 18.04.1
lightkurve version: 1.0b25-py_0
installation method: conda install --channel conda-forge lightkurve

Desirable solution:
conda install lightkurve # i.e. from the default channel

Did I miss something that could be put in the documentation for conda users?
Is there a way of plucking out only lightkurve from conda-forge and everything else from the default channel?  If I find a way, I'll add a note here for updating the documentation.

Proposed Solution (documentation amendment)
Document that conda users append the default channel entry with conda-forge so that entries (explicitly requested or as an implied dependency) come from the default channel as long as there an entry in the default channel; else conda will continue searching in conda-forge:
conda config --append channels conda-forge # one-time operation

Then, the following command works without creating downgrading warnings and stays in the default channel whenever possible for the dependencies:
conda install lightkurve

Sample Output
## Package Plan ##

  environment location: /home/elkins/anaconda2

  added / updated specs:
    - lightkurve

The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    scipy-1.1.0                |   py27h7c811a0_2        17.6 MB
    astroquery-0.3.9           |          py_1000         2.6 MB  conda-forge
    lightkurve-1.0b25          |             py_0         245 KB  conda-forge
    mkl_random-1.0.2           |   py27hd81dba3_0         383 KB
    astropy-2.0.9              |   py27hdd07704_0         6.8 MB
    mkl_fft-1.0.6              |   py27hd81dba3_0         191 KB
    autograd-1.2               |             py_1          33 KB  conda-forge
    numpy-base-1.15.4          |   py27hde5b4d6_0         4.2 MB
    bokeh-1.0.2                |           py27_0         5.3 MB
    keyring-17.0.0             |           py27_0          48 KB
    oktopus-0.1.2              |             py_0          13 KB  conda-forge
    numpy-1.15.4               |   py27h7e9f1db_0          47 KB
    ------------------------------------------------------------
                                           Total:        37.5 MB

The following NEW packages will be INSTALLED:

    astroquery: 0.3.9-py_1000         conda-forge
    autograd:   1.2-py_1              conda-forge
    keyring:    17.0.0-py27_0
    lightkurve: 1.0b25-py_0           conda-forge
    oktopus:    0.1.2-py_0            conda-forge

The following packages will be UPDATED:

    astropy:    2.0.8-py27h035aef0_0              --> 2.0.9-py27hdd07704_0
    bokeh:      0.13.0-py27_0                     --> 1.0.2-py27_0
    mkl_fft:    1.0.4-py27h4414c95_1              --> 1.0.6-py27hd81dba3_0
    mkl_random: 1.0.1-py27h4414c95_1              --> 1.0.2-py27hd81dba3_0
    numpy:      1.15.1-py27h1d66e8a_0             --> 1.15.4-py27h7e9f1db_0
    numpy-base: 1.15.1-py27h81de0dd_0             --> 1.15.4-py27hde5b4d6_0
    scipy:      1.1.0-py27hfa4b5c9_1              --> 1.1.0-py27h7c811a0_2

Proceed ([y]/n)?

Of course, if one wants to prioritise using conda-forge ahead of the default channel for whatever reasons, one can prepend it instead:
conda config --prepend channels conda-forge

@gully Do you think we have narrow constraints on the conda package that could be relaxed to avoi the issue above, or do you think we should update the documentation as per @texadactyl's suggestion?

Whatever you do, just remember that your users are scientists who will appreciate a low complexity solution.  (=:


Applicant - Success notification when logging in/out and saving data

Description
The 'Save' buttons (Save Diploma/Degree, Save Reference, etc) cause the page to reload with form data. Users with assistive technologies don't receive a cue when this happens, the confirmation is not obvious.
Suggest adding some confirmation text (Your diploma was successfully saved...) which would receive focus when the button is clicked and the page reloads.

Notes from slack conversation:

You can usually just flash to the session and have a template partial that checks for available flashed messages.
https://laravel.com/docs/6.x/session#flash-data
return redirect()->route('settings.edit')->withSuccess('Change of password was successful.');


UV Transforms

Materials should contain a 3x3 matrix to transform UV coordinates so textures can be scaled, rotated, or transformed.

This should also implement the KHR_texture_transform extension to glTF.

This should also implement the KHR_texture_transform extension to glTF.


a drawer should also be disabled if the immediate parent is disabled.

Nice! I noticed this issue after this Merge of this PR
https://github.com/GEOLYTIX/xyz/commit/f614ed95bab5596e0b9d4b11dce1d4432b89a06d


feat(autocomplete-icon): added support for the autocomplete icon

Summary
This pull request adds support for the autocomplete-icon to be used as the user types the command. It does this by changing the behavior on how the command is generated to use the new experimental command
features
Ticket Link
https://github.com/mattermost/mattermost-plugin-confluence/issues/72
fix #72

@DHaussermann This is also a good one for dev testing

cc @jfrerich @hanzei please help with merging if Automerge label is unsuccessful.


Fix unaligned memory access in emulator

Together with #380 and #381, this makes bm/basm work on SPARC and Solaris (10).

@zhiayang looks goode to me! :+1: Thank you for your contribution!


GraphViz2 update

As discussed on #2. Adds as_graph, and uses it in the GraphViz2-interfacing code.

Incredible contributions, thanks @mohawk2

@mohawk2 Just released v0.44
https://metacpan.org/release/MANWAR/Map-Tube-Plugin-Graph-0.44


Some questions about Memory Bank Protocol

Hi. I'm trying to do PnR of an OpenFPGA. My technology node is 250nm. So DFF chain based architectures cost a huge area because of DFF's. To be able to reduce area, I saw memory bank and frame based architectures. I also saw that ql_memory_bank protocol is physical design friendly. Should I continue with ql_memory_bank protocol architectures for physical design? Does this choice give me area cost gain that I expected? What is its disadvantages? Further, there are only k4n4 architecture files that support memory bank protocol. I want to do a design of k4n8 or k6n10. How can I configure k4n8 architecture for my purpose? @tangxifan @ganeshgore

Hello @mattvlsi
ql_memory_bank protocol used latches instead of flip-flops.
Definitely, there is an area benefit but it depends on how the latch cell is implemented in the standard cell library.
Challenge of using memory bank:
ql_memory_bank protocol is essentially like SRAM addressing, which has a long bit and word line running across the fabric.
It shud be straightforward if you are performing flat place and route.
In the case of hierarchical/tileable flow, the physical design requires a lot more effort (as OpenFPGA does not generate feedthrough for these lines), also based on the place and route tool you use there could be high routing congestion on the boundary interface of each tile.
Configuring K4N8 or K6N10
You can configure any architecture to use memory bank protocol, makes sure you set <organization type="ql_memory_bank"
and define circuit_model type="sram" with WL and BL lines defined, Alternately you can copy from the existing OpenFPGA architecture file.

@mattvlsi Please note that ql_memory_bank will replace memory_bank in future. Current memory_bank will be deprecated.
Therefore, I suggest to start with ql_memory_bank to avoid any backward compatibility issues.

Thanks a lot for your detailed explanations.


CoinList

gib karmapoints to lobster holders

What are karmapoints?
What Coinlist wants from the lobs?

What are karmapoints? What Coinlist wants from the lobs?

https://blog.coinlist.co/introducing-coinlist-karma-earn-rewards-for-advancing-crypto/
basically lobs holders to have ability for priority queue for token sales on coinlist

Can we please clarify with Coinlist team if the geographical rules are the same for regular queue and for priority queue? Reason for the question: A friend of mine was offered priority queue for IMX sale. Location is Hong Kong. He was not able to register for priority queue due to geo-restrction, but he was able to join regular queue.

Lobster NFT holders get CoinList priority queue access and one month of free trading.
CoinList is collaborating with LobsterDAO to airdrop Karma to high value-add LobsterDAO members (based on engagement in the LobsterDAO Telegram groups and dictated by the LobsterDAO team) and to give them one month of free trading on CoinList Pro, CoinList’s pro exchange. Lobster NFT holders identified by LobsterDAO from the block 13825000 Snapshot (https://raw.githubusercontent.com/lobster-dao/lobs-holders/snapshots/lobs_owners/lobs-owners_2021-12-17T21%3A20%3A31Z_blk13825000.txt) are eligible for this drop.
CoinList's mission is to accelerate crypto advancement and adoption. We help the best crypto projects (ex. Filecoin, Solana, Flow, etc.) throughout their life cycles and give early adopters access to quality crypto assets before mainstream exchanges.
CoinList Karma (https://blog.coinlist.co/introducing-coinlist-karma-earn-rewards-for-advancing-crypto/) is a reflection of users’ contributions to token networks on CoinList. The greater a user’s contribution through value-add activities (ex. staking, governance, etc.), the higher their Karma. Eligible users with high levels of Karma can earn access to the Priority Queue on CoinList, an invite-only queue for token sales that is significantly shorter than the main token sale queue.
To receive the benefits, eligible users need to:

Complete CoinList KYC at https://coinlist.co/lobsterdao-karma before 00:00 UTC, January 1, 2022.
Link your Ethereum address holding the Lobster NFT with your CoinList account by submitting your wallet address and signing a provided message at the end of the KYC flow (https://coinlist.co/lobsterdao-karma).
If you are eligible for the Karma airdrop and have an existing CoinList account, please use your existing account and do not create a new account.

The CoinList team will also be joining the LobsterDAO Spotlight on December 22, 2021 to share more information about this Karma drop.
For more information, please refer to the LobsterDAO Karma Drop FAQ (https://coinlist.co/help/lobsterdao-karma-drop-faq). Thank you for supporting the CoinList community!

Thank you for the proposal and suggestion!

What is the reasoning behind keeping the amount of Kama reward a secret?

re: "The exact amount and dates will be disclosed on or around January 2022."

Considering the decay after two months, what are the ongoing decay rates going to be?

Overall Coinlist Karma farming is a wide spread practice, where accounts in the 1000-1500 range can be farmed for a $150 investment or bought at the $75 range. Considering the decay and ease-of-availability of Kama points i would expect a Kama range of at least above 3000 to be considerable in order for this not look like a low effort user acquisition.

Держатели Lobster NFT получают приоритетный доступ к очереди CoinList и один месяц бесплатной торговли.
CoinList сотрудничает с LobsterDAO для передачи кармы участникам LobsterDAO с высокой добавленной стоимостью (на основе участия в группах телеграмм LobsterDAO и под диктовку команды LobsterDAO) и предоставления им одного месяца бесплатной торговли на CoinList Pro, бирже CoinList pro. Держатели Lobster NFT, идентифицированные LobsterDAO из снимка блока 13825000(https://raw.githubusercontent.com/lobster-dao/lobs-holders/snapshots/lobs_owners/lobs-owners_2021-12-17T21%3A20%3A31Z_blk13825000.txt) имеют право на это снижение.
Миссия CoinList заключается в ускорении продвижения и внедрения криптографии. Мы помогаем лучшим криптопроектам (напр. Filecoin, Solana, Flow и т.д.) На протяжении всего их жизненного цикла и предоставляют ранним пользователям доступ к качественным криптоактивам до основных бирж.
Карма CoinList (https://blog.coinlist.co/introducing-coinlist-karma-earn-rewards-for-advancing-crypto/) является отражением вклада пользователей в сети токенов в CoinList. Чем больше вклад пользователя в деятельность с добавленной стоимостью (например, ставки, управление и т.д.), Тем выше его Карма. Подходящие пользователи с высоким уровнем Кармы могут получить доступ к Приоритетной очереди в CoinList, очереди только по приглашению для продажи токенов, которая значительно короче основной очереди на продажу токенов.
Для получения льгот соответствующим пользователям необходимо:

Полный список монет KYC на https://coinlist.co/lobsterdao-karma до 00:00 UTC, 1 января 2022 года.
Свяжите свой адрес Ethereum, содержащий Lobster NFT, с вашей учетной записью в CoinList, отправив адрес своего кошелька и подписав предоставленное сообщение в конце потока KYC (https://coinlist.co/lobsterdao-karma).
Если вы имеете право на участие в программе Karma airdrop и у вас есть существующая учетная запись CoinList, пожалуйста, используйте существующую учетную запись и не создавайте новую учетную запись.

Команда CoinList также присоединится к LobsterDAO Spotlight 22 декабря 2021 года, чтобы поделиться дополнительной информацией об этом падении кармы.
Для получения дополнительной информации, пожалуйста, обратитесь к часто задаваемым вопросам о падении кармы ЛобстерДАО (https://coinlist.co/help/lobsterdao-karma-drop-faq). Спасибо вам за поддержку сообщества CoinList!

здраствуйте. подскажите пожалуйста, если я не имею на данный момент нфт лобстер ДАО , я могу его приобрести и получить возможность на приоритетную очередь, или существует ещё какие нибудь варианты получения приоритетной очереди и что я должен для этого сделать. спасибо.

Lobster NFT holders get CoinList priority queue access and one month of free trading.
CoinList is collaborating with LobsterDAO to airdrop Karma to high value-add LobsterDAO members (based on engagement in the LobsterDAO Telegram groups and dictated by the LobsterDAO team) and to give them one month of free trading on CoinList Pro, CoinList’s pro exchange. Lobster NFT holders identified by LobsterDAO from the block 13825000 Snapshot (https://raw.githubusercontent.com/lobster-dao/lobs-holders/snapshots/lobs_owners/lobs-owners_2021-12-17T21%3A20%3A31Z_blk13825000.txt) are eligible for this drop.
CoinList's mission is to accelerate crypto advancement and adoption. We help the best crypto projects (ex. Filecoin, Solana, Flow, etc.) throughout their life cycles and give early adopters access to quality crypto assets before mainstream exchanges.
CoinList Karma (https://blog.coinlist.co/introducing-coinlist-karma-earn-rewards-for-advancing-crypto/) is a reflection of users’ contributions to token networks on CoinList. The greater a user’s contribution through value-add activities (ex. staking, governance, etc.), the higher their Karma. Eligible users with high levels of Karma can earn access to the Priority Queue on CoinList, an invite-only queue for token sales that is significantly shorter than the main token sale queue.
To receive the benefits, eligible users need to:

Complete CoinList KYC at https://coinlist.co/lobsterdao-karma before 00:00 UTC, January 1, 2022.
Link your Ethereum address holding the Lobster NFT with your CoinList account by submitting your wallet address and signing a provided message at the end of the KYC flow (https://coinlist.co/lobsterdao-karma).
If you are eligible for the Karma airdrop and have an existing CoinList account, please use your existing account and do not create a new account.

The CoinList team will also be joining the LobsterDAO Spotlight on December 22, 2021 to share more information about this Karma drop.
For more information, please refer to the LobsterDAO Karma Drop FAQ (https://coinlist.co/help/lobsterdao-karma-drop-faq). Thank you for supporting the CoinList community!

hello. please tell me if I do not currently have a lobster DAO nft, I can purchase it and get the opportunity for a priority queue, or there are some other options for getting a priority queue and what should I do for this. thanks.

Agree with @D-d-dot

Also what do you expect from lobster community?

Did Coinlist have new launches recently?
They did great in the past indeed, but what about now?

What do we need to do? How to help moving this forward？

thx gang, epic questions, will ask all today in spotlight.

What do we need to do? How to help moving this forward？

after spotlight today there will be snaposhot voting, so do vote when snapshot is live, will post url here and in chat

hi guys,
are the any desired amount of nftto be kept

Will airdrop eligibility require KYC prior/before the actual airdrop/claim?

Considering that there is a 2 months decay, it would be interesting to know how many new projects are actually lined up in the first two months of 2022.

Concerns that  D-d-dot expressed are legit.

Thank you for the proposal and suggestion!

What is the reasoning behind keeping the amount of Kama reward a secret?

re: "The exact amount and dates will be disclosed on or around January 2022."

Considering the decay after two months, what are the ongoing decay rates going to be?

Overall Coinlist Karma farming is a wide spread practice, where accounts in the 1000-1500 range can be farmed for a $150 investment or bought at the $75 range. Considering the decay and ease-of-availability of Kama points i would expect a Kama range of at least above 3000 to be considerable in order for this not look like a low effort user acquisition.

3000 points is nonsense. As you can see on the chart below only 0.33% have 2000+ points https://blog.coinlist.co/content/images/2021/12/Screen-Shot-2021-12-09-at-4.52.26-PM.png
Getting Karma is not so easy as you described.

The 3000 are an arbitrary number- it seems that 1000-1500 are the number that accounts are relatively easy gameable to and qualify for the karma queue. Considering about 1-2 launches per month on Coinlist and the decay in karma, i would suggest a number above 1500 that holds for the initial 2 month + 2-3month in the decaying period before we have to start engaging with karma upholding activities.


UT Extended timeouts in ConnectivityMonitorTest

Hi @mlesnic, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

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

TTYL, MSBOT;


Using Components with Multipart Emails (multiple formats)

I was trying to convert a partial that's used in my mailers to a ViewComponent today, and because the partial is used in a multipart email, it has a plaintext template (_thing.text.erb) as well as an html template (_thing.html.erb). I was surprised I could not define a component with two different template formats, I get the following error:
ViewComponent::TemplateError: More than one template found for Mailers::ThingComponent. There can only be one default template file per component.
Maybe I could workaround by using a variant?
It sure would be nice if this just worked out of the box the way that Rails does with different formats.

See our work in progress here: https://github.com/ViewComponent/view_component/pull/1681.
At this point, it looks like it will be too much work to land this any time soon. I'm tagging this issue as help wanted in case someone would like to step in and give it shot.

@jaredmoody @joelhawksley I am working on adding support for this by checking using request.format to determine the format used in rendering the template

@reeganviljoen sounds good, let me know what you think of our previous attempt 😄

@joelhawksley I looked at the previous attempt and it seemed solid, the only place where I differ is I believe the format should be assumed from the request


Plugin error when specifying environment variable QUARTO_VERSION

I specified QUARTO_VERSION to install a pre-release:
QUARTO_VERSION=1.2.172
cat netlify.toml
[[plugins]]
package = "@quarto/netlify-plugin-quarto"

cat package.json
{
  "dependencies": {
    "@quarto/netlify-plugin-quarto": "^0.0.5"
  }
}

Here the error on Netlify:
9:30:52 AM: ────────────────────────────────────────────────────────────────
9:30:52 AM:   1. @quarto/netlify-plugin-quarto (onPreBuild event)
9:30:52 AM: ────────────────────────────────────────────────────────────────
9:30:52 AM:
9:30:52 AM:
9:30:52 AM: ────────────────────────────────────────────────────────────────
9:30:52 AM:   Plugin "@quarto/netlify-plugin-quarto" internal error
9:30:52 AM: ────────────────────────────────────────────────────────────────
9:30:52 AM:
9:30:52 AM:   Error message
9:30:52 AM:   Error: function () { [native code] } could not be cloned.
9:30:52 AM:
9:30:52 AM:   Plugin details
9:30:52 AM:   Package:        @quarto/netlify-plugin-quarto
9:30:52 AM:   Version:        0.0.5
9:30:52 AM:   Repository:     git+https://github.com/quarto-dev/netlify-plugin-quarto.git
9:30:52 AM:   npm link:       https://www.npmjs.com/package/@quarto/netlify-plugin-quarto
9:30:52 AM:   Report issues:  https://github.com/quarto-dev/netlify-plugin-quarto/issues
9:30:52 AM:
9:30:52 AM:   Error location
9:30:52 AM:   In "onPreBuild" event in "@quarto/netlify-plugin-quarto" from netlify.toml and package.json
9:30:52 AM:       at writeChannelMessage (node:internal/child_process/serialization:109:9)
9:30:52 AM:       at process.target._send (node:internal/child_process:840:17)
9:30:52 AM:       at process.target.send (node:internal/child_process:740:19)
9:30:52 AM:       at node:internal/util:361:7
9:30:52 AM:       at new Promise (<anonymous>)
9:30:52 AM:       at bound  (node:internal/util:347:12)
9:30:52 AM:       at sendEventToParent (file:///opt/buildhome/node-deps/node_modules/@netlify/build/lib/plugins/ipc.js:123:46)
9:30:52 AM:       at handleError (file:///opt/buildhome/node-deps/node_modules/@netlify/build/lib/plugins/child/error.js:13:9)
9:30:52 AM:       at handleEvent (file:///opt/buildhome/node-deps/node_modules/@netlify/build/lib/plugins/child/main.js:45:11)
9:30:52 AM:       at processTicksAndRejections (node:internal/process/task_queues:96:5)
9:30:52 AM:
9:30:52 AM:   Resolved config
9:30:52 AM:   build:
9:30:52 AM:     environment:
9:30:52 AM:       - QUARTO_VERSION
9:30:52 AM:     publish: /opt/build/repo/_site
9:30:52 AM:     publishOrigin: ui
9:30:52 AM:   plugins:
9:30:52 AM:     - inputs: {}
9:30:52 AM:       origin: config
9:30:52 AM:       package: '@quarto/netlify-plugin-quarto'
9:30:52 AM: Caching artifacts
9:30:53 AM: Creating deploy upload records
9:30:52 AM: Started saving node modules
9:30:52 AM: Finished saving node modules
9:30:52 AM: Started saving build plugins
9:30:52 AM: Finished saving build plugins
9:30:52 AM: Started saving pip cache
9:30:53 AM: Failed during stage 'building site': Build script returned non-zero exit code: 3 (https://ntl.fyi/exit-code-3)
9:30:52 AM: Finished saving pip cache
9:30:52 AM: Started saving emacs cask dependencies
9:30:52 AM: Finished saving emacs cask dependencies
9:30:52 AM: Started saving maven dependencies
9:30:52 AM: Finished saving maven dependencies
9:30:52 AM: Started saving boot dependencies
9:30:52 AM: Finished saving boot dependencies
9:30:52 AM: Started saving rust rustup cache
9:30:52 AM: Finished saving rust rustup cache
9:30:52 AM: Started saving go dependencies
9:30:52 AM: Finished saving go dependencies
9:30:53 AM: Build failed due to a plugin error: Build script returned non-zero exit code: 3
9:30:53 AM: Failing build: Failed to build site
9:30:54 AM: Finished processing build request in 17.875993949s

This is a known issue we are having sporadically with netlify, unfortunately, and it's a bug on netlify's side. I'm just letting you know "we are aware, and are investigating a fix", but I can give no firm timeline at this moment.

Thanks,
Is there another way of specifying the version?
On Sat, Oct 1, 2022, 16:50 Carlos Scheidegger @.***>
wrote:

This is a known issue we are having sporadically with netlify,
unfortunately, and it's a bug on netlify's side. I'm just letting you know
"we are aware, and are investigating a fix", but I can give no firm
timeline at this moment.
—
Reply to this email directly, view it on GitHub
https://github.com/quarto-dev/netlify-plugin-quarto/issues/4#issuecomment-1264510284,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC5Q4T5G3KBURQ7XKCQUSLWBDE5PANCNFSM6AAAAAAQZ5UUYU
.
You are receiving this because you authored the thread.Message ID:
@.***>


Allow configuring liveness and readiness probe timeouts

Fixes #73

Makes the timeoutSeconds configurable for probes and sets the default to 5 seconds
Also fix inconsistency in Zookeeper probes where the value for periodSeconds was used for timeoutSeconds.

These changes look good. The only complication is that k8s will restart all the brokers when the probes are changed, so upgrading to this version of the helm chart will cause a rolling restart of the brokers.

I think that would introduce additional complexity to the Helm chart if we start optimizing for preventing possible restarts for upgrades. I'll skip handling that for now.


Contact Page

[x] Styling
[x] Form function
[x] Form validation
[x] Form thank you page

Resolved by #10


Qualifier Issue when Adding Points

When using the Add Point form and adding qualifiers to the new points, the value is populated with a string when it should be a number. When you try and save, there is a database type issue.

@AmberSJones  this issue is ready for testing on the qualid branch. but I am not setting it up to merge yet because there are still some issues with some of the values when saving. the new row saves fine but the default values are set to nan. let me know if that is normal.

The behavior is as expected for me on qualid brach. I am not seeing the nan that you posted in the screenshot @sreeder . I'm closing the issue.


add more nf-core data entities

@mashehu please add:

your name and email to author and author_email in setup.py
the relevant copyright line to repo2rocrate/nextflow.py

@mashehu can you add your copyright line to repo2rocrate/nextflow.py? E.g.:
--- a/repo2rocrate/nextflow.py
+++ b/repo2rocrate/nextflow.py
@@ -1,4 +1,5 @@
 # Copyright 2022-2024 CRS4.
+# Copyright 2024 <MASHEHU'S EMPLOYER>.
 #
 # Licensed under the Apache License, Version 2.0 (the "License"); you may not
 # use this file except in compliance with the License. You may obtain a copy

After you do that, I can merge.

sorry for missing that.


[wishlist] streamline Kodi startup

When starting to use Kodi using my Kore remote, I need to take several steps in sequence:

Enable Wifi
Start Kore
wait for Wifi to be connected
Press the Wake-up button
wait for the Kodi box to be started adn Kore to be connected

Ideally, all of that could happen when I open the Kore app, as it is in most configurations pretty useless outside a local network and without a Kodi server.
I'd like to suggest to add advanced configurations options (possibly on-by-default on new setups) that say:

Enable WiFi when Kore is started. (This might need additional privileges in Android, but i think that those can easily be argued to be convenient. Connection attempts should be held off until readiness of the network is signaled by Android, to avoid waiting for any timeouts and tempt the user to press reconnect for things to be faster.)
Send wake-up-on-LAN on every connection attempt. (Those can be sent right after the initial SYN package. If the device is off, no time is lost, and if it's on, the additional one multicast package (or burst) when starting the app won't do any harm).

I understand your wishes but I don't agree at all.
Ad Enable WiFi:
For me enabling/disabling Wi-Fi is something, I never want to be done by an App automatically. I want control for my device if it should use mobile Data, Wi-Fi and also which Wi-Fi network.
 AFAIK for enabling Wi-Fi the permission CHANGE_WIFI_STATE is needed and this permission cannot be revoked by the user.
In my case I also have more than one WLAN networks and I have to select the correct network (and this is not the strongest network and will not be selected automatically).
Ad Send WOL:
For me also this is not absolutely necessary. I'm fine with the button for WOL.
I also use Kore sometimes without running my Kodi-Server, e.g. see my move library and maybe I find a move to watch, but maybe also not.
Anyway there should be no automatic WOL always but it should be optional.
BTW: Maybe you can/will use an app like Tasker to control Wi-Fi and send WOL. I don't know Tasker and so I don't know the features of this app.

I'm fine with any of this being optional, and even opt-in.
As for WiFi permissions, it's a sad property of the Android ecosystem
that such permissions can't be fine-grained. Wiring this in with another
app is something that I'd need to try out to see whether it's a feasible
option.

Somehow i missed this issue when you created it, so i didn't comment.
Anyway, i agree with @NeroRome, and i would strongly oppose changing Kore to ask for more permissions to control wi-fi. Even as an option.
As for sending a WOL automatically, personally i also don't see the need for it, but as an option, it might be acceptable. It's not that easy because we wouldn't want to be constantly issuing wol so some care should be taken in the code.
I'm inclined to close this issue as is. If you want to continue with the wol part, maybe creating another issue would be better. I also think that @NeroRome's suggestion of looking at tasker might be useful.


java: ClassDict should extend LinkedHashMap in order to provide predictable attribute iteration order?

Do you have any information if Python makes any guarantees about the ordering of dict attributes (eg. declaration order, initialization order, etc)? If it does, then it should be reflected at the ClassDict level by choosing a more specialized parent class.
Of course, there will be a slight performance penalty (perhaps 10 to 15%) when switching from HashMap to LinkedHashMap.

This question can be generalized to all dict-type attributes.
For example, it appears to be the case that numpy.dtype.values should have a predictable attribute iteration order. The HashMap implementation class does not reflect it, which breaks the unpickling behaviour for sklearn.tree._tree.tree class (I need to rewrite the value attribute in method DType#toDescr()): https://github.com/jpmml/jpmml-sklearn/blob/master/src/main/java/numpy/DType.java
Or perhaps it only applies to CPython classes.

Dictionaries in Python don't have a guaranteed order of their values. What's more, there's even a setting that allows you to control/change the hash algorithm's seed value (PYTHONHASHSEED) which in turn will change the apparent order of keys in a dict.
If you're using OrderedDict however, the order of the keys is guaranteed to be the same as the order in which they are inserted in the dict https://docs.python.org/3/library/collections.html#collections.OrderedDict
I don't know what numpy.dtype.values is and a quick google didn't teach me much. What does python itself do when you pickle/unpickle such a value?

OK, you have clearly thought about it before.
I have a suspicion that CPython classes assume fixed/positional attribute ordering. The CPython object initialization method takes an array of arguments (eg. __init__(Object[])), and it is the responsibility of the CPython class to establish the mapping between its attributes and array elements.
In that case, my CClassDict should extend java.util.LinkedHashMap (or provide an alternative mechanism for communicating the list of attribute names), whereas the regular ClassDict can stay a subclass of java.util.HashMap.

Somehow I have the impression that you're confusing parts of object creation using the __init__ method and its parameter list, an object's attributes, and filling a dictionary with key/value pairs. Those are all different things. Recreating a dict via pickle is doing peculiar things too. Doesn't matter, you seem to have solved your issue.


Link in new tab

ive noticed how you cant right click a link and make it open up in a new tab?
only why i can think of it is you right click the link and below open link in open link in new tab?
in case you want to open a link and you dont trust someone and something like forsen doesnt happen again

The way I understand windows decides which window to open the link in, is based on which was focused last. I'm not sure if there's anything that can be done here.

Yes, as far as I know the link you click will be opened in a new tab in the last focused default browser window.
If you want to open a link and not have it show on stream, you should either take care to last focus the off-stream browser window or you could just copy the link and paste it into a new tab/window in the place of your choosing.
Please elaborate on the issue and re-open it if this didn't cover your issue.


Update code-review.md

Adding steps for what devs should do with Jira tickets after a PR is merged.

@amyblais Heads up that there is a merge conflict to resolve


A13 issues

Restart button is not working and ui cache button iam not sure but i think is not workin. Safe mode and respring works fine. Another issue when scroll specifically on lock screen wont show any button just the empty box

having same issue in iphone 7plus ios 13.3 and using uncover.

uicache works and the reboot button is a duplicate issue (#2)


Make blackbox invoker fraction configurable via Ansible

Extend Ansible deploy playbook for controller role such that it passes the blackbox fraction
setting as environment variable when running the controller container. Make the blackbox fraction
a required property of the LoadBalancerService such that the setting is read from the environment.
Allow overriding of the default blackbox fraction in Ansible.
All this is needed to vary the proportion between managed and blackbox invokers to accomodate
usage in production.
I tested the change by adding the setting controller_blackbox_fraction: 0.5 to file ansible/environments/docker-machine/group_vars/all and re-deploying the controller. As a result, the controller creates the following log entry indicating that the setting was picked up properly:
[2017-09-15T12:55:35.122Z] [INFO] [#sid_120] [LoadBalancerService] blackboxFraction = 0.5

PG3 - 1106 running


Pre-level subdomain status is being checked when requesting a certificate for a subdomain

What happened?
I'm trying to generate a certificate for a wildcard subdomain *.sub2.sub1.sld.tld and the challenge fails with: Error presenting challenge: OVH API call failed: GET /domain/zone/sub1.sld.tld/status - HTTP Error 404: "This service does not exist".
Indeed, sub1.sld.tld is not a correct DNS entry in our server. Although, *.sub2.sub1.sld.tld is a correct DNS entry and correctly answers to a dig request.

The status of sub1.sld.tld is not supposed to be checked since it is not the DNS entry for which we're trying to request a certificate. The status of *.sub2.sub1.sld.tld should be enough. If I'm mistaken, please let me know why and how I should fix this issue in my DNS configuration.
Steps to reproduce

On your OVH account, create a DNS entry for *.sub2.sub1.sld.tld and make sure that there aren't any entries for sub1.sld.tld or *.sld.tld
Create a certificate with the following configuration

apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: <CertificateName>
  namespace: cert-manager
spec:
  issuerRef:
    name: <ClusterIssuerName>
    kind: ClusterIssuer
  privateKey:
    algorithm: ECDSA
    size: 256
  dnsNames:
    - '*.sub2.sub1.sld.tld'
  isCA: false
  secretName: <TLSSecretName>

Look at the challenge's status

Versions in use

cert-manager-operator.v1.10.2
Kubernetes Version: v1.25.8+37a9a08
OpenShift Version: 4.11.20
Latest version of the chart installed via helm

Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Hi Aurélien
Thanks for the quick reply. The specific wildcard domain name I'm trying to generate a certificate for is *.stagiaire.ocp.its4u.eu. The challenge chokes on ocp.its4u.eu.
I will take a look at how SOA is implemented in our organization.


Need unit-testing on old converters

Description
All converters shall be tested. However the converters given from ParentElement did not come with tests.
Motivation
Everything in this repo shall be unit tested, and adding legacy code is no loophole. The old code should then be properly tested.
Inspiration
https://github.com/JamesNK/Newtonsoft.Json/blob/master/Src/Newtonsoft.Json.Tests/Converters/StringEnumConverterTests.cs

Was solved in #10


deb package

https://ubuntuforums.org/showthread.php?t=910717
https://wiki.debian.org/Packaging
https://wiki.debian.org/Packaging/Intro?action=show&redirect=IntroDebianPackaging

done


2.3-1

Compared to CLRS2e, the Figure 2.4 has so many differences, that the solution can't be marked as migratable.


Notification for low toner in Brother printer

Notification for low toner in Brother printer

Perhaps also look for status errors.


model: scikit: Add scikit models for RandomForest

https://scikit-learn.org/stable/auto_examples/ensemble/plot_forest_importances.html

Implemented in #160


Construct OpenApi from YAML/JSON

I am in a situation where a am dealing with a number of types that are being defined in eternal crates for which I cannot implement ToSchema. I've checked possible workarounds such as those listed in this open issue, but they remain quite verbose, especially if the types in question require to define a significant number of new schemas (for example GeoJson).
I'd be great if it was possible to construct a new OpenApi object from a yaml/json string/document, which would be much easier to work with.
This would allow, for example, to do things like:
 ApiDoc::openapi()
   .merge(OpenApiBuilder::parse("<MY_SCHEMA>").unwrap());

Even better if we could re-use the serde::Deserialize trait, which is already implemented for most of the types.

You have the components: {} wrapper in your JSON that is unexpected field. Below is a a working schema.
let components_json = r#"
{
    "schemas": {
        "GeoJsonObject": {
            "description": "GeoJSon object",
            "type": "object",
            "properties": {
                "type": {
                    "type": "string",
                    "enum": [
                        "Feature",
                        "FeatureCollection"
                    ]
                }
            },
            "required": [
                "type"
            ]
        }
    }
}
"#;

let components = serde_json::from_str::<openapi::Components>(components_json).unwrap();
dbg!(&components);

assert!(!components.schemas.is_empty());

Thanks your example works for Components :) I ended up removing all the unsupported fields from the YAML with the GeoJson specification and I can currently use the Deserialize trait as it.

Thanks your example works for Components :)

You are welcome


Adds a proof harness for s2n_stuffer_read_line

Please note that while we are transitioning from travis-ci to AWS CodeBuild, some tests are run on each platform. Non-AWS contributors will temporarily be unable to see CodeBuild results. We apologize for the inconvenience.
Resolved issues:
N/A.
Description of changes:

Adds a proof harness for the s2n_stuffer_read_line function;
Adds a pre- and post-conditions to the s2n_stuffer_read_line function;

Call-outs:
N/A.
Testing:
N/A.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #2048 into master will increase coverage by 0.01%.
The diff coverage is 80.00%.

@@            Coverage Diff             @@
##           master    #2048      +/-   ##
==========================================
+ Coverage   81.06%   81.07%   +0.01%
==========================================
  Files         247      247
  Lines       18390    18394       +4
==========================================
+ Hits        14907    14913       +6
+ Misses       3483     3481       -2


OC-316 ~ Adds support to send OSLP requests from the OslpMockServer t…

…o the Platform

This pull request makes the build fail.

This pull request makes the build fail.

This pull request makes the build fail.

This pull request makes the build fail.

This pull request makes the build fail.

 All committers of the pull request should sign our Contributor License Agreement in order to get your pull request merged.1 out of 2 committers have signed the CLA.:white_check_mark: MartijnSipsCGI:x: web-flow

This pull request makes the build fail.

This pull request makes the build fail.

please test this

This pull request makes the build fail.

This pull request makes the build fail.

This pull request makes the build fail.

All is well.


Add varchar/ubigint variant bindings

It looks like it should be possible to define variants of the H3 functions that accept varchar or ubigint, so users do not need to always convert the types if they have indexes as strings.
Reference https://github.com/duckdb/duckdb/blob/master/src/function/scalar/list/list_concat.cpp#L75

#47 may have a simpler way of doing this, as we need to have a limited set of types, it may be fine to just list the bindings all out.

BIGINT (signed 64 integer) could also be supported


Make build use ocaml from third-party with not installed on the host …

…system
Summary:
Whether ocaml was built from third-party or not, gen_build_id.ml was always
called using the host ocaml binary. This led to a build failure when no OCaml
interpreter was installed on the host system.
Signed-off-by: Arthur Loiret<EMAIL_ADDRESS>

Also see https://github.com/facebook/hhvm/pull/7704


pull request for e2e test at 01/15/2017 09:56:12

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


runtime: finalizer did not run

After CL https://go-review.googlesource.com/c/37520/ checked in, there are a couple of failures on the build dashboard. The failures are mostly related to finalizers, but may also include others like wrong number of goroutines. For example:
--- FAIL: TestStackGrowth (20.69s)
	stack_test.go:114: finalizer did not run
--- FAIL: TestEmptySlice (4.06s)
	mfinal_test.go:185: finalizer of next object in memory didn't run
--- FAIL: TestEmptyString (4.06s)
	mfinal_test.go:217: finalizer of next string in memory didn't run
--- FAIL: TestNumGoroutine (0.05s)
	proc_test.go:382: NumGoroutine=10, but found 11 goroutines in stack dump: goroutine 127528 [running]:

The failure is sporadic.
linux-mips64le:
https://build.golang.org/log/0b5c6130c6b1662e36a7956577ec677c1b80d7d4
https://build.golang.org/log/bbd7a380874739987ab10150d325ba55123f0ad6
freebsd-arm:
https://build.golang.org/log/e06e99f7bb6d15834d3ced9cd62f490666a3531a
https://build.golang.org/log/2c63f9ced656ef095edabe6178298749fbac5cd1
plan9-386:
https://build.golang.org/log/c69f2dd74ebf3c7a571ca902bb66fde0f9a4bb81
The linux-mips64le builder is single core. I wonder whether the other two builders are also single core. Not sure whether this is related.
cc @aclements

I think freebsd-arm is unrelated to CL 37520. It's been failing pretty regularly since mid-January (fdde7ba).
The other two look real. My hunch is that TestNumGoroutine is a cascade from the others. I don't have a hunch why the first three are failing.
No luck so far reproducing with GOMAXPROCS=2 numactl -C 0 stress -p 1 ./runtime.test -test.cpu=1,2,4 -test.short on linux/amd64. @cherrymui, is there a way I can access the linux/mips64le machine?

@aclements, unfortunately my home router's port forwarding stopped working a few months ago... Maybe I can bring the machine on Monday. Let me know if any command I can try locally in the meantime.

@cherrymui, it would be useful if you could run GOMAXPROCS=2 numactl -C 0 stress -p 1 ./runtime.test -test.cpu=1,2,4 -test.short just to see if that reproduces it. If it does, I can put together some debug patches.

Ok, I'll try it this evening.

This bug also rises randomly on my raspberry pi 2. I have to set
line 114 of src/runtime/stack_test.go from
case <-time.After(20 * time.Second):
to
case <-time.After(30 * time.Second):
to avoid it.

This one happens frequently on the android/arm builder:
https://build.golang.org/log/c22a2ed235e51df8991d0439881eb626d8053ec9
I can reproduce it fairly quickly with
GOOS=android GOARCH=arm go test -short -cpu=1,2,4 runtime
is there anything I can do to help?

Increasing the timeout in stack_test.go:114 to 30 seconds or checking out 44ed88a5a768a54c1880c58f3438bf2fa8639c4c (the parent of CL 37520) both make the problem go away.

Closing as a dup of #19381. (But there's useful discussion here, which I've linked to and summarized from that issue.)


Improve typing for useDoc and other firestore hooks

We should be able to do:
interface DataShape {
    status: 'pending' | 'active';
    otherProp: number;
}

const [data, isLoading] = useDoc<DataShape>({
    path: '',
})

then data should get the types defined in DataShape

closed by #596


change spec.str() into str(spec)

launch jenkins icon cosmo

These tests failed:
daint_cosmo_test_devbuild_cpu timed out waiting for write lock
daint_icon_test_devbuild_cpu timed out waiting for write lock
The failures have nothing to do with this PR. So, I consider them green.


custom workflow labels: custom_properties

Related to #339 .
This is probably a niche problem.
Would it be possible to, using the env variable GITHUB_EXPORTER_WORKFLOWS_LABELS, to add a  label for a custom_properties key.
Example webhook
{
  "action": "completed",
  "workflow_job": {...}
  "repository": {
   ...
   "custom_properties": {
      "DEPARTMENT": "JAVATEAM"
   }
}

This way we can add a label for the departement. Each department can have their own dashboard with metrics that are only relevant to their repo.

Can you explain more what you want to get in the end? Do you want to add labels which gets added to all metrics per exporter instance?


Add Configuration to doc website repo.

Signed-off-by: carolxob<EMAIL_ADDRESS>Description
Add Configuration to doc website repo.
Issues Resolved
Closes #1267
Checklist

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

@dlvenable This PR is ready for tech review.

Information already exists in Get Started, Pipelines, and Data Prepper Reference. Closing PR. @asifsmohammed if you see any information in these pages that you'd like to carry over in this configuration page, please let me know.


Adding forward DLQ to management option

adding ability to set a custom queue for DLQ forwarding

LGTM
the integration test failure is ACI related when using MSI.
the other auth mechanism worked fine, so I'd say merge it


support multiple rgw instances on a single host

As I found, only single rgw instance is could be created for a single host as we
use the hostname as the rgw instance name.
But we definitely would want to run multiple rgw instances on a single host with names like
$(hostname).1, $(hostname).2, $(hostname).3, ...
of course with different bind ports separately.
And more rgw instances on a single host will reduce the risk of dropping requests due to
a too long request queue.
I've tried the rgw-standalone.yml playbook at the master branch,
but it does not seems to work very well(as I saw, rgw process could start, but it failed to read
the specific port config for additional rgw instances)
As far as I know, ceph-ansible 2.1.1 seems to have the support for this feature,
but it definitely does not work for now.
Do you think this feature is meaningful, or why the support is eliminated during the development ?

e....since on one showed any interest in this, I tried to open a PR myself:
https://github.com/ceph/ceph-ansible/pull/3358


[Release-1.30] - Allow configuration of Rootlesskit's CopyUpDirs through an environment variable

Backport fix for Allow configuration of Rootlesskit's CopyUpDirs through an environment variable

#10385

Validated on release-1.30 branch with commit 737f5946c03c9f5599e2292af9852335d4861a62
Steps: https://github.com/k3s-io/k3s/issues/11006#issuecomment-2420180848
Validation
$ k3s -v
k3s version v1.30.5+k3s-737f5946 (737f5946)
go version go1.22.6

$ kubectl exec -it pod/basic -- ls my_share
pretest.txt
$ kubectl exec -it pod/basic -- touch my_share/hellop2l.txt
$ kubectl exec -it pod/basic -- ls my_share
hellop2l.txt  pretest.txt
$ ls containerShare/
pretest.txt


Traffic Shaping at instance registration

I believe that Fabio should be able to apply weight's of a service during registration without declaring a override.
For example
tags: [
  "urlprefix-example.com/",
  "weight-0.05",
  "foo"
]

Would result in this instance having %5 traffic routed to it because weight-$(myWeight) was specified.  I believe this will make it easier for users to perform Blue / Green Deployments.

urlprefix-example.com weight=0.05 should do the trick. I probably need to update the docs.

@magiconair Is that 1 tag space separated?
tags: [
  "urlprefix-example.com/ weight-0.05",
  "foo"
]

Like this?

@magiconair,
I just confirmed that this works.  Are there more things I can set via tags at registration?
You can close this :)

@magiconair
Is there a way to view the version tag in the UI for each service?
The following image displays 0.05 for version 1.0.1 and 0.15 for version 1.0.2 .  I'd like to be able to identify that... I'm assuming there is something I'm missing?


Remove unnecessary bounded_offset from PathFollow2D

This is no longer necessary after #29172
Resolves #7665
Might slightly break compatibility.

Thanks!


Updated for newer EMR for Spark and Scala

also added install-spark-shark.sh and run-spark-job-0.1.0.sh to scripts directory for self hosting

EMR Commands https://gist.github.com/bigsnarfdude/92154d84ce222e118bac

Closing to open PR under issue


Weird indentation with match guard containing parentheses

Before:
    match input.trim().parse::<f64>() {
        Ok(val) if !(
            // A valid number is the same as what rust considers to be valid,
            // except for +1., NaN, and Infinity.
            val.is_infinite() || val.is_nan() || input.ends_with(".") || input.starts_with("+")
        ) => {
        }

After:
    match input.trim().parse::<f64>() {
        Ok(val)
            if !(
            // A valid number is the same as what rust considers to be valid,
            // except for +1., NaN, and Infinity.
            val.is_infinite() || val.is_nan() || input.ends_with(".") || input.starts_with("+")
        ) =>
        {
        }

This may be related to #3005.

I think the real error is that rustfmt does not format a paren expression with // comment. Putting if ... on the next line is ok w.r.t. the rfc (though I think putting it on the same line looks better - we could probably add some heuristics for this).


Add ability to re-use skills within the same project

add ability to copy a read-only version of a skill into a different subject or group (copy-by-reference)
one idea is to enhance the copy skill button, another idea is to add another button next to the copy button

PR: https://github.com/NationalSecurityAgency/skills-service/pull/1469

:+1:


Forum by default in asian language?

The forum uses an asian language. Somehow this looks strange.
I guess this is a configuration error with your forum software:

Strange, now it is in english again. Closing this.


[CHORE]: Investigate v29 Changes

With the significant UI changes in version 29 I need to audit tests against v29 to determine what if any changes are needed.

Run tests for the following features against v29:

[ ] App
[ ] Survey Supporting Data App
[ ] API Key
[ ] Attachment Field
[ ] Content Record
[ ] Date/Time Field
[ ] Date/Time Formula Field
[ ] Formatted Text Block Object
[ ] Image Field
[ ] List Field
[ ] List Formula Field
[ ] Number Field
[ ] Number Formula Field
[ ] Reference Field
[ ] Text Field
[ ] Text Formula Field
[ ] Time Span Field
[ ] Email Body
[ ] Data Import
[ ] User
[ ] Attachment Question
[ ] Date/Time Question
[ ] Likert Scale Question
[ ] Matrix Question
[ ] Multi Select Question
[ ] Number Question
[ ] Reference Question
[ ] Single Select Question
[ ] Text Question
[ ] Container
[ ] Group
[ ] Role
[ ] Survey Page
[ ] Survey Design


pyautogui.size() gives wrong resolution on Windows 10 laptop

Description:
pyautogui.size(), pyautogui.position(), pyautogui.moveTo() and some more functions are giving wrong output on Windows 10 and Windows 8 laptops (I tried on Lenovo and Dell). However, things are working fine on desktops with Windows 8 and Windows 10 versions.
Python version: 2.7.12 and 2.7.11
Please see the attached image.

I also saw this

What are the models of the laptops?

Some preliminary research suggests that it might be the screen DPI setting.
In Windows 8, you can right-click on the desktop, select Screen Resolution, and then click "Make text and other items larger or smaller". This might be different for Windows 10, but I believe it still exists.

yes indeed that's it.
Put the slider to 100% to get the proper size...

#116 has a clever workaround for this it seems.

I've added the DPI scaling fix to 0.9.35, so hopefully this is now fixed.