Unified Grid System

Unified Grid System Overview
The team intends on creating and implementing a Unified Grid System (UGS) for use across the whole studio. This feature is important to the studio as a whole as it adds a method of obtaining the state of tiles which will be used by the whole studio. This Unified Grid System will be an improvement over the current system, which is currently different teams are using their own systems which don't integrate together seamlessly.
Why a Unified Grid System is needed?
Upon evaluating the code and progress made by all the teams in sprint 1 and 2 there is a noticeable underlying integration issue with respect to the coordinate system used by most teams. Buildings, enemies, obstacles, and main character were all implemented into their own relative coordinates as an extension of the global world coordinates. Any interaction between entities is convoluted and cumbersome, providing a mine field of bugs and integration issues. Additionally, the map was generated as a function of the world coordinates which create several issues with the intuition of the placement of entities relative to map tiles. As the studio progresses through to later sprints it is clear that more and more integration issues will arise as more team features are interacting with other team features. From research and testing, it is recognized that an updateable deterministic world state is needed in the form of a unified grid system to drastically improve playability  of the game.
How will the UGS be implemented?
Map tiles will become the standard grid coordinate system used for the game. Every map tile will have a x, y position that will know its area in world space (the rendered space of the game). These tile coordinates will then become keys in a searchable dictionary that will allow for easy access to valuable information about the referenced tile. Some examples of this valuable information include:

tile type
what entity is placed on that tile (null if none)
valuable information about that entity

health
damage
entity type
any other valued information (pending studio polling and further investigation)
On starting the game, the grid system will be created and will be updated upon every state changing game action.

Implementation and Deliverables
As a team we will implement the necessary classes and functions needed in the backend to handle the creation, updates, and integration of the new grid system into the existing game.
As a team we will deliver the necessary support functions (internal api) along with the necessary detailed wiki documentation for all other teams to understand the new system and incorporate it into their feature themselves.
Benefits
With a Unified Grid System, several current game bugs will have a simple solution. The table below outlines some of the major issues and the proposed solution using UGS.

Major Issue
Proposed UGS solution

Entities being placed on top of each other
UGS will store the state of every game tile including if it is occupied or not. Before entities are added to the map their position will be checked against the UGS.

Main character moving freely relative to the map in their own coordinate plane
UGS will be consulted before the player moves. If the user’s input for the player is invalid the player will simply not try to move and the user will be alerted that their input is an illegal move.

Enemy path finding
UGS will be a deterministic representation of the state of the game. This deterministic property allows for the simple implementation of popular search/path finding algorithms such as BFS, DFS, UCS, Dijkstra’s, A*.

Entities can walk and be placed anywhere regardless of island size
UGS will allow for hard limits / predefined rules to be set for the generation and movement of objects. For example, the main character cannot walk on water tiles, or no character can walk on building tiles, or the shipwreck can only spawn on the shore.

Building range attack component
UGS will allow for buildings to know the state of the game including the position of all characters and objects. This allows them to easily only attack enemies in specific ranges along with support for projectiles.

Entity scale relative to other entities (i.e the player is bigger than a building, the shipwreck is the same size as a tree, etc)
With UGS several grid points can be easily grouped together and point to the same entity. This allows entities to take up more than one map tile with the scaleEntity function. (i.e. the shipwreck can be assigned to take up 5x4 map tiles allowing the game to scale it accordingly)

Dependencies

[ ] Map integration
[ ] Entity system integration

Milestones
List of sub-features we intend to have done by the end of the sprint:

[x] #211 Sept 18
[x] #247 Sept. 19
[x] #246 Sept. 20
[x] #212 Sept. 21
[x] #248 Sept. 22
[x] #253  Sept. 22
[x] #254 Sept. 23
[x] #268 Sept. 24
[ ] #269 Sept. 25

Completion Deadline: Oct. 4
Extras (optional)

[ ] Add validation of main character movement
[ ] Add integration of Building's ranged attack component

Documentation

Main description of feature
User documentation

Members

Harland Jensen (@harland-jensen) (Harry Jensen)
Jonathan Allen (@jonooallen) (Jonathan Allen)

Hi Team 7, as we spoke on Wednesday, could you finalise the size of tile suits for buildings?

@alexyun0429 64x64f please and thank you.

@alexyun0429 this has changed to 16fx16f btw.


Support for Deploy Recent Validation

Would love to know if there are plans to support deployRecentValidation as mentioned here: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deployRecentValidation.htm
Doing two deployments, one for validation and one to do the actual deployment of files, works but is not ideal. Unless I completely missed where it has already been added.

This should be fixed in v3, see: https://github.com/jsforce/jsforce/discussions/1529


Update the draft e2e spec

This largely just moves notes from drafts/markjh_end_to_end.rst into the e2e
draft spec. It also seeks to clarify a few points.

Crucially this PR doesn't merge into master, but instead merges into a drafts branch.
With that in mind, LGTM.


Update BinaryTarget

Updating to latest MaasCore.

Was the checksum for dev06 incorrect?

Was the checksum for dev06 incorrect?

Was the checksum for dev06 incorrect?

Yes it was, i don't know why but it was wrong. cc @mikasdo do you remember how you created checksum ? 🤔

Was the checksum for dev06 incorrect?

Yes it was, i don't know why but it was wrong. cc @mikasdo do you remember how you created checksum ? 🤔

🤔  i used swift package compute-checksum path/to/MyFramework.zip

🤔  i used swift package compute-checksum path/to/MyFramework.zip

I'm wondering whether it would be enough to update the checksum for dev06, what changes are in dev07?

I'm wondering whether it would be enough to update the checksum for dev06, what changes are in dev07?


npm run dev

Describe the bug
I’ve been trying to set up a private account system to import data via Printify, but the process keeps failing. Every attempt to resolve it leads to the same errors, particularly with npm run dev. It feels like the system is repeating the same steps without diagnosing the root cause.
Comment
Can we identify whether the issues are related to my environment (e.g., Firebase configuration, browser, etc.)? Also, credits are being consumed with no progress. I’d appreciate a clear plan to resolve this issue definitively.
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-mqnxwy
Steps to reproduce
Attempt to set up a private account system using Firebase for authentication and Printify for importing product data.
Run npm install to install dependencies.
Run npm run dev to start the development server.
Observe repeated errors with missing scripts, failed installations, or issues running the dev server.

Expected behavior
Expected behavior: The environment should set up successfully, and I should be able to log in and import data from Printify.
Screen Recording / Screenshot

Platform
Browser name = Firefox
Full version = 133.0
Major version = 133
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:133.0) Gecko/20100101 Firefox/133.0
performance.memory = undefined
Username = BenDeLaPorte
Chat ID = 0601ddcfd2db

Additional context
No response

I spend at least half my tokens with these various npm erros. annoying.

Oh my god thanks for your message; It was driving me crazy and I thought I was alone in this case


Bug: not waiting for Image placeholder => real image transition

Bug description
Not sure what's the problem exactly or how it can be fixed.
I have a React image component that renders first a blurry placeholder, and it gets replaced by the real image after React hydrates.
For some reason, Argos doesn't seem to wait for the placeholder to be replaced by the real image tag, and this can lead to screenshots being taken too early
Correct behavior expected
screenshot the real image once loaded
Wrong behavior observed
screenshot the blurry placeholder
Screenshot
https://app.argos-ci.com/slorber/docusaurus-visual-tests/builds/10/40206532

Reproduce
Try to screenshot this page: https://docusaurus.io/docs/playground
Sometimes it leads to a blurry placeholder
Setup
Describe the setup you have when you encounter the bug : device, browser, library version...
Additional information
The code used to switch from the blurry placeholder to the real image is here:
https://github.com/endiliey/react-ideal-image/blob/master/src/components/IdealImage/index.js
It's quite old, and it is probably the fault of this code, not Argos, but still wanted to open the discussion because you may have encountered this issue before.
Was wondering for example if Argos would:

wait for React hydration?
try to fit all the content in current viewport, making sure that libs detecting viewport entrance (like react-waypoint here) have time to trigger their onEnter events)

The rendered markup switches from:

   <div style="background-size:cover;background-repeat:no-repeat;position:relative;background-image:url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAoAAAAGCAYAAAD68A/GAAAACXBIWXMAABYlAAAWJQFJUiTwAAAA2UlEQVR4nB2OzU7CQAAG9wEMQgCp7Xa73daWJaBoTHxLPBBPpPEh/ImJZ8NZPVouuARjFE89GBLHlEkm8x0/Ya3l7PyC4WiMNunOKE7wwwipNEobVGQQMspQxuIFMb5K6XqKrH/M/eMDT/M5zy+v3NzeIXqBwY+H9MKcejc7AUf2hOXyHedW8Acf6zXiUCaEyQip+0id0/Y0mT2lXCxwzvG73fJWlogwztDJgPqCJ1NaHUk+GLPZ/FBVFTWf31+I/dYBtY1md9e9RhtfaqbTK2azgqK4ZjK55B8ECXu6qQVRyQAAAABJRU5ErkJggg==")">
      <svg style="width:100%;height:auto;max-width:100%;margin-bottom:-4px" width="640" height="356"></svg>
      <img style="width:100%;height:auto;max-width:100%;margin-bottom:-4px;position:absolute;top:0;left:0" src="https://d33wubrfki0l68.cloudfront.net/664f5db095eb34e875e932eb1cce0b286906cfb2/9f1c2/assets/ideal-img/stackblitz.da95b77.640.png" srcset="https://d33wubrfki0l68.cloudfront.net/664f5db095eb34e875e932eb1cce0b286906cfb2/9f1c2/assets/ideal-img/stackblitz.da95b77.640.png 640w,https://d33wubrfki0l68.cloudfront.net/4594d2cadb54291a90ce849a10cd579a94b37029/eab63/assets/ideal-img/stackblitz.ab6e191.1030.png 1030w" alt="⚡ StackBlitz 🆕's image" width="640" height="356">

To:

Hi @slorber, in term of accessibility, these blurry image placeholder should use aria-busy attribute isn't it?
If you do so, it will be automatically awaited by Argos.

@slorber ? any update?

Didn't have time to investigate sorry 😅 probably my fault so going to close and see if I can create a smaller repro


Location permission

I am just curious, why the library requires to have location permissions enabled in order to work?
Thanks!

