is our project support cuda 11.4 (current 11.3)

my os cuda version is cuda 11.4, your lib. automatically download version is 1.11.0-cu113 ， not match ths os, will you deal this bug?
cause:

fatal error:

error msg:
ai.djl.engine.EngineException: nvrtc: error: failed to open nvrtc-builtins64_113.dll.
Make sure that nvrtc-builtins64_113.dll is installed correctly.
nvrtc compilation failed:
#define NAN __int_as_float(0x7fffffff)
#define POS_INFINITY __int_as_float(0x7f800000)
#define NEG_INFINITY __int_as_float(0xff800000)
template
device T maximum(T a, T b) {
return isnan(a) ? a : (a > b ? a : b);
}
template
device T minimum(T a, T b) {
return isnan(a) ? a : (a < b ? a : b);
}
extern "C" global
void fused_sigmoid_mul(float* tx_10, float* aten_mul) {
{
float tx_10_1 = __ldg(tx_10 + (long long)(threadIdx.x) + 512ll * (long long)(blockIdx.x));
aten_mul[(long long)(threadIdx.x) + 512ll * (long long)(blockIdx.x)] = tx_10_1 * (1.f / (1.f + (expf(0.f - tx_10_1))));
}
}

@moowcharnfu
pytorch-native-cu113 should be able to run on CADA 11.4. On Linux, there is a symbolic link to libnvrtc-builtins64.so.1.10.
To workaround this issue on Windows, you can copy nvrtc-builtins64_114.dll to nvrtc-builtins64_113.dll

@moowcharnfu
pytorch-native-cu113 should be able to run on CADA 11.4. On Linux, there is a symbolic link to libnvrtc-builtins64.so.1.10.
To workaround this issue on Windows, you can copy nvrtc-builtins64_114.dll to nvrtc-builtins64_113.dll

so smart to deal,   closed


az functionapp plan create with --min-instances option fail

This is autogenerated. Please review and update as needed.
Describe the bug
This error may happen below line.
max() function does not accept str input
https://github.com/Azure/azure-cli/blob/e894197d8cc890b4a1ab973e2c183c50a04d8a98/src/azure-cli/azure/cli/command_modules/appservice/custom.py#L1918
Command Name
az functionapp plan create
Errors:
The command failed with an unexpected error. Here is the traceback:
'>' not supported between instances of 'str' and 'int'
Traceback (most recent call last):
  File "/opt/az/lib/python3.10/site-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 663, in execute
    raise ex
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 718, in _run_job
    return cmd_copy.exception_handler(ex)
  File "/opt/az/lib/python3.10/site-packages/azure/cli/command_modules/appservice/commands.py", line 39, in _ex_handler
    raise ex
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 697, in _run_job
    result = cmd_copy(params)
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 333, in __call__
    return self.handler(*args, **kwargs)
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/opt/az/lib/python3.10/site-packages/azure/cli/command_modules/appservice/custom.py", line 3388, in create_functionapp_app_service_plan
    _enable_zone_redundant(plan_def, sku_def, number_of_workers)
  File "/opt/az/lib/python3.10/site-packages/azure/cli/command_modules/appservice/custom.py", line 1918, in _enable_zone_redundant
    sku_def.capacity = max(3, number_of_workers)
TypeError: '>' not supported between instances of 'str' and 'int'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az functionapp plan create --name {} --resource-group {} --sku {} --location {} --min-instances {} --tags {} --zone-redundant --verbose --debug

Expected Behavior
Environment Summary
Linux-<IP_ADDRESS>-microsoft-standard-WSL2-x86_64-with-glibc2.31, Ubuntu 20.04.1 LTS
Python 3.10.5
Installer: DEB

azure-cli 2.38.0

Extensions:
appservice-kube 0.1.7
connectedk8s 1.2.9
customlocation 0.1.3
k8s-extension 1.2.3

Dependencies:
msal 1.18.0b1
azure-mgmt-resource 21.1.0b1

Additional Context

@georgeOsdDev Thank you for reaching out, we are looking into it.

route to CXP team


layer normalization after Linear

Is there any module for layer normalization after linear transformation? Thanks.

We don't have any particular kernel fusions for that pattern, so there's no harm in putting a LayerNorm module after the linear:
linear = te.Linear(...)
norm = te.LayerNorm(...)
y = norm(linear(x))

