Sporadic GoferRepositoryError via Metacello/SmalltalkCI

The project Vivide experiences sporadic issues on TravisCI via SmalltalkCI while loading the dependencies (including this and that).
It is always some (other) repository that cannot be fetched. Manual retries will eventually solve the problem, and the build will pass. I get the following hint in Travis' output:
gofer repository error: 'GoferRepositoryError: ByteString called #basicNew: with invalid argument -236'...ignoring

I suspect that some HTTP request might not behave as expected and somewhere in the requestor (VM, Plugin, Squeak's sockets, Squeak's unzip mechanism, Gofer, Metacello, ...) the issue occurs and propagates up to Gofer.
I think that a more elaborate error log in Gofer can give us more clues here. Not sure how to enable such a thing. :-)
Best,
Marcel

Metacello has the ability to unconditionally fail in the face of a GoferRepositoryError (see
MetacelloCommonMCSpecLoader class>>retryPackageResolution and MetacelloCommonMCSpecLoader class>>retryPackageResolution:) but I'm not sure if you can arrange to set that for a Travis run --- it can be challenging to debug issues remotely via Travis.
The best bet for figuring out what is going on is to reproduce this in an interactive environment with retryPackageResolution set to false ... then a debugger can be used to quickly get to the heart of the problem ...
It should be possible to run SmalltalkCI interactively, but the type of failure you are describing should happen during regular Metacello loads, do you see these failures running local loads?

No, it always loads w/o debuggers locally once SqueakSSL is up an running. 😄

Am 26. Februar 2018 17:27:25 MEZ schrieb Marcel Taeumel<EMAIL_ADDRESS>
No, it always loads w/o debuggers locally once SqueakSSL is up an
running. 😄

;P
Sent from mobile device

Hmm, that complicates things ... I don't think there is a way to customize the version of Metacello that is used by SmalltalkCI ... short of creating a clone of SmalltalkCI that uses a custom Metacello version, In the past I've debugged these problems by dumping stacks or logging additional information to the transcript.
In this case we need to start by dumping a stack in MetacelloCommonMCSpecLoader>>retryingResolvePackageSpecReferences:gofer: and then work backwards with logging as we learn more about what is going wrong ...
Alternatively, if we can figure out the code involved in the bogus ByteArray creation, we could possibly work forward and understand the issue from that direction --- putting in some logging that is only triggered on errors or at least code that could be safely put into the master branch of Metacello ...
It just occurred to m e that I may have seen a similar issue elsewhere: Error when loading from github (failed only on gemstone) ... If you work your way down the thread there's a bug in ZipArchive when used with large zip files ... of course the error is not quite the same and in Mariano's case it was not intermittent ...but it may be related somehow...

@dalehenrich you can run a custom script before loading a project and do whatever you want with the image, e.g. patch Metacello methods. Apart from that, there's only #useLatestMetacello because that seems like a common request. Not sure if we really need to support loading of a specific Metacello version for debugging purposes in smalltalkCI?
Maybe you could provide a changeset that adds additional logging, so Marcel can file that in before Vivide is loaded.
I'm not sure if this is the reason for the error, but the VMs smalltalkCI uses for Squeak are quite old, because there are still some problems with SqueakSSL. I hope we can update them soon...

Perhaps the root cause is actually the old vms being used by SmalltalkCI? What do you think @krono? if I is likely to be a Metacello issue then we'll need to go into debug mode...

Old VMs is very likely. @fniephaus lets wait for a OpenSmalltalk VM release?

Ok then, let's wait for the release and I will give those new VMs a try...fingers crossed

Here are all variations of this behavior:
Job 347760798
Could not resolve: BaselineOfAnimations [BaselineOfAnimations] in /home/travis/smalltalkCI-master/_builds/package-cache github://hpi-swa/animations:master/repository ERROR: 'GoferRepositoryError: can''t find EOCD position'

Job 345921210
Could not resolve: BaselineOfWidgets [BaselineOfWidgets] in /home/travis/smalltalkCI-master/_builds/package-cache github://hpi-swa/widgets:master/repository ERROR: 'GoferRepositoryError: '

Job 345921211
Could not resolve: BaselineOfSignals [BaselineOfSignals] in /Users/travis/smalltalkCI-master/_builds/package-cache github://hpi-swa/signals:master/repository ERROR: 'GoferRepositoryError: ByteString called #basicNew: with invalid argument -236'

...maybe just a socket problem after all? Broken ZIP download and hence "EOCD" and negative byte string sizes...


OOC-3753 Updates

Captialize optionaltext
Add missing validation option
Update broken error message

Quick q, why do we need to set the any.required messages in the json? They seem to be okay in prod as is

Quick q, why do we need to set the any.required messages in the json? They seem to be okay in prod as is

The default has changed in the merge upstream. All required messages used to be the same by default but the default has changed (the any.required now sets to a "select X" error message rather than "x is required" for radio and checkboxes). To maintain existing behaviour but also bring in the new defaults I've updated the json file.
I spoke with Ge from design and the steer they've always had in the past is to use the XGov default messaging, but the messaging doesn't make sense with the new defaults and question names we have (e.g. "Enter Please Enter your local HPT" would be the new error for the HPT question. Ge has said he's going to look at the error messages now he can see the new defaults and create a ticket to update in the future, but for now wants to maintain the existing behaviour, which means we can't use the "any.required" default that's been brought in by merging in upstream. Any further questions I'm happy to hop on a call and show the original diff :)

Quick q, why do we need to set the any.required messages in the json? They seem to be okay in prod as is

The default has changed in the merge upstream. All required messages used to be the same by default but the default has changed (the any.required now sets to a "select X" error message rather than "x is required" for radio and checkboxes). To maintain existing behaviour but also bring in the new defaults I've updated the json file.
I spoke with Ge from design and the steer they've always had in the past is to use the XGov default messaging, but the messaging doesn't make sense with the new defaults and question names we have (e.g. "Enter Please Enter your local HPT" would be the new error for the HPT question. Ge has said he's going to look at the error messages now he can see the new defaults and create a ticket to update in the future, but for now wants to maintain the existing behaviour, which means we can't use the "any.required" default that's been brought in by merging in upstream. Any further questions I'm happy to hop on a call and show the original diff :)

In that case it seems like an issue with the validationOptions file. if you change it to:
required: "{{#label}} is required",
that should fix it no? Currently it's "Enter {question name}"

Quick q, why do we need to set the any.required messages in the json? They seem to be okay in prod as is

The default has changed in the merge upstream. All required messages used to be the same by default but the default has changed (the any.required now sets to a "select X" error message rather than "x is required" for radio and checkboxes). To maintain existing behaviour but also bring in the new defaults I've updated the json file.
I spoke with Ge from design and the steer they've always had in the past is to use the XGov default messaging, but the messaging doesn't make sense with the new defaults and question names we have (e.g. "Enter Please Enter your local HPT" would be the new error for the HPT question. Ge has said he's going to look at the error messages now he can see the new defaults and create a ticket to update in the future, but for now wants to maintain the existing behaviour, which means we can't use the "any.required" default that's been brought in by merging in upstream. Any further questions I'm happy to hop on a call and show the original diff :)

In that case it seems like an issue with the validationOptions file. if you change it to:
required: "{{#label}} is required",
that should fix it no? Currently it's "Enter {question name}"

It would fix it, but the design team in future want to use the XGov defaults, and I'm reluctant to change the default error messaging provided by XGov forms when the steer for the design team is to use the default messaging where they can. Our messages are custom, so I think it should be updated in the form. That way our code is a close to upstream as possible, and next time we merge with upstream we won't run into the same issues, as our custom changes will be front loaded and not touch the backend


Hi, I am not clear with the steps to run the benchmarks.  Could you please help me with elaborated sequence of steps to be followed to run this test. My setup details are : cpu: AMD FX 4100 quad core:: gpu: Ellesmere

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

Version used:
Environment name and version (e.g. rustc 1.26.0-nightly):
Operating System and version:
Hardware (e.g. CPU: Intel i5-6360U, GPU: Intel Iris Graphics 540, 8GB RAM)

Hello, do you know which open cl device is which? This can usually be found with the clinfo command

Ping @luckynikki


Use recommended style for fontawesom lists

Change the way the template renders un-ordered lists according to recommendations at https://fontawesome.com/v5/docs/web/style/lists
Fixes #72

Thanks @aelfric for updating the sample site, too!


Accessing PropTypes via the main React package is deprecated

I'm stuck in this warning:
bundle.js:59529 Warning: Accessing PropTypes via the main React package is deprecated, and will be removed in  React v16.0. Use the latest available v15.* prop-types package from npm instead.  Can anyone help me?

This is likeley an error generated from elsewhere in your application, this package uses the external prop-types package.


Added missing parameter 'timeit'

the PR contains changes of your local branch, including naming and refactoring of your own taste.
What is the purpose of the pr?


A11y_SQLMigrationControlPlane_  AssessmentResultsAndRecommendations _View/SelectButton_ScreenReader: Proper accessible name is not announced by the screen reader for the link "SQL Server Agent differences in azure SQL Managed Instance.

“Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”
GitHubTags:#A11yMAS;#A11yTCS;#AzureDataStudioextension'AzureSQLMigration'-Mac-Sept2022;#SQL Migration Control Plane;#A11ySev2;#WCAG1.3.1;#DesktopApp;#Win11;#ScreenReader;#Benchmark;#VoiceOver;#Mac
Environment Details:
Azure Data Studio: Version: 1.39.1
Operating System: Mac Version 12.5.1
Screen reader: VoiceOver
Steps to Reproduce:

Install Azure data studio and open
Tab till Extension press enter key and install Azure SQL Migration
Tab till Respective server and right click
Tab till manage and press enter key
5Tab till Azure SQL Migration and press enter key
Tab till migrate to azure SQL and press enter key
Saved session page will open
Select start new session and give next
Databases for assessment page will open
Select the respective databases and give next
Assessment results and recommendations page will open
Select Azure SQL managed Instance /Virtual Machines from Azure SQL Target
Tab till View/Select button, assessment results for '' dialog will open
Observe that Proper accessible name is not announced by the screen reader for the link "SQL Server Agent differences in azure SQL Managed Instance".

Actual:
Proper accessible name is not announced by the screen reader for the link "SQL Server Agent differences in azure SQL Managed Instance". It is only announcing "more info" link.
Expected:
Proper accessible name should be announced by the screen reader for the link "SQL Server Agent differences in azure SQL Managed Instance. It should announce like "more info, SQL Server Agent differences in azure SQL Managed Instance, link.
User Impact:
Screen reader users will get not proper info related to that link.
Screen Recording 2022-09-14 at 3.44.31 PM.zip

Can you please add the right aria-label to the more info links?

The expected aria-label should be "SQL Server Agent differences in azure SQL Managed Instance".

this issue is fixed in PR #20265

this issue was fixed as part of this PR:
20265