Hey!
Starting from Android 6.0 it is required to hold ACCESS_COARSE_LOCATION or ACCESS_FINE_LOCATION in order to get scan results of device mac address. This is to strengthen user privacy. Even more, it is required that the user will have location services enabled.
You can read more [here](http://developer.android.com/reference/android/bluetooth/le/BluetoothLeScanner.html#startScan(java.util.List<android.bluetooth.le.ScanFilter>, android.bluetooth.le.ScanSettings, android.bluetooth.le.ScanCallback)).

Hi,
I see, was not aware of that. Thanks!
--
Klemen
Sent with Airmail
On 7 April 2016 at 15:41:53, Paweł Urban<EMAIL_ADDRESS>wrote:
Hey!
Starting from Android 6.0 it is required to hold ACCESS_COARSE_LOCATION or ACCESS_FINE_LOCATION in order to get scan results of device mac address. This is to strengthen user privacy. Even more, it is required that the user will have location services enabled.
You can read more here.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

We handle it internally (both permission and enabled state) and BleScanException is emitted with code LOCATION_PERMISSION_MISSING or LOCATION_SERVICES_DISABLED.

And why don't you handle the "permission request" in your library? Do I have to handle by myself?

Yes, you should handle them by yourself. It would be hard to do it in the library because each application has it's own design. Making an universal one might not be the best idea.
There are libraries for Runtime Permissions that might be a good choice for you.

I always get the hint: Location services needs to be enabled on Android 6.0
How can I enable the location services?
Thanks

Oh, never mind, I just enable it (By enable GPS...)
Thanks for the source anyway.


How to register a non-public class

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
fury: 0.7.0
Component(s)
Java
Minimal reproduce step

full name: com.google.protobuf.LongArrayList
The proto buffer object shown in the above figure
What did you expect to see?
register non-public class
What did you see instead?
register non-public class
Anything Else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

You could use reflection like fury.register(Class.forName)

ok


Apply TestCategory from derived class on inherited test methods

Enables sharing test methods across a class hierarchy while categorizing the inherited tests based on the derived class that's actually running them. It does this by passing the class type from the TypeEnumerator through to the ReflectHelper rather than relying on MemberInfo.DeclaringType.
Fixes #498. Previous behavior was that inherited methods would only receive test categories starting at the class defining the method. This changes it so inherited methods receive test categories starting at the test class being discovered.
I didn't add any new tests because the updated unit tests for ReflectHelper verify the correct class type argument is passed to ReflectionUtility, and the existing tests for ReflectionUtility verify correct test categories are returned based on the class hierarchy passed in. I have manually verified expected behavior specified by @karanjitsingh in https://github.com/Microsoft/testfx/issues/498#issuecomment-436188960 which is my original use case.

@spanglerco, sorry for the late reply. I'll be continuously monitoring this PR from now on until its conclusion.

@dotnet-bot test Windows / Release Build please

Thank you for getting around to this one @jayaranigarg


Selects wrong date when typing date with leading 0 on month in timezones that are behind UTC

Describe the bug
When the computer has a timezone selected that is behind UTC, e.g. Hawaii, typing the date "2023-02-07" will select the date 6th of February 2023.
If you type "2023-2-07" it will correctly select the 7th of February 2023.
If your computer is set to use UTC or a timezone ahead of UTC, e.g. Australia, then both strings will select the correct date.
To Reproduce
Steps to reproduce the behavior:
My react code
<DatePicker
    className={styles['date-range-custom-dates-start']}
    onChange={(val: Date) => { store.setPopupStart(val); }}
    selected={store.popupStartDate}
    name="customDateStart"
    autoComplete="off"
    dateFormat="P"
    locale="currentLocale"
    isClearable
/>

Set timezone to be Hawaii
Click on the datepicker field
Type "2023-02-07"

The 6th of February is incorrectly selected
Expected behavior
The 7th of February 2023 should be selected
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser Microsoft Edge
Version 115.0.1901.203 (Official build) (64-bit)

Additional context
Add any other context about the problem here.

Any updates? I have same error

This solution might work for you: https://stackoverflow.com/a/67599505/5071753


Can't exclude tests using Robot API

I'm having a problem using the Robot API to exclude tests from a test suite built programmatically.
I expect the attached program to cause only Test B to run.  Instead, both Test A and Test B run.  Can you tell me if I'm misusing the API to have this result?  If this is a bug, I'd love to work on fixing it.
Example program:
from robot.api import TestSuite, TestSuiteBuilder
from robot.conf.settings import RobotSettings

suite = TestSuiteBuilder(extension='robot').build('example.robot')

root = TestSuite('Root')
root.suites.append(suite)
root.run(settings=RobotSettings(options={
    'exclude': ['exclude-me']
}))

Example test data:
*** Test Cases ***
Test A
    [Tags]    exclude-me
    No Operation

Test B
    No Operation

Here's the output from the example for reference:
==============================================================================
Root
==============================================================================
Root.Example
==============================================================================
Test A                                                                | PASS |
------------------------------------------------------------------------------
Test B                                                                | PASS |
------------------------------------------------------------------------------
Root.Example                                                          | PASS |
2 critical tests, 2 passed, 0 failed
2 tests total, 2 passed, 0 failed
==============================================================================
Root                                                                  | PASS |
2 critical tests, 2 passed, 0 failed
2 tests total, 2 passed, 0 failed
==============================================================================
Output:  /home/ejd8183/projects/scratch/robot/filtering_mwe/output.xml

I wrote a program that uses the Robot API to build a test suite containing multiple copies of the same suite.  The copies, represented in my example by suite, are appended to a wrapper suite (like root in the example).  After building the suite, my program tries to exclude tests by tag across all of the copies using RobotSettings.
I'm using robotframework-3.1.1 under Python 2.7.15.  I get the same result under Python 3.6.0 and Python 3.7.2.  I'm using Red Hat Enterprise Linux 7.  I tried running the example with
Robot versions back to 2.8.2 and the behavior doesn't change.

exclude not working with suite.run() is actually by design. Only settings that affect the actual execution matter there. If you want to modify the suite that's executed, you can use suite.filter(excluded_tags=['exclude-me']) before execution instead. This is documented in the API docs, but it's nevertheless somewhat annoying there's no explicit error. The question is, is it annoying enough that we should do something to it.

Would be nice to do something to this but I got a feeling there's too much work compared to benefits.


chore: Force jpeg-js to 0.4.4 to fix infinite loop vuln

This isn't working.  I may have to fork jimp instead, to apply https://github.com/oliver-moran/jimp/pull/1090.


reduce number of entries in admin to improve page load

Page load times for us are really slow. Limiting paginatino to 20 entries really helps and I don't think most people need to see the default 100 at a time anyways.

Coverage increased (+0.0%) to 99.64% when pulling 915cf7a40112089b6ff9a6679801d84216b1312b on SteveByerly:entry_admin_list into 79152035d37f5000a44534f08ea681ff57adad76 on Fantomas42:develop.

Coverage increased (+0.0%) to 99.64% when pulling 915cf7a40112089b6ff9a6679801d84216b1312b on SteveByerly:entry_admin_list into 79152035d37f5000a44534f08ea681ff57adad76 on Fantomas42:develop.

Coverage increased (+0.0%) to 99.64% when pulling 915cf7a40112089b6ff9a6679801d84216b1312b on SteveByerly:entry_admin_list into 79152035d37f5000a44534f08ea681ff57adad76 on Fantomas42:develop.

I don't think that limiting the results is a good solution.
Some optimizations were already done on the SQL, but maybe something is broken.
The real question is what is causing this low speed ?

You are right, I should have dug deeper to find the slow down.
It is a bug in django-bitly relating to building URLs based on a passed-in scheme. If there are 'http' urls and you are trying to build 'https' urls, it loops through an additional n times with each page refresh. I will be sending a PR for that repo. Please close and thanks again.

Okay, I see, this is an interesting issue.
I will take a look on your correction when ready, because it's interesting me.
Regards


Store spec.Init under "startup-script" and "userdata"

spec.Init is used by InfraKit to supply per-instance
customisation, often derived from a template. This is
not necessarily a script, so store it both under "startup-script"
and under "userdata"
Signed-off-by: Rolf Neugebauer<EMAIL_ADDRESS>

CI fails because the e2e tests can't run on PRs from forks. It's OK.


Bubble shooter game.

Description

The game is played using arrow keys.
Bubbles pops if three or more match up using floodfill.

Fixes #806
Replace #806 with the issue number which is fixed in this PR
Have you read the Contributing Guidelines on Pull Requests?

[x] Yes
[ ] No

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[x] My documentation follows Template for README.md
[x] My changes generate no new warnings
[x] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works.

Screenshot

@antrikshmisri  @kaustubhgupta  @santushtisharma10 @tamanna-verma , please review the project and guide me if any changes are required.
Thank you :)

@syamala27 you copied from here. All variable names, function name, everything is exactly same

@santushtisharma10  I didn't know about plagiarism can I redo it.

@santushtisharma10 Yup, its exactly the same.

@santushtisharma10 @antrikshmisri I didn't know about plagiarism can I redo it. Sorry for the inconvenience, I will make some changes to the code and I will add new elements to the game.

@syamala27 instead of adding the new features to the exisiting code, if you can create this game on your own only then i can let you redo it.

@syamala27 instead of adding the new features to the exisiting code, if you can create this game on your own only then i can let you redo it.

I am glad to hear that mam ,definitely I will redo it .
Thankyou for giving me another chance.

@santushtisharma10  @antrikshmisri  @kaustubhgupta, I updated the game please verify it.
The changes which I have made:-

Increased screen size
Increased  number of balls
Added  more variety of colors
Added music
Changed background-color
Changed font (score)
Increased text size
Increased more rows

Here I am sharing the screenshot

@syamala27 add the readme file

@santushtisharma10 @kaustubhgupta  I have updated the readme file.
please verify it .


Upgrade to TSLint 4

tslint.json is massively simplified since most rules are already covered by
tslint:recommended.

Current coverage is 100% (diff: 100%)

Merging #1655 into master will not change coverage

@@           master   #1655   diff @@
=====================================
  Files           1       1
  Lines        3948    3951     +3
  Methods         0       0
  Messages        0       0
  Branches      680     680
=====================================
+ Hits         3948    3951     +3
  Misses          0       0
  Partials        0       0

Powered by Codecov. Last update 7219731...d1aaa21

:+1:


Make catalog-rebuilder depend on the dmci python package, and use dmci directly in catalog-rebuilder.py, and remove dmci sidecar.

After some thought, I think a better implementation of the catalog-rebuilder will be to use dmci-package inside the catalog_rebuilder script, so to avoid the dmci-sidecar. This will also make it easier to implement multithreading.

After some thought the solution we have will work better, and using dmci sidecar gives us some benifits with multiple workers etc.
And we will see if it is solr,pycsw or dmci that reject a the incoming file.
This takes a bit of time using the catalog rebuilder. So in the future, when we are not dependent on pycsw, we could implement a multithreaded bulkindexer insted. Then we create a new issue.
Closing this issue.

A new version is now available. Need to add overrides for staging

New version implement this. This can now be closed


ippool creation issue

when two ippool with conflicted IP are creating or updating at the same time,  the two webhook gorouting may fail to check the conflicted IP before both ippool are accepted by the api-server
it needs a lock design to

Waiting for support

any comment

no ideas

same as #868


Scoping

