Define scripts with bin in package.json

IMO it's an anti-pattern to ask users to run something directly from node_modules.
Instead you should define a bin section in package.json.
https://docs.npmjs.com/cli/v7/configuring-npm/package-json#bin

Thanks @bartenra,
you're right, I also don't really like the node_modules solution, but haven't yet looked for a better solution.
I definitely need fix this!

Nice change!

version 2.17.1 was released a few moments ago.
You are now able to run the watcher via:
> npx typesafe-i18n

or by defining a script in your package.json file:
{
   "scripts": {
      "typesafe-i18n-watcher": "typesafe-i18n"
   }
}


Keybindings and Running Tasks

Hi there,
this tool is a game changer! Thanks so much for building open-sourcing it! I have two questions:

Can I remap a few keys? E.g., instead of using ctrl+z to move back, I'd rather use just q
I'm running quite a few scheduled tasks. Is it possible to view all running tasks in a cluster that are not associated with any service?

Hi, thank you.

e1s doesn't support custom remapping yet. I added Ctrl+Z to avoid keystroke conflicts when running it in a browser. You can use Esc instead.

Yes, you can do that with n when you are in a cluster.

Thanks!


Update docs

Edited docs for content and readability.

Coverage decreased (-0.02%) to 78.257% when pulling 91dfcb8e49ec8f1a09748d0a19ccb7e04cae3a9f on bl/docs into b98352433bb1b3bb1b6c9b57b5f5e99ebf876ebb on dev.

Coverage decreased (-0.02%) to 78.257% when pulling 91dfcb8e49ec8f1a09748d0a19ccb7e04cae3a9f on bl/docs into b98352433bb1b3bb1b6c9b57b5f5e99ebf876ebb on dev.


NTP test rewritten

Redo ntp checker and did small correction for readme file

for me it seems good, approved from my side


fixed: Add poll result message support

Pull Request Type

[ ] Feature addition
[x] Bugfix
[ ] Documentation update
[ ] Code refactor
[ ] Tests improvement
[ ] CI/CD pipeline enhancement
[ ] Other: [Replace with a description]

Description

The new poll feature results in a new EmbedType, poll_result. Missing this will lead to error to be:
ValueError: 'poll_result' is not a valid EmbedType

Changes

Add the poll_result to the EmbedType in the enum.py
Related Issues

N/A
Test Scenarios

Create a poll and end the poll.
Try to use the following code in the channel where the poll was created.
@interactions.slash_command(
    "test", description="test command", scopes=[DEV_GUILD] if DEV_GUILD else None
)
async def test_cmd(self, ctx: interactions.SlashContext):
    """Register as an extension command"""
    async for msg in ctx.channel.history(10):
        ...

It should not generate any error
Python Compatibility

[ ] I've ensured my code works on Python 3.10.x
[x] I've ensured my code works on Python 3.11.x

Checklist

[x] I've run the pre-commit code linter over all edited files
[ ] I've tested my changes on supported Python versions
[x] I've added tests for my code, if applicable
[x] I've updated / added  documentation, where applicable

This yields another message:
Class `MessageType` received an invalid and unexpected value `46`, a new enum item will be created to represent this value. Please update interactions.py or report this issue on GitHub - https://github.com/interactions-py/interactions.py/issues

I think this is the poll_result message type. However, it is not shown on the official documentation on https://discord.com/developers/docs/resources/message#message-object-message-types
Do you think I need to create a message type in the MessageType enum like POLL_RESULT for the value of 46?

We usually don't add undocumented features.

OK. I will document this into an issue. And if there is any update about this on the official documentation, we can proceed with the addition


Method translators should cache reflection objects

The following translators are not caching reflected method information:
ConvertTranslator
MathRoundTranslator
MathTruncateTranslator

Fixed in 71fe9fd2fa1081f8b66ef219a1eef93830b9cd54


Fancy Zones doesn't start

Microsoft PowerToys version
v0.60.0
Running as admin

[ ] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
Get your laptop running, then plug in an external monitor, then drag an a running application to the external monitor while holding the shift to snap it into a window. Last version and previous versions it work well.
✔ Expected Behavior
Fancy Zones start working on my external monitor as soon as I plug it in, just like previous versions
❌ Actual Behavior
Fancy Zones doesn't work unless my large external monitor is plugged in during a startup
Other Software
No response

Tried it out but couldn't reproduce it.
/bugreport

Thank you for you quick reply.
What is key for this bug at least on my system is using my laptop where I think Fancy Zones likely is loaded and use my laptop. Then turn on my X34 HP external monitor then plug the Display Port to USB-C to my USB-C port.
I have a HP Spectre X360 Convertible  15-df0xxx and a HP X34 with a Insignia Display Port to USB-C cable. HP has support in the USB-C ports to support Display Port monitors.
This problem seems to be with v0.60.0 release.
Mike's Auto Parts
Patrick M Mahoney
@.***
+1<PHONE_NUMBER> Cell
Time Zone PDT (-07:00 Hours UTC)

From: msftbot[bot] @.>
Sent: Tuesday, July 12, 2022 8:59:04 AM
To: microsoft/PowerToys @.>
Cc: Patrick M Mahoney @.>; Author @.>
Subject: Re: [microsoft/PowerToys] Fancy Zones doesn't start (Issue #19353)
Hi there!
We need a bit more information to really debug this issue. Can you add a "Report Bug" zip file here?  Then drag the zipfile from your desktop onto the GitHub comment box in this issue. Thanks!
[Report Bug]https://user-images.githubusercontent.com/11349917/133042052-4975be21-4699-4363-83c9-a8e1869d079d.png
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerToys/issues/19353#issuecomment-1181945774, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH5Q63Q4NBLFI2M6OAR2GX3VTWI4RANCNFSM53LOFFOQ.
You are receiving this because you authored the thread.Message ID: @.***>

Thanks for the info.
E-mails won't send attachments to GitHub. Please send the bug report through GitHub so we can see.
/needinfo

Look like v0.60.1 has fixed this reported issue.


Unable to run a simple project 'AccessViolationException'

I'm using Windows 10 (not using a Hololens) machine to run a small Stereokit project but I'm facing an error AccessViolationException, and also in console window I can see a XR_ERROR_FORM_FACTOR_UNAVAILABLE message. Basically, my project is a very simple one, just
    static void Main(string[] args)
    {
        //Console.WriteLine("Hello World!");
        SK.Initialize(new SKSettings { appName = "Project" });

        Model helmet = Model.FromFile("Assets/DamagedHelmet.gltf");

        while(SK.Step(() => {
            helmet.Draw(Matrix.TS(Vec3.Zero, 0.1f));
        }));
        SK.Shutdown();
    }

Does anyone know how am I able to work around about this issue?

XR_ERROR_FORM_FACTOR_UNAVAILABLE is expected if a VR headset isn't set up/active, and StereoKit is designed to fall back to a flatscreen simulator in that case. So that's not an issue in this case!
I'd probably look towards the Model instead, is the DamagedHelmet.gltf file in your project's Assets folder, and is it properly getting copied over to the final build folder? The log may also have some notes about not being able to read the file if so.

Hi!
DamagedHelmet.gltf is is being copied to binaries folder, also with
Stereokit.dll. The error occurs right on SK.Initialize, there isn't so much
information on logs as you can see below.
[image: image.png]
[image: image.png]
Em qui., 18 de nov. de 2021 às 14:11, Nick Klingensmith <
@.***> escreveu:

XR_ERROR_FORM_FACTOR_UNAVAILABLE is expected if a VR headset isn't set
up/active, and StereoKit is designed to fall back to a flatscreen simulator
in that case. So that's not an issue in this case!
I'd probably look towards the Model instead, is the DamagedHelmet.gltf
file in your project's Assets folder, and is it properly getting copied
over to the final build folder? The log may also have some notes about not
being able to read the file if so.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maluoi/StereoKit/issues/224#issuecomment-973070847,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAM4GLH6QV5HTVHJDNCPOLLUMUXVTANCNFSM5IJ2XJIQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Muilaerte Júnior

Okay, yeah! Looks like it's crashing in the system that creates the default assets. This is the first system that really starts working with graphics stuff, (it loads the default shaders and assembles some textures and meshes) so there's a good chance it's related to that.
What GPU do you have, and have you updated your graphics drivers recently? Updating graphics drivers often seems to have a pretty decent success rate for fixing graphics related bugs.

I'm using a laptop with Intel(R) HD Graphics 5500 and NVIDIA GeForce 920M.
I didn't update any graphics drivers recently and there are no graphics
drivers pending update.
Em qui., 18 de nov. de 2021 às 15:35, Nick Klingensmith <
@.***> escreveu:

Okay, yeah! Looks like it's crashing in the system that creates the
default assets. This is the first system that really starts working with
graphics stuff, (it loads the default shaders and assembles some textures
and meshes) so there's a good chance it's related to that.
What GPU do you have, and have you updated your graphics drivers recently?
Updating graphics drivers often seems to have a pretty decent success rate
for fixing graphics related bugs.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maluoi/StereoKit/issues/224#issuecomment-973147301,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAM4GLBXNCQ75RV7GODIVVLUMVBNPANCNFSM5IJ2XJIQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Muilaerte Júnior

It's possible the GPU may be a little old? I see it lists DirectX feature level 11_0 only, and it's possible that could be problematic. I don't recall which features fall into which feature level, but I am using texture layer targets in the shaders, which is definitely a more recent feature, like potentially 11_1.
Does your GPU run stuff like the Mixed Reality Portal or SteamVR?

Well, apparently not. I've just installed MRP and got stuck checking
compatibility, It's been a while since I've been waiting for the results
here hahaha.
Em qui., 18 de nov. de 2021 às 19:28, Nick Klingensmith <
@.***> escreveu:

It's possible the GPU may be a little old? I see it lists DirectX feature
level 11_0 only, and it's possible that could be problematic. I don't
recall which features fall into which feature level, but I am using texture
layer targets in the shaders, which is definitely a more recent feature,
like potentially 11_1.
Does your GPU run stuff like the Mixed Reality Portal or SteamVR?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maluoi/StereoKit/issues/224#issuecomment-973324892,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAM4GLEHPEWAGU2HATCHINLUMV4ZXANCNFSM5IJ2XJIQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Muilaerte Júnior

Ah, that's pretty unfortunate! While I'd love to support older devices, it's tough to justify time working on backwards compatibility with devices that aren't themselves VR capable. If I find an easy way to do it, then I will, but I'm pretty sure this one would require dipping into some bigger rendering architecture changes :(


asr model missing from bundle

Thanks for sharing this — I'm enjoying prodding around :)
FYI: When I run the macOS app's asr model or the or cli asr-file I see that<EMAIL_ADDRESS>is missing — and I don't think it's set up to be downloadable from hf.

Right, this is an internal model at the moment, I have to find a good way to make these only displayed when they are actually available.


Unable to install v0.32.0 (karpenter.sh/v1alpha5 api service missing)

