Getting "The request is not supported" while trying to execute docker run

Hi! I'm using Windows Server 2019 (1809, build 17763), with "Containers" feature enabled. Performed all the steps from README.md. When trying to execute
docker run --platform linux --rm -ti busybox sh
I get following error message:
Error response from daemon: failed to start service utility VM (createreadwrite): CreateComputeSystem 123aa681adc9fe7814322a95068e28911b4f42d887cd734fe3b3a02dc3b90203_svm: The request is not supported. (extra info: {"SystemType":"container", "Name":"123aa681adc9fe7814322a95068e28911b4f42d887cd734fe3b3a02dc3b90203_svm",  "Layers":null, "HvPartition":true, "HvRuntime":{"ImagePath":"C:\\Program Files\\Linux Containers", "LinuxInitrdFile":"initrd.img", "LinuxKernelFile":"kernel"}, "ContainerType":"linux", "TerminateOnLastHandleClosed":true}).
docker version
Client:
Version:           18.09.2
API version:       1.39
Go version:        go1.10.6
Git commit:        1ac774dfdd
Built:             unknown-buildtime
OS/Arch:           windows/amd64
Experimental:      false
Server:
Engine:
Version:          18.09.2
API version:      1.39 (minimum version 1.24)
Go version:       go1.10.6
Git commit:       1ac774dfdd
Built:            02/10/2019 04:13:25
OS/Arch:          windows/amd64
Experimental:     true
docker info
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 6
Server Version: 18.09.2
Storage Driver: windowsfilter (windows) lcow (linux)
Windows:
LCOW:
Logging Driver: json-file
Plugins:
Volume: local
Network: ics l2bridge l2tunnel nat null overlay transparent
Swarm: inactive
Default Isolation: process
Kernel Version: 10.0 17763 (17763.1.amd64fre.rs5_release.180914-1434)
Operating System: Windows Server 2019 Datacenter Version 1809 (OS Build 17763.316)
OSType: windows
Architecture: x86_64
CPUs: 2
Total Memory: 15.71GiB
Docker Root Dir: C:\ProgramData\docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: true
Insecure Registries:
<IP_ADDRESS>/8
Live Restore Enabled: false
Might be not related to LCOW, but still not sure, where shall I ask for help with this issue. Will appreciate any suggestions regarding possible root causes