We have quite a few PRs and the discussion is spread accross those PRs instead of being in one issue. I know, adding yet another discussion thread seems kind of pointless then, but I think it's important to gather some clear statements about expectations regarding scoping.
PRs

#139
#142
#144
#145
#149

My own statement
I think a clear scope avoids bugs with different drivers. We allow passing a driver to be run to Loop::execute and should therefore only rely on the driver being accessible with the Loop accessor inside that Loop::execute scope.
It has been mentioned that this would prevent the adapter for React having a correct run method and additionally would prevent first setting things up and then running the loop.
The React adapter currently uses Loop::execute(function () {}, Loop::get()); to run the default / current loop. This continues to work with a strict Loop::execute scope (#139) as long as the whole application is wrapped in Loop::execute. It uses a stacked driver then, but as both are the same, everything will work fine.
Another solution for the adapter is to use an explicit driver first and then simply pass it to Loop::execute as React uses an explicit loop that's passed around anyway.
<?php

$loop = new LoopAdapter($interopLoop);
$connector = new DnsConnector($loop);
// ...
$loop->run(); // Executes Loop::execute

Registering events on a specific loop instance without the accessor will always register those events on the right driver (obviously) and is therefore totally fine outside of Loop::execute.
But after all, this is something which doesn't affect any library code. It only affects tests and application code, which both have to be changed anyway to make use of the accessor and interop loop.
I really want to avoid having resetDriver and a default driver at all if we can have a clear scoping and thus avoid bugs with different drivers and forgot-to-reset drivers in tests. It's going to be less confusing for newcomers if the following code just errors instead of just not working, because it's using two different loops.
<?php

Loop::defer(function () { /* never executed */ });

// Uses a new driver and thus "ignores" the previous `Loop::defer()`
Loop::execute(function () { print "hello"; });

I'm very interested in opinions especially from @WyriHaximus @jsor @cboden @davidwdan @mbonneau

I see #149 is also related.
I proposed something similar to #149 way early on when we started, though not quite as spartan. I think Loop::run() looks slightly nicer than Loop::get()->run(), but the latter form certainly reduces the responsibility of the Loop static accessor.
I think there are two major benefits of the current execute() function. The first is that the lifetime of the loop driver is lexically guaranteed:
$myDriver = new MyDriver();

Loop::execute(function() {
    // Loop::get() is guaranteed to return $myDriver (sans a sub-scope).
});

// $myDriver is guaranteed to be removed from global scope here.

You can no longer guarantee a controlled lifetime for the global event loop with a pure get()/set().
The second benefit is allowing multiple pieces of code to set the global driver without affecting each other. With a plain set(), the order of execution could become important and unrelated code will affect each other.
I would propose a slightly less plain but similar compromise: a stack-based solution similar to a Lisp special variable. This has the second benefit above that execute() also has:
// Create some specific driver.
$myDriver = new MyDriver();

// Make the driver the active driver.
// Could also call this Loop::push().
Loop::init($myDriver);

// Do some async...
Loop::get()->defer(function() {
    // We can also call other functions which run their own loop.
    doSomethingAndWait();
});

function doSomethingAndWait()
{
    // We can set the active driver without destroying the previous driver.
    Loop::init(new OtherDriver());

    // Do some stuff while OtherDriver is active...

    // Clean up after ourselves.

// Could also call this Loop::pop().
Loop::drop();

This is a pattern I see in a few libraries that try to reduce the pain of global variables, where every init call should be paired with another cleanup call to manually control the scope of the global value. (Of course should isn't something we can guarantee, but that is the tradeoff we're discussing.)

Note that this issue is redundant if we go with #149. (As this then no longer is this specifications problem to solve.)
If we'd go with #149, it'd be the task of libraries to provide friendly access.
E.g. \Amp\defer($cb) could call Loop::get()->defer($cb) then. And we'd have \Amp\run() which provides proper scoping for you.
Also, your Loop::init()/Loop::drop() is really just sugar for $old = Loop::get(); Loop::set(new OtherDriver); ... Loop::set($old);.
IFF we go with a radical cleanup, I'd go with the simplest common denominator of interop, just a simple getter and setter.

fyi @sagebind back then when you proposed it, we were still retaining the loop accessor functions (e.g. Loop::defer() etc.) … Initially at least I intended the Loop class to be directly consumed by users; and not just libraries at the very lowest level.

@bwoebi It's mostly sugar, but the key is that Loop::init() would not allow breaking the driver stack. It provides at least some guarantee that code cannot set the global driver without preserving the previous driver.

Forgetting to drop() at the end breaks it again (that's actually why Loop::execute() expects a closure so that the scope is well delimited).
At the point where we have just get+set, there will be only a few well-defined functions for each low-level library using Loop::set(). Thus it won't be even worth using init()/drop().

@sagebind described very nicely the benefits of execute(); I really think it would be a shame to move away from that approach. Has there been any happening elsewhere about this issue, as it doesn't seem like this has really moved on in the past three weeks?

I believe we should go with the scoped version using execute(). This is the better way to do things. We shouldn't be burdened by prior practices, especially since it is trivial to wrap code previously written for an un-scoped loop within a callback for a scoped loop.

I'm in favor of retaining a scoped execute() as well. The benefits outweigh the disadvantages we might be concerned about.


Antigen Caching Issues with powerlevel9k for font Glyphs

Hi,
I am having issues with Antigen caching. If the caching is enabled the glyphs and icons do not show up properly:
without caching:

with caching:

It is not a font or terminal problem but clearly comes from cahing. With caching disabled the terminal startup is quite slow. I tried zplug, it worked without a glyph issue but was even slower!
A simplified .zshrc is as follows:
POWERLEVEL9K_INSTALLATION_PATH="~/.antigen/bundles/bhilburn/powerlevel9k/"
POWERLEVEL9K_MODE="awesome-patched"
POWERLEVEL9K_ALWAYS_SHOW_CONTEXT=true
POWERLEVEL9K_PROMPT_ON_NEWLINE=true
POWERLEVEL9K_COMMAND_EXECUTION_TIME_THRESHOLD=1
POWERLEVEL9K_COMMAND_EXECUTION_TIME_PRECISION=3
POWERLEVEL9K_LEFT_PROMPT_ELEMENTS=(status os_icon context dir dir_writable)
POWERLEVEL9K_RIGHT_PROMPT_ELEMENTS=(vcs root_indicator background_jobs command_execution_time history)

antigen use oh-my-zsh
# ...
antigen bundle git
antigen bundle git-extra
antigen bundle github
# ...
antigen bundle zsh-users/zsh-autosuggestions
antigen bundle zsh-users/zsh-completions
antigen bundle zsh-users/zsh-history-substring-search
antigen bundle zsh-users/zsh-syntax-highlighting

antigen theme bhilburn/powerlevel9k powerlevel9k

# Tell Antigen that you're done.
antigen apply

I tried zgen and I have the same issue.

@yahyavi - Your configuration looks sane. I'm actually not an antigen user myself, and am fairly unfamiliar with not only how it does caching but how it works, generally.
I just checked over in the @zsh-users antigen docs, though, and check it out, they have an example specifically showing how to handle P9k and caching =)
https://github.com/zsh-users/antigen/wiki/Commands#antigen-theme
Give it a shot and let me know if it helps!

Thanks. Yes, this is what I found also which led me to try ANTIGEN_CACHE=false (images in the original post) which does solve the glyph problem but it add considerably to startup time.
The weird thing is I am not dynamically loading bundles based on environment variables. The example they give is dynamically loading different themes depending on the terminal. In my case, I am not doing that, so maybe the issue is that internally powerlevel9k is loading different things depending on env variables and that somehow affects the caching in antigen. At least that would be my guess right now.
Can I ask what plugin manager do you use (if any)? I had the same problem with zgen. zplug worked correctly but was quite slow.

@yahyavi - Ah, bummer. I use Oh-My-Zsh as a plugin manager and don't have any issues (although OMZ also doesn't have caching like that).
P9k does indeed load different things depending on environment variables - specifically, font glyph configurations. It looks like that might be what's happening to you. Is there a way to force an overload of the Antigen cache?  You're using awesome-patched, so it would specifically be this case in the switch statement:
https://github.com/bhilburn/powerlevel9k/blob/master/functions/icons.zsh#L17

Thanks, will look into it and report back if I find a solution.

resolved in the antigen 2.2.2 with proper caching.

@yahyavi - Great! Glad to hear it's been resolved. Thanks for updating the thread =)


Consider adding OpenC2 to the list of formats

Consider adding the  OASIS Open Command and Control (OpenC2) Technical Committee and specification under the list of formats. I have created a pull request for this at:
https://github.com/hslatman/awesome-threat-intelligence/pull/112

Thank you! I've merged it and added a line about what OpenC2 is about.


Pagination reliance on finishing scrolling

The scroller only resets itself once it returns a false upon a scroll is determined not to continue.
This is confusing in the code to see when does the reset actually happen, and if a scroller is shared between jobs AND not "finished", it would not reset, which is hardly useful anywhere ever.
The solution probably shouldn't be changing the way the scroller resets, though resetting in getFirstRequest might be one.
A better solution would probably be having a new instance of the scroller for each job.

    public function testMultipleJobsSameScroller()
    {
        $config = $this->getScrollerConfig();
        $config['default'] = 'page';
        $scroller = new MultipleScroller($config);

        $client = RestClient::create();

        $config1 = new JobConfig('none', [
            'endpoint' => 'data1'
        ]);
        $config2 = new JobConfig('none', [
            'endpoint' => 'data2'
        ]);

        $response = (object) [
            'data' => [1,2]
        ];

        $first1 = $scroller->getFirstRequest($client, $config1);
        $second1 = $scroller->getNextRequest($client, $config1, $response, $response->data);
        // $last1 = $scroller->getNextRequest($client, $config1, [], []);

        $first2 = $scroller->getFirstRequest($client, $config2);
        $second2 = $scroller->getNextRequest($client, $config2, $response, $response->data);

        var_dump($first1, $second1, $first2, $second2);
    }

Without the $last, the followup requests will continue the increments from previous "job"

A new instance of scroller is now used for each job https://github.com/keboola/generic-extractor/commit/535b116e8e98577987d3d600ecb63eb153ef9e72


[RFC] Wrap Leaflet's GridLayer

This wraps Leaflet GridLayer so that each tile is an instanciated Vue component.
There are some things I don't know if the approach I used follows the best Vue/JS practices (since I'm quite new to Vue and non-ancient JS in general):

What this.$parent of a created tile component should point to?
Is the way the tile component is passed to the LGridLayer ok?
Destruction of the tile components hopefully works as intented but somebody with more Vue background might want to check what happen on tileunload event
Changing tileComponent prop on the fly might not work (I've not tested it since I don't need it change it but I had to add the setter to avoid triggering some error).

@ij1 Hi! This is awesome :) I will go through this today, but can you please document the new component in the new docs  ?
You will need to have docsify installed in your global node modules, but for the rest is just readme editing

