Slow evaluation of fairly simple expression

I have the following code segment for reading entries from a bcolz database which I am having problem porting to blaze and having it run at comparable speeds.
It basically reads all entries corresponding to locA, locB or locC from the database, provided the value does not correspond to a self-defined NaN-indicator (significand & exponent field with limit values). From the read data, a floating point value is calculated from the significand and exponent fields:
db = bcolz.open(rootdir='../mydata.bcolz', mode='r')
colNames  = db.cols.names

significand_limit = 2**(32-1)-1
exponent_limit = 2**(8-1)-1

# read only a subset of the columns of the database
db.cols.names = ['id', 'date', 'location', 'valueSignificand', 'valueExponent']

e = pd.DataFrame(db["((location == 'locA') | (location == 'locB') | (location == 'locC')) & " +
        "((valueSignificand != %d) & (valueExponent != %d))" % (-significand_limit-1, -exponent_limit-1)
        ])
e['value'] = e['valueSignificand'] * 10.0 ** e['valueExponent']
f = e[['id', 'date', 'location', 'value']]

db.cols.names = colNames     # restore original field names

This code segment run against my database completes in 8.3 sec.
I transformed this to the following using blaze:
db = bcolz.open(rootdir='../mydata.bcolz', mode='a')
d = blaze.Data(db)

significand_limit = 2**(32-1)-1
exponent_limit = 2**(8-1)-1

d = blaze.Symbol('d', 'var * {id: string, date: string, location: string, valueSignificand: int, valueExponent: int, validUntil: string}')

a = d[['id', 'date', 'location', 'valueSignificand', 'valueExponent']]
b = a[
    (a.valueSignificand != -significand_limit-1) &
    (a.valueExponent != -exponent_limit-1) &
    ((a.location == 'locA') |
     (a.location == 'locB') |
     (a.location == 'locC'))
    ]
c = (b.valueSignificand * 10.0 ** b.valueExponent).label('value')
e = blaze.merge(b[['id', 'date', 'location']], value=c)

f = blaze.compute(e)

This evaluates in 14.9 sec. (1.8 times slower) This is does not shock me since blaze reads the unnecessary columns from the database before dropping them again. The decompression will of course take more time.
But I thought I would gain this again by using a parallel mapping with:
from multiprocessing import Pool
p = Pool()
f = blaze.compute(e, map=p.map)

Surprisingly, this is even slower, taking 29.3 sec!
I looked at the splitting of the expression but cannot find any obvious problem:
blaze.split(d, e)

((chunk,
  Merge(_child=chunk[((chunk.valueSignificand != -2147483648) &
                      (chunk.valueExponent != -128)) &
                     (((chunk.location == 'locA') |
                       (chunk.location == 'locB')) |
                      (chunk.location == 'locC'))],
        children=(chunk[((chunk.valueSignificand != -2147483648) &
                         (chunk.valueExponent != -128)) &
                        (((chunk.location == 'locA') |
                          (chunk.location == 'locB')) |
                         (chunk.location == 'locC'))][['id', 'date', 'location']],
                  label((chunk[((chunk.valueSignificand != -2147483648) &
                                (chunk.valueExponent != -128)) &
                               (((chunk.location == 'locA') |
                                 (chunk.location == 'locB')) |
                                (chunk.location == 'locC'))].valueSignificand)
                        * (10.0
                           ** (chunk[((chunk.valueSignificand != -2147483648) &
                                      (chunk.valueExponent != -128)) &
                                     (((chunk.location == 'locA') |
                                       (chunk.location == 'locB')) |
                                      (chunk.location == 'locC'))].valueExponent)),
                        'value')
                  )
        )
  ),
 (aggregate, aggregate))

@ARF1 Thanks for providing a nice example!
There are a couple of things going on here.

If the string columns in your bcolz store are object dtype, then you lose quite a bit of performance no matter what. The performance increase you get from converting variable length string columns (e.g., object dtypes) to fixed length string columns is worth the time it takes to do the conversion. The odo library can help with this. For example,

ds = '1234567890 * {id: int64, name: string}'  # string is not performant
ds2 = '1234567890 * {id: int64, name: string[10, 'A']}'  # compute the length of the longest string and put that where 10 is in this example, 'A' means ASCII, which takes up a little bit less space

odo('mydata.bcolz', 'mynewdata.bcolz', expectedlen=len(resource('mydata.bcolz')), dshape=ds2)

bcolz uses numexpr to perform queries like this db['a > b']. It evaluates the predicate with numexpr and when doing the selection it skips reading chunks for which all the values of the predicate are False and thus can save a ton of IO cost when there are a lot of False values in the condition.

Unfortunately, Blaze does not take advantage of this feature of bcolz. Instead it reads the entire chunk of data in no matter what, then does the selection with numpy and concatenates the result back together. We haven't experimented with attempting to take advantage of all that bcolz has to offer here. It might be possible to leverage their expression evaluation.

I'm not completely sure why chunking with a process pool was slower than no process pool. It's possible that the size of the data + cost of the computation are not enough to dwarf the cost of inter-process commuication.


Dracula Dark Theme for Firefox

dracula-firefox repository
A dracula dark theme for firefox

Do you happen to know the differences between yours and this other theme? Guessing these themes will also be slightly better than whatever we can accomplish with Firefox Color, right?

Do you happen to know the differences between yours and this other theme? Guessing these themes will also be slightly better than whatever we can accomplish with Firefox Color, right?

I've looked it up and the theme you mentioned seem to have been made using Firefox Color, so the theme is not applied to the the home page, the popups and buttons properly and the color scheme used there is different as well, whereas mine is fully themed and written using JSON and the Manifest.json documentation.
The theme you mentioned:

Mine:


add ui to demo

Proposed changes
Add ui to the demo to provide complete end-to-end environment
Types of changes
What types of changes does your code introduce to the project: Put
an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)

Checklist
Put an x in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to
ask. We're here to help! This is simply a reminder of what we are going
to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have signed the Contributor License Agreement
[x] I have updated the RELEASE NOTES
[ ] I have added tests that prove my fix is effective or that my
feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in
downstream modules

Further comments
N/A

@Cerfoglg have a look :)


Make content_range an optional field

This is just #268 with merge conflicts fixed. cc @jefshe

thanks for sorting out the conflicts 👍

Merged in original #268 instead.


Run dev-debug is not working

Version
v2.5.0
Reproduction link
https://github.com/baturali/nuxt-dev-debug
Steps to reproduce
Clone the project and run>
yarn
yarn run dev-debug
What is expected ?
The debugging process should work as expected.
What is actually happening?
I receive the error below:
$ yarn run dev-debug
yarn run v1.13.0
$ node --inspect node_modules/.bin/nuxt
Debugger listening on ws://<IP_ADDRESS>:9229/1a9f338a-2040-4011-84c5-88f7b37e522e
For help, see: https://nodejs.org/en/docs/inspector
C:\Users\user\Desktop\Dev\debug-try\node_modules.bin\nuxt:2
basedir=$(dirname "$(echo "$0" | sed -e 's,\,/,g')")
^^^^^^^
SyntaxError: missing ) after argument list
at Module._compile (internal/modules/cjs/loader.js:743:23)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:810:10)
at Module.load (internal/modules/cjs/loader.js:666:32)
at tryModuleLoad (internal/modules/cjs/loader.js:606:12)
at Function.Module._load (internal/modules/cjs/loader.js:598:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:862:12)
at internal/main/run_main_module.js:21:11
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Additional comments?
Any idea why this happens?

This bug report is available on Nuxt community (#c8880)

Unable to reproduce it on macOS

Unable to reproduce it on macOS

Its just starter template of Nuxt.js me only added the dev-debug script on package.json.
So you can try to build a new project with following these steps: https://nuxtjs.org/guide/installation and
add that line on package.json file in scripts > "dev-debug": "node --inspect node_modules/.bin/nuxt"

I have the same problem on Windows 10.

Dev-debug works fine on Mac with v2.5.0 but still not on Windows.

Actually, on Windows, the nuxt executable was ./node_modules/.bin/nuxt.cmd.
On MacOS it's ./node_modules/.bin/nuxt.
If you take a look the content of these two files, despite lines and syntax which is platform specific, then you'll find out it's executing ./node_modules/nuxt/bin/nuxt.js.
So, just simply change your dev-debug script to node --inspect ./node_modules/nuxt/bin/nuxt then you have no problem debugging your code on both platforms.

I have the same problem on Windows 10.

@Manieck https://github.com/nuxt/nuxt.js/issues/5308#issuecomment-482698759


fix: always send Trojan header

fix #2250
In some protocol, such as SMTP , the client will watiing the command send from server after TCP handshaked, so Trojan header should be send even if payload is empty.

Codecov Report
Patch coverage: 42.85% and project coverage change: -0.04 :warning:

Comparison is base (62bef88) 39.05% compared to head (02fd1fa) 39.02%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2511      +/-   ##
==========================================
- Coverage   39.05%   39.02%   -0.04%
==========================================
  Files         617      617
  Lines       37036    37043       +7
==========================================
- Hits        14466    14456      -10
- Misses      20978    20991      +13
- Partials     1592     1596       +4

Impacted Files
Coverage Δ

proxy/trojan/client.go
0.98% <0.00%> (-0.05%)
:arrow_down:

proxy/trojan/protocol.go
46.57% <75.00%> (+1.12%)
:arrow_up:

... and 5 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

This merge request have been merged with modification.


Autonomous Flight Algorithm

Autonomous Flight Algorithm
This algorithm aims to fly the drown towards the next AprilTag autonomously while taking into account its "pose threshold" to detect drift.

The historicalNavData program doesn't seem to be showing coherent data. I will be updating it to help create a better visualization of the data to better understand how the hardware is interacting with the software.

I've created a plotting program (plotting.py) to display the sensors' historical data on a graph separating the X-Y-Z-axes into three different lines. This will help us to better visualize what data the sensor is receiving in relation to the drone's movement.


Forces WrappedJsonAdapter to re-throw all exceptions.

All IOExceptions and JsonDataExceptions will be re-thrown.
Other types of exceptions will be wrapped in an AssertionError.

I've received a bug report where the adapter was failing later on in the finally bock. I assume this has to do with the fact that JsonDataExpection expends form RuntimeException, thus the error was not propagated properly.

Codecov Report

Merging #60 into master will decrease coverage by 0.93%.
The diff coverage is 50%.

@@             Coverage Diff              @@
##             master      #60      +/-   ##
============================================
- Coverage     94.15%   93.22%   -0.94%
  Complexity       95       95
============================================
  Files            23       23
  Lines           291      295       +4
  Branches         48       50       +2
============================================
+ Hits            274      275       +1
- Misses            7        8       +1
- Partials         10       12       +2

Impacted Files
Coverage Δ
Complexity Δ

...com/serjltt/moshi/adapters/WrappedJsonAdapter.java
89.13% <50%> (-6.11%)
17 <0> (ø)

Continue to review full report at Codecov.

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

:+1:

I'll ignore the coverage failure because moshi always wraps RuntimeExceptions into a JsonDataException, that there is a fail-safe.


Data Quality Profiler evolution dashboard

Feature

https://github.com/open-metadata/OpenMetadata/issues/4652

Describe the task
Based on https://github.com/open-metadata/OpenMetadata/issues/4656, prepare the dashboard to showcase the evolution of profiling metrics

Tracked in #6558


When do you plan to release your full code?

Hi,
Im currently working on a coreference project (a non-English one).
And I liked your demo.
When do you guys plan on releasing the code? We suppose to start the annotation in the following weeks.
I also have my own ready-to-use mention detector, so I guess would be able to plug it your system some how.
Thanks

Hi,
Apologies for delayed response. We have released our tool, in case, you are still running your study and would like to use it. Let me know if you have any questions while using it :)