Description
Observed Behavior:
Pod is not starting due to missing api service (v1alpha5):
$ k logs -f karpenter-7bfffc9bd6-2nllq
{"level":"DEBUG","time":"2023-10-31T13:14:04.193Z","logger":"controller","message":"loaded log configuration from file \"/etc/karpenter/logging/zap-logger-config\"","commit":"3a61217"}
{"level":"DEBUG","time":"2023-10-31T13:14:04.194Z","logger":"controller","message":"discovered karpenter version","commit":"3a61217","version":"v0.32.0"}
panic: failed to setup machine provider id indexer: failed to get API group resources: unable to retrieve the complete list of server APIs: karpenter.sh/v1alpha5: the server could not find the requested resource

goroutine 1 [running]:
github.com/samber/lo.must({0x25adc00, 0xc00017bf40}, {0xc000997730, 0x1, 0x1})
        github.com/samber/lo@v1.38.1/errors.go:51 +0x1c5
github.com/samber/lo.Must0(...)
        github.com/samber/lo@v1.38.1/errors.go:72
github.com/aws/karpenter-core/pkg/operator.NewOperator()
        github.com/aws/karpenter-core@v0.32.0/pkg/operator/operator.go:182 +0x16ce
main.main()
        github.com/aws/karpenter/cmd/controller/main.go:33 +0x25

I found that the version that is installed is v1beta1:
$ k get apiservices.apiregistration.k8s.io |grep karpenter
v1beta1.karpenter.k8s.aws              Local     True        15s
v1beta1.karpenter.sh                   Local     True        15s

Expected Behavior:
It should work. Right now pod is in the crashloop.
Reproduction Steps (Please include YAML):
helm upgrade --install karpenter ./karpenter --namespace karpenter  --set settings.clusterName=${CLUSTER_NAME}     --set serviceAccount.annotations."eks\.amazonaws\.com/role-arn"="arn:${AWS_PARTITION}:iam::${AWS_ACCOUNT_ID}:role/KarpenterControllerRole-${CLUSTER_NAME}"     --set controller.resources.requests.cpu=1     --set controller.resources.requests.memory=1Gi     --set controller.resources.limits.cpu=1     --set controller.resources.limits.memory=1Gi

Versions:

Chart Version: v0.32.0
Kubernetes Version (kubectl version): v1.24.17-eks-f8587cb

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Can you grab all the CRDs that you have installed? You should have a mix of alpha and beta APIs or the install is not going to succeed. The current v0.32.0 version expects to be able to handle a mix of the two API versions so that migration happens gracefully.
Without both of these versions, it won't start.


[IVANCHUK] [WIP] Refactor add disk type in vm_reconfigure_task in app/models.

[IVANCHUK] Refactor add disk in vm_reconfigure_task in app/models.
Added 'type' of disk and updated spec.

@miq-bot remove_label refactoring


chore: add docs about remix-dev-tools

What
This implement a small documentation about setting up Remix Development Tools in Front-Commerce
How
Add a quickstart guide

:warning: If it works already, please target main branch instead of next


Unable to sign in

Describe the bug
not able to sign-in to IBM site or access it's content. using Firefox browser. same issue on Microsoft Edge. Able to access Login page, input email, password, and verification code. Redirected to home page, but nothing shows. Shows as not signed in in the top right corner. Content on home page is loading. Not able to view any courses / catalog
Steps to reproduce
Expected behavior
being logged in and accessing catalog courses.
Suggested solutions
able to fix sign in..
Additional Information

qiskit-ibm-runtime version:
Python version:
Operating system: Windows

Hi @amdequit, please visit our support page https://docs.quantum.ibm.com/support if you are having trouble logging in.
This github repository is for the client side SDK qiskit-ibm-runtime - it's not related to https://quantum.ibm.com/


Ignore gosec false positives

gosec has started reporting a G307 linting error for code that correctly checks the return value of file.Close() within a defer statement. We'll ignore that error until it's fixed. gosec#714

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
318

Relevant Lines:
374

💛  - Coveralls


Memory use: Use ref-counted buffers for images and meshes

We currently store all incoming log messages (so we can save them as .rrd files) while also indexing and storing their contents in the data store. This basically duplicate all data.
We should make sure that big components, such as meshes and tensors, use Arc under the hood so that the log messages and the store can share the memory.
Currently we use Vec when storing the contents of an image (TensorData::U8) and a mesh (RawMesh3D).
We want to use ref-counted types like Arc or arrow2::Buffer, otherwise we duplicate our memory use.
The natural thing to use is arrow2::Buffer<u8> or Arc<[u8], but neither of those implement ArrowSerialize/ArrowDeserialize yet (see below).
See also:

https://github.com/rerun-io/rerun/pull/1372
https://github.com/DataEngineeringLabs/arrow2-convert/issues/101
https://github.com/DataEngineeringLabs/arrow2-convert/issues/102

An alternative solution is to not store LogMsges at all and instead the data store to file.

While I definitely agree with these improvements I think this issue also points to a higher level question: should we really be keeping all the incoming log messages in memory at all?
First of all we should probably make it easier to set up ways to stream messages directly to a file, both from the SDK and as it hits the viewer / server.
Still, it's very useful to be able to decide to save a recording (.rrd file) after the fact. Shouldn't we be able to to quite simply serialize and deserialize the data store to achieve the same ends?

Fixed:

We don't store data LogMsgs anymore.
TensorData, EndcodedMesh3D and RawMesh3D all use Buffers under the hood.


Better docs coming

Could you at least add a sample file of what the key+blog name file looks like?

I haven't worked on this in a couple of years, so I don't really remember how it works. 😅
Looking at the code quickly, there's a lot of stuff to tidy up now that I've learned more about making real command line projects with Go. I think how it works now is it expects a tumblr.toml file with your blog's name and API key like:
blog = "carlmjohnson"
key = "ABC123"

But honestly, it's been a long time, so I don't know if maybe the blog name is supposed to be a full URL or something.
If I ever get a free weekend, I'd like to polish this up so it's actually useable, heh. If nothing else, I need to get the rest of my old posts saved somewhere.

I rewrote the whole app. Should be easier to use now. If someone wants to make a better theme or document that part, I'd appreciate it, but I don't think I'll tackle that part.

Wow that's so impressive and not what I expected from my humble ask! Thanks a lot <3


[core] Console improvements

Since this PR is about Console and errors, I'd like to ask, whether Kyo is able to surface (instead of swallowing) the error(s) described in

https://blog.sunfishcode.online/bugs-in-hello-world/
https://github.com/sunfishcode/hello-world-vs-io-errors

?

No, we don't handle exit codes yet. Do you mind creating an issue for it?

we don't handle exit codes yet. Do you mind creating an issue for it?

Happy to help:

https://github.com/getkyo/kyo/issues/790

But the issue the blog post describes is even more about silently swallowing failures when writing to stream/pipe. So I thought it's relevant to this PR, which is changing things around Console. Does (Kyo) Console swallow errors like that? Because errors passing silently is a bad thing ™, right?


Copilot "Unable to connect"

Describe the bug

It points to the docs "for troubleshooting", but not really seeing much info there about how to figure out what's going wrong.
Seems to be the same issue as https://github.com/marimo-team/vscode-marimo/issues/43 but seemed like it belongs on this repo, since it's not related to the VSCode extension
Environment
$ marimo  env
{
"marimo": "0.9.14",
"OS": "Linux",
"OS Version": "<IP_ADDRESS>-microsoft-standard-WSL2",
"Processor": "x86_64",
"Python Version": "3.11.5",
"Binaries": {
"Browser": "--",
"Node": "v18.18.0"
},
"Dependencies": {
"click": "8.1.7",
"docutils": "0.21.2",
"itsdangerous": "2.2.0",
"jedi": "0.19.1",
"markdown": "3.6",
"narwhals": "1.10.0",
"packaging": "24.0",
"psutil": "5.9.8",
"pygments": "2.18.0",
"pymdown-extensions": "10.8.1",
"pyyaml": "6.0.1",
"ruff": "0.7.1",
"starlette": "0.37.2",
"tomlkit": "0.12.5",
"typing-extensions": "missing",
"uvicorn": "0.29.0",
"websockets": "12.0"
},
"Optional Dependencies": {}
}
Code to reproduce
No response

how are you running marimo? different port or proxy? anything in the chrome/browser network logs?

Strange, had already tried restarting server and refreshing page, but for whatever reason doing it again seemed to fix the issue: was able to get authorized

Where can I find more info about how marimo is using the copilot connection? looks like it's authorizing as the official github extension, so I'm assuming it's reverse engineered? (and has full access to my whole GH account?). Wondering whether there's a risk of getting my account flagged for using this?

@gabrielgrant we use https://github.com/jfcherng/copilot-node-server which as far as I know is also used by Sublime Text