@ij1  about this:
Changing tileComponent prop on the fly might not work (I've not tested it since I don't need it change it but I had to add the setter to avoid triggering some error).
You can remove the custom: true and remove the setter, if you don't want to have reactivity in your component

You can remove the custom: true and remove the setter, if you don't want to have reactivity in your component

Like I said, that leads to an error (but if I comment the propsBinder call, the error goes away so it has something to do with all that trickery in there). And unfortunately I've no idea what I should do to fix that error.

You can remove the custom: true and remove the setter, if you don't want to have reactivity in your component

Like I said, that leads to an error (but if I comment the propsBinder call, the error goes away so it has something to do with all that trickery in there). And unfortunately I've no idea what I should do to fix that error.

I will look into this because it should not be the case!
Thank you for adding the docs, about building the new config uses vue-cli 3.0
https://cli.vuejs.org/
Installing this will make you be able to build the project with vue-cli-service build --entry src/main.js --mode production --dest dist --target lib --watch
Or by using the vue ui.
The page fails to find the gridLayer because the docs import it from npm beta version, my bad! I am going to merge this and make a new release for the beta package

@ij1 I did a tiny fix to docs and uploaded it to the npm beta version of vue-leaflet, you can check it!

Yes! Docs worked now :-).

Thank you for adding the docs, about building the new config uses vue-cli 3.0
https://cli.vuejs.org/
Installing this will make you be able to build the project with vue-cli-service build --entry src/main.js --mode production --dest dist --target lib --watch

I figured that out yes and added something along those lines into my package.json scripts (the "hack" I referred to).

Or by using the vue ui.

I was surprised that it was not provided anymore in package.json scripts but this kind of explains it I guess. I'm just not an ui person really so I had no way of knowing the alternative for the long cmd :-). Although I have to admit that with Vue (in general) I feel, for the first time, generating UIs myself is so much less pain that the effort is actually worth it :-).

@ij1 Yes my bad there, I had to process a lot of tasks and did a lot of changes lately and I probably failed to document all of them.
I am glad that vue is persuading you that building UI also add value beside the 'prettiness'!
Do you think I should modify the README ? also any feedback on the new docs would be greatly appreciated

I am glad that vue is persuading you that building UI also add value beside the 'prettiness'!

Lol, I'd hardly call something I've done 'pretty' :-). What I meant and what appeals me more is 'robustness' with very little effort.

Do you think I should modify the README ? also any feedback on the new docs would be greatly appreciated

I like the new docs more because the vue bits are easier to read than in the earlier examples that were hard to even match to the corresponding .vue file (the examples link in the top row of the current docs is broken btw, gives 404 for me).


Bug with item drawing inside tmux

Open attached db, enter to the "Lifehacker" feed and move selection by pressing "down" button. You will see that the item number 61 became same as 62. I can reproduce this only inside tmux (with both versions of newsbeuter: 2.8 and HEAD), it draws correct without tmux.

.newsbeuter.zip

Moving this to 2.11 milestone to unblock 2.10 release.

I can't reproduce this in tmux and newsbeuter 2.9 or 2.10(HEAD), although I seem to recall having a this problem previously.  Is this still a problem in the latest version of newsbeuter?

Neither can I. Perhaps it was fixed with tmux update.

…but I can.
The title of this item contains a soft hyphen, which seem to break either STFL or Ncurses. We actually remove them, but only from HTML; titles aren't passed through that module. This is related to #237; I should probably re-consider my decision on that issue.


Enhance Trusted Call and Getter wrappers

We need to update our wrappers due to the following reasons:

The public rpc interface will be using substrate extrinsic as an overall wrapper for TrustedGetters and TrustedCalls.
The indirect invocation only uses TrustedCalls.
TrustedOperation wrapper is now obsolete and can be removed completely

Due to the various wrapper changes, the chance could be taken to improve the TrustedCall and TrustedGetter Wrapper in general. This could include the following:

implement a new hash() function, making the various duplicated hash_of functions obsolete.
...

Closing as completed with leftover task in #1040


Compound objects

Adds capacity for "compound_object" and "multiple" formats
Updates item page layout following CollectionBuilder-CSV
Includes accessibility improvements following CollectionBuilder-CSV

@owikle it looks like the conflict above in nav-menu is fixing dropdown overlap issues? I guess it is because .sticky-top sets z-index to 1010, which over rides what ever we set in .about-nav in _sass/_pages.scss. Probably delete the rule in _pages.scss


package versions have conflicting dependencies, probably with cadquery or cq-editor

Thank you for building Build123d.
FWIW, I had an issue on install, but worked around it.
But Not able to install build123 (prmopt> pip install build123d) due to package versions have conflicting dependencies.
I only have cadquery and cq-editor installed on that machine, so conflict is likely with one of them.
The packages listed by pip that have the error are all ipython 8....
There are about 30 to 40 of them.
So I downloaded an older version of python and ran that specific pip.  (in windows powershell: > Start-Process -FilePath ". . . \Python\Python311\Scripts\pip3.11.exe").  (cadquery is installed in my python 3.12 environment)
No errors on install,  but when I test in cq-editor
import sys
sys.path.append('C:/Users/martinez/AppData/Local/Programs/Python/Python311/Lib/site-packages')
from build123d import *
length, width, thickness = 80.0, 60.0, 10.0
ex1 = Box(length, width, thickness)
show_object(ex1)
I get this error:
INFO: build123d: None context requested by Box
Any thoughts on what I need to fix?
Thank you.
--Chris

If you're using a Mac with Apple Silicon there are special instructions here: https://build123d.readthedocs.io/en/latest/installation.html#special-notes-on-apple-silicon-installs

INFO: build123d: None context requested by Box

That is not an error, that is an info message in the log. It looks like it might be working correctly. Can you test your installation per the instructions at this link? https://build123d.readthedocs.io/en/latest/installation.html#test-your-build123d-installation

@MotoCyti were you able to solve this issue, and if so can you please close it?

I am no longer using build123d, so I don't need it fixed.  But I have no
idea if it is still a problem or not for others.
Br,
Chris
On Tue, Sep 3, 2024 at 2:51 PM jdegenstein @.***> wrote:

@MotoCyti https://github.com/MotoCyti were you able to solve this
issue, and if so can you please close it?
—
Reply to this email directly, view it on GitHub
https://github.com/gumyr/build123d/issues/655#issuecomment-2327198017,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJQEMJAMFOYHV7YZOLXJSYDZUYAJZAVCNFSM6AAAAABKGMSDNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRXGE4TQMBRG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

thank you
On Mon, Sep 9, 2024 at 11:49 AM jdegenstein @.***>
wrote:

Closed #655 https://github.com/gumyr/build123d/issues/655 as not
planned.
—
Reply to this email directly, view it on GitHub
https://github.com/gumyr/build123d/issues/655#event-14185686212, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BJQEMJFKGK6PRL566AOWTRLZVW7QBAVCNFSM6AAAAABKGMSDNCVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUGE4DKNRYGYZDCMQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Tor config : no passphrase provided

Keep getting:
Tor configuration invalid or server down :: no passphrase provided

have the same issue
after i got tis error " Tor configuration invalid or server down :: [Errno 111] Connection refused"
i started tor and so the error message changed to " Tor configuration invalid or server down :: no passphrase provided"
any advice?

I wish there was answers for this but I just cant find these, you guys still stuck?


Multiple performance measurements & Extra debug message

When multiple performance measurements are set, like the Nagios plugin check_load:

$ check_load -w 10,20,30 -c 20,30,40
OK - load average: 0.09, 0.17, 0.16|load1=0.090;10.000;20.000;0; load5=0.170;20.000;30.000;0; load15=0.160;30.000;40.000;0;

there are issues with status calculation and performance data format.