This error comes from the image you're referencing not being compatible with the current OS you're running.
Since busybox is a linux image, you'll have to specify --isolation=hyperv in your run command. But I'm not sure this is fully supported yet.
I'm also fairly certain that Server 2019 is not officially supported with Docker EE engine, but you might try updating to 18.09.7 just to see, or try version 19.03.0-rc2 if you're feeling brave (but they're having some issues with the hash on the package file last I checked.)

Correction:
It may be related to the way that you're phrasing your run command. I discovered this the hard way.
For example:
docker run -d -p 9000:9000 --name portainer --restart always -v \\.\pipe\docker_engine:\\.\pipe\docker_engine -v E:\Portainer:C:\data portainer/portainer:windows1809-amd64

works. ... But
docker run -d --restart=always --mount type=npipe,source=\\.\pipe\docker_engine,destination=\\.\pipe\docker_engine --mount type=bind,source=E:\Portainer,destination=C:\data -p 9000:9000 --name portainer portainer/portainer:windows1809-amd64

doesn't.
I would try using different parameters or alternative parameters to what you have and see if changing something gives you the same errors.

I had the same issue on a clean win2019(1809) + docker(v19.03.2) + lcow (v4.14.34)
I enabled the hyper-v feature from server configuration manager, and restarted the server. the issue was solved.


split different gen config elements into files

Cuts up the massive pkg/generate/config/config.go file into separate
files for field, operation and resource. This patch contains no
functional changes; it is simply prep for work that will refactor the
FieldConfig and AdditionalFieldConfig structs.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Note to reviewers: I pushed this style-only patch separately from #599 to make it easier to review.


Dataset in Echarts 4 does not work properly with line series that have the areaStyle prop.

One-line summary [问题简述]
Dataset in Echarts 4 does not work properly with line series that have the areaStyle prop.
Version & Environment [版本及环境]

ECharts version [ECharts 版本]: 4.0.2
Browser version [浏览器类型和版本]: chrome 65
OS Version [操作系统类型和版本]: arch linux

Expected behaviour [期望结果]
With areaStyle prop, line series should have filled color from x axis to the line.
But now the base line turn to the line segment between the first data's coordinate to the last.
ECharts option [ECharts配置项]

option = {
  legend: {},
  tooltip: {
    trigger: 'axis',
  },
  dataset: {
    source: [
      ['order', '1', '2', '3', '4', '5', '6'],
      ['a', 41.1, 30.4, 65.1, 53.3, 83.8, 98.7],
      ['b', 86.5, 92.1, 85.7, 83.1, 73.4, 55.1],
      ['c', 24.1, 67.2, 79.5, 86.4, 65.2, 82.5],
      ['d', 55.2, 67.1, 69.2, 72.4, 53.9, 39.1],
    ],
  },
  xAxis: { type: 'category' },
  yAxis: { gridIndex: 0 },
  series: [
    { type: 'line', smooth: true, seriesLayoutBy: 'row', areaStyle: {} },
    { type: 'line', smooth: true, seriesLayoutBy: 'row', areaStyle: {} },
    { type: 'line', smooth: true, seriesLayoutBy: 'row', areaStyle: {} },
    { type: 'line', smooth: true, seriesLayoutBy: 'row', areaStyle: {} },
  ],
};

Other comments [其他信息]

JSFiddle: http://jsfiddle.net/cj31rtpf/36/

Fixed on bf0df08


Allow multiple users to see the same device(s)

I understand that this is not possible at the moment. However, this would be helpful in cases of hierarchical organizations, where both the employee and his manager want to see the employee's device. How would I go about doing that?

I have implemented this feature in my fork. So there are now three different types of accounts: administrator, manager and user. Administrator sees all devices and can 'Share' any device to any user. Manager can create new users and managers, which are linked with manager. Then, manager sees his devices and devices of all underlying users in hierarchy.

Thank you very much.

Any update on whether this will work in this repo anytime soon? I see that there is a table setup for users_devices and I did manually add some records for my second user to "read" and "write" and it worked, so it seems that there just needs to be some UI to be able to add these records in without needing to do it manually in the DB.

It's already implemented in the source code, so the feature will be available with the next official release.

Do you have any plan to add a feature wherein a normal user can share the devices link with him, with other normal user(s)?

This is not the right place to ask questions.


Update distage-core to 1.2.13

About this PR
📦 Updates io.7mind.izumi:distage-core from 1.2.11 to 1.2.13
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.7mind.izumi", artifactId = "distage-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.7mind.izumi", artifactId = "distage-core" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #49.


Make authorization error more user-friendly

If I am trying to upload artifacts to a repository which requires sign-in credentials without having specified them in ~/.gradle/gradle.properties the following error is shown:
Execution failed for task ':foobar:uploadArchives'.
> Could not publish configuration 'archives'
   > Failed to deploy artifacts: Could not transfer artifact
     com.example.library.foobar:foobar:aar:1.0.0-20160817.125338-10 from/to remote
     (http://example.com/repository/example-snapshots/): Failed to transfer file:
     http://example.com/repository/example-snapshots/com/example/library/foobar/foobar/
     1.0.0-SNAPSHOT/foobar-1.0.0-20160817.125338-10.aar.
     Return code is: 401, ReasonPhrase: Unauthorized.

How about explicitly telling the user that the plugin is looking for the credentials in that location and that they could not be found?

Return code is: 401, ReasonPhrase: Unauthorized.
Cannot find sign-in credentials to authorize at the target repository. Please provide 'nexusUsername' and 'nexusPassword' in ~/.gradle/gradle.properties.

This is coming from Gradle core (or to be more specific the Ant task provided by the Maven project) and would need to be fixed there. I would like to completely get away from having any credentials-related code in this plugin.

Can you please point me to the Ant task? I would be happy to report it there to address this UX issue.

I believe it's coming from the Aether library if I am not mistaken. See MavenDeployAction in Gradle core for more information and further digging.


the bot not lavalink :'(

Yes the bot supports spotify and soundcloud. The github version is outdated and not maintained anymore. but the main version has lavalink


feat(agora): add export delegates OMS JC

Frontend for https://github.com/AEGEE/statutory/pull/540

:tada: This PR is included in version 1.29.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add Dockerfile and Makefile

This PR adds a new Dockerfile and a Makefile to support the deploy scripts

@jmelis I'll merge if this looks good?


Make it Ractor safe

Can we mark the external code as ractor safe?
I looked at the code and did some tests and it looked OK.

Sorry, did not see this was already done in 0.5.0


Cucumber 2.4 - after_test_case scenario name being chopped off

Summary
Scenario name is chopped off in the after_test_case(scenario, result) formatter hook if the test fails.
Expected Behavior
The expected behavior is that the scenario.name should be the same between a passing and a failing scenario.
Current Behavior
The current behavior is the scenario.name is truncated.
Steps to Reproduce (for bugs)

Create a scenario with the scenario name: This is a very long scenario name that causes the truncation on the after_test_case call in a cucumber 2.4 formatter
Create the step with a `fail("this should fail")
Create a custom formatter with a def after_test_case(scenario, result) method
See that scenario.name has been truncated.

Your Environment

Version used: 2.4.0
Operating System and version: Win 10
Link to your project: Internal

Anyone looking into this?


Allow rectangular pinholes for ISM

If I understood it correctly, currently only circular pinholes are allowed?
But for a pixelated detector, it would make more sense to have square shaped apertures?
Best,
Felix

The confocal as well as the ISM psf calculation supports to define the pinhole type.
For ISM the default is a square-shaped pinhole. If you want a square-shaped pinhole for a normal confocal image, you can specify this as follows:
pp_em = PSFParams(0.488, 1.4, 1.518; mode=ModeConfocal); pp_ex = PSFParams(5, 1.4, 1.518); h = psf((128,128), pp_em, pp_ex=pp_ex, pinhole=4.0, sampling=(0.04, 0.04), pinhole_ft=PointSpreadFunctions.box_pinhole_ft);
The excitation wavelength was set here to a really large value so that the emission PSF can essentially be seen by itself. As you see, you get a square-shaped PSF.


Why is the result of decode is an array?

The array has 1 element which is the payload. Why not the payload itself?
Thanks a lot

It has the headers at the second index.. :-) got it


ExpiredAuthenticationToken errors when using Azure CLI credentials

Describe the bug
When connecting to Azure with Azure CLI credentials, I eventually encounter errors like
Failure responding to request: StatusCode=401 -- Original Error: autorest/azure: Service returned an error. Status=401 Code="ExpiredAuthenticationToken" Message="The access token expiry UTC time '10/6/2022 7:35:55 PM' is earlier than current UTC time '10/6/2022 8:08:46 PM'."

after Steampipe has been running for a while. I haven't timed it exactly, but it feels like I'm running into this problem every 20-30 minutes.
It looks like automatic token refresh is not working: I have to run steampipe service restart to fix things.
It seems like this is a reoccurrence of an earlier bug: #261
Steampipe version (steampipe -v)
steampipe version 0.16.4

Plugin version (steampipe plugin list)
hub.steampipe.io/plugins/turbot/azure@latest     | 0.33.0
hub.steampipe.io/plugins/turbot/steampipe@latest | 0.6.0

Sorry to hear that you are running into this issue @JoshRosen.
I tried to replicate this issue without much success. Could you please provide more details about the environment that you are running steampipe on? I found a conversation online, but I am not sure if it might help - https://github.com/Azure/azure-powershell/issues/6585
@LalitTurbot could you please provide some more insights on the fix that you made per  https://github.com/turbot/steampipe-plugin-azure/issues/261

I tried to replicate this issue without much success. Could you please provide more details about the environment that you are running steampipe on?

I'm running Steampipe on Mac OS 12.5.1
az --version reports:
azure-cli                         2.40.0 *

core                              2.40.0 *
telemetry                          1.0.8

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

I'm using az login --tenant <tenant-id> to obtain Azure credentiasls.
My Azure configuration file looks like this (except there's several connections being aggregated):
connection "azure_all" {
  type        = "aggregator"
  plugin      = "azure"
  connections = ["azure_*"]
}

connection "azure_test" {
  plugin  = "azure"
  subscription_id = "<subscription id>"
}

Hey @JoshRosen, apologies for the delay. @LalitTurbot has raised a fix for the issue - https://github.com/turbot/steampipe-plugin-azure/pull/544
Could you please give it a try from your end and check if it fixes your issue?
Thanks a lot for your patience 👍 and promptness in providing insightful details for us to replicate this issue 😄.

@misraved, @LalitTurbot, https://github.com/turbot/steampipe-plugin-azure/pull/544 appears to have completely resolved my issue: I've been using it for a few hours and haven't hit any expired credential issues. Thanks for the fix!


Bug: does not sort vizualizers / visualize sorts

How to use GitHub

Please use the 👍 reaction to show that you are affected by the same issue.
Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
Subscribe to receive notifications on status change and new comments.

Steps to reproduce

Clone the SortVizualizer repository
Attempt to compile or run the SortVisualizer (404)

Expected behavior
The sort should be visualized, or the vizualizers should be sorted.
Actual behavior
There is no program.
Host OS
Windows for Workgroups 3.11
CPU: Intel Mobile Pentium II 300Mhz
RAM: 384MB SDRAM
Video Adapter: NeoMagic Media256AV 2.5MB VRAM

This issue is fixed in a fork already. My Pull Request is still pending @DLadendorfer's approval.
That being said it could take a while seeing the codebase has been undergoing hibernation recently.

I will try to address the issue. The concepting phase has not yet left my brain. Still thinking about over engineering the architecture.

I made some progress on this issue but not enough to close it. Will keep you updated. :)

Closing as resolved as the project is now stunningly beautiful and functional (as you are) ❤

I wouldn't have closed it already. It is missing a few small details and the test coverage is lacking at the moment. Will push towards the "release" and will update the ReadMe accordingly. Thanks anyways. ❤


Correction of inconsistent method invocation

LoadBalancingPolicy.java defines a pair of consistent methods onAdd/onRemove and onUp/onDown. I guess a ControlConnection.java is broke this contract.

Thanks for bringing this to our attention @exploder86.  That definitely does look wrong and this looks like a straightforward fix, we'll look into getting this in our next release, thanks!

Created JAVA-2070 for tracking.


Dagger Function "initialize" times are prohibitively long (0.11.0)

What is the issue?
The startup time for Dagger Functions takes a long time, even on subsequent runs. It seems to be the step where the function is prepared, compiled, dependencies fetched.  We are aware of the init time and are actively working on it 🚀

stark difference with TS (much longer)

About the TypeScript, we just merged our support for Bun #6591 that can be used to divide by 2 to 3 the init time for TS modules.
It's still experimental but it's a conveniant way to improve performances if you need some.

Duplicate of #7093, please follow the performance improvement on this issue instead

That issue is specific to TS while this one is not, so reopening.

Hey @verdverm we've made some huge progress on performance over the last few releases, could you update to latest and re-run your benchmarks and let us know how it goes?

When rerunning "hello world" after a first run:

Go timings are the most variable, 2-12s
Py times are around 3s
Ts times are around 4s

For context, when I rebuild a complex Go application (100k LOC), it's 0.3s and the Py/TS runs I have feel instantaneous
Average repro-go run:
time dagger -v call container-echo --string-arg='Hello Daggernauts!' stdout
✔ connect 0.7s
  ✔ starting engine 0.3s
  ✔ connecting to engine 0.1s
  ✔ starting session 0.2s
✔ initialize 4.8s
✔ ReproGo.containerEcho(stringArg: "Hello Daggernauts!"): Container! 0.4s
  ✔ Container.from(address: "alpine:latest"): Container! 0.2s

Hello Daggernauts!
dagger -v call container-echo --string-arg='Hello Daggernauts!' stdout  1.79s user 1.81s system 57% cpu 6.248 total

Thanks so much for re-running, looks like we still got some work to do here, lets try again in the near future :)

I would expect the connect phase to be nearly instantaneous, given the engine is already running, and I am running the same command in a loop
I would think a single API call ought to be enough to know it's running and in a good state

I noticed that my "initialize" time tripled (from 30s to 1m 30s) after installing node_modules in the host workspace, when using a dagger call that contains --source=. in it, so it seems that copying the workspace to the context is a major player in this.

Yeah definitely, in the general case we suggest not including
node_modules this way. Outside of the performance implications it can
also lead to issues between local/ci compatibility. For example if
you're working on MacOS locally but running Linux in CI.
We're still working on adding this to our docs, but we do shows how to
exclude node_modules using "views" in our own dagger.json file here: https://github.com/dagger/dagger/blob/main/dagger.json#L24
Once you have your view set up you then reference it like this:
dagger call --src .:default
On Fri, Jun 14, 2024 at 12:33:34PM -0700, Max Pixel wrote:

I noticed that my "initialize" time tripled (from 30s to 1m 30s) after installing node_modules in the host workspace, when using a dagger call that contains --source=. in it, so it seems that copying the workspace to the context is a major player in this.
--
Reply to this email directly or view it on GitHub:
https://github.com/dagger/dagger/issues/7043#issuecomment-2168640786
You are receiving this because you commented.
Message ID: @.***>

Hey @verdverm did you try with v0.12? We tried to make Dagger significantly faster!
If that's not the case, let us know because we're doing our best to make it fast.
There's still several things happening on the TS SDK to make it faster, I might have unlock an optimization with https://github.com/dagger/dagger/pull/7864 that I'll do once it's merge, hopefully this will also reduce the initialization time.

@TomChv for dagger 0.13.1 I also experience slow startup times of ~20 secs for python poetry project. Installing module and analyzing module are the culprits. It varies heavily depending, I think, on whether the code has changed or not, like there's a caching mechanism behind, but if I did change the module - I'll have to wait.

We do have some cache misses we're investigating:

https://github.com/dagger/dagger/issues/8254

But it's likely that the module's uploading more than it needs to. I'm interested in whether this POC helps with your Installing module phase (i.e., module load):

https://github.com/dagger/dagger/pull/8501

For the analyzing part, I didn't expect you to see an impact there. That phase is just doing module introspection in order to build up the CLI (later, in prepare). How long can it take for you in this step?

Experiencing 20s initialisation as well in a Python monorepo project. My gut feeling is that regardless of strict includes&excludes in dagger.json (btw that json lacks documentation), too much code gets still included.
I'm additionally confused of how can I change the context where Dagger operates. It seems by default to use the git repository.

There seems to be https://docs.dagger.io/manuals/developer/functions/#directories-and-files which describes something related to the context; and seems that I can add some additional ignores there
There seems to be new views feature for additional includes/excludes but it's unclear that when this is applied

@attekei, first of all, the includes/excludes in dagger.json affect module loading (initialize), while DefaultPath + Ignore and views affect passing a Directory argument to a function via the CLI (prepare). See this for more context:

https://github.com/dagger/dagger/issues/8542

Debug function arguments
For Directory arguments it’s simple to debug (DefaultPath + Ignore, a view, or CLI flag without Ignore in code). Just create a function that receives a Directory as input, and returns the same Directory:
@function
def debug(
    self,
    source: Annotated[
        dagger.Directory,
        DefaultPath("."),
        Ignore([".venv", "sdk"]),
    ],
) -> dagger.Directory:
    return source

There’s several things you can do here:

Calling the function will show you the Directory’s digest and top level entries. The digest is content addressed, so it changes if there’s changes in the contents of the directory. Looking at the entries field you may be able to spot an interloper:
❯ dagger call debug

You can also list all files, recursively to check it more deeply:
❯ dagger call debug glob --pattern="**/*"

Or open the Directory in a Terminal to navigate around:
❯ dagger call debug terminal

Or even export to your host to check it with local tools:
❯ dagger call debug export --path=audit

Note that these examples assume you’re using DefaultPath (i.e., don’t provide it via CLI) because that’s the only time where Ignore is used right now, but in the next release you’ll be able to just set Ignore and pass different directories via the CLI (--source flag in this case):
❯ dagger call debug --source=./subdir

Views
In the meantime, if you can’t wait, views allow providing multiple set of named filters (in dagger.json). Assuming a view named “default”, you’d call test it with:
❯ dagger call debug --source=.:default

⚠ However, be warned that views may be deprecated soon in favor of Ignore in code.

Debug module loading

My gut feeling is that regardless of strict includes&excludes in dagger.json (btw that json lacks documentation), too much code gets still included.

Sounds like you’re doing it blind (and I get why!), so I think what you need is to inspect the files that were actually uploaded and see which dirs/files weren’t excluded properly.
I’m not sure if there’s a simpler way of doing this, or what that would look like, but I can tell you how I debug it.
Whenever you see a ModuleSource.resolveFromCaller step, it’s the engine importing files from your host:

If it’s taking a long time, it could be that you’re uploading files unnecessarily, and it can possibly have a compounding effect if any changes on unwanted files cause cache misses later on.
When you open it (in the Cloud UI), look for upload <module context> ... (exclude: ...) (include: ...), where “module context” is either the git repo root if the module is in a git repo, or the directory with dagger.json if the module isn’t in a git repo).
Notice the final include/exclude patterns that the engine is using to filter. It’s not all coming directly from dagger.json, that just contributes to it. See if all looks good.
Then, notice the “blob” step just after it. Blobs are a sort of cache for Directories when they’re imported from the host. You can get them through the API but don’t take too long because they can be pruned after a while:

For example, using dagger core, just copy those inputs:
❯ dagger core blob \
    --digest="sha256: aa44c7c71c77c77cb979724122078b7ecff40d9c6affcb59f9a7ff3fe86175c0" \
    --mediaType="application/vnd.oci.image.layer.v1.tar+zstd" \
    --size=136179 \
    --uncompressed="sha256:cb65d8eb5f603a68afb4be1551b82b32bd381c77907e0fc4651d721a07c0d8ee"

The advantage of dagger core is you have the same Directory printing feature (with digest and entries), and you can add terminal to navigate, but it can be cumbersome to copy the digest, size, and uncompressed inputs multiple times.
The step in the UI is already formatted as a GraphQL query field though, so you can also copy the whole thing and sub-select the field(s) that you’re interested (digest, entries, glob, export…):
❯ echo '{ <insert blob() here> { digest glob(pattern: "**/*") } }' | dagger query

Full query
{
    blob(digest: "sha256:aa44c7c71c77c77cb979724122078b7ecff40d9c6affcb59f9a7ff3fe86175c0" mediaType: "application/vnd.oci.image.layer.v1.tar+zstd", size: 136179, uncompressed: "sha256:cb65d8eb5f603a68afb4be1551b82b32bd381c77907e0fc4651d721a07c0d8ee") {
        digest
        glob(pattern: "**/*")
    }
}

Or, you can also just copy the DirectoryID by clicking the randomly generated icon:
❯ echo '{ loadDirectoryFromID(id: "<insert ID here>") { export(path: "./audit") } }' | dagger query

The downside of using a GraphQL query is you may not be familiar with GraphQL enough to figure out the right syntax, but you can create a simple shell script to make this easier, or a function to get dagger call capabilities.
Function example
@function
def load_directory(
    self,
    from_id: Annotated[string, Doc("DirectoryID value")],
) -> dagger.Directory:
    """Get a Directory object from its ID"""
    return dag.load_directory_from_id(id: dagger.DirectoryID(dir_id))

Shell shortcut:
alias dagdir="dagger call -m github.com/example/daggerverse/debug-utils load-directory --from-id"

Example usage:
❯ dagdir DIRECTORYID terminal

This is actually a good use case to allow passing ids (in certain cases) to dagger core, so watch out for that.


Evernote - Creation of tokens has been disabled

When I try to get a token I see this message from Evernote: "Update: the creation of developer tokens is temporarily disabled. Any other way to import data?"
Thank you

I'm working on a new cli app to import the evernote's note, but now you will need a Consumer Key and Consumer Secret, sadly. If someone share with me a consumer key and secret to put on the cli app, I can make it default, so it'd a lot easier for the user.

Here, https://github.com/matheusfaustino/ever2boostphp. It's not that easy like this repo, but we don't have more the developers token. I'm gonna try to make it a little easier than it's now.

I've made some adjustments and now it a lot easier to import the notes.


pip install winrt succeeds, but import winrt results in ModuleNotFoundError

PS C:\Users\prasadk\Media> python --version
Python 3.9.4
PS C:\Users\prasadk\Media> pip --version
pip 21.0.1 from C:\Users\xxx\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\pip (python 3.9)
PS C:\Users\xxx\Media> pip install winrt
Requirement already satisfied: winrt in c:\users\xxx\appdata\local\packages\pythonsoftwarefoundation.python.3.9_qbz5n2kfra8p0\localcache\local-packages\python39\site-packages (1.0.21033.1)
PS C:\Users\xxx\Media> & "C:/Program Files (x86)/Microsoft Visual Studio/Shared/Python37_64/python.exe" c:/Users/xxx/Media/winrtEx.py
Traceback (most recent call last):
File "c:/Users/xxx/Media/winrtEx.py", line 1, in
import winrt.windows.foundation as wf
ModuleNotFoundError: No module named 'winrt'
PS C:\Users\xxx\Media> & "C:/Program Files (x86)/Microsoft Visual Studio/Shared/Python37_64/python.exe" c:/Users/xxx/Media/winrtEx.py
Traceback (most recent call last):
File "c:/Users/xxx/Media/winrtEx.py", line 1, in
import winrt.windows.foundation as wf
ModuleNotFoundError: No module named 'winrt'

@pkaku You are using different versions of python to install and import.  You are using Python 3.9 (installed via windows store) to install and then using Python 3.7 (installed via Visual Studio) to import.
Try this:
"C:/Program Files (x86)/Microsoft Visual Studio/Shared/Python37_64/python.exe" -m pip install winrt

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off.


(Idea) AMD FSR

This is mainly an idea, but AMD FSR could add some performance and quality when playing with a lower resolution, especially on the Steam Deck. I guess it would have to run on the client though, which has spotty OpenGL support.

There is a project https://github.com/fholger/openvr_fsr , if can integrate it would be great

this looks promising, but it doesn't have any form of linux support (.dll's are for windows only). Linux especially needs FSR right now due to the lack of decent async reprojection and other key vr features on NVIDIA cards to smooth out frames. I could probably try to get this to work on windows later though.

probably shouldn't have closed this- i think that openvr-fsr could be ported to linux later

#780 already mentioned this, but i have an idea as to how this could be done:
the client upscales, reducing bandwidth usage and performance associated with lower resolution. I assume that the switch can do it.

I'm pretty sure this has already been attempted. Video decoding is simply to taxing for FSR to be ran. I would love to see another attempt though!

The quest 2 has ~1200 GFLOPs, more then enough for running FSR. Since the GPU isn't being used much ( I assume), then game, encoding, and decoding latency can be greatly reduced in exchange for an amount of up-scaling latency. To reduce noise the encoder would have to be less lossy, but the smaller image size should more then make up for increase in quality.

for the Oculus Quest client, there is no need to do FSR, you need to do FSR on the server so that it does upscaling after receiving the SteamVR image and sends the already updated image to the Quest


Edit task ratings

Added RoadmapReadUsers permission to Business-role

Business-users can read either Developer-users or users with at least one same represented customer
This enables business-users to see who rated listed ratings. It could have been confusing otherwise, as the user could not even identify their own ratings in the list

Moved edit icons to the right side of an editable rating

Added Juho's suggestions 👍

they all open the same modal where there are all the tasks

In last weekly we discussed it can be like this, at least for now

The design indicated (at least to me) that I would just change the rating of that exact task

I do still agree with this. If we want to change the modal to display only a certain task on edit, I'd add it as another task to do: it requires some logic changes to the modal, which could take a while.


Code cleanup

@TexasSwede Please run the following command after merging this PR to remove node_modules from git history.
git filter-branch -f --index-filter 'git rm -rf --cached --ignore-unmatch node_modules' HEAD

Then you will have to force push using
git push -f origin main

My next PR is awaiting on https://github.com/TexasSwede/netsuite-print/pull/3#issuecomment-1543561032


Feature request - DVD mode - Bruteforce the 0x3C SCSI command when /raw is used for unknown drives.

Is your feature request related to a problem? Please describe.
Currently, DIC has a fixed list of drives that support various methods of reading 'raw' data from the drive through various methods. For instance, certain LG/Hitachi drives support the E7 memory dump command, but many drives can support reading raw data through the 0x3C command like Lite-Ons and LG/ASUS drives. However, DIC will only allow /raw to be used if the drive is hard-coded into DIC to function leaving a lot of potential drives out without support.
Describe the solution you'd like
I think DIC should attempt to brute force or automatically detect if a drive has support for reading with /raw by using brute-forcing methods to determine the right parameters that return data off the disc. Friidump includes an (unfortunately closed-sourced) called BruteForce3C which can brute force the 0x3C opcode by incrementing the command parameters until the drive returns data off the disc while the target drive has a DVD inserted. The program comes with a .cfg file that blacklists returns that are all 00s, as that would suggest that the drive has nothing on the cache/buffer. However, if the program returns a .bin containing non-zero data, it can potentially read raw data.
However, DIC could go one step further and implement this for drives that aren't hardcoded into the program. Here's how I imagine it can work:
1.) User uses /raw with their unsupported drive.
2.) If DIC determines that the drive is unsupported, try and see if the drive is an LG/Hitachi drive. see if E7 is present by using the opcode and return data where the first 4 bytes are 00 03 00 00. This would indicate PSN data for LBA 0, the first sector on the DVD.
3.) If E7 doesn't work, move on to brute forcing 0x3C. Alert the user that the drive is unsupported but that DIC will bruteforce for 0x3C. DIC will then increment the 2 parameters of 0x3C and return data from the drive as it reads LBA 0. If 0x3C returns 00, increment and move on to the next value. If it returns data, see if 00 03 00 00 are the first bytes present. If it is, that's the command for 0x3C to use for raw dumping. If you exhaust all values for 0x3C, the drive doesn't support reading with /raw, so stop DIC. DIC should let the user know what values it's trying or how long it will take to brute force.
4.) Next determine what data is being returned by the drive. This is a bit tricky as since drives can return different data, there are a few things you need to look for.

raw dumps should always have sync information like a PSN number as the first 4 bytes for the sector. maybe read the next sector and see if it follows in sequence with LBA 0. Look at the usual offsets where the next PSN would be stored (2064 bytes away, 2384 bytes away, etc) and find the four bytes for the next PSN in the sequence from LBA 0. Once you determine how many bytes away the next LBA is, that's how many bytes per sector the drive is returning
next, you need to determine if the resulting data is scrambled or unscrambled. I don't know of a safe way to determine this...do you?

5.) Once everything has been determined, dump the rest of the disc to a .raw file using the discovered 0x3C opcode.
Make sure everything is recorded in a log file.
Describe alternatives you've considered
It would be nice to have DIC do this for the user, but I suppose you could always just include BruteForce3C with DIC and call it externally when /raw is used. I wish the source code were available, but I have a feeling this would be easy to implement in DIC anyway.
Additional context
Grab BruteForce3C here.
BruteForce3C.zip
For the record, here is what BruteForce3C does:

In case none of existing 'commands' work, use this program to determine your
drive's READ BUFFER command parameters. By default Mode will be scanned from
$00..$0f, Buffer ID from $00 to $ff. Mode range can be set from commandline.
Full scan ($00..$ff) takes about 10 minutes to complete. All returned data
different from $00 will be logged to files, but it's possible to configure
masking behaviour by adding CRC32 values of unwanted data files to
'BruteForce3c.cfg' e.g. if drive returns a lot of similar files.

IMPORTANT: When scanning there should be readable (e.g. PC) DVD in drive!
If full scan completes but there were no files created, your drive either
uses completely custom command for buffer acces (as e.g. Hitachi-LG drives do),
in which case you could try to look it up in chipset documentation or find it
by reverse engineering some of vendor's programs, such as firmware flashers,
or it simply has none.

If someone find a new drive using the BruteForce3C.exe, I'll add it as whitelist.

Currently, DIC has a fixed list of drives that support various methods of reading 'raw' data from the drive through various methods.

DiscImageCreator_test.zip
added set the command and size using your spreadsheet (https://docs.google.com/spreadsheets/d/1pu3oXHRJ_qlyXrsHUyXOzD5mNp7dU8rgrfVuRBLyQFA/edit?pli=1#gid=0).


Fixed various module related deadlocks

Fixed various module related deadlocks through the following:

Removed synchronous calls to aePostFunction as they were causing issues with the GIL and deadlocking.
Changed the scope of g_fModuleThread from static to thread local in order to properly determine whether a thread was spawned by a module or not.
Fixed scenario where module thread waiting for s_mutexModule in moduleAcquireGIL can deadlock with module thread waiting for s_mutex in moduleReleaseGIL by allowing s_mutex to be released while waiting for s_mutexModule.

Merged seperately


Cache problem / Type name Math is redefined from module Math

Hi, I didn't get any problem to install flambe and run the demos but now that I try to edit the files I encounter some issues which I guess are relative to the cache of the server but I don't know how to solve this.
First of all I've got this error in compiling a project for the second time :

Building: build/web
haxe --connect 6000 -main PhysicsMain -lib nape -D NAPE_RELEASE_BUILD -lib flambe -cp src -dce >full -debug --no-opt --no-inline -D html -D js-es5 -D js-flatten --macro >flambe.platform.ManifestBuilder.use("build/web/assets") -D source-map-content -js >build/web/targets/main-html.js
Type name Math is redefined from module Math

If I restart the server I'm able to build again without any error but then if I try to rebuild I've got the same issue.
If I try to compile another project and run it on http://localhost:7000/ it keeps showing me the same built I've done for the first time.
I didn't find any solution so I hope someone could highlight me on this and helps me to start with Flambe

Edistra, I encountered the same issue recently. While flambe is being served I 'pkill haxe' in another tab. It seems to be working but interferes with code completion when writing haxe. A thing to note that if your issue is the same as mine, every time I open a new sublime window I have to 'pkill haxe'. Let me know if you find a better solution or if this works.


refactor: file_upload function

[x] Add templateId column in file_upload table
[x] Provide schema object in fetch issued credentials API
[x] Refactor file upload function for w3c schema type
[x] Refactor bulk issuance API for w3c schema type
[x] Resolve pagination issue in file preview API

This task is completed.


Issue with Arista version in quickstart topology

I went through the quickstart guide and have noted a couple of issues.
The most significant is that the suggested version of Arista (4.25.0F) is not present on the Arista website for download. The closest I could find was 4.25.11M.
After downloading this version and running, containerlab seemed to hang indefinitely after doing containerlab deploy.
I noticed that while the docker VMs were up, if I try to use the Cli command on Arista, it doesn't work:
jmh@the-pot:~/clab-quickstart$ docker exec -it clab-srlceos01-ceos bash
bash-4.2# exit
jmh@the-pot:~/clab-quickstart$ docker exec -it clab-srlceos01-ceos Cli
OCI runtime exec failed: exec failed: unable to start container process: exec: "Cli": executable file not found in $PATH: unknown

In order to fix, I tried downloading the latest available Arista image, 4.32.0F. This works without flaw, topology starts up and the above Cli command works.
There was one other small flaw I noticed. The command given to connect to the srl container is wrong.
It is listed as:
docker exec -it clab-srlceos01-srl1 bash

It should be:
docker exec -it clab-srlceos01-srl bash

Here is the topology file with the "good" version activated and the "bad" version commented out:
# topology documentation: http://containerlab.dev/lab-examples/srl-ceos/
name: srlceos01

topology:
  nodes:
    srl:
      kind: nokia_srlinux
      image: ghcr.io/nokia/srlinux
    ceos:
      kind: arista_ceos
      image: ceos:4.32.0F
      #image: ceos:4.25.11M

  links:
    - endpoints: ["srl:e1-1", "ceos:eth1"]

thanks @james-m-henderson
do you want to raise a PR with those fixes and get into the prestigious contributors ranks? =)
thank you!

Hi Roman,
I already started on one, but I wanted to know if I should update all
arista lab examples and docs as well? In addition some are on a different
version, which I haven’t tested yet. Would it make sense to just
standardize on the newest?
Thanks,
James
On Sat, May 4, 2024 at 3:35 PM Roman Dodin @.***> wrote:

thanks @james-m-henderson https://github.com/james-m-henderson
do you want to raise a PR with those fixes and get into the prestigious
contributors ranks? =)
thank you!
—
Reply to this email directly, view it on GitHub
https://github.com/srl-labs/containerlab/issues/2033#issuecomment-2094357277,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHPVXSDWBLOTN4ULHEVTWLZAUZ6TAVCNFSM6AAAAABHGYDRD2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJUGM2TOMRXG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

Feel free to update all of them to the version you tested. We don't have sophisticated labs  that exercise advanced platform features, so you can safely bump them all to the 4.32.0F

https://github.com/srl-labs/containerlab/pull/2034
I have to checkout for the day, and I haven't yet installed all the test dependencies into my lab, so I haven't done full regression yet. However I did run the updated .yml files and it seems everything is OK.


Fatal error: Unexpectedly found nil while unwrapping an Optional

I am going to link the outlook calendar with my own client

Hi, can you provide some more context (when is the error happening, what's the stack trace, ...)?

Hi, can you provide some more context (when is the error happening, what's the stack trace, ...)?


sql server create Deployment failed.  Location 'West Europe' is not accepting creation of new Windows Azure SQL Database servers at this time.

I get the following error when trying to create sql server.
Deployment failed. Correlation ID: SomeIdHere. Location 'West Europe' is not accepting creation of new Windows Azure SQL Database servers at this time.
I followed the basic tute.

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

ID: 00961883-36eb-f736-b906-73d4c35e69b0
Version Independent ID: 3a2fd493-9682-eedf-fad1-571b9391cd46
Content: Tutorial: ASP.NET Core with SQL Database - Azure App Service
Content Source: articles/app-service/app-service-web-tutorial-dotnetcore-sqldb.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

Hi @pheu, thanks for the feedback! We are currently investigating and will update you shortly.

@Grace-MacJones-MSFT. Thank you. I tried with many locations eventually I was able to create the server in "East US" location. Still I think it's unclear, since the "West Europe" is listed by az appservice list-locations --sku FREE.

My colleague, who is administering our Azure accounts, contacted Microsoft yesterday, and today I can create DB in “West Europe” again.

@pheu can you try again to create a new sql server? are you still getting that error?

This error is no longer reproducible. #please-close

The same error seems to be back again.

@pheu can you try again to create a new sql server? are you still getting that error?

@Grace-MacJones-MSFT I don't have the error when creating db anymore, but I have another one while trying to create an app service plan:
"This region has quota of 0 instances for your subscription. Try selecting different region or SKU."

Make sure that you have added Microsoft.SQL as allowed resource in your subscription. I got that same error on a new subscription where it was not available by default http://microsoft-bitools.blogspot.com/2020/10/synapse-snack-no-new-azure-sql-database.html

Make sure that you have added Microsoft.SQL as allowed resource in your subscription. I got that same error on a new subscription where it was not available by default http://microsoft-bitools.blogspot.com/2020/10/synapse-snack-no-new-azure-sql-database.html

This worked for me. Both the Microsoft.Synapse and Microsoft.Sql needs to be registered first before you'll be able to create an Azure Synapse Analytics workspace. To do this, go to Subscriptions > Subscription name > Settings > Resource Providers, search then click the Provider name and Register.

I've tried all of these but the issue still remains

have the same issue for West Europe, providers registered, dont see any specific limit which should block me from creating this.

Occurred just now, error was:
Location 'West Europe' is not accepting creation of new Windows Azure SQL Database servers at this time
East Asia, East US 2 regions deployed OK.  I was also following the tutorial.

Occurred just now, error was:
Location 'West Europe' is not accepting creation of new Windows Azure SQL Database servers at this time
East Asia, East US 2 regions deployed OK. I was also following the tutorial.

If you already have around 40 (west europe) SQL servers in your Azure Subscription then you probably reached the max. You could add an Azure Support ticket and ask them to increase the Server Count Quota for SQL DB.

A reason can be that there are no more resources at this region.
https://stackoverflow.com/a/75410688/448100


make bin/vsql fails due to distinction between result and option

Output of v doctor
OS: linux, Pop!_OS 22.04 LTS
Processor: 6 cpus, 64bit, little endian, AMD Ryzen 5 4500U with Radeon Graphics
CC version: cc (Ubuntu 11.2.0-19ubuntu1) 11.2.0

getwd: /home/astro/.vmodules/elliotchance/vsql
vmodules: /home/astro/.vmodules
vroot: /home/astro/Projects/V/v-main
vexe: /home/astro/Projects/V/v-main/v
vexe mtime: 2022-08-15 06:04:48
is vroot writable: true
is vmodules writable: true
V full version: V 0.3.0 5464de4.6fdcc5b

Git version: git version 2.34.1
Git vroot status: weekly.2022.32-34-g6fdcc5bc
.git/config present: true
thirdparty/tcc status: thirdparty-linux-amd64 827f7452

The Command
Here's the command I tried to execute:
make bin/vsql

The Expected Result
I expected the project to compile with no errors.
The Actual Result
Because of the recent deprecation, the following error are generated:
mkdir -p bin
v  -prod cmd/vsql -o bin/vsql
vsql/pager.v:102:22: error: propagating a result like an option is deprecated, use `foo()!` instead of `foo()?`
  100 |
  101 |     mut buf := []u8{len: p.page_size}
  102 |     p.file.read(mut buf)?
      |                         ^
  103 |
  104 |     mut b := new_bytes(buf)
vsql/pg.v:80:24: error: propagating a result like an option is deprecated, use `foo()!` instead of `foo()?`
   78 | fn (mut c PGConn) read_byte() ?u8 {
   79 |     mut bytes := []u8{len: 1}
   80 |     c.conn.read(mut bytes)?
      |                           ^
   81 |
   82 |     return bytes[0]
vsql/pg.v:194:24: error: propagating a result like an option is deprecated, use `foo()!` instead of `foo()?`
  192 | fn (mut c PGConn) read_int32() ?int {
  193 |     mut bytes := []u8{len: 4}
  194 |     c.conn.read(mut bytes)?
      |                           ^
  195 |
  196 |     return int(binary.big_endian_u32(bytes))
vsql/pg.v:216:25: error: propagating a result like an option is deprecated, use `foo()!` instead of `foo()?`
  214 |     mut s := ''
  215 |     for {
  216 |         c.conn.read(mut bytes)?
      |                               ^
  217 |         read++
  218 |         if bytes[0] == 0 {
make: *** [Makefile:18: bin/vsql] Error 1

The Solution
This requires a Pull Request that updates the current code to match the updated syntax.

I'm attempting to update the code to the new style.

If I'm reading that correctly, it might be a significant change to the language and a lot of code changes required. It would be great if you want to take that on. Run make ready after changes which will do cleanup stuff like formatting.

If there's been no progress on this, I'll try to dedicate some time to this next week.

I would appreciate that. After discussing (more like me complaining) on discord everything needs to be changed to !Type. I don't use none anywhere in vsql.


URA state machine

This PR supersedes, and is base on, the state machine diagrams PR #318.
It introduces a state machine for PatientSession to replace the existing system to derive state. It uses a concern to keep  the state machine logic wrapped up in it's own module. This also allows for snappy specs by removing the need to have a PatientSession constructed for each spec.
This PR is currently in draft to get feedback on the implementation and the design of the states and transitions. The approach I landed on was to have states that represented all the possible states a patient could have within a session, with transitions that performed the logic to determine the correct state to transition to.
I've also left transitionary commits in to help illustrate the different approaches I was trying, feel free to tell me if you prefer one of the other approaches or have a suggestion for a better one.
Remaining work:

[ ] Add missing transitions from "Check Refusal" for gillick competence or verbal consent
[ ] Add "not vaccinated" states to represent whether patient cannot be vaccinated for the session or the campaign
[ ] Update states diagram
[ ] Integrate with the existing system

Ugh. I could've swore I clicked on the option to make this PR a draft. 🤦

Here's how this looks on the console, by the way:
[3] pry(main)> ps = PatientSession.all.sample
  PatientSession Load (2.4ms)  SELECT "patient_sessions".* FROM "patient_sessions"
=> #<PatientSession:0x00000001287d5ab8 id: 2, session_id: 1, patient_id: 2, created_at: Tue, 11 Jul 2023 10:02:45.831124000 BST +01:00, updated_at: Tue, 11 Jul 2023 10:02:45.831124000 BST +01:00, state: "added_to_session">
[4] pry(main)> ps.may_process_triage
NoMethodError: undefined method `may_process_triage' for #<PatientSession id: 2, session_id: 1, patient_id: 2, created_at: "2023-07-11 10:02:45.831124000 +0100", updated_at: "2023-07-11 10:02:45.831124000 +0100", state: "added_to_session">
from /Users/misaka/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/activemodel-7.0.6/lib/active_model/attribute_methods.rb:450:in `method_missing'
[5] pry(main)> ps.may_process_triage?
=> false
[6] pry(main)> ps.may_process_consent?
  Patient Load (0.2ms)  SELECT "patients".* FROM "patients" WHERE "patients"."id" = $1 LIMIT $2  [["id", 2], ["LIMIT", 1]]
  Session Load (0.2ms)  SELECT "sessions".* FROM "sessions" WHERE "sessions"."id" = $1 LIMIT $2  [["id", 1], ["LIMIT", 1]]
  Campaign Load (0.2ms)  SELECT "campaigns".* FROM "campaigns" WHERE "campaigns"."id" = $1 LIMIT $2  [["id", 1], ["LIMIT", 1]]
  ConsentResponse Load (0.3ms)  SELECT "consent_responses".* FROM "consent_responses" WHERE "consent_responses"."patient_id" = $1  [["patient_id", 2]]
=> true
[7] pry(main)> ps.process_consent
=> true
[8] pry(main)> ps.state
=> "consent_given_triage_not_needed"
[9] pry(main)> ps.may_process_triage?
=> false
[10] pry(main)> ps.consent_given?
=> true
[11] pry(main)> ps.triage_needed?
=> false
[12] pry(main)> ps.vaccination_administered
  VaccinationRecord Load (0.8ms)  SELECT "vaccination_records".* FROM "vaccination_records" WHERE "vaccination_records"."patient_session_id" = $1 ORDER BY "vaccination_records"."id" DESC LIMIT $2  [["patient_session_id", 2], ["LIMIT", 1]]
=> nil

I know this isn't our primary use case, but it does seem to show decent ergonomics.

@benilovj Theo and I chatted about the action names and we agreed it's nice to have action names that are more clearly verbs/actions. We tried to find some other synonym to process since that word is a little overloaded, and came up with do_*. WDYT?

@benilovj Theo and I chatted about the action names and we agreed it's nice to have action names that are more clearly verbs/actions. We tried to find some other synonym to process since that word is a little overloaded, and came up with do_*. WDYT?

:shipit:

Ok, ready to merge once approval is given.


PDF fix

This fixes the following multicols error:
! Package multicol Error: Error saving partial page.

See the multicol package documentation for explanation.
Type  H <return>  for immediate help.
 ...

l.4182 \begin{multicols}{5}
                               \textit{LinkageAttribute}
? H
The part of the page before the multicols environment was nearly full with
the result that starting the environment will produce an overfull page. Some
text may be lost! Please increase \premulticols either generally or for this
environment by specifying a suitable value in the second optional argument to
the multicols environment.

I have no idea if this is the right way to fix it - I just set \premulticols to what I think is its default value.


feat: spinner component

closes #866

I'm not sure if we should be showing loading cursor on hover, wouldn't it be better to display the default instead? @buseselvi what do you think?
Also a small thing but can we increase the spinner size for the Relative Overlay story?

We discussed this in the meeting as well. The size is adjustable via a prop. Is there another concern here? @AykutSarac


XEP-0440: SASL Channel-Binding Type Capability

Dear @go-xmpp team, @mdosch,
Can you add "XEP-0440: SASL Channel-Binding Type Capability" support?

https://xmpp.org/extensions/xep-0440.html

Thanks in advance.

Already supported.

@mdosch: Badly I do not find in the code :/

https://github.com/search?q=repo%3Axmppo%2Fgo-xmpp+0440&type=code

Can you add details in code?

You'll find it if you search for the namespace.
Maybe you could contribute some documentation when working on #114 and
#115.
Am 08.11.2024 12:48, schrieb Neustradamus:

@mdosch: Badly I do not find in the code :/

https://github.com/search?q=repo%3Axmppo%2Fgo-xmpp+0440&type=code

Can you add details in code?
--
Reply to this email directly or view it on GitHub:
https://github.com/xmppo/go-xmpp/issues/191#issuecomment-2465726660
You are receiving this because you were mentioned.
Message ID: @.***>

@mdosch: The .doap file is really important :)
Same for go-sendxmpp

@Neustradamus see #193, #114  and #115.


Error: Selecting or moving a token causes an error when trying to start background caching (develop branch only)

This issue does not affect the version of drag ruler that has been deployed (1.12.8), only what is on the develop branch.
When controlling or moving a token, the function startBackgroundCaching  throws an error because the cache layer doesn't contain an entry for the token's position. This doesn't seem to cause any problems in the outwardly visible behavior, but it does show the error in the console and presumably the benefits of the background caching aren't being used because of this error.

It seems that this stems from commit 2979e86201f411003d6b09fa6fa489fab3727bf1 by @JDCalvert which is present on develop, but not master.

This appears to only happen on gridless scenes. Can you confirm that observation?

Correct, only on gridless scenes.


Where is the sample code

@msched commented on Tue Dec 04 2018
Hey, where do I find the C#, Python and R sample code mentioned in the article?

Dokumentdetails
⚠ Bearbeiten Sie diesen Abschnitt nicht. Er ist für die Verknüpfung von docs.microsoft.com zum GitHub-Artikel erforderlich.

ID: edc98ded-e57a-f28e-89c4-6b352476609e
Version Independent ID: 4345a74c-afeb-d48d-0cf3-68aee6a56007
Content: Programmgesteuertes erneutes Trainieren von Machine Learning-Modellen
Content Source: articles/machine-learning/studio/retrain-models-programmatically.md
Service: machine-learning
GitHub Login: @YasinMSFT
Microsoft Alias: yahajiza

Hi Team,
Please check the issue reported
Thanks!

I have moved from this team. @Josée<EMAIL_ADDRESS>FYI
From: Lisandro<EMAIL_ADDRESS>Sent: Tuesday, December 4, 2018 12:05 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Yasin Hajizadeh<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Where is the sample code (#19986)
Hi Team,
Please check the issue reported
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F19986%23issuecomment-444238736&data=02|01|yasin.hajizadeh%40microsoft.com|f5cea2d7bc6e41de814108d65a23c3a7|72f988bf86f141af91ab2d7cd011db47|1|0|636795506988448579&sdata=qAh5%2F5VH55iu0rv4UfwBApCxu6gFowZF1Ju1p0gqFa4%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAhnNmOa3Z7Fsqgopn_sEdI2CErK-Gaqaks5u1tVpgaJpZM4ZBZ5i&data=02|01|yasin.hajizadeh%40microsoft.com|f5cea2d7bc6e41de814108d65a23c3a7|72f988bf86f141af91ab2d7cd011db47|1|0|636795506988448579&sdata=HNEzP5TthQvjodW4kaBdxq%2BjRWRSnhZ0rpBCCoN6qF4%3D&reserved=0.

@YutongTie-MSFT - please assign to @ericlicoding
https://github.com/MicrosoftDocs/azure-docs-pr/blob/master/articles/machine-learning/studio/retrain-models-programmatically.md
This article refers to samples and r and python files but there are no links to them. I saw some stuff in the gallery, but I don't know where things are: https://gallery.azure.ai/browse?categories=["1"]

@j-martens Done, thanks.

@YutongTie-MSFT - #please-close as this article was retired a few weeks ago. We apologize for the late update.


Generalize Lexeme State into Flags

Generalize the current "is at start of line" bit into a small flag set. On top of that, pass the lexer's "is multiline string" flag up to the parser. This mirrors the behavior of the C++ parser and makes sure we don't have to spend time re-lexing the string literal to determine this for ourselves in a completely separate component.
The important part here is that we have a space to attach a future "error" bit to the tokens, rather than yielding plain .unknown back. This should give us the space to start issuing (what were formerly) lex-time diagnostics.

@swift-ci test


No such file or directory: '.../VOCdevkit/VOC2007/Annotations' in 2012 dataset

╭─user@user-pc /media/sdb1/dev/learn/keras-frcnn  ‹master›
╰─$ ls -l python train_frcnn.py --path=/home/machinelearning/datasets/VOCdevkit/
4 drwxrwxrwx 7 kochan kochan 4096 maj 11  2012 VOC2012
╭─user@user-pc /media/sdb1/dev/learn/keras-frcnn  ‹master›
╰─$ python train_frcnn.py --path=/home/machinelearning/datasets/VOCdevkit/
Using TensorFlow backend.
Parsing annotation files
[Errno 2] No such file or directory: '/home/machinelearning/datasets/VOCdevkit/VOC2007/ImageSets/Main/trainval.txt'
[Errno 2] No such file or directory: '/home/machinelearning/datasets/VOCdevkit/VOC2007/ImageSets/Main/test.txt'
Traceback (most recent call last):
  File "train_frcnn.py", line 79, in <module>
    all_imgs, classes_count, class_mapping = get_data(options.train_path)
  File "/media/sdb1/dev/learn/keras-frcnn/keras_frcnn/pascal_voc_parser.py", line 46, in get_data
    annots = [os.path.join(annot_path, s) for s in os.listdir(annot_path)]
FileNotFoundError: [Errno 2] No such file or directory: '/home/machinelearning/datasets/VOCdevkit/VOC2007/Annotations

Python 3.6.3 :: Anaconda, Inc.

Not sure if there may be unintended consequences to this, but I got around the error by editing pascal_voc_parser.py as to replace:
 ['VOC2007', 'VOC2012']
with
 ['VOC2012']
FWIW, after 96 epochs (resnet50) where only VOC2012 is used, I get a model that at least seems to somewhat work for person detection though it didn't seem to work well for other objects.

The combined capacity of ['VOC2007', 'VOC2012'] = 22136 training images, giving your model a better chance at generalization(assuming everything else is in place). Removing 'VOC2007' simply deprives your model of the additional training data (5011 images to be specific). To train on both datasets, download them into /path/to/pascalvoc/ as VOC2007 and VOC2012.


Custom Helpers for Query Builder

Is it possible to add a custom Helper to the Query Builder.
If so, where can I put this?

@theobouwman maybe you need use query scopes?
http://adonisjs.com/docs/3.1/lucid#_query_scopes

@belozer na, not really

Hey @theobouwman!
What do you mean by custom Helper if it's not Query Scope?

Closing since no updates from the reporter


My robot do not move with cmd_vel sent

ISSUE TEMPLATE ver. 0.2.0

Which TurtleBot3 you have?

[x] Burger
[ ] Waffle
[ ] Waffle Pi

Which SBC(Single Board Computer) is working on TurtleBot3?

[ ] Raspberry Pi 3
[ ] Intel Joule 570x
[x] up board

Which OS you installed in SBC?

[X ] Ubuntu MATE 16.04 or later
[ ] Raspbian
[ ] etc (PLEASE, WRITE DOWN YOUR OS)

Which OS you installed in Remote PC?

[x] Ubuntu 16.04 LTS (Xenial Xerus)
[ ] Ubuntu 18.04 LTS (Bionic Beaver)
[ ] Linux Mint 18.x
[ ] etc (PLEASE, WRITE DOWN YOUR OS)

Write down software version and firmware version

Software version: [1.12.14]
Firmware version: [x.x.x]

Write down the commands you used in order

roslaunch turtlebot3_bringup turtlebot3_robot.launch
rostopic pub -r 10 /cmd_vel geometry_msgs/Twist  '{linear:  {x: 0.1, y: 0.0, z: 0.0}, angular: {x: 0.0,y: 0.0,z: 0.0}}'
robot suppose to move but did not. So I checked the cmd_vel. rostopic echo /cmd_vel. I do saw a lot of message are receiving.
I checked rostopic echo /diagnostics. I found something wired like this, I guess something wrong. because I remember it suppose show some useful things.

"
header:
seq: 20
stamp:
secs:<PHONE_NUMBER>
nsecs: 546103237
frame_id: ''
status:
level: 0
name: ''
message: ''
hardware_id: ''
values: []

level: 0
name: ''
message: ''
hardware_id: ''
values: []

level: 0
name: ''
message: ''
hardware_id: ''
values: []

level: 0
name: ''
message: ''
hardware_id: ''
values: []

level: 0
name: ''
message: ''
hardware_id: ''
values: []
""
5.  I then update firmware base on this page http://emanual.robotis.com/docs/en/platform/turtlebot3/opencr_setup/#opencr-firmware-upload-for-tb3. still not move
6. Then I go this step  Setup Dynamixels for TurtleBot3:  please refer the error at the png file. http://emanual.robotis.com/docs/en/platform/turtlebot3/faq/#setup-dynamixels-for-turtlebot3

when I go back to bringout. I found some new error. I guess it does not matter" the major error is the step 6.

"ERROR] [1546578809.571690]: Unable to sync with device; possible link problem or link software version mismatch such as hydro rosserial_python with groovy Arduino
[ERROR] [1546578824.575145]: Unable to sync with device; possible link problem or link software version mismatch such as hydro rosserial_python with groovy Arduino
[ERROR] [1546578839.579704]: Unable to sync with device; possible link problem or link software version mismatch such as hydro rosserial_python with groovy Arduino"

I can't help you.
Please write down the issue sheet in detail.

Hi @angrysword :)
I think that this issue is OpenCR firmware. Could you try to update OpenCR using Arduino?
Refer to this.
Thanks,
Gilbert.

Hi @kijongGil ,
 I have updated the firmware, bringout is good now as it was. However, the problem is still there. It did not move the robot after I pub some cmd_vel. The below is diagnostics info . I think it did not find the motor.

header:
seq: 42
stamp:
secs:<PHONE_NUMBER>
nsecs: 170895867
frame_id: ''
status:
level: 0
name: "IMU Sensor"
message: "Good Condition"
hardware_id: "MPU9250"
values: []

level: 0
name: ''
message: ''
hardware_id: ''
values: []
level: 0
name: ''
message: ''
hardware_id: ''
values: []
level: 0
name: ''
message: ''
hardware_id: ''
values: []
level: 0
name: ''
message: ''
hardware_id: ''
values: []


Updating broken link (and pointing to new pkg.go.dev)

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


'Headers' is undefined

I am getting following error only in IE
SCRIPT5009: 'Headers' is undefined
File: aurelia-fetch-client.js, Line: 90, Column: 7
this is the line in aurelia-fetch-client.js , where i am getting the error:
if (defaults && defaults.headers instaehnceof Headers) {
Any solution, or i am doing something wrong...
I am using Typescript as my language to code. I have also looked into the d.ts file its also right.

You will need to include the fetch polyfill.


Menu doesn't move with selection when scrolling

Select text, then scroll. The menu won't stay tethered to the selection.

SelectionMenu doesn't suffer from this problem.
Demo and screencast:


higher required then latest gives "out of date"

I use [patch.crates-io] to override the crate used in my project when I make a bug fix that is waiting to be upstreamed.
However this results in a higher version then is listed on crates.io causing the deps.rs listing to say "out of date", when it should really say "up to date".
Occurs on vulkano-win here: https://deps.rs/repo/github/rukai/pf_sandbox

Hmm, yeah, that's an interesting problem!
Technically when a dependency is "patched" through [patch.crates-io] there is no easy way to figure out whether that patch is strictly less or more recent than the last published version of the dependency (DVCS being what it is, it could even be both less and more recent).
I'm inclined to say that maybe patched dependencies shouldn't not count either way, but rather be tracked as "patched" (as opposed to "outdated" or "up to date").
There is similar logic today for dependencies that are sourced directly from a git repository, e.g.
[dependency.foo]
git = ...

Would that kind of solution work for you? Effectively it would exclude patched dependencies from weighting in for the dependency status, and an "up to date" status would be achievable even in the presence of patched dependencies.

That sounds great!

This situation also happens when deps.rs cannot detect the latest version on crates.io because of cache.
(The latest version on crates.io is 0.15.1 in this image)


fix: notation unexpander on overapplication of non-nullary notation

Fixes #2045

Should be uncontroversial, the code movement into Prelude really is a general fix to allow more quotation features early.

On leanprover/lean4:nightly-2023-02-03, I'm still having the problem reported by @PatrickMassot in #2045:
variable (f : α → β) (g : β → γ) (x : α)

#check (g ∘ f) x           --Function.comp g f x : γ

Wasn't this supposed to fix it?

Thanks for the reminder, should be fixed in the next nightly


Track how many people start a quiz

this involves db and frontend and backend work

Done as of 55b439e506e05d7c7e2a812908d6b1b498b65287


PDB parse_element_string fix, error on fully uppercase element strings

It was erroring on MG, ZN and some other element strings. Quick fix for element strings of length 2 => First letter uppercase, second lower case.

Good catch, thx! I think you could use Base.titlecase here instead of your if construct:
result = parse(Elements, titlecase(es))


Issue with key

I get the following message after running the script:
Google Maps JavaScript API warning: NoApiKeys https://developers.google.com/maps/documentation/javascript/error-messages#no-api-keys
My key is activated, no restrictions billing is enabled on Google Cloud Platform, and the key is inserted into the script.
Could the issue be related to the application being writen for API v2?
Google's troubleshooting page reports the following:

NoApiKeys
Warning
The script element that loads the API has no API key. Please make sure       you include a valid API key as a key parameter.       You can generate a new API key in the Google Cloud Platform Console.              See          Get an API key.                     If you are loading Maps JavaScript API from the deprecated v2       path with an old v2 key, you will get the NoApiKeys warning,       even if you specified the key parameter. Please check the       v2 to v3 upgrade guide       and migrate your application to Maps JavaScript API v3.

https://developers.google.com/maps/documentation/javascript/v2tov3

@cnaptik The script is using v3 of the Google Maps API. If you are using the Autocomplete field, make sure your API key has access to the Places API:
The map or autocomplete field search shows "This page can't load Google Maps correctly" or "For development purposes only"
This usually indicates an issue with your API key. Make sure you set the API key variable. Check that the API key has access to both the Maps JavaScript API, and if you are using the Autocomplete Field, the Places API. If you are still having trouble, follow Google's API key troubleshooting steps.
Additionally, make sure you only inserted the key in the variable on line 17, nowhere else in the code.

Thanks a lot for your very prompt answer!
It is now working. The problem was that I had inserted the key on both line 17 and line 148.


Sybil Attacker Report

Related Safe Addresses
batch 1:
0xf1054ed333a92c4c5e6ffae27b6bc379c8f7d89e
0x5d4d4e90fd99a907f779fb419deb7f80bebcac9a
0x243a46b5708889fb09fb6a789fef7d67c7f60684
batch2:
0x7f8db4e0374f58cfe7de774db4c9806b30c9bf31
0xab0e85e0b14a8bd14f4a0b479c4040fc3904cf91
0x12c907bf798759ffc57b5b8e65f006f70b485914
0x61909a19a0159d03cfed0c14ddd104f956d10284
0xc0a3de036e9c5727bf762aaba0fe914376c6d37f
0x52fc3796b3efc323f38fb764f3fcf31abf5f2565
0xab6e0003a04183a513d4b052c41d9ed3573688f7
0xc1efc164344a2d616e36bf4a5f2e7e819744daf2
0x8e51f9019f916a85633ca634a7d446ca15549309
0xb5c74cc8668709a8e333546ba832daa12ac65791
Reasoning

Each Safe Address finished first transaction between 2022-07-06 and 2022-07-07
batch 1 has 51,59,65 transactions
batch 2 has 23,24,25 transactions
the transaction volume for batch 1 is always the 0.01
the transaction volume for batch 1 is always around 0.1
for each address, the time gap between two successive transactions is also the same. This behavior strongly indicates the transaction is made by bots/scripts, not manually.
The volume in the same period for a large proportion on each address transactions, they happened as follows
batch 1 , at 04:15 UTC  2022-07-07,   at 06:19 UTC 2022-07-07 ,at 08:14 UTC 2022-07-09 same transaction etc..
batch 2, at 09:56 UTC 2022-07-06 , at 11:05 UTC 2022-07-06 , at 11:33 UTC 2022-07-06 same transaction etc....
same transactions for a large proportion on each address transactions.

https://github.com/michaelhadoop/Safe_sybil_attack_report/blob/fd18c2da82cf5cc610ca78c93a84ba92fae9bee7/sybil-attack-analytics-%23456.xlsx
Methodology
Same issue as #306
Safe Address
0x4069CCDd9e25D9E106ECa36561b2F6d787425110

Thanks for the report. We found the following to be related to airdrop farming:
0xf1054ed333a92c4c5e6ffae27b6bc379c8f7d89e
0x5d4d4e90fd99a907f779fb419deb7f80bebcac9a
0x243a46b5708889fb09fb6a789fef7d67c7f60684
0x7f8db4e0374f58cfe7de774db4c9806b30c9bf31
0xab0e85e0b14a8bd14f4a0b479c4040fc3904cf91
0x12c907bf798759ffc57b5b8e65f006f70b485914
0x61909a19a0159d03cfed0c14ddd104f956d10284
0xc0a3de036e9c5727bf762aaba0fe914376c6d37f
0x52fc3796b3efc323f38fb764f3fcf31abf5f2565
0xab6e0003a04183a513d4b052c41d9ed3573688f7
0xc1efc164344a2d616e36bf4a5f2e7e819744daf2
0x8e51f9019f916a85633ca634a7d446ca15549309
0xb5c74cc8668709a8e333546ba832daa12ac65791


The use of domains

Just now, Matias Salimbene requested information on how one or more organizations should use domains. What is the recommended approach? A domain per organization should work, in my opinion.
Still, we can have different situations in different setups using Iroha 2, and I'd like to hear your input before either I or someone else writes the details.
To be more specific, I think we should explain the different approaches similarly to the "choosing between the store and metadata assets" article.

One org can have more than one domain.
Domain metadata can link things (kv).
Config reference will have details on Kura.


[eas-cli] Export ora as default from mock

Checklist

[ ] I've added an entry to CHANGELOG.md if necessary. You can comment this pull request with /changelog-entry [breaking-change|new-feature|bug-fix|chore] [message] and CHANGELOG.md will be updated automatically.

This is a mock-fix only, so I don't think it should be listed in the changelogs. It's just an internal thing.
Why
We import ora as default import in src/ora.ts. Whenever we test anything that includes Ora code, it would fail with this error (source):
TypeError: (0 , ora_1.default) is not a function
  24 |   const inputOptions = typeof options === 'string' ? { text: options } : options ?? {};
  25 |   const disabled = Log.isDebug || !process.stdin.isTTY;
> 26 |   const spinner = oraReal({
     |                          ^
  27 |     // Ensure our non-interactive mode emulates CI mode.
  28 |     isEnabled: !disabled,
  29 |     // In non-interactive mode, send the stream to stdout so it prevents looking like an error.

How
Export the ora stub as default from the mock.
Test Plan
Add this export as default, and try to test code using ora (e.g. see PR #1116)

Ah I think you are right, I mistakenly took this for a node module mock while it's positioned as a user module mock.


how i create a FlxUITabMenu?

Describe your problem here.
how i create a FlxUITabMenu?
its for a editor state
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
nothing

You already have an open issue, don't create another one

You already have an open issue, don't create another one

so, how i make a flxuitabmenu

so, how i make a flxuitabmenu

don't duplicate the same issue and be patient

Idk, it's not even psych engine related

Idk, it's not even psych engine related

Haxe and Psyche seem pretty related to me...

well no this is for psych engine issues, not haxe

Idk, it's not even psych engine related

Haxe and Psyche seem pretty related to me...

psych uses haxe, but the thing he is requesting is not psych related sooooo


Stringmatcher: factory context for ext_authz

Commit Message:
Additional Description:
Part of #32792
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/retest

/retest


Support querying log analytics/data explorer

It would be beneficial to be able to query all different data sources from Azure Data Studio. Thus being able to query Log Analytics/Data Explorer would be great.
This would provide more weight to Azure Data Studio being the tool for querying data in Azure and on premise.
https://feedback.azure.com/forums/267889-log-analytics/suggestions/36598216-integrate-log-analytics-with-data-studio-to-have-d
https://feedback.azure.com/forums/915733-azure-data-explorer/suggestions/36598138-have-an-desktop-client-that-allows-sharing-of-quer

+1 for being able to connect data studio directly to my Az Log Analytics Workspace and running/saving/managing my KQL queries locally.

we do have these extensions now, please give them a try.


Added keywords for spooky things. 💀 ☠ ⚰

👻 WoooOOoooo... 👻
Added "pirate" to skull_and_crossbones because the pirate flag is not everywhere yet.

LGTM. Thanks!


[RFC] OpenSearch Simple Schema : Search

Is your feature request related to a problem?
Why Use a Schema?
Schema is a means to address the problems of managing and handling unstructured or loosely structured data, in opensearch we need to address the following concerns regarding the stored data:
Integrity - when data is semi/weakly structured - it is hard or even impossible to control the state and validity of the data.
Accessibility and retrieval - without high-level structure comes the lack of possibility to query the data meaningfully:

it may be since our data structure is too low level to express complex queries
handling the complexity of such super detailed and low level queries becomes a problem.
it's hard to express search relevancy in a structured-domain related question without the explicit schema definition

Consequently, we might be forced to ask simple questions only or fall back to client side reasoning functionality.
Maintenance -  With very little control over the structure of our data it is hard to alter that structure over time as requirements change.
What solution would you like?
The schema defines a specific, high-level structure of data that is enforced across the datasets, providing:

logical integrity guarantees
consistency guarantees
maintenance simplified and can be automated
build-in tools for defining relevancy inside the (schema) data-domain

A well-constructed schema enables writing intuitive queries, such queries are seamlessly mapped with how we form them as questions in our mind.
Using a schema sets the ground for performing automated reasoning over the represented data.
----- Introducing opensearch simple search draft - https://github.com/opensearch-project/sql/issues/763  -----
What alternatives have you considered?
A clear and concise description of any alternative solutions or features you've considered.
Do you have any additional context?
Add any other context or screenshots about the feature request here.

@YANG-DB How do you see the schema here as it relates to index mapping for search applications? Defining a schema per application for e-commerce & document search makes sense and can be accomplished by 1) letting the mapping be autodetected at index time and refining that mapping or 2) defining the mapping intentionally up front while designing your document structure. In details in the https://github.com/opensearch-project/sql/issues/763 proposal, I see that this is all geared towards observability to start. That makes sense given the three pillars (i.e. logs, metrics, traces) and there may be some bootstrapping we could do for search applications, but I assume those schemas would most likely diverge quickly. Do you see this differently?

@macohen
I think that a schema is a common need for every type of domain - the physical schema dictates the index mapping and the logical schema represent the real world entities and relations
Our goal here as a search engine is giving the logical schema for query time questions and having the physical schema for the execution time
This will allow max flexibility during the planing of the relevant domain schema and evolve the logical schema with little physical changes as possible.
Existing open source schema repositories we can review and consider:

https://schema.org/
https://www.wikidata.org/wiki/Wikidata:Database_reports/EntitySchema_directory

The search apps team reviews this and concluded that it's outside of our current direction.
We might think about trying to define some domain-specific schemata for different search use-cases, but that's probably not something we would address this year.
@YANG-DB -- Are you currently doing or planning anything to support this? Should we move this to another repo?

Hi
The simple-schema project is the facility of defining and using a scheme on top of open search.
It will have an API for other plugins to introspect the domain scheme and use this knowledge for their own use case


Fix statuses

Description

Add logging of dspa namespace to metrics logging  (fix https://github.com/opendatahub-io/data-science-pipelines-operator/issues/123)
Update statuses for dspa when components are scaled down (fix https://github.com/opendatahub-io/data-science-pipelines-operator/issues/122)

Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

/lgtm
/approve


[torchlib] topk results do not match when input is int64

Is it about the ordering when values are the same? Wonder if either is stable sort.

It could be - I haven't looked into that yet. The same happens for int32


plantuml: 1.2024.5 -> 1.2024.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/plantuml/versions.
meta.description for plantuml is: Draw UML diagrams using a simple and human readable text description
meta.homepage for plantuml is: https://plantuml.com/
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.2024.6 in filename of file in /nix/store/cx6ix3jgjqmp44kw5pj837mgqpwzjjcd-plantuml-1.2024.6

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath

plantuml
plantuml-c4
python311Packages.plantuml-markdown
python311Packages.sphinxcontrib-plantuml
python312Packages.plantuml-markdown
python312Packages.sphinxcontrib-plantuml
vscode-extensions.jebbs.plantuml

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/cx6ix3jgjqmp44kw5pj837mgqpwzjjcd-plantuml-1.2024.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A plantuml https://github.com/r-ryantm/nixpkgs/archive/20ea72b1c80412c8983791dc0b78d63962637d5a.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/20ea72b1c80412c8983791dc0b78d63962637d5a#plantuml

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/cx6ix3jgjqmp44kw5pj837mgqpwzjjcd-plantuml-1.2024.6
ls -la /nix/store/cx6ix3jgjqmp44kw5pj837mgqpwzjjcd-plantuml-1.2024.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

plantuml-c4

10 packages built:

plantuml
python311Packages.plantuml-markdown
python311Packages.plantuml-markdown.dist
python311Packages.sphinxcontrib-plantuml
python311Packages.sphinxcontrib-plantuml.dist
python312Packages.plantuml-markdown
python312Packages.plantuml-markdown.dist
python312Packages.sphinxcontrib-plantuml
python312Packages.sphinxcontrib-plantuml.dist
vscode-extensions.jebbs.plantuml

Maintainer pings
cc @bjornfor @mogria for testing.

@ofborg build plantuml-c4

The plantuml-c4 error is:
plantuml-c4> Error: A JNI error has occurred, please check your installation and try again
plantuml-c4> Exception in thread "main" java.lang.SecurityException: Invalid signature file digest for Manifest main attributes

So it looks like https://github.com/plantuml/plantuml/issues/1850


[systemtest] Increase test timeout for self-checking apps

Increase the timeout to receive a PASS indication from self-checking
tests running under Verilator from 4 to 10 minutes to reduce the risk of
flaky tests.

That's what you get from running on free infrastructure :smile: Overall a fair deal I'd say.


Allow synchronization of deployments

ie. only swapping the symlink of a multiservers/multiconnections deploy when all of them are ready to

Closed by 20ced2157332f65b568207f1750f4a27fb93d711


@conda-forge-admin please rerender

Additional comment:
No response

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I rerendered the recipe in conda-forge/wxwidgets-feedstock#19.


Update basic-tutorial.md

Point references to their proper namespaces and classes.

I'd argue that whole tutorial is lacking in quality... Would be nice to give it a proper upgrade.

Agreed but I learned some very basic working stuff so I wouldn't knock it too hard
Sent from my iPhone

On Jun 24, 2015, at 8:34 PM, Krzysztof<EMAIL_ADDRESS>wrote:
I'd argue that whole tutorial is lacking in quality... Would be nice to give it a proper upgrade.
—
Reply to this email directly or view it on GitHub.

@petersmax thanks for the contribution, however I'm not sure why we'd want the tutorial to fully qualify the namespaces of all classes, to me it just makes it look more complicated?

well naturally I would have to agree in that case

Maximus Peters
On Wed, Jun 24, 2015 at 11:48 PM, Jonathon Rossi<EMAIL_ADDRESS>wrote:

@petersmax https://github.com/petersmax thanks for the contribution,
however I'm not sure why we'd want the tutorial to fully qualify the
namespaces of all classes, to me it just makes it look more complicated?
—
Reply to this email directly or view it on GitHub
https://github.com/castleproject/Windsor/pull/91#issuecomment-115092706.

but would like to note that the namespace references to Component is
ambiguous and it keeps thinking that it is referencing .NET .Component
namespace... as for ClassLibrary it also could not find it either until I
added that.

Maximus Peters
On Thu, Jun 25, 2015 at 6:51 AM, Maximus Peters<EMAIL_ADDRESS>wrote:

well naturally I would have to agree in that case

Maximus Peters
On Wed, Jun 24, 2015 at 11:48 PM, Jonathon Rossi<EMAIL_ADDRESS>
wrote:

@petersmax https://github.com/petersmax thanks for the contribution,
however I'm not sure why we'd want the tutorial to fully qualify the
namespaces of all classes, to me it just makes it look more complicated?
—
Reply to this email directly or view it on GitHub
https://github.com/castleproject/Windsor/pull/91#issuecomment-115092706
.


Less death not shown

Only in very odd cases though.

@jossmac is this still the desired behaviour?

@jossmac can you confirm,  does less still silently die occasionally?