Provide a controller for VMware IaaS

OSCM comes with mature integration capabilities for providing and provisioning IaaS services through its service catalog, e.g. OpenStack, Amazon Web Services or  Fujitsu Trusted Public S5.
VMware is a very popular virtual machine environment with a mature product portfolio. Therefore provide an adapter for IaaS services for VMware.

For a discussion thread about the contribution of this feature please see #3.

This feature has been implemented. Released with 16.1.


Hardware decryption

Enable use of hardware-backed keys for decryption.
TODO: Signing?

Part of #323 now.


Change script in UrlReaderProcessor.ts adding some code to handle URL Reader from GCS with wildcard /*

This fixes bug #21955

:heavy_check_mark: Checklist

[x] ChangeSet name is tasty-tips-itch.md and there l describe what it doing it the code. (more info)
[x] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

The implementation consist in adding a path with wildcard starting with https://storage.cloud.google.com/[bucketname]/*
and the wilcard is to load all the files inside the bucket and not just a single one with the full path
So the behavior is:
Before implementation we had this:

After implementarion:

So as you can see after the implementation the UI is capable to render all the components loaded from a relative path with wildcard.
Thank you for reviewing the pull request.

Hi All!
Just for your knowledge, my PR is failling in just two test that are nothing to do with the change l made.
failing test: E2E Linux / E2E Linux 18.x (pull_request)
E2E Linux / E2E Linux 20.x (pull_request)

Hi All!
Just for your knowledge, my PR is failling in just two test that are nothing to do with the change l made.
failing test: E2E Linux / E2E Linux 18.x (pull_request) E2E Linux / E2E Linux 20.x (pull_request)

Yep, those will stay broken until mui/material-ui#40427 is fixed

Hi All!
Just for your knowledge, my PR is failling in just two test that are nothing to do with the change l made.
failing test: E2E Linux / E2E Linux 18.x (pull_request) E2E Linux / E2E Linux 20.x (pull_request)

Yep, those will stay broken until mui/material-ui#40427 is fixed

Hi @jamieklassen do you had some time to review my PR? Dont hesitate to ping me if you have any question.

Hey guys 👋,
I just want to follow up this open issue PR, l have replaced the line const { filepath } = parseGitUrl(location); with const { pathname: filepath } = new URL(location); looks like it has worked.
Let me know your comments.
Thank you for taking the time to review them
@jamieklassen @benjdlambert @viglesiasce

@armandocomellas1 did you mean to keep all the other changes to the other files that you've made like the GKEClusterLocator.ts in kubernetes-backend? Or are you just looking to bug #21955?
I think that you might want to revert the other changes as they don't seem relevant for this bug fix, maybe you can explain what these other changes do in another PR and what issue they are trying to solve as I don't see the overlap here.
Thanks!

@armandocomellas1 did you mean to keep all the other changes to the other files that you've made like the GKEClusterLocator.ts in kubernetes-backend? Or are you just looking to bug #21955?
I think that you might want to revert the other changes as they don't seem relevant for this bug fix, maybe you can explain what these other changes do in another PR and what issue they are trying to solve as I don't see the overlap here.
Thanks!

Yeah, that's my bad, l mixed both issue solution in this PR, l had in my local repo the solution for the Gke backend auth, but they are two completley separetly things, if you want l can close this issue, and l will open a new PR for each issue.
Thanks!

Hi Guys!
@benjdlambert @jamieklassen
I already reverted to just the single and about this issue.
Please if you can review l will be happy to hear any news.
Thanks!

Handing over to @backstage/catalog-maintainers after the suggestions are done.


[CLOSED] Top-level Fixpoint Definitions

 Issue by euisuny
Monday Feb 24, 2020 at 03:09 GMT
Originally opened as https://github.com/antalsz/hs-to-coq/pull/148

Currently, we have DefinitionSentences at the top-level, even for recursive operators. Fixpoints are defined using inlined fix operators.
However, it would be cleaner (i.e. Coq's unfolding through cbn or simpl will behave ""as expected"") if we had top-level fixpoint definitions using FixpointSentence.
This is implemented by slapping on an extra pattern match on a top level function in src/lib/HsToCoq/ConvertHaskell/Module.hs. Probably not the most robust way to add on this feature, but it works (passes examples/boot.sh).
Also deleted src/lib/HsToCoq/ConvertHaskell/Declaration/Value.hs, which isn't used anywhere and seems to be a deprecated version of ConvertHsGroup in src/lib/HsToCoq/ConvertHaskell/Module.hs.
Proposed fix to #140.

euisuny included the following code: https://github.com/antalsz/hs-to-coq/pull/148/commits

 Comment by lastland
Monday Feb 24, 2020 at 03:23 GMT

@antalsz @nomeata What do you think? Any special reasons that hs-to-coq prefers Definition and fix to Fixpoint?

 Comment by antalsz
Monday Feb 24, 2020 at 03:24 GMT

@euisuny I'll have to take a closer look at this, but this looks potentially promising!  One thing I'm not certain about is what advantage we get – can you elaborate on how cbn/simpl work differently with Fixpoint vs. Definition := fix?

 Comment by euisuny
Tuesday Feb 25, 2020 at 14:24 GMT

Oops, I had thought that change made some difference in unfolding behavior, but I was wrong and can use fold to do what I wanted to do originally, anyways...
So, for now, the only selling point that remains for this change is aesthetics (and the marginal code cleanup on Value.hs).

 Comment by lastland
Tuesday Feb 25, 2020 at 20:20 GMT

The CI report seems to suggest that this is a nice aesthetic change that does not require extra editing on existing proofs.

 Comment by antalsz
Thursday Mar 12, 2020 at 16:18 GMT

I like this change.  I think there are two broader questions that go with it, though:

Does this change impact the question of what I've provisionally taken to calling “legibility”?  That is, the does this disrupt the source-level similarity between the Haskell code and the Coq code that is our best argument for why you should trust hs-to-coq?  On reflecting, I think the answer here is that this helps legibility, so I like it!

If we're going to do this, why not do it for Definitions too?  It's a good change, and we can spread it further!

If you could look into point 2 and the small code changes I mentioned above, then let's merge this!

 Comment by lastland
Thursday Mar 12, 2020 at 17:35 GMT

Thank you for including a troubleshooting section! Is this this really the best way to get lndir? It might be – I've certainly never checked why I have it – but that's a big install for a simple tool.

I can testify that installing xquartz is how I get lndir on my new Macbook. It may not be the only way to get lndir, but it's the easiest way after studying this a bit on Google.

 Comment by lastland
Tuesday May 19, 2020 at 15:06 GMT

I have just encountered an example that favors this change.
I have the following Haskell definition (please excuse me for not trying to minimize the example at this moment---I will do that later):
data SetExt :: * -> * where
  Empty :: SetExt a
  Singleton :: a -> SetExt a
  Add :: Eq a => a -> SetExt a -> SetExt a
  Union :: Eq a => SetExt a -> SetExt a -> SetExt a
  PowerSet :: SetExt a -> SetExt (MySet.Set a)

interp_ext :: SetExt a -> MySet.Set a
interp_ext Empty = MySet.empty
interp_ext (Singleton a) = MySet.singleton a
interp_ext (Add a s) = MySet.add a $ interp_ext s
interp_ext (Union s1 s2) = MySet.union (interp_ext s1) (interp_ext s2)
interp_ext (PowerSet s) = MySet.powerSet $ interp_ext s

The original hs-to-coq translation would give me a definition of interp_ext that cannot be type checked:
Error:
In environment
interp_ext : forall a : Type, SetExt a -> MySet.Set_ a
a : Type
interp_ext0 : SetExt a -> MySet.Set_ a
arg_0__ : SetExt a
T : Type
e : Base.Eq_ T
a0 : T
s : SetExt T
The term "s" has type "SetExt T" while it is expected to have type
 "SetExt a".

However, switching to this version with top-level fixpoint definitions solves the problem.

So, for now, the only selling point that remains for this change is aesthetics.

Not true! 🙂

 Comment by lastland
Tuesday May 26, 2020 at 19:56 GMT

I have manually merged this PR.


Consider using data structure other than HashMap in examples

HashMaps use a variable amount of gas, making the results of estimateGas unreliable.

As expected, Vec is the right choice for key-value stores in this ephemeral environment. benchmark


Symfony4 services upgrade

Due to nature of change, I dropped most of support of symfony < 4.

Its link to this PR https://github.com/GeniusesOfSymfony/WebsocketAppDemo/pull/11

Huge work thank you !
I have only one remark, i'm against the DIC autowiring

It's introduce black magic until you don't know how the container implement it
It's less explicit / readable
As OSS maintainer it could raise some issues about services definitions (for newcomers) introspections

I know it's an opiniated choice, but from a bundle perspective there are only downside and pitfall. So if you could switch to a fully wired services, much appreciated!
As you composer version bump, I will a tag a v2 as pre release, to let dev validate that everything is ok then public release like I did for sf4 supports. (I will keep updated this PR about the release status)
And again, amazing work, thank very much for your contribution!

Sorry to interrupt this discussion. I just wanted to say that the official position of Symfony about using autowiring on third-party bundles is: don't use it. That's why we don't use it in official bundles like MakerBundle.
The only reason is that it introduces a minor performance penalty in the dev environment (not in prod!!). If you use lots of bundles and all of them used autowiring, this could be noticeable (again, not in prod, where autowiring doesn't affect the app execution at all).

Hello @javiereguiluz, nice to see you here!
I was not aware that symfony as "official position" about that and it makes sense fo third party bundle.
Thank's for all your clarification :100:

I am sorry, I invite you to use my PR and add the service class back to remove autowiring as I am not gonna be able to do this change soon. I am already overcharge for next month. :(


Clean-up / organize codegen tests

Currently, when generating code for tests such as verifying the Codable conformance for some model is as expected, the code generation logic for tests is different than that which is used for production. This can result in issues slipping as tests can provide false positives.
To alleviate this, let's audit the code gen flow for production and ensure all tests go through the same flow (as much as possible).
The following is a concrete example of this issue.
In production, some preprocessing is done on the models here
This preprocessing is not performed in tests.

we must cleanup SetupTest methods which are duplicated all across.

https://github.com/awslabs/smithy-swift/blob/cb478655c8bdfe386d25f8b6729b3c9546c52742/smithy-swift-codegen/src/main/kotlin/software/amazon/smithy/swift/codegen/CodegenVisitor.kt#L175

Re: codegen flow for codegen tests; left most unchanged because each test tests for specific portion of codegen, and setup varies wildly depending on tests. Still did refactor out setUpTests function for XML codegen tests bc those are exact duplicates.
Organized codegen test files physically using directories, and logically using Kotlin package declarations.


Interrupt  other PCNT

Hi ,
Use 3 PCNT for Quadrature Encoder with ISR for overflow. (run ISR Overflow OK)
Use your LIB with succes for 2 steppers and 1 frequency module.
Lost somes Interrupts on PCNT encoders overflow when FastAccelStepper  -> engine.stepperConnectToPin
Howto fix it ?
(change priority or insert the ISR Quadrature Encoder  in your LIB )
Thanks JF

Hi,
what comes to my mind:

isr service is installed twice and it is not clear, which one is valid and which config is applied. Which parameters are you handing over to pcnt_isr_service_install(ESP_INTR_FLAG_SHARED | ESP_INTR_FLAG_IRAM); ?
Run time of all pcnt-ISR services is too long, if your and mine interrupts occur on same time. BTW your overflow interrupts happening how often ?

BtW: you mention, that you loose interrupts. Only during call of stepperConnectToPin or permanently ? And you loose all or only some ? Steppers are working in this condition ?

FastAccelStepperEngine engine = FastAccelStepperEngine();
FastAccelStepper *Fstepper[MAX_STEPPER];
OK
before FastAccelStepper -> engine.stepperConnectToPin no Int loose.
After one engine.stepperConnectToPin  some Int loose .
Int for PCNT in Half_encoder mode with 176 step count (rotate axe).
more loose when speed >=1000 rot/mn .
Time count =(30 to 100ms )1T loose for 2T or 5T (1 to 5 five Interrupt)

Thanks for explanation. Apparently the interrupts do not cooperate so well.
Do you use a lib for the other three pulse counters, or do you manage those interrupts in your app ? In the latter case, how do you call pcnt_isr_service_install() ?

I use this lib:
https://github.com/madhephaestus/ESP32Encoder

Thanks. This lib and FastAccelStepper are not compatible.
ESP32Encoder takes over the whole PCNT-module and installs an own interrupt handler.
If you call afterwards FastAccelStepper's connectToStepperPin(), then the ESP32Encoder will stop working.
Solution: ESP32Encoder author should not take over the PCNT-module interrupt. Espressif offers a cooperative solution: use pcnt_isr_service_install() and with pcnt_isr_handler_add() routines ca be registered to manage one channel's interrupt request.

Ok thanks for this explain!
It's a little bit hard to modifiethe .
I don't now howto do !

It is not rocket science to change that. Perhaps you can file an issue with the ESP32Encoder's github and he will implement this change.


Fix incorrect formatting of goenv-help output under MAWK

New lines in help output are wrongly replaced with empty string under Ubuntu Linux 16.04. For example:
$ goenv help shell
Usage: goenv shell <version>       goenv shell --unset|-u

Set GOENV_VERSION for the lifetime of a shell.

Expected is:
$ goenv help shell
Usage: goenv shell <version>
       goenv shell --unset|-u

Set GOENV_VERSION for the lifetime of a shell.

Rbenv once had the same problem and it was fixed by following pull request:
Fix incorrect formatting of rbenv-help output under MAWK by leocassarani · Pull Request #310 · rbenv/rbenv
https://github.com/rbenv/rbenv/pull/310

Sorry, I used old release of anyenv. I'm going to update anyenv and use recent one (syndbg/goenv) instead of your fork.
So it is okay to close this PR. (Of course, even if you merge it is okay too.)


[moto]

We help skilled programmers to be powerfully efficient; Nike-like - focus on the best in the field

"we'll updgrade and clean you're code, while you keep delivering features on time"


Add option to recursively clone submodules in ibek support git-clone

I found myself having to drop out of the convenient ibek support git-clone command in my first ibek-support adventure because the support module uses git submodules to pull in an external dependency.
Would it be possible to add an option to the git-clone function to recursively clone submodules? The equivalent of git clone --recurse-submodules...

Yes that should definitely be in the command - making a new more general issue for this:  https://github.com/epics-containers/ibek/issues/194


fix(ingest): canonicalize ingest JSON

Canonicalize JSON produced for ingest tests such that incidental changes is form of the JSON objects (keys moving around) that does not change the content of that JSON object does not trigger an ingest-test failure.

Might as well change it everywhere?
cd unstructured; find -name '*py' | xargs grep json.dumps | grep -v sort_keys


Setup proper staging and qa environment

Context
Proper environments i.e. staging and qa (for https://bat-dev-manage-courses-frontend-app.azurewebsites.net/)
Changes proposed in this pull request

Add {staging, qa}.rb - duplicates of production.rb
Add settings for staging and qa

Guidance to review
bin/rails server -e staging -b "ssl://localhost:3000?key=config/localhost/https/localhost.key&cert=config/localhost/https/localhost.crt"

We could reduce a lot of the duplication in the environment files, here's how: https://stackoverflow.com/questions/18193946/cascading-inherited-shared-rails-configuration-environments

Agree with Heidar, would be good to set up some kind of base settings so that there's less duplicate files.


REQUEST: MTLS with kafka, mongodb, postreSQL and microservices

enbaled mtls strict mode in a namespace where all the microsrevices and kakfka , mongodb , PostgreSQL are running, the connections are failing.
any suggestions would be helpful, Thanks in advance.

let's track on https://github.com/istio/istio/issues/51982


⚠ SceneTime has degraded performance

In b2dfbcf, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1657 ms

Resolved: SceneTime performance has improved in 666f4f8 after 6 minutes.


Fix table BBE output

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues.

Fixes #
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

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

@@           Coverage Diff           @@
##           master   #17268   +/-   ##
=======================================
  Coverage   68.85%   68.85%
=======================================
  Files           5        5
  Lines         122      122
  Branches       21       21
=======================================
  Hits           84       84
  Misses         38       38

Continue to review full report at Codecov.

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


[CI] Init torchinductor correctness and performance tests

Maybe I need to add torchinductor-tests.yml first, and then test if other scripts work file in a separate PR


refactor: Move all commands to their own files

Description

Start moving commands to their own files: /debug-env
migrate /debug-args
migrate /follow and /unfollow
migrate /uptime
migrate /user and /requests
sort cmakelists
migrate /lowtrust
migrate /chatters and /test-chatters
migrate /clip
migrate /marker
migrate /streamlink
migrate /popout
migrate /popup
migrate /clearmessages
Migrate /settitle
migrate /setgame
migrate /openurl
Migrate /raw
Migrate /fakemsg
Migrate /copy
Migrate /color
Migrate /clear and /delete
Migrate /block, /ignore, /unblock, and /unignore
Migrate /mods
Migrate /mod
Migrate /unmod
Migrate /announce
Migrate /vip
Migrate /unvip
Migrate /unban and /untimeout
Migrate /raid
Migrate /unraid
Migrate /vips
Migrate /commercial
Migrate /unstable-set-user-color
Migrate /debug-force-image-gc
Migrate /debug-force-image-unload
Migrate /reply

Misc.cpp/Misc.hpp is where I've put "random stuff" for now - idea is to see if CommandController.cpp can be clang-tidy'd now
As I have been migrating over files, I have been removing helix timegating from the commands


ketcher is undefined issue when updating from 2.13.0 to 2.14.0 and above

When updating ketcher from 2.13.0 to 2.14.0, what was working fine in my NextJS react app now  breaks (with Ketcher core, react and standalone). I've checked any uses of ketcher in my code and they're never undefined or if they are I've checked before trying to do anything with the Ketcher object. The stacktrace given suggests the error emerges from ketcher-react and not my user-code.
Any help on this would be appricated. Thank you.

In my case it seems that Ketcher was accessing window.ketcher after the Ketcher react component had unmounted and I was cleaning up the window object.


Directive outside of main index.html

I am currently having an issue with the directive being placed anywhere other then on the main index.html . If i add it to a view being called from a controller the redirect back to the site will not return a token in the session storage and the button will still have a text value of "sign in".
As soon as i add it to the index.html this issue goes away. I am very curious as to why this is occurring and if there is any way in which i can add the <oauth> directive into a view instead of on the main page.
thanks

I'm on holiday at the moment but when I get a chance I'll knock up a sample and see what's going on - I've never used it in that scenario but it should support it.

I am having the same issue.  Is there any update on this?

I'll try and take a look at it at the weekend - I'm super busy at the moment.

I've had a chance to look into this and the problem is caused, at least in my sample app, by the .otherwise entry in the Angular router redirecting to the root and losing the full URL before the directive embedded on the page can get to it.
One possibility is to update the .otherwise to also include the parameters but I'm looking to see if there is a more seamless solution.


scenarios were getting run multiple times due to stream usage

the scenario_finalize, scenario_starting_state only run once tests may not be too useful, feel free to remove these. I poked in the wrong place initially

May need to kick the travis build again somehow

:+1: not sure there's even any benefit to having this using streams


Engineering spawn point is on top of table

One of the engineering spawn points is on top of the table. The other spawn points should also be checked for weird spawns.

Credit to Laboredih123#7348 for the reminder.

Fixed by #4436


TCES-43: Create Add New Job Post Page

Description
Created the Add Job Post page.

The Save As Draft/Publish submission buttons were mocked and need to be replaced once those endpoints are merged.
The Save As Draft/Publish buttons currently redirect to /dashboard since the Job Post page is not yet complete
The Add Specific Fields button is also a dummy button since the design is not yet complete.

Figma Link: https://www.figma.com/design/ckkCZEVkae0kIXUwaQPbib/High-Fidelity-Designs?node-id=3577-17861&node-type=canvas&t=0Y1lrakUPy6YlHr0-0

Use Cases:

Filling in form values
Failure on Submitting/Publishing
Pressing Next and Back
Discard cancel and Discarding + redirect to Dashboard
https://github.com/user-attachments/assets/f124e93b-7a41-452a-9a33-e58105947aee

Use Cases:

Success on Submitting/Publishing
https://github.com/user-attachments/assets/ffebc8e9-e137-4ebf-b0b2-f17a111c491b

Use Cases:

Form values not filled in
https://github.com/user-attachments/assets/88f9e78e-9868-4a81-a91b-4197d44236c9

Issue #TCES-43
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

Checklist
Please delete options that are not applicable.

[x] My code follows the style guidelines of this project (required)
[x] I have performed a self-review of my code (required)
[x] I have linted and formatted my code (required)
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings

Well done! I think one more thing is that the title for Job Application still says Job Posting, but other than that and a few comments I left I think this is good.

Wait just to confirm this should say like "Submit Job Application" instead of Job Posting right? I might be wrong though.

This is amazing Michelle, great work!
Just a small edit, is it possible to make the form fields an even width?


Upgrade to React v15.3.0-rc.2

There were several fixes to how calls to propType checkers. This is to
account for the new deprecation warning - React.PropTypes will not be
part of production builds in the future.
Note: There is still a warning about an invalid argument to React.PropTypes.oneOf (React is running that validation sooner now). Specifically both of these because View.AccessibilityTraits is actually undefined in tests (didn't look into why you conditionally set that).
Test plan (required)
npm test & fixed all warnings due to proptype secret

By analyzing the blame information on this pull request, we identified @cpojer and @janicduplessis to be potential reviewers.

Let's try this…
@facebook-github-bot import

Thanks for importing. If you are an FB employee go to Phabricator to review.

Are you sure about this? :)


angularjs-slider displaying NaN and not working ...

angularjs-slider is not working on mobile browser (or with chrome desktop in mobile mode: CTRL+SHIFT+I and CTRL+SHIFT+M) ...
Display NaN when trying to slide ...  seems to be a touch event issue, because it's working with keyboard (but there is no JS error) ...
Actual problem is discribe with sample in this stackoverflow :
http://stackoverflow.com/questions/35758496/angular-js-touch-slider-displaying-nan-error-when-used-with-ionic-framework
Sample : https://jsfiddle.net/oziris_sp/t381ff52/
Updated : It's seems to be an side effect of using jQuery 3.0.0
Expected behaviour
Working without problem on mobile ...
Actual behaviour
Not working and display NaN when slided

All sliders on the demo site work on mobile. Please provide the demo that doesn't work.

Here a jsfiddle : https://jsfiddle.net/oziris_sp/t381ff52/ , try it in mobile mode !
It's happen only with jQuery 3.0.0 ...

 Touch events are broken with jQuery 3.0. This line is the culprit because in jQuery 3.0, they use proxy, so this way of testing undefined is incorrect.
I'm fixing it right away.

Demo of fixed version: https://jsfiddle.net/p9aa2ub3/


Proposal for enhancing Prisma Studio docs

Description
I would like to propose enhancing the documentation for Prisma Studio which is currently very sparse. I absolutely love this tool and think that it truly strikes a fantastic balance of abstraction.
This is just a start, but if we agree that this is a great time to work on this, I'd love to add more detail such as showing a comparison between how tables look in the underlying database and how they are represented in Prisma Studio in a way that is based on the datamodel.

cc: @mhwelander
bcc: @nikolasburk

Thanks so much for this Robin! Overall I think it looks great and we can definitely use a bit more content on this page. I just pointed out a few formulations that sound a bit too matketing-y for a reference docs page IMO, I think the tone here should be as neutral as possible (but would also love to hear @mhwelander's thoughts on this) 🙂
Also, just FYI, we already have an open (internal) "issue" for the Studio page where we want to add:

the different "features" of Studio, e.g. browsing data, modifying data, table vs tree view,...
ideally add a number of screenshots per feature

Just as a side-note in case you want to take a stab at this as well 😄

Thanks for this feedback, @nikolasburk ! I'll be sure to apply your suggestions and also try to expand things a bit. Also, I'd be happy to take a stab at that internal "issue" you mentioned. Could you link me to the issue or let me know how I should go about taking it on?
I'll work on these changes as soon as I can, hopefully this evening after work!


Support more dtypes for series in native code

This is because some operations like aggregations can return dtypes we
were not expecting, specially for integer columns.
Closes https://github.com/elixir-nx/explorer/issues/287

I decided to cast all integer series to i64 for simplicity. I think this works for all, except if we have a u64 series.


[Bug] Run API on Page load configuration does not get duplicated when the application is duplicated

Description

Create a new API
Set it to run on page load from the settings tab
Go to the applications page and duplicate the app
Check the API settings within the duplicated application, run on page load value it not set the same

@trishaanand assigning it to myself as per today's action pod meeting.


Escape dots in regular expressions

We had a situation where a customer domain was being caught as a bad referer due to the dot matching any character.  In this case ico.re was matching within a much longer domain name,
I think it would also benefit from looking for a word boundary at the beginning of each domain to avoid other false positives, so might add that later!

Hi Simon,
I can't really check the nginx file, but thanks for your input :+1:
Can you confirm that this technique works for you? Then i will merge it!
Looking forward for your next pull request.

Hi Stevie-Ray,
Yep, tested and in production! :)


Is typesafe Model.create possible?

Versions

sequelize: 5.7.6
sequelize-typescript: 0.6.10
typescript: 0.6.10

I'm submitting a ...
[x ] bug report
[ ] feature request
Actual behavior:
I seem to be able to pass any object to Model.create and not get any type errors.
Expected behavior:
I had hoped sequelize-typescript would help make sure the data moving into my db was typed correctly. Am I using it wrong?
Steps to reproduce:
run yarn tsc on the following repo and get no warnings or errors: https://github.com/jessep/sequelize-typescript-issue
Related code:
import { Table, Column, Model, Sequelize } from "sequelize-typescript";

const sequelize = new Sequelize({
    database: "some_db",
    dialect: "sqlite",
    username: "root",
    password: "",
    storage: ":memory:",
    modelPaths: [__dirname]
});

@Table
class User extends Model<User> {
    @Column
    name!: string;

    @Column
    birth!: Date;

    @Column
    state!: boolean;

    @Column
    card!: number;
}

// I had hoped that sequelize-typescript would protect me
// from attempting to create instances with bad data
const user = User.create({
    random: null,
    attributes: "blah",
    no: new Date(),
    error: false
});

sequelize-typescript types Model.create correctly if you use previous versions:
"sequelize-typescript": "0.6.10",
"sequelize": "4.43.2",

So it definitely is possible.
However, since sequelize@5 and sequelize-typescript@alpha, types for Model.create (and many other classes and methods) are moved to sequelize, but in a type-unsafe versions utilising any.
I don't quite understand the reasoning behind this regression.
This is actually the onlny reason we're still on sequelize@4 branch — we don't want to lose the type-safety.

Hey @jessep, thanks for asking. First, I see an issue here: sequelize@5 doesn't work with<EMAIL_ADDRESS>either use sequelize-typescript@next (which installs a sequelize-typescript@1) together with sequelize@5 or<EMAIL_ADDRESS>with sequelize@4
If you use<EMAIL_ADDRESS>with sequelize@4, you should get what you want :)
sequelize@5 provides its own typings, which are unfortunately less strict than the ones from<EMAIL_ADDRESS>Hope this helps!

To make it even more interesting, TypeScript contributors recommend to keep on using @types/sequelize because the typings bundled with Sequelize are unsafe by design :|

@mmiszy but does „by design“ also mean the create und build functions? Or would the sequelize team approve a PR which implements keyof for these functions? What do you think?

Closing this due to inactivity

Wtf, there is no answer here ! 😆
@RobinBuschmann please; it's not writen in the docs.
Is MyModel.create({ /* here */ }) (or even MyModelRepository.create()) supposed to be type-safe, or is that a bug that I get "object" as values in intellisense ?