Extra debug message only be printed in verbose mode to avoid some issues (https://github.com/trifthen/NagAconda/issues/6, https://github.com/trifthen/NagAconda/issues/9)

+1

+1, solves the problems I mentioned in this issue: https://github.com/trifthen/NagAconda/issues/7 and those regarding the additional print statements.

People are still using this plugin? Dear lord.
I'll merge this because I don't have time to test it right now, and the +1's suggest it works. :)


Apollo error + UI error + Kafka Missing Topics

Describe the bug
I deleted all the datahub containers (initially, from the docker osx gui; later with the nuke command)
I reinstalled using datahub docker quickstart
The containers pull, there is an error that says mysql is unhealthy, but the first install I did I got that also, and it seemed to work fine.
Now, in the fresh install if I manually add an ingestion secret, I get
"Failed to update ingestion source!: Invariant Violation: 8 (see https://github.com/apollographql/invariant-packages)" in a model in the GUI. If I reload, the secret is present. it is saved to mysql. In the debugging pages (https://datahubproject.io/docs/troubleshooting/quickstart/) I went through these steps. In one step it asks to run kafkacat (kcat on osx via brew I think), and see that "Confirm that MetadataChangeEvent, MetadataAuditEvent, MetadataChangeProposal_v1 and MetadataChangeLog_v1 topics exist besides the default ones."
Mine does not have that, here is the output:
(venv) bash-3.2$ kcat -L -b localhost:9092
Metadata for all topics (from broker 1: localhost:9092/1):
 1 brokers:
  broker 1 at localhost:9092 (controller)
 9 topics:
  topic "MetadataChangeLog_Timeseries_v1" with 1 partitions:
    partition 0, leader 1, replicas: 1, isrs: 1
  topic "DataHubUpgradeHistory_v1" with 1 partitions:
    partition 0, leader 1, replicas: 1, isrs: 1
  topic "MetadataChangeProposal_v1" with 1 partitions:
    partition 0, leader 1, replicas: 1, isrs: 1
  topic "__consumer_offsets" with 50 partitions:
    partition 0, leader 1, replicas: 1, isrs: 1
    partition 1, leader 1, replicas: 1, isrs: 1
    partition 2, leader 1, replicas: 1, isrs: 1
    partition 3, leader 1, replicas: 1, isrs: 1
    partition 4, leader 1, replicas: 1, isrs: 1
    partition 5, leader 1, replicas: 1, isrs: 1
    partition 6, leader 1, replicas: 1, isrs: 1
    partition 7, leader 1, replicas: 1, isrs: 1
    partition 8, leader 1, replicas: 1, isrs: 1
    partition 9, leader 1, replicas: 1, isrs: 1
    partition 10, leader 1, replicas: 1, isrs: 1
    partition 11, leader 1, replicas: 1, isrs: 1
    partition 12, leader 1, replicas: 1, isrs: 1
    partition 13, leader 1, replicas: 1, isrs: 1
    partition 14, leader 1, replicas: 1, isrs: 1
    partition 15, leader 1, replicas: 1, isrs: 1
    partition 16, leader 1, replicas: 1, isrs: 1
    partition 17, leader 1, replicas: 1, isrs: 1
    partition 18, leader 1, replicas: 1, isrs: 1
    partition 19, leader 1, replicas: 1, isrs: 1
    partition 20, leader 1, replicas: 1, isrs: 1
    partition 21, leader 1, replicas: 1, isrs: 1
    partition 22, leader 1, replicas: 1, isrs: 1
    partition 23, leader 1, replicas: 1, isrs: 1
    partition 24, leader 1, replicas: 1, isrs: 1
    partition 25, leader 1, replicas: 1, isrs: 1
    partition 26, leader 1, replicas: 1, isrs: 1
    partition 27, leader 1, replicas: 1, isrs: 1
    partition 28, leader 1, replicas: 1, isrs: 1
    partition 29, leader 1, replicas: 1, isrs: 1
    partition 30, leader 1, replicas: 1, isrs: 1
    partition 31, leader 1, replicas: 1, isrs: 1
    partition 32, leader 1, replicas: 1, isrs: 1
    partition 33, leader 1, replicas: 1, isrs: 1
    partition 34, leader 1, replicas: 1, isrs: 1
    partition 35, leader 1, replicas: 1, isrs: 1
    partition 36, leader 1, replicas: 1, isrs: 1
    partition 37, leader 1, replicas: 1, isrs: 1
    partition 38, leader 1, replicas: 1, isrs: 1
    partition 39, leader 1, replicas: 1, isrs: 1
    partition 40, leader 1, replicas: 1, isrs: 1
    partition 41, leader 1, replicas: 1, isrs: 1
    partition 42, leader 1, replicas: 1, isrs: 1
    partition 43, leader 1, replicas: 1, isrs: 1
    partition 44, leader 1, replicas: 1, isrs: 1
    partition 45, leader 1, replicas: 1, isrs: 1
    partition 46, leader 1, replicas: 1, isrs: 1
    partition 47, leader 1, replicas: 1, isrs: 1
    partition 48, leader 1, replicas: 1, isrs: 1
    partition 49, leader 1, replicas: 1, isrs: 1
  topic "PlatformEvent_v1" with 1 partitions:
    partition 0, leader 1, replicas: 1, isrs: 1
  topic "MetadataChangeLog_Versioned_v1" with 1 partitions:
    partition 0, leader 1, replicas: 1, isrs: 1
  topic "DataHubUsageEvent_v1" with 1 partitions:
    partition 0, leader 1, replicas: 1, isrs: 1
  topic "MetadataChangeEvent_v4" with 1 partitions:
    partition 0, leader 1, replicas: 1, isrs: 1
  topic "_schemas" with 1 partitions:
    partition 0, leader 1, replicas: 1, isrs: 1

To Reproduce
Steps to reproduce the behavior:

Install via quickstart
Go to ingestion->secret, add one

Expected behavior
Secret is added without an error.
Screenshots

Desktop (please complete the following information):

OS: osx
Browser chrome
Version 119

Additional context
Add any other context about the problem here.

Sorry, a bit unsure about the title, because the manifesting bug seems relatively mild, but I'm concerned about the kafka topics (doc bug?)
deletes work fine with the delete button.


CLOUD-52971 added support for mesos into cloudbreak shell

@biharitomi

Jenkins build failed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/2130/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/2131/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/2132/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/2133/


Script for downloading and pre-processing wikitext datasets

Added an automated script for downloading and pre-processing wikitext-103 and wikitext-2 datasets for the LSTM language models, in the format described in https://nvidia.github.io/OpenSeq2Seq/html/language-model.html. This is very helpful for generating the files needed for training LSTM language models.

Thank you for the PR.


Add bash example and label batch example correctly

The example labelled "bash" was actually a batch file.
Added a bash example, and re-labelled the batch file.

@microsoft-github-policy-service agree

@cpickard, Thank you for taking the time to contribute to Azure CLI documentation. Your feedback has brought code tag inconsistencies to our attention. Your PR, however, has been replaced with PR 4331 to comply with Microsoft's Contributor Guide.  Please see the following two sections:

Contributor guidelines for Azure CLI code tags .  It is the code tag that controls color formatting and the behavior of the code block menu bar.

Contributor guidelines for conceptual tas. It is the conceptual tab that indicates the environment.

The tab IDs are intentional as-is because the different document sections aren't related to one another, as they would be in a how-to guide or tutorial.


Added first cut at attribute support.

Test enhanced to use attributes and global attributeGroup definition and reference as well as local attribute declarations.
Does not detect, nor handle,  the fact that an attribute is allowed to have the exact same name as an element in XML Schema.
Currently does not distinguish optional/required attributes (they're all addNullable), and does not implement XSD default/fixed.
Note that attribute definitions in XSD come last in the element definition lexically; however, they come out first in Drill field order. This is consistent with the way XML text looks where the element tag carries attributes first, in the opening tag, then child elements follow after the opening tag.

@mbeckerle Thanks for this.  One thing to note... The current implementation of the XML reader in Drill adds a map called atttributes for the attributes.  The key is the path for the attribute in question and they are separated by an underscore.
Take a look here:  https://github.com/apache/drill/tree/master/contrib/format-xml#attributes
That way you can have attributes with the same name as a key.
Regarding the required/optional, mainly out of laziness, for the XSD reader, I made all the fields nullable in Drill.  I know that XSD supports required and optional fields, so we can certainly add that capability.  The tricky part is if you define that schema, and then you encounter data that doesn't follow that schema, the queries will fail.  My preference in Drill is to make it as fault tolerant as possible, so that the user gets something other than a stack trace...

@mbeckerle Thanks for this. One thing to note... The current implementation of the XML reader in Drill adds a map called atttributes for the attributes. The key is the path for the attribute in question and they are separated by an underscore.
Take a look here: https://github.com/apache/drill/tree/master/contrib/format-xml#attributes
That way you can have attributes with the same name as a key.
Regarding the required/optional, mainly out of laziness, for the XSD reader, I made all the fields nullable in Drill. I know that XSD supports required and optional fields, so we can certainly add that capability. The tricky part is if you define that schema, and then you encounter data that doesn't follow that schema, the queries will fail. My preference in Drill is to make it as fault tolerant as possible, so that the user gets something other than a stack trace...

I will add the attributes to the attributes map.
As for the nullable aspect. I think at runtime of a query what you describe makes sense. I.e., if the document doesn't match the schema, then it should fall back on behavior that is like non-schema XML querying. However, when drill analyzes a query and there is an XSD, is it possible to issue a warning that a field is being requested that is not part of the schema? Many XML (and DFDL) data types are deeply nested. One will need help to formulate queries that are actually accessing the fields you want. If it just "always works but produces nothing", that will actually be quite hard to deal with.

@mbeckerle,
Let me clarify a bit...
Drill is officially schema free.  However over the years we've discovered that reading data with no schema is a REALLY hard problem and lends itself to all kinds of issues that then get dumped on the user.  If you read through the Drill dev list you can see that we've had a lot of discussions around this topic.   This is in stark contrast with other federated query engines which require a schema in order to read data.
With that said, Drill settled on the approach of giving developers three options:

Predefined schema:  This is useful for databases and other data sources where it is relatively easy to get schema metadata before the data is actually read.  In this case, you can define the schema and all the readers, and know that it will not change.
"Late" schema:  This is a sort of middle ground.  In this case, you use whatever metadata is available before reading starts to initialize a schema, however, as new fields are encountered, they are added to the schema.
Schema as you go:   This is where the schema is discovered as the data is being read.

We also added the ability for users to provide the schema in various ways.  Users can provide a schema at query time, or via a file.
What I was thinking was that once the XSD reader is working to our satisfaction, we'd enable the XML format plugin to download the XSD (cache it) and convert that to a schema.   I wouldn't use this to "lock" the schema, so that if Drill encounters data that is not defined in the schema, Drill could add that to the schema dynamically.
Take a look at this PR:  https://github.com/apache/drill/pull/2710
Thank you for all your work on this!!

@cgivre
So, given an XSD then, how would a Drill user's experience change? What does the XSD help them with?
I think given the nature of Drill, the right thing is for it to help them create correct queries, for when the XML documents in fact obey the schema. This means issuing warnings to them with informative instructions about what doesn't make sense, given the XSD schema.
There are some asserts in the code where I wasn't sure what to do. E.g., what if the user's element declares a child element named "attributes" which conflicts with our reserved name?  What do we do in that situation?

Another comment w.r.t. schema and what it is used for.
The non-schema-aware XML-reader treats all content as strings.
But with schema, we have real simple types like integers, double, float, date, time, etc.
What happens when incoming data doesn't convert to the expected type? Is there any sort of warning? Can the schema be "broadened" to change the type to 'string'? If the query operates on the data (doing arithmetic say), then that will likely fail at runtime in that case.
In some sense, we have the information necessary to specify in the error message that the data field was expected to be a number (from the XML schema of the data), but was not in conformance with this.

I'm on the road today but will respond to this tonight.

@mbeckerle
You've encountered another challenge that exists in Drill reading data without a schema.
Let me explain a bit about this and I'm going to use the JSON reader as an example.  First Drill requires data to be homogeneous.   Drill does have a Union vector type which allows heterogeneous data however this is a bit experimental and I wouldn't recommend using it.  Also, it really just shifts schema inconsistencies to the user.
For instance, let's say you have a column consisting of strings and floats.  What happens if you try to do something like this:
SELECT sum(mixed_col)
-- or
SELECT.... ORDER BY mixed_col

Remembering that Drill is distributed and if you have a column with the same name and you try to do these operations, they will fail.
Let's say we have data like this:
[
  {
     'col1': 'Hi there',
     'col2': 5.0
  },
  {
     'col1':True,
     'col2': 4,
     'col3': 'foo'
  }
]

In older versions of Drill, this kind of data, this would throw all kinds of SchemaChangeExceptions.   However, in recent versions of Drill, @jnturton submitted https://github.com/apache/drill/pull/2638 which overhauled implicit casting.  What this meant for users is that col2 in the above would be automatically cast to a FLOAT and col1 would be automatically cast to a VARCHAR.
However, when reading data the story is a little different.  What we did for the JSON reader was have several read modes.  The least tolerant attempts to infer all data types.  This seems like a great idea in practice, however when you start actually using Drill with real data, you start seeing the issues with this approach.  The JSON reader has a few configuration options that increase its tolerance for bad data.  The next level is readAllNumbersAsDouble which... as the name implies, reads all numeric data as Doubles and does not attempt to infer ints vs floats.  The next options is allTextMode which reads all fields as VARCHAR.  This should be used when the data is so inconsistent that it cannot be read with either mode.  These modes can be set globally, at the plugin level or at query time.
For the XML reader,  I didn't add type inference because I figured the data would be quite messy, however it wouldn't be that hard to add basically the same levels as the JSON reader.
This fundamental issue exists in all the readers that read data without a schema.  My rationale for working on the XSD reader is that this will enable us to accurately read XML data with all the correct data types.


Tray icon invible in macos dark mode

I have set my system theme to dark mode which sets the background color of the system tray to a very light gray. Since the tray-base.png is white without new notifications the tray icon is basically invisible unless clicked (in fact I only noticed that there was even a tray icon since I had new notifications).

It would be great if gitlight would either provide dedicated icons for dark mode, or if that is impossible with the used tauri-1.* switch the icons to use something which works reasonably well against both a light and a dark background.

Thanks for your feedback!
I think this problem is more about the wallpaper than the os theme, for example here I set a light wallpaper but I'm still in dark mode:

The solution is probably about template icon (https://developer.apple.com/documentation/appkit/nsimage/1520017-template?language=objc\), I'll look into it

Ah you are right. The tray seems to be (at least partially) transparent and my whitish background images shines through.


Got the error "The specified key does not exist."

What's wrong with the error?
here is the endpoint and ibmAuthEndpoint
endpoint: "s3-api.dal-us-geo.objectstorage.softlayer.net",
ibmAuthEndpoint: "https://iam.ng.bluemix.net/oidc/token",

The file you were trying to download/modify/access doesn't seem to exist.
It could be that you accidentally entered the wrong name, or that the object you were looking for was never successfully uploaded. Otherwise, it looks like everything is set up properly though.

I need to upload a file to my bucket, I can use listBuckets  to get my bucket data. But once I use putObject method to upload a file under my bucket, I got the message "Unhandled error for request POST /api/object-storage/objects: NoSuchKey: The specified key does not exist".

I don't see anything that sticks out. I'd maybe double-check that the region you created the bucket in is the same as the region your current config is tied to.
I'm not sure I'll be able to find anything, but would you mind pasting your cos constructor/configuration minus apikey/serviceinstanceid/accesskeys?

Those are my credentials
  endpoint: "s3-api.dal-us-geo.objectstorage.softlayer.net",
  apiKeyId: "uDA5SQ7SBlZa5fOFACdfJM-mAOS1wd2lHhYYL9jjbEor",
  serviceInstanceId: "crn:v1:bluemix:public:cloud-object-storage:global:a/3496eff1aa4dc5ce59049e0bb8cbf05e:485ac6b3-4a27-43c6-bda2-c2ac2a0bba45::",

resovle by my self :)

Hi @TopGunBasten
I have the same issue
How did you resolve it?
Thanks

Just in case you have the same errors, I have solved this passing the stage variable to my lambda.

please use correct region with the corresponding endpoints

While creating the bucket, create a cross region bucket or give correct end point to your us-east or wherever region you have defined

i found that the endpoints had been changed.
from these
auth_endpoint = 'https://iam.bluemix.net/oidc/token'
service_endpoint = 'https://s3-api.us-geo.objectstorage.softlayer.net'
to
auth_endpoint = 'https://iam.bluemix.net/identity/token'
service_endpoint = 'https://s3.ap.cloud-object-storage.appdomain.cloud'
how do we contact someone to change / update the course accordingly?

Believe it or not I actually got this error when I incorrectly tried to grab the stream from my LOCAL file, so don't let that fool you.


HBASE-23031 Upgrade Yetus version in RM scripts

The latest version of Apache Yetus is 0.11.0

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
6m 17s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:blue_heart:
shelldocs
0m  0s
Shelldocs was not available.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

:blue_heart:
mvndep
0m 42s
Maven dependency ordering for branch

_ Patch Compile Tests _

:blue_heart:
mvndep
0m 10s
Maven dependency ordering for patch

:green_heart:
shellcheck
0m  2s
There were no new shellcheck issues.

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

_ Other Tests _

:blue_heart:
asflicense
0m  0s
ASF License check generated no output?

8m 16s

Subsystem
Report/Notes

Docker
Client=19.03.2 Server=19.03.2 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-692/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/692

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux a9e9eb603635 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-692/out/precommit/personality/provided.sh

git revision
master / f69e7705e0

Max. process+thread count
46 (vs. ulimit of 10000)

modules
C:  U:

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-692/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) shellcheck=0.7.0

Powered by
Apache Yetus 0.11.0 https://yetus.apache.org

This message was automatically generated.


Extend the parser to handle embedded line comments

Currently, only comment lines are ignored
# test
https://hexdocs.pm/dotenvy/dotenv-file-format.html#comments
The hash-tag # symbol denotes a comment when on its own line or when it follows a quoted value. It is not treated as a comment when it appears within quotes.
# This is a comment
SECRET_KEY=YOURSECRETKEYGOESHERE # also a comment
SECRET_HASH="something-with-a-hash-#-this-is-not-a-comment"

Handled in 1abe1d2


Make it possible to test using the token contract WASM

What
Adds new feature "token-wasm" that enables using the WASM. Adds a new line to Makefile to actually run this test.
Why
Resolves #29.
Known limitations
Doesn't pass tests right now because the WASM itself doesn't work.

Closing this to change the target branch.


Backdeploytest

update

Hello @gwenchee! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file tests/integration_tests/back_deployment_test.py:

Line 34:80: E501 line too long (106 > 79 characters)


Full screen to VR device

WebVR extends the HTML5 full screen API to allow full screening to a VR display device; voxel-VR and/or https://github.com/deathcap/voxel-fullscreen ought to support this
if( canvas.webkitRequestFullscreen ) {
canvas.webkitRequestFullscreen({vrDisplay: vrHMD});
} else if( container.mozRequestFullScreen ) {
container.mozRequestFullScreen({vrDisplay: vrHMD});
}

Considering adding a config option to voxel-fullscreen to pass arbitrary fullscreen options, but right now it is calling requestFullScreen(ALLOW_KEYBOARD_INPUT), how to both enable keyboard input and set the vrDisplay, request(ALLOW_KEYBOARD_INPUT, {vrDevice: vrHMD})?
requestFullScreen({vrDevice: …}) is not documented in https://github.com/MozVR/webvr-spec/blob/master/WebVR-spec.html, no search engine hits for "requestfullscreen ALLOW_KEYBOARD_INPUT vrDisplay", but vrDisplay is mentioned in http://blog.bitops.com/blog/2014/06/26/first-steps-for-vr-on-the-web/


Remove _experimental flag

Summary
Remove _experimental flag since we now use version.
Details and comments
Fixes #

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.008%) to 51.91%

Totals

Change from base Build<PHONE_NUMBER>:
-0.008%

Covered Lines:
3099

Relevant Lines:
5970

💛  - Coveralls


add machine-readable version of Open Government Directive

content has been added here
just needs markup!

basic outline markup has been added


Keep getting Failed to resolve directive: validate

Hey,
I have installed Vue-validator 1.4.4 and set it all up but i keep getting Failed to resolve directive: validate i just used the example
<validator name="validation1">
  <form novalidate>
    <input type="text" v-validate:username.required>
    <input type="text" v-validate:comment.maxlength="256">

      Rquired your name.
      Your comment is too long.

    <input type="submit" value="send" v-if="$validation1.valid">
  </form>
</validator>

What can i have done wrong?

Hi :smile_cat:
The above codes doesn't work 1.4.4.
You can upgrade to 2.0.0-alpha latest version.
Please try it :smile_cat:

Hi,
i have the same issue with<EMAIL_ADDRESS><EMAIL_ADDRESS>


Jitterish audio with livestream specific stream

Describe the Bug
When playing a specific livestream, the audio stutters- no matter which buffer settings I pick.
Steps To Reproduce
Create a track with this URL to play: https://stream1.icehosting.nl/1twente-hengelo/;stream.mp3. This audio plays perfectly fine on my browser.
Code To Reproduce
Open example app and use above stream to test.
Replicable on Example App?
Can you replicate this bug in the React Native Track Player Example App?
Yes.
Environment Info:
System:
  OS: macOS 14.0
  CPU: (10) arm64 Apple M1 Pro
  Memory: 216.16 MB / 32.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.2.0
    path: ~/.nvm/versions/node/v20.2.0/bin/node
  Yarn:
    version: 1.22.19
    path: ~/.nvm/versions/node/v20.2.0/bin/yarn
  npm:
    version: 9.8.0
    path: ~/.nvm/versions/node/v20.2.0/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.13.0
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.0
      - iOS 17.0
      - macOS 14.0
      - tvOS 17.0
      - watchOS 10.0
  Android SDK:
    Android NDK: 22.1.7171670
IDEs:
  Android Studio: Not Found
  Xcode:
    version: 15.0/15A240d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: <IP_ADDRESS>
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.72.6
    wanted: 0.72.6
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

Using 3.2.0, but I tested it with the latest RC as well - same issue.
Tested it on a simulator, and on my Samsung S23.
How I can Help
I am unsure what is causing this. Once I know what is causing this, I can take a look at a possible PR, however I have slim to no experience with iOS development. I have some with Android, so happy to help out!
Hoping for anyone to have some information as to why this is happening.

is this happening on android or ios? (Since the first title of this issue contained ios and your test device was a Samsung)

Hi @puckey, the issue is happening on Android and iOS. I tested it on iOS emulator first and after creating this ticket I thought: hey, let me check my phone too! Hence I added my Samsung S23 Ultra as well.

Hmm I see what you mean with the stuttering audio – not sure what might be causing it though.. Especially since the underlying playback systems are completely different between android and ios.

Yes I wonder what this is, because its not happening on web. I tried to view logmessages of logcat on android but nothing really that pops out. Any ideas?

is your station carried on any other radio apps? might be interesting to see if the problem is occurring there also

I hear your stream stuttering in my Safari too. I think it is not an RNTP-related issue.

Indeed, this was an issue on our end. A reboot of the streaming server fixed the issue. Thanks all!


Add default case for useReducer form example

The current example's reducer function doesn't have a default case, so I thought I'd add one and put the error throwing inside it. :)

the code is fine as-is; the way it is has the advantage of also throwing if you forget to return in one of the cases


Add decimal type validation rule

Add a rule to validate precision and scale in decimal(p,s) are all matched in target data source table/sql

legacy issue.


jshint shows no error but they appear in Sublime

I am consuming an external API and I do not want to rename incoming data fields fields
var User = function() {
  'use strict';
  /* jshint camelcase: false */
  this.user_id = null;
  this.username = null;
  this.isAdmin = function() {
    return true;
  };
};

When I run jshint from the command line I get no error, but Sublime shows an error exactly where the suppressing comment is placed:
User.js: line 18, col 0, Identifier 'user_id' is not in camel case.
My .jshintrc is:

{
  /*
   * ENVIRONMENTS
   * =================
   */

  // Define globals exposed by modern browsers.
  "browser": false,

  // Define globals exposed by jQuery.
  "jquery": false,

  // Define globals exposed by Node.js.
  "node": true,

  // Allow ES6.
  "esnext": false,

  /*
   * ENFORCING OPTIONS
   * =================
   */

  // Force all variable names to use either camelCase style or UPPER_CASE
  // with underscores.
  "camelcase": true,

  // Prohibit use of == and != in favor of === and !==.
  "eqeqeq": true,

  // Enforce tab width of 2 spaces.
  "indent": 2,

  // Prohibit use of a variable before it is defined.
  "latedef": true,

  // Enforce line length to 80 characters
  "maxlen": 80,

  // Require capitalized names for constructor functions.
  "newcap": true,

  // Enforce use of single quotation marks for strings.
  "quotmark": "single",

  // Enforce placing 'use strict' at the top function scope
  "strict": true,

  // Prohibit use of explicitly undeclared variables.
  "undef": true,

  // Warn when variables are defined but never used.
  "unused": true,

  /*
   * RELAXING OPTIONS
   * =================
   */

  // Suppress warnings about == null comparisons.
  "eqnull": true
}

Cannot reproduce in recent versions. Probably a configuration issue, or it basically solved itself in recent years.


Improve discoverability of napari/docs repository.

Fixes/Closes
Description

Currently, When user see list of issue templates, there is a Documentation template that suggest that all documentation-related problems should be reported in the napari main repository.
In This PR I add information about napari/docs
References

Type of change

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

How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change
[ ] example: I check if my changes works with both PySide and PyQt backends
as there are small differences between the two Qt bindings.

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

Good catch! Thanks @Czaki ! ❤
I made a small tweak to the wording, not sure it's clearer or not.


Check topic filters

This the last missing part of the specification, so from now on we have
fully compliant implementation of the parser.
Closes #1.
@drets please, review.

Minor comment, otherwise LGTM 👍


Cannot connect via the client on OSX

I'm running OSX Yosemite and using Chrome. The online demos work fine for me but when running the server locally, I can access the page and enter my name but the game never loads when I press the play button.

I had a similar problem with the latest version. I just cloned the repository again and it worked. Check what error you're getting with inspect elements in chrome. Use npm install and npm start. Im using ubuntu so I dont think it's your os.

Yeah first of all try deleting the your directory and cloning it again, then run npm install and npm start, let us know if it still doesn't work after that :)

Awesome, it worked, thanks! I figured it out, node server/server.js doesn't work anymore because it doesn't start Gulp. The readme says you can start the server using either.

Good catch, I'll update it!


PDF JIS Z 8301: wrong indent for multiline example

Source issue: https://github.com/metanorma/metanorma-jis/issues/9
Original PDF:

Generated PDF:

The indent occurs due the wide character ［ (U+FF3B, Fullwidth Left Square Bracket). Second line indentation can be 'modelled' by adding four nbsp chars.

Done:


 Seems like a bug somewhere! This is on latest. I'm tracing back to see if I can find a working version, but I'm not sure how much time I have to spin on this project.

Thanks for the report! When you say "latest" do you mean the latest commit on master or the latest release?
Our S3 integration test for multipart uploads work: I ran the test and ensured the multipart upload works as expected: file size and contents are correct and aws s3api list-multipart-uploads --bucket BUCKETNAME doesn't show any incomplete uploads.
However, that test uses upload_part instead of upload_copy_part. Perhaps upload_copy_part is where the bug is.

Hi @matthewkmayer! Sorry, yes, latest release 0.35 in my Cargo.toml. I haven't tested upload_part, only upload_copy_part but yes - definitely can't see to get anything back, the output is always completely empty!

I've reproduced the bug. 🎉
Working on a unit test to verify our parsing is correct. If that's working right it's off to see what the difference is between what AWS sends us and what we expect.

@matthewkmayer awesome! Do you have a diff I can apply for the unit test? I'd be happy to take a shot at patching it (unless you're already getting there :p)

