Auto-injectors transfers solution to beaker

Description
Infinite Dex+ supply by injecting beaker and then refilling autoinjector.

Could not repro. Steps?

Could not repro. Steps?

Take autoinjector (for example CMBicaridineAutoInjector)
Click on beaker
"You inject large beaker"

That seems correct? I'm not seeing where the infinite chems are factoring in.

That seems correct? I'm not seeing where the infinite chems are factoring in.

You can refill autoinjector in MarineMed/We-Ya Med Plus.


Update S2_nircam_wfss_template.ecf

skip_bkg_subtract was set to False by default

Codecov Report

Merging #417 (b231ff5) into main (19cfebf) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #417   +/-   ##
=======================================
  Coverage   58.06%   58.06%
=======================================
  Files          71       71
  Lines        7497     7497
=======================================
  Hits         4353     4353
  Misses       3144     3144

Help us with your feedback. Take ten seconds to tell us how you rate us.


One test is always skipped

Let me preface by saying that the test infrastructure in meson.build is inscrutable to me (and that this is why GSSAPI support is still outstanding).
But it definitely appears to my eye that if tests only has a single value, no tests get run, and if I define n tests, meson/ninja are only aware of n-1 of them.

Figure it out?

Yes.  Going to include some notes in PR (hopefully soon).


unresolved address error while harvesting STUN candidates

While running IceDistributed , getting the following error:
Mar 04, 2023 1:18:14 PM org.ice4j.ice.harvest.StunCandidateHarvest sendRequest
INFO: Failed to send ALLOCATE-REQUEST(0x3)[attrib.count=3 len=32 tranID=0x26C197AB86016EEB5E36E9A6] through <IP_ADDRESS>:2020/udp to stun6.jitsi.net:3478/udp
java.lang.IllegalArgumentException: unresolved address
at java.base/java.net.DatagramPacket.setSocketAddress(DatagramPacket.java:350)
at java.base/java.net.DatagramPacket.(DatagramPacket.java:157)
at org.ice4j.stack.Connector.sendMessage(Connector.java:326)
at org.ice4j.stack.NetAccessManager.sendMessage(NetAccessManager.java:634)
at org.ice4j.stack.NetAccessManager.sendMessage(NetAccessManager.java:581)
at org.ice4j.stack.StunClientTransaction.sendRequest0(StunClientTransaction.java:267)
at org.ice4j.stack.StunClientTransaction.sendRequest(StunClientTransaction.java:245)
at org.ice4j.stack.StunStack.sendRequest(StunStack.java:680)
at org.ice4j.stack.StunStack.sendRequest(StunStack.java:618)
at org.ice4j.ice.harvest.StunCandidateHarvest.sendRequest(StunCandidateHarvest.java:1300)
at org.ice4j.ice.harvest.StunCandidateHarvest.startResolvingCandidate(StunCandidateHarvest.java:1405)
at org.ice4j.ice.harvest.StunCandidateHarvester.startResolvingCandidate(StunCandidateHarvester.java:340)
at org.ice4j.ice.harvest.StunCandidateHarvester.harvest(StunCandidateHarvester.java:252)
at org.ice4j.ice.harvest.CandidateHarvesterSetElement.harvest(CandidateHarvesterSetElement.java:86)
at org.ice4j.ice.harvest.CandidateHarvesterSetTask.run(CandidateHarvesterSetTask.java:107)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:577)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1589)

Indeed that DNS entry doesn't appear to exist any more.
@aaronkvanmeerten @bgrozev any idea what happened here?

it was an issue with the STUN/TURN servers URLs in Ice.java. (stun.jitsi.net:3478 not getting resolved)
tried with google's Stun server..it worked.


Interaction between cellDates and dateNF

I'm trying to parse some dates from a base64 string or a binary string.
The parsing configuration:

cellDates: false
dateNF: 'dd/mm/yyyy"

The data example:

COD,DES,DATE,NUM
01,ZEROONE,12/01/2009,1.2
02,ZEROTWO,16/02/2016,3

With base64 parsing type:

cellDates seems to be ignored, cell datatype is always "d".
dateNF ignored too, date output format is "mm/dd/yyyy"
https://jsfiddle.net/fd30kLg6/1/

with binary parsing type:

cellDates works fine, cell datatype "n" (and "d" with cellDates true)
dateNF ignored, date output format is "mm/dd/yyyy"

Am I misunderstanding how cellDates and dateNF works?

Thanks for reporting @mmancosu !  Your understanding is correct, cellDates:true should be generating date cells with type "d", cellDates:false should be generating numeric cells, dateNF should override the default date format.  Neither option has been applied to CSV, we'll fix it in the next push.
Background: cellDates is an option that mainly pertains to the XLS/XLSX/XLSB file formats.  XLS and XLSB don't really have a native date type -- they store numbers and the "date" comes from the number format.  For example, Saturday May 13 2017 is the number 42868:

(XLSX technically has a date cell type but Excel generates XLSX files that solely use the number form)
For example, with
sheetjs.xlsx in node:
> XLSX.readFile('sheetjs.xlsx').Sheets.SheetJS.C3
{ t: 'n', v: 41689.604166666664, w: '2/19/14' } // <-- default uses the number code
> XLSX.readFile('sheetjs.xlsx', {cellDates:true}).Sheets.SheetJS.C3
{ t: 'd', v: 2014-02-19T14:30:00.000Z, w: '2/19/14' } // <-- when cellDates is true, generate a date cell instead
> XLSX.readFile('sheetjs.xlsx', {dateNF:"dd/mm/yyyy"}).Sheets.SheetJS.C3
{ t: 'n', v: 41689.604166666664, w: '19/02/2014' } // <-- use the specified number format
> XLSX.readFile('sheetjs.xlsx', {dateNF:"dd/mm/yyyy", cellDates:true}).Sheets.SheetJS.C3
{ t: 'd', v: 2014-02-19T14:30:00.000Z, w: '19/02/2014' } // <-- use the specified number format

@mmancosu the current master should honor the cellDates/dateNF options for CSV.  We'll ensure other formats also honor the options before closing the issue

I still have a parsing problem in version 0.10.2.
dateNF is used for formatting the output but not as parsing option.
In my example

COD,DES,DATE,NUM
01,ZEROONE,12/01/2009,1.2
02,ZEROTWO,16/02/2016,3

dates are in dd/mm/yyyy format.
The parsing system from base64 text returns 12/01/2009 as 30/11/2009, clearly reading from the format mm/dd/yyyy. 16/02/2016 returns data type string, because 16 is not a valid month.
Fiddle proving it: https://jsfiddle.net/92qu04vd/2/

@SheetJSDev
This was helpful! Thank you. I would like to someday devote some time to helping you guys make better documentation if thats an option?.. Give back to SheetJs a bit and get my company to give a donation once we have completed this project.


Favicon issue

When first time Site is bootup then favicon is work fine but navigate to different url then it's not working properly.
@tirthbodawala  have you checked this issue?

@RizwanZaheer Checking this right now. I see the issue here... Thanks for reporting.

Thanks @tirthbodawala ,
Let me know when you fix this bug :)

@RizwanZaheer This bug has been solved with the implementation of PawJS v2. Unfortunately, it is a major change and would require upgrading a lot, but upgrading to PawJS v2 is recommended for more performance.

Thanks @tirthbodawala
can you please share the migration steps for us.


Baklava docs improvements

Description
This PR applies some improvements and address comments
Tested
Other changes
Related issues
v2 of #1688
Backwards compatibility

@aaitor Just merged for others to build upon this PR, please address @asaj 's comments in follow on PR


mysql key length errors with utf8mb4

Laravel Version: 5.4
PHP Version: 7.0.14
Database Driver & Version: 10.1.18-MariaDB

