Cannot debug hello_world example on web - null exception in static interop

Repro

start VSCode in flutter/examples/hello_world
add a breakpoint on runMain
start debugging on web

Expected
Debugger starts and execution pauses on the breakpoint line
Actual: exception in chrome
"Error: Expected a value of type 'FontCollectionNamespace', but got one of type 'Null'
    at Object.throw_ [as throw] (http://localhost:55836/dart_sdk.js:5454:11)
    at Object.castError (http://localhost:55836/dart_sdk.js:5413:15)
    at dart.StaticInteropType.new.as (http://localhost:55836/dart_sdk.js:7328:40)
    at Object.getProperty (http://localhost:55836/dart_sdk.js:63119:14)
    at Object.CanvasKitExtension$124get$35FontCollection [as CanvasKitExtension|get#FontCollection] (http://localhost:55836/dart_sdk.js:195764:20)
    at [_registerWithFontProvider] (http://localhost:55836/dart_sdk.js:148200:128)
    at _engine.SkiaFontCollection.new.registerDownloadedFonts (http://localhost:55836/dart_sdk.js:148282:38)
    at initializeEngineServices (http://localhost:55836/dart_sdk.js:206223:39)
    at initializeEngineServices.next (<anonymous>)
    at http://localhost:55836/dart_sdk.js:40976:33
    at _RootZone.runUnary (http://localhost:55836/dart_sdk.js:40809:59)
    at _FutureListener.thenAwait.handleValue (http://localhost:55836/dart_sdk.js:36012:29)
    at handleValueCallback (http://localhost:55836/dart_sdk.js:36583:49)
    at _Future._propagateToListeners (http://localhost:55836/dart_sdk.js:36621:17)
    at [_completeWithValue] (http://localhost:55836/dart_sdk.js:36456:23)
    at http://localhost:55836/dart_sdk.js:35653:46
    at _RootZone.runUnary (http://localhost:55836/dart_sdk.js:40809:59)
    at _FutureListener.then.handleValue (http://localhost:55836/dart_sdk.js:36012:29)
    at handleValueCallback (http://localhost:55836/dart_sdk.js:36583:49)
    at _Future._propagateToListeners (http://localhost:55836/dart_sdk.js:36621:17)
    at [_completeWithValue] (http://localhost:55836/dart_sdk.js:36456:23)
    at http://localhost:55836/dart_sdk.js:35653:46
    at _RootZone.runUnary (http://localhost:55836/dart_sdk.js:40809:59)
    at _FutureListener.then.handleValue (http://localhost:55836/dart_sdk.js:36012:29)
    at handleValueCallback (http://localhost:55836/dart_sdk.js:36583:49)
    at _Future._propagateToListeners (http://localhost:55836/dart_sdk.js:36621:17)
    at [_completeWithValue] (http://localhost:55836/dart_sdk.js:36456:23)
    at async._AsyncCallbackEntry.new.callback (http://localhost:55836/dart_sdk.js:36490:35)
    at Object._microtaskLoop (http://localhost:55836/dart_sdk.js:41119:13)
    at _startMicrotaskLoop (http://localhost:55836/dart_sdk.js:41125:13)
    at http://localhost:55836/dart_sdk.js:36846:9"

/cc @srujzs
/cc @christopherfujino @elliette FYI

Update: this is a duplicate of as https://github.com/flutter/flutter/issues/123737, closing.


Update English subtitles for Morevna Episode 4.0.1 on Youtube

The Youtube captions for Morevna Episode 4.0.1 (https://www.youtube.com/watch?v=Ubx-_jhya10) are still using an older version of the subtitles from this repository. It should be updated to use the current msrt.

Hey @scribblemaniac! Maybe you can update subtitles if I will make you admin of Morevna channel? ^__^

Sure, if you want me to. Would be helpful if I ever decide to look at #41 (which I'm thinking about again).

Hi Konstantin!
Great to hear from you!
I'm sorry I haven't answered your messages but I've been quite busy for the
last couple of weeks.
I'll be a little more relaxed later today and will have a look at the
captions you want me to.
I'll let you know if admin access is needed or if I have any questions.
Hope you have an awesome day!
Raúl
On Mon, 24 May 2021 at 23:41, scribblemaniac @.***>
wrote:

Sure, if you want me to. Would be helpful if I ever decide to look at #41
https://github.com/morevnaproject/subtitles-translation/issues/41
(which I'm thinking about again).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/morevnaproject/subtitles-translation/issues/68#issuecomment-847524504,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF7XH6N5A6GLFP6WVUVW2FDTPMS7LANCNFSM45MCO3BA
.

I opened a pull request to add the Spanish translation to Episode 4
subtitles master on github:
https://github.com/morevnaproject/subtitles-translation/pull/70
I don't seem to be able to add them directly on YouTube yet. Was zootiteres
at gmail dot com granted access?
See you around! :-)
On Fri, May 28, 2021 at 10:15 AM Konstantin Dmitriev <
@.***> wrote:

@scribblemaniac https://github.com/scribblemaniac Added you to our
YouTube channel now. Thank you! ^__^
@rulcas https://github.com/rulcas Hey Raúl! Happy to hear from you! The
current issue is already handled by @scribblemaniac
https://github.com/scribblemaniac, but maybe you will consider to
contribute to translations for Morevna Episode 4
https://github.com/morevnaproject/subtitles-translation/blob/master/morevna-ep4.msrt?
We have only English translation there, translations to other languages are
much appreciated! ^__^
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/morevnaproject/subtitles-translation/issues/68#issuecomment-850490090,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF7XH6LTX323DLLS6KMLQHLTP6XR5ANCNFSM45MCO3BA
.

--
Zoo Títeres
Cuernavaca, Mor
562 621 8862
@.***

@morevnaproject I'm going to need you to change my permissions. The communications manager role can't use Youtube, so it does not appear that I can change the subtitles or even switch to the brand account on Youtube with it.

@scribblemaniac Sorry, I have assigned wrong permissions! Can you please check again now?

The English subtitles for Morevna Episode 4.0.1 have been updated now.

Thank you so much!


Update UI test for mac OS

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes
Several UI test cases failed on the mac OS.

The scenario of  get a parsed JSON response in cookbook_uispec.js failed.

Reason: When inputting a value into a text box, WebdriverIO fails to clear the default vaule.
Information: https://github.com/webdriverio/webdriverio/issues/1140
Workaround: Nothing (run the test on the OS other than mac OS)

All scenarios failed when running with WebdriverIO 4.14.1 and --non-headless option.

Reason: Maximizing a browser fails.
Information: https://github.com/webdriverio/webdriverio/issues/3043
Workaround: Run a UI test without --non-headless option, or run with WebdriverIO 4.13.1.

Most scenarios failed when running UI test simultaneously.

Reason: Concurrent connection to ChromeDriver fails.
Information: https://github.com/flavorjones/chromedriver-helper/issues/44
Workaround: Change the value of maxInstances of capabilities in wdio.conf.js from 2 to 1.
After you applied the workarounds of the above 2 and 3, all scenarios other than 1 will result in success.

Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the mailing list/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage remained the same at 76.484% when pulling 715cc77e763acc2e8d4e67c76f1852037ed8c548 on node-red-hitachi:dev-uitest-mac into c0837ead0ec1364116a23378c143e5cbd4b45134 on node-red:dev.


Update cup_finals.txt

Updated with the Uruguay - Portugal match.

Thanks again. Keep it up. See the GitHub invitation to join. Welcome.


[17.03.x] fix autoremove on older api

Commit 87a5346 cherry-picked changes into the 17.03 branch to make the client skip auto-removing containers on API 1.25 and up.
Some changes got lost during that cherry-pick, resulting in 17.03 clients to not fall back to the old behavior when connecting to API version 1.24 or below.
This patch addresses this issue for the 17.03 branch by copying the HostConfig.AutoRemove property to a local variable before it is overridden in ContainerCreate().
This change is not needed on "master" (17.04-dev), which does not have this problem.
Thanks to @jlhawn  for finding this bug.
I also added integration tests in a second commit (32dbb5c46569fbd404a88775c5eb58b5da0b9240), so that we can merge those tests to master

LGTM


Support Surface server-side rendering component library (apply class)

Support Surface server-side rendering component library (apply class)

Looks good. Thanks!


Exclude/disable commands via config

Context
Palm commands come from many places. Core, plugins, the repository... and that list is growing!
Some of those commands are useful maybe one time (palm containerize). The rest of the time, those commands are clutter in palm --help.
Some commands may also just not work in your project - for example palm lint which uses the black library to lint python will not work in a javascript project. Ideally, palm lint is overridden by a command that does work. However, in the event that linting is not implemented, a developer on that project should be able to disable that command entirely.
Is your feature request related to a problem? Please describe.
When I'm working in an established palm project, I do not want to see irrelevant, or un-useful commands in palm help.
Describe the solution you'd like
Allow each project to specify plugins to exclude via palm config. E.g.
disable_commands:
- containerize
- init
- lint

Describe alternatives you've considered

One-time use commands could potentially be disabled with logic (e.g. is this project already containerized?) however that does not scale well and will not solve the need to disable a command due to incompatibility (e.g. the linting example)

Is there an existing feature request for this?

[x]  I have searched the existing issues

+1

agreed this would be nice to clean things up. so like..
.palm/config.yml
...
disabled:
    - init


fixed bug resulting in mode desync, causing fuse to fail

type bits in mode bitplane will now be cleared before DB entry and re-created on export using the "type" column
plan to move these functionality to attr.go

Hello, Noah!
Thanks a lot for checking out this project and sending out a fix!
Could you also please attach some more information around the bug you faced (how to reproduce it)?


fixed version number being incorrect

I changed _version_ to 1.0.1

thanks!

And... now I need to update. lol just got a message about it but thanks for making this script :)

This may need to be fixed too...
glitch_this: Glitchify images and GIFs, with highly customizable options!
* Website: https://github.com/TotallyNotChase/glitch-this
* Version: 1.0.0
* Changelog: https://github.com/TotallyNotChase/glitch-this/blob/master/CHANGELOG.md
The version number is wrong on the glitch_this -h text and probably the version command flag too

I need to update the package on pypi to fix the versions, will do that

should be fixed now

ok, thanks


No file named 'scoring'

No module named 'scoring' in SemiSkipGram

I believe I forgot to upload that scoring.py file, sorry for the inconvenience! I plan to clean up this repo, upload my input data and write some documentation over this weekend. I will let you know when this is almost done -- it should be around Jan 6th.


Integration of Cosmos SDK based Apps with Substrate Pallets for IBC

Integration of Cosmos SDK based Apps with Substrate Pallets for IBC

Thanks, @gokulsan
This project is a substrate pallet similar to other pallets in https://github.com/paritytech/substrate/tree/master/frame. It should not contain go code or a demonstration chain. We already have a substrate chain to demonstrate how this pallet can be used.
Yes, we should have a cosmos sdk chain to test and demonstrate that the substrate chain can communicate with it using ibc, but I think this cosmos sdk chain should be stored in a separate repo or in ibc-demo.

Hi @gokulsan. Nice to see you here, show interesting on substrate IBC. Would you like to join substrate ibc working group call, which discuss interoperability between substrate/polkadot and cosmos. Quit a few orgs involved, including interchain foundation, web3 foundation, band protocol, terra, chorus one, interlay, snowfork ... and of cause cdot is there. Plz check it out: https://hackmd.io/@substrate-ibc/SkcTfw3lD

@toliuyi Definitely Yes. It would be awesome. I have joined the Substrate IBC Working Group in Telegram last week. I would like to know how can I build Games and Apps that can be deployed seamlessly between Cosmos and Polkadot Parachains using Substrate and IBC.


Fixed a typo

"capture_propagation" member documentation description was missing the second 'p' in "propagation". Fixed this minor typo
This is for the 3.4 branch because that is where I was able to find the BakedLightmap in the beginning. I'm hoping this qualifies for the "change is only relevant for that branch" clause.

This is for the 3.4 branch because that is where I was able to find the BakedLightmap in the beginning. I'm hoping this qualifies for the "change is only relevant for that branch" clause.

The change should be made in 3.x instead of 3.4, since the change is also relevant for the upcoming 3.5.

Closing this PR and resubmitting under 3.x branch

Superseded by https://github.com/godotengine/godot/pull/56868.


First example will not build.

[grazfather ~/code/discovery/src/05-led-roulette]$ rustup default nightly
info: using existing install for 'nightly-x86_64-apple-darwin'
info: default toolchain set to 'nightly-x86_64-apple-darwin'

  nightly-x86_64-apple-darwin unchanged - rustc 1.22.0-nightly (277476c4f 2017-09-16)

[grazfather ~/code/discovery/src/05-led-roulette]$ xargo build --target thumbv7em-none-eabihf
   Compiling f3 v0.3.1
   Compiling cortex-m v0.1.6
error: `<core::cell::UnsafeCell<T>>::new` is not yet stable as a const fn
  --> /Users/grazfather/.cargo/registry/src/github.com-1ecc6299db9ec823/cortex-m-0.1.6/src/interrupt.rs:13:24
   |
13 |         Mutex { inner: UnsafeCell::new(value) }
   |                        ^^^^^^^^^^^^^^^^^^^^^^
   |
   = help: in Nightly builds, add `#![feature(const_unsafe_cell_new)]` to the crate attributes to enable

error: aborting due to previous error

error: Could not compile `cortex-m`.

To learn more, run the command again with --verbose.

@Grazfather I managed to build this example by adding #![feature(const_unsafe_cell_new)] to ~/.cargo/registry/src/github.com-1ecc6299db9ec823/cortex-m-0.1.6/src/lib.rs

Thanks for the bug report, @Grazfather.
This error has been fixed in cortex-m v0.1.7. You'll probably need to remove the Cargo.lock file, which is next to the Cargo.toml file, to make this work. cargo update should update the lockfile as well.
@ALPHA-60 You are not supposed to modify the registry that comes crates.io; it's supposed to be immutable.

Confirmed it works now :)


Fixes #592

This PR has a few style/naming changes, and adds a test and a common tool for debugging.
Looks good to me!


Update changelog for release 2.0.1

Summary Change Description
Added DataFrame changes to changelog before creating tag for release 2.0.1.
Affected Issue Numbers
None
Code Review Notes
Checklist

This might be a good opportunity to fix the missing closing div tag I noted in your previous PR.
#595 (comment)

@hepcat72 Thank you so much for your suggestions about PR 595. Sorry I didn't reply sooner, somehow I didn't get email notifications about your comments (maybe it's due to that the PR was closed before your review). I made changes to customtags.py using the 2nd set of code you suggested,  but it seems to me I still need to use mark_safe to get correct display.

@lparsons I meant to request new review from Rob, but probably sent to all of you. I know you just reviewed, please ignore my new request.


refactor(format): Bump clang-format to 14

After GitHub actions forced to run on node20 [1], and node20 depends
on GLIBC_2.28, we have to run actions on newer operation systems which
has higher builtin glibc.
Before this patch, we are using clang-format-3.9 to format C++ code,
but if we using newer OS (say Ubuntu 22.04), the clang-format-3.9 is
too old and it's difficult to install such an old version.
This patch bumps the clang-format to 14 as the code format tool, and
update relative chores, such as updating cpp_clang_format_linter
action job in .github/workflows/lint_and_test_cpp.yaml, removing
clang-format-3.9 docker images, adding more options in .clang-format
(almost all of the options are kept as old version and default values).
The main part of this patch is the C++ code updating according to the
newer clang-format, they are formated automatically.

https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

I'll fix the failed "Build Debug on CentOS 7" job in following patches.


ValueError when column_types defined in dbt_project.yaml but null/empty shows up in seed file

Describe the bug
dbt seed --full-refresh caused the issue and resulted in max() arg is an empty sequence.
Steps To Reproduce
Provide seed definitions in dbt_project.yaml with something along the lines of :
seeds:
  project_name:
    enabled: true
    schema: seeds_schema
    foo_barr_seed:
      column_types:
        column_that_breaks: varchar(128)

Then create a seed file where at least one row has an empty string "" in the column_that_breaks column.
The final line in the debug log file from dbt cloud shows that a null value isn't being handled well in Python:
max_len = max(lens) if lens else 64
Expected behavior
dbt seed should either handle null/empty values when a column_type is defined or exit with a more graceful message
Screenshots and log output
Full log attached. Screenshot of the last lines of the stack trace as well as the error below:
debug (1).log

System information
Which database are you using dbt with?

[ ] postgres
[x] redshift
[ ] bigquery
[ ] snowflake
[ ] other (specify: ____________)

The output of dbt --version:
installed version: 0.16.0
   latest version: 0.16.0

Up to date!

The operating system you're using:
macOS Catalina
10.15.3
Also fails in dbt cloud.
The output of python --version:
Python 3.7.3
Additional context
From the #support channel in the dbt slack community: https://getdbt.slack.com/archives/C2JRRQDTL/p1585243307097400
As an addition, thanks to you all for maintaining an amazing and responsive slack community. I always have confidence that I'll get help whenever I have an issue with dbt. Much love from Envoy!

triage note: we can fix this issue by just making lens a list comprehension instead of a generator expression, but this also exposes a need to unit test these conversion methods - this seems like an easy fix to inadvertently revert!

Thanks for this really thorough report @jasonwang592!
@beckjake should we sneak this in for 0.16.1 or is this an 0.17.0 fix?

@drewbanin If it's a regression, it's of the "other changes to dbt exposed an existing bad behavior" variety, because the code in question hasn't changed. The user on slack reported it in the context of "I updated to dbt 0.16.0 and ...", and it's believable that the issue was exposed by the changes to how dbt handles seeds with user-defined types in 0.16.0.
I think we should get it into 0.16.1 regardless - it seems like it's a pretty trivial fix with low/no risk.

Cool, sounds good to me, just added this to the 0.16.1 milestone - let's make it happen

Fixed in #2255


Are they idiots?  They also made a tool that anyone can use to copy anyone else.
Your argument is empty and vapid. And before you attempt to be an additional clown, I have been doing physical and VFX for 20+ years in Film and VFX, building the literal pipelines used at Nick and Disney.
Buy a mitt, catch a clue -- you are not the definer of what tools are useful nor what "artist" means. Crawl back to your cave and stay mad.

Así que, si esa es tu mayor queja, ve a gritarle al fabricante de lápices, idiota. También crearon una herramienta que cualquiera puede usar para copiar a cualquier otra persona.
Tu argumento es vacío y superficial. Y antes de que intentes hacerte el payaso más, te diré que llevo más de 20 años haciendo arte físico y efectos visuales digitales en cine y televisión, construyendo los canales literales que se utilizan en Nickelodeon y Disney.
Compra un guante, capta la idea: no eres tú quien define qué herramientas son útiles ni qué significa "artista". Vuelve a tu cueva y sigue enfadado.

Así que, si esa es tu mayor queja, ve a gritarle al fabricante de lápices, idiota. También crearon una herramienta que cualquiera puede usar para copiar a cualquier otra persona.
Tu argumento es vacío y superficial. Y antes de que intentes hacerte el payaso más, te diré que llevo más de 20 años haciendo arte físico y efectos visuales digitales en cine y televisión, construyendo los canales literales que se utilizan en Nickelodeon y Disney.
Compra un guante, capta la idea: no eres tú quien define qué herramientas son útiles ni qué significa "artista". Vuelve a tu cueva y sigue enfadado.

LOOK IN THE MIRROR.

Así que, si esa es tu mayor queja, ve a gritarle al fabricante de lápices, idiota. También crearon una herramienta que cualquiera puede usar para copiar a cualquier otra persona.
Tu argumento es vacío y superficial. Y antes de que intentes hacerte el payaso más, te diré que llevo más de 20 años haciendo arte físico y efectos visuales digitales en cine y televisión, construyendo los canales literales que se utilizan en Nickelodeon y Disney.
Compra un guante, capta la idea: no eres tú quien define qué herramientas son útiles ni qué significa "artista". Vuelve a tu cueva y sigue enfadado.

LOOK IN THE MIRROR.

Así que, si esa es tu mayor queja, ve a gritarle al fabricante de lápices, idiota. También crearon una herramienta que cualquiera puede usar para copiar a cualquier otra persona.
Tu argumento es vacío y superficial. Y antes de que intentes hacerte el payaso más, te diré que llevo más de 20 años haciendo arte físico y efectos visuales digitales en cine y televisión, construyendo los canales literales que se utilizan en Nickelodeon y Disney.
Compra un guante, capta la idea: no eres tú quien define qué herramientas son útiles ni qué significa "artista". Vuelve a tu cueva y sigue enfadado.

LOOK IN THE MIRROR.

You think we cant read what you wrote?

un verdadero artista profesional no necesita esta herramienta inútil y estúpida que solo fue hecha para plagiar y falsificar.

Says who? You? sure thing, chief. Talk about a false sense of authoirty. Get bent.

Así que, si esa es tu mayor queja, ve a gritarle al fabricante de lápices, idiota. También crearon una herramienta que cualquiera puede usar para copiar a cualquier otra persona.
Tu argumento es vacío y superficial. Y antes de que intentes hacerte el payaso más, te diré que llevará más de 20 años haciendo arte físico y efectos visuales digitales en cine y televisión, construyendo los canales literales que se utilizan en Nickelodeon y Disney.
Compra unos guantes, capta la idea: no eres tú quien define qué herramientas son útiles ni qué significa "artista". Vuelve a tu cueva y sigue enfadado.

Qué comparación más estúpida hiciste, no quiero venir aquí con una falacia de autoridad, no me importa quién seas, eso no cambiará el hecho de que esto se usará para robar y falsificar, en el futuro estoy seguro que lo veremos, ustedes solo se hacen los idiotas.

¡Pajeate! Literalmente estás publicando por aquí lo que significa ser artista.
MÍRATE AL ESPEJO.

Realmente me demuestras que tienes una pésima comprensión lectora y que tu inteligencia es bastante cuestionable con tu comparación anterior, no voy a discutir con alguien tan estúpido.

¿Eres tú, tonto?
¿Crees que no podemos leer lo que escribiste?
un verdadero artista profesional no necesita esta herramienta inútil y estúpida que solo fue hecha para plagiar y falsificar.

¿Quién lo dice? ¿Tu? Claro que sí, jefe. ¡Qué falsa sensación de autoridad! ¡Que se joda!

I won't keep wasting my time with the "Disney worker" HAHAHAHA 🤫

this is you saying 3 posts ago you were not going to argue.

Esto es lo que dijiste hace 3 publicaciones antes: no ibas a discutir.
Así de estúpido y poco comprometido eres con tu propio mensaje. Felicidades.

I'm not arguing, I'm making fun of your stupidity zzzzzz

Sure thing... stay committed to not bringing yourself down to my level -- gets better with each reply.

Así que, si esa es tu mayor queja, ve a gritarle al fabricante de lápices, idiota. También crearon una herramienta que cualquiera puede usar para copiar a cualquier otra persona.
Tu argumento es vacío y superficial. Y antes de que intentes hacerte el payaso más, te diré que llevo más de 20 años haciendo arte físico y efectos visuales digitales en cine y televisión, construyendo los canales literales que se utilizan en Nickelodeon y Disney.
Compra un guante, capta la idea: no eres tú quien define qué herramientas son útiles ni qué significa "artista". Vuelve a tu cueva y sigue enfadado.

LOOK IN THE MIRROR.

You think we cant read what you wrote?
un verdadero artista profesional no necesita esta herramienta inútil y estúpida que solo fue hecha para plagiar y falsificar.

Says who? You? sure thing, chief. Talk about a false sense of authoirty. Get bent.

Don't waste your time. The best we can do is to just let then keep talking and punching the sea.  Peace!

Oh hey, look at that, account deleted. =D

posting in ebin thread

Once again the AI Bros™ can’t justify the existence of a tool created by plagiarizing myriads of artists (yes, real artists that create art by themselves), whose only legitimate, non-contrived intent is generating forgery.

You have to draw a line somewhere between what you consider "learning" off of material (eg: transformative) and what you consider copyright infringement.
Obviously today's ML is not similar to human learning in any meaningful way, but it could probably be considered learning under a lot of meanings of the word. I think it would be a inconsistent to allow humans to learn off of copyrighted material and not allow computers.
Under some circumstances we do not in fact allow people with extensive knowledge of copyrighted codebases to write code for open source projects (see WINE developers), but I think this would not apply for a correctly trained model.
I think correctly trained models should be considered transformative, especially this model, which can't reproduce copyrighted artworks.

Obviously today's ML is not similar to human learning in any meaningful way,

Say no more, fam. It's copyright infringement for the intent to defraud people by forging AI hallucinations as real art.

Someone is using foul language under technical questions.
But I cannot say that these words are demons. Because demons are people who use foul language.
There is no doubt that this technology has brought image artificial intelligence one step closer to "becoming human". Now it is a reverse deduction, and in the future it may be possible for AI to learn the human painting process. Rather than eliminating Gaussian noise.
Someone has lost his mind. If he has so much energy to use foul language to technicians, why doesn't he resist those real scammers? This sounds like the Inquisition broke into the Wright brothers' house and said to them: "You know, flying is something controlled by God... How can you let humans fly? I can't imagine what people would do if they flew into the sky! Wright brothers, you are really demons!"
Such people have existed for a long time.
In the 19th century, spinning machines and cameras were called "demons" by them;
In the 20th century, electronic typesetting was called "demon" by them;
Now it is AI.
Why do they still dare to use github? This is a cloud platform that integrates complex science and technology. It's too dangerous! They can't imagine what these programmers dare to do! Why don't they just degenerate into slugs and find a wet crack in the rocks to crawl into!
Let's see who is going to fit in?

You think you're Prometheus.
Prometheus gave humans fire, something that can burn down cities and injure or kill people, but nonetheless has many legitimate uses, such as cooking, heating, and lighting the way in the dark or the fog. Prometheus made human life better.
This was what the Biro ball point pen was. It democratized writing and drawing to a wide demographic, making it available much more conveniently, at a much lower price. Literacy rates improved drastically once people had the power to write.

 Would Prometheus have been justified to spread this evil onto humans? Of course not. Prometheus could try to come up with ad-hoc rationalizations, like "Well maybe it can help demolish old buildings", but much better and less harmful methods already exist to demolish old buildings.
This is what this repository does. It creates nothing new except lies, fraud, and deception. You can rationalize the existence of this lying robot by imagining what a real artist could use it for, but those are just rationalizations with zero demand from any tangible person outside that hypothetical.
This AI is a solution looking for a problem. Nay, this AI is a menace looking for an excuse to exist.

Quick reminder this is for "issues". To give your opinion of how good or bad is the AI this is not the place.

Quick reminder that this is for ISSUES. To give your opinion about how good or bad is the AI this is not right place. You can go to discussions but mind that we are in a Github repo, lol.

Quick reminder that this is for ISSUES.

The existence of this entire repo is the issue.

So your master plan is just downvote everyting not aligned with your vision and continue to spam messages till you get blocked or something from this repo? That's the master plan I guess. Anyways, well... good luck on fighting also the forked repos and copies too.

Really the assholes programmers want to disguise this as a way to support artists when it will simply be used to counterfeit art, they try to absolve themselves of all blame by saying that it is not their responsibility for how people use this shitty tool that was created specifically to counterfeit
I do blame you and I hope people do too

The evaluation appears to carry a subtle undertone of stress, reflecting a result-driven utilitarian approach. The purpose of engaging in any activity should be self-fulfillment rather than concern for the residual value extracted by society on a daily basis. Those who fail to grasp this concept may not be suited for art. If one truly loves and derives pleasure from art, concerns about whether an AI has 'violated' their utilitarian mindset may become less significant.

 Would Prometheus have been justified to spread this evil onto humans? Of course not. Prometheus could try to come up with ad-hoc rationalizations, like "Well maybe it can help demolish old buildings", but much better and less harmful methods already exist to demolish old buildings.

lmao, are you Biden?
You have lost even the basic logic. Good and evil are used to define subjective things, you try to use it to define fire?
Primitive people said the same thing before they learned how to use fire.
You should just go punching the fraudsters instead of harassing the researchers.

Really the assholes programmers want to disguise this as a way to support artists when it will simply be used to counterfeit art, they try to absolve themselves of all blame by saying that it is not their responsibility for how people use this shitty tool that was created specifically to counterfeit

l was an artist before a techbro so I feel inclined to point out the free market only creates things out of demand. Regardless of the point of this project, the reason this is a problem for you is you've created an isolationist group with rules for how money moves instead of working on integrating the tools and being more productive. Complain it's not fair, I agree. Nothing about capital is fair, but as an artist, this tool doesn't hurt me at all because I didn't invest any energy into fighting the tides of change.

didnt know crying artists can create issues, But they still miss the point of the issues anyway, as expected from them
https://github.com/lllyasviel/Paints-UNDO/assets/172938297/41dd599b-4e78-4496-8eb9-4cbaa742f4c2

Yosshi999
AI bros belike "lol I can generateARTS by simply writing prompts" while tryin' hard to mimic the labor done by REAL ARTISTS doing REAL ARTS

I can tell you that prompts played a very small role in this

ghost, you shouldn't have even started this discussion. Not that I disagree with you. But these people know exactly what they're doing. They're massive trolls. But who cares? But at the end of the day, we're artists and they're not.
This feature is going to be most useful to scammers and posers. We all know it. They can spew out their word salad lame explanations and arguments but it doesn't change a thing.
Dust off your easels, your sketchbook, your paintboxes and start painting the old school way, the way that Dan Dos Santos and Carla Ortiz do. With traditional oil or acrylics or your other media of choice.  Not that I disagree with you. But these \

Ghost isn't an account. Its the account that was deleted.
Show us how we are all losers and go do a better job than the years as an artist and technical artist I have done.
Prove all us tool makers and tool users wrong who have done nothing but help you your entire life.
Dont tell, show.

Ghost isn't an account. Its the account that was deleted.

Ah, I see. I'm a newbie.

Dont tell, show.

I'm not here to convince you all of anything. You've already drunk your Kool-Aid. I was responding only to the person who started this thread. I was telling them why their protests were fruitless. I was telling them to not be fussed, because nobody can ever fake really being an artist and we all know it.
You all do whatever you're going to do. I said what I said. I'm saying it to other artists who stumble upon this discussion.
Real artists who can actually paint need to channel people like Dan Dos Santos and Carla Ortiz and get back into oils and acrylics. AI will have a lot harder time faking "work in progress" time lapses of traditional painters because the traditional WIPs are not limited to a Photoshop screen capture or whatever. AI will have to fake a person at an easel, mixing paints, the movements of the artist's hands, the different types of easels, the whole thing. Good luck with that. It's harder to scam and lie and fake when there's a physical original piece of art.

Real artists who can actually paint need to channel people like Dan Dos Santos and Carla Ortiz and get back into oils and acrylics. AI will have a lot harder time faking "work in progress" time lapses of traditional painters because the traditional WIPs are not limited to a Photoshop screen capture or whatever. AI will have to fake a person at an easel, mixing paints, the movements of the artist's hands, the different types of easels, the whole thing. Good luck with that. It's harder to scam and lie and fake when there's a physical original piece of art.

correct and I 100% agree with this.
Simple concept that a lot of "artists" cant seem to grasp.

Unless the "medium" is a computer they commission to do the art for them, lol.

What qualifies as "art" differs widely based on personal beliefs. I think in most definitions it has a significant emotional aspect to it.
Simply put, if someone perceives it as art, then it is art.

Hi all, as an action of GitHub ToS we must lock this thread.
For future comments please follow the instructions here.


request clarification: conflict with sparse fieldsets and required fields

Presently, to respect Sparse Fieldsets a server MUST NOT return fields other than those listed in the fields query param. This is at odds with the requirement that a resource object MUST contain both id and type fields.
I'm assuming that a resource requested with fields=name will still include id and type along with name.
So is the client required to always explicitly request the id and type fields (if specifying fields)? Or are id and type just assumed to be included?

Or are id and type just assumed to be included?

Yes, I think that has to be true. Thanks for picking up on this conflict. We should correct the Sparse Fieldsets section.

Yes, I think that has to be true.

I figured as much. Otherwise it would have been a rather odd requirement on the client. The example given didn't help clarify, since it explicitly requested id and type anyway.

So the server should ignore a request to include id and type, and always include them anyway? For example,
GET /articles/1?fields[articles]=id
Will return
{"data": {"type": "articles", "id": "1"}

@jfinkels I believe so. The requirement to include id and type with each resource is pretty absolute.

Should the self link always be included as well?
I think an example in this section would be very helpful.

Clarification provided via b7fe0e06c8a0e8e3fb6929470323f3cb70785c8b

Should the self link always be included as well?

The self link isn't a MUST requirement.


check dmi table may cause misjudgement

https://github.com/ShellCode33/VM-Detection/blob/4fd05cb2aa479b68529a3a7a7ea8956bd4b08c41/vmdetect/linux.go#L19-L32
DMI id may contains xen string, but I'm sure it is not a virtual machine :
root@node1:~# cat /sys/class/dmi/id/board_serial
07V122XEN6001010

Thanks for your feedback, it seems to be a tricky situation that would require some thinking.
Unfortunately I don't have time to maintain this. However I'd be more than happy to review and merge any PR you submit.

I noticed that there's many conditions to check if is running in a virtual machine, can I say remove the checkDMITable() check condition   still makes IsRunningInVirtualMachine() reliable ?
https://github.com/ShellCode33/VM-Detection/blob/4fd05cb2aa479b68529a3a7a7ea8956bd4b08c41/vmdetect/linux.go#L167-L214

Yes you can remove it on your end if you want, it will still detect most of the usual stuff. I don't want to completely remove it here though. The "real" solution might be to perform a case-sensitive comparison with Xen instead.


⚠ ClamAV has degraded performance

In 2e7616e, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 76 ms

Resolved: ClamAV performance has improved in 8d42b69.


reflect: Value.Call call on nil interface of T assignable to R

I'm investing a bug report and I traced it down to the following discrepancy, and I've convinced myself that it is a bug, but would appreciate a 2nd opinion.
Consider the following snippet:

type Iface interface {
	Method()
}

type IfaceWrapper interface {
	Iface
}

type Struct struct {
	IfaceWrapper
}

func Func(x Iface) bool {
	return true
}

func main() {
	s := Struct{}

	v1 := s.IfaceWrapper
	fmt.Println(Func(v1))

	v2 := reflect.ValueOf(s).FieldByName("IfaceWrapper")
	fmt.Println(reflect.ValueOf(Func).Call([]reflect.Value{v2})[0])
}

\cc @ianlancetaylor @mdempsky

@dsnet did you intend to close this?

Hmm yes, looks like you opened #22143 instead.


blockchain Ethereum api

is there a separate api to access the ethereum balcance or i can use the existing one?

There is no Ethereum API support yet.


Students should be allowed to register in more than one course

As @estefaniamiguel noticed, this is not working.
Solutions should go to the last registered course.

@aguspina @fedescarpa isn't this already happening? Can we close this issue?

@flbulgarelli Yes, student can be registered in many courses, and solutions
are only sent to the last one.
El dom., 21 de ago. de 2016 a la(s) 17:07, Franco Leonardo Bulgarelli <
<EMAIL_ADDRESS>escribió:

@aguspina https://github.com/aguspina @fedescarpa
https://github.com/fedescarpa isn't this already happening? Can we
close this issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mumuki/mumuki-teacher-tools/issues/136#issuecomment-241278634,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD6mDCW8flfFeaH3e1iYx6ZpMqXVVWuRks5qiLAUgaJpZM4Jlftn
.


ListView Selection mode

Hello, I was trying to implement a property that allows you to change the behavior of the selection, in two different modes when the allowMarking property is true:
MultipleSelection and SingleSlection, in the first way it should be currently working (allows you to select more than one element) in the other mode, you should allow the user selects one and only one item from the list.

Excelent, I will try it, thanks!


Does not read second dataset if "label" attribute is the same for both datasets

Expected Behavior
The graphs should reflect the different data points specified.
Current Behavior
Instead, the label attribute interferes with this, causing the same data values to be drawn twice (albeit potentially with different styling).
Possible Solution

Steps to Reproduce

Context

Environment

Chart.js version:
Browser name and version:
Link to your project:

Chart.js version and an interactive example is missing.

Tested with Chart.js v2.1.0 ... v3.0.0-alpha.2 and works in all of those versions. So the bug is somewhere else.
https://codepen.io/kurkle/pen/dyMNgXq


Environment Variables (Windows)

Can I use %HOMEPATH% in the different path options? I have pandoc, pdflatex, and an export folder in similar places on different devices, up to the %HOMEPATH%, and would like this plugin to work across these devices. However, at least with an HTML (no pandoc) export, I get (for an export location value of something like %HOMEPATH%/<location>) an error that the plugin's trying to export to C:/Users/<user>/AppData/Local/Obsidian/%HOMEPATH%/<location>. For other exports that use pandoc (and have %HOMEPATH% helping point to it), I get no response. No error of pandoc not existing, nothing.

I am still stumped by this, although I've remembered that you need to do %HOMEDRIVE%%HOMEPATH% on Windows to get the full path to ~ (C:\Users\user for example)


Set default server URL and Name before first start (set it without UI)

Hello. I need to connect to mattermost server automatically right after mattermost desktop installation on Windows.
I followed guide https://docs.mattermost.com/deploy/desktop-app.html and changed config.json as was mentioned there. But after running mattermost it prompted for url and name. Config was reset to initial state.
The question: is there any way to configure server url and name parameters at installation step? (may be pass parameters to msi to start MM with configured server and name, so user will not have to do it). Or am i doing something wrong?

If you're on Windows, you can configure a Group Policy setting as per this guide: https://docs.mattermost.com/install/desktop-msi-installer-and-group-policy-install.html

If you're on Windows, you can configure a Group Policy setting as per this guide: https://docs.mattermost.com/install/desktop-msi-installer-and-group-policy-install.html

Thank you for your answer. Is there any other way?
I need this to wrap MM msi installer in exe installer with some other installers, so that user will not have to configure anything.
Do you know, if i do something wrong with config.json? Why is it reset to default? Is there any way to set server with that config?

You can create a custom build of the Desktop App and edit the buildConfig file, that will allow teams to be automatically added.
However if you just edit the config.json file in the install directory, it should pick up those teams that you've added. If not, it's possible that the changes aren't formatted correctly and the app is rejecting them. Have a look at the logs if this is the case.

Closing as inactive, likely resolved.


PR 200 + specify bash to fix error

@rhatdan testing this fix with your PR

I took yours and found another issue and repushed.


More liberal license?

It will be wonderful, if this project will be distributed under more liberal license like MIT or BSD.

No problem

Thanks!


Use codecov.io for calculating code coverage

I have no relations with codecov.io but I think it could be useful for this project (I used it for a while for vfs-s3 and it works fine). There are a few pros for it

It looks like coverall never worked for commons-vfs

It looks like codecov more active in compare to coverall - more twitter followers, latest tweets and blog posts from May, codecov was a part of Github marketplace initial submission etc.
Don't need separated maven plugin - it supports jacoco reports and could be installed as one-liner inside travis.yaml

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@ce498a1). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #63   +/-   ##
=========================================
  Coverage          ?   60.38%
  Complexity        ?     2058
=========================================
  Files             ?      246
  Lines             ?     9264
  Branches          ?     1118
=========================================
  Hits              ?     5594
  Misses            ?     3088
  Partials          ?      582

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 ce498a1...4c3b4ee. Read the comment docs.

We already use JaCoCo and/or Cobertura for code coverage on most Apache Commons projects for sites you can generate locally and also for our own sites, I'd rather not add yet a third option. Ideally, we can standardize one one. Then more recently, some projects use Travis and Coveralls. We do have not bothered to sync up all projects on a single coverage platform.
Also the square graph above looks useless to me :-( that or my brain does not connect in that way. Look at the HTML reports below for something more useful.
Cobertura Example: https://commons.apache.org/proper/commons-io/cobertura/index.html
JaCoCo Example: https://commons.apache.org/proper/commons-lang/jacoco/index.html

It looks like a little misunderstanding about my changes - there are two components work together on code coverage. One is an agent for gathering coverage data (JaCoCo or Cobertura) and another is external service to gather historical data (Codecov or Coverall).
Cobertura is abandoned project, it doesn't support annotations and latest Java 8+ features. So I think we don't needto spend time on keeping this plugin inside pom. And JaCoCo is only one option that works fine with latest Java and has been supported by all code coverage services. I didn't put JaCoCo into  tag because I think single report doesn't make any sense and gives zero information about the project itself.
Because from my understanding the only thing that matter for code coverage is changing of coverage. And here come external services that gather historical data - Codecov and Coverall. If you are submitting huge pile of code then only changing of code coverage could say you did you spend enough efforts on writing tests or not. There is how it looks like for vfs-s3 https://codecov.io/gh/abashev/vfs-s3/commits
In first I wanted to keep Coverall and migrate vfs-s3 on it too. But it looks like coverall never worked for commons-vfs and you don't have any historical data about the coverage. Another issue is if you want to have coverall reports then need to add one more maven plugin into pom. In compare Codecov works directly with JaCoCo reports and don't need to update pom at all. And last but not least, Coverall looks neglected for me - latest tweet from 2017 https://twitter.com/CoverallsApp no any activity in issue tracker for months. And in compare Codecov is more active with more followers https://twitter.com/codecov?lang=en
You are main contributor so that is up to you - I can move JaCoCo into  and fix coverall integration but you should have in mind that there is an alternative.


deprecate xlink:href

...in some 3.x point release, in favor of plain href, and remove in v4 when Safari 9 dies off.
https://github.com/hyperapp/hyperapp/pull/211#issuecomment-313247520

it's been axed.


error: values of type 'anyopaque' must be comptime known, but operand value is runtime known

Description
const Omg = struct {
    children: std.AutoArrayHashMap(u32, u32),
};

W:\dev\definitive_dialoguer\.gyro\getty-getty-zig-github.com-8be90217\pkg\src\de.zig:188:46: error: values of type 'anyopaque' must be comptime known, but operand value is runtime known
                        free(allocator, value.*);
                                        ~~~~~^~
W:\dev\definitive_dialoguer\.gyro\getty-getty-zig-github.com-8be90217\pkg\src\de.zig:188:46: note: opaque type 'anyopaque' has undefined size
W:\dev\definitive_dialoguer\.gyro\getty-getty-zig-github.com-8be90217\pkg\src\de.zig:188:46: error: values of type 'fn(*anyopaque, usize, u29, u29, usize) error{OutOfMemory}![]u8' must be comptime known, but operand value is runtime known
                        free(allocator, value.*);
                                        ~~~~~^~
W:\dev\definitive_dialoguer\.gyro\getty-getty-zig-github.com-8be90217\pkg\src\de.zig:188:46: note: use '*const fn(*anyopaque, usize, u29, u29, usize) error{OutOfMemory}![]u8' for a function pointer type
W:\dev\definitive_dialoguer\.gyro\getty-getty-zig-github.com-8be90217\pkg\src\de.zig:188:46: error: values of type 'fn(*anyopaque, []u8, u29, usize, u29, usize) ?usize' must be comptime known, but operand value is runtime known
                        free(allocator, value.*);
                                        ~~~~~^~
W:\dev\definitive_dialoguer\.gyro\getty-getty-zig-github.com-8be90217\pkg\src\de.zig:188:46: note: use '*const fn(*anyopaque, []u8, u29, usize, u29, usize) ?usize' for a function pointer type
W:\dev\definitive_dialoguer\.gyro\getty-getty-zig-github.com-8be90217\pkg\src\de.zig:188:46: error: values of type 'fn(*anyopaque, []u8, u29, usize) void' must be comptime known, but operand value is runtime known
                        free(allocator, value.*);
                                        ~~~~~^~
W:\dev\definitive_dialoguer\.gyro\getty-getty-zig-github.com-8be90217\pkg\src\de.zig:188:46: note: use '*const fn(*anyopaque, []u8, u29, usize) void' for a function pointer type
W:\dev\definitive_dialoguer\.gyro\concepts-ibokuri-github.com-05c73681\pkg\src\lib.zig:75:21: error: concept `StringKey` was not satisfied (expected key type to be `[]const u8`)
            else => @compileError(base ++ extra),
                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
W:\dev\definitive_dialoguer\.gyro\concepts-ibokuri-github.com-05c73681\pkg\src\lib.zig:48:57: note: called from here
                for (results) |result| if (!result) fail(concept, msg);
                                                    ~~~~^~~~~~~~~~~~~~
W:\dev\definitive_dialoguer\.gyro\json-getty-zig-github.com-5753d08c\pkg\src\de\deserializer.zig:323:91: note: called from here
            comptime concepts.Concept("StringKey", "expected key type to be `[]const u8`")(.{
                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^

The deserialization block:

pub const de_AutoArrayHashMap = struct {
    pub fn is(comptime T: type) bool {
        @compileLog(@typeName(T));
        return comptime std.mem.startsWith(u8, @typeName(T), "array_hash_map");
    }

    pub const Visitor = AutoArrayHashMapVisitor;
    pub const deserialize = getty.de.blocks.HashMap.deserialize;
};

pub fn AutoArrayHashMapVisitor(comptime HashMap: type) type {
    return struct {
        const Self = @This();

        pub usingnamespace getty.de.Visitor(
            Self,
            Value,
            undefined,
            undefined,
            undefined,
            undefined,
            visitMap,
            undefined,
            undefined,
            undefined,
            undefined,
            undefined,
            undefined,
        );

        const Value = HashMap;

        fn visitMap(_: Self, allocator: ?std.mem.Allocator, comptime Deserializer: type, map: anytype) Deserializer.Error!Value {
            const K = std.meta.fieldInfo(Value.KV, .key).field_type;
            const V = std.meta.fieldInfo(Value.KV, .value).field_type;
            const unmanaged = comptime std.mem.startsWith(
                u8,
                @typeName(Value),
                "array_hash_map.ArrayHashMapUnmanaged",
            );
            @compileLog(K, V, Value, HashMap);

            var hash_map = if (unmanaged) HashMap{} else HashMap.init(allocator.?);
            errdefer getty.de.free(allocator.?, hash_map);

            while (try map.nextKey(allocator, K)) |key| {
                errdefer getty.de.free(allocator.?, key);

                const value = try map.nextValue(allocator, V);
                errdefer getty.de.free(allocator.?, value);

                try if (unmanaged) hash_map.put(allocator.?, key, value) else hash_map.put(key, value);
            }

            return hash_map;
        }
    };
}

How to Reproduce the Bug
const Omg = struct {
    children: std.AutoArrayHashMap(u32, u32),
};

_ = try json.fromSliceWith(null, Omg, file_data, model_serialization.deserialization_blocks);

Additional Context
No response

Removed label since there aren't any actual bugs afaict.
Errors

error: values of type 'anyopaque' must be comptime known, but operand value is runtime known

This error is b/c you're trying to free a std.AutoArrayHashMap with getty.de.free. However, std.AutoArrayHashMap isn't supported yet, so there's no handling logic in getty.de.free for values of that type. Thus, Getty tries to free it like a normal struct and is probably running into some weird internal pointer field in std.AutoArrayHashMap.
What you want to do (at least, until support is added) is call hash_map.deinit instead of getty.de.free.

error: concept StringKey was not satisfied (expected key type to be []const u8)

This error is b/c getty-json always returns a string from nextKey (since JSON keys are always strings), but you're passing in K at the callsite, which is an integer type.
You can fix it by passing in a string type ([]const u8) to nextKey and then turning that string into an integer afterwards with std.fmt.parseInt.

_ = try json.fromSliceWith(null, Omg, file_data, model_serialization.deserialization_blocks);

You need to pass in an allocator here btw. Otherwise you'll get a compile error later on when your visitor tries to make a std.AutoArrayHashMap.

With this code:
pub fn AutoArrayHashMapVisitor(comptime HashMap: type) type {
    return struct {
        const Self = @This();

        pub usingnamespace getty.de.Visitor(
            Self,
            Value,
            undefined,
            undefined,
            undefined,
            undefined,
            visitMap,
            undefined,
            undefined,
            undefined,
            undefined,
            undefined,
            undefined,
        );

        const Value = HashMap;

        fn visitMap(_: Self, allocator: ?std.mem.Allocator, comptime Deserializer: type, map: anytype) Deserializer.Error!Value {
            const K = std.meta.fieldInfo(Value.KV, .key).field_type;
            const V = std.meta.fieldInfo(Value.KV, .value).field_type;
            const unmanaged = comptime std.mem.startsWith(
                u8,
                @typeName(Value),
                "array_hash_map.ArrayHashMapUnmanaged",
            );
            @compileLog(K, V, Value, HashMap);

            var hash_map = if (unmanaged) HashMap{} else HashMap.init(allocator.?);
            // errdefer hash_map.deinit();
            _ = map;
            // while (try map.nextKey(allocator, K)) |key| {
            //     errdefer getty.de.free(allocator.?, key);

            //     const value = try map.nextValue(allocator, V);
            //     errdefer getty.de.free(allocator.?, value);

            //     try if (unmanaged) hash_map.put(allocator.?, key, value) else hash_map.put(key, value);
            // }

            return hash_map;
        }
    };
}

I am still getting a bunch of errors:
W:\dev\definitive_dialoguer\.gyro\getty-getty-zig-github.com-8be90217\pkg\src\de.zig:189:46: error: values of type 'anyopaque' must be comptime known, but operand value is runtime known
                        free(allocator, value.*);
                                        ~~~~~^~
W:\dev\definitive_dialoguer\.gyro\getty-getty-zig-github.com-8be90217\pkg\src\de.zig:189:46: note: opaque type 'anyopaque' has undefined size
W:\dev\definitive_dialoguer\.gyro\getty-getty-zig-github.com-8be90217\pkg\src\de.zig:189:46: error: values of type 'fn(*anyopaque, usize, u29, u29, usize) error{OutOfMemory}![]u8' must be comptime known, but operand value is runtime known
                        free(allocator, value.*);
                                        ~~~~~^~
W:\dev\definitive_dialoguer\.gyro\getty-getty-zig-github.com-8be90217\pkg\src\de.zig:189:46: note: use '*const fn(*anyopaque, usize, u29, u29, usize) error{OutOfMemory}![]u8' for a function pointer type
W:\dev\definitive_dialoguer\.gyro\getty-getty-zig-github.com-8be90217\pkg\src\de.zig:189:46: error: values of type 'fn(*anyopaque, []u8, u29, usize, u29, usize) ?usize' must be comptime known, but operand value is runtime known
                        free(allocator, value.*);
                                        ~~~~~^~
W:\dev\definitive_dialoguer\.gyro\getty-getty-zig-github.com-8be90217\pkg\src\de.zig:189:46: note: use '*const fn(*anyopaque, []u8, u29, usize, u29, usize) ?usize' for a function pointer type
W:\dev\definitive_dialoguer\.gyro\getty-getty-zig-github.com-8be90217\pkg\src\de.zig:189:46: error: values of type 'fn(*anyopaque, []u8, u29, usize) void' must be comptime known, but operand value is runtime known
                        free(allocator, value.*);
                                        ~~~~~^~
W:\dev\definitive_dialoguer\.gyro\getty-getty-zig-github.com-8be90217\pkg\src\de.zig:189:46: note: use '*const fn(*anyopaque, []u8, u29, usize) void' for a function pointer type

Compile Log Output:
@as(type, u32), @as(type, u32), @as(type, array_hash_map.ArrayHashMap(u32,u32,array_hash_map.AutoContext(u32),false)), @as(type, array_hash_map.ArrayHashMap(u32,u32,array_hash_map.AutoContext(u32),false))

Looks like the culprit is getty-json.
In json.fromDeserializer (which is called from json.fromSlice), there's an errdefer'd call to getty.de.free. The compiler evaluates this call, which means for std.AutoArrayHashMap, it'll evaluate the normal struct branch in getty.de.free, which causes the errors for the reasons I mentioned earlier.
Seems like this would happen to any non-supported type that's a struct. Not quite sure how to fix this yet...

I'd propose deinit() function in de/serialization blocks. What allocates stuff, should be able to deallocate it itself.
btw is there any trick to get a bigger stacktrace? In the case above I commented that getty.de.free call you mentioned and still am getting an error somewhere else:
W:\dev\definitive_dialoguer\.gyro\concepts-ibokuri-github.com-05c73681\pkg\src\lib.zig:75:21: error: concept `StringKey` was not satisfied (expected key type to be `[]const u8`)
            else => @compileError(base ++ extra),
                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
W:\dev\definitive_dialoguer\.gyro\concepts-ibokuri-github.com-05c73681\pkg\src\lib.zig:48:57: note: called from here
                for (results) |result| if (!result) fail(concept, msg);
                                                    ~~~~^~~~~~~~~~~~~~
W:\dev\definitive_dialoguer\.gyro\json-getty-zig-github.com-5753d08c\pkg\src\de\deserializer.zig:326:91: note: called from here
            comptime concepts.Concept("StringKey", "expected key type to be `[]const u8`")(.{
                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^

I totally don't get where that comes from. any tricks?

btw is there any trick to get a bigger stacktrace?

Not that I know of. It definitely is annoying though having such unhelpful errors.
I can't tell if it's just stage2 woes or what.

The following code now works as of https://github.com/getty-zig/getty/commit/da514225da1898a917f5d34637665e7624f0e70c:
const std = @import("std");
const getty = @import("getty");
const json = @import("json");

const json_string =
    \\{
    \\  "children": {
    \\      "1": 10,
    \\      "2": 20
    \\  }
    \\}
;

const Omg = struct {
    children: std.AutoArrayHashMap(u32, u32),
};

pub const ArrayHashMap_db = struct {
    pub fn is(comptime T: type) bool {
        return comptime std.mem.startsWith(u8, @typeName(T), "array_hash_map");
    }

    pub const deserialize = getty.de.blocks.HashMap.deserialize;

    pub fn Visitor(comptime HashMap: type) type {
        return struct {
            const Self = @This();

            pub usingnamespace getty.de.Visitor(
                Self,
                Value,
                undefined,
                undefined,
                undefined,
                undefined,
                visitMap,
                undefined,
                undefined,
                undefined,
                undefined,
                undefined,
                undefined,
            );

            const Value = HashMap;

            fn visitMap(_: Self, allocator: ?std.mem.Allocator, comptime Deserializer: type, map: anytype) Deserializer.Error!Value {
                const unmanaged = comptime std.mem.startsWith(
                    u8,
                    @typeName(Value),
                    "array_hash_map.ArrayHashMapUnmanaged",
                );
                const K = std.meta.fieldInfo(Value.KV, .key).field_type;
                const V = std.meta.fieldInfo(Value.KV, .value).field_type;

                var hash_map = if (unmanaged) HashMap{} else HashMap.init(allocator.?);
                errdefer getty.de.free(allocator.?, hash_map);

                while (try map.nextKey(allocator, []const u8)) |key| {
                    defer getty.de.free(allocator.?, key);

                    const k = try std.fmt.parseInt(K, key, 10);
                    const value = try map.nextValue(allocator, V);
                    errdefer getty.de.free(allocator.?, value);

                    try if (unmanaged) hash_map.put(allocator.?, k, value) else hash_map.put(k, value);
                }

                return hash_map;
            }
        };
    }
};

pub fn main() !void {
    var map = try json.fromSliceWith(
        std.heap.page_allocator,
        Omg,
        json_string,
        ArrayHashMap_db,
    );

    std.debug.print("{}\n", .{map.children.getEntry(1).?.value_ptr.*});
    std.debug.print("{}\n", .{map.children.getEntry(2).?.value_ptr.*});
}

It's basically the same as the code you posted in the issue but with a bit of refactoring and the changes mentioned here.


Maltrail - Combine 'General' Configuration Options To Sensor/Server

This pull request attempts to merge all 'General' configuration option to the 'Sensor' and 'Server' sections.

not going to mature, needs to much efforts from other people.


Cloudwatch alarms for evicted pods in k8s

Summary | Résumé
Adding alarms that will trigger when any of the notify apps show evicted pods.
NOTE: A manual import of the prometheus cloudwatch log group will be required for staging and prod.
Test instructions | Instructions pour tester la modification
Tested in scratch.
Unfortunately there doesn't seem to be an easy way to test this exactly. I verified that the queries return the correct data in staging on June 16th. I also tested the inverse query (kube_pod_status_reason = 0) to validate that the alarm trips.

LGTM! Is there a way to manually evict to test?

From what I've been able to see, unfortunately not in the way we need :( When a pod gets evicted by K8s, it stays showing in the namespace as status evicted, but when you manually tell k8s to evict a pod, it just deletes it...


Add FAIRs SAM as serverless AI interactor

I'm not affiliated with FAIR or Meta in any way. Just thought that including SAM as an interactor would be extremely helpful considering SAMs outstanding performance.
I just added a new interactor under serverless/pytorch/facebookresearch/
Currently this is not ready.
When trying to set a positive or negative point,  I'm getting:
Error: Request failed with status code 503. "('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))"
or
cvat Error: Request failed with status code 503. "HTTPConnectionPool(host='host.docker.internal', port=32857): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f96c8e88460>: Failed to establish a new connection: [Errno 111] Connection refused'))".
And I'm not sure why this happens.
If anyone has an idea feel free to help out. I might get back to it after the weekend maybe?
Checklist

[x] I submit my changes into the develop branch
[ ] I have added a description of my changes into the CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (see GitHub docs)
[ ] I have increased versions of npm packages if it is necessary
(cvat-canvas,
cvat-core,
cvat-data and
cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

Hi @Alx-Wo
I finished integration work in this PR #6008 keeping your commit.
Thank you for the contribution!
I will close this PR.

Awesome thanks, I just finished my changes to get it running, but you were a little bit quicker ;)


Update secret names

This was already done in https://github.com/rwx-research/upload-captain-artifact/pull/146


Add a more specialized test for squash (UI)

not a solution. only better testing for https://github.com/VirtusLab/git-machete-intellij-plugin/issues/1079

java.lang.AssertionError: expected:

Hmm okay so you've managed to repro the #1079 bug locally right?
Anyway, lemme refrain from diagnosis until is #1334 is addressed (so that there's more clarity as to what's compared to what) 🤔

java.lang.AssertionError: expected:

Hmm okay so you've managed to repro the #1079 bug locally right?
Anyway, lemme refrain from diagnosis until is #1334 is addressed (so that there's more clarity as to what's compared to what) 🤔

no no no, my question is about getCommitsUntilParent method - why does is return Develop commit (and probably a more important question, why isNonRoot got true on the develop branch)?


Add loading variable number of columns for different splits

Is your feature request related to a problem? Please describe.
The original dataset blended_skill_talk consists of different sets of columns for the different splits: (test/valid) splits have additional data column label_candidates that the (train) doesn't have.
When loading such data, an exception occurs at table.py:cast_table_to_schema, because of mismatched columns.

Hi! Indeed the column is missing, but you shouldn't get an error? Have you made some modifications to the script? I've opened a PR to add the missing columns to the loading script.


[Bug] Database is closed - Locally and in the cloud

The same exception happens in 2 environment, so I'll list them both
Local:
OrientDB Version: 3.1.0-M3 (source)
Java Version: 1.8.0_211
OS: Windows 10
Cloud:
OrientDB Version: 3.0.29 (docker)
Java Version: 1.8.0_212
OS: Debian GNU/Linux 9 (stretch)
Expected behavior
An exception not too happen ? or at least some info on why it happens and how to avoid it
Actual behavior
Every now and then an exception in the form of database is closed will be thrown. example:
com.orientechnologies.orient.core.exception.ODatabaseException: Database 'remote:localhost/mydb/mydb' is closed
	DB name="mydb"
	at com.orientechnologies.orient.core.db.document.ODatabaseDocumentAbstract.checkOpenness(ODatabaseDocumentAbstract.java:2255) ~[orientdb-core-3.1.0-M3.jar:3.1.0-M3]
	at com.orientechnologies.orient.core.db.document.ODatabaseDocumentAbstract.rollback(ODatabaseDocumentAbstract.java:2086) ~[orientdb-core-3.1.0-M3.jar:3.1.0-M3]
	at com.orientechnologies.orient.core.db.document.ODatabaseDocumentAbstract.rollback(ODatabaseDocumentAbstract.java:2081) ~[orientdb-core-3.1.0-M3.jar:3.1.0-M3]

Steps to reproduce
This seems to happen randomly
Notes

The exception happens both in the cloud and locally. Locally it's all running on my computer, so there is no network issues that can interfere
At first I thought the exception only happen when the connection hasn't been used for some time, but it seems not true;
for example, I've done 4 calls in a minute, and the fourth caused the exception.

Hi,
This seems like an instance of the database was bound to the thread local while it was closed, or that the OrientDB context was closed before the session instance spawn from it was closed.
let me know if this info helps.
Regards

@tglman I don't know, but I've been using the database on a daily basis and I haven't seen this exception since. It was probably fixed, either on your side or mine.
If it happens again I'll reopen this issue


TweenManager.frameBased not working as expected

According to the docs, the frameBased property works like this:

A frame based tween will use the physics elapsed timer when updating. This means it will retain the same consistent frame rate, regardless of the speed of the device. The duration value given should be given in frames.
If the Tween uses a time based update (which is the default) then the duration is given in milliseconds. In this situation a 2000ms tween will last exactly 2 seconds, regardless of the device and how many visual updates the tween has actually been through. For very short tweens you may wish to experiment with a frame based update instead

However, in practice it seems like the only way to have tweens running for a fixed amount of time regardless of the device speed is setting frameBased to true.
There are a couple of threads on the forms about it:
http://www.html5gamedevs.com/topic/18183-tweenmanagerframebased-not-working-as-expected/
http://www.html5gamedevs.com/topic/18242-tweens-duration-different-on-different-machines/

Confirming that I see the same erroneous behaviour: by default, a 2000ms tween does not last exactly 2 seconds; it is dependent on frame rate.
This can be demonstrated with the Phaser 'Slow Down Time' example: http://phaser.io/examples/v2/time/slow-down-time
On v2.4.1 and later, lowering the suggestedFps slider will slow down the tween motion even though it is set to complete at 500ms and frameBased is false. The motion is correct with v2.2.2 though. This is a regression defect.
Debugging the issue it appears this.game.time.elapsedMS used in TweenData#update with time based updating is providing erroneous values that ignore frame rate:
https://github.com/photonstorm/phaser/blob/v2.4.6/src/tween/TweenData.js#L363
I suggest setting game.tweens.frameBased = true. The default behaviour produces erroneous tweens.

Thank you for taking the time to open this issue. However, official support for Phaser 2 has now ended as we focus on preparing Phaser 3 for beta release. In a bid to keep the project tidy, and avoid confusion, we are closing all v2 related issues.
This does not mean your issue won't be looked-at. In November 2016 the Phaser CE (Community Edition) project began. The aim of Phaser CE was to allow the community to continue v2 development. Since then it has gained significant traction, with many updates and releases.
If you are still interested in having your issue investigated we strongly recommend testing the latest Phaser CE release. And only if the problem persists, opening an issue on the Phaser CE repo.

This issue has been mentioned on Phaser. There might be relevant details there:
https://phaser.discourse.group/t/animations-got-slower/8197/23


Add specification of default cell pin values

This adds structures for DeviceResources for the default values for cell pins that are missing or disconnected.
Previously the contract was that the synthesis tool would always give cell pins a value, but this has several problems:

existing flows aren't doing this
cells might want to be created by the PnR tool or anything else reading the interchange format
sometimes, floating is a valid default value (for example certain dedicated pins) and the existing contract didn't recognise that
setting all disconnected pins to ground is definitely not correct, vendor tools usually connect disconnected clock enables to Vcc for example.

It's a bit tricky because the same fields are also being used to encode other info like inversion, but this is how nextpnr-nexus is encoding this information at the moment:

https://github.com/YosysHQ/nextpnr/blob/2912860c9788033a7501726e77bb4962b394280d/nexus/pins.cc#L27
https://github.com/YosysHQ/nextpnr/blob/2912860c9788033a7501726e77bb4962b394280d/nexus/arch.h#L767-L814

likewise for nextpnr-xilinx:

https://github.com/daveshah1/nextpnr-xilinx/blob/d40ffba7b34d0bd6ae7d62d1bf849f8ec4d1da78/xilinx/pins.cc#L364-L626

It's a bit tricky because the same fields are also being used to encode other info like inversion

In fact, a question I have is whether it made sense to have a unified CellPin parameters field, that would comprehend inversion and defaults when the pin is left unconnected.

Yes, I think that makes sense

Updated - this is a breaking change due to some renaming, I'm not sure how best we want to handle that wrt RapidWright and python-fpga-interchange changes?

@gatecat - I need to think a bit more about this. There are a couple of potential complications around this idea. I believe (?) we made an explicit decision that the place and route tools should not be doing transforms on the netlist which this kind of looks like and we have also generally eared on the side of being more strict as well. On the flip side, describing the "default state" of things seems like a potentially good idea too....

@gatecat - Perhaps you have a broader perspective when seeing how things are handled through other architectures.  However, from my understanding unused cell pins receive a default pin mapping through the CelBelMapping construct.  Some of those defaults are dictated by the type of cell mapping used.  Broadly, I can see three levels of specifying pin defaults:

Exceptional, situation-dependent cases where a particular use of a UNISIM necessitates a particular default setting.
A broader (architecture/vendor specific) mode of defaulting pins (e.g. dangling inputs connected to GND/VCC) to avoid DRC issues.
Hardware defaults where no specification is necessary (bitstream default settings that are implicit)

As you noted, the changes will break the format.  I'm ok to accommodate breaking changes if needed, but we probably want to make it an exceptional process.  This topic, however, probably requires some more discussion before moving to that point.

To give some more context here, consider running the following Verilog through Vivado:
module top();
(* keep, dont_touch *) RAMB18E1 ram_i ();
endmodule

despite there being no ports given on the RAMB18E1, in practice Vivado will connect some ports to ground, some to Vcc, and leave others floating (I appreciate in hardware connecting to Vcc and left floating are the same, although this may not be the same for non-Xilinx devices):

There is currently no logic in Yosys to do this, so it would pass a RAMB18E1 instantiation with no ports over to nextpnr (or whatever downstream tool you are using). Essentially there are two options to fix it:

add logic and data to Yosys in order to support this
add data to the interchange format to support this, and implement the logic to fixup the ports either during place and route (as we do for pre-existing nextpnr flows at the moment), or perhaps more practically in the Yosys JSON to logical netlist importer tool.

It's notable that the interchange format already includes default values for parameters (which Yosys could also handle, and indeed has the data for already), so including the default values for ports doesn't seem such a great step. This would also be needed if cells are created at (post-)PnR time - imagine the equivalent of doing create_cell in a post-PnR Vivado design.

It's entirely possible to add this as a new field, separate from the inversion stuff as in the original version of this PR, which wouldn't be a breaking change btw - it's a question of whether we prefer a breaking change at this point, or a (possibly) slightly less neat format.

@gatecat - On the topic of breaking change verse slightly less neat format, I think we should just get into the habit of never making a breaking change if possible. We should be able to just retire the old inversion stuff and replace it with the new pin properties follow https://capnproto.org/language.html#evolving-your-protocol right?

@gatecat - Thanks for the RAMB18E1 example, I think I better understand what you are getting at.  I can see that in this case there is a lack of default information when no user connectivity information is provided.
The straight forward location (for me, at least) to add the default information would be on the CellBelPinEntry, for example:
  # Map one cell pin to one BEL pin.
  # Note: There may be more than one BEL pin mapped to one cell pin.
  struct CellBelPinEntry {
    cellPin @0 : StringIdx $stringRef();
    belPin  @1 : StringIdx $stringRef();
    # *NEW*
    default @2 : CellPinValue;
  }

  # These structures are used to define default constant values for unused
  # or missing cell pins
  enum CellPinValue {
    # leave floating
    float        @0;
    # connect to ground
    gnd          @1;
    # connect to vcc
    vcc          @2;
  }

This change would not break backwards compatibility and would provide the most relevant context to the information in my opinion.

I think CellBelPinEntry is definitely a neat place to put this; however, the disadvantage with that is in terms of the flow order it is possible that you'd want to resolve these before doing cell-bel mappings, and therefore before the bel that the cell is being mapped to is known. If we decide that resolving these while doing cell-bel mappings is fair, then that would work though.

I am in favor of making the default value property of a cell pin and having them defined for cells rather than within CellBelPinEntry. That's because default pin connections are essentially cell properties.
If we don't want a breaking change we can define another list next to CellInversions, for example DefaultCellConnections or something similar and store the default values there.

I am in favor of making the default value property of a cell pin and having them defined for cells rather than within CellBelPinEntry. That's because default pin connections are essentially cell properties.
If we don't want a breaking change we can define another list next to CellInversions, for example DefaultCellConnections or something similar and store the default values there.

Done, how does this look? This is no longer a breaking change at all either, which I think is probably better all things considered.

@gatecat Looks good to me.

The addition could use a more comprehensive comment (see the rest of the file for examples).

I've improved the comments a bit in my most recent force-push

@acomodi / @mkurc-ant  do you have permissions on this repo to merge this?

@gatecat Actually, I do not. I guess we need to wait for @mithro


refactor package pki to be unit testeable

Which issue this PR addresses:

Makes the package pki unit testeable decoupling the HTTP calls with the business logic and removes the unused "fake" unit test we are skipping in the CI. It also removes the unused state that was maintained just for the sake of the previous unit test (technically not a unit test as was touching HTPP and was flaky).
We still need to decide what needs to be tested and if the unit test that we will create is enough.
The main idea is to change from:

function which performs HTTP call + business logic
to
a public function that makes the HTTP call + another function that is unit testeable that uses the previous result.

I think caMap, mu, getCaCertPoolFromMap and setCaCertPoolInMap can be deleted.
Slack thread with context.
I have also refactored newPipeline that now calls getClientOptions which contains the logic to build the clientOptions in one function as IMHO the current usage of the initialised cp to nil is not straightforward to reason about. i,e: we are calling NewClientOptions(nil) implicitly when options == nil and issuerUrlTemplate == "" || caName == "", something that now is explicit and clear.
I have also introduced an early return in the functions to make things a bit clearer.
What this PR does / why we need it:

We need to stop having a flaky hidden integration test as part of our regular unit tests. Unit tests should never touch the external world (I/O, netowrking, etc.). This PR also removes the unnecessary global state that was created just to be used in the test of the HTTP Get calls.
Test plan for issue:

I have removed the "fake" unit test that existed in pkg/util/pki/pki.go because it was calling the HTTP endpoint and checking that the result was not nil. It was not even testing explicitly any result of business logic after performing the HTTP calls, so I think at this point it does not bring much value. On top of that, we are most of the time skipping this test in the CI (using the env var) because it is almost always failing.
One last note: I have refactored the code to be unit-testable. If we really want to test the objects without the external HTTP calls we can do that in the near future, but a different kind of test would be more valuable.
Is there any documentation that needs to be updated for this PR?

N/A

For reference: this was previously from my fork: https://github.com/Azure/ARO-RP/pull/3389

/azp run ci

/azp run ci


Using self.context.hook_data['some_key'] does not work when you are trying to diff a stack

I'm using the release-1.0 branch and a common workflow for me is to make edits to our template.yaml and the blueprints and then run 'stacker diff' to see the changes that would be emitted.
If you have a pre_build hook(specifically the aws_lambda.upload_lambda_functions hook) then it is impossible to diff a stack that reaches into the context.hook_data to retrieve the results(in this case the troposphere Code object being generated in the hook) because the hook_data object is not populated when you run the diff command.

I had not considered this case when writing the hook. They are not usually run in diff mode, and would need special support for it, to generate relevant data without actually applying any changes. Do you have any suggestions on how it should work in that case?

The way I managed to work around it for now was simply providing a mock troposphere Code object like the following in my blueprint. It still creates entries in the diff but at least that is manageable when scanning the output.
        if 'lambda' in self.context.hook_data:
            code = self.context.hook_data['lambda']['BuildsAccessLogParser']
        else:
            code = Code("JunkCode", S3Bucket="JUNK", S3Key="JUNK")

Yeah, I'm not sure there's a good way to genericize this - if the hook_data was somehow typed, we could potentially do something, but that's a bigger change.

The best I believe can be done is to let the hook signal that it knows how
to run in diff-only mode, and run it. It can't be done by default or
existing hooks may run twice.
Em dom, 29 de jan de 2017 17:12, Michael Barrett<EMAIL_ADDRESS>escreveu:

Yeah, I'm not sure there's a good way to genericize this - if the
hook_data was somehow typed, we could potentially do something, but that's
a bigger change.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/remind101/stacker/issues/296#issuecomment-275937946,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAtnToKNoU-jmYbMj_PHZeYQov83Hmwrks5rXOSEgaJpZM4LmTdU
.

@mchristen So after talking with @danielkza and others on the slack, I think the plan going forward will be to change diff so that it no longer does our own version of diffing, but instead uses CFN changesets, which would be more "complete".  We already use changesets when using --interactive in the stacker build action, so it should be easy-ish to implement.
This doesn't fix any issues we might have in stacker build --dump, namely that the hooks are actually ran whenever you run the dump (which isn't really what most people would expect is my guess).  Going to try and talk this out some more - I have, in the past, advocated for doing away with the --dump argument, but maybe it's used by too many people.
Opinions?

Sorry for the delay in getting back, I was distracted with other work and haven't had much time to look at the Lambda stuff again. I've been loosely following the discussion about pulling in blueprints via git and I think that the lambda stuff could benefit from something similar. I also hacked in some requirements.txt parsing as well to pull in the runtime dependencies and package them up with the zip file since lambda has no concept of setup.py or requirements.txt.
In general I don't need to execute the lambda hook unless code has actually changed.
Ideally, I think the lambda hook could look at the Python dependency tree of the lambda function code and not do anything unless either the lambda function code itself has changed or a dependency needs to be updated. If the hook has knowledge of the current version of the lambda function deployed and the version of the current code for the function (via. git hash or something) then it could do something different when running in 'diff' mode, like print out that the lambda hook needs to be updated and what it is going to update when executing the hook in 'build' mode.

Regarding the --dump command
I personally don't use --dump at all and prefer to manage our stack changes through the diff command.
I think my ideal workflow would be something like:

Make changes to blueprint code and/or configuration files
Inspect all the changes that CloudFormation is going to make to the templates

It would be nice if the resource lifecycle could be incorporated into this somehow. For example, some resource types force a replacement of the entire resource instead of updating the specific parameter. So sometimes what looks like a simple configuration change might in turn tear down entire resources and stacks to rebuild them completely. The only way to know is to go look up the specific properties in the CFN Documentation and try and piece together what CloudFormation will do.

Issue the build command that updates the stacks

Hah! @mchristen - re: the diff command, see my response to your other issue. I plan to change diff to use actual CFN changesets, so that should make it easier to have full confidence in it, since the changesets can tell you if there's a replacement required :)


adding sharding based on first 2 character to zagg data files

The two changes to None comparison I changed because pylint was crying about it.

:+1:


[EVENT REQUEST] - Codeunit 80 "Sales-Post" - Function PostItemTrackingForReceipt

Describe the request
Dear AL Development Team,
We would like to request the modification of a current event located in Codeunit 80 "Sales-Post" inside the function PostItemTrackingForReceipt
Old code:
                    OnPostItemTrackingForReceiptOnBeforeReturnRcptLineModify(SalesHeader, ReturnRcptLine, SalesLine);
                    ReturnRcptLine.Modify();

                    OnBeforePostItemTrackingReturnRcpt(
                      SalesInvHeader, SalesShptLine, TempTrackingSpecification, TrackingSpecificationExists,
                      SalesCrMemoHeader, ReturnRcptLine, SalesLine, QtyToBeInvoiced, QtyToBeInvoicedBase);

Requested Code:
                    IsHandled := false;
                    OnPostItemTrackingForReceiptOnBeforeReturnRcptLineModify(SalesHeader, ReturnRcptLine, SalesLine, IsHandled);

                    if not IsHandled then
                        ReturnRcptLine.Modify();

                    OnBeforePostItemTrackingReturnRcpt(
                      SalesInvHeader, SalesShptLine, TempTrackingSpecification, TrackingSpecificationExists,
                      SalesCrMemoHeader, ReturnRcptLine, SalesLine, QtyToBeInvoiced, QtyToBeInvoicedBase);

Modified Publisher:
    [IntegrationEvent(false, false)]
    local procedure OnPostItemTrackingForReceiptOnBeforeReturnRcptLineModify(SalesHeader: Record "Sales Header"; var ReturnRcptLine: Record "Return Receipt Line"; SalesLine: Record "Sales Line"; var IsHandled: Boolean)
    begin
    end;

Additional context
We need an additional IsHandled to the current event OnPostItemTrackingForReceiptOnBeforeReturnRcptLineModify inside the function PostItemTrackingForReceipt.
Thank you in advance.
Internal work item: AB#538739

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 21140.


Show how integrate the wallet selector kit in a tutorial

Guide developers to integrate to multiple wallets using the [Stellar Wallet Kit]{https://github.com/Creit-Tech/Stellar-Wallets-Kit) in our tutorial in addition to only Freighter
Background: https://docs.google.com/document/d/1zkWiCiGtLn6rCvlGI5JvulSA_1PG4KFwfqnbnIPiDTE/edit

Closing in favor of #443


Project Proposal: add secure_context_required for all HTTPS-only features to BCD

See https://github.com/mdn/browser-compat-data/issues/4696 for more details.

Thanks for filing this OWD project proposal!
It is very specific and actionable, I think. I doubt it is high priority, though.
See also the OWD prioritization criteria which guides us to make decisions.
Please complete and/or correct the following, so we can judge the priority correctly here.

Effort
In the issue the task list is about 160 interfaces affected. I believe the task is to add BCD entries to them.
There might also be also unsolved questions that lead to more work, for exmaple:

Should this be added to any/all features with the [SecureContext] flag like single methods/properties?

Dependencies
Agreement on a BCD data guideline for HTTPS only features.
Community enablement
Seems like Joe is interested in this. Unclear if that's still the case in 2022.
Momentum
https://github.com/mdn/browser-compat-data/issues/4696#issuecomment-526224085 never got an answer. I don't think there is momentum on this. Haven't seen any particular interest in this data recently (correct me if I'm wrong)
Enabling learners
Not part of any curriculum or learning pathway.
Enabling professionals
Making people aware of all the things that don't work in HTTP is useful. Not sure how much awareness around "Make sure to use HTTPS!" is still needed.
Underrepresented topics / ethical web
n/a
Operational necessities
n/a
Addressing needs of the Web industry
n/a

There is also a content part to this data. Probably need to see how to update and maintain this page going forward.
https://developer.mozilla.org/en-US/docs/Web/Security/Secure_Contexts/features_restricted_to_secure_contexts

There is now talk about metadata for MDN pages in YAML front-matter and it includes a key called "secure-context". I guess before doing this project we need clarity how both things work together, or if we even want to have both things.
(maybe compat data is only needed if the secure context requirement has been added in a later version, that is, if the feature has already been shipped without a secure context previously).
https://github.com/mdn/mdn-community/discussions/226

The information could also come directly from the IDL files as Will describes here: https://github.com/mdn/mdn-community/discussions/254
I will close this project given it is proposing a specific solution that isn't agreed on yet. It would be nice to file a new proposal that is along the lines of "How to present secure context requirement to MDN readers and MDN data consumers".


Expose html transformation API

Is your feature request related to a problem? Please describe.
I tried to make a plugin to support asciidoctor files.  In webpack this is covered by html-loader. I see that this is also happened in plugin vite:build-html
Describe the solution you'd like
Maybe you can export API used in this plugin?
Describe alternatives you've considered
Without this the only way I see is too copy a bunch of code from vite or html-loader internals

The better way is to support html as a result of transform hook (vite should transform html to js itself after that)

Hello @Djaler is this feature https://vitejs.dev/guide/api-plugin.html#transformindexhtml what you are looking for?

No. This hook allows me to add additional transformations for the entry point index.html.
I have a plugin that allows to import asciidoctor files as html. This files can contain images, videos, etc. And I want this static resources to be automatically imported to build. In webpack I can just return html string from my loader and then html-loader will do the magic. So now I just use html-loader code with some hacks https://github.com/Djaler/vite-plugin-asciidoc/blob/master/src/html/html-loader-adapter.ts

related: #2321


Chore: change underscore to lodash

Simply change the package underscore to lodash. Lodash is one of the default package which installed when initialising react native project. And it is same as underscore. This PR is cleaning the project package, the underscore page no long need be installed.

@opp100 Sorry it took me so long to get to this.  I went ahead and implemented the change myself when I consolidated the files, so I'm going to close this merge request.  If you continue to use my fork, you may find my re-implementation of the auto selection picker to be more accurate, and if ScrollViews are used in the child views, you can make sure that the views never go off screen.

Never mind bro, your change is much better than original source. I do appreciate. May I ask which branch are you working at?

@opp100 I do all of my work off the develop branch currently, not the best practice I know


Fix for cannot import name 'LlamaTokenizerFast' (#647)

It would appear that a newer version of the transformers library is required for the inference/huggingface/text-generation example. Details in Issue #647
I have also added documentation for use of this example with conda and conda-forge.

@microsoft-github-policy-service agree [company="InfinStor"]

@jagane-infinstor - please follow the CLA and we are ready to merge this.

@microsoft-github-policy-service agree company="InfinStor"


Docker build gives Illegal Instruction (Core Dump) with Latest and v2.1.1 tag

The docker build on my system is giving a "Illegal instruction (core dumped)" message upon running a docker build.
The break is at step 12 of 15 where it goes to run the mongo database, returns with a non-zero code of 132.  That said, there's some broken stuff slightly up from there (step 10/15) and down.
Step 10/15 : RUN npm install
 ---> Running in 440d3d8f2c9f
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!

><EMAIL_ADDRESS>preinstall /data/db2/node_modules/node
> node installArchSpecificPackage

+<EMAIL_ADDRESS>added 1 package in 8.252s
found 0 vulnerabilities

npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 1160 packages from 499 contributors and audited 1162 packages in 64.13s

73 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

Removing intermediate container 440d3d8f2c9f
 ---> 955b92e8d4bf
Step 11/15 : COPY --chown=mongodb:mongodb . /data/db2/
 ---> 3698a675a51d
Step 12/15 : RUN mongod --fork --logpath /var/log/mongodb.log --dbpath /data/db2   && npm run db:refresh   && mongod --dbpath /data/db2 --shutdown   && chown -R mongodb /data/db2
 ---> Running in abb8170388c2
Illegal instruction (core dumped)
The command '/bin/sh -c mongod --fork --logpath /var/log/mongodb.log --dbpath /data/db2   && npm run db:refresh   && mongod --dbpath /data/db2 --shutdown   && chown -R mongodb /data/db2' returned a non-zero code: 132

Tried this with the 'latest' checkout from the 'main' branch and a checkout of v2.1.1 tag branch.  My "mongo:latest" shows 3 weeks ago on a docker image ls.  5eAPI is working fine (built fine) but database isn't happy.
Any ideas?

This is probably from us using mongo:latest. Though, I was having trouble testing since I'm on an M1 laptop now. It looks like locking us to Mongo 6.x.x got us going again.

You guys rock, will test as soon as I get a moment.


Upsert Not working with the class cluster name in Update query

OrientDB Version: 3.1.3
Java Version:
java 13.0.2 2020-01-14
Java(TM) SE Runtime Environment (build 13.0.2+8)
Java HotSpot(TM) 64-Bit Server VM (build 13.0.2+8, mixed mode, sharing)

OS: WIndows 10
Expected behavior
Update class record query should work with UPSERT keyword and the CLUSTER name provided
Actual behavior
Not able to execute the Update query consisting of the UPSERT Keycword and  CLUSTER name

Steps to reproduce

I added one class Customer with the two properties name and customerNo
added the cluster for the class using below query
 ALTER CLASS customer ADDCLUSTER UK_Customers
given the Unique index name in the customer vertex
Executed the below UPDATE query

UPDATE customer CLUSTER:UK_Customers SET name = “David”, customerNo =“C001”
UPSERT RETURN AFTER @rid, * WHERE customerNo =“C001”

but getting this error mentioned in Actual result section
Is there any workaround for UPSERT for the queries using cluster names Or is there any syntax error in above update query with UPSERT keyword

Hi @SameerChorge94
I just pushed a fix that solves this problem, it will be released with v 3.1.13
Please consider that your SQL syntax is wrong anyway: you have to specify the class OR the cluster as target, not both: eg.
UPDATE CLUSTER:UK_Customers SET name = “David”, customerNo =“C001”
UPSERT RETURN AFTER @rid, * WHERE customerNo =“C001”

Thanks
Luigi


Check is there without dimension but having r attribute

[ ] check 100 xlsx files dimension and r mapping situation, e.g : <dimension ref="A1:D6"/>, contains E9 cell
[ ] check is there without dimension but contain r attribute situation, e.g : without dimension but contains A1-A9 r cell

Use foreach rows and each time check maxColumnIndex < currentColumnIndex then update maxColumnIndex
maybe it'll case top rows lost some column but it's better performance
e.g

Column 1
Column 2
Column 3

Text

Text
Text

Text
Text
Text

Text
Text

Text


feat: kusion watch supports networking/v1.Ingress

What type of PR is this?
/kind feature
What this PR does / why we need it:
add watch and healthcheck for ingress

Which issue(s) this PR fixes:
Part of #173

Wow, you are so outstanding, 👏