https://github.com/rusoto/rusoto/compare/s3-multipart-upload-copy-bug?expand=1 will show the work on the branch I've pushed up. Also has an integration test which I used to get the result from AWS.
I'm probably going to run out of time soon, so if you'd like to get a fix done that'd be excellent. 👍 I'm currently exploring https://github.com/rusoto/rusoto/pull/892 since it fixed a similar issue of consuming the XML node before we attempt to pull out its value.
<CopyPartResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
  <LastModified>2018-11-10T02:47:18.000Z</LastModified>
  <ETag>"9a9d1bbe80188883302bff764b4cb321"</ETag>
</CopyPartResult>

In this case we're consuming CopyPartResult before trying to find it, so the resulting object we return is completely blank since the deserializer can't find it.

@matthewkmayer I'm new to this project, so progress is definitely slow :p One thing I don't seem to get though; I think the unit test should have some sort of outer binding in the XML response, right?

Ok, I think I've got this fixed in https://github.com/rusoto/rusoto/pull/1196. I'm a little worried about it affecting anything else, but all tests continue to pass so I don't think I broke anything 😅.
As mentioned in the PR, there are optimizations we can do here too by omitting some deserializers but I stopped short of that because a) it was complicated, and b) it would change the existing APIs.


Auto Parry