Description:
Setting the default collation to utf8mb4 (see https://github.com/laravel/laravel/commit/9d01389ce3039f483dcc9ed405e02ba49042bfa3) means that out of the box migrations failed with a mysql key length error:
SQLSTATE[42000]: Syntax error or access violation: 1071 Specified
   key was too long; max key length is 767 bytes (SQL: alter table
  `users` add unique `email`(`email`))

Previously raised in https://github.com/laravel/framework/issues/15725
Steps To Reproduce:
composer create-project laravel/laravel okr dev-develop
config the db connection in .env and add a database with utf8mb4 and utf8mb4_unicode_ci
php artisan migrate

I was also seeing this issue yesterday. L5.4, PHP 7.0.13, MySQL 5.6.34

It was discussed many times. for example here #11451
Shortly what is going wrong:
By default string column uses 255 characters, in utf8mb4  each character cost 4 bytes.  4*255=1020. But maximum key length is 767.
So you can reduce length of column to 191
or try to use MySQL 5.7, it has no errors like that for me

Mysql 5.7.7 introduced changes to the default innodb parameters.

Important Change; InnoDB: The following changes were made to InnoDB configuration parameter default values:

The innodb_file_format default value was changed to Barracuda. The previous default value was Antelope. This change allows tables to use Compressed or Dynamic row formats.
The innodb_large_prefix default value was changed to ON. The previous default was OFF. When innodb_file_format is set to Barracuda, innodb_large_prefix=ON allows index key prefixes longer than 767 bytes (up to 3072 bytes) for tables that use a Compressed or Dynamic row format.
The innodb_strict_mode default value was changed to ON. The previous default was OFF. When innodb_strict_mode is enabled, InnoDB raises error conditions in certain cases, rather than issuing a warning and processing the specified statement (perhaps with unintended behavior).

Source: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-7.html

Yeah i understand whats going on, my issue is that out of the box things don't work, if mysql5.7 is a requirement we should document that, or at least have something in the docs to explain whats going on when this happens

https://github.com/laravel/framework/issues/11518#issuecomment-167406157

Been playing with this one tonight.
Did the switch from mysql -> mariadb. Going back to get mysql 5.7 to make this go away would cost me a lot of time with having to dump and replay a couple of large databases.
When mariadb 10.2 is stable and released, this will go away as the defaults mirror mysql 5.7.7
Using mariadb 10.1.21
Adding to my.cnf
innodb_large_prefix=1
innodb_file_format=Barracuda
which are both defaults in 10.2
unfortunately the directive ROW_FORMAT=DYNAMIC only exists from 10.2.2
but found adding the directive to the sql string in MySqlGrammar after collation for every table creation does the trick and creates the larger index keeping everything happy in 10.1.x
Believe this will also work for MySQL 5.6

An hack would be $table->engine='innodb ROW_FORMAT=DYNAMIC'; in every migration that creates a table. The dynamic row_format is the default starting from mariadb 10.2.2, it is supported starting at mysql 5.5 so mariadb 5.5 and upward (including all 10.x) should support it.

I agree this should be open and probably the default  length changed. I assume there is no special reason that it is 255 now, other than that used to be the max length back in MySQL < 5.0.3?
migrate should generate a schema compatible with the target database server. It knows the target database engine and version when it generates the schema, so it should be smarter about either warning the user, or generating a compatible schema.
There are lots of tickets for this same thing #17530 #17508 #17337 #17714 #20012 because migrate is creating a bad user experience.
On the upside, it is well documented 👍, but better migrate behavior would be preferable.

I propose an alternative to Schema::defaultStringLength(191); in artisan command line. Something like php artisan migrate -dsl=191. This way we can accommodate for various versions of Mysql/MariaDB in different environments.

Any up to date ways to solve this? With latest mariadb, and laravel.

Problem still seems to persist as of today, at least for me.
I am using Laravel 9 and MySQL with MariaDB 10.3.3.
Note that innodb_large_prefix and innodb_file_format have been removed from MariaDB (see https://mariadb.com/kb/en/innodb-system-variables/)
At the same time it seems that starting from MariaDB 10.2.2 the default File Format has been changed to Barracuda, so I am wondering why the error keeps popping out.
Maybe we should just turn off MySQL Safe mode?
I mean, setting defaultStringLength(191) does not seem to be the best solution either anyway.


[Runtime Bug] Sonic Riders: In-game character models have misaligned limbs, hair, etc.

Describe the bug

Character models in-game have severely misaligned parts, such as limbs, shoes, hair etc.
0.4.1
RTX 3060
551.52
<IP_ADDRESS> (it’s from Sega PC Collection 2009)

Attach files!
SonicRiders RTXRemixLogsbugreport.zip
To Reproduce
Steps to reproduce the behavior:

Select any mode and map
Select character that you wish to play as (Tails is the easiest to see the bug on)
See error
(bonus) See the misaligned parts in-game during the race

Expected behavior

The in-game character models are supposed to have their parts, limbs, hair etc. aligned correctly with their bodies.

Screenshots

The bug still appears on 0.5.0 Runtime

REMIX-3138 for tracking


Add view values to lookup actions menu

On the look ups page you can now click on the magnifying glass icon to view the key value pairs of that lookup.

Looks great, thank you 👍


log can not format

I am really confusing right now:
from absl import logging as logger
import logging

fmt = '[%(levelname)s %(asctime)s %(filename)s:%(lineno)s] %(message)s'
formatter = logging.Formatter(fmt)

logger.get_absl_handler().setFormatter(formatter)
logger.set_verbosity('debug')

a = 3434
logger.info('{}'.format(a))

Doesn't applied format........... it prints
INFO:absl:3434

I want line number and filename time etc....

Closing as a duplicate of https://github.com/abseil/abseil-py/issues/124.


Add compile-time hardening flags, and enable by default.

LGTM, just a nit.

I've had to modify a bit to support gcc/g++ too, PTAL.

This feels like it's slowly turning into the tarpit I was expecting... :disappointed:

All right, let's have that, and figure it out better later.


Update pod version to 7.0.4 in README.rst

I'm sorry, I forgot to update README file

No problem, it's just an example, doesn't need to be updated each time.


Added OpenIG

Added OpenIG to tracking list

Hi Aditi can you review the changes

I reviewed now  add the Reviewers they will merged


Remove Livisi Unoffival

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
Logger: homeassistant.components.fritzbox_callmonitor
Quelle: components/fritzbox_callmonitor/init.py:48
Integration: AVM FRITZ!Box Call Monitor (Dokumentation, Probleme)
Erstmals aufgetreten: 18:37:16 (1 Vorkommnisse)
Zuletzt protokolliert: 18:37:16
Invalid authentication: Unable to perform operation. 401 Unauthorized (ERR_NONE) 401 Unauthorized ERR_NONE Webserver Mon, 22 Apr 2024 16:37:16 GMT
Logger: homeassistant.helpers.frame
Quelle: helpers/frame.py:188
Erstmals aufgetreten: 18:37:11 (1 Vorkommnisse)
Zuletzt protokolliert: 18:37:11
Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues
Logger: homeassistant.components.cover
Quelle: helpers/entity_platform.py:744
Integration: Abdeckung (Dokumentation, Probleme)
Erstmals aufgetreten: 18:37:36 (96 Vorkommnisse)
Zuletzt protokolliert: 18:37:42
Platform livisi does not generate unique IDs. ID 27d9c3d6d0484b9b8baa572e0d2f7bd4 already exists - ignoring cover.rollladen_strasse
Platform livisi does not generate unique IDs. ID 498cdf515e344ea9bfd286997c689d3b already exists - ignoring cover.rollladen_carport
Platform livisi does not generate unique IDs. ID 1826c8691ca24d229b613f299e6f7fca already exists - ignoring cover.rollladen_garten
Platform livisi does not generate unique IDs. ID e2920798fef54dd6a66a261644e60f8e already exists - ignoring cover.rollladen_terasse
Describe the solution you'd like
Beseitigung des Problems
Describe alternatives you've considered
keine
Additional context
keiner

Unfortunately, I cannot debug issues with the cover integration (as I don't have any), but I think this problem comes from a broken setup (maybe an update that went wrong). Removing the SHC and entities and then readding it should help in these cases. As long as they haven't been renamed, all entities will get the same name.


Load Image in Standalone

Hi, is there a way to load the image save from standalone?

hi, i found a way, thanks!


[Docs] Update docs for new entry script

Preview at https://opencompass--246.org.readthedocs.build/zh_CN/246/get_started.html#quick-start

Chinese document first, English version will be released in next release.

https://opencompass--246.org.readthedocs.build/en/246/get_started.html#quick-start


Adding my school

my school site
http://www.itisgalilei.edu.it/

@profmassimopisani First stage of verification passed, official domain is itisgalilei.edu.it as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: https://www.itisgalilei.edu.it/pagine/contatti

@profmassimopisani Thank you for your patience while waiting for a review and processing your request. Pull request merged.


OpenAPI incorrect oneOf definition when used with required

What version of CUE are you using (cue version)?

$ cue version
cue version (devel)

go version go1.20.7
      -buildmode exe
       -compiler gc
     CGO_ENABLED 1
          GOARCH arm64
            GOOS darwin

Does this issue reproduce with the latest stable release?
Yes
What did you do?

exec cue import spec.yml -o -

-- cue.mod/module.cue --
module: "loftorbital.com/crdcue"
-- spec.cue --
// OneOf test

info: {
	title:   *"OneOf test" | string
	version: *"1.0.0" | string
}
// Oneof test
#main: ({
	opt1: _
	...
} | {
	opt2: _
	...
}) & {
	// option 1
	opt1?: string

	// option 2
	opt2?: string
	...
}

What did you expect to see?
// OneOf test
info: {
    title:   *"OneOf test" | string
    version: *"1.0.0" | string
}
// Oneof test
#main: {
    { opt1: string } | { opt2: string}
}

or something akin.
What did you see instead?
// OneOf test

info: {
	title:   *"OneOf test" | string
	version: *"1.0.0" | string
}
// Oneof test
#main: ({
	opt1: _
	...
} | {
	opt2: _
	...
}) & {
	// option 1
	opt1?: string

	// option 2
	opt2?: string
	...
}