OK; I found your PR on sequelize main repo @RobinBuschmann
For anyone landing here; wondering why something.create() does not type hint values, this is a trouble with raw sequelize (not sequelize-typescript) typings.
See @RobinBuschmann PR here to follow


id property

Does any way to generate or set manually an id?

Hi! Right now it's possible to set id manually:
const rect = figma.createRectangle();
// @ts-ignore
rect.id = "14:56";

But it's just workaround and id field is a part of Figma behavior, so I think id generating inside figma-api-stub should be implemented.
I don't know how exactly Figma aliased id field, maybe we can just generate string through nanoid.

I have implemented simple id generating:

figma.root got 0:0
figma.currentPage got 0:1
Other nodes get 1:{n}, where n started from 2 and increased after every node creation. E.g. this code

const rect1 = figma.createRectangle();
const rect2 = figma.createRectangle();
console.log(rect1.id, rect2.id);

prints 1:2 1:3.
It's available in latest version (figma-api-stub@0.0.34).

@ilyalesik amazing, thanks


Clarify Game Support Role

Clarify Game Support Role
A description of the issue:
The new Game Support role seems to be being misunderstod quite a lot. Meaning no disrespect, there seem to be a lot of people who have registered for the role despite only starting Game this year. This would suggest that they think the role is for them to recieve support, not to give it. I suspect this comes from people seeing others join the role, but not the announcement.
Proposed Solution:
We've already updated the join message to say Thank you for volunteering for the Game Support role! You can remove the role at any time with !removegamesupport. in an effort to help people who see someone else joining but not the announcement, but we think that more can be done.
An idea being discussed is locking the role behind the HQ, Moon, Forensics, and Volcano roles, and whilst this would require a bit of development work, certainly nothing insurmountable. It does also raise the question of if we should have a Game Support role for each base, as this would kinda seem necessary for such a system. WHY IS THE FEATURE CREEP ALARM GOING OFF?
Separately, the idea of resetting the role may be worth considering, so as to clean out the people who misunderstood, but it needs to be decided a) if it's needed, and b) how we should pick who to keep and who to kick.