[Enter feedback here]

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

ID: fb8172aa-183f-6821-f7a3-1a1f838d671c
Version Independent ID: fb8172aa-183f-6821-f7a3-1a1f838d671c
Content: Simplify DevTools using Focus Mode - Microsoft Edge Development
Content Source: microsoft-edge/devtools-guide-chromium/experimental-features/focus-mode.md
Product: microsoft-edge
Technology: devtools
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

Closing as incomplete. Please feel free to add more information if you have any and we can re-open the issue.


There is no way to decrypt

How would it be possible to decrypt the script, there is no option on the page, there is only option to encrypt

You can just take the original script from loadstring or load 's first argument. Just change it to print.

You can just take the original script from loadstring or load 's first argument. Just change it to print.


do not review  -- testing

@ironman-machine all systems batch delete?

Hello @LaurenSpiegel
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_S3_BRANCH": "ft/batchDelete", "DEFAULT_BRANCH": "master"}
Please follow http://ci.ironmann.io/gh/scality/Integration/5122 for CI status.

@ironman-machine please try again

Hello @LaurenSpiegel
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_S3_BRANCH": "ft/batchDelete", "DEFAULT_BRANCH": "master"}
Please follow http://ci.ironmann.io/gh/scality/Integration/5124 for CI status.

@ironman-machine so close
SCALITY_INTEGRATION_BRANCH=ft/batchDelete

Hello @LaurenSpiegel
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_S3_BRANCH": "ft/batchDelete", "DEFAULT_BRANCH": "master", "SCALITY_INTEGRATION_BRANCH": "ft/batchDelete"}
Please follow http://ci.ironmann.io/gh/scality/Integration/5126 for CI status.

@ironman-machine give it a go
SCALITY_INTEGRATION_BRANCH=ft/batchDelete

Hello @LaurenSpiegel
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_S3_BRANCH": "ft/batchDelete", "DEFAULT_BRANCH": "master", "SCALITY_INTEGRATION_BRANCH": "ft/batchDelete"}
Please follow http://ci.ironmann.io/gh/scality/Integration/5262 for CI status.

@ironman-machine with the module
SCALITY_INTEGRATION_BRANCH=ft/batchDelete

Hello @LaurenSpiegel
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_S3_BRANCH": "ft/batchDelete", "DEFAULT_BRANCH": "master", "SCALITY_INTEGRATION_BRANCH": "ft/batchDelete"}
Please follow http://ci.ironmann.io/gh/scality/Integration/5304 for CI status.

@ironman-machine get it on
SCALITY_INTEGRATION_BRANCH=ft/batchDelete
SCALITY_VAULT_BRANCH=ft/batchDelete

Hello @LaurenSpiegel
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_S3_BRANCH": "ft/batchDelete", "DEFAULT_BRANCH": "master", "SCALITY_VAULT_BRANCH": "ft/batchDelete", "SCALITY_INTEGRATION_BRANCH": "ft/batchDelete"}
Please follow http://ci.ironmann.io/gh/scality/Integration/5575 for CI status.

@ironman-machine being explicit
SCALITY_INTEGRATION_BRANCH=ft/batchDelete
SCALITY_VAULT_BRANCH=ft/batchDelete
SCALITY_ARSENAL_BRANCH=ft/batchDelete
SCALITY_UTAPI_BRANCH=ft/batchDelete
SCALITY_VAULTCLIENT_BRANCH=ft/batchDelete

Hello @LaurenSpiegel
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_UTAPI_BRANCH": "ft/batchDelete", "SCALITY_INTEGRATION_BRANCH": "ft/batchDelete", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "ft/batchDelete", "SCALITY_ARSENAL_BRANCH": "ft/batchDelete", "SCALITY_VAULTCLIENT_BRANCH": "ft/batchDelete", "SCALITY_VAULT_BRANCH": "ft/batchDelete"}
Please follow http://ci.ironmann.io/gh/scality/Integration/5586 for CI status.


Fixed substitution for list of strings

When doing the substitutions in a pipeline step, an issue was found when the value object contained a list of strings - as each string was being treated as a dict.

/test-extended


Error: didn't find any Jaguar devices

From tmit to time Jaguar application stops running:
failed to ping 'device'.
Scanning ...
Error: didn't find any Jaguar devices
[wifi] DEBUG: connecting
[wifi] DEBUG: connected
[wifi] DEBUG: closing
[jaguar] WARN: running Jaguar failed due to 'DEADLINE_EXCEEDED' (2/3)
??? any glue?

Are there any exceptions that could help debug this issue?

this is the monitor output:
o
o    ESP32 TOIT Prototype, Motion sensor and HASS-interface
o
o    dev-ID: 1f84d167-d56b-5c38-85f4-610f775a97a8
o
[wifi] DEBUG: connecting
[wifi] DEBUG: connected
[wifi] DEBUG: closing
[wifi] DEBUG: connecting
[jaguar] WARN: running Jaguar failed due to 'DEADLINE_EXCEEDED' (1/3)
[wifi] DEBUG: connected
[wifi] DEBUG: closing
[wifi] DEBUG: connecting
Received a Toit system message. Executing the command below will
make it human readable:
build/host/sdk/bin/toit.run tools/system_message.toit "$SNAPSHOT" -b WyNVBVVYU1UOdjIuMC4wLWFscGhhLjFTVQBbJFUjVRAAAAAAAAAAAAAAAAAAAAAAWyNVBFVFU1UJRVhDRVBUSU9OU1URREVBRExJTkVfRVhDRUVERURbI1UCVVNbI1UjWyNVA1VGVQBJWCVbI1UDVUZVAUliSlsjVQNVRlUCSWFlWyNVA1VGVQNJWaNbI1UDVUZVBElaBVsjVQNVRlUFSWF4WyNVA1VGVQZsAACJb1sjVQNVRlUHSTqrWyNVA1VGVQhJRLhbI1UDVUZVCUlE3VsjVQNVRlUKSRj7WyNVA1VGVQtJGNhbI1UDVUZVDEk61lsjVQNVRlUNSTr5WyNVA1VGVQ5JYrlbI1UDVUZVD0lZo1sjVQNVRlUQSVoFWyNVA1VGVRFJYtBbI1UDVUZVEkk6Q1sjVQNVRlUTSTnFWyNVA1VGVRRJOTpbI1UDVUZVFUk5tVsjVQNVRlUWSR1oWyNVA1VGVRdJJaJbI1UDVUZVGEklylsjVQNVRlUZSVz9WyNVA1VGVRpJXSVbI1UDVUZVG0ldXFsjVQNVRlUcSQoUWyNVA1VGVR1JCztbI1UDVUZVHkkLUFsjVQNVRlUfSQsrWyNVA1VGVSBJRX5bI1UDVUZVIUlFkVsjVQNVRlUiSQoo
[wifi] DEBUG: connected
[wifi] DEBUG: closing
[jaguar] WARN: running Jaguar failed due to 'DEADLINE_EXCEEDED' (2/3)
[wifi] DEBUG: connecting
[wifi] DEBUG: connected