which fails to vet correct values like
obj: #main & {
    opt1: "foo"
}

(incomplete)

This is one of the situations where the current "encoding" of one-ofs fails/is just plain wrong. Whilst #943 will address this with a builtin, we could consider switching our notion of one-of "encoding" to be something like the following:
exec cue export x.cue working.cue
cmp stdout stdout.golden

! exec cue export x.cue broken.cue
cmp stderr stderr.golden

-- x.cue --
package x

#main: {
	{
		opt1?: string
		opt2?: _|_
	} | {
		opt1?: _|_
		opt2:  string
	}

	// Not sure whether you wanted the definition open or not.
	// Comment out if not.
	...
}

-- working.cue --
package x

examples: [string]: #main

examples: obj1: #main & {
	opt1: "foo"
}

examples: obj2: #main & {
	opt1: "foo"
	opt3: "test"
}

-- broken.cue --
package x

examples: bad: #main & {
	opt1: "foo"
	opt2: "test"
}
-- stdout.golden --
{
    "examples": {
        "obj1": {
            "opt1": "foo"
        },
        "obj2": {
            "opt1": "foo",
            "opt3": "test"
        }
    }
}
-- stderr.golden --
examples.bad: 2 errors in empty disjunction:
explicit error (_|_ literal) in source:
    ./x.cue:6:10
explicit error (_|_ literal) in source:
    ./x.cue:8:10

https://tip.cuelang.org/play/?id=GmmKjdTk_h9#cue@export@json contains a variation of that.

Yup that would work. The error message would not the best in term of UX, but in term of functionality that would fix the issue.

Yup that would work. The error message would not the best in term of UX, but in term of functionality that would fix the issue.

Absolutely. A builtin would facilitate a much more precise error message.

ISTM there are a few of issues going on here. For reference, here's a full testscript example that includes the source OpenAPI spec that wasn't included above:
exec cue import -p x spec.yml
exec cat spec.cue
exec cue vet -c
-- spec.yml --
openapi: 3.1.0
info:
  title: OneOf test
  version: 1.0.0
components:
  schemas:
    main:
      description: Oneof test
      oneOf:
        - required:
            - opt1
        - required:
            - opt2
      properties:
        opt1:
          description: option 1
          type: string
        opt2:
          description: option 2
          type: string
      type: object
-- cue.mod/module.cue --
module: "example.com"

-- test.cue --
package x

examples: [string]: #main

examples: obj1: opt1: "foo"
examples: obj2: opt2: "foo"

This currently fails:
> exec cue import -p x spec.yml
> exec cat spec.cue
[stdout]
// OneOf test
package x

info: {
	title:   *"OneOf test" | string
	version: *"1.0.0" | string
}
// Oneof test
#main: ({
	opt1: _
	...
} | {
	opt2: _
	...
}) & {
	// option 1
	opt1?: string

	// option 2
	opt2?: string
	...
}
> exec cue vet -c
[stderr]
examples.obj1: incomplete value {opt1:"foo",opt2?:string} | {opt1:"foo",opt2:string}
examples.obj2: incomplete value {opt2:"foo",opt1:string} | {opt2:"foo",opt1?:string}
[exit status 1]
FAIL: /tmp/testscript2972845514/x.txtar/script.txtar:3: unexpected command failure

Specific issues:

since both arms of the disjunction are valid for the input, we get the incomplete value error. This is the issue that @myitcv points out above.
the #main definition is using regular fields where it should be using required fields
the disjunction is unified with a struct that contains all the (optional) fields; instead, the fields should only be defined in the arms of the disjunction.

There's another issue: in the above example, additional fields are allowed, but if we explicitly try to disallow them (by specifying additionalProperties: false), the resulting CUE allows them anyway. Here's a repro for that:
exec cue import -p x spec.yml
exec cat spec.cue
exec cue vet -c
-- spec.yml --
openapi: 3.1.0
info:
  title: OneOf test
  version: 1.0.0
components:
  schemas:
    main:
      description: Oneof test
      oneOf:
        - required:
            - opt1
        - required:
            - opt2
      properties:
        opt1:
          description: option 1
          type: string
        opt2:
          description: option 2
          type: string
      additionalProperties: false
      type: object
-- cue.mod/module.cue --
module: "example.com"

-- test.cue --
package x

examples: [string]: #main

examples: obj1: opt1: "foo"
examples: obj2: opt2: "foo"

Result:
> exec cue import -p x spec.yml
> exec cat spec.cue
[stdout]
// OneOf test
package x

info: {
	title:   *"OneOf test" | string
	version: *"1.0.0" | string
}
// Oneof test
#main: ({
	opt1: _
	...
} | {
	opt2: _
	...
}) & {
	// option 1
	opt1?: string

	// option 2
	opt2?: string
}
> exec cue vet -c
[stderr]
examples.obj1: incomplete value {opt1:"foo",opt2?:string} | {opt1:"foo",opt2:string}
examples.obj2: incomplete value {opt2:"foo",opt1:string} | {opt2:"foo",opt1?:string}
[exit status 1]
FAIL: /tmp/testscript1805129990/x.txtar/script.txtar:3: unexpected command failure

Even without an explicit new builtin for this purpose, the above should work: it should probably produce something like the following definition for #main, which then validates OK:
#main: {
	opt1!: _
} | {
	opt2!: _
}

There's another issue: in the above example, additional fields are allowed, but if we explicitly try to disallow them (by specifying additionalProperties: false), the resulting CUE allows them anyway.

I'm not 100% on the detail but I think this is an artefact of OpenAPI's usage of JSON Schema. I have a vague recollection of @mpvl telling me that this "encoding" within CUE is deliberate, because OpenAPI is intentionally "open".

FWIW I looked for any indication of this kind of difference and was unable to find one. To the best of my knowledge, OpenAPI's JSON Schema is exactly the same as regular JSON Schema. Here's some evidence of that: https://apisyouwonthate.com/blog/openapi-v3-1-and-json-schema/
I'm fairly sure that if there was a distinction in the treatment of additionalProperties between the two, it would have been mentioned in that article or one of those that it points to.

Very related to this I've just raised https://github.com/cue-lang/cue/issues/3165 to capture discussion on how oneofs could/should be encoded in CUE. That new issue provides a JSON Schema example, but I don't think the question of how we encode oneofs is specific to JSON Schema necessarily. Protocol Buffers also has the concept - quite how the semantics and implementation lines up I'm not 100% sure.
On the basis OpenAPI uses an extended subset of JSON Schema, I'm tempted to close this issue and move discussion of how we should encode oneofs (perhaps generally) into https://github.com/cue-lang/cue/issues/3165, consolidating this and a number of other issues.
Please do say though if I'm holding things wrong and we need to keep this open for OpenAPI-specific reasons. If we do, we need to evolve the conversation in https://github.com/cue-lang/cue/issues/3165 in any case to make clear how specific encodings might carry with them specific oneof-semantics/details.


Rename "export" to "release"

Secure key release will be changing the export API and enum to release. We must change all our export-related APIs accordingly. Keep an eye on the swagger for when that change occurs.

This bug is actually incorrect, as "export" and "release" are separate operations.

This bug is actually incorrect, as "export" and "release" are separate operations.


Add Copy-Paste functionality for Nodes

Problem
There's sometimes situations where it is faster, specially for duplicating structures, to copy and paste your current selection of Nodes that it is to recreate that structure from scratch. The 1st option is currently not possible.
Proposed Solution
In a similar fashion to moving several selected Nodes at once, we could include Copy/Cut/Paste functionalities to Nodes, so that Nodes can be selected and then easily duplicated or repositioned through these shortcuts. The existing Dictionary-based Save&Load system that exists for Nodes could be useful for this purpose.
Ideally, this feature should be included in the Undo/Redo system, so that using these actions can be undone and redone as you would for any other changes in the DialogueData file.
Additionally, as a user, I would expect for selected Nodes I've duplicated or moved to retain the connections between them, as in connections between the Nodes I've edited. I would not expect (nor desire) for Nodes that I've Cut+Paste or Duplicated to retain connections to Nodes I've not performed the same operation on, i.e. Nodes that I've "left out".

Currently, the editor supports duplicating the selected nodes using CTRL+D, but I can see cases where copy/paste would be more useful, like copying nodes from one file to another. The idea of converting the selection into a temporary DialogueData resource and using it to copy/paste/duplicate is something I experimented in the past but it turned out to be a bit complicated for me. I'll definitely take a look into it again soon. Cheers!

I don't see this as a priority, but I feel it is a set of actions that feel really natural to execute, and when using the addon for the first time you expect it to be there. This holds little importance, but if we can add it eventually it would be a net positive for the addon imo.


⚠ Aither has degraded performance

In 77d5bac, Aither ($AIH) experienced degraded performance:

HTTP code: 200
Response time: 15060 ms

Resolved: Aither performance has improved in d367c1c.