this still exists , first time clicking on github  gives the error , but if you choose none and github again , the error goes away.
 marimo env
{
  "marimo": "0.10.7",
  "OS": "Linux",
  "OS Version": "5.14.0-503.19.1.el9_5.x86_64",
  "Processor": "",
  "Python Version": "3.12.8",
  "Binaries": {
    "Browser": "--",
    "Node": "v23.5.0"
  },
...

Here is the error message:
error logs :
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/usr/local/lib/python3.12/site-packages/starlette/applications.py", line 112, in __call__

    await self.middleware_stack(scope, receive, send)

  File "/usr/local/lib/python3.12/site-packages/starlette/middleware/errors.py", line 152, in __call__

    await self.app(scope, receive, send)

  File "/usr/local/lib/python3.12/site-packages/starlette/middleware/base.py", line 101, in __call__

    await self.app(scope, receive, send)

  File "/usr/local/lib/python3.12/site-packages/starlette/middleware/authentication.py", line 48, in __call__

    await self.app(scope, receive, send)

  File "/usr/local/lib/python3.12/site-packages/starlette/middleware/cors.py", line 77, in __call__

    await self.app(scope, receive, send)

  File "/usr/local/lib/python3.12/site-packages/marimo/_server/api/middleware.py", line 88, in __call__

    return await self.app(scope, receive, send)

           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/usr/local/lib/python3.12/site-packages/marimo/_server/api/middleware.py", line 316, in __call__

    return await self.app(scope, receive, send)

           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/usr/local/lib/python3.12/site-packages/marimo/_server/api/middleware.py", line 329, in __call__

    await self._proxy_websocket(scope, receive, send, ws_url)

  File "/usr/local/lib/python3.12/site-packages/marimo/_server/api/middleware.py", line 381, in _proxy_websocket

    async with connect(ws_url) as ws_client:

               ^^^^^^^^^^^^^^^

  File "/usr/local/lib/python3.12/site-packages/websockets/asyncio/client.py", line 485, in __aenter__

    return await self

           ^^^^^^^^^^

  File "/usr/local/lib/python3.12/site-packages/websockets/asyncio/client.py", line 442, in __await_impl__

    self.connection = await self.create_connection()

                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/usr/local/lib/python3.12/site-packages/websockets/asyncio/client.py", line 368, in create_connection

    _, connection = await loop.create_connection(factory, **kwargs)

                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1135, in create_connection

    raise OSError('Multiple exceptions: {}'.format(

OSError: Multiple exceptions: [Errno 111] Connect call failed ('::1', 2918, 0, 0), [Errno 111] Connect call failed ('<IP_ADDRESS>', 2918)

I'm running it in docker btw


Not Compatible with Restify 7.x.x

All validation rules are completely ignored using Restify 7.x.x. Rolling back to Resitfy 6.4.0 resolves the issue for me, and everything works as before.
I'm running this on Node 8.9.0

no fix?

I'm using Restify v8.3.3 and validations are ignored again.
Is this library still supported currently?
const trendingValidation = {
  queries: {
    near_lat: { isRequired: true },
    near_lng: { isRequired: true },
    since: { isRequired: true }
  }
};

router.get({ path: '/trending', version: API_VERSION, validation: trendingValidation}, getTrending);

kindly merge the code with master #85  @z0mt3c


nixos/pipewire: disable socket activation by default

Description of changes
In order to successfully connect bluetooth audio devices, pipewire must be running already which it might not when socketActivation is enabled.
-> disabling socketActivation is a better default as it provides the more stable user experience

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Another option would be enabled = config.hardware.bluetooth.enable != true;

That just sounds like a bug. I've never had that issue in my testing, and running any desktop environment will activate Pipewire anyway because it'll immediately connect to pw-pulse.


WIP: HPA container resource metrics blog

The container resource metrics is planning to get graduated to beta in v1.27. So, the feature will be available for many people by default.
It’s worth sharing this feature and the motivation for people since this feature is very important to configure safe HPAs for Pod with multiple containers.

It's the placeholder. I don't have time to write it, but will get back here by the document freeze.
ref: https://github.com/kubernetes/enhancements/issues/1610

/area blog

/sig autoscaling

/sig autoscaling

/cc @gjtempleton @mwielgus @pbetkier

Hello, Comms Lead for the 1.27 release here. This feature blog is tracked for release, the deadline for submitting the draft is on 4th of April- the sooner the better since there's still editing to be done afterwards. Any doubt, the Comms team is here to help.
Thank you!

@gjtempleton Thanks for reviews, please retake a look when have time 🙏

Hello @sanposhiho, we're doing a global reminder about submitting a draft for review for all opted-in feature blogs. If it's at all possible, it is very helpful for the release team to have drafts submitted for review before the hard deadline date, to better plan the release dates and avoid missing out. Thank you!

Thanks for addressing the feedback. Looks good to me from a technical standpoint now.
/lgtm

/assign @onlydole
For approval

@tengqm Thanks for the review. I've fixed it based on your suggestions

@tengqm I applied fix based on your suggestion 🙏

Hello, Comms Lead for v1.27 here. The publication order and date for the Feature Blog series has been finalized and the tracking board is updated.
The publication date for this article is 02-05-2023 (May 02).
Thank you!

@sanposhiho, friendly reminder for the above fixes.

Ah, sorry for unnotice. I'll give a quick fix.

A couple of things could be improved with spelling and word choice. Still, given its publication date is today, and we are already pushing other blog posts out, I'd like to approve this -- especially since it has a technical LGTM.
Reapplying @gjtempleton's tech lgtm:
/lgtm
Approving from a tech docs lens:
/approve
I'll open a PR to update the spelling and grammar shortly after approval.

/label tide/merge-method-squash


Outlets refactor in PDP [after tabs redo / AddtoCart change]

We've already put outlets in pdp but these should be reviewed and update before release, as we're stuck with them until 2.0 at least.
We can do listings later because we're adding not changing anything.

we need GH-2267 and GH-2264
tabs redo / AddtoCart cms change

PR #2683

QA Steps

Stop whatever server you are testing this on with ./spartacus.sh stop
In app.component.html add

<ng-template cxOutletRef="PDP.DESCRIPTION">

Test

</ng-template>

In app.module.ts add OutletRefModule in the imports

import {
  [...]
  OutletRefModule
} from '@spartacus/storefront';
[...]
imports: [
 [...],
 OutletRefModule
]

Restart server with ./spartacus.sh start
Go to any product's PDP page. The description should be only "Test"
Stop server, remove the changes and restart it

Tested on dev2.
After the changes, the product description is now "Test"

Before the changes:


[Task] Fix progress bar reporting

Progress bars are currently stuck at 0% until scanning is complete.

Current research points to VRC reading from UnityWebRequest.downloadedBytes rather than getprogress.  More work to follow...


Remove broken submodule

Removes the broken test-project submodule, as per discussion with @CakeVR in Discord.

Adding the conversation for the record. @CakeVR fine to merge this?

Thanks a lot!


Roll Plugins from 0283a99ce39d to 6ed6b61eeb4e (6 revisions)

https://github.com/flutter/plugins/compare/0283a99ce39d...6ed6b61eeb4e
2022-03-02<EMAIL_ADDRESS>Roll Flutter from a13f893d9fa8 to 87f5f4685c62 (3 revisions) (flutter/plugins#4981)
2022-03-02<EMAIL_ADDRESS>Roll Flutter from f8eee10f96fe to a13f893d9fa8 (1 revision) (flutter/plugins#4980)
2022-03-02<EMAIL_ADDRESS>Roll Flutter from 7372ad17f654 to f8eee10f96fe (2 revisions) (flutter/plugins#4979)
2022-03-02<EMAIL_ADDRESS>Roll Flutter from c8a930b6967e to 7372ad17f654 (2 revisions) (flutter/plugins#4978)
2022-03-02<EMAIL_ADDRESS>Roll Flutter from 03ed3c911cd1 to c8a930b6967e (1 revision) (flutter/plugins#4977)
2022-03-02<EMAIL_ADDRESS>Roll Flutter from 8f360c977a61 to 03ed3c911cd1 (2 revisions) (flutter/plugins#4976)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-plugins-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Map chart: "Uncaught TypeError: e.toFixed..." when using strings instead of numbers (2.2.0 only)

Hi ECharts team!
I'm trying the new 2.2.0 release and getting an error when using strings instead of numbers in map data, for example:
data:[
{name : 'China', value : "1359821.465"}
]
shows the Uncaught TypeError: e.toFixed in the console when hovering over China in the World Map example.
where this works fine:
data:[
{name : 'China', value : 1359821.465}
]
This leads into something like this when hovering over countries:

I guess using numbers is more appropriate but it used to work in 2.1.10 so would be nice if it's backwards compatible.
Haven't found any other issues with 2.2.0 so far which is impressive!
Anyway, thanks everyone for your hard work.

Catch you. I will fixed it.
But I don't think using string would be ok even in 2.1.10.
We have not made any convert between string and number, so it must be wrong in some case like multiple map series, the sum or the average result would be wrong.
So we recommend name should be string, value should be number just like its literal comprehension.
Thanks @jarben , see you again.

Great, thanks!


Messages not being displayed

Hello, I have just installed this extension since I'm moving from VSCode to NVim.
One of the problems I'm encountering with is that the error messages that should be displayed by line, are not being shown, even if my mouse or cursor is on the line. This only appears on this extension, but not on others.

I have no aditional configuration. Is there any more data I should provide?

@Moffinguer I'm really sorry for the late reply.
The last time I checked it was working, something might have changed on coc-nvim to make it just stop.
I'll take a look on that and fix whatever is needed.

Oh @bmeneg it's all right!, since it was my first time dealing with LSP with coc, i thought it was my fault, so i simply used a vanilla solution meanwhile.

But it's indeed not working as it should.
I may have some spare time to check it tomorrow, hopefully I can find the culprit of it, but it's, probably, outside coc-perl scope, but language server side.

Yeap, that's indeed an error on server side. The server sends two notification to the client about "syntax check": one it says there are errors, while the other notification says "things are fine". I'm not sure why, but VSCode seems to know how to handle this "difference" (stacking notifications?), while coc.nvim just overrides the first notification by the second, so depending on the order the notifications are sent, the pop-up doesn't appears.
Although I'm not sure how VSCode vs coc-nvim work behind the scenes for this case, the Perl server is broken on sending two notifications for the same "issue" and confusing things, thus I'm going to fix the server and get the same behavior in both clients (VSCode and coc-nvim).

@bukephalos just reported the exact behavior I saw during this issue investigation yesterday:

Install your most recent version. When the install was done everything looked very good. Errors were marked and the corresponding Perl error messages shown below.
Then I closed vim and opened the same file again. Now the errors were still marked but the messages are no longer shown.
After more open/close cycles or creating a new file also with a syntax error nothing is shown. Just the Perl code but no error indicator. CocInfo gives no error and lookes as if the Language Server was started/connected. But as I said, no noticable effect.
I did a reboot and was back to the second state: error indicators (two ancle brackets to the left of the lines with syntax errors) but no messages about the type of error.
I fixed one error (the file contained several syntax errors) and all error indicators disappeared. Very strange.

While testing, I also notice that VSCode is also having the very same issue, which yesterday it didn't.
Basically, this inconsistency is due to the ordering by which each notification is being sent to the client (VSCode or coc.nvim), since the original structure holding the notification is a dictionary, which isn't ordered and every for-loop on it get the notification might get things in different order. So, when the "wrong" notification is sent last, it overrides the "correct" notification with real "syntax check" problems.
I already have a possible fix for the problem on server code, I'll be posting it in a few and hopefully we can get it merged during the week.

Simple PR submitted to server: richterger/Perl-LanguageServer/pull/185.
As soon as it get fixed I'll ask the maintainer to generate a hotfix release.

Thanks for the fix. Looks better with it but it still doen't work as expected. I guess it is another problem with LanguageServer or with my understanding. Doesn't really belong here but I am not sure where else to ask (is there a Perl-LanguageServer discussion forum/mailing list or something similar?).
I have a very simple test script:
#!/usr/bin/perl

use strict;
use warnings;

$a = 112;

dosomething();

sub dosomething {
    print "foo\n";
}

It doesn't indicate the missing "my" before the variable definition. But if I remove the semicolon from the end of the definition the correct diagnostics is shown (missing simcolon and syntax error). I remember that in my tests I have seen a "global symbol..." diagnostic indicating a missing "my" but not in this little example.
Second problem/misunderstanding: I move the cursor to "dosomething()" and type "gd" to go to the sub definition but I only get the message "[coc.nvim] definition not found".
As I said, it might be a misunderstanding on my part but I am just trying to move from simple editor to IDE functionality use and see that I have a lot to learn (any idea where to get help with that?).

@bukephalos feel free to ask here :)
For the first question, related to $a assignment, no errors is indeed to correct behavior: I have no idea why Perl developers it would be a good idea, but both $a and $b are always globally declared by the interpreter to be used with the sort() function whenever a code block is passed to it like sort({$a > $b}), you basically can't lexically declare them on your package like my $a; my $b (for more info: https://perldoc.perl.org/perlvar#$a). If you change the $a to $c you're going to see the error message.
For the second question: how are you configuring coc-perl on CoC config (:CocConfig)? Is it being added within a "languageserver" object is it by its own object starting with "perl"? Do you have the following?
{
    "perl": {
        "enable": true
    }
}

How is your coc-definition (gd) defined at your vimrc/init.vim, is it like the following?
nmap <silent> gd <Plug>(coc-definition)

Thanks for your help!
$a is understood now.
This is my CocConfig:
{
      "languageserver": {
         "perl": {
          "enable": true,
          "filetypes": ["perl"]
        }
      }
  }

gives the warning/error message:
Missing property "module". (json)
once I also got this message when I opened a perl file:
[coc.nvim] Wrong configuration of LS "perl", no command or module specified.
But seems to work at least for syntax checks but still no luck with gd. My key mapping is exactly as yours and it seems to be unterstood, at least I get the message:
[coc.nvim] definition not found
which indicates it is looking for a definition.
And I get the same ("no definition found for 'dosomething'") in VScode with the same little example script I quoted yesterday.
This is why I suspect that it is a misunderstanding on my side.
Does it work for you? With the same script, same CocConfig and same key binding? Does it perhaps only work for methods and not for simple subs? A test within one of the Perl::LanguageServer source files worked (somewhat): didn't go to the definition but showed the source of the definition near my cursor. But I have no idea what conditions have to be met for this functionality to work (should it also work for variable definitions? Didn't for me)

Followed your suggestion but still the same: gd gives "[coc.nvim] definition not found"
CocConfig looks exactly like yours:
{
⚠     "perl": {
         Property perl is not allowed. (json)
      }
  }

And as you can see coc-json shows a syntax error with it. (the diagnostics hides the "enable": true which is also present)
To be sure, here it is as a complete cut and paste without the diagnostic message:
{
     "perl": {
          "enable": true
      }
}

@bukephalos, the json diagnostic about perl not being allowed is fine, it won't affect the overall functionality (although I still need to find what's causing it). But the [coc.nvim] definition not found is curious. I tested with your example and gd just worked. Would you mind opening a new bug report so we can dive into this specifically, at the same time, could you add the following configurations to your coc settings?
{
  "perl": {
    "enable": true,
    "logFile": "<any-folder>/coc-perl.log",
    "logLevel": 2
  }
}

Make sure to substitute <any-folder> by a location in your machine where you can open later.
Then once you open the Perl file with you example:

run on your neovim the command :CocOpenLog, save it to a file and paste in the issue.
open the coc-perl.log that you registered in the coc-settings.json and paste its content to https://l.perl.bot/ (click on "submit" button under the text field after you've pasted all log content, then copy and paste the URL in the new issue.

Simple PR submitted to server: https://github.com/richterger/Perl-LanguageServer/pull/185.
As soon as it get fixed I'll ask the maintainer to generate a hotfix release.

A new version of the server was released containing the fix for the issue originally pointed in this issue.
I just released v1.3.1 which include the fix. Just make sure to cpan Perl::LanguageServer to update the server in your local machine.


Pin open component md-sidenav

Hello, is it possible to pin open an md-sidenav and remove the backdrop ?

https://github.com/angular/material2/tree/master/src/lib/sidenav#bound-properties


Fixed a bug with read feed with partition key.

Pull Request Template
Description
Read feed with partition key has bug that causes it to go down the wrong pipeline which adds additional values which are not compatible with partition key. I updated the logic and added tests.
Type of change
Please delete options that are not relevant.

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

Closing issues
Put closes #610

ChangeLog missing


thak you for the time anjd atention, i did the configuration of firebase.js. the error appeared in the line 111 of the src/App.js

thak you for the time anjd atention, i did the configuration of firebase.js. the error appeared in the line 111 of the src/App.js
Originally posted by @caiobraga in https://github.com/aladinyo/WhatsappyApp/issues/4#issuecomment-828446119

thak you for the time anjd atention, i did the configuration of firebase.js. the error appeared in the line 111 of the src/App.js
Originally posted by @caiobraga in #4 (comment)


[gvar] lazy loading

We're probably not going to fix this, but I noticed that unlike glyf table which loads individual glyphs lazily, gvar table loads all glyphs. So when creating eg. a glyphSet for a font, if the glyphset is variable (as in PR https://github.com/fonttools/fonttools/pull/2738) then there's significant delay loading the gvar table.
Ideally gvar should also lazily load per glyph variations like glyf table works.

I've noticed that, too, and I think we should fix it. At some point I tried to see how it could be done, and I vaguely remember seeing that it should be quite doable. I may have another look.


For review

Add To-Do List files for Peer Feedback 🙌

Peer Code Review
Hi @ritikarawat220,
Status: Approved 💯 👍
Highlights

[x] Followed JavaScript Best Practices
[x] Followed [DRY, KISS, and YAGNI] rules
[x] Applied HTML and CSS Best practices
[x] No linters

Good job implementing the requirements 👍 Your project is complete! There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
Congratulations! 🎉
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag @sawmon71293 in your question so I can receive the notification.

@sawmon71293


Question - Module error when building on Travis CI

Hello,
I am running into a Module parse failed error when trying to deploy the application using Travis CI. All my builds were working fine till yesterday and started failing from today.
I am able to run the application fine from my local but its erroring out on Travis. I did check with the Travis team to make sure they have not made any updates which causes this error and they did not make any updates.
PFA a screenshot of the build error from Travis CI

Node Version is 8.17.0 and npm version is 6.13.4
Any help is appreciated. Thanks!

Hi - sorry about this, this is a known issue in the sub-dependency, react-draggable: https://github.com/STRML/react-draggable/issues/479
It is fixed in the latest release, 4.4.1. An easy way to upgrade is to simply remove react-resizable from your project, and re-add it.


Feature Request: Multiple Repository View

Have an overall view (a dashboard, if you will) that shows all open issues across all repositories.

Or, at least at the organization level for GH organizations.


A request/help for workspace switching

it would be really cool , if u could have the previous workspace fade out into the next one

That sounds feasible.
I will see if I can get some time to fulfill your request

mark all windows o the current workspace with fade
fade out all widows with fade
make all windows in new workspace invisible and mark with fade
switch to new workspace
fade in all marked windows

sounds like it will work
Thanks : )

https://github.com/user18130814200115-2/swayscrips/tree/main/workspacefade
Is now up, enjoy and feel free to report if you have any issues with it.


Updating NearlyFreeSpeech.NET host details

Added links to PHPInfo pages and updated version numbers.

Thank you!


Example ?

I can manage to test it can you redirect me to an example ?

@parweb Thanks for the interest in the project. However, the documentation is still a work in progress and I do not have any examples.


how to cancel textarea auto focus?

Fixed in https://github.com/antoine92190/vue-advanced-chat/commit/468a2263e9b90706af8ca64331b60b67b6b0381a

can fixed in next branch? I use in vue3, thanks.

Done


[PACKAGE] move version number to a file

Isolate the package version a single file. Similar to: https://github.com/allenai/allennlp/blob/master/allennlp/version.py

closed in favour of #93


chore(main): release 2.9.2

:robot: I have created a release beep boop
2.9.2 (2024-03-06)
Bug Fixes

kib release (#1032) (bcec706)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/mesosphere/konvoy-image-builder/releases/tag/v2.9.2 :sunflower:


Error 61 : API access denied

I received a confirmation for inscription without api_key
so I try with confirmation_key ( at the end of confirmation link)
I have this pretty message : Error 61 : API access denied !
any idea about it ?

Hi,
you can ask your apikey to<EMAIL_ADDRESS>stating your username;


[Enhancement] support bitmap hll percentile type for mv

What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #14223
Problem Summary(Required) ：

support bitmap hll percentile type for mv
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 2.5
[x] 2.4
[ ] 2.3
[ ] 2.2

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

run starrocks_admit_test

run starrocks_fe_unittest

run starrocks_admit_test

run starrocks_admit_test

run starrocks_fe_unittest

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

@Mergifyio backport branch-2.5 branch-2.4

fix https://github.com/StarRocks/starrocks/issues/14223


Dynamo transport nodes not working on receive

It seems like the logic to handle transports other than Server is missing in the receive node.
Ref: https://speckle.community/t/dynamo-transport-nodes/2816/4

This is what I'm getting on Safari. Not sure what to make of it yet

Closing as stale.


GetAccountsAsync

Hi
I would like to work aslo with private fuctions that are provided by GDAX
I see that it is not implemented in your library... Have you had some problems during implementation of its ??
I created  one base on your fuctions(see code bellow) .. but I still return error 400 as HTML response... (your fuctions are working for me OK..)
Could you help me ?
Thanks

    public static async Task<Accounts> GetAccountsAsync(string id)
    {
        string ts = GetNonce();
        string method = "/accounts";
        string str_GDAX_Main = "https://api.gdax.com";
        string sig = GetSignature(ts, "GET", method, string.Empty);
        Accounts myprodticker = new Accounts();
        using (var client = new HttpClient())
        {
            client.BaseAddress = new Uri(str_GDAX_Main);
            client.DefaultRequestHeaders.Accept.Clear();
            client.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));
            client.DefaultRequestHeaders.Add("CB-ACCESS-KEY", config_API_Key);
            client.DefaultRequestHeaders.Add("CB-ACCESS-SIGN", sig);
            client.DefaultRequestHeaders.Add("CB-ACCESS-TIMESTAMP", ts);
            client.DefaultRequestHeaders.Add("CB-ACCESS-PASSPHRASE", config_API_Passphrase);
            client.DefaultRequestHeaders.Add("User-Agent", UserAgent);
            HttpResponseMessage response = client.GetAsync(method).Result;
            response.EnsureSuccessStatusCode();

            string json = await response.Content.ReadAsStringAsync();
            myprodticker = JsonConvert.DeserializeObject<Accounts>(json);
        }
        return myprodticker;
    }

Sorry for taking so long to get back to you. Life has been crazy. I'm not getting an http 400 back from the web call. Did you create API credentials and put them in your copy of APIData.xml?
Other than that, the Accounts endpoint is going to return a list of accounts, which can't be parsed directly into an Accounts object. You'll need to change your last line to  myprodticker.account_list = JsonConvert.DeserializeObject<List>(json);
I've added a version of your routine for getting all accounts in my working copy and I'll get that uploaded.


NIST Key Wrap Lab

reverting accidental merge

Some thoughts on where I left off:
The types and variables don't populate after I load the literate markdown document. This may be user error, but I had to correct some typos, so I know it's parsing something

The Answers document could probably stand to be cleaned up, further comments added

I found some additional test vectors from NIST... these found some additional bugs with small plain text sizes in the cryptol implementations... but the lab still flows as is

There is one more algorithm KWP which has some heavy type constraints and would probably make a good lab on its own. There's a good start for the implementation in this branch.

The Triple-DES module throws a warning which could probably be corrected and I think we need to implement the blockDecrypt function there as well. I've made a first attempt at correcting this.

Looking good. I'm going to put a string bid in, though, that the KWP material be its own lab... I think there are important technical pieces to focus on there. Furthermore, the TKW algorithms are a very natural and relatively straightforward thing to implement after seeing KW. KWP in between may be a distraction.
I would be more confident in KWP on its own if we had some more material to discuss. Going over the mod-ceil operator would be good. Maybe we can think of a natural candidate algorithm where padding is important as an example...

the TKW algorithms are a very natural and relatively straightforward thing to implement after seeing KW. KWP in between may be a distraction.

Yeah, it's too bad KWP comes in between them in the document. I'll smush them back together and place KWP down below. I'm going to take a stab at KWP and see how it goes...if it's too complex I'll make a new lab, but I want to try first.
The way they describe padLen really bugs me ---

That's really the number of "octets", and if they're willing to use ceiling division, why not just use ceiling mod and make the whole thing much simpler!

So.... I've not seen ceiling mod before. And my quick glance through
"Programming Cryptol" didn't reveal a clean definition.
Definitely unpack that here -- maybe all of the type operators too, because
that's a strange concept for many coming to this language. I STILL want to
use width where I shouldn't sometimes.
On Fri, Jun 19, 2020, 9:31 AM weaversa<EMAIL_ADDRESS>wrote:

the TKW algorithms are a very natural and relatively straightforward thing
to implement after seeing KW. KWP in between may be a distraction.
Yeah, it's too bad KWP comes in between them in the document. I'll smush
them back together and place KWP down below. I'm going to take a stab at
KWP and see how it goes...if it's too complex I'll make a new lab, but I
want to try first.
The way they describe padLen really bugs me ---
[image: image]
https://user-images.githubusercontent.com/7407930/85137565-67908700-b20f-11ea-9f28-814203b62aa4.png
That's really the number of "octets", and if they're willing to use
ceiling division, why not just use ceiling mod and make the whole thing
much simpler!
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/weaversa/cryptol-course/pull/39#issuecomment-646637046,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANWESPW6DPD4P2YQAIRQO4TRXNSBRANCNFSM4N5TM63A
.

P is defined to be some number of octets, so taking the floor here "[]" is useless notation ---

I'm also bugged by their rational for upper limits in A.4

if S is extremely long, about 2^67 semiblocks...it is likely that [there are collisions in W].

First off, W can't take 2^67 semiblocks as input because t is only a 64-bit value and t ranges from t = 1, ..., 6*(n-1)), where n is the number of semiblocks. If 6*(n-1) is >= 2^^64, t doesn't fit in a 64-bit number --- W isn't defined for n greater than 2^60 (roughly).
Of course, Cryptol's type checker immediately demands that 64 >= width (6*(n-1)), which seems to me to be a better bound than the somewhat arbitrary 2^54 chosen in the document.

Oh man this is a lot of work. I really hope someone appreciates what we're doing...

It seems like KWP really should operate on semiblocks, rather than a giant bitvector (which we give as type [l]). I think it really should be [l/64][64] and then the constraints from Table 1 can be applied, which is 1 < l/64, l/64 <= 2^^29. Though, I think these are implicit because k already has the octet constraints from Table 1. Also, the constraints on n could probably be lowered, I'm not even sure they matter...
Woh...I was able to remove the constraints on n (which, after writing the sentences above, makes perfect sense).

I think the KWP Ciphertext column of Table 1 in the NIST spec is off by one.
:t KWPAE`{k = 2^^32 - 1, l = 64 * (2^^29 + 1)}
KWPAE`{k = 2 ^^ 32 - 1,
       l = 64 *
           (2 ^^ 29 +
            1)} : ([128] -> [128]) -> [4294967295][8] -> [34359738432]

Here we find that, for KWP if the number of octets of P is the upper limit (2^^32-1), the number of semiblocks of C is actually 2^^29+1, where the table says it should only be 2^^29.

I think the KWP Ciphertext column of Table 1 in the NIST spec is off by one.
:t KWPAE`{k = 2^^32 - 1, l = 64 * (2^^29 + 1)}
KWPAE`{k = 2 ^^ 32 - 1,
       l = 64 *
           (2 ^^ 29 +
            1)} : ([128] -> [128]) -> [4294967295][8] -> [34359738432]

Here we find that, for KWP if the number of octets of P is the upper limit (2^^32-1), the number of semiblocks of C is actually 2^^29+1, where the table says it should only be 2^^29.

I wrote this up as part of the lab. It is just too compelling to let disappear.


Ignore coverage folders during hygiene

Only really matters for local runs, but the stuff in these shouldn't be ran through the check.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.005%) to 42.096%

Totals

Change from base Build<PHONE_NUMBER>:
0.005%

Covered Lines:
27899

Relevant Lines:
61992

💛  - Coveralls


could not pass array through bash as an inline parameter

Following the format of exampleArray showed in this document, and using a windows command line terminal, I got this response:
' was unexpected at this time.
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f0aca150-4747-7670-f465-7439aecc40e5
Version Independent ID: f836844c-0089-1477-57af-43a76181e5d6
Content: Deploy resources with Azure CLI and template - Azure Resource Manager
Content Source: articles/azure-resource-manager/templates/deploy-cli.md
Service: azure-resource-manager
Sub-service: templates
GitHub Login: @mumian
Microsoft Alias: jgao

@masonwolf Thanks for your query, we will further look into it and get back to you at the earliest.

@masonwolf - did you use:
exampleArray='("value1", "value2")'
or:
exampleArray="['value1','value2']"

@masonwolf - I double-checked the syntax. For Windows Command Prompt or PowerShell, this syntax works:
--parameters parameter1="['value1','value2']"
For Bash, this syntax works:
--parameters parameter1='("value1", "value2")'
We'll close this item, but feel free to reopen if that is not working for you.

#please-close


Drop strong naming

I've been thinking about dropping strong naming from some of the OSS projects I've got. I've gone back and forth with the idea with urges to drop it and have then reconsidered to keep it because of the poor souls who HAVE to strong name their projects because some guy higher up the rank thinks it must be done.
Jeremy Miller's post did it for me. So I'm going to draw the line today. No more strong naming for vNexts of my OSS. If someone thinks this or other libraries are useful they will either have to use the older versions or drop their SN.

While I agree wholeheartedly with dropping strong-naming, I will join the club of getting a crapload of pushback on my other projects where I tried that. Aside from being a breaking change, it does penalize people who don't have much, if any, control over it. Plus, there are some users (like VS Addins) that require strong naming.
The best compromise I've seen is the whole "OSS Signing" strategy, which just includes checking the key in. No lock-in (no security loss because there was never any).

I completely agree with you.
On 25 Oct 2015 4:49 am, "Oren Novotny"<EMAIL_ADDRESS>wrote:

While I agree wholeheartedly with dropping strong-naming, I will join the
club of getting a crapload of pushback on my other projects where I tried
that. Aside from being a breaking change, it does penalize people who don't
have much, if any, control over it. Plus, there are some users (like VS
Addins) that require strong naming.
The best compromise I've seen is the whole "OSS Signing" strategy, which
just includes checking the key in. No lock-in (no security loss because
there was never any).
—
Reply to this email directly or view it on GitHub
https://github.com/MehdiK/Humanizer/issues/253#issuecomment-150840678.

I'll close this out then there's nothing further to do on this for v2.

Re-opening this as @dsplaisted just released a tool to help people who do need strong named libraries use non-strong-named ones: https://github.com/dsplaisted/strongnamer
Is it acceptable to just tell the people that do need a strong name to install that StrongNamer package and have things "just work" for them?

My advice would be to wait a while to see how well StrongNamer solves the issue.  I think it will work well but I hacked it together in two days for my presentation at .NET Unboxed, so it's still super new and untested. :-)

Closing as it seems no one is interested in "fixing" this issue. my rationale is "do not break things": having Humanizer signed does not harm anyone (apart a few of anti-SN activists).


Seeking new ownership!

Would anyone like to take over ownership of this project? I have moved on from .net and do not intend to maintain this library. If you're interested, please respond to this issue.

Hello,
I would be interested in mantaining this project. Please feel free to reach out to me.

Thanks! Please reach out if I can do anything!


Cannot discern which stock the bar update is for with stream API

Description
When I subscribe to the "bars" updates for a set of stocks, I want to be able to listen to updates with stream.on("bar", (bar) => {}); but the issue is that the Bar type does not contain any information about which stock this bar is for. So when I listen for bar updates I have no idea which stock these updates are for.
In the alpaca documentation however, it seems to say that the JSON returned for Bar objects contains a property S which is the symbol name.

Yeah it appears they did not have that field at the time of initial beta release. I've added it in the latest version and tested locally to confirm.


error in the build of the front end

In attempting to build the front end, I have run into issues with
npm install
npm run build:prod
After further inspection, it was because I ran a cmd versus a node cmd window.  Consider clarifying the instructions.

It is noted in the README that you must have Node.js installed for this demo to work.  Do you mean to say that npm wasn't on your PATH and that's why it didn't work?  I build the demo from a regular cmd and have never had any issues, but I also have npm on my PATH variable.


Parse bech32 and hex npubs

requested by @futurepaul

looks like this is still returning the hex version for contacts?

Oh will add that

@futurepaul added

sry still seems to be returning the hexpub

Okay think i fixed it


Building Docker containers w/pyinfra

Target a base image
Use docker run to collect facts
Command output to Dockerfile and filesystem (temp dir w/generated templates/etc?)
Run docker build in the temp dir

Closed as of v0.9!
Can't make dockerfiles/templates currently - but will build containers :)


Tdr 2760 delete empty properties

I was thinking shouldn't we handle the delete part on the client side?
@vimleshtna considered doing this as well. My feeling is this should be down to the API, to ensure the DB doesn't get into an invalid state. The API shouldn't rely on any clients using it correctly. Whilst at the moment the risk is lower, the more properties/dependencies added in, the more likely a client is going to misuse the API and put invalid data into the DB.

I was thinking shouldn't we handle the delete part on the client side?

@vimleshtna considered doing this as well. My feeling is this should be down to the API, to ensure the DB doesn't get into an invalid state. The API shouldn't rely on any clients using it correctly. Whilst at the moment the risk is lower, the more properties/dependencies added in, the more likely a client is going to misuse the API and put invalid data into the DB.

@TomJKing Yeah, you are right. I think we should change the endpoint updateBulkFileMetadata to updateOrDeleteBulkFileMetadata or throw an exception if the user passes an empty value which will ensure that the user has to pass the correct value if he is calling an update API.

I think we should change the endpoint updateBulkFileMetadata to updateOrDeleteBulkFileMetadata or throw an exception if the user passes an empty value
@vimleshtna good point, I've changed the endpoint to throw an exception if an empty property value is passed in. That should prevent misuse by any clients.


Need help

Need help
Originally posted by @itsanpachsys in https://github.com/amzn/distance-assistant/issues/2#issuecomment-651947636

Hello, could you please describe a full description of the issue you are experiencing?
Thank you


Increase / decrease font size with CMD-+ like VSCode

Is your feature request related to a problem? Please describe.
I'd like to increase and decrease font size with CMD+ and decrease with CMD- like VSCode.

Duplicate of https://github.com/lapce/lapce/issues/785


ci: push image on tag starting with v

I tried to make a v0.1.0 tag but it didn't push the image to dockerhub, this should fix that.

ship it! 🚀


Added state module and corresponding unit tests for vmc network

Added state module and corresponding unit tests for vmc_network

A minor change, as well as integration tests are still needed here

To keep the review small, I have planned to create separate PR for integration tests

updated code as per the given suggestion and also added integration tests


Jar not starting

Hi,
I downloaded the jar to play, unfortunaly the jar will not open despite java 8 is installed, there is not implication why.
Thanks!

I just tried it myself with Windows 10 and Java 8 Update 191 and JSkat is starting as expected. Do you have the latest Java version installed?
You can find out with this command:
java -version

I actually did not, but instead I had Java 8 Update 192 installed. Following your advice, I deinstalled Update 192 and installed 191, unfortunaly without a positive result. Weirdly, all my other .jar applications are running just fine, only JSkat does not even show any error or notification.

Hmm, it's hard to guess what's going wrong without having any error message. I could think of some incompatibility with your graphics driver and JavaFX that I don't have in my virtualized Windows 10 here.
You could try out whether the non-JavaFX version 0.15 of JSkat is running to prove that assumption:
https://github.com/b0n541/jskat-multimodule/releases/download/v0.15.0/JSkat-0.15.0.jar
I'm currently working on making JSkat compatible with Java 11. You can checkout the latest state from the develop branch and do
gradlew.bat run
in the directory you've checked out.

Hi, I don't know whether the problem still exists for Jokah16.
I've tested the snapshot with a Win10 machine, java version "12.0.2" 2019-07-16, while starting it from a Git Bash and I was able to play on a local table.

There where just some warnings (ReflectionsExceptions), e.g.:

could not get type for name org.codehaus.groovy.runtime.GeneratedClosure
could not get type for name com.google.gson.JsonDeserializer

and the like.

Since version 0.17 JSkat requires at least Java 11 and is shipped with JavaFX included. So this bug might not occur anymore.


Feature Request: Add Login and Registration Page with Blurred Background Effect

I'd like to suggest adding a login and registration functionality to the project with a modern design. The idea is to have a modal popup for login/registration when a user clicks the "Login" or "Register" button. The popup should appear on the same page with a smooth animation, and the background should blur, providing a clean, user-friendly experience similar to many trendy designs.
Attaching the reference!

@anuragverma108, please assign me this issue under Hacktoberfest 2024. I'm open to any suggestions or feedback you may have!

Thanks for creating the issue in WildGuard! The issue has been assigned to you.
Before you start working on your PR, please make sure to:

⭐ Star the repository if you haven't already.
Pull the latest changes to avoid any merge conflicts.
Attach before & after screenshots in your PR for clarity.
Include the issue number in your PR description for better tracking.

Don't forget to follow @anuragverma108 – Project Admin & @PriyaGhosal-Project Collaborator  – for more updates!
We're excited to see your contribution as part of Hacktoberfest 2024! 🎉
Happy open-source contributing!


[DependencyScan] Prevent command-line flags added again on re-scan

Add a flag finalized to indicate that a module entry in the dependency cache is finalized and no longer needs to be updated. This prevents the command-line flags from dependency inputs get added multiple times on re-scan with the same service.
While during normal compilation, adding the same command-line flags multiple times are fine, it is bad for caching builds as a new compilation cache key needs to be computed every time.

@swift-ci please smoke test

ping! swift-driver patch is depending on this to pass the tests.


Unbreak gofmt

Jenkins build failed due to another occurrence of #622.

LIke #619, Coveralls ran under Jenkins and passed (https://coveralls.io/jobs/29666984), but github isn't seeing the update.

Again coveralls is stuck. It did run and was successful: https://coveralls.io/jobs/29666984.
Merging.


Progress component ignores className prop when bar prop is specified

In the following example:
<Progress multi className="class-a">
    <Progress bar value={25} className="class-b" />
    <Progress bar value={25} className="class-c" />
</Progress>

class-a is added to the outer div, but class-b and class-c are not added to bar divs.

This the same for single as well.
For instance:
<Progress value="75" className="class-b" />
// makes:

None of the .progress-bar elements can have custom classes at this point; multi or not.


Notification socket gets broken pipe when behind a firewall

This happens because it is not possible to manually send "keepalive" packets in this notification socket.
Then the firewall will tear down the connection after a set inactivity timeout.
I Really do not know exactly where this ticket belongs, as zinolib 0.9 do not have a form of keepalive.. but curitz have created a keepalive by asking for ticket 0 every once in a while.
There should be implemented a way to ensure that the notification socket will not break. it might be that this should be fixed in the zino server directly or some way in the client but i'm creating the ticket here for reference.

It looks like this pr will fix the issue reported. looking at the firewall logs sessions are no longer decreasing its timeout into a "nonsafe" area where sessions are cleared on the firewall. i've for now only tested this for the ntie session, will test for both sessions


Fourth and final PR to address #491

On this PR, we finally introduce the concept of "policy engine" in its complete form. Please refer to the item 3 of #491 for the details.
Signed-off-by: Mike Spreitzer<EMAIL_ADDRESS>

@maugustosilva one more thing that would be helpful: I know we've talked about having full documentation for this feature, which will come in later, but can we have a short documented way to use this (besides just the accept-all policy)? The tests options are quite extensive, so seeing this in action, even in a small way, would make it easier to visualize.

@maugustosilva one more thing that would be helpful: I know we've talked about having full documentation for this feature, which will come in later, but can we have a short documented way to use this (besides just the accept-all policy)? The tests options are quite extensive, so seeing this in action, even in a small way, would make it easier to visualize.

I have opened a PR with an initial draft of the full documentation on keylime-docs repository.


Avg Disk IO wait time has no datapoints

See attached image.

Just remove it from the dashboard.
This metric is no more collected.


i18n: Updates for missing translations for Ukrainian and Russian. Also, a minor correction for English

Since there is no contact list but rather a favorites list, I think it should specify "favorites list" to avoid confusing users (changes for the English).

Thank you!


Use of built-in node module triggers node_modules errors

If you require any of the built-in node modules (https://github.com/nodejs/node/tree/master/lib), the following errors are incorrectly triggered:
You have defined functions but no package.json has been found.
You have defined functions but no node_modules has been found
Example function for easy checking:
const util = require('util')

module.exports = event => {
  console.log(util.inspect(event))
  return {
    data: {
      message: `Hello ${event.data.name || 'World'}`
    }
  }
}

Built-in modules are now being ignored.


Creating target directory if missing (it can happen when it's a paren…

When running promote:make-promotable in a Maven project with <packaging>pom</packaging>, it fails with the following error:

[ERROR] Failed to execute goal se.jiderhamn:promote-maven-plugin:1.0.0:make-promotable (default) on project mag-parent-pom: Error writing artifacts to file: /Users/XXX/dev/myproject-parent-pom/target/promotable-artifacts.properties (No such file or directory) -> [Help 1]

fixed.

Thanks for the Pull Request!

No worries, any plans to release a 1.0.1?

I had plans for a 1.1.0 with another feature, but since I'm unsure if I'll find the time this week I just made a 1.0.1 release. Should be available in Maven central shortly.


WIP: Add routes to get contract data about votes and bloom

Pairs with https://github.com/polyswarm/contracts/pull/56

[x] Get votes from contract
[ ] Get bloom values from contract

Should I update the following to retrieve votes, assertions, and bloom?
@bounties.route('/<uuid:guid>', methods=['GET'])
@chain
def get_bounties_guid(guid):
    bounty = bounty_to_dict(
        g.chain.bounty_registry.contract.functions.bountiesByGuid(guid.int).call())
    if not is_valid_ipfshash(bounty['uri']):
        return failure('Invalid IPFS hash in URI', 400)
    if bounty['author'] == zero_address:
        return failure('Bounty not found', 404)

    return success(bounty)

Yeah, it would probably be useful.

I think we should do the bounty changes in a separate ticket and PR


Fetch operations from ElasticSearch storage

This change is

I close this PR in favour of es-refresh branch


BuildStream 1.6.4 stable release

I want to use .netrc support in bst-1 branch and would like this in a stable Bst release.
List of outstanding bugfix MRs we should look at before releasing.

https://github.com/apache/buildstream/pull/1563

I've merged some of these which appear mostly harmless and straight forward.
I accidentally merged #1564 so now we have broken CI in bst-1, I'm hoping we can fix this in #1562 rather than having to revert that change.
I'm not entirely sure off hand whether to merge #1575 or not.

Related: https://github.com/apache/buildstream/issues/1588

https://github.com/apache/buildstream/pull/1576 would also be great to be integrated if no objections. It's blocking us from fixing sandbox arch in freedesktop-sdk.

Released today.


Alexa

Any way to connect this wirelessly to alexa with a trigger word to open/close garage door?

I used AWS IoT + Alexa.
Alexa skill "[Open|Close] garage door"
Sends to AWS Lambda function
AWS Lambda sends to SNS topic
SNS sends to AWS IoT MQTT topic
(Lambda can also push MQTT as well)
Device receives MQTT message and performs the action

Thanks h3smith! I'm unfamiliar with some of the processes in your suggestion. Could you elaborate?

same here, would love to see the associated language to integrate with Alexa!

I'll throw up a gist over the holiday weekend - if I don't by next Sunday please @ me!

Looking forward to it! Thanks for your help!

Also interested in Alexa integration.

Interested in Alexa here too.  Everything worked perfectly, thank you!

@tgdibello.  Can you please elaborate how you made this work?  I need some
more detail with the step by steps on this process.  NOOB here.  Thanks!
On Sun, Nov 27, 2016 at 9:43 PM, tgdibello<EMAIL_ADDRESS>wrote:

Interested in Alexa here too. Everything worked perfectly, thank you!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/andrewshilliday/garage-door-controller/issues/39#issuecomment-263177176,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARfX3xWRUofFFb3WuN_dL7e9h04HuVVLks5rCk3mgaJpZM4KuF7_
.

--

Andy

What are you having trouble with?

On Nov 27, 2016, at 10:46 PM, Andy<EMAIL_ADDRESS>wrote:
@tgdibello. Can you please elaborate how you made this work? I need some
more detail with the step by steps on this process. NOOB here. Thanks!
On Sun, Nov 27, 2016 at 9:43 PM, tgdibello<EMAIL_ADDRESS>wrote:

Interested in Alexa here too. Everything worked perfectly, thank you!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/andrewshilliday/garage-door-controller/issues/39#issuecomment-263177176,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARfX3xWRUofFFb3WuN_dL7e9h04HuVVLks5rCk3mgaJpZM4KuF7_
.

--

Andy
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@tgdibello @h3smith Could either of you post a brief tutorial of the steps and methods you used to get Alexa to function with your garage controller?
Did you create your own private Alexa skill for your use or is it publicly available?

I really don't even know where to start with this. Thanks for direction.
On Mon, Nov 28, 2016, 10:51 AM zbowman<EMAIL_ADDRESS>wrote:

@tgdibello https://github.com/tgdibello @h3smith
https://github.com/h3smith Could either of you post a brief tutorial of
the steps and methods you used to get Alexa to function with your garage
controller?
Did you create your own private Alexa skill for your use or is it publicly
available?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/andrewshilliday/garage-door-controller/issues/39#issuecomment-263325252,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARfX3y7pqwKxyWJPehQ4UDFe0pmeyhBMks5rCwacgaJpZM4KuF7_
.

I'm sorry, I haven't finished the Alexa setup yet.  My comment was about
the original app.  I'll be working on the Alexa setup very soon, and will
share as I learn.
On Mon, Nov 28, 2016 at 12:37 PM, Andy<EMAIL_ADDRESS>wrote:

I really don't even know where to start with this. Thanks for direction.
On Mon, Nov 28, 2016, 10:51 AM zbowman<EMAIL_ADDRESS>wrote:

@tgdibello https://github.com/tgdibello @h3smith
https://github.com/h3smith Could either of you post a brief tutorial
of
the steps and methods you used to get Alexa to function with your garage
controller?
Did you create your own private Alexa skill for your use or is it
publicly
available?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/andrewshilliday/garage-door-controller/issues/39#
issuecomment-263325252>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ARfX3y7pqwKxyWJPehQ4UDFe0pmeyhBMks5rCwacgaJpZM4KuF7_>
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/andrewshilliday/garage-door-controller/issues/39#issuecomment-263338497,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXGEdGnJXh7GJ5yrXChbr6FMGQLIRvoCks5rCxFSgaJpZM4KuF7_
.

@zbowman @morejava @drunet I've thrown something up here: https://github.com/h3smith/aws-iot-alexa
I am away on holiday since last week - I'll upload the Lambda code and Raspberry Pi code on how to do the hard work when I get back tomorrow. Apologies for the delay.

Thanks Harold!
On Tue, Nov 29, 2016, 1:31 PM Harold Smith III<EMAIL_ADDRESS>wrote:

@zbowman https://github.com/zbowman @morejava
https://github.com/morejava @drunet https://github.com/drunet I've
thrown something up here: https://github.com/h3smith/aws-iot-alexa
I am away on holiday since last week - I'll upload the Lambda code and
Raspberry Pi code on how to do the hard work when I get back tomorrow.
Apologies for the delay.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/andrewshilliday/garage-door-controller/issues/39#issuecomment-263673387,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARfX3yurPBd6AfT9bKUylTB98wlW_GJBks5rDH2fgaJpZM4KuF7_
.

This has been off my radar for the past year. Only just now having to rebuild my pi and noticing some of the changes that have happened with this project since I first started using it. Have built some demo skills for work when Alexa first launched. Will do what I can to help.

Thanks guys!  I am pretty good with AWS, but not so great with coding.  A working example will go a long way.

Thanks @h3smith, I was able to setup all of the AWS functions but haven't made it to the pi portion of the setup. Could you add the MQTT / pi portion to https://github.com/h3smith/aws-iot-alexa ?

Just adding a comment to show my interest as well. @h3smith thank you for what you've provided already, and the rest of the steps would be greatly appreciated.

@boogy886 @zbowman i pushed to the repo - apologies for the delay - work has been crazy! please just tag me on that repo so I don't clog up Andrews :)

I'm a bit late to the party but just to chime in on this:  Firstly, can Alexa respond to automation commands that aren't explicitly open and close (or turn on/turn off)?  The reason I ask is that except under specific circumstances, we don't know whether pushing the garage door button will open the garage or shut it.  So if we were to use Alexa, a preferred trigger would be something like "Alexa toggle the garage" or something like that.
Secondly, I was thinking of improving the degree to which the garage door controller is integrated with OpenHab.  This allows for a more integrated interface with some of the other home automation stuff I have.  If I go that route, then in theory I (we) could make use of the Alexa/OpenHab integration that is already in place.  I'll look into it.


SQLContext.sql() needs to escape the " character

SQLContext.sql() surrounds the sql string with ", so we need to escape any occurrences in the string itself.

Duplicate of #23


ServiceBalancerJob loop on daemon services with affinity filter

Running a strategy: daemon service with affinity: label... filters to only run on a subset of grid nodes results in a continous ServiceBalancerJob: rebalancing service .... loop. It seems like the ServiceBalancerJob should_balance_stateless_service? -> all_instances_exist? -> desired_count_for_service logic does not take the scheduling filters into account for daemon services. The rebalancer expects each daemon service to be running on all grid nodes, and thus attempts to deploy it.
kontena node ls
  Name                                                                   Version    Status     Initial    Labels
⊛ core-01                                                                1.1.2.rc1  online     1 / 1      test
⊛ core-02                                                                1.1.2.rc1  online     -          no-ingress-lb

kontena service show ingress-lb/lb
development/ingress-lb/lb:
  created: 2017-02-22T10:41:22.509Z
  updated: 2017-02-22T10:41:22.509Z
  stack: development/ingress-lb
  state: running
  image: kontena/lb:latest
  revision: 1
  stack_revision: 1
  stateful: no
  scaling: 1
  strategy: daemon
  deploy_opts:
    min_health:
    wait_for_port: 80
    interval: 604800
  dns: lb.ingress-lb.development.kontena.local
  affinity:
    - label!=no-ingress-lb
  secrets:
    - secret: LB_STATS_PASSWORD
      name: STATS_PASSWORD
      type: env
  env:
    - KONTENA_LB_HEALTH_URI=/__health
  net: bridge
  ports:
    - 80:80/tcp
    - 443:443/tcp
  health check:
    protocol: http
    uri: /__health
    port: 80
    timeout: 10
    interval: 60
    initial_delay: 10
  health status:
    healthy: 1
    total: 1
  instances:
    ingress-lb.lb-1:
      rev: 2017-02-24 11:00:56 UTC
      service_rev: 1
      node: core-01
      dns: lb-1.ingress-lb.development.kontena.local
      ip: <IP_ADDRESS>
      public ip: <IP_ADDRESS>
      health: healthy (58s ago)
      status: running
      exit code: 0

kontena-server logs
I, [2017-02-24T13:01:18.182670 #23219]  INFO -- ServiceBalancerJob: rebalancing service: development/ingress-lb/lb
I, [2017-02-24T13:01:18.230342 #23223]  INFO -- GridServiceDeployer: starting to deploy development/ingress-lb/lb
I, [2017-02-24T13:01:18.256393 #23223]  INFO -- GridServiceDeployer: deploying service instance development/ingress-lb/lb-1 to node core-01
I, [2017-02-24T13:01:18.256765 #23223]  INFO -- GridServiceDeployer: throttling service instance development/ingress-lb/lb deploy because of min_health limit (1 instances in-progress)
I, [2017-02-24T13:01:21.957685 #23223]  INFO -- GridServiceDeployer: service development/ingress-lb/lb has been deployed
I, [2017-02-24T13:01:34.194585 #23215]  INFO -- LeaderElectorJob: won election ♚
I, [2017-02-24T13:01:38.258360 #23215]  INFO -- ServiceBalancerJob: rebalancing service: development/ingress-lb/lb
I, [2017-02-24T13:01:38.715953 #23219]  INFO -- GridServiceDeployer: starting to deploy development/ingress-lb/lb
I, [2017-02-24T13:01:38.809646 #23219]  INFO -- GridServiceDeployer: deploying service instance development/ingress-lb/lb-1 to node core-01
I, [2017-02-24T13:01:38.810035 #23219]  INFO -- GridServiceDeployer: throttling service instance development/ingress-lb/lb deploy because of min_health limit (1 instances in-progress)
I, [2017-02-24T13:01:42.533291 #23219]  INFO -- GridServiceDeployer: service development/ingress-lb/lb has been deployed
I, [2017-02-24T13:01:58.205907 #23215]  INFO -- ServiceBalancerJob: rebalancing service: development/ingress-lb/lb
I, [2017-02-24T13:01:58.605193 #23219]  INFO -- GridServiceDeployer: starting to deploy development/ingress-lb/lb
I, [2017-02-24T13:01:58.672945 #23219]  INFO -- GridServiceDeployer: deploying service instance development/ingress-lb/lb-1 to node core-01
I, [2017-02-24T13:01:58.673284 #23219]  INFO -- GridServiceDeployer: throttling service instance development/ingress-lb/lb deploy because of min_health limit (1 instances in-progress)
I, [2017-02-24T13:02:02.375805 #23219]  INFO -- GridServiceDeployer: service development/ingress-lb/lb has been deployed
I, [2017-02-24T13:02:18.210269 #23215]  INFO -- ServiceBalancerJob: rebalancing service: development/ingress-lb/lb
I, [2017-02-24T13:02:18.513984 #23219]  INFO -- GridServiceDeployer: starting to deploy development/ingress-lb/lb
I, [2017-02-24T13:02:18.575474 #23219]  INFO -- GridServiceDeployer: deploying service instance development/ingress-lb/lb-1 to node core-01
I, [2017-02-24T13:02:18.575859 #23219]  INFO -- GridServiceDeployer: throttling service instance development/ingress-lb/lb deploy because of min_health limit (1 instances in-progress)
I, [2017-02-24T13:02:22.791369 #23219]  INFO -- GridServiceDeployer: service development/ingress-lb/lb has been deployed
I, [2017-02-24T13:02:32.206800 #23223]  INFO -- LeaderElectorJob: won election ♚
I, [2017-02-24T13:02:38.241463 #23223]  INFO -- ServiceBalancerJob: rebalancing service: development/ingress-lb/lb
I, [2017-02-24T13:02:38.896039 #23219]  INFO -- GridServiceDeployer: starting to deploy development/ingress-lb/lb
I, [2017-02-24T13:02:38.936099 #23219]  INFO -- GridServiceDeployer: deploying service instance development/ingress-lb/lb-1 to node core-01
I, [2017-02-24T13:02:38.936454 #23219]  INFO -- GridServiceDeployer: throttling service instance development/ingress-lb/lb deploy because of min_health limit (1 instances in-progress)
I, [2017-02-24T13:02:42.658394 #23219]  INFO -- GridServiceDeployer: service development/ingress-lb/lb has been deployed
I, [2017-02-24T13:02:58.130696 #23223]  INFO -- ServiceBalancerJob: rebalancing service: development/ingress-lb/lb
I, [2017-02-24T13:02:58.157493 #23215]  INFO -- GridServiceDeployer: starting to deploy development/ingress-lb/lb
I, [2017-02-24T13:02:58.197567 #23215]  INFO -- GridServiceDeployer: deploying service instance development/ingress-lb/lb-1 to node core-01
I, [2017-02-24T13:02:58.197940 #23215]  INFO -- GridServiceDeployer: throttling service instance development/ingress-lb/lb deploy because of min_health limit (1 instances in-progress)
I, [2017-02-24T13:03:02.365853 #23215]  INFO -- GridServiceDeployer: service development/ingress-lb/lb has been deployed
...

kontena-agent logs
kontena-agent | D, [2017-02-24T11:04:38.739724 #1] DEBUG -- RpcServer: rpc request: Kontena::Rpc::ServicePodsApi#create [{"service_id"=>"58ad6ad2de3578692900007a", "service_name"=>"ingress-lb.lb", "service_revision"=>1, "updated_at"=>"2017-02-22 10:41:22 UTC", "instance_number"=>1, "image_name"=>"kontena/lb:latest", "image_credentials"=>nil, "deploy_rev"=>"2017-02-24 11:04:38 UTC", "stateful"=>false, "user"=>nil, "cmd"=>nil, "entrypoint"=>nil, "memory"=>nil, "memory_swap"=>nil, "cpu_shares"=>nil, "privileged"=>nil, "cap_add"=>[], "cap_drop"=>[], "devices"=>[], "ports"=>[{"ip"=>"<IP_ADDRESS>", "protocol"=>"tcp", "node_port"=>80, "container_port"=>80}, {"ip"=>"<IP_ADDRESS>", "protocol"=>"tcp", "node_port"=>443, "container_port"=>443}], "volumes"=>[], "volumes_from"=>[], "net"=>"bridge", "hostname"=>"lb-1", "domainname"=>"ingress-lb.development.kontena.local", "exposed"=>true, "log_driver"=>nil, "log_opts"=>{}, "pid"=>nil, "env"=>["KONTENA_LB_HEALTH_URI=/__health", "KONTENA_SERVICE_ID=58ad6ad2de3578692900007a", "KONTENA_SERVICE_NAME=lb", "KONTENA_GRID_NAME=development", "KONTENA_STACK_NAME=ingress-lb", "KONTENA_NODE_NAME=core-01", "KONTENA_SERVICE_INSTANCE_NUMBER=1"], "secrets"=>[{"name"=>"STATS_PASSWORD", "type"=>"env", "value"=>"OWNQkluHOPBS"}], "labels"=>{"io.kontena.container.id"=>"58b01346de35785ab3000007", "io.kontena.service.id"=>"58ad6ad2de3578692900007a", "io.kontena.service.name"=>"lb", "io.kontena.stack.name"=>"ingress-lb", "io.kontena.grid.name"=>"development", "io.kontena.health_check.uri"=>"/__health", "io.kontena.health_check.protocol"=>"http", "io.kontena.health_check.interval"=>"60", "io.kontena.health_check.timeout"=>"10", "io.kontena.health_check.initial_delay"=>"10", "io.kontena.health_check.port"=>"80"}, "hooks"=>[], "networks"=>[{"name"=>"kontena", "subnet"=>"<IP_ADDRESS>/16", "multicast"=>true, "internal"=>false}]}]
kontena-agent | I, [2017-02-24T11:04:38.745178 #1]  INFO -- Kontena::ServicePods::Creator: creating service: ingress-lb.lb-1
kontena-agent | I, [2017-02-24T11:04:38.745527 #1]  INFO -- Kontena::Workers::ImagePullWorker: pulling image: kontena/lb:latest
kontena-agent | I, [2017-02-24T11:04:41.807099 #1]  INFO -- Kontena::Workers::ImagePullWorker: pulled image: kontena/lb:latest
kontena-agent | I, [2017-02-24T11:04:41.926239 #1]  INFO -- Kontena::ServicePods::Creator: service is up-to-date: ingress-lb.lb-1
kontena-agent | D, [2017-02-24T11:04:42.384624 #1] DEBUG -- RpcServer: rpc request: Kontena::Rpc::AgentApi#port_open? ["<IP_ADDRESS>", 80]
kontena-agent | D, [2017-02-24T11:04:58.648268 #1] DEBUG -- RpcServer: rpc request: Kontena::Rpc::ServicePodsApi#create [{"service_id"=>"58ad6ad2de3578692900007a", "service_name"=>"ingress-lb.lb", "service_revision"=>1, "updated_at"=>"2017-02-22 10:41:22 UTC", "instance_number"=>1, "image_name"=>"kontena/lb:latest", "image_credentials"=>nil, "deploy_rev"=>"2017-02-24 11:04:58 UTC", "stateful"=>false, "user"=>nil, "cmd"=>nil, "entrypoint"=>nil, "memory"=>nil, "memory_swap"=>nil, "cpu_shares"=>nil, "privileged"=>nil, "cap_add"=>[], "cap_drop"=>[], "devices"=>[], "ports"=>[{"ip"=>"<IP_ADDRESS>", "protocol"=>"tcp", "node_port"=>80, "container_port"=>80}, {"ip"=>"<IP_ADDRESS>", "protocol"=>"tcp", "node_port"=>443, "container_port"=>443}], "volumes"=>[], "volumes_from"=>[], "net"=>"bridge", "hostname"=>"lb-1", "domainname"=>"ingress-lb.development.kontena.local", "exposed"=>true, "log_driver"=>nil, "log_opts"=>{}, "pid"=>nil, "env"=>["KONTENA_LB_HEALTH_URI=/__health", "KONTENA_SERVICE_ID=58ad6ad2de3578692900007a", "KONTENA_SERVICE_NAME=lb", "KONTENA_GRID_NAME=development", "KONTENA_STACK_NAME=ingress-lb", "KONTENA_NODE_NAME=core-01", "KONTENA_SERVICE_INSTANCE_NUMBER=1"], "secrets"=>[{"name"=>"STATS_PASSWORD", "type"=>"env", "value"=>"OWNQkluHOPBS"}], "labels"=>{"io.kontena.container.id"=>"58b0135ade35785abb00000a", "io.kontena.service.id"=>"58ad6ad2de3578692900007a", "io.kontena.service.name"=>"lb", "io.kontena.stack.name"=>"ingress-lb", "io.kontena.grid.name"=>"development", "io.kontena.health_check.uri"=>"/__health", "io.kontena.health_check.protocol"=>"http", "io.kontena.health_check.interval"=>"60", "io.kontena.health_check.timeout"=>"10", "io.kontena.health_check.initial_delay"=>"10", "io.kontena.health_check.port"=>"80"}, "hooks"=>[], "networks"=>[{"name"=>"kontena", "subnet"=>"<IP_ADDRESS>/16", "multicast"=>true, "internal"=>false}]}]
kontena-agent | I, [2017-02-24T11:04:58.655937 #1]  INFO -- Kontena::ServicePods::Creator: creating service: ingress-lb.lb-1
kontena-agent | I, [2017-02-24T11:04:58.658910 #1]  INFO -- Kontena::Workers::ImagePullWorker: pulling image: kontena/lb:latest
kontena-agent | I, [2017-02-24T11:05:01.675429 #1]  INFO -- Kontena::Workers::ImagePullWorker: pulled image: kontena/lb:latest
kontena-agent | I, [2017-02-24T11:05:01.768975 #1]  INFO -- Kontena::ServicePods::Creator: service is up-to-date: ingress-lb.lb-1
kontena-agent | D, [2017-02-24T11:05:02.060890 #1] DEBUG -- Workers::StatsWorker: starting collection
kontena-agent | D, [2017-02-24T11:05:02.265036 #1] DEBUG -- RpcServer: rpc request: Kontena::Rpc::AgentApi#port_open? ["<IP_ADDRESS>", 80]

As you can see above this looping appears to be causing some issues :)

The rebalancer loop happens every 20 seconds, so the pattern there would be be on a much shorter timescale.
Interesting to see the constant level of CPU utilization increase over time, though. Is it the kontena-server-api Docker container -> ruby/puma process that's eating CPU, or the kontena-server-mongo Docker container -> mongodb process?

It appears to be the server-api container. The mongo container maintains a fairly consistent cpu usage. (and was not the one restarted in the above image)

#1873 should fix this

Any idea when 1.2.0 will be ready for production or any chance a fix could be applied to 1.1? This issue is making my Kontena stacks very unreliable (service instances deploying to all nodes and then later disappearing) and is the only issue preventing me from being comfortable with completing a migration to Kontena.

Or is there at least a temporary fix besides removing the entire stack and re-deploying? Right now for example I have a service with only 2 instances running when there should be 4 and none of the non-destructive commands I've tried can revive the other 2. E.g. 'kontena service restart', 'kontena service deploy --force', restarting the Kontena master API container, etc...
Log example:
I, [2017-03-22T18:00:29.513860 #6]  INFO -- GridServiceDeployer: starting to deploy primary/redis-cache/lb
I, [2017-03-22T18:00:33.108473 #6]  INFO -- GridServiceDeployer: deploying service instance primary/redis-cache/lb-1 to node app2
I, [2017-03-22T18:00:33.115329 #6]  INFO -- GridServiceDeployer: throttling service instance primary/redis-cache/lb deploy because of min_health limit (1 instances in-progress)
I, [2017-03-22T18:00:39.583310 #6]  INFO -- GridServiceDeployer: deploying service instance primary/redis-cache/lb-2 to node app1
I, [2017-03-22T18:00:39.586034 #6]  INFO -- GridServiceDeployer: throttling service instance primary/redis-cache/lb deploy because of min_health limit (1 instances in-progress)

The problem is that there are two other nodes besides app1 and app2 that never get the esrvice deployed to them because of some issue with this service getting stuck on app1 and app2. If I deploy the stack fresh it works and then some number of days later at some point it breaks ostensibly due to this service deploy thrashing.

I've been digging in deeper and found that the error is that the 'wait_for_port' option is timing out even though the service is running and accepting connections on that port. I started using "nc -z  " to confirm if it should really be timing out and found something very interesting.. On the service that is broken if I use "nc -z" against the bridge IP it works and if I use it against the weave IP it doesn't. For a different service with an almost identical image and service config the "nc -z" test works against BOTH the bridge IP and the weave IP.. So I'm guessing that "container.ip_address" on this line is the weave IP and not the Docker bridge IP? However, I have no idea why the host and agent would not be able to connect to the new container over the weave IP but it would over the docker IP; that is beyond my knowledge of weave/kontena..
Here is proof from the kontena-agent container:
/app # getent hosts lb-1.galera.primary.kontena.local
<IP_ADDRESS>      lb-1.galera.primary.kontena.local  lb-1.galera.primary.kontena.local
/app # getent hosts lb-1.redis-cache.primary.kontena.local
<IP_ADDRESS>      lb-1.redis-cache.primary.kontena.local  lb-1.redis-cache.primary.kontena.local
/app # nc -z <IP_ADDRESS> 1936 && echo yes
yes
/app # nc -z <IP_ADDRESS> 1936 && echo yes
/app # nc -z <IP_ADDRESS> 1936 && echo yes
yes

The next to last line is the kontena network IP, the last line is the Docker bridge IP of the same container.

Any idea when 1.2.0 will be ready for production or any chance a fix could be applied to 1.1? This issue is making my Kontena stacks very unreliable (service instances deploying to all nodes and then later disappearing) and is the only issue preventing me from being comfortable with completing a migration to Kontena.

This issue is about the server triggering unnecessary re-deploys, which should be harmless, as the services are already deployed and up to date. If these extra deploys are then in turn triggering other bugs that make your services unstable, then that's a separate issue.

I've been digging in deeper and found that the error is that the 'wait_for_port' option is timing out even though the service is running and accepting connections on that port.

Let's figure this one out over in #1862

Fixed by #1873
D, [2017-03-27T13:44:24.728149 #8740] DEBUG -- GridScheduler: service does not need rescheduling: development/null/redis-daemon