In nick's original issue, I did suggest the idea of having Sudos/Roots able to 'veto' people from having the role, and I definitely agree that it is ambiguous about whether or not it is for people who can give support, or who want to receive it.
Potentially, we could make the base roles pingable? I don't know if there's a way to make a second role that would excuse people from being pinged but if so that'd be good as well. Then someone could ping @HQ if they needed HQ help, etc etc. This would avoid having 4 additional game support roles, just by making use of an unused role system that's already in place.

Support role for each base that the user can only volunteer for when they have that base's completed role sounds good. Then people can do @hqhelp in the headquarters channel for example, and have people who actually know what they're doing come and assist.
A reset sounds good too, with an announcement with it saying what the support roles are, how you get them and how to use them.
This would require minimal code changes on the bot

we could make the base roles pingable?

I'm not sure I can think of a faster way to discourage people claiming them

I don't know if there's a way to make a second role that would excuse people from being pinged but if so that'd be good as well.

I feel like splitting up the role into three roles probably wouldn't work. Without wanting to sound pretentious, people who are actually going to be useful if you do an @GiveMeHelp are going to be helpful for all bases. If you've just finished HQ, but have no clue about Forensics or Moon, realistically the odds are that someone who's after help is going to get lower quality help.

Sure, but they'll also get lower quality help if they're getting it from a newbie on 40%.