Broken example?

I can't get the example from the setup instructions in the README to work.
It says to do
  import {type Editor, EditorTheme, SvelteEditor} from '@nextlint/svelte';

but Editor doesn't seem to be exported by this library. Its content is
export { default as SvelteEditor } from './Editor.svelte';
export { default as EditorTheme } from './EditorTheme.svelte';

so no Editor.

Having similar issue

Hi @rotimi-best  @andoppomny ,
Yes the docs is outdate. I'm working on update it.
Thanks for report!

Hi @andoppomny  @rotimi-best ,
Please try the new version 2.1.0


Pbkdf2

This is a PBKDF2 pure JS implementation to progress towards supporting BIP39 mnemonics (I'll branch mnemonics off of this - want to try to keep reviews small and make sure I'm on the right track code-style-wise).
It's based on this implementation https://github.com/browserify/pbkdf2/blob/master/lib/sync-browser.js with a change to support derivedKeyLength that is less than the hmacLength (both NodeJS's PBKDF2 implementation and Python's support this - the test vectors I've found also have this).
The interface is a it clunky - I've tried to keep to the "under three params" lint rule and, unfortunately, we need to know the HMAC length in advance (we could determine this at run-time by "trying it", but I'm not sure that feels proper or efficient?j). Currently, the Pbkdf2PHmac interface breaks the functional/no-mixed-type linter rule too - but I'm not too sure what's a good approach for this (maybe I remove this interface and just pass those params direct into function? Let me know if you have any suggestions).
The implementation itself breaks many linter rules. At the moment, I've set a lot of these to be ignored as there's some precedent for this in the CashAddress implementation and rewriting around them may be less efficient considering we're dealing with an algo that iterates into the thousands in practice. Let me know what's preferred here and I can try to rewrite.
Overall, if you could take a look and just let me know which parts you'd like refactored and whether the general direction (e.g. the tests) look appropriate, that'd be great. I'm still digesting and learning the styles from elsewhere in Libauth.

Hey Jim, really fantastic work, thank you! 🚀
On first review the code and interface look great, and code/comment style is excellent!
Did you consider turning pbkdf2HmacSha256 and pbkdf2HmacSha512 into exported functions themselves? So the pbkdf2 function might become something more like instantiateHmacFunction, maybe instantiatePbkdf2Function?
Since your ultimate goal with this is to add BIP39 support, if you're willing, I'd love to see that in this PR too! That would let us confirm that the interface is exactly what we need + improve test coverage.

@bitjson probably ready for another look now. Note the long list of ignored linter rules and which ones we should try to fix up.
Original algo is taken from https://github.com/browserify/pbkdf2/blob/master/lib/sync-browser.js

Just pushed my initial recommendation, but feel free to experiment with other options 👍

I think this is finally ready for review (sorry about how long this took!)
A few notes:

It was hard to find suitable vectors - those referenced in BIP39 all used the passphrase "TREZOR" and did not provide the seed value without the passphrase. In the end, I decided to just generate using the following script so that I could have both a) without passphrase and b) with passphrase. If preferred, I can do a conversion of the Trezor vectors to derive seed value without passphrase, but I thought we might want to tinker with the number of vectors to reduce overall test time (I've done four per wordlist in the below).

import bip39 from 'bip39';

const wordlists = ['english', 'chinese_simplified', 'japanese', 'spanish', 'italian', 'french', 'korean', 'czech', 'portuguese', 'chinese_traditional'];

let validData = [];

// Create tests for each wordlist.
for(let wordList of wordlists) {
	// Set the wordlist to use.
	bip39.setDefaultWordlist(wordList)

	// Generate four mnemonics using the given wordlist.
	for (let i = 0; i < 4; i++) {
		const passphrase = 'libauth';
		const mnemonic = bip39.generateMnemonic();
		const seed = bip39.mnemonicToSeedSync(mnemonic).toString('hex');
		const seedUsingPassphrase = bip39.mnemonicToSeedSync(mnemonic, passphrase).toString('hex');
		const entropy = bip39.mnemonicToEntropy(mnemonic);

		const test = {
			entropy,
			mnemonic,
			seed,
			wordList,
			passphrase,
			seedUsingPassphrase,
		}

		validData.push(test)
	}
}

console.log(JSON.stringify(validData, null, 2));

I've cheated in some places with eslint ignore where I couldn't find an otherwise elegant solution (or name).

Japanese is exceptional - it uses a \u3000 separator as opposed to a space character. Detection of Japanese wordlist is dirty - but it seems most other implementations use a similar approach.

There is almost 100% test coverage. The one exception is with an entropy check function which I think is redundant - but is in the bip39 npm package I based this on. I've left it there just in case there's some undocumented edge-case that I'm unaware of but please let me know if you think I can safely remove it.

Wow, fantastic work @jimtendo! Thanks for the attention to detail, this looks great. I'm going to dedicate some more time to reviewing it, and I'll pull it in with the next release. 🚀

Thanks again for all your work here @jimtendo! 🎉
I added a few more functions, expanded the docs, and added a few more tests (including fuzzing/property-based testing) in https://github.com/bitauth/libauth/pull/116/commits/4709c17c2e2876c6f7a1910c84c292991bc84fba.
Now released in<EMAIL_ADDRESS>🚀


Documentation suggestion for SZWESAMP(ZWESECUR)

@xwu0226 commented on Tue May 12 2020
Describe the bug
In SZWESAMP(ZWESECUR)
ZWESECUR sample should have a line with CONNECT for normal user IDs as it does for administrative user IDs for clarity.

Duplicate of #1202. Closing.


Fixed one typo in README.md

Fixed one typo in README.md

Thank you very much for the PR @sandakersmann.
In this case, "interoperably" is an adverb meaning "in an interoperable manner". The whole sentence means that Zebra and zcashd can maintain the Zcash network together in an interoperable manner.
If the phrasing still doesn't seem right, let us know, and we'll come up with a more suitable alternative.

@upbqdn "interoperably" does not exist in the dictionary:
https://www.oxfordlearnersdictionaries.com/spellcheck/english/?q=interoperably

Yea, that word is peculiar, and is probably going to cause confusion. What if we replaced it with "together"?

Sounds good :)

If you want to fix it, push a new commit, and I'll merge it. Otherwise, I'll do it over the week.

It's ready to be merged :)


Monorepo project builds & deploys on any change

I'm using the Amplify console to deploy a site. Originally this site was in its own githib repo, but i've just moved it into a monorepo.
The application now live in the standard monorepo structure which is, for example packages/app-a next to a whole load of other packages.
I don't want to set up a new app in Amplify as i have lots of data. For this reason i have just clicked re-connect repo, but when i do this there is no monorepo checkbox.
I thought just moving the amplify.yml out to the root, and specifying an appRoot would work fine, and it does deploy the site on commits to the branches as expected, but any commit to the repo triggers a build.
As i understand it should only build when the specific package has changed, is that right?
version: 1
applications:
  - appRoot: packages/app-a
    backend:

Is there something else i need to do in order to get this working, or have i misunderstood how this should work?
Thanks!

@dhoulker you need to first define the build settings in the amplify console, run a build, and then move it to the amplify.yml. Here's instructions: https://gist.github.com/swaminator/3f2e400675f3322ed76bad82a59b393b


uv tool install yewtube results in httpx post failure

OS: MacOS Sonoma 14.6.1
UV version:
uv 0.5.5 (95cd8b8b3 2024-11-27)
uv-tool 0.5.5 (95cd8b8b3 2024-11-27)

running pipx install yewtube yields a 'yt' script that lets you search for videos to play, but when you search with the uv tool install version, you get:

Error fetching data. Possible network issue.
post() got an unexpected keyword argument 'proxies'

Running with --debug yields the traceback:
-----------------------------------------------------------------------
~ » yt --debug                                        cpatti@rocinante
yewtube version    : 2.12.0
yt_dlp version     : 2024.11.18
Python version     : 3.12.7 (main, Oct  1 2024, 02:05:46) [Clang 15.0.0 (clang-15<IP_ADDRESS>)]
Processor          : arm
Machine type       : arm64
Architecture       : 64bit,
Platform           : macOS-14.6.1-arm64-arm-64bit
sys.stdout.enc     : utf-8
default enc        : utf-8
Config dir         : /Users/cpatti/.config/mps-youtube
dbus               : None
glib               : False
env:TERM           : screen-256color
env:SHELL          : /bin/zsh
env:LANG           : en_US.UTF-8
could not load MPRIS interface. missing libraries.
--