@brian-harris Please don't close a11y issues yourself, the a11y needs to verify and close them - so you should @-mention them to let them know they need to recheck.
(if there isn't a response in a week after doing that then we can close them ourselves though)

@BhanuPrakashGit Please validate that the issue is fixed using the latest insiders build

@Charles-Gagnon Tried to update the application but getting below error. Could you please tell me from where we can download the latest insiders build or what action should I take here? Thanks

Did you click the link in the notification? That should provide information on what to do when you see this error.
Here's the direct link to the Insiders download though if you want to just start fresh with the latest version : https://github.com/Microsoft/azuredatastudio#try-out-the-latest-insiders-build-from-main

Verified the bug in the env:
Azure Data Studio
Version: 1.39.1
Bug is fixed and does not repro. Hence closing the bug.
PFA for reference
Screen Recording 2022-11-28 at 11.38.15 AM.zip

Githubtags:  #AzureDataStudioextensionAzureSQLMigration-Mac-Sept2022;

Githubtags: #Closed;


Bug 1867169: Fix stale content in configmap due to stale bundle image in the node

If the bundle is already present in the node, during the unpack process
the configmap may potentially use a stale bundle image. The default
setting for ImagePullPolicy is IfNotPresent and should be changed to
Always.
Signed-off-by: Vu Dinh<EMAIL_ADDRESS>
Description of the change:
Motivation for the change:
Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Docs updated or added to /docs
[ ] Commit messages sensible and descriptive

This does potentially cause more egress from the cluster but the fix is necessary for the update feature to work correctly.
Also I assume this will also work in disconnected environments (since all bundle images are hosted internally) and shouldn't break anything else.
/lgtm

/retest

/retest

/retest

/approve

/retest

/retest

/retest

/retest

/retest

/retest

/cherry-pick release-4.5


12196 validate usages of :value before saving

Validates for both form "default name" and questioning "default answer".
Example:

Specs are flappers!


As a reader, I would like this handbook in epub format

Can you make this book available in Epub (or mobi) format?

Sorry for the delay. I've definitely wanted this in the past. You can definitely do this on your own using Pandoc or Gitbook. I think we'd accept PRs on this as well.

Can I work on this if its not already taken? I am trying to do gitbook, will update if it goes well!

Just saw this, but sure, go for it!

Just wrote a Ruby script to do this using pandoc, see below. Let me know if you'd like to have this as a PR in some way.
# Define chapters

chapters = [
  "Basic Types",
  "Variable Declarations",
  "Interfaces",
  "Classes",
  "Functions",
  "Generics",
  "Enums",
  "Type Inference",
  "Type Compatibility",
  "Advanced Types",
  "Symbols",
  "Iterators and Generators",
  "Modules",
  "Namespaces",
  "Namespaces and Modules",
  "Module Resolution",
  "Declaration Merging",
  "JSX",
  "Decorators",
  "Mixins",
  "Triple-Slash Directives",
  "Type Checking JavaScript Files"
]

# Reformat Markdown sources

full_content = <<-HEREDOC
---
title: TypeScript Handbook
author: Microsoft Corporation
rights: Apache License 2.0
language: en-US
---
HEREDOC

chapters.each do |chapter|
  file_name = "#{chapter}.md"
  content = File.read(file_name)

  # Increase section level of headings
  content = content.gsub(/(#){1,5}\s([^\n]*)/, '#\1 \2')

  # Add top-level heading
  content = content.prepend("# #{chapter}\n\n")

  full_content << content
end

File.write("all.md", full_content)

# Generate epub file

markdown_file_names = chapters.map { |chapter| "'#{chapter}.md'" }.join(" ")

system("pandoc -s -o ~/Desktop/TypeScript-Handbook.epub all.md")

File.delete("all.md")

@DanielRosenwasser Could you clarify what kind of PRs you'd welcome on this issue? I suppose for example one could rewrite the Ruby script as Typescript, and then perhaps move this to a new scripts folder.
What do you think?

Thanks for the code, before generating the book i needed to:
Save the nodejs/js code in a file called crea-sumary.js
and run:
node crea-sumary.js
then install gitbook and a dependencie:
npm install gitbook-cli -g
npm install svgexport -g
and finally generate the epub:
gitbook epub . typescript-handbook.epub

We ship a copy of the handbook with epub and pdf support now - http://www.staging-typescript.org/docs/handbook/


[apollo2] User appears logged out after reloading page

Form @eric-burel:
in context.js I got this code
const getAuthToken = req => {
  return req.headers.authorization || new Cookies(req.cookies).get('meteor_login_token');
};

the cookie does not seem to be set as soon as you authenticate, but only after the next page reload
to reproduce :

empty cache
login (eg in example-forms of the Starter). The cookie meteor_login_token is not set
reload page. You appear as logged out. During this reload, the cookie meteor_login_token is set.
reload again. Now you seem to be logged back in, because the cookie is correctly set. (edited)

I think the issue is that the cookie meteor_login_token is somehow stored too late, hence this behaviour. It should already work during the first reload. Note that you are actually never logged out, it's just SSR that fails to retrieve the user and thus render the page is if you were logged out. (edited)
see the auth.js, it is called on Meteor.start but should also be called after login I think
I'll need help on this, I am not really familiar with the auth system, I guess the solution is just running the auth.js initToken function in a callback triggered after login.

Fixed it was a small regression, sorry. When you save Meteor.loginToken into the localStorage, it is now automatically added to the cookies too.


typo fix

About the PR

Fixed a typo in the Agrichem is Fun PR that was missed.
Why / Balance

Typos are bad.
Technical details

N/A
Media

Requirements

[x] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

N/A
Changelog

perry beat me to it, closing


Registrar - Does not delete devices in the registry which are not in the site model

When running registrar, if there are devices registered in the IoT core registry, which are not defined in the site model, they are not deleted from the registry.
Default behaviour should be to remove them, so the registry matches the site model

Right now it blocks them rather than removing them. Deleting things is a
fairly disruptive operation so not likely the right default behavior. But
maybe creating a flag to say "delete them" would be appropriate...
On Tue, Jun 28, 2022 at 5:34 AM Noureddine @.***> wrote:

When running registrar, if there are devices registered in the IoT core
registry, which are not defined in the site model, they are not deleted
from the registry.
Default behaviour should be to remove them, so the registry matches the
site model
—
Reply to this email directly, view it on GitHub
https://github.com/faucetsdn/udmi/issues/378, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIEPDZM3IG2N6EPXKSMRZDVRLBMDANCNFSM52BPRD2A
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Right now it blocks them rather than removing them.

It's stopped doing that .. but I've just checked and seems to because it's become a configurable parameter. I've done a PR #382 to change the default.
But true about deletion, you're right. Default behaviour would be to block, and then a flag to delete devices if required (devices need to be unbound from respective gateways before they can be deleted). Maybe even a backup.. We have a use-case where a registry has with 20k of which about 5k are proxy devices aren't in the site model and were accidently created so need to be removed.

Right -- I'd recommend a two phase approach to that... First being to block
all devices that are candidates for deletion -- so we can test the system
to make sure it's WAI, and then a separate pass to "delete all blocked
devices" or something like that!
On Wed, Jun 29, 2022 at 10:03 AM Noureddine @.***>
wrote:

Right now it blocks them rather than removing them.
It's stopped doing that .. but I've just checked and seems to because it's
become a configurable parameter. I've done a PR #382
https://github.com/faucetsdn/udmi/pull/382 to change the default.
But true about deletion, you're right. Default behaviour would be to
block, and then a flag to delete devices if required (devices need to be
unbound from respective gateways before they can be deleted). Maybe even a
backup.. We have a use-case where a registry has with 20k of which about 5k
are proxy devices aren't in the site model and were accidently created so
need to be removed.
—
Reply to this email directly, view it on GitHub
https://github.com/faucetsdn/udmi/issues/378#issuecomment-1170022563,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIEPD56ZGN2II5HHK6FT4TVRRJTNANCNFSM52BPRD2A
.
You are receiving this because you commented.Message ID:
@.***>


Please remove your debugger; statements in production builds

Brief Issue Summary
Currently the released main.js in the cmake-tools extension includes serveral debugger; statements like in line 11006, 110061, 97194, 97223, 97311 and some more.
Since CMake-tools already floods the dev console, these debugger statements only add to the frustration, making it even more difficult to debug your own extensions when the extension is installed and enabled. Especially when working with virtual workspaces, it's all too common to get stuck in your own source code.
CMake Tools Diagnostics
<ERROR>

Debug Log
<ERROR>

Additional Information
An excerpt from the dev console:
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:08.694Z [info] [proc] Executing command: "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" --version (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:08.825Z [info] [proc] Executing command: "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" -E capabilities (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:08.955Z [debug] [main] Safe constructing new CMakeProject instance (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:08.956Z [debug] [variant] Constructing VariantManager (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:08.957Z [debug] [main] Constructing new CMakeProject instance (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:08.958Z [debug] [main] Starting CMake Tools second-phase init (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:08.959Z [debug] [expand] expanded ${workspaceFolder} (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:08.982Z [debug] [kit] Reading kits file C:\Users\MyUser\AppData\Local\CMakeTools\cmake-tools-kits.json (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:09.057Z [info] [kit] Successfully loaded 0 kits from C:\Users\MyUser\AppData\Local\CMakeTools\cmake-tools-kits.json (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:09.209Z [debug] [kit] Not reading non-existent kits file: c:\Users\MyUser\PicoDevTest\sdgsdfg\.vscode\cmake-kits.json (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:09.238Z [info] [variant] Loaded new set of variants (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:09.239Z [debug] [main] CMakeProject instance initialization complete. (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:09.240Z [debug] [main] Safe constructing new CMakeProject instance (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:09.241Z [debug] [variant] Constructing VariantManager (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:09.242Z [debug] [main] Constructing new CMakeProject instance (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:09.243Z [debug] [main] Starting CMake Tools second-phase init (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:09.245Z [warning] [expand] Invalid variable reference ${workspaceFolder} in string: ${workspaceFolder} (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
C @ console.ts:137
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:09.246Z [debug] [expand] expanded ${workspaceFolder} (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
log.ts:439   ERR [Extension Host] [CMakeTools] 2024-09-10T16:46:09.251Z [error] [rollbar] "sourceDirectory" is not a directory {"sourceDirectory":"${workspaceFolder}"}
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:09.251Z [error] [rollbar] "sourceDirectory" is not a directory {"sourceDirectory":"${workspaceFolder}"} (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
C @ console.ts:137
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:24.820Z [debug] [main] Not starting CMake driver: no kit selected (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:24.834Z [debug] [kit] Reading kits file C:\Users\MyUser\AppData\Local\CMakeTools\cmake-tools-kits.json (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:24.864Z [info] [kit] Successfully loaded 0 kits from C:\Users\MyUser\AppData\Local\CMakeTools\cmake-tools-kits.json (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:25.121Z [debug] [kit] Not reading non-existent kits file: \.vscode\cmake-kits.json (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:25.122Z [debug] [expand] expanded ${workspaceFolder} (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
log.ts:439   ERR [Extension Host] [CMakeTools] 2024-09-10T16:46:25.123Z [error] [rollbar] "sourceDirectory" is not a directory {"sourceDirectory":""}
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:25.123Z [error] [rollbar] "sourceDirectory" is not a directory {"sourceDirectory":""} (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
C @ console.ts:137
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:26.317Z [info] [variant] Loaded new set of variants (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:26.318Z [debug] [main] CMakeProject instance initialization complete. (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
log.ts:439   ERR [Extension Host] [CMakeTools] 2024-09-10T16:46:26.373Z [fatal] [rollbar] Unhandled exception: Unhandled Promise rejection: Post-folder-open false [object Object]
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:26.373Z [fatal] [rollbar] Unhandled exception: Unhandled Promise rejection: Post-folder-open false [object Object] (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))
C @ console.ts:137
console.ts:137 [Extension Host] [CMakeTools] 2024-09-10T16:46:32.313Z [debug] [main] Not starting CMake driver: no kit selected (at console.<anonymous> (c:\Users\MyUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:151:47754))

@paulober You can control how much logging comes from our extension by setting the cmake.loggingLevel to info and maybe of these will not be sent.

@gcampbell-msft Please reopen and remove the debugger calls. It's just rude for other extension devs.
I also did do your work and created a very simple PR which integrates with your current webpack build system to not execute debugger statements in production.
As you already use production and development mode for your webpack setup it auto-detects this and guards the statements.
(Sorry for my tone but deploying debugger statements and then shutting of people reporting it (twice) triggers me. Therefor I created a quick PR that will fix this in the next release)

And @Yingzi1234 as you requested more info on if debugger statements should be in your production code:
Here, a small excerpt from LinkedIn Web developer advices:

To use a debugger statement effectively, you need to follow some best practices and tips. For instance, you should only use a debugger statement for temporary debugging purposes and never leave it in production code.

[...]

Finally, it is wise to add comments or console.log statements to mark the places where you have inserted debugger statements. This will help you remember to remove them later and avoid confusion with other parts of your code.

source: https://www.linkedin.com/advice/1/what-debugger-statement-how-can-you-use-effectively

@paulober Thanks for the PR! We greatly appreciate it, I'll review it now 👍

thanks


Trojan Detected

Need to install the following packages:
<EMAIL_ADDRESS>Ok to proceed? (y) y
_
_____  ___ __   ___  ___  ___     __      | |
/ _ \ / / ' \ / _ / |/ _ _\ \ /\ / / | |
|  />  <| |) | () _ \  /\ V  V /_ \ |
_//_\ ./ _/|/_|      _/_/ |_/|
||
⏳ Downloading WSLHostPatcher... extracting... running... /home/support/.npm/_npx/0e95d415fb20f5d8/node_modules/expose-wsl/WSLHostPatcher.exe: Invalid argument
failed to run ❌
🔥 Please report this issue at https://github.com/icflorescu/expose-wsl/issues
/home/support/.npm/_npx/0e95d415fb20f5d8/node_modules/expose-wsl/WSLHostPatcher.exe: Invalid argument

also got this, is the source file infected, cause ive installed this script on another pc and no problem...
maybe a false positive?
i wont risk it until this issue is answered by dev.

As @CzBiX mentioned, this is to be expected. Afterall, the host patcher is executing some commands that alter the standard WSL behavior. Opening access from remote addresses could lead to security issues, but as a developer you probably know what you're doing.
The code is open-source and therefore publicly available, this project was born out of convenience, but if you have concerns, feel free to use the manual alternatives.


Angular 8 and CLI 8 do not build noticeable smaller bundles for es2015

🐞 Bug report
Command (mark with an x)

- [ x] build

Description
According to https://blog.angular.io/version-8-of-angular-smaller-bundles-cli-apis-and-alignment-with-the-ecosystem-af0261112a27, the bundle size with NG8 CLI8 could be 7-20% smaller. However, in my big fat NG client,
when with NG7 CLI7, the production bundle size for es2015 is 5.17 MB, excluding assets.
when with NG8.1 CLI8.1, the production bundle size for es2015 is 5.16 MB, excluding assets.
So less than 1% difference.
🔬 Minimal Reproduction
@filipesilva , this is loosely related to #13734 in which you had done the benchmark for memory consumption during build, with the repro of my big fat SPA. So I would presume that you can analyze this with the same repro.

The title is somewhat misleading as the bundles are indeed smaller just not as small as you expected.  Since your application is already ES2015 only and assuming that any unneeded polyfills are already removed, this particular application won't see the size reduction benefits as many applications would due to the application only supporting ES2015+ browsers.  IE11 is still a browser that many still need to target.
Note this paragraph from the linked blogpost in the differential loading section and the "for modern browsers" aspect:

On angular.io we saved over 40kB of initial bundle size for modern browsers. From the community we’ve heard that applications generally save 7–20% of their bundle size, depending on the amount of modern JavaScript features they take advantage of.

thank you for the clarification, which I had suspected such too. However, I was not sure if I had missed some "magic" switches in NG 8 and CLI 8 which may produce more optimization for smaller bundles of es2015.

Closing as there is nothing to action. As explained by @clydin in the above comment.


[BUG] Fails to detect existing configuration and overwrites it with default template

Have you read the Important information text above

[X] Yes i did

Current behavior
Despite having existing config files mounted, it fails to detect them and overwrites them with the template, every single time.
This has started happening today (likely related to #5), after the docker image was updated.
Desired behavior
Existing mounted config files should be respected.
Links to screenshots

To Reproduce

Launch the docker container to generate config files, then shut it down
Change config files as needed
Launch the docker container again
Config is overwritten by template

Software setup

OS: Ubuntu 22.04.3 LTS
Docker: Docker 24.0.5, Docker Compose 1.29.2

Hardware setup

CPU: Intel i7-10710U (6C/12T)
RAM: 32gb
Disk: 2 TB nvme

Additional context
No response

The standard config is copied every start on purpose, so you get the latest config and not a "not working server".
The usual stuff can be setup in the Docker-Compose file.
And yes #5 was the merge to help establish this setup.

The problem is that none of the config will ever survive a container restart, which is bad for a dedicated server. You'd never be able to config difficulty, rates or other configs if they're being replaced every boot.
Also, an empty password (on purpose because you want an empty password) on the env vars results in the default template password, which again, means you currently can't even access the server because the game itself also has a bug with asking for passwords (and also, you should  be able to just not have a password at all).

It's not gonna be good practice to overwrite everything with defaults every time. It should be up to the server software itself to generate missing files, add missing properties, and if the server wont launch due to old config, up to the user to remove old config files and regenerate them. If they exist they should be prioritized.

I have the same issue and even after updated my compose file, the configuration file has not been modified with the compose values. I overwrote my compose env variables with the one in the readme.
This is quite annoying because it reset the server password the default one and so making players unable to join the server ...

The latest version of the container allows for setting the SERVER_PASSWORD envvar, which should then be copied to the conf file :)

The latest version of the container allows for setting the SERVER_PASSWORD envvar, which should then be copied to the conf file :)

On systems like TrueNAS Scale, the environment variable can't be blank.  So how can we make it a public server without a password?

The latest version of the container allows for setting the SERVER_PASSWORD envvar, which should then be copied to the conf file :)

On systems like TrueNAS Scale, the environment variable can't be blank. So how can we make it a public server without a password?

Disregard. Double quotes works.

I have the same issue and even after updated my compose file, the configuration file has not been modified with the compose values. I overwrote my compose env variables with the one in the readme. This is quite annoying because it reset the server password the default one and so making players unable to join the server ...

Hey @Lakio21
This should defently be possible, update your docker-image please and maybe try a fresh docker-compose file from the template. I have testet this now surely 50+ times. If you have still problems let me know that we will get down to this.

@redeven if have fixed a lot of bugs, this should be better now i hope, please review and let me know.
Please go ahead and test things.
New Docker-Compose File is needed.
You can find now examples in the README.md.
The docker-compose.yml was removed because of dublicate code.

@jammsen Sorry for the late reponse. It was a little urgent so I end up forking your repo and revert to the previous state to make the server quickly up and running. I will give it ago later when I have more free time.

If this issue is solved, please give me feedback on the patch and please consider giving me a Star here and on Docker-Hub.

Ping

What would be the best way to update the server options that are not covered by the env vars in the game? For example bEnableFriendlyFire or GuildPlayerMaximum? Thanks!

While setting it through the env var (which requires doing SERVER_PASSWORD="" with quotes as an empty var will fail and get overwritten) works, it "expands" for lack of a better word, during the replacement in the settings file.

As you can see, on every boot, it adds extra quotes. The game server still seems to parse it as empty which is fine but it's definitely not the intended value replacement.

Please use  SERVER_PASSWORD= @redeven

What would be the best way to update the server options that are not covered by the env vars in the game? For example bEnableFriendlyFire or GuildPlayerMaximum? When I edit the values, they get overwritten on launch.

@gchai If you need other variables you are free to open an issue and i will look into that OR you join the issue #29 which "maybe wants" to have a "dumb" or "manual" mode to not use ENVs but only the config-file itself to be manually edited. Not sure what the requestor really wanted. But a manual/dum mode would be possible, while the ENVs way is considered Best-Practice in all of Docker and K8s / Twelve-Factor-App

I can add all the variables in as a Env Var and make a PR!

#40 submitted!

Hey @gchai
Thats some nice work, are you already on the readme for this too?

This behavior should be solved with https://github.com/jammsen/docker-palworld-dedicated-server/commit/8546c890a518c99ab9be13b35a876c01ddaa7bde#diff-3b41cd2eeb76ac64c4b71b9cc6b253b358ab737f50d54e333b631ca27357e98e
Feel free to reopen the issue if the problem persists.
If you like this project, please consider giving this repo and the docker-hub-repo a Star.


Fundamentals: Networks and nodes

Resources:
https://github.com/paritytech/polkadot-blockchain-academy/tree/main/syllabus/4-Substrate/4.7-Networking
https://github.com/paritytech/polkadot-blockchain-academy/tree/main/syllabus/4-Substrate/4.7-Networking_and_RPCs
RPC and custom RPC
https://polkadot.js.org/docs/api + smart contract RPC endpoint
Revise node role graphics.

Same error here -- do I need specific permissions to view that directory?


ProcessGroupNCCL does not support scatter

When trying running DLRM distributedly using mpirun with NCCL as the backend there is a runtime error "ProcessGroupNCCL does not support scatter". Is there anyway to solve that?
Thanks!

can u paste the complete trace?

The trace is as follows:
Traceback (most recent call last):
File "dlrm_s_pytorch.py", line 1056, in
Z = dlrm_wrap(X, lS_o, lS_i, use_gpu, device)
File "dlrm_s_pytorch.py", line 915, in dlrm_wrap
lS_i
File "/home/wisr/anaconda3/lib/python3.7/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
result = self.forward(*input, **kwargs)
File "dlrm_s_pytorch.py", line 331, in forward
return self.distributed_forward(dense_x, lS_o, lS_i)
File "dlrm_s_pytorch.py", line 401, in distributed_forward
a2a_req = ext_dist.alltoall(ly, self.n_emb_per_rank)
File "/home/wisr/aoranwu/dlrm/extend_distributed.py", line 439, in alltoall
output = All2All_Scatter_Req.apply(a2ai, *inputs)
File "/home/wisr/aoranwu/dlrm/extend_distributed.py", line 225, in forward
req = dist.scatter(out_tensor, scatter_list if i == my_rank else [], src=i, async_op=True)
File "/home/wisr/anaconda3/lib/python3.7/site-packages/torch/distributed/distributed_c10d.py", line 1380, in scatter
work = _default_pg.scatter(output_tensors, input_tensors, opts)
RuntimeError: ProcessGroupNCCL does not support scatter
Traceback (most recent call last):
File "dlrm_s_pytorch.py", line 1056, in
Z = dlrm_wrap(X, lS_o, lS_i, use_gpu, device)
File "dlrm_s_pytorch.py", line 915, in dlrm_wrap
lS_i
File "/home/wisr/anaconda3/lib/python3.7/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
result = self.forward(*input, **kwargs)
File "dlrm_s_pytorch.py", line 331, in forward
return self.distributed_forward(dense_x, lS_o, lS_i)
File "dlrm_s_pytorch.py", line 401, in distributed_forward
a2a_req = ext_dist.alltoall(ly, self.n_emb_per_rank)
File "/home/wisr/aoranwu/dlrm/extend_distributed.py", line 439, in alltoall
output = All2All_Scatter_Req.apply(a2ai, *inputs)
File "/home/wisr/aoranwu/dlrm/extend_distributed.py", line 225, in forward
req = dist.scatter(out_tensor, scatter_list if i == my_rank else [], src=i, async_op=True)
File "/home/wisr/anaconda3/lib/python3.7/site-packages/torch/distributed/distributed_c10d.py", line 1380, in scatter
work = _default_pg.scatter(output_tensors, input_tensors, opts)
RuntimeError: ProcessGroupNCCL does not support scatter

All2All_Scatter_Req

The trace is as follows:
Traceback (most recent call last):
File "dlrm_s_pytorch.py", line 1056, in
Z = dlrm_wrap(X, lS_o, lS_i, use_gpu, device)
File "dlrm_s_pytorch.py", line 915, in dlrm_wrap
lS_i
File "/home/wisr/anaconda3/lib/python3.7/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
result = self.forward(*input, **kwargs)
File "dlrm_s_pytorch.py", line 331, in forward
return self.distributed_forward(dense_x, lS_o, lS_i)
File "dlrm_s_pytorch.py", line 401, in distributed_forward
a2a_req = ext_dist.alltoall(ly, self.n_emb_per_rank)
File "/home/wisr/aoranwu/dlrm/extend_distributed.py", line 439, in alltoall
output = All2All_Scatter_Req.apply(a2ai, *inputs)
File "/home/wisr/aoranwu/dlrm/extend_distributed.py", line 225, in forward
req = dist.scatter(out_tensor, scatter_list if i == my_rank else [], src=i, async_op=True)
File "/home/wisr/anaconda3/lib/python3.7/site-packages/torch/distributed/distributed_c10d.py", line 1380, in scatter
work = _default_pg.scatter(output_tensors, input_tensors, opts)
RuntimeError: ProcessGroupNCCL does not support scatter
Traceback (most recent call last):
File "dlrm_s_pytorch.py", line 1056, in
Z = dlrm_wrap(X, lS_o, lS_i, use_gpu, device)
File "dlrm_s_pytorch.py", line 915, in dlrm_wrap
lS_i
File "/home/wisr/anaconda3/lib/python3.7/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
result = self.forward(*input, **kwargs)
File "dlrm_s_pytorch.py", line 331, in forward
return self.distributed_forward(dense_x, lS_o, lS_i)
File "dlrm_s_pytorch.py", line 401, in distributed_forward
a2a_req = ext_dist.alltoall(ly, self.n_emb_per_rank)
File "/home/wisr/aoranwu/dlrm/extend_distributed.py", line 439, in alltoall
output = All2All_Scatter_Req.apply(a2ai, *inputs)
File "/home/wisr/aoranwu/dlrm/extend_distributed.py", line 225, in forward
req = dist.scatter(out_tensor, scatter_list if i == my_rank else [], src=i, async_op=True)
File "/home/wisr/anaconda3/lib/python3.7/site-packages/torch/distributed/distributed_c10d.py", line 1380, in scatter
work = _default_pg.scatter(output_tensors, input_tensors, opts)
RuntimeError: ProcessGroupNCCL does not support scatter

this is because NCCL indeed does not support scatter I believe? If you can update your pytorch to the latest, the code should be directly usingt the all2all primitive. For scatter, you have to use MPI guess. But we will update the documentation for better debugging.

see https://github.com/pytorch/pytorch/issues/47291

It looks like this is resolved.


StopOnFirstFailure when doing repository builds

avoids MSBuild continuing past failed repositories in sequential builds
ignored when building in parallel (unfortunately)

Any objections?

I might be missing some context...but wasn't the "keep going even on failure" design intentional? e.g. sometimes we want the whole thing to run, even if some tests fail. This allows us to use TeamCity to mute a test.

This option doesn't work when $(BuildInParallel) is set. So, it should have no affect on CI builds.
In any case, the CI has been failing after the first repo with failed tests for ages.

Ok.

dd38898


Reapply presto change

TL;DR
Somehow I accidentally reverted the changes in presto_task.py made here: https://github.com/lyft/flytekit/pull/126/files
when I pushed to this PR here: https://github.com/lyft/flytekit/pull/107/commits/cebd511b29d7cc48756f3d32176d19104eb6df39
Type

[x] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[ ] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
How did you fix the bug, make the feature etc. Link to any design docs etc
Tracking Issue
https://github.com/lyft/flyte/issues/
Follow-up issue
NA
OR
https://github.com/lyft/flyte/issues/

Codecov Report

Merging #129 into master will decrease coverage by 0.01%.
The diff coverage is 56.25%.

@@            Coverage Diff             @@
##           master     #129      +/-   ##
==========================================
- Coverage   81.39%   81.38%   -0.02%
==========================================
  Files         217      217
  Lines       14145    14153       +8
  Branches     1159     1160       +1
==========================================
+ Hits        11514    11518       +4
- Misses       2349     2353       +4
  Partials      282      282

Impacted Files
Coverage Δ

flytekit/common/tasks/presto_task.py
74.41% <53.33%> (-5.59%)
:arrow_down:

flytekit/__init__.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Support of DPX with "v1.0" ("v" in lowercase)

if  --conch is used, there is a warning:
Warning: non-conforming DPX Version number of header format.

FFmpeg has another one:
[dpx @ 00000242E8204480] Unknown header format version v1.0.

but accepts it, so let's go.

Cc'ing @kmurmur who may have access to a version of the specification for the V1.0 version of the DPX specification as SMPTE no longer sells or provides access to this version of the specification. For reference, here is version 2 which makes a parenthetical mention of V2.0 but the expression of version is never defined.
Am noting that The LOC formats registry mentions:

Finally, the SMPTE Standards Quarterly Report from March 2015 indicates that the latest revision of the DPX v. 2 standard, SMPTE ST 268:2014 was found to contain "significant errors ...[and] a corrected version is being put together." The authors of this website will wait until a stable version is released before conducting any analysis.

but I can't find any particular update.
The FADGI DPX guidlines mentions that V1.0 and V2.0 are permissible values, but also acknowledges that "[ST268 has no formal definition for this field]".
Definitely worth reporting a bug to whatever muxer is writing these DPX frames.

specification for the V1.0 version of the DPX specification as SMPTE no longer sells or provides access to this version of the specification.

Archiving matters, including mine :).
ANSI/SMPTE 268M-1994:
3 8 8 ASCII C Version number of header format (V1.0)

The FADGI DPX guidlines mentions that V1.0 and V2.0

Reason I have put a conformance check on it. any supplier using --conch (or  --all) would have the warning in the log (once for RAWcooked, 1 time per frame for FFmpeg, ouch).

Definitely worth reporting a bug to whatever muxer is writing these DPX frames.

Not sure that AppleComputers.libcineon (c) 2007 will care about that :).
but scanner vendor could maybe update/change of lib, for you @digitensions :-p.

@digitensions could you ask Andy Sargeant to look at the SMPTE standards for v1 in case our subscription to the standards library makes that available? And could you let Lucy know which context this DPX came from so that we can add it to the document of which scanners create which issues for us?

Well, there are alot of fields in the DPX spec w/o formal definitions :).
In the DPX 2.0 fdd, I detailed all the differences bt v1 and v2 - I had access to a copy many moons ago but don't have it anymore although I'll look around a bit more

Just a quick note: I vaguely remember that Kodak’s Cineon specification has been useful to me, because in some regards it’s better than DPX v1. Somewhere I should still have it and during the weekend I can look for, if needed.

I vaguely remember that Kodak’s Cineon specification

For reference : Kodak’s "Cineon File Format Version 4.5 for Digital Film Images" specification.
But it is about Cineon file format.
I put in bold "file" here because I also found Cineon company DPX draft.
DPX draft from Cineon company.
Surprise, "v1.0" is there:
ASCII vers[8];          /* which header format version is being used (v1.0)*/

Be careful, in this doc there are 2 formats:

DPX draft is called "Cineon Image File Format Draft"
Legacy Cineon format is called "Cineon File Format Version 4.5 for Digital Film Images"

Summary: in 2007, someone was using a draft from 1994 while the official SMPTE doc was there during 10+ years.
@kmurmur it may worth it to document the differences between the DPX draft from Cineon and DPX v1 from SMPTE.

Thanks @JeromeMartinez - I'll add it to the list of things to do

Summary: in 2007, someone was using a draft from 1994 while the official SMPTE doc was there during 10+ years.

Funny indeed!
And thank you for the information.

ROFL: I just notice that DaVinci Resolve 16.2.8 still generates DPX V1.0 (with a capital V).

(with a capital V).

Which is the standard, or did I miss something?

Yes, of course, it is. Yet 1.0 in 2021…

Yet 1.0 in 2021

Well, there are actually not so many advantages of V2.0 IMO.

To me, there is the avantage that the standard 2.0 can be checked easily, which is not the case with 1.0, therefore is more difficult to discuss inconsistent real world implementations of 1.0 than of 2.0.


dropdown onClick bind fix

When dom data is loaded async and the dropdown functionality needs to be re-initiated via the same selector (e.g. $('.dropdown-button').dropdown({}))  previously bound buttons will fail to work. This fixes the problem.
But maybe a check for pre-existing binds is better?

It is fine to have them update all incase you update options.


iOS : not able to run app in Release mode

Steps to Reproduce

create simple app
Open in xcode
From xcode Select Runner on top and edit scheme
Now in Run section : Build Configuration : Select Release
Run app from xcode as well
It throws error like conenctivity module not found
same thing working in debug mode.

Expected results:
It should run in release mode as well.
Actual results:
Working only with debug mode , for release mode fails

Logs

[✓] Flutter (Channel stable, 2.0.5, on macOS 11.0.1 20B29 darwin-x64, locale en-GB)
    • Flutter version 2.0.5 at /Users/UserA/Library/Android/flutter
    • Framework revision adc687823a (6 weeks ago), 2021-04-16 09:40:20 -0700
    • Engine revision b09f014e96
    • Dart version 2.12.3

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/UserA/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] VS Code (version 1.55.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (1 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 90.0.4430.212

! Doctor found issues in 1 category.

Hi @mehtahardikr
Unable to reproduce the issue on the latest stable in a new project

flutter doctor -v
[✓] Flutter (Channel stable, 2.2.0, on macOS 11.3.1 20E241 darwin-x64, locale
    en-GB)
    • Flutter version 2.2.0 at /Users/tahatesser/Code/flutter_stable
    • Framework revision b22742018b (11 days ago), 2021-05-14 19:12:57 -0700
    • Engine revision a9d88a4d18
    • Dart version 2.13.0
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Volumes/Extreme/SDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Volumes/Extreme/SDK
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.5, Build version 12E262
    • CocoaPods version 1.10.1
[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
[✓] VS Code (version 1.56.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.22.0
[✓] Connected device (3 available)
    • Taha's iPhone (mobile) • 00008020-001059882212002E • ios            • iOS
      14.6
    • macOS (desktop)        • macos                     • darwin-x64     •
      macOS 11.3.1 20E241 darwin-x64
    • Chrome (web)           • chrome                    • web-javascript •
      Google Chrome 90.0.4430.212
• No issues found!

Can you please upgrade to the latest  stable and try again
Execute the following commands to upgrade
flutter channel stable
flutter upgrade --force
flutter doctor -v
First of all, delete Podfile in your existing project rm ios/Podfile
Make sure you've selected team ID and the physical device is connected when run the app so it can generate new Podfile and then release in mode

@TahaTesser  : Have you tried with Simualtor  with release mode ?

@mehtahardikr
The simulator doesn't support release https://github.com/flutter/flutter/issues/11754, please use a physical device and provide the details from https://github.com/flutte mode r/flutter/issues/83389#issuecomment-848636854

@TahaTesser  : will let you know.


Default/Null properties values on deserialization

Hi!
First of all, thank you for this library! It helped me a lot to clean my POCO classes and solved my problem with namespaces!
I have this xml file as an example:

<Root Id="ID1234567891234567891234567891234567">
  <FirstClass>
    <Value1>1</Value1>
    <Value2>2</Value2>
    <Value3>v02_05_00</Value3>
    <SecondClass>
      <Value4>4</Value4>
      <Value5>19468557</Value5>
    </SecondClass>
  </FirstClass>
</Root>

And these POCO classes also:
    public class Root
    {
        public string Id { get; set; }

        public FirstClass FirstClass { get; set; }
    }

    using System.Collections.Generic;

    public class FirstClass
    {
        public byte Value1 { get; set; }
        public byte Value2 { get; set; }
        public string Value3 { get; set; }

        [XmlElement("SecondClass")]
        public List<SecondClass> SecondClass { get; set; }
    }

    public class SecondClass
    {
        public byte Value4 { get; set; }
        public string Value5 { get; set; }
    }

In this example, the problem happens when I deserialize a xml file and the final object contains a collection property, as seen in the class "FirstClass". The created object have both Value4 and Value5 properties default/null, as show in the following image:

The problem does not occur when I use the dotnet native serialize library, however, i had to keep the "[XmlElement("SecondClass")]" property decoration on "FirstClass".
Here is my Main method:
        static void Main(string[] args)
        {
            var xmlFile = Assembly.GetExecutingAssembly().GetManifestResourceStream("PoCXML.Test.xml");
            var xmlRdr = XmlReader.Create(xmlFile);

            //var xmlSerializer = new XmlSerializer(typeof(Root));
            //var createdObject = xmlSerializer.Deserialize(xmlRdr);
            var xtendedXmlSerializer = new ConfigurationContainer().EnableImplicitTyping(typeof(Root)).Create();
            var createdObject = xtendedXmlSerializer.Deserialize(xmlRdr);
        }

Any suggestions?
Thanks in advance!

Hey @gabrielfetz thanks for writing in.  You are indeed running into a known issue for our v2 serializer here and one that I have officially captured in #240.
Essentially we do differ from the classic serializer currently in this regard.  If you want to succsessfully deserialize the above, you will need to provide an explicit property there as shown here:
https://github.com/wojtpl2/ExtendedXmlSerializer/blob/c75b9768cf9807363c721083bef4a81af9bd90a4/test/ExtendedXmlSerializer.Tests/ReportedIssues/Issue239Tests.cs#L14-L37
Please note that the test is configured to use nested classes so the root element is Issue239Tests-Root.
This is a bit of an ugly problem but I will think about it some more to see if there's something we can do about it.
I'd hate to resort to an ugly hack, but that might be what we need to do here. :(

Hi Mike!
I changed the structure of my xml file as you suggested and it worked like a charm!
For now, I'll try to adapt it at runtime and you can close this issue if you want.
Thanks for your help and best regards!

Cool!  Glad it can get you unblocked.  I believe there have been a few times where the incoming XML is outside of the control of the user so it left them having to use the classic serializer.
It's a tough problem and I am still not sure of a good way of tackling it as we still need to be able to serialize an entire subgraph while making it work for the currently deserialized context.
In any case, we have #240 open to keep track going further.  Hopefully, others that run into this issue will be able to see that as well and know of the limitation, too.
Thanks again for checking in and let us know if any further questions/issues you encounter. 👍


Github link at bottom of page is outdated

Describe the bug
At the bottom of each page is a section with links to, among others, an RSS Feed and Github. The Github link is https://github.com/OldTimes-Software, which no longer exists.
To Reproduce
Steps to reproduce the behavior:

Go to https://archive.thedatadungeon.com/index.html
Scroll down to the bottom of the page
Click on "GitHub"
Github says "Page not found"

Expected behavior
The Github link should go to https://github.com/TalonBraveInfo/thedatadungeon.com
Desktop (please complete the following information):

OS: Mac OS X
Browser Firefox, Safari
Version 113.0.1 (Firefox), 12.1.2 (Safari)

Fixed!


Add listSubFolderAssets and getResponseUsingQuery,

Fix tests

📦 Published PR as canary version: Canary Versions

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>

The module could be implemented with only that query, however, the lists and get methods serve as a helper so people won't need to implement everything by hand. Since we are dealing with GraphQL, the new method lets the user send wherever query they want, and the module handles errors and returns the full response. Without that, the user gets limited on the built-in methods.
It doesn't break the isolation, since we are calling a method that gives more flexibility to the user. It would, though, if the user calls _post or buildRequestOptions, IMO.
The method is not temporary, it is just a tool to give more flexibility to the user.

:rocket: PR was released in<EMAIL_ADDRESS>:rocket:


command handling

I am using the github.com/go-sql-driver/mysql MySQL driver for Go. When I try to execute a query containing  a variable i get the error that it is not implemented yet.
Error 1047: command handling not implemented yet: 22

q, err := db.Query(`
	SELECT
		COUNT(*)
	FROM
		commit_files
	NATURAL JOIN
		ref_commits
	WHERE
		ref_commits.ref_name = 'HEAD'
		AND ref_commits.history_index = 0
		AND commit_files.repository_id = ?
		AND commit_files.file_path NOT REGEXP '^vendor.*'
	`, repoID)

Yep, that's not implemented yet AFAIK

Then see this as a feature request 😉I could not find it listed here.

After a little bit of investigation, turns out this COM_STMT_PREPARE and COM_STMT_EXECUTE are not implemented in vitess.
I'm not sure if we want to do this and contribute it to vitess, give it's not a requirement for now in the OKRs. How should we proceed? @ajnavarro
More info:

https://dev.mysql.com/doc/internals/en/com-stmt-execute.html
https://dev.mysql.com/doc/internals/en/com-stmt-prepare.html
https://github.com/vitessio/vitess/blob/68f33e4ca6c78e7b58f063b1543b1f67cec2d995/go/mysql/server.go#L509

@erizocosmico we should focus on OKRs.


Create the voters table

User Story

As a user, I can request a list of voters alphabetized by last name.

As a user, I can request a single voter's information.

As a user, I can create a voter.

As a user, I can update a voter's email.

As a user, I can delete a voter.

The user can request the list of voters alphabetized by last name. Also, the user can request a single voter's information, create a voter, update a voter's email and delete a voter.


openstack cloudprovider implementation

Looks like right now the cloudprovider impl is AWS only.... Any plans for GCE, Openstack, ... ?

Thanks for your interest in Escalator. We currently don't have plans to implement any other cloud providers ourself right now, but are very welcome to PRs for this. We'd be open to any cloud provider support, whether GCE, Azure, Openstack, etc..


App stuck at 'wait until bundle finished: /assets/app.js'

So, for some reason the app won't get past wait until bundle finished: /assets/app.js when I run 'npm start' or 'npm run serve'.
Also, 'npm run dist' gets stuck at > copyfiles -f ./src/index.html ./src/favicon.ico ./dist
Anyone running into this issue as well?
I am on node v5.0.0
Latest version of the generator.
I have been using this for a week now without a problem, so im not sure what is causing it now.

UPDATE: I am now able to reproduce this.
Only way to get out of this problem that throws no error is by going to Main.js , removing all the components import, restarting the server and when app is ready putting them back in.
Anyone who runs into this, please see if you can reproduce as well. I will leave this open but feel free to close if no one runs into this issue.

UPDATE2: even though I got around the issue above, npm run dist still does not get past > copyfiles -f ./src/index.html ./src/favicon.ico ./dist

Removing the components again, I get this when running
npm run dist

Hello @HarrisRobin,
Interesting, I do not had such problems once. Could you please provide a link to the code where the error  happens? Also, which operating system are you working on?

@weblogixx I am on OSX. and I cannot host it because I can't even build the project. However, here is a repo: https://github.com/HarrisRobin/react-flux-movie-UI

After just skimming through the code a bit, the only thing that I see that could cause problems is the way you incloude node-bourbon in the config.
I will have a closer look over the weekend.

@weblogixx interesting. what red flags do you see? @import bourbon; is working just fine fyi.

Hi @HarrisRobin,
had another look at it. There are known problems with bourbon in webpack configs. Someone worked around these and build https://github.com/lowik/bourbon-sass-loader. Maybe you should try this out. When I check out your repo and just remove the Aside.scss require statement it builds. Seems like it really has to do with the way that webpack tries to build the dependencies.
As I am no sass expert by myself, someone else may help here?

@weblogixx thanks for the feedback. I will try the bourbon-sass-loader and report back if it works :)

@weblogixx just wanted to come back and say that i don't think the problem is with bourbon. removing bourbon completely did not solve my issue and I still have to do the same thing in order to get the project to compile and work (remove the highlighted block of stuff in the screenshot, re-run npm start and then add them again)

I will keep digging and figure out what's going on. I'll also try doing it from a project from scratch and see.

Yeah so unless I reduce the amount of components or remove them before i run npm start then the app never finishes to bundle and it gets stuck on :
webpack: wait until bundle finished: /assets/app.js infinitely. I ruled out bourbon as the issue and don't really know what's going on.

@HarrisRobin: I think I identified the problem know. https://github.com/jtangelder/sass-loader/issues/168 brought me closer to it. Seems like the sass version shipped with the generator is way too old. In the meantime it made a jump from 1.0 to 3.1. The following works for my setup, hope for yours too:

First, npm uninstall sass-loader
Remove the sass-loader from npm config
Run npm install --save sass-loader. It should now be installed with the latest version (3.1.x)
Start your project.

After going this steps, it should work the way it is expected. There was a threadpool limit that gets hit in the old version of sass-loader and node-sass. This seems to cannot be fixed without updating the plugin.
In any case, I will update the dependencies for sass.
Please tell me if this helps.

@weblogixx spot on! that was it.
thanks for the fix :)
cheers

@weblogixx I am facing the exact same issue, but I am not using any of above mentioned packages. —
webpack: bundle is now VALID.
webpack: bundle is now INVALID.
webpack: wait until bundle finished: /

The index.html file is being created via a custom plugin that I have written. It's highly possible that's the culprit but I am not sure why. My logic is simple — I listen to the emit event on the compiler and create my index.html file. Once the file is generated I call the callback.

Hi @tusharmath,
have you tried with the built in index.html? If you need a custom index.html generated, you could also have a look at https://github.com/ampedandwired/html-webpack-plugin.
If not, please provide a link to your repo if this is possible.
Thanks!

@weblogixx Thanks for responding. There was a ridiculously lame bug in my code. I was using RxJS to listen to the emit event using the fromCallback operator which only gets fired once.
I should have used the fromEventPattern to convert the emit events into a stream and then consume.

using an older version of node worked for me.


Register script to add media, ship yard and mercs cohorts to firebase

Creating this PR because I saw 20230907_create_cohorts_data.js registered in the repo, so I'm guessing this should be registered also.
Created the script to add latest cohorts to the database, so they appear in the /activity?filter=cohort.withdraw and in the buidlguidl.com cohorts table. The script still needs to be executed.
Fixes #105

Thanks for this @Pabl0cks
I opted for adding them manually into the database. it was very handy to have all the data in the script, thanks!!
I also ran the cohort cron manually (a script that fetches all the cohort data to populate all the required fields: builders, balance, withdraws, etc than runs every hour) + rebuilt the BG.com site (since the homepage is cached)... and the data is showing correctly now!

Thank you @carletex! Looking great in BG.com and in the app activity 🙌


2417 flow layout issues

Fix misaligned path for detached flows that do not contain any pages.
Correct left-alignment requirement for flows inside unconnected section.
Code organisation:

Move FlowItem Component to own file
Move FlowConditionItem Component to own file

Realigned path:

Left alignment:

are we still not at the JS unit tests stage yet?


pandas.CSVDataSet cannot write utf8 chars to a file

Description
I am working with pandas.CSVDataSet files that contain text. When these DataFrames contain non-ascii character such as 'less-than-or-equal' : \u2264 kedro throws an exception upon writing the file to disk.
The problem seems to be limited to windows.
Steps to Reproduce

Define a simple csv file on windows with a non-ascii character

column1,column2,column3
a,b,c
≤,2,3

Try to load and write that file in catalog.yml

test_read_file:
  type: pandas.CSVDataSet
  filepath: data/01_raw/t.csv
  load_args:
    encoding: utf8

test_write_file:
  type: pandas.CSVDataSet
  filepath: data/01_raw/t2.csv
  save_args:
    encoding: utf8

Define a simple node

def t_node(df):
    print(df)
    df.to_csv("this_works.csv", encoding="utf8")
    return df

node(
func = t_node,
inputs = "test_read_file",
outputs = "test_write_file",
name = "t_node",
)

Expected Result
The returned data frame should be written to t2.csv.
Actual Result
The plain pandas to_csv writes the file successful to disk.
But kedro raises an exception:

Failed while saving data to data set CSVDataSet(filepath=C:/Users/[user]/Documents/kedro/health_ai/data/01_raw/t2.csv, load_args={}, protocol=file, save_args={'encoding': utf8, 'index': False}).
'charmap' codec can't encode character '\u2264' in position 0: character maps to

Your Environment
Include as many relevant details about the environment in which you experienced the bug:

Windows 10
Kedro 0.17.3
Python 3.8.10
Pandas 1.2.4

Hi @jan-kaufmann! Because of the way Kedro relies on fsspec under the hood, encoding has to be passed as fs_args. You can see an example in https://github.com/quantumblacklabs/kedro/issues/359#issuecomment-632760205.

Hi @deepyaman,
first of all thanks for pointing me in the right direction.
  fs_args:
    open_args_save:
      encoding: utf8

allowed me to run the code!
However, I noticed the following things in the kedro documentation:

CSVDataSet claims that "It uses pandas to handle the CSV file." Since utf-8 is panda's default encoding, why does kedro not use it?
It also claims that I can configure it via save_args – Pandas options for saving CSV files. Since 'encoding' is one of pandas csv options I would expect that I can specify the encoding here aswell. Why does that not work?

To me it looks like kedro is ignoring parts of pandas/python here and there. I encountered a similar problem earlier when I wanted to pass a 'None' to pandas but in the yml file I had to leave the setting empty or pass 'NULL' instead.
Is it a bug that the 'encoding' is not used from pandas or does it work as designed? In that case the documentation should make that more clear.

Hi @jan-kaufmann , as @deepyaman mentioned the discrepancy is because of the fsspec wrap kedro has on top of the pandas call, i.e. https://github.com/quantumblacklabs/kedro/blob/master/kedro/extras/datasets/pandas/csv_dataset.py#L157-L158
So it's not that kedro is purposefully ignoring anything, but it's the interaction between pandas and file handles / fsspec. More recently pandas has integrated with fsspec themselves, so some of these wrappers can go away, with a view to simplify the kedro API an remove the need for open_args_save / open_args_load. This has been improved on develop (see https://github.com/quantumblacklabs/kedro/commit/4f5f9c17bb8daf36a57048982c0b40d7a21fd3a0) and the change will be made available in the next breaking release, 0.18.0.
TL;DR: this has been fixed on develop and will be out in 0.18.0. 🙂

Closing this as resolved.


Set interpolation mode to "monotone" to avoid backwards-going line

This should fix #70.

Interesting, thank you for digging in the ChartJS docs to solve this 🙏


Gallery

Updates gallery publishing buttons and links to interact with standalone gallery

Can one of the admins verify this patch?

I'm working on this branch for my MEng thesis. We are not planning on merging it in this state. It will probably be a while before the branch is ready.

The gallery code was merged in a separate change.

The gallery code was merged in a separate change.


URL parser trips on trailing >

The > character becomes part of the link, and is also followed by a semicolon:

Duplicate of #199.

Whoops. -_-


Split language intents by file

Not for merging.
This splits language intents by file.
Since we only allow lists/expansion rules to be defined in _common.yaml, we can limit the intent parser to common + the sentences in the file that we're looking at.
This however did not result in a speedup.
Before
48 passed in 11.36s

Slowest:
3.99s setup    tests/test_language_intents.py::test_language_sentences[de]
2.22s setup    tests/test_language_intents.py::test_language_sentences[nl]
1.74s setup    tests/test_language_intents.py::test_language_sentences[hu]

After
288 passed in 38.57s

Slowest:
2.25s call     tests/test_language_intents.py::test_cover_HassOpenCover[de]
1.83s call     tests/test_language_intents.py::test_cover_HassCloseCover[de]
1.76s call     tests/test_language_intents.py::test_climate_HassClimateGetTemperature[de]

German is slowest as it's currently the most complete language. Leaving it open as draft so I can tinker with it a bit more. But I doubt this is going somewhere. It's a pity because the per-file feedback is a lot more user friendly.

Caching the parsing of _common.yaml solved everything.
288 passed in 11.60s

Slowest:
1.49s setup    tests/test_language_intents.py::test_homeassistant_HassTurnOn[de]
1.00s call     tests/test_language_intents.py::test_light_HassLightSet[hu]
0.75s call     tests/test_language_intents.py::test_cover_HassOpenCover[de]

There is now no noticeable speed loss per test.


Is possible edit cell in mobile?

I have updated the master repo. You just need to sync and get the most recent version. The touch in mobile will edit the cells now and re-order if you click in the headers.

Hi @paulhodel,
I'm trying to edit the cells on mobile (Safari and Chrome as well, using jExcel v2.0.0) but after touching a cell nothing happens. After touching the header and long-touching then that column, the first row will change but nothing more. Do you have any solution for this?

Did you try long touch in the cells
On Sunday, May 12, 2019, kristofvass97<EMAIL_ADDRESS>wrote:

Hi @paulhodel https://github.com/paulhodel,
I'm trying to edit the cells on mobile (Safari and Chrome as well, using
jExcel v2.0.0) but after touching a cell nothing happens. After touching
the header and long-touching then that column, the first row will change
but nothing more. Do you have any solution for this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/paulhodel/jexcel/issues/26#issuecomment-491621007,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABN5VAIM6SEFPYPP736A6FDPVBTUZANCNFSM4DZP7AVQ
.

@paulhodel Yes, I did but sadly nothing. It's not working either with examples on your website.

@paulhodel Now i tried with jExcel v1.5.7 and touching working nice with that.


Documentation for CRD Upgrades

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio

Bug Description
In the documentation,
https://istio.io/latest/docs/setup/upgrade/helm/#in-place-upgrade
there is the following kubectl apply -f manifests/charts/base/crds command to apply the new CRDs before going through the upgrade procedure. However when I look at the base chart there isn't a folder called crds.
In the README for the charts folder, there is the following command kubectl apply -f base/files however this also doesn't look right to me.
What should be the correct command to upgrade the CRDs? I assume it is kubectl apply -f base/files/crd-all.gen.yaml but I wanted to make sure.
Version
❯ istioctl version
client version: 1.23.1
❯ kubectl version
Client Version: v1.31.1
Kustomize Version: v5.4.2
Server Version: v1.31.0
❯ helm version --short
v3.16.1+g5a5449d

Additional Information
No response

yes, other yaml files were introduced recently.

This is documented in the 1.24 upgrade notes, which is the release where the change was introduced.
https://preliminary.istio.io/latest/news/releases/1.24.x/announcing-1.24/upgrade-notes/
Additionally, istio.io doc changes have already been merged in https://github.com/istio/istio.io/pull/15744 and should be updated when the 1.24 docs bump happens (if it has not already).


"Status: 500. Message: unknown OpenSearch error response" when trying to do any sort of aggregation in grafana

What happened:
We have a grafana instance connected to an AWS OpenSearch cluster.  We can view metrics with this however whenever we try to create any sort of simple aggregation with the data we get a generic opensearch error.  There are no errors being logged on our opensearch cluster and there are no 500s being reported.  The error that grafana is logging every time this happens is:
logger=context userId=1 orgId=1 uname=admin t=2024-05-29T13:44:46.453355732Z level=info msg="Request Completed" method=POST path=/api/ds/query status=400 remote_addr=<IP_ADDRESS> time_ms=9636 duration=9.636188649s size=192 referer="https://grafana.bcdemas.local/explore?orgId=1&panes=%7B%22Qv8%22%3A%7B%22datasource%22%3A%22e3d933fa-bf77-4cc0-baef-ba3ee6d4f9d1%22%2C%22queries%22%3A%5B%7B%22refId%22%3A%22A%22%2C%22datasource%22%3A%7B%22type%22%3A%22grafana-opensearch-datasource%22%2C%22uid%22%3A%22e3d933fa-bf77-4cc0-baef-ba3ee6d4f9d1%22%7D%2C%22query%22%3A%22%22%2C%22queryType%22%3A%22lucene%22%2C%22alias%22%3A%22%22%2C%22metrics%22%3A%5B%7B%22id%22%3A%221%22%2C%22type%22%3A%22avg%22%2C%22field%22%3A%22system.cpu.iowait.pct%22%7D%5D%2C%22bucketAggs%22%3A%5B%7B%22type%22%3A%22date_histogram%22%2C%22id%22%3A%222%22%2C%22settings%22%3A%7B%22interval%22%3A%22auto%22%7D%2C%22field%22%3A%22%40timestamp%22%7D%5D%2C%22format%22%3A%22table%22%2C%22timeField%22%3A%22%40timestamp%22%7D%5D%2C%22range%22%3A%7B%22from%22%3A%22now-6h%22%2C%22to%22%3A%22now%22%7D%7D%7D&schemaVersion=1" handler=/api/ds/query

Initially we were getting the error that too many buckets were being created but I've had AWS increase our bucket limit and now this is what we are seeing.

I am on the latest grafana opensearch plugin, 2.15.3
What you expected to happen:
to be able to create simple aggregations on the data in opensearch
How to reproduce it (as minimally and precisely as possible):
do a Group By on any metric
Anything else we need to know?:
Environment:

Grafana version:  10.2.3
OpenSearch version: OpenSearch 2.9
Plugin version: 2.15.3

Hi @danfinn,
I've opened a PR to improve the error message. Once it's merged and release, it'll hopefully provide a more helpful message to help pinpoint the issue.

I'm assuming you think I'm still hitting the too many buckets issue then?  Previously I was actually getting this error and I increased the bucket limit and now I'm getting this generic error.

Hi @danfinn, I actually don't have a guess of what the issue is. There's an error from the OpenSearch response that will likely be in caused_by.reason, but the current handling doesn't handle that so it's just returning the generic error message. I'm hoping that the actual error will be in caused_by.reason and it will be more helpful than the generic error message.

ok, defiinitely sounds like an improvement.  hopefully it will give me some insight

@kevinwcyu do you know when this might get released?

@danfinn, I just released it in v2.15.4

That did help, thanks @kevinwcyu.  We are still hitting the same max buckets error.  Interesting that it was previously giving this error but then stopped once we initially raised the limit.

Thanks for the update @danfinn, I'll close this issue off since the cause has been found.

Effort tracked in https://github.com/grafana/opensearch-datasource/issues/394


[EDIT] The Beanstalk exploit post-mortem analysis link is dead

Entry

April 17, 2022 - Beanstalk Farms stablecoin project loses $182 million to exploit
Changes

The post-mortem analysis post that was linked has been deleted. There's an archive here, although it reload loops.
Agreement
By submitting this issue, I irrevocably agree to release my contribution under the CC-BY 3.0 License. I agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Please attribute this contribution to:

Cody Mims

https://codymi.ms

Thanks! I've replaced it with a working archive.


"The controller encountered an unrecoverable error" when stopping a controller or cancelling a job

ACMA: The controller encountered a unrecoverable error
System.Threading.SemaphoreFullException: Adding the specified count to the semaphore would cause it to exceed its maximum count.
   at System.Threading.SemaphoreSlim.Release(Int32 releaseCount)
   at Lithnet.Miiserver.AutoSync.MAController.ReleaseLock(SemaphoreSlim mre, String name, String caller)
   at Lithnet.Miiserver.AutoSync.MAController.TakeLocksAndExecute(ExecutionParameters action)
   at Lithnet.Miiserver.AutoSync.MAController.Init()
   at Lithnet.Miiserver.AutoSync.MAController.<Start>b__110_0()

Fixed in https://github.com/lithnet/miis-autosync/releases/tag/v1.2.6692


fix: sdk version bug fix

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


pixman: Raise individual test timeout to 240 seconds

Description of changes
On some slower hardware of mine (which happens to be powerpc64-linux), the runtime of tolerance-test barely exceeds the hardcoded timeout of 120 seconds.
33/33 tolerance-test                OK             120.28s

So raise the timeout.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[x] powerpc64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This also fixed the test timeout for me on a Xeon 5222 (so not exactly ancient 2005 hardware…).
33/33 tolerance-test                OK             129.95s

Might be because I'm building from pkgsStatic.


Literal annotation does not render type to json-schema

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
When defining a property as Literal, eg:
from pydantic import BaseModel
from typing import Literal

class Foo(BaseModel):
    bar: Literal["Bar"] = 'Bar'
    baz: Literal[None] = None

The output json-schema model loses the typing of the variable used for the literal. I.e.:
{
  "properties": {
    "bar": {
      "const": "Bar",
      "default": "Bar",
      "title": "Bar"
    },
    "baz": {
      "const": null,
      "default": null,
      "title": "Baz"
    }
  },
  "title": "Foo",
  "type": "object"
}

It would be nice to infer this type and correctly add it to the schema. This could be achieved by simply extending the literal_schema method
https://github.com/pydantic/pydantic/blob/9811727b1353e605d7183bae3d4e0d1d4ba30b95/pydantic/json_schema.py#L722
with:

def literal_schema(self, schema: core_schema.LiteralSchema) -> JsonSchemaValue:
        """Generates a JSON schema that matches a literal value.

        Args:
            schema: The core schema.

        Returns:
            The generated JSON schema.
        """
        expected = [v.value if isinstance(v, Enum) else v for v in schema["expected"]]
        # jsonify the expected values
        expected = [to_jsonable_python(v) for v in expected]

        types = {type(e) for e in expected}

        if len(expected) == 1:
            if isinstance(expected[0], str):
                return {"const": expected[0], "type": "string"}
            elif isinstance(expected[0], int):
                return {"const": expected[0], "type": "integer"}
            elif isinstance(expected[0], float):
                return {"const": expected[0], "type": "number"}
            elif isinstance(expected[0], bool):
                return {"const": expected[0], "type": "boolean"}
            elif isinstance(expected[0], list):
                return {"const": expected[0], "type": "array"}
            elif expected[0] is None:
                return {"const": expected[0], "type": "null"}
            else:
                return {"const": expected[0]}

        if types == {str}:
            return {"enum": expected, "type": "string"}
        elif types == {int}:
            return {"enum": expected, "type": "integer"}
        elif types == {float}:
            return {"enum": expected, "type": "number"}
        elif types == {bool}:
            return {"enum": expected, "type": "boolean"}
        elif types == {list}:
            return {"enum": expected, "type": "array"}
        # there is not None case because if it's mixed it hits the final `else`
        # if it's a single Literal[None] then it becomes a `const` schema above
        else:
            return {"enum": expected}

Example Code
No response
Python, Pydantic & OS Version
pydantic version: 2.5.3
        pydantic-core version: 2.14.6
          pydantic-core build: profile=release pgo=true
                 install path: <...>\.venv\Lib\site-packages\pydantic
               python version: 3.11.7 (tags/v3.11.7:fa7a6f2, Dec  4 2023, 19:24:49) [MSC v.1937 64 bit (AMD64)]
                     platform: Windows-10-10.0.19045-SP0
             related packages: typing_extensions-4.9.0

Related to this, it would be nice if StringConstraints had a values parameter (or similar) that would let you specify the literal allowed values. This would fulfill the same use-case as using the Literal type hint, but would allow for a dynamic list of strings to be used instead. Currently this behaviour can be approximated by using StringConstraints with pattern='^(literal_value_1|literal_value_2|etc)$', but the JSON schema this produces isn't as clear as it could be.
As a workaround, I'm using a dynamically generated string enum.

@WillDaSilva does the following not work for you?
from typing import Literal

from pydantic import BaseModel

class A(BaseModel):
    x: Literal['a', 'b', 'c']

print(A.model_json_schema())
#> {'properties': {'x': {'enum': ['a', 'b', 'c'], 'title': 'X', 'type': 'string'}}, 'required': ['x'], 'title': 'A', 'type': 'object'}

More generally, I think we should do a better job of handling single-item literals as I have discovered some JSON-schema-consuming tools that misbehave if you use just a plain const instead of enum with a single item. Hopefully we'll have some improvements here shortly.

@dmontagu That works for when the list of possible values is static (i.e. hard-coded), but when you have the list of strings as a variable it does not work.

Ah, now I understand. Not sure how the other maintainers feel but I wouldn't be opposed to adding that option to StringConstraints.
@WillDaSilva I'll just note though in case it is useful that I think it is still technically possible to using Literal in a dynamic way to achieve this:
from typing import Literal, TYPE_CHECKING

from pydantic import BaseModel

choices = ['a', 'b', 'c']
if TYPE_CHECKING:
    MyStringChoices = str
else:
    MyStringChoices = Literal[*choices]

class MyModel(BaseModel):
    x: MyStringChoices

print(MyModel.model_json_schema())
#> {'properties': {'x': {'enum': ['a', 'b', 'c'], 'title': 'X', 'type': 'string'}}, 'required': ['x'], 'title': 'MyModel', 'type': 'object'}

but I would agree that having StringConstraints support literal choices would be better than this.

@bruno-f-cruz does the change proposed in #8944 address your issue, or do you otherwise have any problems with it? It goes a bit farther than just adding the type in order to also address other issues at the same time, but if you (or anyone) have a problem with that change then it might be more reasonable to scale it back.

I don't have an informed opinion on the full scope of your PR. That being said, it would solve this issue. Thanks!

@dmontagu Sorry if i am too late to the party but I failed to noticed something in the previous test. While the string type is indeed added to the schema, the Literal[None] does not give rise to a typing in the schema. Can you think of a reason why it would be a bad idea to add this typing to the PR too? Thanks!

@sydney-runkle Would it be possible to open this issue given my last comment or should I open a new one?

@bruno-f-cruz,
Ah, thanks for the ping. Let's see what @dmontagu thinks!

@bruno-f-cruz,
Looks great, please add a test!