@thebeanogamer I see your problem and I agree with rak and think the rank should be by request only. I think it would be smart for people to only have it if they have completed some bases. I do feel people starting this year that have done the challenges are qualified to give hints just as much as veterans. Keep in mind veterans haven’t looked at some of the challenges in a long time. Someone who just completed them will be able to more easily recall exactly how he or she did it making their hints better.

Personally I feel like the rank should be avaliable if you have >75% total game completed; by this point you're a fair way in to each base and that seems fair to me.

@Bentechy66 makes a good point, but there is no way to tell.
Just make it assignable to someone who has completed at least 1 (or 2) base(s). That seems like the most reasonably achievable way to make sure that the pople giving advice can give advice.

if you have >75% total game completed

This would mean even more roles for us to have to verify...

IMO, there's not really any harm in allowing everyone access who wants it, even if they have only done a tiny amount. I would hope most people who are struggling with lvl 1 HQ won't pretend that they can help with someone stuck on lvl 13, and that most people seeking help would realise if the help they're getting is decent, and if the person they're getting it from is knowledgeable.


Installing it seems to come up with many broken dependencies

I tried to install Storex-Hub on my Mac per the instructions here and the terminal started screaming at me when I tried npm install lol
Is Storex-Hub currently functional? I'm trying to get Memex to sync up with DevonThink and Storex seemed like the most natural route.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@worldbrain/storex
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/storex-hub-plugin-internal-selftest
npm ERR!     dev<EMAIL_ADDRESS>from the root project
npm ERR!   3 more (@worldbrain/storex-backend-typeorm, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@worldbrain/storex-backend-dexie
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@worldbrain/storex-middleware-change-watcher
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/@worldbrain/storex
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@worldbrain/storex-backend-dexie
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@worldbrain/storex-middleware-change-watcher
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /Users/roberthaisfield/.npm/eresolve-report.txt for a full report.

npm ERR!      /Users/roberthaisfield/.npm/_logs/2022-04-28T18_28_15_175Z-debug-0.log

I have the same issues and I am on windows. I did try the npm to fix it with --force and when that didn't work --legacy-peer-deps at the end to try and install it anyways despite the broken dependencies and I still saw these errors.


[Expressions] Add prebuilt functions for adaptive cards

Discovered this via partner validation (adaptive cards team). We need to add two prebuilt functions to enable one of the adaptive card teams core samples (stock card)

formatNumber(value, precision) -> formatNumber(20, 2) = 20.00; formatNumber(0.53, 1) = 0.5. With this you could do formatNumber(value * 100, precision) to achieve your scenario.

formatDateTime() accept ticks as string input.

@boydc2014
@emgrol for docs impact.

formatNumber(1.55, 1) would be 1.5 or 1.6 ?
Currently, formatDateTime() accept number or string as the first parameter, if the first parameter is number, treat it as unix timestamp, otherwise treat it as a normal date string.
Can I think that, after the change, formatDateTime() would also accept number or string type as the first parameter, if the first parameter is number, treat it as unix timestamp. If it is a string type, and can be parsed into ticks, treat it as ticks input, else treat it as normal date time string. Is that right?

@vishwacsena  the formatNumber is straighforward and i put @cosmicshuai on this.
To suppoprt "ticks" the thing is it's not distinguishable from epoch, i mean, if formatDateTime see an int, how does it know to treat as millionSecondsFromepoch or window ticks.
We can either

extend the interface as formateDateTime(int, epoch=true),
just create two new functions like

formateEpoch
formateTicks
or whatever names we want.

I will recommend 2 for simplicity.

@vishwacsena
for formatNumber, I got a question. The returned value should be a string or a number? Since I met some difficulty with returning a number, the trailing zeros will disapper. Therefore, my current solution is returning a string to do the format.

@boydc2014 I like formatEpoch and formatTicks for clarity. Let's go with that.

making mods to priority label.  I've changed this to P0.  But to be clear, we have 1 shot at this in R9.  If we miss something or AC wants additional functionality beyond what this and JS PR provides, I won't hold R9 for it.  We'll have to give it to them in R10.


Other advantage of using a single file approach

In the Why Would I Use This Instead of Separate Files for Each Language? section, one of the biggest advantages that spring to my mind is partially translated content which often appears on multi-lingual websites as content of lesser value and/or interest is often left untranslated "for later" (and it might or might not get translated in the end).
If you are using a multi-file approach, this means you'll have to copy-paste such sections from file to file, whereas, with the fallback mechanism mentioned here, you can have some sections only available in the fallback language.
Even if you discount document that should to be translated at a future date, there are things that do not require translations, code snippets and math formulas spring to mind here.

Fantastic points.
The more I hear from folks on this project, the more things I realize I hadn't considered or had never run into myself.
I'll work on adding this to the Readme tomorrow.

Incorporated your notes into the README in d8bcf1c158c4900ca9a6a0bcc7b65b560f4678b1


maxDataPoints trimming rather than consolidating.

target=carbon.agents.host-a.committedPoints&from=-30min&format=json
[{
  "target": "carbon.agents.host-a.committedPoints",
  "datapoints": [[964976.0,<PHONE_NUMBER>], [972315.0,<PHONE_NUMBER>], [970754.0,<PHONE_NUMBER>], [974463.0,<PHONE_NUMBER>], [968827.0,<PHONE_NUMBER>], [968299.0,<PHONE_NUMBER>], [960593.0,<PHONE_NUMBER>], [973262.0,<PHONE_NUMBER>], [973257.0,<PHONE_NUMBER>], [967282.0,<PHONE_NUMBER>], [966225.0,<PHONE_NUMBER>], [962319.0,<PHONE_NUMBER>], [981648.0,<PHONE_NUMBER>], [967382.0,<PHONE_NUMBER>], [974717.0,<PHONE_NUMBER>], [968815.0,<PHONE_NUMBER>], [1019255.0,<PHONE_NUMBER>], [1034422.0,<PHONE_NUMBER>], [1028064.0,<PHONE_NUMBER>], [1027373.0,<PHONE_NUMBER>], [1021855.0,<PHONE_NUMBER>], [1033602.0,<PHONE_NUMBER>], [1013480.0,<PHONE_NUMBER>], [1017615.0,<PHONE_NUMBER>], [1031959.0,<PHONE_NUMBER>], [1027342.0,<PHONE_NUMBER>], [1031385.0,<PHONE_NUMBER>], [1026407.0,<PHONE_NUMBER>], [1033633.0,<PHONE_NUMBER>], [1020878.0,<PHONE_NUMBER>]]
}]

target=carbon.agents.host-a.committedPoints&from=-30min&format=json&maxDataPoints=15
[{
  "target": "carbon.agents.host-a.committedPoints",
  "datapoints": [[972315.0,<PHONE_NUMBER>], [970754.0,<PHONE_NUMBER>], [974463.0,<PHONE_NUMBER>], [968827.0,<PHONE_NUMBER>], [968299.0,<PHONE_NUMBER>], [960593.0,<PHONE_NUMBER>], [973262.0,<PHONE_NUMBER>], [973257.0,<PHONE_NUMBER>], [967282.0,<PHONE_NUMBER>], [966225.0,<PHONE_NUMBER>], [962319.0,<PHONE_NUMBER>], [981648.0,<PHONE_NUMBER>], [967382.0,<PHONE_NUMBER>], [974717.0,<PHONE_NUMBER>], [968815.0,<PHONE_NUMBER>]]
}]

It looks like on the surface that zip is just retrieving each element sequentially rather than via the consolidating generator.  This of course makes rendered graphs completely wrong with third party interfaces such as grafana.

Closing as it was infact a bug in pypy.


Need to modify folly::hash::fnv64_buf function to MurmurHash2 when get data from storage

This is done. Close


New & update icons from Orbit UI for Sketch 0.23.0 release

New and updated icons: icons.zip
We also need to rename a few icons but be careful, it's breaking change (icons are part of the package)
baggage-big => baggage-checked
baggage-small => baggage-cabin
baggages => baggage-set

Added & updated in #277


Chrome's file explorer crashing Application

Describe the bug
On MacOS 13.2.1 Ventura, Chrome 111 seems to crash whenever user attempts to upload a file using PASS
To Reproduce
Steps to reproduce the behavior:

Login into PASS
Click on "Choose File"
See error

Expected behavior
Expect to open Chrome's file explorer GUI
Screenshots
Difficult to show via screenshot, the browser just crashes (Chrome window with application disappears) after clicking on "Choose File"
Desktop (please complete the following information):

OS: MacOS 13.2.1
Browser: Chrome
Version 111

Have isolated the issue to HTML5's  element with Jared and reproduced the bug with a simple HTML with just the input element with type="file" embedded in a div.
The browser window instantly broke when trying to open the file explorer for file selection, based on the following configuration.
OS: MacOS 13.2.1 Ventura
Browser: Chrome
Version 111
However, things still work with an older version of Chrome (with Version 104) or with an older MacOS (10.15.7). Opera with MacOS 13.2.1 still works since Opera 96 is still running Chromium 110.0.5481.192 at this time (see link to Opera's Dev Blog), so it's safe to assume that the current issue is due to Chrome's Version 110 to 111 update with the latest MacOS version.

Bug might be caused by a small typo in the  element

Bug fully isolated to  element, namely the accept attribute. There was an extra . within one of the extensions ".docx.", which caused Chrome to go haywire. Issue has now been fixed with fixes merged into Development and Master.


BSC to DFI TypeError: Failed to fetch

Hi,
From BSC to DFI is not working. With the recovery function, the error "Failed to fetch" is displayed.
BSC Hash: 0xece95f973cca5137c65ceb4b217aba892bc8ecdb66223679d665e16e849604ba

Please try again and report, when problem still exists.


esp_eth: adapt ksz8041.c to changes from commit 03a6c49 (IDFGH-5874)

Local tests showed, that this should fix bug #7570.
As I just applied the changes analogous to commit 03a6c4975, someone who understands these changes should review this. Maybe @suda-morris?

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

Thank you for your reporting and fixing! I believe this is left over when we backporting some fixes to other release branches. We will apply your fix and sync it to GitHub ASAP.

Thank you for approving the changes! Please, can you explain shortly why the fix solves the issue that the phy init is called after the dhcp client gets started? I just copied your changes but don't really understand why they resolve the issue.

Yes, sure. In esp-idf Ethernet driver, the PHY link up/down status is fetched by a "timer". The timer is started in "esp_eth_start", after we send out the "ETHERNET_EVENT_START" signal.
There's a event handler for "ETHERNET_EVENT_START", which is responsible for setup up network interface (e.g. add Ethernet interface to LwIP).
The link timer will wake up periodically (default 2s), reading the PHY register and check if the link status got changed. Fo example, if it detects link up event, it will send out "ETHERNET_EVENT_CONNECT" signal. Likewise, there's an event handler for that, which is responsible for starting the DHCP client.
Without your fix, the buggy driver check the link status in the negotiation function (and then send out "ETHERNET_EVENT_CONNECT" event). But at that time, the network interface has been established, because we haven't call esp_eth_start yet.

Ok. Thank's for that explanation. So the significant part of the fix is the removal of <phy>_update_link_duplex_speed() inside the <phy>_negotiate() function...

@suda-morris, who takes care of merging this pull-request? Github tells me that I am not authorized to merge this pull request..


Update oci-java-sdk-objectstorage to 2.1.0

Updates com.oracle.oci.sdk:oci-java-sdk-objectstorage from 1.37.2 to 2.1.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.oracle.oci.sdk", artifactId = "oci-java-sdk-objectstorage" } ]

labels: library-update, semver-major

Superseded by #53.


Emoji in server name

Hello! I tried to parse info from FiveM servers and some of them contains emoji in names. But script returns weird things instead of normal utf8 symbols.
Example: 🌴 = ðŸŒ´ in response... Is it possible to convert them to something normal?

Fixed in 1.0.46


[Bug]: Unable to insert milk into exnihilo sequentia barrel

Minecraft Version
1.18.2
Forge Version
40.1.68
Mod Version
<IP_ADDRESS>
Modpack or other Mod
incompatibility with bucket lib <IP_ADDRESS> ed exnihilosequentia 20220818.010806; unable to put milk with a wooden or ceramic bucket into a barrel of exnihilo.
I sent this message to exnihilo owner to resolve this issue. Thank you
Describe the Issue
If you right click with a milk wooden or ceramic bucket the empy barrel doesn't fill up;
while doing this if  i have a milk wooden or ceramic bucket and the barrel is full of another liquid, the bucket take this liquid and empty the barrel and when i right click the empty barrel the second fluid go into the barrel while milk is always in the bucket.
Logs
No response
Do you use any performance-enhancing mods (e.g. OptiFine)?
No response

Thanks for your report. I will look into that.
Related issue: https://github.com/NovaMachina-Mods/ExNihiloSequentia/issues/347

@TimeheroTH is there any possibility to put milk into a barrel in Ex Nihilo Sequentia? For example with a vanilla milk bucket?
I cannot find such behaviour.

I fixed the strange behaviour that milk buckets could be filled with other fluids in 1.18.2-<IP_ADDRESS> and 1.19-<IP_ADDRESS>.
Filling a Ex Nihilo barrel with milk is no feature of Ex Nihilo, so this is not a compatibility issue.

I reopened the issue, because there was missing information that another mod enabeled the milk fluid and only im this case milk can be placed into barrels with a vanilla bucket. The BucketLib buckets do not work in this case and this should be fixed here. :)

to be clear: forge itself adds that possibility :D

Important is that now with all the information we arrived to a solution. Thank you both for the patience :D

I fixed the fluid handler of the milk bucket when the milk fluid of Forge is enabled. The versions 1.18.2-<IP_ADDRESS> and 1.19-<IP_ADDRESS> contain the changes. Thanks for your report. :)