Enter /search-term to search or [h]elp
> /VISION
Traceback (most recent call last):
  File "/Users/cpatti/.local/share/uv/tools/yewtube/lib/python3.12/site-packages/mps_youtube/main.py", line 73, in matchfunction
    func(*matches)
  File "/Users/cpatti/.local/share/uv/tools/yewtube/lib/python3.12/site-packages/mps_youtube/commands/search.py", line 310, in search
    wdata = pafy.search_videos(term, int(config.PAGES.get))
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/cpatti/.local/share/uv/tools/yewtube/lib/python3.12/site-packages/mps_youtube/pafy.py", line 73, in search_videos
    videosSearch = VideosSearch(query, limit=50)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/cpatti/.local/share/uv/tools/yewtube/lib/python3.12/site-packages/youtubesearchpython/search.py", line 148, in __init__
    self.sync_create()
  File "/Users/cpatti/.local/share/uv/tools/yewtube/lib/python3.12/site-packages/youtubesearchpython/core/search.py", line 29, in sync_create
    self._makeRequest()
  File "/Users/cpatti/.local/share/uv/tools/yewtube/lib/python3.12/site-packages/youtubesearchpython/core/search.py", line 51, in _makeRequest
    request = self.syncPostRequest()
              ^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/cpatti/.local/share/uv/tools/yewtube/lib/python3.12/site-packages/youtubesearchpython/core/requests.py", line 20, in syncPostRequest
    return httpx.post(
           ^^^^^^^^^^^
TypeError: post() got an unexpected keyword argument 'proxies'
--

Traceback (most recent call last):
  File "/Users/cpatti/.local/share/uv/tools/yewtube/lib/python3.12/site-packages/mps_youtube/main.py", line 73, in matchfunction
    func(*matches)
  File "/Users/cpatti/.local/share/uv/tools/yewtube/lib/python3.12/site-packages/mps_youtube/commands/search.py", line 310, in search
    wdata = pafy.search_videos(term, int(config.PAGES.get))
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/cpatti/.local/share/uv/tools/yewtube/lib/python3.12/site-packages/mps_youtube/pafy.py", line 73, in search_videos
    videosSearch = VideosSearch(query, limit=50)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/cpatti/.local/share/uv/tools/yewtube/lib/python3.12/site-packages/youtubesearchpython/search.py", line 148, in __init__
    self.sync_create()
  File "/Users/cpatti/.local/share/uv/tools/yewtube/lib/python3.12/site-packages/youtubesearchpython/core/search.py", line 29, in sync_create
    self._makeRequest()
  File "/Users/cpatti/.local/share/uv/tools/yewtube/lib/python3.12/site-packages/youtubesearchpython/core/search.py", line 51, in _makeRequest
    request = self.syncPostRequest()
              ^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/cpatti/.local/share/uv/tools/yewtube/lib/python3.12/site-packages/youtubesearchpython/core/requests.py", line 20, in syncPostRequest
    return httpx.post(
           ^^^^^^^^^^^
TypeError: post() got an unexpected keyword argument 'proxies'

Error fetching data. Possible network issue.
post() got an unexpected keyword argument 'proxies'
>

Thank you for such an amazing project!

Based on what I'm seeing, I think the issue is with httpx==0.28.x which was released on Nov 28th. See announcement which states The deprecated proxies argument has now been removed. . Its likely the case that your pipx install is still using an older version of httpx 😅

This generally would require a fix in yewtube, but in the mean time you can resolve your issue by using uv tool install --with httpx==0.27.2 yewtube

Thanks so much for the quick and helpful response!
You're right. I'll use the work-around for now and make a PR on their end.

One more detail JIC anyone else sees this issue. yewtube also uses pip as a standalone tool, so in order to get this to a working state I had to run:
uv tool install --with httpx==0.27.2,pip yewtube


merge image cropped, zoomed and blur

Hi
I just wanted to replace the green screen with image attached, but the output is quite blur and image is cropping and zoomed.
Please help me to resolve on same

Can you send me the code and the output image to reproduce?

`
from PIL import Image
from pathlib import Path
import numpy as np
from chromakey import chroma_key
Image from
https://sotamedialab.wordpress.com/2017/02/14/common-green-screen-photography-mistakes/
image_path = Path(file).parent / "uneven_green_green_lighting.png"
image = Image.open(str(image_path))
#background_image = Image.new("RGB", image.size, "red")
background_image_path = Path(file).parent / "MAWP-C-1302_1.jpg"
background_image = Image.open(str(background_image_path))
image = np.asarray(image)
background_image = np.asarray(background_image)
masked_image, _ = chroma_key(
image, keycolor="#6dff8b", background_image=background_image, tola=25, tolb=50
)
Image.fromarray(masked_image).show()`

Ah yes. If you look into the code, the background image is resized to the same size as the original image. Background image is then summed with the mask.
If you don't want it to be zoomed in. You have to somehow project your image onto the mask.

Can you suggest, where I need to do this changes?
I think this changes will go in core.py?

I imagine it would be a separate new function. It is quite specific to your use case. You have to change the way you sum your background image and the mask array. Check:
https://github.com/eugeneteoh/chromakey/blob/main/chromakey/core.py#L40

I have one more more query.
Is it possible to start masking where the green-screen start instead of taking full width.
It prevents my background image from cropping


OnlineCheckerImpl does not check for internet connectivity

The OnlineCheckerImpl only checks if there is a network connection available (packets can be sent) but not whether it is connected to the greater internet.
As described in this stackoverflow:
http://stackoverflow.com/questions/6493517/detect-if-android-device-has-internet-connection
A decent way to do this would be checking if a host is reachable with a small timeout at a regular interval:
http://stackoverflow.com/questions/8919083/checking-host-reachability-availability-in-android

Probably, you're right. In previous versions of the library I was performing actual ping, but it seemed to be not so reliable. Moreover, I wasn't sure which solution is the best and actually correct. Nevertheless if people encountering problems with that or false-positive information, it would be good to update it. I think, we can combine existing solution (checking available network connection and if we can send packets) with actual ping. I think this solution looks good: http://stackoverflow.com/a/25816086/1150795. What do you think? We can also make this url configurable, but when given host will be unavailable, final result will be wrong.

I'm doing actual pings in my app. I wrote this answer:
http://stackoverflow.com/a/35647892/1820510
The only difference is that instead of sending a full TCP request, I just check establish the TCP connection and then close the socket right after so its a bit faster to execute.

It seems to be reasonable. I'll check it out and probably enhance existing solution. Optionally, if you want to contribute to this project, good PRs are welcome. :)

I'm wondering if opening a TCP connection requires running such operation in a separate thread asynchronously like regular HTTP request. I guess it may be necessary.

Yup you need to do it in a background thread, android will actually throw an exception if you do networking on the main thread. I'm using a scheduler like this:
https://github.com/lingz/NetworkMonitor/blob/master/android/app/src/main/java/com/networkmonitor/NetworkMonitoringService.java#L150

It's fixed. Now, we're pinging remote host. Update will be available in the next release.


Mechanism for getting the version of DC/OS

Please answer the following questions before submitting your issue. Thanks!
What version of the DCOS CLI are you using (dcos --version)?
SNAPSHOT
What version of DCOS are you using?
1.6.1
What operating system and version are you using?
Fedora 22
What did you do?
If possible please provide a recipe for reproducing.
I am trying to get the version of DC/OS
What did you expect to see?
dcos --version should display the CLI version and the DC/OS version. I don't know if this is the right solution but the user should be able to get the version of DC/OS. This helps to debug issues.
What did you see instead?
dcos --version only shows the version of the CLI

We could output {DCOS_VERSION: 1-7.dev, DCOS_CLI_VERSION: 0.4.2}.
We can get the dcos_version from dcos-metadata/dcos-version.json

Sounds good to me.


Add enum module support

Checklist

[x] Confirmed that run-checks all script has been executed.

Related Issues/PRs
Issue #726
#[derive(Module, Debug)]
enum ModuleEnum<B: Backend> {
    Basic(ModuleBasic<B>),
    Composed(ModuleComposed<B>),
}

Changes
Added support for #[derive(Module)] with enums.

Added enum record derive support
Added enum module derive support

Testing
Added enum module definitions in derive module tests and transposed some existing unit tests for enum modules.

Should we add something in the book to state that we support enum modules?


Added new game (Snake game)

PR Description 📜
Please include summary related to the issue you have fixed and describe your PR in brief over here by specifying the issue number on which you were working below
Fixes # 5130

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in GameZone's README.md
[x] I have added README.md in my Game folder

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @rugved0102 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Hey @rugved0102, You have reached your limit to contribute in GameZone with a score of 180.
We believe in giving equal opportunity to everyone so you will not be able to contribute to GameZone now onwards. 💗
Thank you for your valuable time and contribution in GameZone 🕹!
Your merged pull requests:

#5129 with labels: level3 score: (45)
#5125 with labels: level3 score: (45)
#5109 with labels: level3 score: (45)
#5053 with labels: level3 score: (45)

Thank you  @rugved0102 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Test change

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/12510/
Test FAILed.


Drop pyproj.Proj

It is currently around for backwards compatibility with pyproj 1.x. However, no new features will be likely be added.
This is superseded by use of CRS and Transformer classes:
cc = CRS(...)
transformer = Transformer.from_crs(cc.geodetic_crs, cc)
transformer.transform(...)

It is also requires conversion to a PROJ string, which may or may not be reliable:
https://github.com/pyproj4/pyproj/blob/ae074ee4be00e245e23d1e26d0a06c0205af1dae/pyproj/proj.py#L161-L168
The plan would be to deprecate its usage in a 2.x release with deprecation/future warning.

Related #320


Fractal-Tree broken on mobile

The Fractal-Tree / Fractal-Canopy doesn't show nicely on mobile. Needs some calculations to figure out the maximum Root Length based on the current settings, to stay within the bounds of the screen.

Hey I didnt check out the code yet, but isnt that similar to what I have worked on?
I was wondering, if you would like me to outsource and refactor my work with proper interfaces so the scaling logic can be re-used. If so, what about you create another issue for the outsourcing and assign it to me, ill take care of it.
Afterwards we can go through the fractals one by one to refactor to reuse that logic.
What do you think?

Sry I didn't see that. Not the most on top of things sometimes, should really enable notifications for this repo haha :sweat_smile:
I like the idea, the outsourcing is already done, so now it's just a question of using that same logic to close this issue right?
There is one problem I see you could run into with this approach, namely the different fractals will have different algorithms and hence you might need to figure out how to adapt the Barnsley Fern approach to new types of fractals that don't have a mapping to the idea of "furthest point left,right,up,down".
Especially L-Systems could be a bit of a problem since they are just long strings executed as draw instructions one by one and the scaling happens in between iterations with some magic numbers.
Let me know how it goes/if you need help :+1:

Well I guess we need to find different ways to determine the sizes depending on the fractals. I could not really abstract for the canopy :c
But once there are multiple following certain scaling logics, it would make sense to refactor. Like determine scaling directing depending on a growth function or something.
// I will just hit you with the @trebeljahr this time haha check out the PR at your leisure :)


Titaniam second blog - BYOK for B2B SaaS Operators #647

Description
This PR posts Titaniam's second blog - BYOK for B2B SaaS Operators #647
Issues Resolved
#647
Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

Hey @pakshi - the PR is failing the DCO check. Can you fix that? This is a good guide on how to fix it.

@brijos you want to review this blog post?

I've reached out to @pakshi for a meeting to have a conversation.

@brijos I added an introduction as we discussed. Can you please check?
@stockholmux there is a good chance I did not get the signed-off right. I will ask my developer to check again.

Creating a new PR


Korepi's assembly issue + Discord Link

Greeting
I just wanted to start my korepi today (I've used it before) but it took cmd user assembly so long to initialize.
Also the discord link is not working.
++ There is no release? the files has been removed?

Hello, access to the discord server is closed and, most likely, it will not be open in the near future,
Releases have been deleted, it seems that only those that require presence on the discord server remain

Is there any chance or way to get access to discord?
I've been Akebi, Kebabi, Korepi user and I didn't expect that such things happen whoch only needed discord. I'd be happy if the devs need to interview me or sth just to get access.

I can't know this, I'm just a translator, and I don't have access to this information.
Perhaps one of the developers will answer you about this, but the chances are slim

go to the keyauth repo then click releases there is the releases for korepi.

https://github.com/Korepi/keyauth-cpp-library

I really hope so, also If you have access to the discord, maybe alerting DEVs so they take a look a this? :(

Is it no longer usable ?

I'm sorry, but this issue is not resolved :) discord members are increasing and yet ppl from here are the only one not being able
to join/ use?

discord will be opened when korepi 4.0 released


MemoryError:

When I follow these steps to set up dopamine,everything seems ok until testing the "dopamine/atari/train.py.".The problem is:
MemoryError:    In call to configurable 'WrappedReplayBuffer' (<unbound method WrappedReplayBuffer.__init__>)   In call to configurable 'DQNAgent' (<unbound method DQNAgent.__init__>)   In call to configurable 'Runner' (<unbound method Runner.__init__>)

Hi! Were you able to solve this? I am getting the exact same error.

could you please specify the command line you used to run this?

I use the common line as follow to test "dopamine/atari/train.py.",and get this error.
``(dopamine-env) cx@cx-PC:~/dopamine$ python -um dopamine.atari.train
--agent_name=dqn
--base_dir=/tmp/dopamine
--gin_files='dopamine/agents/dqn/configs/dqn.gin'
I0905 10:25:25.734432<PHONE_NUMBER>18336 tf_logging.py:115] Creating DQNAgent agent with the following parameters:
I0905 10:25:25.735104<PHONE_NUMBER>18336 tf_logging.py:115] 	 gamma: 0.990000
I0905 10:25:25.735372<PHONE_NUMBER>18336 tf_logging.py:115] 	 update_horizon: 1.000000
I0905 10:25:25.735630<PHONE_NUMBER>18336 tf_logging.py:115] 	 min_replay_history: 20000
I0905 10:25:25.735881<PHONE_NUMBER>18336 tf_logging.py:115] 	 update_period: 4
I0905 10:25:25.736156<PHONE_NUMBER>18336 tf_logging.py:115] 	 target_update_period: 8000
I0905 10:25:25.736394<PHONE_NUMBER>18336 tf_logging.py:115] 	 epsilon_train: 0.010000
I0905 10:25:25.736629<PHONE_NUMBER>18336 tf_logging.py:115] 	 epsilon_eval: 0.001000
I0905 10:25:25.736864<PHONE_NUMBER>18336 tf_logging.py:115] 	 epsilon_decay_period: 250000
I0905 10:25:25.737092<PHONE_NUMBER>18336 tf_logging.py:115] 	 tf_device: /gpu:0
I0905 10:25:25.737313<PHONE_NUMBER>18336 tf_logging.py:115] 	 use_staging: True
I0905 10:25:25.737536<PHONE_NUMBER>18336 tf_logging.py:115] 	 optimizer: <tensorflow.python.training.rmsprop.RMSPropOptimizer object at 0x7f9ae3be8f10>
I0905 10:25:25.768975<PHONE_NUMBER>18336 tf_logging.py:115] Creating a OutOfGraphReplayBuffer replay memory with the following parameters:
I0905 10:25:25.769330<PHONE_NUMBER>18336 tf_logging.py:115] 	 observation_shape: 84
I0905 10:25:25.769594<PHONE_NUMBER>18336 tf_logging.py:115] 	 stack_size: 4
I0905 10:25:25.769826<PHONE_NUMBER>18336 tf_logging.py:115] 	 replay_capacity: 1000000
I0905 10:25:25.769923<PHONE_NUMBER>18336 tf_logging.py:115] 	 batch_size: 32
I0905 10:25:25.770018<PHONE_NUMBER>18336 tf_logging.py:115] 	 update_horizon: 1
I0905 10:25:25.770113<PHONE_NUMBER>18336 tf_logging.py:115] 	 gamma: 0.990000
Traceback (most recent call last):
File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
"main", fname, loader, pkg_name)
File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "/home/cx/dopamine/dopamine/atari/train.py", line 134, in
app.run(main)
File "/home/cx/dopamine-env/local/lib/python2.7/site-packages/absl/app.py", line 300, in run
_run_main(main, args)
File "/home/cx/dopamine-env/local/lib/python2.7/site-packages/absl/app.py", line 251, in _run_main
sys.exit(main(argv))
File "/home/cx/dopamine/dopamine/atari/train.py", line 128, in main
launch_experiment(create_runner, create_agent)
File "/home/cx/dopamine/dopamine/atari/train.py", line 117, in launch_experiment
runner = create_runner_fn(FLAGS.base_dir, create_agent_fn)
File "/home/cx/dopamine/dopamine/atari/train.py", line 99, in create_runner
return run_experiment.Runner(base_dir, create_agent_fn)
File "/home/cx/dopamine-env/local/lib/python2.7/site-packages/gin/config.py", line 1032, in wrapper
utils.augment_exception_message_and_reraise(e, err_str)
File "/home/cx/dopamine-env/local/lib/python2.7/site-packages/gin/utils.py", line 50, in augment_exception_message_and_reraise
six.reraise(proxy, None, sys.exc_info()[2])
File "/home/cx/dopamine-env/local/lib/python2.7/site-packages/gin/config.py", line 1009, in wrapper
return fn(*new_args, **new_kwargs)
File "dopamine/atari/run_experiment.py", line 163, in init
self._agent = create_agent_fn(self._sess, self._environment)
File "/home/cx/dopamine/dopamine/atari/train.py", line 71, in create_agent
return dqn_agent.DQNAgent(sess, num_actions=environment.action_space.n)
File "/home/cx/dopamine-env/local/lib/python2.7/site-packages/gin/config.py", line 1032, in wrapper
utils.augment_exception_message_and_reraise(e, err_str)
File "/home/cx/dopamine-env/local/lib/python2.7/site-packages/gin/utils.py", line 50, in augment_exception_message_and_reraise
six.reraise(proxy, None, sys.exc_info()[2])
File "/home/cx/dopamine-env/local/lib/python2.7/site-packages/gin/config.py", line 1009, in wrapper
return fn(*new_args, **new_kwargs)
File "dopamine/agents/dqn/dqn_agent.py", line 151, in init
self._replay = self._build_replay_buffer(use_staging)
File "dopamine/agents/dqn/dqn_agent.py", line 235, in _build_replay_buffer
gamma=self.gamma)
File "/home/cx/dopamine-env/local/lib/python2.7/site-packages/gin/config.py", line 1032, in wrapper
utils.augment_exception_message_and_reraise(e, err_str)
File "/home/cx/dopamine-env/local/lib/python2.7/site-packages/gin/utils.py", line 50, in augment_exception_message_and_reraise
six.reraise(proxy, None, sys.exc_info()[2])
File "/home/cx/dopamine-env/local/lib/python2.7/site-packages/gin/config.py", line 1009, in wrapper
return fn(*new_args, **new_kwargs)
File "dopamine/replay_memory/circular_replay_buffer.py", line 706, in init
extra_storage_types=extra_storage_types)
File "dopamine/replay_memory/circular_replay_buffer.py", line 157, in init
self._create_storage()
File "dopamine/replay_memory/circular_replay_buffer.py", line 173, in _create_storage
array_shape, dtype=storage_element.type)
MemoryError:
In call to configurable 'WrappedReplayBuffer' ()
In call to configurable 'DQNAgent' ()
In call to configurable 'Runner' ()