I found out, that after reflashing the controller runs.
But if I start the "jag monitor" afterwards the controller hangs up ans shows the 'DEADLINE_EXCEEDED' message.
After a reset with running/already opened montor the controller runs properly and shows the debug message in monitor window.
BUT if I close the monitor an reopen it again, the controller behaves faulty again.


Merge upstream v0.0.19

I'm not sure that I actually want to merge this one to master, but more generally make this the main branch.


Move review page and add placeholder for restaurant page

#38 initial page created, maybe needs to move the review also in that.
Another idea is to move everything to the list page as a drawer thingy

Moved details to sidebar


⚠ Bofrost.fr has degraded performance

In a7d3d43, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1165 ms

Resolved: Bofrost.fr performance has improved in 7fe98d9.


[Bug]: Project does not Create Jar File in IntelliJ

Is there an existing issue for this?

[X] I have searched the existing issues

Contact Name
Anton
Description of the bug?
Project does not create Jar file
Version
Develop Branch
Steps to Reproduce the Error
Run Build on Maven.

Code of Conduct

[X] I agree to follow this project's Code of Conduct

bug lost in sprint


add showcase docs

reduced docs from mobile-docs

Generally after reviewing the content I think that amount of the files might not justify having this a separate thing. Maybe we can have it merged into or get into some consenus how we link this with push and sync together

Removed setup docs:
None of this info is valid. Showcase is available as part of the template that is described in sync docs (and might be in push) and content there is not reflecting any setup - all was focued on MDC and currently showcase is automatically configured so there is no extra work needed to get it running unless we do Auth. For auth we have dedidacted walkthough


Good catch, we'll look into this.

@rtyler Good catch. This will be fixed by #32.

@rtyler Thanks for reporting this. The fix has been merged. The server is also updated with the latest change that should report the 400 error for an invalid json.

@zsxwing did y'all happen to set up a CD pipeline for the demo site, or will we need to wait for Denny to get back from his "Eat. Throw. Love." ultimate frisbee vacation? :smile:

We have not set up an automatic CD pipeline yet. I'm doing the deployment manually. But this is a good idea. I will wait for Denny and get his help 😄 .


Add execution stat reporting after each invocation

What type of PR is this? (check all applicable)

[X] Feature

Have you discussed this change with the InvokeAI team?

[X] Yes
[ ] No, because:

Have you updated all relevant documentation?

[X] Yes
[ ] No

Description
This PR adds execution time and VRAM usage reporting to each graph invocation.
The current implementation keeps track of graph ids separately so will not be confused when several graphs are executing in parallel. It handles exceptions, and it is integrated into the app framework by defining an abstract base class and storing an implementation instance in InvocationServices.

Lgtm. We might consider throwing in the session ID to be able to differentiate if multiple are being run in parallel.
also black test is failing

I'm going to keep track of the graph ids so that each graph is reported separately rather than getting mixed. So don't merge yet.

Lgtm. We might consider throwing in the session ID to be able to differentiate if multiple are being run in parallel.
also black test is failing

This is now done.

This is just too freaking cool! Love it.

This is just too freaking cool! Love it.

I wonder if it makes sense to sort the nodes chronologically?


Refactor/remove launcher

refactor: remove launcher pseudo-app
Removes launcher pseudo app and solely relies on omap.py to start the platform

@JulianFeinauer I rebased it to fix the conflict. Now the CI is broken. You probably know what to do.

@NiklasMerz the issue is indeed a valid one.
Its pytest_django crashing because I removed the settings.py file.
So to be able to use pytest django with the "omap" construction we need a slightly patched version of pytest_django, I guess...

@NiklasMerz I opened an issue on pytest-django, that would solve the problem for us: https://github.com/pytest-dev/pytest-django/issues/1001

@NiklasMerz you see a demo implementaton here: https://github.com/pytest-dev/pytest-django/pull/1002
And this is how the code would need to be modified to work, if the PR above would be merged: https://github.com/pragmaticindustries/open-machine-plattform/tree/feature/new-launcher-with-pytest-fixes

@NiklasMerz thanks to your hint its green again now : )


[Gally]: master <- dev

Automatically created by Git-Ally

:tada: This PR is included in version 2.9.13 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


merge from template-sync/template-arlac77-github

package.json

chore(deps): add ^15.5.0 remove ^15.4.0 (devDependencies.npm-pkgbuild)

:tada: This PR is included in version 1.11.62 :tada:
The release is available on:

npm package (@latest dist-tag)
v1.11.62
GitHub release

Your semantic-release bot :package::rocket:


It is possible to add 2 keys with different contents

╰─± deis keys:add
Found the following SSH public keys:
1) deis-champagne.pub<EMAIL_ADDRESS>2) deis.pub deis
3) id_boot2docker.pub<EMAIL_ADDRESS>4) id_rsa.pub<EMAIL_ADDRESS>0) Enter path to pubfile (or use keys:add <key_path>)
Which would you like to use with Deis? 1
Uploading deis-champagne.pub to deis... done
╭─jonathanchauncey at ENG000637 in ~/go/src/github.com/deis/k8s-claimer on master✔ using ‹2.0.0-p645›
╰─± deis keys:add
Found the following SSH public keys:
1) deis-champagne.pub<EMAIL_ADDRESS>2) deis.pub deis
3) id_boot2docker.pub<EMAIL_ADDRESS>4) id_rsa.pub<EMAIL_ADDRESS>0) Enter path to pubfile (or use keys:add <key_path>)
Which would you like to use with Deis? 3
Uploading id_boot2docker.pub to deis... done
╭─jonathanchauncey at ENG000637 in ~/go/src/github.com/deis/k8s-claimer on master✔ using ‹2.0.0-p645›
╰─± deis keys:list
=== admin Keys
<EMAIL_ADDRESS>ssh-rsa AAAAB3Nz...0637.local
<EMAIL_ADDRESS>ssh-rsa AAAAB3Nz...0637.local

this looks important enough to fix for the release candidate.

A bit confused on this one, is it that you expect a 1:1 between user and key?
A user with multiple ssh keys is fine. But a key should not be shared between multiple users.

I think it's just the confusion that the client shows the pulley and the comment, whereas it's the fingerprint that uniquely identifies the key now. Probably just a client fix.

Let's move this issue to workflow-cli instead.

What field is used when deleting the key? It seems to me that deis keys:remove<EMAIL_ADDRESS>works.

Going to mark this one as a duplicate of #1023 even if this is older


Porting CC 89 Langton's Ant

Added:

Thumbnail according to the CT color scheme
Timestamps
Showcase screenshots
Descriptions, tags, icons
Checked links

This looks great!  I think that "102-2d-water-ripple" might be another challenge to add to related challenges.


Support Selective Aggregations: FILTER clause to aggregate Functions

PostgreSQL and SparkSQL support adding the FILTER clause to aggregate functions and this clause is quite useful when we want to count or sum specific records
SELECT SUM(age) FILTER (where name is not null),
SUM(age) FILTER (where name is null)
FROM EMPLOYEE;

https://www.postgresql.org/docs/15/sql-expressions.html#SYNTAX-AGGREGATES

https://modern-sql.com/feature/filter


WIP: Client Type Provider

Here comes the promised PR for the Type Provider. At the end I'm trying a mixed approach: I read the Query objects from the schema and build methods based on that (with the query as a static argument so it can be checked at design time) so the query names and arguments are automatically added (the SelectionSet must still be passed as a string). @Horusiath please have a look and tell me what you think and which features we should focus on. I'm writing some ideas below.

[ ] Improve query validation: right now it's just running parse on the query string. It should validate the name of the fields, etc, as it's done by graphiql
[ ] Support mutations
[ ] Build types for queries according to the fields requested? Though according to what we talked this probably doesn't add much value for the work involved
[ ] Anything else?

I think, that query string validation can come later. Doesn't have to be here right away.
Other remarks:

We could separate queries from mutations and subscriptions by creating static class scopes for them i.e. Instead of using convention MyClient.HeroQuery (what if that field name will be "heroQuery"? "HeroQueryQuery"?), maybe use MyClient.Queries.Hero, MyClient.Mutations.Hero and so on?

Beside that, everything looks cool :+1: Please rebase with dev (remember to update client.fsx example) and we're ready to merge.

Thanks for merging and sorry for the delay, there was a minor error in the server script that troubled me a bit. I implemented your comments. I'm having a first look now at validation and I'm also trying to implement the type provider with Fable so it's easier to use from the client side.
Cheers!

Don't worry. Everything is fine. Regarding Fable, great idea! :)


There should be an issue and PR template

I would like to add an issue and PR template as it will provide more clarity of the issue and PRs

your views @divyanshu-rawat ?

@ParthS007 👍

Great work @ParthS007
It would great if you can add similar templates in other repos also 😄


Password hide from operation log

Should fix #625

It would be nice if this pull request get merged. Quite important in a shared environment.


Maurer Rose contribution: "maurer triangles rainbow swish"

Community Contribution
Link to live project, video, or image:
https://editor.p5js.org/sequentialchaos/full/Zq70Kbrmk
Sharing

[ x] I would be happy to have my project shared on The Coding Train's social media!

Instagram:
Twitter:
@sequentialchaos

This is amazing! ❤


Stackanetes packaged with kpm

Hi
I'm working on a package manager for kubernetes: kpm
I've packaged stackanetes with kpm:
https://github.com/kubespray/kpm-stackanetes
Each component has it's own package and version, which help to iterate and maintain them.
A package named stackanetes/stackanetes, regroup all the dependencies.
To deploy stackanetes with kpm :
pip install kpm
kpm deploy stackanetes/init
kpm deploy stackanetes/stackanetes

I see many advantages to use kpm instead of kolla to deploy the kubernetes resources. If your interested we can scedule a call to discuss them.
cc: @philips

It was quite some work to package everything. I won't be able to maintain and update it in parallel of kolla-k8s development.
I propose to discuss the switch(or not) from kolla to kpm, before that it changes to much.

Moved to #87