Not downloading

Hey, THANKS so much for creating this! I am very interested in this project and was just testing it out on Linux. I am not able to get it working and wondered if you had any way to help me get it working.
I have leveraged your README and added a couple of imports to my script I'm running to make sure that my /home/USER location is printing/set appropriately.
The script runs, and then waits for several seconds, then closes out - there's no verbosity so I can't see what it's doing. There's no files being created in the directories I've chosen.
Thanks in advance for any help here. If you can tell me what flags or additions to my script I can add to see more, I'd appreciate it. I am using the following (USER is my username):
from general_conference_extractor.extract_URLs import extract_multiconference_talk_urls
from general_conference_extractor.data_output import extract_conference_talks
from pathlib import Path

home_dir = Path.home()

print( f'Path: { home_dir } !' )

# As an example
multiconference_talk_urls = extract_multiconference_talk_urls(2010,2024)

# Step 2 - Save the talks as txt docs and their metadata in a csv file
output_folder = '/home/USER/conference_talks'
metadata_csv_path = '/home/USER/conference_talks/metadata.csv'

# to produce the respective folders and documents
# extract_conference_talks(multiconference_talk_urls, output_folder, metadata_csv_path)

nvm - got it! Needed to uncomment the last line!

Great! If I ever find the time, I'll be sure to add verbose output for when problems arise (or if you'd like, you can branch the repo, makes some changes, and then do a pull request). If you find anything else, feel free to note it; I just can't guarantee that I'll be able to get to it right away though.


[UpdateManagement] SoftwareUpdateConfiguration changes to support Inclusion

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-libraries-for-java

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

Automation for azure-sdk-for-go

@ravbhatnagar , Could you please review ?

Typically this should have gone in a new api-version. but since this is preview, it should be fine. Signing off.

Ready for me to merge, @ikanni?

Please go head and merge

Please go head and merge

@marstr @ravbhatnagar  Thank you!


Signup using phone number instead of email

How to implement signup using phone number and OTP instead of email/password ?

Right now, you would need to do this solution yourself. It would be pretty easy to base it on the email solution. It is a planned future feature though.
Another option can be to use the Firebase login, which supports phone numbers.

I want to work on that issue can you assign me this label, so I can start work on this issue @vlidholt

@GautamSharma05 Have you done it?

Not yet @Faizan-Pasha

@GautamSharma05 No worries. I did it #1362.

New Issue created for this here: https://github.com/serverpod/serverpod/issues/2050
Closing this issue as it will be tracked there.


Implement robust regularization in 'survival:aft' objective

This is a follow-up to PR #4763, specifically to address https://github.com/dmlc/xgboost/pull/4763#discussion_r395942466.
Background: Latest XGBoost now supports survival regression with Accelerated Failure Time model. The AFT model involves maximizing a log likelihood, which is in a fraction form. Often, the gradient or hessian value would become INF or NAN because the denominator would be far too small. A first attempt to eliminate INF/NAN was in #4763, where I replace a small denominator with eps = 1e-16 if the denominator is smaller than eps. It certainly eliminates all INF and NAN. Also, the gradient is capped to a certain level.
Problem: Replacing the denominator with eps = 1e-16 introduces a bad artifact in the behavior of the gradient and hessian function. For example, the following graph visualizes the gradient of the AFT loss function as we vary the predicted label from 1e-2 to 1e4:

[True label = 100 (not censored), Distribution type = extreme, sigma = 2]
The gradient value abruptly snaps to zero if the predicted label is set to 1e-2. This is unreasonable, because y_pred = 1e-2 is strictly worse prediction than y_pred = 5.88e-2 but the former would have zero gradient and the latter gradient -20. We do not want this kind of sudden breaks in the graph. More generally, we'd like to precisely define the behavior of the gradient and the hessian functions at extreme values, i.e. when prediction (y_pred) is very small or very large.
The graph above should be modified as follows:

We catch two rabbits with one stone.

No sudden jump. Both y_pred = 5.88e-2 and y_pred = 1e-2 are identically set to -15.
No exploding gradient. Gradient is clipped to -15. (If gradient was positive, we'd clip to 15 instead.)

Here is how we set gradient and hessian values for very small or large y_pred:

Distribution

Uncensored Label
Right-censored Label
Left-censored Label
Interval-censored Label

y_pred=0
y_pred=INF
y_pred=0
y_pred=INF
y_pred=0
y_pred=INF
y_pred=0
y_pred=INF

Normal
Gradient
-15
15
-15
0
0
15
-15
15

Hessian
1/sigma^2
1/sigma^2
1/sigma^2
1e-16
1e-16
1/sigma^2
1/sigma^2
1/sigma^2

Logistic
Gradient
-1/sigma
1/sigma
-1/sigma
0
0
1/sigma
-1/sigma
1/sigma

Hessian
1e-16
1e-16
1e-16
1e-16
1e-16
1e-16
1e-16
1e-16

Extreme
Gradient
-15
1/sigma
-15
0
0
1/sigma
-15
1/sigma

Hessian
15
1e-16
15
1e-16
1e-16
1e-16
15
1e-16

where we clipped large gradients to +15 or -15, depending on their sign, and zero hessians are replaced with 1e-16 because XGBoost expects all data points to have nonzero hessians.
Also:

Fix a few typos in the AFT tutorial.
Add the AFT tutorial to https://xgboost.readthedocs.io Table of Contents.

cc @avinashbarnwal

This looks good and the right step to correct the behavior.

@trivialfis Take a look at GetLimitAtInfPred and see if it looks reasonable to you. Mainly I want your feedback on the coding style.

Let me take the small holiday and go through all the math.  :-)

@trivialfis Do you have any immediate objection? Given that this PR is a local change, I’d like to merge it for now. I would like to run benchmarks, and I need this PR so that hyperparameter tuning doesn’t crash in rare cases.

@hcho3 It would be great if we can clean up the commit message upon merging.  The squash and merge squashes all messages into one, which is kind of weird on master branch.  I sometimes grep those messages for finding a change,  also a summarized message could be helpful for easing the release procedure.  ;-)


NeoVIM Crashing when Scrolling Files w/o Error Message

Description
When scolling through files NeoVIM will crash.
Here's a screen recording on what we've already acomplished in the treesitter issue #5501:

https://youtu.be/t968TqB8vyI
Neovim version
NVIM v0.9.2
Build type: Release
LuaJIT 2.1.0-beta3

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/local/Cellar/neovim/0.9.2/share/nvim"

Run :checkhealth for more info