What system are you trying to run dopamine on?  Looks like you may not have enough memory in your box.

I tried it on a system with 8GB RAM and running Ubuntu 16.04
If that's insufficient, could you please add a minimum requirements in the Readme?

we have not tested dopamine to figure out how low you can go, but it may be that the default replay memory size is too big. can you try the following command and see if it works:
python -um dopamine.atari.train \
  --agent_name=dqn
  --base_dir=/tmp/dopamine
  --gin_files='dopamine/agents/dqn/configs/dqn.gin' \
  --gin_bindings=WrappedReplayBuffer.replay_capacity=1000

and see if it works? this is running with a very small replay buffer, so the it will not perform as well, but should indicate whether it's just a low ram issue you're seeing.

Cool, nice spot.
On Thu, Sep 6, 2018, 11:49 AM Pablo Samuel Castro<EMAIL_ADDRESS>wrote:

we have not tested dopamine to figure out how low you can go, but it may
be that the default replay memory size is too big. can you try the
following command and see if it works:
python -um dopamine.atari.train
--agent_name=dqn
--base_dir=/tmp/dopamine
--gin_files='dopamine/agents/dqn/configs/dqn.gin'
--gin_bindings=WrappedReplayBuffer.replay_capacity=1000
and see if it works? this is running with a very small replay buffer, so
the it will not perform as well, but should indicate whether it's just a
low ram issue you're seeing.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/dopamine/issues/13#issuecomment-419202024, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AbaF5AW6Ae_rVfN_w1MHQobrzBviY-93ks5uYW4rgaJpZM4WWehU
.