Using the operation-based API (see https://github.com/NVIDIA/TransformerEngine/pull/1033), this could be:
layer = te.ops.Sequential(
    te.ops.Linear(...),
    te.ops.LayerNorm(...),
)

If we do find some kernel fusions for this pattern, we would probably implement it using the operation-based API instead of implementing a new module.

Hello, @timmoon10
I am working on a two-layer MLP setup within a tensor parallelism context (e.g., tp=2), which consists of a TEColumnParallelLinear followed by a TERowParallelLinear. I’m looking to perform a LayerNorm operation right after the output from TEColumnParallelLinear, and importantly, I want each tensor parallel split (tp slice) to have its own independent LayerNorm.
Could you provide any suggestions on whether there is an existing module that supports this, or how one might go about adding this functionality? Thank you for your assistance!


Browse through train pages

Inserting two buttons on the subpages https://trains.jo-m.ch/#/trains/XXXX to get to the pages XXXX-1 and XXXX+1.

PRs are welcome.


Make available in method

Would there be any way this could be used from within a method?
I'm using it in a thumbnail gallery, which is setup to swap photos on mouseover, or on click/touch for mobile devices. I'd like to scroll only when the thumbnail is clicked (which is currently a separate method from mouseover)
Currently when you click while on a desktop, it scrolls slightly from the top of the browser, which looks a bit odd. Thus the method approach.

Just ran into a situation when I would need to call scroll-to programmatically, in a method for example. Is there a way to do it?


Hotkeys in Html View

Basic hotkey support for navigation by keyboard like / for search or ? for showing modal with help.

Won't fix due to the termination of the Apiator UI


trans dont work

Check if you can actually visit https://translate.google.com/ from the browser, and check the output of  curl -I https://translate.google.com/. This is most likely because either your IP has been blocked by Google or you're hitting a firewall.
FYI According to some sources, they're shutting down the translate service in China too. So you will probably need a proxy. https://www.solidot.org/story?sid=72923


Hololens unity3d support

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

Hi @sabariprasad, I see that you opened this feedback item on Azure Kinect DK Feedback. That is the best place to track the enhancement, so I am going to close this one.


Link to documentation is broken

The link from the main page, https://github.com/malisipi/mui#documentation, points to a broken link (below).
https://github.com/malisipi/mui/blob/main/docs.md (broken link).
Maybe you want to post links to your new documentation, in place of the broken one:
https://github.com/malisipi/mui/blob/main/docs_md/mui.md
https://github.com/malisipi/mui/blob/main/docs_md/webview.md

Thanks for your issue. I had totally forgotten to update documentation links.


Allow callback= to be an awaitable function

If callback= could be provided an awaitable, users could construct functions that e.g. make an async call to a database as part of deciding if a host should be allowed.
I tried implementing this with a asyncio.isawaitable() test against the callable but for some reason it didn't detect my await function as being awaitable. Here's the unit test I added which I failed to get passing:

@pytest.mark.asyncio
async def test_callback_async():
    was_called = False

    async def callback_true(origin):
        return True

    async def callback_false(origin):
        return False

    assert EXAMPLE_HOST == await get_cors_header(asgi_cors(hello_world_app, callback=callback_true), EXAMPLE_HOST)
    assert None == await get_cors_header(asgi_cors(hello_world_app, callback=callback_false), EXAMPLE_HOST)

@simonw Admittedly, this might not be much help to you (or relevant anymore) but would changing asyncio.iscoroutine(...) to asyncio.iscoroutinefunction(...) fix the issue?


docker swarm Mode: host

In the dockers compose swarm

target: 80
         Published: 80
         Mode: host
"8080:8080"
Unable to access the working node, unable to synchronize port 80 (the management node can access and return the real client ip)
(8080 port is normal on the management node and the working node)
How can I solve this problem?

Docker-compose file:
version: '3.4'
services:
reverse-proxy:
image: traefik
command: --api --docker --docker.swarmMode --docker.domain=traefik --docker.watch
ports:
- target: 80
published: 80
mode: host
- "8080:8080"
deploy:
mode: global
placement:
constraints: [node.role == manager]
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- /root/traefik/traefik.toml:/traefik.toml

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Traefik!
We dedicate the issue tracker to bug reports and feature requests only. My advanced AI tells me this one is neither of them.
I encourage your to seek community support: join our Slack workspace and reach out to us on the #support channel.
Another option is to use Stack Overflow and tag your question traefik.
You can of course double check Traefik's documentation :sweat_smile:


Gatekeeper Path Randomization makes life hard #182

A follow up for https://github.com/Squirrel/Squirrel.Mac/issues/182
The issue was never solved and it creates a big bunch of problems to many of us.
https://github.com/Microsoft/vscode/issues/7426
Nothing you can do about it?
The problem still exist on macOS Mojave

@steffanhalv That issue was closed by https://github.com/Squirrel/Squirrel.Mac/pull/186
There is a usable error that you can show your users that tells them how to fix it (move the app to a non-readonly place)

@MarshallOfSound Sorry, guess I didn't look close enough, but still doesn't solve the problem for me.
Here is a summary for how I got into this and hopefully you have better insights as of where the problem occurs:

Creating an electronjs application
Using latest electron-updater which uses Squirrel.Mac for autoupdates on mac
Creating a build and upload it to the web as a .dmg  in a github release together with a .zip file for autoupdates
I download the .dmg and drag it to the application folder
Application starts and update is detected and downloads successfully
Trying to perform Quit and Install of the new update, now does not work
I look in the log files and I find: Error: Could not create temporary directory: No access
I navigate to ~/Library/Caches/com.myapp.MyApp.ShipIt and find that its not owned by the user
So I run sudo chown $USER ~/Library/Caches/com.myapp.MyApp.ShipIt and then the update works

It's just very strange if I have to drag the app out of the application folder to the desktop and open from there to use the updater. If I drag it to the desktop and back in to the application folder the error still does persist.
So some says it's a problem with ShipIt, maybe it could be a bug in Electron Updater, I dont know ^^.
I forgot to see which user that had access to /Caches/com.myapp.MyApp.ShipIt but I guess it was root. At least I was forced to use sudo to make it work.
So I think it has to be either ShipIt or Electron that creates this cache folder as wrong user, and that is not necessary or am I wrong?


project: bump major version to 3.0.0

Work in preparation for a v3.0.0 release tag.
I split this branch up into several commits to try and make it easier to follow. The first, be079af moves everything from v2/ to v3/ as-is. Notably this commit won't build because all of the references remain for v2. The second 065541e introduces the fixes for those references both in code and documentation/CI config. Lastly 5bcbe22 bumps the module version to v3 and includes a go mod tidy.
Updates https://github.com/zmap/zlint/issues/503

(mutters about how much I hate this works)

The dev experience of schlepping around the whole code base through a series of incrementing subdirs is... not ideal :laughing:


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/63631

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/65686


fix(docs): fix critical typo in configuration.md

This PR contains a critical fix for the example in configuration.md when using sibling viewports.
The current example is broken and uses a components key in the mapping, which should be component.
This PR fixes the typo so the example becomes correct.

I noticed that in some of the discussions there is a mention of using components instead of component, but the current version breaks when using components.
If the goal is to keep using components then the code may need fixing instead of the documentation.

I just realized that I've been inconsistent.
I don't have a strong opinion – to be honest, I think it's fine for:
component: 'foo', component: { default: 'foo' }, components: { default: 'foo' } to all mean the same thing, maybe with a warning for a preferred format.

Thanks @btford!
There could be a third way that allows both component and components to create synergy as discussed in #118.
I think if combinations (as in #118) are not allowed, it would be best to use component to avoid confusion (and not having to worry about what to do when both keys are present).
Does that make sense?

Yeah, totally. I'm gonna mull it over for a bit, and in the mean time just have component and components alias to the same thing.

I'm gonna close this, since I've pushed a fix, but let's continue the discussion on #118.

Makes sense, thanks for the follow up @btford!


error - Could not create tunnel

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.81.0
OS Version: Docker image

Steps to Reproduce:
I've built this Docker image in order to deploy a remote vscode server instance on my Raspberry PI.
The operations I do are:

Create the container using the following compose file

version: "2"
configs:
services:
  vscode:
    image: ilteoood/vscode-remote-tunnels
    container_name: vscode-remote-tunnels
    environment:
      - MACHINE_NAME=raspberry
    restart: unless-stopped
    dns:
      - <IP_ADDRESS>

Complete the authorization process.

When I re-create the container with the same MACHINE_NAME, the container dies and displays the following logs:
*
* Visual Studio Code Server
*
* By using the software, you agree to
* the Visual Studio Code Server License Terms (https://aka.ms/vscode-server-license) and
* the Microsoft Privacy Statement (https://privacy.microsoft.com/en-US/privacystatement).
*
To grant access to the server, please log into https://github.com/login/device and use code 35E5-9E6B
[2023-08-07 15:45:02] info Creating tunnel with the name: raspberry
[2023-08-07 15:45:05] error Could not create tunnel with name: raspberry

Expected behavior: when a tunnel is closed, its name should be free to use for other instances.

This bug has been fixed in the latest release of VS Code Insiders!
@ilteoood, you can help us out by commenting /verified if things are now working as expected.
If things still don't seem right, please ensure you're on version d62534a60f7eb4280bcbee66bbd84a2e15f13765 of Insiders (today's or later - you can use Help: About in the command palette to check), and leave a comment letting us know what isn't working as expected.
Happy Coding!

/verified


⚠ Bofrost.be has degraded performance

In f23fa18, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1517 ms

Resolved: Bofrost.be performance has improved in 3c1e5af.


Move default SecurityGroup from Org to VPC

I hit hold on this while we run qa-dev on it

qa-dev passed: https://github.com/nexodus-io/nexodus/actions/runs/6802130282/job/18494550541


Validate if OvenPlayer

https://ovenplayer.com/
afterwards, we maybe could migrate to a OvenMediaEngine streaming.
A Streaming Software which allow low-latency Streaming based on WebRTC - Videokonferenze Protocoll.

Example Config:
for Video (test here):
player = OvenPlayer.create("player", {
    sources: [
  {
    "id": 0,
    "file": "https://v2.media.kukoon.de/videos/df1555f5-7046-4f7a-adcc-195b73949723/542685cb-3693-e720-a957-f008f5dae3ee/video_best.mp4",
    "type": "mp4",
    "label": "Origin"
  },
  {
    "id": 1,
    "file": "https://v2.media.kukoon.de/videos/df1555f5-7046-4f7a-adcc-195b73949723/542685cb-3693-e720-a957-f008f5dae3ee/video_720.mp4",
    "type": "mp4",
    "label":"720P"
  },
  {
    "id": 2,
    "file": "https://v2.media.kukoon.de/videos/df1555f5-7046-4f7a-adcc-195b73949723/542685cb-3693-e720-a957-f008f5dae3ee/video_480.mp4",
    "type": "mp4",
    "label":"480P"
  },
  {
    "id": 3,
    "file": "https://v2.media.kukoon.de/videos/df1555f5-7046-4f7a-adcc-195b73949723/542685cb-3693-e720-a957-f008f5dae3ee/audio_best.mp3",
    "type": "mp4",
    "label":"Audio-Origin"
  }
]
});

for Streaming (test here):
player = OvenPlayer.create("player", {
    sources: [
  {
    "default":true,
    "id":0,
    "file": "wss://webrtc.edge01.media.kukoon.de/app/c4eba06b-1ab3-4367-93e1-da584b96fcc8",
    "type": "webrtc",
    "label":"WebRTC"
  },
  {
    "id":1,
    "file": "wss://webrtc.edge01.media.kukoon.de/app/c4eba06b-1ab3-4367-93e1-da584b96fcc8?transport=tcp",
    "type": "webrtc",
    "label":"WebRTC-TCP"
  },
  {
    "id": 2,
    "file": "https://edge01.media.kukoon.de/app/c4eba06b-1ab3-4367-93e1-da584b96fcc8/playlist.m3u8",
    "type": "hls",
    "label":"HLS"
  },
  {
    "id": 3,
    "file": "https://edge01.media.kukoon.de/app/c4eba06b-1ab3-4367-93e1-da584b96fcc8/manifest.mpd",
    "type": "dash",
    "label":"DASH"
  }
]
});

Maybe we could generate the exact sources format by the API / Server,


Use sensible tor options, and document why each one is used

@juga0 mentioned some tor options from bwscanner on #tor-dev. bwscanner took them from chutney and torflow. Let's think about whether we need each one:
'LearnCircuitBuildTimeout': 0,  # Disable adaptive circuit timeouts.
'CircuitBuildTimeout': 20,

Yes, we should have a set timeout, to avoid biasing results.
'UseEntryGuards': 0,  # Disable UseEntryGuards to avoid PathBias warnings.

Yes, we don't need entry guards, we won't be using them.
'UseMicroDescriptors': 0,
'FetchUselessDescriptors': 1,

We shouldn't need these options, if Stem and sbws are coded correctly. Or, we can choose to work with them on or off, see #144.
'FetchDirInfoEarly': 1,
'FetchDirInfoExtraEarly': 1,

If we want to prioritise measuring new relays, we should set these options. But we should be prepared for exits to fail our circuits, because they don't have the new relay's descriptor yet.
'SafeLogging': 0,
'LogTimeGranularity': 1,

These are useful logging options for clients that don't care about anonymity.

Status update:
#147 has most of these options already.
#144 and #145 deal with the flavour options:
'UseMicroDescriptors': 0,
'FetchUselessDescriptors': 1,
We should use these options to measure new relays faster:
'FetchDirInfoEarly': 1,
'FetchDirInfoExtraEarly': 1,
We should use this option to avoid warnings:
'UseEntryGuards': 0,  # Disable UseEntryGuards to avoid PathBias warnings.

Sure. That also seems like a good design choice. If sbws fetches on a client schedule, then all the relays it uses should have updated consensuses.
We only vote once an hour anyway. And it takes clients 1-2 hours to get new bandwidths after they are in a consensus.
So when fetching early, the best case delay is 3 hours, and the worst case is about 4.5 hours.
When fetching on the client schedule, the best case delay is about 4 hours, and the worse case is about 6.
You're right, the extra load isn't worth it.


[sidenav] new component

The vwc-sidenav would be commonly used inside the vwc-side-drawer.
The vwc-sidenav will feature sidenav-item (link) and sidenav-menu (button expanding/collapsing list).
The vwc-sidenav have to be accessible via keyboard

examples for side-nav component in other design systems:

Spectrum

Side navigation - anatomy

Focus management
Referencing the above libraries shows that roving index isn’t applied in all. There’s no significant take on whether focus management, thus keyboard navigation, should be applied to side navigation or not. should navigation be handled natively by tabbing?
some opinions suggest that a plain navigation does not need roving index but an ARIA menu does, and that adding such support is only relevant to menus.
ARIA menus are not for navigation, but for app actions.
here's a take on flyout navigation vs application menu.

Focus management
Referencing the above libraries shows that roving index isn’t applied in all. There’s no significant take on whether focus management, thus keyboard navigation, should be applied to side navigation or not. should navigation be handled natively by tabbing?
Common opinions suggest that a plain navigation does not need roving index but an ARIA menu does, therefore adding such support is only relevant to menus. ARIA menus are not for navigation, but for app actions. here's a take on flyout navigation vs application menu.
This issue is more relevant to a flyout design pattern (shared above), although it will only ascend vertically instead of a horizontal navigation flow.
Note that users can navigate through the list by tabbing, and can also skip it if it’s correctly identified as such (or a <navigation> landmark. Screen readers all have a way to navigate by landmarks, which give you a way to browse the page in a non-linear way. If the navigation is in a proper <nav>, that will make it skippable.
A big caveat here is that landmark navigation is quite an advanced skill for screen reader users. Designing for it alone is like designing for power users alone.
https://webaim.org/projects/screenreadersurvey9/#landmarks highlights some of this but WebAIM does skew toward the advanced user, so reality is probably even more dramatic
This complexity might be a reason for in-distinguished design pattern when referencing existing libraries and when it comes to focus management.
in opposed to side navigation, popup menu has clear visual indication of it being a composite widget. lack of such clear visual encapsulation may confuse sighted keyboard users trying to navigate side navigation by tabbing.
I suggest featuring opt-in / out to side navigation keyboard focus management

authors may choose whether focus management should be enabled if navigation list is large and can become tedious to step through
enabling focus management should affect design to reflect clear visual indication of the side navigation component
alternatively document clear guidelines reflecting the above caveats when opting-in to focus management

@yinonov You suggest that focusing on the sidenav will affect the design. What do you want it to look like? Do you have an example for that?
@jshenkman @AyalaBu

no.
focus management refer to what is tabbable and when keyboard focus management is integrated.
when no intervention, sidenav-items are tabbable. when there are, say, more than 12 items, tabbing through items can be tedious. in such scenarios, authors might want to opt-in to focus management to result in a tab stop on sidenav itself rather (than its items).
this means all nested items within sidenav will no longer be tabbable and will be focused by keyboard interaction (arrows etc').
that way users will be able to tab to sidenav and next tabbable sibling element following sidenav. without the need to go through all 12+ items

Maybe we can consider a behavior like this:
https://atlassian.design/components/drawer/examples
but it doesn't have to be a modal,
and instead of a button maybe it can be a hamburger?
here it is similar:
https://codepen.io/illvart/pen/xLKqyR
https://codepen.io/butchewing/pen/PozMBoN
or maybe even something like this:
https://codepen.io/akshayvcsbim/pen/jwGxjj
What do you guys think?
On Mon, Jul 11, 2022 at 2:59 PM Rina Oksman @.***>
wrote:

Focus management
Referencing the above libraries shows that roving index isn’t applied in
all. There’s no significant take on whether focus management, thus keyboard
navigation, should be applied to side navigation or not. should navigation
be handled natively by tabbing?
Common opinions suggest that a plain navigation does not need roving index
but an ARIA menu does https://www.w3.org/TR/wai-aria-practices-1.2/#menu,
therefore adding such support is only relevant to menus. ARIA menus are not
for navigation, but for app actions. here's a take on flyout navigation
https://www.w3.org/WAI/tutorials/menus/flyout vs application menu
https://www.w3.org/WAI/tutorials/menus/application-menus.
This issue <#m_-5051619765872467898_200> is more relevant to a flyout
design pattern (shared above), although it will only ascend vertically
instead of a horizontal navigation flow.
Note that users can navigate through the list by tabbing, and can also skip
it if it’s correctly identified as such (or a  landmark
https://w3c.github.io/aria-practices/#aria_landmark. Screen readers all
have a way to navigate by landmarks
https://w3c.github.io/aria-practices/#aria_landmark, which give you a
way to browse the page in a non-linear way. If the navigation is in a
proper , that will make it skippable.
A big caveat here is that landmark navigation is quite an advanced
skill for screen reader users. Designing for it alone is like designing for
power users alone.
https://webaim.org/projects/screenreadersurvey9/#landmarks highlights
some of this but WebAIM does skew toward the advanced user, so reality is
probably even more dramatic
This complexity might be a reason for in-distinguished design pattern when
referencing existing libraries and when it comes to focus management.
in opposed to side navigation, popup menu has clear visual indication of
it being a composite widget. lack of such clear visual encapsulation may
confuse sighted keyboard users trying to navigate side navigation by
tabbing.
I suggest featuring opt-in / out to side navigation keyboard focus
management

authors may choose whether focus management should be enabled if
navigation list is large and can become tedious to step through
enabling focus management should affect design to reflect clear
visual indication of the side navigation component
alternatively document clear guidelines reflecting the above caveats
when opting-in to focus management

@yinonov https://github.com/yinonov You suggest that focusing on the
sidenav will affect the design. What do you want it to look like? Do you
have an example for that?
@jshenkman https://github.com/jshenkman @AyalaBu
https://github.com/AyalaBu
—
Reply to this email directly, view it on GitHub
https://github.com/Vonage/vivid-3/issues/200#issuecomment-1180321730,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZMYI5M3O4FVMQADKWTTSX3VTQECXANCNFSM5OREXCLQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Permission Node to Control Membership of Specific Group

Hello,
Thank you for actively maintaining LuckPerms! I've migrated my server from PermissionsEx to LuckPerms.
When I used PermissionsEx, I was able to allow a person or group to add or remove people from a specific group using PermissionEx's group-specific permission node.
However, that kind of permission node doesn't seem to exist in LuckPerms.  There are groups where the head of the group can add or remove members from (for LWC's group chest protection functionality), but currently, I have to give all of my moderators all permissions to add or remove members from every permission groups (which is dangerous, but I trust my staff team to not abuse permission groups possibly by adding themselves to an admin group) until I can get time to write up another special plugin to hook into LuckPerms API.
Will the group membership management feature be added?  It was useful while I used PEx.
Thank you!
~Simon

Such feature already exist, but it is disabled by default.
https://github.com/lucko/LuckPerms/wiki/Argument-based-command-permissions
It's quite a lot more in-depth than the system provided by PEX, and allows for much more customization. However, it's quite difficult to understand, and therefore disabled by default. :)


chore(merge-back): 2.66.0

See CHANGELOG

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 0ae4e65aed26c86bcdd72a9b019317dd22d170d5
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


pretrained_model_dir not implemented

layers/common_hparams.py mentions a hyperparameter "pretrained_model_dir":
"Directory containing a checkpoint for a pretrained model. This will only be used if a new run is being started. Parameters not found in the pretrained model will be randomly initialized. Superfluous parameters in the pretrained model will be ignored."
It sounds like it could be useful, however, as far as I can tell, the hyperparameter is not actually hooked up anywhere. The name of the parameter does not appear anywhere else in the sources of tensor2tensor, tensorflow, or tensorflow_estimator.
Is this feature obsolete or not yet implemented?

maybe option warm_start_from is what you need;

Possibly, but that's not the point.

@ekuznetsov139  @lukaszkaiser  Any update on this?

I don't believe this repo is active any more.

@ekuznetsov139 Thanks pal, for the info and time.


Ledger.to_list returns removed accounts

Some background on ledger mask implementation: A ledger mask (attached) stores all the accounts that were involved in a transaction applied to it and this includes newly created accounts, modifying any existing accounts that were added to the mask's ancestors. Ledger.to_list applied to a mask returns all the account state corresponding to the merkle root of the mask which includes modified accounts from the mask itself and all the other accounts from its ancestry.
Applying a transaction to a mask does not affect the state of parent masks. However, removing an account removes the account from the parent mask if it wasn't present in the child mask.
Bug:
When undoing a transaction that was applied to a parent mask, the current undo implementation undoes any balance changes to the involved accounts and then removes any accounts that were created as part of the transaction. Since the balance update was performed first all the accounts are added to the masks state (which were previously only in the parent's state). Removing those newly created accounts will now only remove it from the child mask and not from the parent mask. Since the parent mask still has these accounts, Ledger.to_list (or Masking_merkle_tree.to_list)on the mask returns the accounts that were deleted and a ledger creates using of this account list is not the same as the one represented by the mask.
There are two issues here:

Undoing a transaction causes the issue described above
Should removing an accounts from a mask (Masking_merkle_tree.remove_accounts_exn) be delegated to the parent mask? This will cause inconsistencies since we chain masks in transition frontier and each mask represents the staged ledger of a block

Proposed fix:
When undoing a transaction, do not delete any accounts from the parent mask. Keep track of any deleted accounts in a mask's state and not fetch those when performing a get or to_list operation on the mask.
This change might have a significant impact since it'll affect many of the mask operations. Currently we do not use Ledger.undo anywhere and so this might not be high priority.
This investigation came about when I was trying to export snarked ledgers (#8844) by undoing staged transactions on staged ledger. However, undoing staged transactions was taking almost the same time ( ~15-20 seconds on my machine, sometimes more) as redoing proven transactions on root snarked ledger and so decided to go with redoing the transactions

It is used in the function merkle_root_after_user_command_exn which is in turn used only in tests in transaction_snark.ml. We'll could move all the undo functions to a test module or update the tests to not use it. The latter is probably better since we won't have to main the undo functions

We've removed ledger undo. Closing.


Doesn't work with Link Time Optimization

When I pass -flto to Compiler options, the Compiler output is Compiled ok, but Assembly output is empty.

Thanks. This has been on my todo list for a long while but I've yet to bite
to bullet and rearchitect GCC explorer to work with binary output instead
of the text output it currently uses.
On Mon, Oct 26, 2015 at 11:14 PM, Alexander Riccio<EMAIL_ADDRESS>wrote:

When I pass -flto to Compiler options, the Compiler output is Compiled ok,
but Assembly output is empty.
—
Reply to this email directly or view it on GitHub
https://github.com/mattgodbolt/gcc-explorer/issues/88.

Fixing this would also allow fixing #25

Please try again now. LTO is now supported, though do note that you'll need to write a main() that actually calls your test code else you'll end up with a xor eax,eax and nothing else.  Something like http://goo.gl/CMuwb1


Fix for install issue where bigquery not installed

When installing EODataDown via Docker an error occured:'
from google.cloud import bigquery
ModuleNotFoundError: No module named 'google.cloud'

This fix does a pip install to fix this.


DBus reason of closing

Please, do not ignore this value here: https://github.com/hoodie/notify-rust/blob/3ab49e7f2e04d817ed12aef6eb2dc65e2b4f727e/src/xdg/dbus_rs.rs#L233
According to the spec: https://specifications.freedesktop.org/notification-spec/latest/ar01s09.html

The second param it's the only way to handle click on notification itself

oh cool, thanks for pointing this out, I hadn't noticed that yet

@tonyshkurenko how about this?

actually, since you mention "The second param it's the only way to handle click on notification itself" what Desktop environment are you using? because the under KDE at least clicking on the notification triggers the "default" action".

I tested on xfce4 and gnome. Thanks for your help!

thank you for pointing this out

I hadn't realized this at the time, but why do you even use notify_rust::handle_action? there is .wait_for_action()
I was even thinking about deprecating the free function api, is there any good reason not to?


VPC Lattice Service

What problem are you facing?
I am attempting to implement a Kubernetes API Gateway via the aws-application-networking-k8s controller. This uses VPC lattices in its implementation.
What could help solve your problem?
It seems like Terraform has an implementation, so I am assuming it can be plugged into the relevant provider?

Unfortunately no, not in provider-upjet-aws. The resource you linked to is in terraform-provider-awscc, which is different than terraform-provider-aws. In order to support the resource, one should create a new Crossplane Upjet provider, based on terraform-provider-awscc.


Question : how to output video to binary data

how to use this sdk to output transcoded video to binary data and save it to python variable ?
Thank you

https://github.com/kkroening/ffmpeg-python/blob/master/examples/README.md#convert-video-to-numpy-array

Thanks for the reply


Ignore images within data-pagefind-ignore

Currently there is no ability to exclude images selected for the image meta data, this is mainly problematic when there is no image related to the content at which an image from the site design is selected instead.
I tried to exclude these images by putting them in a data-pagefind-ignore container expecting those images to be ignored but without success.
As alternative I'm overruling the image meta data with the automatically generated open graph image, but this prevents any other images from within the content to be selected.
<meta property="og:image" content="{{- $img.Permalink -}}" data-pagefind-meta="image[content]"/>

Hello! 👋
Hmm yes I see. It is intentional that data-pagefind-ignore only affects the indexing — for example the <head> is an implicit data-pagefind-ignore, but we still want to pluck filters and metadata out of it. In another case, I have sites where I wrap a sidebar navigation in data-pagefind-ignore, but some data inside that sidebar is useful for setting up a filter group.
I might look at expanding that attribute to take an argument. Then the current argumentless version would imply data-pagefind-ignore="index", and we could add a data-pagefind-ignore="all" which also omits filters and metadata.
How does that sound to you?

That would work, thanks.

Another thought here is that you can fall back to the open graph image when the content search has not provided any results, I don't think that this is something that can currently be configured.

Yes good call. If you're defining your own data-pagefind-meta then subsequent definitions will overwrite the earlier ones, but there isn't a configuration to have the auto-detected image take precedence.
One way to allow this would be adding some configuration to the Pagefind UI along the lines of
{
  image: ["image", "og-image"]
}

Where the UI tries to use those keys in order for the image. Which would let the default image stay as meta.image, and you could separately tag your open graph image as og-image. Then at the UI end it can fall back to the og-image if no auto image was found.

That could be a good approach, this meta data would also need to be ignored in the skipMeta in that case.

Hi @vanbroup  👋
Some fixes have landed in Pagefind v0.5.0 🎉

data-pagefind-ignore="all" has been implemented as described above
An alternate solution for fallback content was implemented, allowing you to tag your og image as data-pagefind-default-meta


Update service-connect-to-smartsheet.md

Typo fix

@stevea1 - thanks for submitting this edit!

merging now


Add support for MVC Areas

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.
We have an Asp.NET Core web application structured into seperate areas web dashboard which contains Razor pages and different area for web api. The problem is that Api versioning isn't supprted with Areas although apis can be used with areas and it's officially supported on the asp.net core using methods like MapAreaControllerRoute and using the Area attribute on the controller.
Describe the solution you'd like
Adding support for api versioning with areas using extension method like MapAreaControllerRoute for ex: MapVersionedAreaControllerRoute.
Additional context
No response

I'm not sure what you mean by:

The problem is that Api versioning isn't supprted with Areas

In what way?
API Versioning doesn't care if your controller is an area. Collation by area is a possible scenario, but it is not intrinsically supported. Combining versioned APIs and UIs in the application is supported, but it doesn't seem to be super common.
If you can explain a bit more about what you want to achieve and what is preventing that from happening, I can probably help flush out how to make it work. Samples of basic setup or a repro project would be quite beneficial as well.

Hello @commonsensesoftware. Thsnks for the reply.
Please check this sample project
When I make a request to this url using postman  I always get this exception back:
Microsoft.AspNetCore.Routing.Matching.AmbiguousMatchException: The request matched multiple endpoints. Matches:

ApiVersioningExample.Areas.Clients.Controllers.AccountController.Get (ApiVersioningExample)
ApiVersioningExample.Areas.Clients.Controllers.Account2Controller.Get (ApiVersioningExample)
   at Microsoft.AspNetCore.Routing.Matching.DefaultEndpointSelector.ReportAmbiguity(CandidateState[] candidateState)
   at Microsoft.AspNetCore.Routing.Matching.DefaultEndpointSelector.ProcessFinalCandidates(HttpContext httpContext, CandidateState[] candidateState)
   at Microsoft.AspNetCore.Routing.Matching.DfaMatcher.MatchAsync(HttpContext httpContext)
   at Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware.Invoke(HttpContext httpContext)
   at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.HttpsPolicy.HttpsRedirectionMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)

Thanks for the repro. I'll take a 👀

The problem is two-fold. First and foremost, you did not call AddMvc() on the IApiVersioningBuilder, which is required in 6.0+. Without that, only the basic services for Minimal APIs are added. The second problem is that your API controllers are not marked as such.
Most API authors that need/want API versioning do not mix and match API controllers and UI controllers (or code) in the same solution. If you control both sides, do you really need versioning? Maybe. Using both is a supported scenario, but there are some things to note. Before the days of Razor Pages, there were only controllers. Fundamentally, there is almost no different between ControllerBase and Controller. You don't even need those types to create a controller. A controller is just a controller. This is problematic if you mix UI controllers with API controllers. How can you tell the difference? Most people don't want the UI controllers to be versioned (but in rare cases they do 🤷🏽).
Many years back, the IApiControllerFilter and IApiControllerSpecification services were added to address this ambiguity. When the API Behaviors feature was released, you opt in using the [ApiController] attribute. This presents a simple, straight forward specification to determine which controllers should be considered APIs. There is a built-in specification for it and it's registered by default. Your controllers do not have [ApiController], therefore, they are filtered out and are not considered by API Versioning. That is why you get ambiguous matches. API controllers normally use ControllerBase as the base class, but you can use Controller if you really want to.
You basically have two options...
Option 1
Apply [ApiController] to your API controllers.
// add api versioning with support for mvc (core)
services.AddApiVersioning(options => options.AssumeDefaultVersionWhenUnspecified = true)
        .AddMvc(); // this is NOT the same as 'services.AddMvc()`

[ApiController]
[Area("Clients")]
public class AccountController : Controller
{
    [HttpGet]
    [AllowAnonymous]
    public IActionResult Get() => Ok("Version 1");
}

Option 2
Replace the default IApiControllerFilter to perform no filtering. Technically, this would require specifying an API version for UI controllers, but since you are using Razor Pages they are not controllers and will be ignored.
// use built-in filter that does no filtering
services.AddTransient<IApiControllerFilter, NoControllerFilter>();

// add api versioning with support for mvc (core)
services.AddApiVersioning(options => options.AssumeDefaultVersionWhenUnspecified = true)
        .AddMvc(); // this is NOT the same as 'services.AddMvc()`

Chose either of those setups and things will begin to work as expected. 😉

Thanks for the detailed and well explained answer.
We aren't using controllers for UI, instead Razor pages are used for UI and versioned Controllers are for API only.
The problem with using ApiControllerAttribute is that I must add Route attribute to each controller and conventional routing can't be used, please check this question on Stack Overflow.

Oh, right. Gosh, it's been so long since I've seen anyone use convention-based routing, I forgot about that.
Just go with Option 2 then. If the NoControllerFilter doesn't work for you, you can replace it with your own implementation. You also have the option to add a new IApiControllerSpecification. The DefaultApiControllerFilter implementation just takes a sequence of registered IApiControllerSpecification instances and applies the filter by evaluating them in sequence.

Conventional routing is way better than attribute routing specially in large projects where there is tens or hundreds of controllers and a lot of razor pages organized into separate areas folders, instead of setting route attribute on each controller seperately we can with conventinal routing get that done in a few line of codes.
I have tried option 2 and it's working. Thanks for the answer.


CB-16012: Set encryption key for an existing env that does not yet have encryption enabled

CB-16012: Set encryption key for an existing env that does not yet have encryption enabled
CB-10502 introduced the encryption of Gcp Managed disks using Customer Managed Key. This feature is behind an entitlement "CDP_CB_GCP_DISK_ENCRYPTION_WITH_CMEK" and can be used for new environments.
This PR allows to set the encryption key for existing environments such that the new disks launched as part of new Datahubs will be encrypted with Customer Managed Key. All the previously launched disks/resources would remain unencrypted.
Validated these changes with :
Existing environment
    Using wrong key url
    Using disabled key
    Using enabled key valid url
Non - Existing environement

See detailed description in the commit message.

Cloudbreak changes are not required. editEnvironment CLI will be used to update the GCP environment parameters.
@topolyai5 Thank you for insights around this.


ShadowrunAnarchy: Fix French Karma boxes

Changes / Comments

Sheet: ShadowrunAnarchy
It is a bug fix
It doe not add functional enhancements or anything, only fix a margin issue in the french version of the sheet

I removed the margin-top: -2em that was hiding the Karma boxes labels, like this:

With this fix, the boxes look like this:

Character Sheet Info Roll20 Internal Use only.


build: Run executable tests with WasmKit

This PR adds a new product, WasmKit, which is a Wasm runtime used for running executable tests. And also configures test suites to be run on CI.
Note that the product is not shipped as a part of the toolchain, but is used only for testing purposes.

preset=buildbot_linux_crosscompile_wasm
@swift-ci Please test with preset Linux Platform

preset=buildbot_linux_crosscompile_wasm
@swift-ci Please test with preset Linux Platform

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test


Laravel: handle possible LogWatcher TypeError's

Based on reported issues in #306 (with thanks to @flc1125 for raising it).
Given we are close to moving to package 1.1.x and dropping support of Laravel 6-9, then it may be preferable to restore the previous behaviour and allow the log messages through. This would keep the package viable for the older Laravel versions.
Unfortunately, there's no log level filtering at that point but I think it's better to handle this gracefully.
The approach in #306 could also provide a stable v1, while we look to tackle this more elegantly in future.

If we plan to only support Laravel versions 10 + and above.
I think the Laravel dependency in composer.json can also be evaluated if it needs to be adjusted.
https://github.com/open-telemetry/opentelemetry-php-contrib/blob/2d2c37b7783f59967de79eba7cad8225e8662dd8/src/Instrumentation/Laravel/composer.json#L15

If we plan to only support Laravel versions 10 + and above.
I think the Laravel dependency in composer.json can also be evaluated if it needs to be adjusted.
https://github.com/open-telemetry/opentelemetry-php-contrib/blob/2d2c37b7783f59967de79eba7cad8225e8662dd8/src/Instrumentation/Laravel/composer.json#L15

Another message: Aside from the fix this time, I'm currently running fine on version 9.x.

Yes to v1.1 moving to support 10 + 11 👍
This package should still work down to Laravel 6; it is just hard to make progress when having to test so many end-of-life versions!

If we plan to only support Laravel versions 10 + and above.
I think the Laravel dependency in composer.json can also be evaluated if it needs to be adjusted.
https://github.com/open-telemetry/opentelemetry-php-contrib/blob/2d2c37b7783f59967de79eba7cad8225e8662dd8/src/Instrumentation/Laravel/composer.json#L15

Another message: Aside from the fix this time, I'm currently running fine on version 9.x.

Yes to v1.1 moving to support 10 + 11 👍
This package should still work down to Laravel 6; it is just hard to make progress when having to test so many end-of-life versions!

Very good plan. If multi-version compatibility needs to be considered, it is a challenge.
Currently, accelerating the advancement of Laravel in OTEL may be a more priority task to do. 💪🏻


1.0 HF conversion script fails on Python 3.8

Describe the bug
While the official recommended Python version for NeoX is 3.8, convert_v1.0_to_hf.py only works with Python 3.9 or later due to minor incompatibility (tested on Python 3.8.10).

TypeError: 'type' object is not subscriptable

Suggested change
Modify list[torch.Tensor] at the line 42 to List[torch.Tensor] (capitalized L)
Add import from typing import List

same here.
will it merge to main branch?

Hi, this should be fixed in #877 --can you share what commit you experience this error in?

@haileyschoelkopf sure!
https://github.com/EleutherAI/gpt-neox/commit/37195333b6805da4a4ecb341bae1da308045e60a

@cateto Try checking out the fix-convert-py3.8 branch and see if that works.

It looks like this got reverted in https://github.com/EleutherAI/gpt-neox/commit/29b968de2b522ad4919f33d671e3e79d4658948c by merge conflicts accidentally, I’ll re-fix this as soon as I’m back to a computer!

thank you 😸

This is fixed in #931 !


Ok so I've actually been loading Exports Tries slightly wrong for a long time

byte here is actually "terminal" size, not an 'if-else' thing, denotes size of terminal data BUT CAN STILL HAVE CHILDREN AFTERWARDS

Beautifully worded. Resolved in a5debb5ba4241a37e2579c96594950063ade6393


feat: setup react app using typescript

To get started we decided to build our WebAppGen using React and typescript together similar to the dekanat-app of the intutable project. Setup a sample project with this technologies

close with pr #39


Module path is encoded in the file path title

On the page<EMAIL_ADDRESS>

This was fixed and is no longer present.


Http4sMatchers gives a test failure for haveHeaders when the headers are correct

One of your tests, which presumably passes since your build is green (I haven't run it myself), fails if you copy its source code into a test case using Http4sMatchers, with a somewhat bizarre error. Here's the error:
[info] HelloWorldSpec
[error] x testing
[error]  the headers 'Headers(Content-Length: 0, Location: http://foo, Accept: audio/*)' is not the same as Headers(Content-Length: 0, Location: http://foo, Accept: audio/*) (HelloWorldSpec.scala:15)
[info] Total for specification HelloWorldSpec
[info] Finished in 1 second, 235 ms
[info] 1 example, 1 failure, 0 error

The source:
package com.example.http4stmp

import cats.effect.IO
import org.http4s._
import org.http4s.dsl.io._
import org.http4s.headers._
import org.http4s.testing.Http4sMatchers
import org.specs2.mutable.Specification

class HelloWorldSpec extends Specification with Http4sMatchers {

  "testing" >> {
    val location = Location(Uri.unsafeFromString("http://foo"))
    val resp = MovedPermanently(location, Accept(MediaRange.`audio/*`))
    resp must returnValue(
      haveHeaders(
        Headers(
          `Content-Length`.zero,
          location,
          Accept(MediaRange.`audio/*`)
        )))
  }

}

The build.sbt:
val Http4sVersion = "0.18.18"
val Specs2Version = "4.2.0"
val LogbackVersion = "1.2.3"

lazy val root = (project in file("."))
  .settings(
    organization := "com.example",
    name := "http4s-tmp",
    version := "0.0.1-SNAPSHOT",
    scalaVersion := "2.12.6",
    libraryDependencies ++= Seq(
      "org.http4s"      %% "http4s-blaze-server" % Http4sVersion,
      "org.http4s"      %% "http4s-circe"        % Http4sVersion,
      "org.http4s"      %% "http4s-dsl"          % Http4sVersion,
      "org.http4s"      %% "http4s-testing"          % Http4sVersion,
      "org.specs2"     %% "specs2-core"          % Specs2Version % "test",
      "ch.qos.logback"  %  "logback-classic"     % LogbackVersion
    ),
    addCompilerPlugin("org.spire-math" %% "kind-projector"     % "0.9.6"),
    addCompilerPlugin("com.olegpy"     %% "better-monadic-for" % "0.2.4")
  )

Related SO question.

Interesting.  This works, which is not far from what that matcher is doing.
    val location = Location(Uri.unsafeFromString("http://foo"))
    val resp = MovedPermanently(location, Accept(MediaRange.`audio/*`))
    resp.unsafeRunSync().headers must_== Headers(
      `Content-Length`.zero,
      location,
      Accept(MediaRange.`audio/*`)
    )

This looks like a bug.

The test was added on master, and the matcher was fixed.  But it buggily used reference equality in the 0.18 series.  #2101 will fix it.

Fixed by #2101.


[BUG] mcdev refresh -m triggeredSend fails with no keys provided error

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior

Expected Behavior
Refresh should have worked
Steps To Reproduce
No response
Version
7.6.0
Environment

OS:
Node:
npm:

Participation

[ ] I am willing to submit a pull request for this issue.

Additional comments
No response

damn it :D


Fix Travis builds and specify an upper bound for Keras version

keras-rl is no longer compatible with versions of Keras over 2.1.3 (as shown in #171). So before the necessary changes are merged, the master version should specify an upper bound for the version of Keras.

Builds for the master branch were not working. I looked into it and found that:

Jobs using Theano were failing due to the version of gym being used.
Jobs using Tensorflow were failing because of the way Conda installs scipy. (https://github.com/keras-team/keras-contrib/issues/211)

@RaphaelMeudec if you include also an upper bound for gym the builds will finally pass 😊

I've seen this, I'm just thinking about cleaning a bit the script (eg add requirements, stuff like that). I'll probably merge your PR by the end of the day! Thanks for taking some time on this!

Just released a new version which supports Keras v2.1.5 and Gym 0.10.3. I'm closing this PR. Thanks for pointing the issues !


about how to implement easy_localization consuming a webservice that returns the language

I have the following situation:
I consume a service that returns, for example:
{
"home": "Home",
"documents": "documents",
}
This would be for the translation into the Spanish language.
How could I implement easy_localization using that service that returns translations as the respective code is sent to it?"

Did you try it with the HttpAssetLoader?

I was able to solve it by making use of the property: "asset Loader" by creating my own class in the configuration. Since with the easy localization loader, it was not possible due to the incompatibility of other packages that I have installed.


ListView binding

Hi,
What is the correct way to do ListView item source and item click binding? Can you please give me a guide?
Thanks,
Albert

The way I usually do that is by using a binding, like so:
l:Binding="Target=Adapter, Path=MyObservableCollectionProperty, Converter={Ioc extrasPlatform:ListAdapterConverter}, ConverterParameter=@layout/MyLayoutForEachItemInCollection"

The converter does the heavy lifting of hooking up your collection to an adapter. You do, however, need to register the namespace of the converter in your bootstrapper, like so:
var aliasRegistry = Dependency.Resolve<INamespaceAliasRegistry, NamespaceAliasRegistry>(true);
aliasRegistry.RegisterNamespaceAlias("extrasPlatform", "Codon.UI.Elements", "Codon.Extras.Platform");

I'll devise a way to streamline the namespace registration in a future iteration.
To subscribe to an item click, add this to the ListView's l:Binding attribute:
Target=ItemClick, Path=HandleItemClick

In the end it will look something like this:
l:Binding="Target=Adapter, Path=MyObservableCollectionProperty, Converter={Ioc extrasPlatform:ListAdapterConverter}, ConverterParameter=@layout/MyLayoutForEachItemInCollection; Target=ItemClick, Path=HandleItemClick"

Hi,
Thanks for the detailed tutorial!
I have only one thing that I couldn't come across. It is the converter part:
Converter={Ioc extrasPlatform:ListAdapterConverter}
I am not sure if "Ioc" is a keyword or shortcut to your own ioc container, or is it a property on my ViewModel. I have my own ioc container that comes from the MVVMLight framework, which I don't want to replace at the moment.
Can you please clarify this one, because I cannot make it work. Big thanks!

Oh I just made it work. I registered the NamespaceAliasRegistry to Codon.Dependency and it is working now. I have it besides my own container because they do not interfere.

Are you using MVVMLight alongside Codon?

Yeah, I am using MVVMLight

If I were you I'd look at the feature overlap and reconsider. Package size and startup performance can be unduly affected by unnecessary assembly references.
I'd be surprised if you found anything in MVVMLight that Codon doesn't do better.

I'll look into this, thanks for the heads up.


Riak explorer 1.4.x not working

Riak cluster version: 2.1.4
With riak explorer 1.3.0 everything works well, but from the next version (1.4.0, 1.4.1) I get this error in the browser:

It looks like it can't find the crypto library. A few questions to help track down what might be gong on:

What OS and version are you on? Also, if you could double check you downloaded the matching distribution of Riak Explorer to your platform, because if not, finding the appropriate system crypto libraries will fail.

Could you try the following: From the riak_explorer directory where you have untarred the distribution, and with Riak Explorer stopped, do this:

First, run the Riak Explorer console, which will bring up an Erlang prompt:
$ ./bin/riak_explorer console

From the console, first try to load the crypto libraries by typing this:
application:ensure_started(crypto).

Erlang should respond with ok. If it doesn't, please share the output here.
Next, try this:
crypto:start().

It should either respond with ok or {error,{already_started,crypto}}. Here it might complain about a missing library. This will give us a clue as to what is missing. If you share the info about your platform, I can help you resolve that.
On my system, here is the output:
$ ./bin/riak_explorer console
config is OK
-config /Users/travisbhartwell/tmp/tmp/riak_explorer/data/generated.configs/app.2<IP_ADDRESS>.44.31.config -args_file /Users/travisbhartwell/tmp/tmp/riak_explorer/data/generated.configs/vm.2<IP_ADDRESS>.44.31.args -vm_args /Users/travisbhartwell/tmp/tmp/riak_explorer/data/generated.configs/vm.2<IP_ADDRESS>.44.31.args
Exec:  /Users/travisbhartwell/tmp/tmp/riak_explorer/bin/../erts-5.10.3/bin/erlexec -boot /Users/travisbhartwell/tmp/tmp/riak_explorer/bin/../releases/2.1.0/riak_explorer               -config /Users/travisbhartwell/tmp/tmp/riak_explorer/data/generated.configs/app.2<IP_ADDRESS>.44.31.config -args_file /Users/travisbhartwell/tmp/tmp/riak_explorer/data/generated.configs/vm.2<IP_ADDRESS>.44.31.args -vm_args /Users/travisbhartwell/tmp/tmp/riak_explorer/data/generated.configs/vm.2<IP_ADDRESS>.44.31.args              -pa /Users/travisbhartwell/tmp/tmp/riak_explorer/bin/../lib/basho-patches -- console
Root: /Users/travisbhartwell/tmp/tmp/riak_explorer/bin/..
Erlang R16B02_basho10 (erts-5.10.3) [source] [64-bit] [smp:8:8] [async-threads:64] [hipe] [kernel-poll:true] [frame-pointer]

Eshell V5.10.3  (abort with ^G)
(riak_explorer@<IP_ADDRESS>)1> application:ensure_started(crypto).
ok
(riak_explorer@<IP_ADDRESS>)2> crypto:start().
{error,{already_started,crypto}}

Hope this helps get to the bottom of things.

My os is macOS Sierra 10.12.2. I've downloaded this version riak_explorer-1.4.1-osx-10.11.tar.gz.
This is the result after running those commands:
*******:riak_explorer *******$ bin/riak_explorer console
config is OK
-config /Users/*******/Documents/Resources/orarmd/riak_explorer/data/generated.configs/app.2<IP_ADDRESS>.24.42.config -args_file /Users/*******/Documents/Resources/orarmd/riak_explorer/data/generated.configs/vm.2<IP_ADDRESS>.24.42.args -vm_args /Users/*******/Documents/Resources/orarmd/riak_explorer/data/generated.configs/vm.2<IP_ADDRESS>.24.42.args
!!!!
!!!! WARNING: ulimit -n is 256; 4096 is the recommended minimum.
!!!!
Exec:  /Users/*******/Documents/Resources/orarmd/riak_explorer/bin/../erts-5.10.3/bin/erlexec -boot /Users/*******/Documents/Resources/orarmd/riak_explorer/bin/../releases/2.1.0/riak_explorer               -config /Users/*******/Documents/Resources/orarmd/riak_explorer/data/generated.configs/app.2<IP_ADDRESS>.24.42.config -args_file /Users/*******/Documents/Resources/orarmd/riak_explorer/data/generated.configs/vm.2<IP_ADDRESS>.24.42.args -vm_args /Users/*******/Documents/Resources/orarmd/riak_explorer/data/generated.configs/vm.2<IP_ADDRESS>.24.42.args              -pa /Users/*******/Documents/Resources/orarmd/riak_explorer/bin/../lib/basho-patches -- console
Root: /Users/*******/Documents/Resources/orarmd/riak_explorer/bin/..
Erlang R16B02_basho10 (erts-5.10.3) [source] [64-bit] [smp:8:8] [async-threads:64] [hipe] [kernel-poll:true] [frame-pointer]

=INFO REPORT==== 2-Feb-2017::10:24:42 ===
    alarm_handler: {set,{system_memory_high_watermark,[]}}
Eshell V5.10.3  (abort with ^G)
(riak_explorer@<IP_ADDRESS>)1> application:ensure_started(crypto).
ok
(riak_explorer@<IP_ADDRESS>)2> crypto:start().
** exception error: undefined function crypto:start/0
(riak_explorer@<IP_ADDRESS>)3>

@es-lab I have observed dependency problems when upgrading versions in the past. If you are running via a dev build, try removing your deps directory and rerunning make and make deps to properly pull in the correct packages, and then try and rerun explorer.

@paultannenbaum I'm using this version riak_explorer-1.4.1-osx-10.11.tar.gz downloaded from github relases and there is no deps directory inside it.

@es-lab Sorry I'm just now getting back with you. I don't have 10.12 on my machine at the moment, so I had to get someone else to test for me.
I'm thinking the issue is with how I compiled Erlang on the build system. I have the openssl libraries installed view homebrew, and it links against that. If you don't have that installed, the necessary crypto libraries can't be loaded.
Could you test this, from the terminal in the RIak Explorer directory?
otool -L lib/crypto-3.1/priv/lib/crypto.so

It should have output similar to this:
lib/crypto-3.1/priv/lib/crypto.so:
	/usr/local/opt/openssl/lib/libcrypto.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1226.10.1)

Yours is probably showing something about libcrypto.1.0.0.dylib missing.
For now, the solution is to install HomeBrew and then install openssl with it:
brew install openssl

Then test Riak Explorer again and let me know if that works. I'll take a closer look and see if requiring users to have Homebrew and Openssl is the best solution long-term.

@travisbhartwell Sorry for the delay, your suggestion worked, now it works perfectly.
P.S.: In this 1.4.1 release should be some "UI updates", but actually I didn't see any updates, it looks the same as 1.3.x.


Consider automatically syncing Bazel and CMake builds

Currently, we have to maintain both builds manually, but it would be nice if that could be automated. E.g. IREE folks have a script that does this.

Is that script public? Can we link it here?

@kuhar Can you provide a brief overview of how this works in IREE?

Iree defines bazel and cmake functions to define targets. These generally have matching signatures so that we can generate cmake based off bazel, using a script: https://github.com/openxla/iree/tree/main/build_tools/bazel_to_cmake.
There are also some escape hooks that make this work we need some special cmake (e.g., preserve all cmake below/above line) or when we reference third-party targets whose target don't map 1:1 (e.g., https://github.com/openxla/iree/blob/571f28a87ba01482c8b24b87e4d2a1909ca61f1c/build_tools/bazel_to_cmake/bazel_to_cmake_targets.py#L102-L113).
I believe that @GMNGeoffrey should know the technical details best.

Some concrete example of matching targets below. Note that the cmake is derived from the bazel file, modulo the prefix:

https://github.com/openxla/iree/blob/571f28a87ba01482c8b24b87e4d2a1909ca61f1c/compiler/src/iree/compiler/InputConversion/StableHLO/Preprocessing/BUILD.bazel
https://github.com/openxla/iree/blob/571f28a87ba01482c8b24b87e4d2a1909ca61f1c/compiler/src/iree/compiler/InputConversion/StableHLO/Preprocessing/CMakeLists.txt

Yeah we've had pretty good success with this style of transformation. This makes the automated mapping almost entirely a syntactic thing. IMO it also makes for much more readable CMake files since you make them semi-declarative.
When we looked into this @ScottTodd found https://github.com/google/bazel-to-cmake, which attempts the much more ambitious task of fully mapping Bazel semantics to CMake. We found that it didn't actually work at all (and you can see that it only ever got one commit). Manually mapping Starlark rules to CMake functions makes the technically complicated thing manual and automates the tedious everyday dependency updates. IMO, barring a dedicated staffed team, this is the much more fruitful approach for this sort of thing.

Here's some more history on IREE's bazel_to_cmake conversion tool:

https://groups.google.com/g/iree-discuss/c/Y_Z2n5A-ofY (background, similar pain points, brainstorming, implementation progress)
https://github.com/openxla/iree/pull/556 (initial PR adding the converter tool)

As Geoffrey mentions, the heavy lifting is done by some declarative CMake functions that behave like Bazel rules (e.g. cc_library, cc_binary). IREE's versions of these are iree_cc_library.cmake, iree_cc_binary.cmake, etc.
We have documentation at the top of https://github.com/openxla/iree/blob/main/build_tools/bazel_to_cmake/bazel_to_cmake.py
The critical implementation detail matches the other bazel-to-cmake project: https://github.com/openxla/iree/blob/5c38bcc7068f486733584bd251c9596059c31b7f/build_tools/bazel_to_cmake/bazel_to_cmake_converter.py#L890

Each BUILD.bazel file is ran through exec (remember, Bazel uses starlark, which is close enough to Python), with a dictionary of functions to call for each top level function. For example, when a native_test function is encountered in a BUILD.bazel file, this block of code runs, parsing the parameters of the function and appending some text to the converted file.

I think we should consider moving the core bazel-to-cmake converter out of IREE and into another repo. We do want to avoid a big maintenance burden though. Stella already did some cleanup to make it generalize a bit and is using it in another OpenXLA project that depends on IREE. Obviously StableHLO can't take a dep on IREE though.


Fix typo in CMakePresets.json schema

This changes visible behavior
The following changes are proposed:

MinSizRel => MinSizeRel

The purpose of this change
The typo in the schema file prevents the use of presets if it contains in any configuration
     "cacheVariables": {
        "CMAKE_BUILD_TYPE": "MinSizeRel",
...
      }

@bluec0re thank you for the PR.  You can install the patch by downloading this artifact and using the "Install From VSIX" command in VS Code to select the VSIX file you downloaded.


Issue 531 configparser with encoding

Overview

Added encoding to configparser as suggested by issue #531.
Added supported python versions to setup.cfg (3.6, 3.7).

Related Issue / Discussion
Fix #531
Additional Information
Contribution Agreement
(as per https://github.com/geopython/pywps/blob/master/CONTRIBUTING.rst#contributions-and-licensing)

[ ] I'd like to contribute [feature X|bugfix Y|docs|something else] to PyWPS. I confirm that my contributions to PyWPS will be compatible with the PyWPS license guidelines at the time of contribution.
[x ] I have already previously agreed to the PyWPS Contributions and Licensing Guidelines

ping @kvold. Could also be added to the 4.2.x release.

Coverage remained the same at 74.26% when pulling b71af91ae4bb7aac95057dcb44467ca5e2503bcc on cehbrecht:issue-531-configparser-with-encoding into e942ada5a74d51fdeef38bbc65fe5092f06042ce on geopython:master.

travis py36 works ... but fails with netcdf issue for py37 ... not related to this PR.

It would be great if this could be added to an 4.2.x release. The only possible issue I can see is if someone was relying on the dynamic behavior of open() to read a non-utf8 and non-ascii config file.

Added this PR to the 4.2.x branch ... so it should be part of the next 4.2.5 releaase.


Python 35 36 support

Updated setup script to properly support newer versions of Cython

Is the cython version consistent with the installer?

Cool!

Yes. The Kivy 1.10 installer supports Cython 0.25.2 and we support it as
well now. I updated the Debian installer to match.
On Fri, Mar 9, 2018 at 2:12 PM jabdoa2<EMAIL_ADDRESS>wrote:

Is the cython version consistent with the installer?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/missionpinball/mpf-mc/pull/313#issuecomment-371946310,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALxozTy24vVtIhRlre68ut84Neaf1xjBks5tcvAvgaJpZM4Sk262
.


sni_cluster: add support for SNI substitutions

Description: This commit enables users to configure SNI substitutions in the SniCluster config. One can use this configuration to rewrite requested_server_name on connection metadata before forwarding it to the TCP Proxy.
Risk Level: Med
Testing: Added and updated tests
Docs Changes: N/A
Release Notes: Added a note about the configuration
/cc @rshriram

WE can't add this to tcp proxy because it does not have the notion of dynamically generated clusters within the proxy. We could create yet-another-filter for this, but the fact is this is coming from sni_cluster and nowhere else. So, from end user perspective, it will be very strange to see a rewrite cluster for dynamically generated key. Finally, if we use a separate filter, then we have to start using mutable filter state (so that the second filter can modify the value generated by sni-cluster). The whole mutable/immutable thing is a big discussion and I really don't want to step into that landmine and waste another 3 weeks bikeshedding. It will definitely get into some precedence and other issues that I wish to avoid by a long pole.
After considering all this, i suggested adding this in Sni_cluster itself as it clearly describes operations on the sni value before using it as the cluster name.

WE can't add this to tcp proxy because it does not have the notion of dynamically generated clusters within the proxy. We could create yet-another-filter for this, but the fact is this is coming from sni_cluster and nowhere else.

Don't assume only sni_cluster will generate the key, it might be true right now if we don't consider out-of-tree filters, but this could happen when we have more protocol sniffing filter as well. tcp_proxy processes that key so it is already aware of that. cc @ggreenway for tcp_proxy expertise here.

Finally, if we use a separate filter, then we have to start using mutable filter state (so that the second filter can modify the value generated by sni-cluster). The whole mutable/immutable thing is a big discussion and I really don't want to step into that landmine and waste another 3 weeks bikeshedding. It will definitely get into some precedence and other issues that I wish to avoid by a long pole.

It is already in mutable state, so a second filter could modify.
Btw, what is the actual use case for this, can you elaborate more? I'm also concerned about having the heavy regex matching and replace in every connection on data path.

Closing this in favor of an external filter (in Istio).


Make it clear that junit is only a test scope dependency

Only use maven dependencyManagement to control the version
to avoid unintended or implicit effects.
The true's are duplicated.

Thanks but I've quite concerned about the removal of the optional dependencies. They are indeed optional by design, it shouldn't be required by every user of REST Assured to have three different JSON parsing libraries in the classpath for example.

I totally agree.   This change doesn't change that at all.   That is specified in the dependency within each module and shouldn't be in the dependencyManagement also (which should just be for the version).

Oh thanks! Then I misunderstood.


docs: change bash to sh in markdown syntax

change bash to shas code blocks language identifier for shell commands as they don't have anything specific to bash

Thanks for your contribution!

@swift-ci please smoke test

@swift-ci please smoke test Linux platform

@swift-ci please smoke test Linux platform

@swift-ci clean smoke test Linux platform

⛵


[Feature Request] Make the update nag a little less naggy

Is your feature request related to a problem? Please describe.
The update nag is a bit too frequesnt - It's been daily for a week.
What is your ideal solution to the problem?
Making it weekly or a command to tell it to chill a bit would be dope.
How would this feature be used?
Maybe the update nag tells you can react with a thumbs down to its message, and if you do, it snoozes for a few weeks unless the update is security related.
Additional Info
Ironically I will need to update my bot in order to get this feature.
I lied when I ticked "I am running the latest version of the bot" because by definition this cannot be true.
Checklist

[X] I have checked the documentation to make sure this feature doesn't already exist
[X] I have searched for similar feature requests
[X] I have confirmed that my requests is not on the list of things that will not be added
[X] I am running the latest version of the bot:

You can stop update alerts by:

Setting updatealerts to false in the configuration, which is not recommended.
Updating to the latest release
or 3. blocking the bot :^)


x/tools/go/analysis: asmdecl false positives on AVX2 instructions

go vet raises invalid VPBROADCASTD of mask+24(FP); uint32 is 4-byte value for VPBROADCASTD mask+24(FP), Y0.
Skimming the asmdecl source, this is because argument size is determined by the final character of the opcode (plus some special cases), but when AVX2 instructions were added, the decision was made to use the actual (ie: Intel's) name of each instruction.  I suspect there are other opcodes that also trigger false positives in this way.

Could we get a reproducer code? What would also help is to have the opening comment follow the default issue formatter.

Could we get a reproducer code? What would also help is to have the opening comment follow the default issue formatter.

I narrowed down and root caused the issue because presumably using a giant wall of assembly isn't all that fun, but ok.
What version of Go are you using (go version)?

go version go1.16.6 linux/amd64
go version go1.17rc2 linux/amd64

Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
This is irrelevant, it's a logic bug in asmdecl.
What did you do?
Ran go vet on an assembly file that contains a memory-sourced VPBROADCASTD (VEX.256.66.0F38.W0 58 /r VPBROADCASTD ymm1, xmm2/m32), where there's size information available for the m32 due to it being an argument (mask+24(FP, mask is a uint32).
https://github.com/oasisprotocol/curve25519-voi/blob/4da56de5ed176dc827391508a16115b250ca91ad/curve/edwards_vector_amd64.s#L201
What did you expect to see?
No asmdecl vet errors regarding VPBROADCASTD.  There's other things that asmdecl complains about in the file that are unrelated (the code generator I'm using so I need to copy-paste  · less, is incorrect).
What did you see instead?
./edwards_vector_amd64.s:201:1: [amd64] vecConditionalSelect_AVX2: invalid VPBROADCASTD of mask+24(FP); uint32 is 4-byte value
What's wrong
https://github.com/golang/tools/blob/758a1a1db799319be7c0ac33d911e0e5107e48d3/go/analysis/passes/asmdecl/asmdecl.go#L717 is the generic catch-all for opcodes that end with D, following the plan 9 convention.  AVX2 opcodes even in Go's assembler use Intel's naming, so the D means "broadcast dword integer".

Maybe related: #39220.

FWIW, I would be fine with adding this as a special case to asmdecl, either to recognize the AVX2 instructions, or to recognize the Yn registers.

For the specific VPBROADCASTD case that I am hitting, I believe this needs the former?  asmdecl is complaining that I am passing it a GP register that contains the address of a uint32 (xmm2/m32).  It is fine with the YMM register I am broadcasting into.
  // ie: Something like this should be "fine", but it costs an extra instruction.
  VMOVD mask+(24)FP, X0
  VPBROADCASTD X0, Y0


[ffmpeg] ld: warning: could not create compact unwind

When I try to link to the ffmpeg libraries I get the following linker warnings:
2021-08-18T22:06:41.3473950Z ld: warning: could not create compact unwind for _ff_cfhd_init_vlcs: stack subq instruction is too different from dwarf stack size
2021-08-18T22:06:41.3475230Z ld: warning: could not create compact unwind for _ff_rl_init_vlc: stack subq instruction is too different from dwarf stack size

The linking itself succeeds and so far it works as well.
How can I get rid of the warnings?
ffmpeg is build with these options
-- Building Options: --enable-pic --disable-doc --enable-debug --enable-runtime-cpudetect --enable-asm --enable-x86asm --enable-gpl --disable-ffmpeg --disable-ffplay --disable-ffprobe --enable-avcodec --enable-avdevice --enable-avformat --enable-avfilter --enable-postproc --enable-swresample --enable-swscale --disable-libass --disable-avisynth --disable-bzlib --disable-libdav1d --disable-libfdk-aac --disable-libfontconfig --disable-libfreetype --disable-libfribidi --disable-iconv --disable-libilbc --disable-lzma --disable-libmp3lame --disable-libmodplug --disable-cuda --disable-nvenc --disable-nvdec  --disable-cuvid --disable-ffnvcodec --disable-opencl --disable-opengl --disable-libopenh264 --disable-libopenjpeg --disable-openssl --disable-libopus --disable-sdl2 --disable-libsnappy --disable-libsoxr --disable-libspeex --disable-libssh --disable-libtensorflow --disable-libtesseract --disable-libtheora --disable-libvorbis --disable-libvpx --disable-libwebp --disable-libx264 --disable-libx265 --disable-libxml2 --disable-zlib --disable-vdpau --extra-cflags="-isysroot /Applications/Xcode_12.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk" --extra-ldflags="-isysroot /Applications/Xcode_12.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk"  --enable-cross-compile --target-os=darwin --arch=x86_64 --extra-ldflags=-arch --extra-ldflags=x86_64 --extra-cflags=-arch --extra-cflags=x86_64 --extra-cxxflags=-arch --extra-cxxflags=x86_64 --pkg-config-flags=--static

Environment

OS: osx
Compiler: AppleClang <IP_ADDRESS>00032

To Reproduce
Steps to reproduce the behavior:

./vcpkg install ffmpeg
link mixxx application

Here is the workflow run building Mixxx
https://github.com/mixxxdj/mixxx/pull/4225/checks?check_run_id=3365982171
And here the Run building vcpkg
https://github.com/mixxxdj/vcpkg/runs/3332915409
Expected behavior
No warning should be logged
I would be great if someone has an idea how to fix the issue or debug it more.
Thank you.

Are you sure ffmpeg was built as 64 bit? https://stackoverflow.com/questions/39598302/ld-warning-stack-subl-instruction-is-too-different-from-dwarf-stack-size-on-os

At least the --arch=x86_64 option is set. See above.

I am not sure it actually does get set:
--arch=x86_64 --extra-ldflags=-arch --extra-ldflags=x86_64 --extra-cflags=-arch --extra-cflags=x86_64 --extra-cxxflags=-arch --extra-cxxflags=x86_64

--extra-ldflags is set twice, first to -arch then to x86_64. The same happens for --extra-cflags and --extra-cxxflags. Perhaps only the first one has an effect.

Hi @daschuer
Thanks for posting this issue.
Do you encounter this issue on your local machine or on the CI https://github.com/mixxxdj/mixxx/pull/4225?
Could you please try to pass the compiler option to rebuild?
LDFLAGS="-Wl,-no_compact_unwind"

This linker flag removes the warning. See https://github.com/daschuer/mixxx/runs/3399675678
I encounter the issue on the GitHub CI. I have unfortunately no access to a local macOS machine.
Can you give some insights?

Why the linker only complains about these two ffmpeg functions? Are other warnings suppressed or are only these two affected?
For my feeling the linker flag is a workaround since it affect all functions, right?
It seems to cause issues with the exception stack  see: https://developer.apple.com/documentation/xcode/addressing-language-exception-crashes
Crawling in GitHub I have found other solutions where the warning is silenced with LDFLAGS="-Wl,-w"
What is the recommended Fix in case of this warning by the supplier?
Is there something official where the  "no_compact_unwind" flag is explained?

By the way, when I do not link to ffmpeg the warning disappears. What could be the cause? It there something special with it?

@daschuer Sorry but I didn'f found the error messages you mentioned in https://github.com/daschuer/mixxx/runs/3399675678, can you please extract it and provide me a log file?
Also, can you get the config logs and install logs in your ci system?
Thanks.

https://github.com/daschuer/mixxx/runs/3399675678 is the run with LDFLAGS="-Wl,-no_compact_unwind"
The original error can be found here:
https://github.com/mixxxdj/mixxx/pull/4225/checks?check_run_id=3403021507
The logs from the vcpkg build run can be downloaded as artifact here:
https://github.com/mixxxdj/vcpkg/runs/3332915409
Thank you for having a look.

By default ffmpeg is build  with gcc. I have patched the build.sh.in to use clang but the warning remains, so it is not a compiler bug.
If I disable the dfhd encoder and decoder, one warning disappears. So it seems to be an issue with the function itself.
Both function have in common that they allocate big arrays on the stack. I guess that this causes the linker to fail applying compact unwind.
I will report the issue upstream, maybe they can suggest a workaround.

https://trac.ffmpeg.org/ticket/9399

Close this PR until upstream fixes this.

Should be fixed with https://github.com/FFmpeg/FFmpeg/commit/e6d89d0efd9194198d9964e47bf428be222594ea


Visualisation evaluation failed: Type error: expected a function, but got 100000 (Integer) resulting in Error

Discord username
No response
What type of issue is this?
Permanent – Ocurring repeatably
Is this issue blocking you from using Enso?

[ ] Yes, I can't use Enso because of this issue.

Is this a regression?

[ ] Yes, previous version of Enso did not have this issue.

What issue are you facing?
While recreating 101 Enso script I have encountered wierd behaviour when changed the original range of 0 to 100 to some greater numbers (1000, 10000, 100000).
Multiple warnings:
[warn] [2023-03-09T17:19:31.685Z] [enso] Visualisation evaluation failed: Type error: expected a function, but got 100000 (Integer)..
resulting in error:
[error] [2023-03-09T17:19:37.349Z] [org.enso.languageserver.requesthandler.visualisation.ModifyVisualisationHandler] Request [Number(120)] timed out.
Starts at 2:05 mark in the vid:
https://user-images.githubusercontent.com/108271897/224111623-ef024b13-a5d6-4f0d-8c62-64ae1ff642b6.mp4
log:<PHONE_NUMBER>_shareX.txt
Expected behaviour
User should be able to enter almost any reasonable range w/o errors.
How we can reproduce it?
See the video
Screenshots or screencasts
attached in the description of the issue
Enso Version
Build: Nightly Release #842
Browser or standalone distribution
Standalone distribution
Browser Version or standalone distribution
standalone
Operating System
Windows
Operating System Version
11pro
Hardware you are using
i9 12th gen / discrete gpu

@xvcgreg This is also a glitch, right? Probably warrants a separate ticket

@xvcgreg This is also a glitch, right? Probably warrants a separate ticket

I believe we have a ticket for broken node links already filed. But found just this #5405 mysterious one.

@xvcgreg are you sure you linked the correct ticket? This one is a placeholder for the future feature we will need to add...

@xvcgreg are you sure you linked the correct ticket? This one is a placeholder for the future feature we will need to add...

@sylwiabr I'm not sure - as I wrote that's the only one I found treating on IO of nodes
@farmaazon Can you recall such ticket?

@xvcgreg https://github.com/enso-org/enso/issues/5095 here it is - you were even an author of it

@xvcgreg #5095 here it is - you were even an author of it

thanks!

We need to isolate where this exception is coming from and then adjust the viz code in Standard.Visualization.

@jdunkerley I'm looking into this

k thanks @hubertp

@farmaazon Feel free to re-assign back to me if you don't think this is not a duplicate.

It seems fixed on newest nightly (which features "literal" suggestions).


Translations of parsers error messages

Messages from the parsers are in english.
For instance : https://github.com/geostyler/geostyler-sld-parser/blob/master/src/SldStyleParser.ts#L976
   throw new Error('MarkSymbolizer cannot be parsed. Unsupported WellKnownName.');

These messages sometimes have to be displayed for the end user who may be using a UI in another language. It would be great to make the parsers more multilingual.
In addition, the message may contain the "Unsupported WellKnownName". (see #924)

Done in #928


New file reader

Description
In long term, we want to be able to reuse ffi::ir_decoder for clp side ir_decoding and ir->archive compression. However, the current ffi::ir_decoder uses it's own class interface which doesn't easily fit with CLP source code. In addition, the ir->archive will require seek_back functionality on the fileReader that is not supported with our s3 layer.
This PR refactors IrBuffer to be a derived class of ReaderInterface, and also introduces a new BufferedFileReader to customized support seek back. As a side effect of the change, the compression code is also simplified,
Validation performed
Added UnitTest for BufferedFileReader and all UnitTest passed
Benchmark
simple benchmark for bufferedFileReader performance: compressing single 10gb hadoop log for 5 times and take the average
clp_ref: 66.956s
clp_buffered_file_reader: 64.871s
Simple benchmark to measure the improvment of ir_decoding from using string view:
BufferReader + string_copy: 86.707s
BufferReader + string_view:  77.331s
BufferedFileReader + string_copy : 88.573 s
BufferedFileReader + string_view:   81.250 s

A future PR should replace the pointer arithmetic with gsl::span

TODO: use gsl::span to replace pointer arithmetic


Feature/socket connection pooling

lets try this again... I changed the IP used in UDP testing to a resolvable one.
This pull request adds multiprocess/thread safety, and add tests (with 100% coverage) to test datagram send/receive.
Connection pooling is implemented with queue.Queue.
The pool is specified as an argument to Socket.__init__. The pool is populated as calls to request are made, after pool maxsize has been reached, any new threads/processes that enter into request will get from the connection pool, and block until a new socket is re-opened (or created).
Also, send_receive is performed based on the value of proto, all datagram sockets will call _dgram_send_and_receive which uses a buffer size, since user datagram sockets have no concept of end of message, you have to know how much data is needed when using user datagrams. A future feature can be to make sure datagrams receive all remaining data.
And, streaming sockets use _stream_send_and_receive which use the already implemented data transfer pattern before this pull request.

I guess github is blocking all NTP servers :(, I'll figure something out and re-run the test.

I made a change to the udp test, since I think github/travis blocks NTP UDP over port 123, lets try DNS UDP over port 53.

Looks great! Thanks!


Using Bastion to access the jump host via SSH

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az network bastion ssh
Errors:
The command failed with an unexpected error. Here is the traceback:
The extension ssh is not installed.
Traceback (most recent call last):
  File "/opt/az/lib/python3.10/site-packages/knack/cli.py", line 233, in invoke
    cmd_result = self.invocation.execute(args)
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 663, in execute
    raise ex
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 697, in _run_job
    result = cmd_copy(params)
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 333, in __call__
    return self.handler(*args, **kwargs)
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/opt/az/lib/python3.10/site-packages/azure/cli/command_modules/network/custom.py", line 8263, in ssh_bastion_host
    _test_extension(SSH_EXTENSION_NAME)
  File "/opt/az/lib/python3.10/site-packages/azure/cli/command_modules/network/custom.py", line 8191, in _test_extension
    ext = get_extension(extension_name)
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/extension/__init__.py", line 340, in get_extension
    raise ExtensionNotInstalledException(ext_name)
azure.cli.core.extension.ExtensionNotInstalledException: The extension ssh is not installed.

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az network bastion ssh --auth-type {} --name {} --resource-group {} --username {} --ssh-key {} --target-resource-id {}

Expected Behavior
Environment Summary
Linux-5.19.0-38-generic-x86_64-with-glibc2.35, Ubuntu 22.04.1 LTS
Python 3.10.8
Installer: DEB

azure-cli 2.43.0 *

Extensions:
azure-devops 0.26.0
aks-preview 0.5.123

Dependencies:
msal 1.20.0
azure-mgmt-resource 21.1.0b1

Additional Context

Thank you for opening this issue, we will look into it.

@flavian-anselmo Thanks for reaching out to us and reporting this issue. The error message talks about the missing ssh extension. Could you please install the ssh extension using the below CLI command and then run the bastion command again ?

az extension add -n ssh

    az extension add -n ssh

it worked


How to send mavlink 2 messages?

Hello , I am trying to use dronekit to send a 'obstacle_distance_encode' message, however I am unable to do this since it says mavlink object has no attribute with such name.  It seems to fix this I need to connect or somehow use mavlink 2, is there a way to do this in dronekit?

did you solve it?


Security Issues

Few security bugs found in your app. Any worth testing them out?

@astoykov1 can you clarify which security issues?


SSL

[Enter feedback here]

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

ID: 68c07ba9-8f4f-c051-c945-16742c7fe409
Version Independent ID: 61c4da19-8278-4764-05a4-000653932b83
Content: Provision Device Portal with a custom SSL certificate - UWP applications
Content Source: windows-apps-src/debug-test-perf/device-portal-ssl.md
Product: uwp
Technology: deployment
GitHub Login: @Karl-Bridge-Microsoft
Microsoft Alias: kbridge
$IssuedTo = "localhost"
$Password = "PickAPassword"
$OutputPath = "c:\temp"
$rootCA = Import-Certificate -FilePath C:\temp\WdpTestCA.cer -CertStoreLocation Cert:\CurrentUser\My\

Create SSL cert signed by certificate authority
$IssuedToClean = $IssuedTo.Replace(":", "-").Replace(" ", "_")
$FilePath = $OutputPath + $IssuedToClean + ".pfx"
$Subject = "CN="+$IssuedTo
$cert = New-SelfSignedCertificate -certstorelocation cert:\localmachine\my -Subject $Subject -DnsName $IssuedTo -Signer $rootCA -HashAlgorithm "SHA512"
$certFile = Export-PfxCertificate -cert $cert -FilePath $FilePath -Password (ConvertTo-SecureString -String $Password -Force -AsPlainText)

Hi @mediagatewizard - can you clarify your issue? You can also use our Open Publishing platform to submit PRs with your suggested updates. Just click the Edit button near the top of the topic and you can use the GitHub editor. Thanks!

If any new actionable items arise, let us know either through a new Issue or directly on this thread. In the meantime, I'll be closing this Issue. Thanks once again for submitting your feedback!


Log into file, not into console

At least for most of the less important messages.
Pros:

less clutter in console
speed up program, especially on start up

Agree.

will be available with next PR


Azure CLI classic task seems to only evaluate first line in 'inline script' mode

I'm under the impression that the Azure CLI task ( in the classical editor ) - in 'inline script' mode, evaluates only the first line of the script in Azure.
Steps to recreate:

Create classic pipeline
Add Azure CLI task
Add two lines of 'az group list' for instance:

Observe output. In my case - I downloaded RAW logs - and here are the interesting bits:

	2019-11-20T10:04:22.1675908Z ##[section]Starting: Azure CLI
	2019-11-20T10:04:22.1783470Z ==============================================================================
	2019-11-20T10:04:22.1783967Z Task         : Azure CLI
	2019-11-20T10:04:22.1784150Z Description  : Run Azure CLI commands against an Azure subscription in a Shell script when running on Linux agent or Batch script when running on Windows agent.
	2019-11-20T10:04:22.1784533Z Version      : 1.156.0
	2019-11-20T10:04:22.1785114Z Author       : Microsoft Corporation
	2019-11-20T10:04:22.1785307Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/deploy/azure-cli
	2019-11-20T10:04:22.1785543Z ==============================================================================
	2019-11-20T10:04:22.5750301Z [command]C:\windows\system32\cmd.exe /D /S /C ""C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin\az.cmd" --version"
	2019-11-20T10:04:44.5431683Z WARNING: You have 2 updates available. Consider updating your CLI installation.
	2019-11-20T10:04:44.5432788Z azure-cli                         2.0.75 *
	2019-11-20T10:04:44.5433598Z
	2019-11-20T10:04:44.5434104Z command-modules-nspkg              2.0.3
	2019-11-20T10:04:44.5434513Z core                              2.0.75 *
	2019-11-20T10:04:44.5435524Z nspkg                              3.0.4
	2019-11-20T10:04:44.5435974Z telemetry                          1.0.4
	2019-11-20T10:04:44.5436334Z
	2019-11-20T10:04:44.5436747Z Extensions:
	2019-11-20T10:04:44.5437170Z azure-devops                      0.13.0
	2019-11-20T10:04:44.5437547Z
	2019-11-20T10:04:44.5437963Z Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
	2019-11-20T10:04:44.5438557Z Extensions directory 'C:\Program Files\Common Files\AzureCliExtensionDirectory'
	2019-11-20T10:04:44.5438895Z
	2019-11-20T10:04:44.5439440Z Python (Windows) 3.6.6 (v3.6.6:4cf1f54eb7, Jun 27 2018, 02:47:15) [MSC v.1900 32 bit (Intel)]
	2019-11-20T10:04:44.5439766Z
	2019-11-20T10:04:44.5440099Z Legal docs and information: aka.ms/AzureCliLegal
	2019-11-20T10:04:44.5440439Z
	2019-11-20T10:04:44.5440712Z
	2019-11-20T10:04:44.5441702Z Setting AZURE_CONFIG_DIR env variable to: D:\a\_temp\.azclitask
	2019-11-20T10:04:44.5442565Z Setting active cloud to: AzureCloud
	2019-11-20T10:04:56.8798559Z D:\a\1\s>az group list
	2019-11-20T10:04:59.1661337Z [
	 ... looks good
	2019-11-20T10:04:59.1733516Z ]
	2019-11-20T10:04:59.2803945Z [command]C:\windows\system32\cmd.exe /D /S /C ""C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin\az.cmd" account clear"
	2019-11-20T10:05:00.6450107Z ##[section]Finishing: Azure CLI

I'm running on the vs2017-win2016 agent. My buddy @rebremer figured out that on a Linux hosted agent, the problem does not occur. Futhermore - the YML that I tried also has no problems - although also runs on Linux:
trigger:
  - master

  pool:
    vmImage: 'ubuntu-latest'

  steps:
  - script: echo Hello, world!
    displayName: 'Run a one-line script'

  - script: |
      echo Add other tasks to build, test, and deploy your project.
      echo See https://aka.ms/yaml
    displayName: 'Run a multi-line script'

  - task: AzureCLI@2
    inputs:
      azureSubscription: 'Microsoft Azure Internal Consumption(5fcb0d36-846f-4721-86e9-47f6c43494fd)'
      scriptType: 'bash'
      scriptLocation: 'inlineScript'
      inlineScript: |
        az group list
        az group list

So could this be Windows specific ?

For some reason, it helps to write "call" in front of every line when running az commands on windows. Something to do with bash, it is slightly mentioned in the help popout for the inline script.

@rsitrifork is absolutely right here. For windows agent batch script whereas for Linux based agent shell script gets executed.  For batch files use the prefix "call" before every azure command.
For Azure CLI v1 version:

example for shell:
az --version
az account show
example for batch:
call az --version
call az account show

You can find details in the tooltip for the InlineScript field in the classic editor.

Hi @rsitrifork and @jalajmsft - thanks the response, and I'm sure that will solve the issue. I actually read that though and didn't consider it because of the 'for batch files, use ...'. I since I was doing an inline script it wasn't applicable. But you're wrapping the inline script in batch then I suppose.

Thanks !

Hey @jochenvanwylick thank you for your inputs, we will update the help text to avoid confusion. Closing this. Feel free to reopen/ open a new issue for further quires.