Expected behavior
NeoVIM keeps on going.
Actual behavior
NeoVIM closes itself without any error message.
Minimal config
local plugins = {
  treesitter = 'https://github.com/nvim-treesitter/nvim-treesitter',
  treesitter_context = 'https://github.com/nvim-treesitter/nvim-treesitter-context',
}

for name, url in pairs(plugins) do
  local install_path = '/tmp/nvim/site/'..name
  if vim.fn.isdirectory(install_path) == 0 then
    vim.fn.system { 'git', 'clone', '--depth=1', url, install_path }
  end
  vim.o.runtimepath = install_path..','..vim.o.runtimepath
end

vim.opt.number = true
vim.opt.relativenumber = true

require('nvim-treesitter.configs').setup {
  ensure_installed = { 'typescript' },
  sync_install = false,
  auto_install = true,
  highlight = {
    enable = true,
    additional_vim_regex_highlighting = false,
  }
}

Steps to reproduce

nvim --clean -u minimal.lua src/index.ts
Scroll up and down

Sorry, this isn't something we can help with here. My guess is this is related to the built parser objects being corrupt in some way.

And there's nothing I can do to fix this? Do I have to live without treesitter-context now? 🥺

I am having the same issue =(

Stacktrace please. However this is likely not an issue with this plugin.
Crashes should be reported to neovim core with a stacktrace.

For me the only solution was to uninstall treesitter-context, not had a single crash since then.

Can't help without a stacktrace. Sorry

Can't help without a stacktrace. Sorry

I tried to log everything, but the crash is happening and no logs are been generated

Can't help without a stacktrace. Sorry

If you give us some way to generate, I will be happy to try

I have the same issue, and I have the following logs from running with
vim.cmd("set verbosefile=~/nvim.log")
vim.cmd("set verbose=15")
vim.cmd('let $NVIM_LOG_FILE = expand("~/nvim.log")')

logs:
... <- successful logs
                                                                                Error executing vim.schedule lua callback: ...vim-treesitter-context/lua/treesitter-context/render.lua:68: 'height' key must be a positive Integer
                                                                                stack traceback:
                                                                                [C]: in function 'nvim_win_set_config'
                                                                                ...vim-treesitter-context/lua/treesitter-context/render.lua:68: in function 'display_window'
                                                                                ...vim-treesitter-context/lua/treesitter-context/render.lua:337: in function 'open'
                                                                                .../lazy/nvim-treesitter-context/lua/treesitter-context.lua:50: in function 'open'
                                                                                .../lazy/nvim-treesitter-context/lua/treesitter-context.lua:111: in function <.../lazy/nvim-treesitter-context/lua/treesitter-context.lua:92>
... <- cleanup logs

I don't know why it's indented, it's outputted like that.
Note: I use lazyvim - don't know if that helps with anything.
Neovim version: 0.9.4, mac m2, running nvim-treesitter-content on head dbcd938 I had this issue.
@lewis6991 let me know if you need more info


Deploy proxy server for Discord hostname update

In #5105 the domain name for the Discord badge requests was updated. However in production this badge proxies the HTTP request to the old servers, due to Discord allowing unlimited requests from our production IPs (see #4962). Our current code can't be deployed to the production servers because of the node version. So, we need to cherry-pick the commit onto a new branch and deploy it specially.
The current commit on legacy s0 is 4999e557c9f974347f06a7b5b4c18fa2f0468d3a (plus the two deploy commits).

This will probably also be something to do when we merge #5079. Maybe we can wait for that PR to be landed to take care of both at the same time?

No longer required following #5346, closing.


Weekly hiring/looking thread

@mrasband @seanson ok for you ?
Any input on the messages ?
#11

Instead of "job offer" probably just say "job". Offer implies a bit more!
Nice work, thanks!


Problem during installation

Error message:
$ pip install elizabeth
Collecting elizabeth
  Using cached elizabeth-0.3.11.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-build-lElGl2/elizabeth/setup.py", line 3, in <module>
        import elizabeth
      File "elizabeth/__init__.py", line 27, in <module>
        from elizabeth.core import *
      File "elizabeth/core/__init__.py", line 1, in <module>
        from .elizabeth import (
      File "elizabeth/core/elizabeth.py", line 38, in <module>
        from . import interdata as common
      File "elizabeth/core/interdata/__init__.py", line 5, in <module>
        from .code import *
      File "elizabeth/core/interdata/code.py", line 56
    SyntaxError: Non-ASCII character '\xc4' in file elizabeth/core/interdata/code.py on line 56, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details

I suggest encoding: utf-8 was forgotten in comment at first line.

@sergeybe Which version of Python do you use?

My version:
$ python
Python 2.7.12 (default, Nov 21 2016, 21:09:09)
[GCC 4.9.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>

@sergeybe That's right. Elizabeth run only on Python 3.x.

@sergeybe Look on the badges in the top of README.md.

Do you have any problems with Python 3.x? Can i close this issue?


Fixed this return types

Please do not update the README or Change Log, we will do this when we merge your PR.
This PR (delete as applicable)

Updates the Documentation

Describe the changes below:

Fixed this return types for Phaser.GameObjects.Bob.
Fixed this return types for Phaser.GameObjects.Components.PathFollower.
Fixed this return types for Phaser.GameObjects.Components.TransformMatrix.
Fixed this return types for Phaser.GameObjects.Container.
Fixed this return types for Phaser.GameObjects.DynamicBitmapText.
Fixed this return types for Phaser.GameObjects.Graphics.
Fixed this return types for Phaser.GameObjects.Group.
Fixed this return types for Phaser.GameObjects.Light.
Fixed this return types for Phaser.GameObjects.Particles.EmitterOp.
Fixed this return types fro Phaser.GameObjects.Particles.ParticleEmitter.
Fixed this return types for Phaser.GameObjects.Particles.ParticleEmitterManager.
Fixed this return types for Phaser.GameObjects.Particles.Zones.EdgeZone.
Fixed this return types for Phaser.GameObjects.Quad.
Fixed this return types for Phaser.GameObjects.Sprite.
Fixed this return types for Phaser.GameObjects.Text.
Fixed this return types for Phaser.GameObjects.Zone.
Fixed this return types for Phaser.Loader.LoaderPlugin.

I didn't realise that {this} was a valid return type here when I documented these, thanks for the fix.


how lock a branch?

How can I lock branches for all users except i selected? (like at BitBucket)

Thanks your feedback but I think it is same as https://github.com/gogits/gogs/issues/776


Feature: finalizers

#4

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.289%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
493

Relevant Lines:
512

💛  - Coveralls


[TOKEN] listing

Token's name and symbol

name: X-NFTOKEN
symbol: XNT

Token's website

www.xnftoken.org

Explorer link

https://songbird-explorer.flare.network/address/0xc6Cb9aA0b3476754491f5427a652294d37CeD8bE

Token's contract address

0xc6Cb9aA0b3476754491f5427a652294d37CeD8bE

PR checklist

[x] The token has a website
[x] The token has a contract address on the chain you want to be added
[x] The smart contract does not allow the minting of an arbitrary amount of tokens (either the minting rules are coded in the smart contract, or the minting permission has been released)
[x] Logo is provided

[x] The logo's shape is enclosed in a circle
[x] The logo has a height 500px and a width 500px
[x] The logo has 8px padding around it

Please let me know if this qualifies


Organise guest blogs

for each research collaboration and open farm (Rory Aronson)

@GrahamSteel  I'm transferring some issues over to you, let me know if you need any help with anything.

Sent out a tweet in this regard to kick this off.


Add black linting to CI/CD

Black formatter is included in the git pre-commit hooks for the repository. Unfortunately, there is no way to automatically enable the pre-commit hooks upon checkout the repository. So it is possible to push commits without ensure the code is formatted appropriately.
So I propose to add black action to the pipeline. This is useful to ensure that git pre-commit hooks are installed and used by all developers/contributors.

address with #214 merged to #198


MIT License in release tarball vs. BSL-1.0 in Git Repository

I've noticed a license inconsistency in the PEGTL repository. The tarball for v3.2.7 downloaded from here contains the MIT License.
[zulu@debian PEGTL-3.2.7]$ cat LICENSE | head -n1
The MIT License (MIT)

However #270 & c7630f1649906daf08b8ddca1420e66b542bae2b indicates a license change occured. Could you please clarify which license applies for the project

The latest official release is still based on the 3.x-branch, in which the PEGTL was still MIT licensed. The change to BSL-1.0 happened on the main branch and will lead to a new major release, but no official releases have been made yet. Yeah, it's a long time in the making...


chore(deps): remove deprecated dependencies and bump aws-cdk

Fixes #255
I think this should be semver major

Not exactly sure what to do about the integ:snapshots, I updated them and the test passes locally. I wonder if it's because of the gh runner differences vs my system.

Slightly offtopic: I also noticed something you may want to look into for the test infrastructure.
The GitHub workflow for testing updates the snapshots, too, while running the tests. This doesn't seem like something you'd want. Screenshot from recent workflow:

Slightly offtopic: I also noticed something you may want to look into for the test infrastructure.
The GitHub workflow for testing updates the snapshots, too, while running the tests. This doesn't seem like something you'd want. Screenshot from recent workflow:

This is the correct behavior, the "mutations" are then committed back, see
https://github.com/jogold/cloudstructs/blob/0ad4e6f8f53867e95aadb38ccdb27adb27ff4443/.github/workflows/build.yml#L55
https://github.com/projen/projen/blob/main/docs/publishing/build.md#self-mutation

Not exactly sure what to do about the integ:snapshots, I updated them and the test passes locally. I wonder if it's because of the gh runner differences vs my system.

Looking into this, usually fixed by running everything in a codespace.

Slightly offtopic: I also noticed something you may want to look into for the test infrastructure.
The GitHub workflow for testing updates the snapshots, too, while running the tests. This doesn't seem like something you'd want. Screenshot from recent workflow:

This is the correct behavior, the "mutations" are then committed back, see
https://github.com/jogold/cloudstructs/blob/0ad4e6f8f53867e95aadb38ccdb27adb27ff4443/.github/workflows/build.yml#L55
<EMAIL_ADDRESS>
Yes, but what's the point of the test if the snapshots are always blindly updated? Seems easy to overlook.

Thanks @andreialecu


Is possible moderate the users' activities?

Hi,
I found django-moderation to moderate the activities of user.
Thanks, best regards

This is interesting, it would be useful under a wider scenario than the originally intended for Bootcamp. Do you have than kind of implementation?

At the moment no, but I am developing a custom Bootcamp.
I'm trying to integrate the django-moderation to have a such "parent control" of activities or feeds.
Furthermore i added groups manager to extend the auth of django.

We you have it implemented, and if you're going to share it, please let me know. It sounds interesting.

Where can I find it?
2017-12-06 17:39 GMT+01:00 Sebastian Reyes Espinosa <
<EMAIL_ADDRESS>
Closed #130 https://github.com/vitorfs/bootcamp/issues/130.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vitorfs/bootcamp/issues/130#event-1375170422, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AVdMg3Z6HeeyDwBa16wQJmtXHqIra3tLks5s9sNGgaJpZM4Qw6UL
.


[iOS] Fatal error: null value for a non-nullable variable

I am using version 1.8.0 of this plugin and Flutter 3.22.1 (can't confirm if this was happening in prior versions since this feature was not being thoroughly tested)
Sharing a picture to my app in iOS works only for the 1st time. All subsequent times, app just breaks upon receiving shared image and all I get in the console is:

receive_sharing_intent/SwiftReceiveSharingIntentPlugin.swift:192: Fatal error: Unexpectedly found nil while unwrapping an Optional value

How fix this?

Have you found the solution yet ? I am having the same issue, except it doesn't work at all not even the first time...

Have you found the solution yet ? I am having the same issue, except it doesn't work at all not even the first time...

I haven't solved it yet. Currently, I manually made another conversion when encodData is empty, which can avoid application crashes. However, sometimes it may not run properly when receiving files.

Tested on my example, works fine, are there any other things I should be careful of or check ? Thanks for help


Parchment manual installation?

@rechsteiner I'm looking forward to use Parchment in a popular service app without any dependency manager.
Is there is any official documentation/guide/wiki for a manual installation and usage?

🤔

yes, it was somewhere on the page

I believe you would have to copy all the files from this folder.

@gchriswill does copying the files work for you? Another option would be to build Parchment.framework and include that in your project.

@linusGeffarth I’m going to try that in a few hours.
@rechsteiner , I’m missing some libraries. Let me check if in that directory I can find the missing dependencies and If it works by copying the files into project. Other wise I’ll try to build the framework.

i dont know how . to include this lib manually  please explain

@LinusGeffarth Thanks for the URL. ☺
@rechsteiner Thanks for pointing out the the tip. 😉
@AnasAlsaadi Download (NOT CLONE) the entire repo and follow one of the example projects. 👌    @AnasAlsaadi Bellow are the steps 👇

Sorry guys for taking so much time to test and reply to this thread.
I downloaded the entire repository to make it work.
I followed up with same approach as one of your examples, the IconsExample
Every example included in the repository works as expected as well.

Here are the steps I followed to get it to work: 🙄

Download the entire repo and open the project
Choose any example target and build at least once
In the file navigator pane, go to the Products folder and right click in the Parchment framework
Choose "Show in Finder", and option + drag the framework bundle to your Desktop (temporary)
Now, open your project's folder where you want to use Parchment and drop the framework there.
Open your project in Xcode, and import Parchment through Embedded libraries sections
In your Swift file, add the import with Parchment
Use it. 😎

@rechsteiner ,
The initial intensions when I created this issue, was because I couldn't find any guidance in the project's repo on how-to use Parchment without a dependency manager. I would recommend providing the guides for manual installations in a WIKI page and/or your README docs. I will close this issue and create another one for requesting the missing technical guide in the Installation section and then will create a PR from my fork with the updated README.
There could be many cases in which a user can't or is not allowed to install Parchment through a dependency manager. In my case, in the project that I'm currently working on, the team only use submodules as we understood that its safer and provides the security messures that are required in our project. In a near future, if approved, I'll need to do some mods to bring Parchment as a submodule to our project from our own git server.
My initial intentions was to build a proof of concept for our lead devs and rest of the team.
If we end up using and including Parchment on a future release of our project, I'll then provide an update and brief report of the usage case.
Also, I'm planning to, "if allowed", start contributing on the Parchment project because I found that the project has good architecture and follows software engineering best practices, and when I see great work I get inspired.
To you and all the Parchment project's contributors:
I appreciate it very much. Thank you and keep the good work! ❤
-- @gchriswill


column "granularity" does not exist

I'm getting these errors in /var/log/messages:
Mar 20 03:58:58 fedora 856f127dd587[1816]: 2023-03-20 09:58:58.007 UTC [37894] STATEMENT:  INSERT INTO serverpod_health_metric ("name", "serverId", "timestamp", "isHealthy", "value", "granularity") VALUES ('serverpod_database', 'default', '"2023-03-20T09:58:00.000Z"', TRUE, 0.007594, 1) RETURNING id
Mar 20 03:58:58 fedora 856f127dd587[1816]: 2023-03-20 09:58:58.158 UTC [37898] ERROR:  column "granularity" does not exist at character 105

Serverpod version: git main
Platform: Linux

Is it possible that you used an older version of Serverpod to create the database tables?


[Feature-Request] Respawning composed node in rgbd_plc.launch.py, restarting from failed states.

Why:
The composable nodes in rgbd_plc.launch.py (same goes for rtabmap.launch.py) do not have any way to get out of critical failure states, for example:
X_LINK_ERROR and ping missed messages which seemingly break the pipeline.

It would be nice if there was a way to kill the nodes and restart the pipeline since ros2 does not support node killing like ros1 did.
What:
A parameter that would allow (composable)nodes to exit (and start up) gracefully after critical error.
How:
Maybe before resulting to straight up killing the nodes, a lifecycle nodes could be implemented and just the pipeline could be destroyed (in on_cleanup()) and restored (in on_configuration()). Otherwise, just exit() in critical failed state, and parameter for respawn in the launcher would be also doable.

Hi, unfortunately Lifecycle nodes are not supported by image_transport package so unfortunately they cannot be used by camera drivers. There is a watchdog/restart mechanism that you can enable via parameter, but in some edge cases it might fail.

Thank you for that restart mechanism, i guess nothing more can be done about it now


The relationship between ISEs and ICEs

The class 'Information Structure Entity' is defined as: "A Generically Dependent Continuant that is not an Information Content Entity (ICE) but which is complemented or complementable by some ICE to create another ICE."
There is, however no object property such as 'complements' in CCO, and the relationship between, say, a cell in a spreadsheet and the information in any copy of a spreadsheet file. This is also not discussed in the 'Model Language with CCO' doc, but seems highly relevant. This leaves it unclear how to represent the relationship between instances of ISE and instances of ICE. Note: I am particularly concerned with software files, which I understand the CCO treats as IBEs.

Information Structure Entity has been obsoleted in version 1.3


Suggestion: Scan through current texfile(s) for defined commands.

quite often macros are set, either through \def, \newcommand, \newdocumentcommand \newenvironment with robust variations and such. Could the editor scan through the current file, or project for any of these definitions and add them to a temporary autocomplete-list? Bonus if it also would be able to create any mandotory fields,
for instance:
\newcommand{\theader}[2]{#1 - #2}  would autocomplete from the... to \theader{field}{field}

For comparison in the Sublime Text version https://github.com/SublimeText/LaTeXTools/pull/711:

It would be more complicated, because the Atom version hasn't something like the analysis yet https://github.com/SublimeText/LaTeXTools/pull/611, which would simplify the project scanning.


Misc docs index & development section improvements

I noticed a few links and omissions in the main docs index and in the development guide sections, fix them up.

Coverage decreased (-0.03%) to 36.892% when pulling 52376acd93499badbedf444b8dc2149bc9de776e on joestringer:submit/dev-guide-fixups into a20dcd10ff2f9c831040309a810ac2409acf0cd6 on cilium:master.


skip type = "I" containers

➜ k ice cpu -l "app.kubernetes.io/name in (backend)"
T  PODNAME                                   CONTAINER      USED  REQUEST  LIMIT  %REQ  %LIMIT
I  protct-backend-v1-5648c9d8df-nx9nd        install        0m    0m       0m     -     -
S  protct-backend-v1-5648c9d8df-nx9nd        backend        72m   0m       1000m  -     7.13
I  protct-celery-beat-v1-6686dfc9df-lw48m    install        0m    0m       0m     -     -
S  protct-celery-beat-v1-6686dfc9df-lw48m    celery-beat    1m    0m       1000m  -     0.02
I  protct-celery-worker-v1-8664579cd5-xhxqk  install        0m    0m       0m     -     -
S  protct-celery-worker-v1-8664579cd5-xhxqk  celery-worker  2m    0m       1000m  -     0.19
I  protct-django-migrations-v1--1-crcb8      install        0m    0m       0m     -     -
S  protct-django-migrations-v1--1-crcb8      migrations     0m    0m       256m   -     -

I assume "I" == init container? What is "S" type container?
Also is it possible all init containers and concentrate only on non-terminated containers?

Yes I is for an init container and S is for a standard or normal container, I believe it's buried somewhere in the documentation.
Regarding your question about the non terminated containers, are you asking for a command line switch that only shows currently running containers?
or something else as I'm not sure I follow

right, technically speaking I'm less interested in INIT containers if I need to get a picture of what is going on and I-containers just clog the view.

P.S. - great plugin I love it :)

right, technically speaking I'm less interested in INIT containers if I need to get a picture of what is going on and I-containers just clog the view.

Ah, ok
So I'll just hide init containers from the output of the mem and cpu commands by default.
Should be easy enough, leave it with me

update v0.0.16 hides Init containers from the cpu and memory output using -i flag will show them if they are needed


selected element will not move always

Expected behavior
after disconnecting a shared* node with tag (e.g. highway=bus_stop) then the node of the selected element (either way or area) should also used for a potential move afterwards
*shared e.g. with way(highway=tertiary) and area(landuse=residential)
Actual behavior
sometimes the other element is moved (this behavior is annoying and persist for a long time - i was just too lazy to report it... )
steps to reproduce:
0. have two shared elements: e.g. way highway=tertiary (should also happened for highway=) and an area of e.g. landuse=residential (should also happened for landuse=)
0. have a shared node on this structure with tag highway=bus_stop or highway=stop

select a shared node (e.g. highway=bus_stop)
right mouse click => disconnect
select the area (landuse=residential)
move the node (highway=bus_stop):
=> the node and line of area (landuse=residential) is modified:  OK   :-)
combine the nodes (highway=bus_stop) of way and area
select a shared node (e.g. highway=bus_stop)
right mouse click => disconnect
select the area (landuse=residential)
move the node (highway=bus_stop):
=> the node and line of way (highway=tertiary) is modified:  not OK   :-(

Screenshots illustrating the current situation
by using the preview.editor.com:

ps: please correct/change the issue subject title text for better understanding

This is #2206


EAGLE-415 Compilation failure in develop branch - Copyright missing

LGTM, thanks.

@dbosco Patch applied. Thanks for the contribution and would you pls. close the pull request?