It does worked.Thank you very much!


[SPARK-8484] [ML]. Added TrainValidationSplit for hyper-parameter tuning.

[X] Added TrainValidationSplit for hyper-parameter tuning. It randomly splits the input dataset into train and validation and use evaluation metric on the validation set to select the best model. It should be similar to CrossValidator, but simpler and less expensive.
[X] Simplified replacement of https://github.com/apache/spark/pull/6996

Merged build triggered.

Merged build started.

Test build #36991 has started for   PR 7337 at commit d699506.

Test build #36991 has finished for   PR 7337 at commit d699506.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class TrainValidatorSplit(override val uid: String) extends Estimator[TrainValidatorSplitModel]

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36993 has started for   PR 7337 at commit 00c4f5a.

Test build #36993 has finished for   PR 7337 at commit 00c4f5a.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class TrainValidatorSplit(override val uid: String) extends Estimator[TrainValidatorSplitModel]

Merged build finished. Test PASSed.

Done for now. This is in very good shape.

Actually, is there much difference between this and CrossValidator other than being able to specify trainRatio? There seems to be a lot of code duplication between the two.

@feynmanliang yes there is a lot of duplicated code. I attempted to refactor that slightly under https://github.com/apache/spark/pull/6996.
It is an interesting idea to just call CrossValidator instead of implementing the logic. I will have a look into that. But I assume we still need the Params and Model specific for TrainValidationSplit? We also need to decide if we want to do that as part of this review or separately.
cc @mengxr

Both CrossValidator and TrainValidationSplit use sampling to split the data to training and validation.
Currently CrossValidator does

numFolds = 1 - not valid
numFolds = 2 - 0.0 to 0.5 training, 0.5 to 1 validation and 0.0 to 0.5 validation and 0.5 to 1 training

TrainValidationSplit does

0.0 to trainRatio training, trainRatio to 1 validation

Therefore the logic is different and using TrainValidationSplit is not the same as just calling CrossValidator. Please let me know if the logic implemented by TrainValidationSplit is what was expected. We can then potentially address the code duplication.

CrossValidator currently doesn't take numFolds = 1 because it uses MLUtils#kfolds which does splits using trainRatio = 1 - 1/numFolds, which in this case would mean nothing goes into the training set.
If we give a trainRatio param to CrossValidator and modify MLUtils#kfold accordingly, then each fold could be split using your set trainRatio so setting numFolds = 1, trainRatio = x would achieve the same functionality as TrainValidationSplit with trainRatio = x.
Note that in this case we would have to change the default trainRatio = 1 - 1/numFolds behavior for the special case numFolds = 1 to avoid the error case described in my first paragraph.

Sorry, didn't address your questions.

I'm proposing to add a trainRatio param to CrossValidatorParams, eliminating the need for the TrainValidatorSplit Params and Model
The logic in TrainValidationSplit looks fine to me and is what I expected

Thanks @feynmanliang. As I mentioned I tried to address the code duplication in my previous PR differently than you propose, but we decided to go with the simplest option for now.
I agree what you are proposing makes sense. The only thing that worries me would be unclear purpose of trainRatio when numFolds != 1. In that case CrossValidator splits the dataset to numFolds subsets of the same size and the ratio of training and validation sets is given (e.g. with numFolds set to 4 the training set is 0.75 and validation is 0.25) and therefore the trainRatio param would not be used?
We could do that, document that approach and essentially get rid of TrainValidatorSplit or the other option would be to preserve TrainValidatorSplit as a wrapper around the functionality to avoid confusion of CrossValidator having the trainRatio param.

Ah, I overlooked your point about when 1 - trainRatio > 1/numFolds we will have overlapping folds. Also, I realized that what I'm proposing (adding a trainRatio for each fold) contradicts what Wikipedia defines for k-fold validation. Thanks for pushing back on this.
I agree with you that TrainValidatorSplit and CrossValidator have two different functionality and should be separate classes. I like the idea of both wrapping a common (perhaps more confusing) implementation with both numFolds and trainRatio; it differentiates the concepts in the public API but shares code in the implementation.

Merged build triggered.

Merged build started.

Test build #37057 has started for   PR 7337 at commit f4fc9c4.

Test build #37057 has finished for   PR 7337 at commit f4fc9c4.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class TrainValidatorSplit(override val uid: String) extends Estimator[TrainValidatorSplitModel]

Merged build finished. Test PASSed.

Merged build triggered.

I think we need a decision how to approach this. I would prefer to focus on the public api and avoid the refactor in this review and then address that in another review as discussed in https://github.com/apache/spark/pull/6996.

@feynmanliang @zapletal-martin The changes in this PR look good to me except a few minor comments. As discussed in #6996, let's focus on the public API to get this merged first.
We can have another PR for code reuse. There would be more discussion, e.g., having a base class handling arbitrary slicing of the input data and making CrossValidator and TrainValidationSplit extend it. I actually think there will be more lines of code if we implement it that way. It might not be worth the trade-off.

Merged build triggered.

Merged build started.

Test build #38015 has started for   PR 7337 at commit cafc949.

Test build #38015 has finished for   PR 7337 at commit cafc949.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class TrainValidationSplit(override val uid: String) extends Estimator[TrainValidationSplitModel]

Merged build finished. Test PASSed.

LGTM. Merged into master. Please create JIRAs for follow-up work, e.g, Python API, user guide, and refactoring (if it is useful). Thanks!


Add QV plotter for plotting heavy output probability vs ntrials

Summary
Add QV plotter for plotting heavy output probability vs ntrials similar to Figure 2a of QV64 paper.
Details and comments
Fixes: #213 and #483:

add plot_hop_accumulative method fro plotting heavy output probability vs ntrials
plots individual HOP and accumulative HOP
plots 2-sigma shaded area
plots 2/3 success threshold

Example:
qv_fitter.plot_hop_accumulative(depth=5)

The lint test error is due to label='2$\sigma$'. This is only a warning why does it fail the test?
qiskit/ignis/verification/quantum_volume/fitters.py:355:68: W605 invalid escape sequence '\s'
ERROR: InvocationError for command /home/runner/work/qiskit-ignis/qiskit-ignis/.tox/lint/bin/pycodestyle qiskit/ignis test/ (exited with code 1)

Suggest reviewer: @dcmckayibm

@ShellyGarion Can you also shed some lights on how to fix the tests errors in this PR? The python tests, doc test and tutorials test give this error message No module named 'qiskit.circuit.library.template_circuits' which seems to be a Terra problem. I am not sure why this is happening.
lint error is because '\s' in '\sigma' gives a warning but it shouldn't fail the test. Is there anyway to work around to allow '\s'?

@ShellyGarion Can you also shed some lights on how to fix the tests errors in this PR? The python tests, doc test and tutorials test give this error message No module named 'qiskit.circuit.library.template_circuits' which seems to be a Terra problem. I am not sure why this is happening.
lint error is because '\s' in '\sigma' gives a warning but it shouldn't fail the test. Is there anyway to work around to allow '\s'?

For the lint error you either need to escape the \ as \\s or change the string to be a raw string with r"\s" to tell python to not treat \s as an escape sequence. Either approach is valid, but without that in certain contexts python will try to use that as an escape sequence which is invalid and why the linter fails.

@ShellyGarion Can you also shed some lights on how to fix the tests errors in this PR? The python tests, doc test and tutorials test give this error message No module named 'qiskit.circuit.library.template_circuits' which seems to be a Terra problem. I am not sure why this is happening.
lint error is because '\s' in '\sigma' gives a warning but it shouldn't fail the test. Is there anyway to work around to allow '\s'?

I changed '\s'. The lint error is now fixed. All tests are passed. Thank you! Release note is also added. Can you please review?

Thanks for the approval! @dcmckayibm and @ShellyGarion


[Proposal] Update the flogo build command

I'm submitting a ...  (check one with "x")
[] bug report => search github for a similar issue or PR before submitting
[X] feature request
[] support request
[] general question

Over time the flogo build command has grown from a simple build, to be able to handle tons of options. As we want to support more targets and options, now is a good time to think about the structure of what flogo build should look like.
Proposal
$ flogo build [-e] [-gen | -nogen] [-target] [-trigger]

Flags

Flag
Usage

e
Embed the application configuration (flogo.json) into the executable

gen
Generate the metadata only (does not perform build)

nogen
Perform build only (does not generate metadata)

target
The target platform to build for

trigger
The trigger to start the app with (only used in combination with the target flag)

Targets
The new target flag would get the following options

docker
lambda
sam
shim

docker
This will trigger the build of an executable, a Dockerfile, and a docker image (based on Alpine Linux). By default it will expose ports for each trigger that exists. If you only want to expose the port for a single trigger you can use the -trigger flag, which would specify the id of the trigger to use.
lambda
This will trigger the build and creation of an executable and zip file that can be uploaded and deployed to AWS Lambda. By default it will create an executable for each Lambda trigger that exists. If you want to build for a specific trigger you can use the -trigger flag, which would specify the id of the trigger to use.
sam
This will trigger the build and creation of an executable and zip file (like with the lambda target) and also generate a SAM template. By default it will create an executable and a service entry in the SAM template for each Lambda trigger that exists. If you want to build for a specific trigger you can use the -trigger flag, which would specify the id of the trigger to use.
shim
A shim build, in which case the trigger flag must be set as well, is a "catch all" for all other targets. This will require the trigger to have a build.go file which will be triggered
What happens to the existing flags

Flag
Usage
Status

o
optimize for directly referenced contributions
will be removed, this flag wasn't used in the code anymore

e
embed application configuration into executable
stays

gen
ONLY perform the build, without performing the generation of metadata
stays

nogen
ONLY perform generation of metadata, without performing the build
stays

sp
skip prepare
will be removed, this flag was deprecated already

shim
trigger shim creates an app as shim, pass trigger id as value
will be removed, replaced with -target

docker
create a docker image based on Alpine Linux
will be removed, replaced with -target

What happens to the existing triggers

Trigger
Impact
New command

cli
Change (-target shim)
flogo build -e -target shim -trigger cli_trigger

coap
No change

kafkasub
No change

lambda
Change (-target lambda)
flogo build -e -target lambda or flogo build -e -target sam

mqtt
No change

rest
No change

timer
No change

Closing this proposal, this is now part of https://github.com/TIBCOSoftware/flogo/issues/327


Speed needs to use EVP_PKEY API to test RSA, DSA, and ECDSA

DH, ECDH, and SM2 are already using EVP_PKEY. RSA, DSA, and ECDSA are remaining to be converted.

Speed should be updated to use EVP for all crypto

Speed should be updated to use EVP for all crypto


Electron renderTo

I'm trying to render a torrent to a browser window in electron. I am running webtorrent in the main process and accessing it through a remote. When trying to render to my browserwindow with this code running in the render thread (the browserwindow)
var {remote} = require('electron');
var main = remote.require('./src/index.js');

var ipc = require('electron').ipcRenderer;
var file;

ipc.on('openFile' , function(event , magnet){
	console.log(magnet);
	var torrent = main.webtorrent.get(magnet);
	console.log(torrent);
	file = torrent.files[0];
	file.renderTo('#player')
});

Main thread code:
var WebTorrent = require('webtorrent');
var client = new WebTorrent();
...
exports.openviewer = (magnet) => {
  win_viewer = new BrowserWindow({width: 1280, height: 720});

  win_viewer.loadURL(url.format({
    pathname: path.join(__dirname, '/views/viewer.html'),
    protocol: 'file:',
    slashes: true
  }));

  win_viewer.webContents.on('dom-ready', () => {
    win_viewer.webContents.send('openFile' , magnet);
  });

  win_viewer.on('close', () => {
    win_viewer = null;
  });
  exports.win_viewer = win_viewer;
};

Error emitted in the render thread:
Uncaught Error: Could not call remote function ''. Check that the function signature is correct. Underlying error: browser-only method
Error: Could not call remote function ''. Check that the function signature is correct. Underlying error: browser-only method
    at callFunction (/usr/local/lib/node_modules/electron/dist/resources/electron.asar/browser/rpc-server.js:235:11)
    at EventEmitter.<anonymous> (/usr/local/lib/node_modules/electron/dist/resources/electron.asar/browser/rpc-server.js:342:5)
    at emitMany (events.js:127:13)
    at EventEmitter.emit (events.js:201:7)
    at WebContents.<anonymous> (/usr/local/lib/node_modules/electron/dist/resources/electron.asar/browser/api/web-contents.js:231:13)
    at emitTwo (events.js:106:13)
    at WebContents.emit (events.js:191:7)

I doubt that Electron's remote package will work correctly in this case. A better way (and what we do in WebTorrent Desktop) is to use torrent.createServer().
If you call torrent.createServer() in your main process, then you can just add a <video> tag in the renderer that points to the local http server which will serve the video.
<!-- Plays the first file in the torrent -->
<video src="http://localhost:<port>/0" />


Border token color not linking to style

Closes https://github.com/tokens-studio/figma-plugin/issues/1792
https://github.com/tokens-studio/figma-plugin/assets/103296157/79ce6a2e-8acb-47df-a259-fd1417cefc6c

@esthercheran @six7
When applying a border token that is using reference mode, it is not connected to a style as expected; input mode however works as of now:
Example video

@esthercheran @six7 When applying a border token that is using reference mode, it is not connected to a style as expected; input mode however works as of now: Example video

yeah we'd want that to work too


types(withDefaults): fix unknown type inference error

close #11887

I think we shouldn't extend the NativeType with unknown, as this behavior is expected. See https://github.com/vuejs/core/issues/11887#issuecomment-2342533586

@jh-leong Agreed, thanks for the reminder.


Help document not found

I've followed the instructions to get this working and it's all fine except for the help link which results in
No route matches [GET] "/wmd/markdownhelp.html"

I'm not sure whether this is a bug or whether something's missing from the readme.

Wmd has a help page(https://github.com/chloerei/wmd/blob/master/markdownhelp.html) but I don't include it in this gem.
Your can download the html page, put it to public folder, or create a custom help page.
And also customize link url when init wmd:
new WMDEditor({
  ...
  helpLink: "/wmd/markdownhelp.html"
  ...
});

If want to remove this link:
new WMDEditor({
  ...
  buttons: "bold italic  link blockquote code image  ol ul heading hr  undo redo help" // remove 'help' string
  ...
});

Great, thanks for the clarification.


BF: Cast integer session identifiers to strings.

Before concatenating with subject identifiers.

This CI error is weird. The Black documentation suggests that it should be ignoring files that are in the .gitignore.

Also, this doc build error is a bit mysterious, but maybe we should just drop 3.6 support (and add 3.9?)

Yes, I'm +1 for dropping 3.6 support and adding 3.9.

I too am perplexed by the linting issue. I don't understand why it's not ignoring that file. And why it did ignore that file in CI tests for #90.