Added shuffle option to all flow methods for GraphSAGE and HinSAGE generators

Previously, as we use fit_generator the mini-batches created by our generators have examples that are in fixed order. This will likely reduce the performance of the trained model, especially when our batch sizes are small.
This PR enables the generators to shuffle the data at each epoch when the shuffle=True option is given to the .flow methods of the generator object.
The notebooks have been updated to use the shuffle=True option when training and not use it at prediction time.

Additionally, I've updated the requirements.txt file to fix the current documentation build failure on readthedocs, and removed pyproject.toml due to PEP-517 errors when pip reads the file – this file was used by poetry, but is now breaks newer versions of pip which read this file.

This post was useful in implementing the shuffling:
https://stanford.edu/~shervine/blog/keras-how-to-generate-data-on-the-fly
However, We don't really need to turn shuffling off in the fit_generator call – shuffling the batches will have no effect after all examples are shuffled, so it's not necessary to set shuffle=False.
I think for the full batch node generator we can just not have the option, as it isn't applicable.  I think having the option and then complaining about it if it's True is more confusing.


10.4 / 10.4.1 compatibility?

Says 10.3.3 compatibility.
When will 10.4 or better ,10.4.1 compatibility be added? Since this introduced changes to remove ARC.

I will do my best to do it as soon as possible, maybe with the 10.4.2


Merge vendor-prefixes.txt from all modules with build.settings.dts_root in zephyr/module.yml

Is your enhancement proposal related to a problem? Please describe.
Recently all device tree compatible strings are checked for valid vendor prefixes and a warning is generated if vendor is not listed in ${ZEPHYR_BASE}/dts/bindings/vendor-prefixes.txt. In case of twister builds warnings are errors by default, which results in CI failures. If downstream project has downstream drivers with downstream DT bindings with unknown vendor, then there is no easy way of extending list of possible vendors and suppressing generated warning/error.
Describe the solution you'd like
Iterate over all MODULE/dts/bindings/ directories that are used so far for DT bindings resolution and check if vendor-prefixes.txt exists there. If yes, then merge list of all vendors, so that warnings for downstream drivers (that use vendor unspecified in Zephyr's vendor-prefixes.txt) can be suppressed.
Additional context
Introduced checking of vendor-prefixes.txt breaks downstream projects that use twister in CI. The workaround for now is to disable "warnings as error" in twister or patching Zephyr's vendor-prefixes.txt.

Implemented in https://github.com/zephyrproject-rtos/zephyr/pull/37802. Working in my testing.


[Feature Request]: Footer is so Fade

How would you like to enhance the existing project.
The Footer is fade and not readable, icons are barely visible.

Describe breifly how would you implement the same.
I would like to work on this issue and make it nice.
Are you contributing for a program?
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hi @Priyaaa1 , I have assigned this issue to you. Kindly complete within 2 days. Good luck!

if it's not done then can I work on this ?


Initial library implementation

This PR implements Go client for the Alluxio File System REST API.

@aaudiber this is now ready for your review

@aaudiber thanks for your detailed review, addressed your comments ... PTAL

I think we're down to just 1-2 outstanding minor comments, should be ready to merge soon


Processor FPU option doesn't cover all possible variants

Currently, the FPU enum consists of two options only on/off
    _"fpu": {
      "enum": [ "on", "off" ],
      "description": "Controls usage of FPU registers (S-Registers that are used for Helium and FPU hardware): on | off"
    },_

if (!context.controls.processed.processor.fpu.empty()) {=
if (context.controls.processed.processor.fpu == "on") {
context.targetAttributes["Dfpu"] = "FPU";
} else if (context.controls.processed.processor.fpu == "off") {
context.targetAttributes["Dfpu"] = "NO_FPU";
}
}
However,  Dfpu enumeration type in cprj has also Single (SP_FPU) and Double Precision (DP_FPU) options

<xs:simpleType name="DfpuEnum">
<xs:restriction base="xs:token">

<xs:enumeration value="FPU" />
<xs:enumeration value="1" />

<xs:enumeration value="NO_FPU" />
<xs:enumeration value="0" />

<xs:enumeration value="SP_FPU" />

<xs:enumeration value="DP_FPU" />
</xs:restriction>
</xs:simpleType>
Thus in my opinion the FPU enum in project manager should be extended to all types listed in CPRJ.

We believe that we should present simple, easy to understand options to the user.
While the device itself may have single or double precision floating point unit, we believe it is sufficient to expose just the option to turn on/off the floating point unit.  The effect for the user is that S-registers are used or not-used (which might be important for interrupt code).  For code generation the tools are using the optimum which is either single or double precision.  The details for the FPU are specified in the Device Family Pack.

@ronyrad  any further input here?

Similar issue under #359

On high level scope having just "off" and "on" (which uses full capabilities of a certain device) seems to be sufficient. When it comes to compiling shared libraries or for testing purposes, one might need more fine grained control.
I'd like to propose keeping "off" and "on" as shortcuts for "no fpu" and "fpu" but add expert options like "hp" (half), "sp" (single), "dp" (double) to allow advanced users to steere the details.
Folding in setting for -mfloat-abi (see #359) we could extend as the following:

fpu:
-mfpu=
-mfloat-abi=

off
none
soft

softhp
<half>
softfp

softsp
<single>
softfp

softdp
<double>
softfp

soft
<best>
softfp

hp
<half>
hard

sp
<single>
hard

dp
<double>
hard

on
<best>
hard

The fpu: option enables/disables usage of S-Registers. It therefore also enables the usage of Helium vector instructions. Not sure if we can find a better name for fpu.
I believe features like the above are for expert user cases, and these type of controls are available using misc:.

@ReinhardKeil, misc: might be an option even if we lose compiler abstraction in this way. Are we sure one can overrule default options (that comes from e.g. fpu) by setting the same flags via misc:?

No we are not sure. @brondani we would need to get your view on that.

Replaced by #879 - do not use this for further discussion.  We may refer to it later.


Replace execSync Node module with sync-exec

Using Node 0.12.0 with execSync 1.0.2 produces the following error:
Native code compile failed!!
Since execSync fails to properly install, none of the Gulp tasks are able to run:
Cannot find module './build/Release/shell'

Yeah, I'm going to merge this for now but will anyhow rewrite that piece of the gruntfile. We'll be moving away from Compass. Could you bump the version number in .travis.yml? This was the reason I didn't do that yet.

Thanks a lot :octocat:
Unfortunately your change is obsolete. Hope to see you contributing again.


File missing: once/ImageSets

data folder provides the imagesets for kitti/lyft/waymo but once/imagesets does not exist, could you tell me where I can get this file? The official page for once not provide, either.

I produced the once/ImageSets and raise a pr #1238 to solve it, please give it a look


Add async events

This feature allows us to yield multiple state updates from an event handler.
This is a breaking change in how the main processing loop works.
Example code:
"""Welcome to Pynecone! This file create a counter app."""
import random

import asyncio
import pynecone as pc

class State(pc.State):
    """The app state."""

    count = 0

    async def go(self):
        for _ in range(5):
            await asyncio.sleep(0.5)
            self.count += 1
            # Every yield will trigger a state update on the frontend.
            yield

def index() -> pc.Component:
    return pc.center(
        pc.vstack(
            pc.heading(State.count),
            pc.hstack(
                pc.button(
                    "Go",
                    on_click=State.go,
                    background_image="linear-gradient(90deg, rgba(255,0,0,1) 0%, rgba(0,176,34,1) 100%)",
                    color="white",
                ),
            ),
            padding="1em",
            bg="#ededed",
            border_radius="1em",
            box_shadow="lg",
        ),
        padding_y="5em",
        font_size="2em",
        text_align="center",
    )

# Add state and page to the app.
app = pc.App(state=State)
app.add_page(index, title="Counter")
app.compile()

https://github.com/pynecone-io/pynecone/assets/6270214/7916fcb7-4aa5-44b5-b89e-3d2d3123e9b7

@picklelo
Wow, I saw this delicious keyword ... yield 😊😊


Reminder: Suggested handleUpgrade and connection flow

It's probably a good idea to stick to something like this:
import WebSocket from 'ws';
import { createServer } from 'http';

const server = createServer();
const wss = new WebSocketServer({ noServer: true });

server.on('upgrade', function upgrade(request, socket, head) {
  // This function is not defined on purpose. Implement it with your own logic.
  authenticate(request, (err, client) => {
    if (err || !client) {
      socket.write('HTTP/1.1 401 Unauthorized\r\n\r\n');
      socket.destroy();
      return;
    }

    wss.handleUpgrade(request, socket, head, function done(ws) {
      // You are done. `ws` is your `WebSocket` instance, you can do
      // whatever you want with it.
    });
  });
});

server.listen(8080);

as discussed in https://github.com/websockets/ws/pull/1966#issuecomment-956449094
Same discussion, just older: https://github.com/websockets/ws/issues/377#issuecomment-462152231
const http = require('http');
const WebSocket = require('ws');

const server = http.createServer();
const wss = new WebSocket.Server({ noServer: true });

wss.on('connection', function connection(ws, request, ...args) {
  // ...
});

server.on('upgrade', async function upgrade(request, socket, head) {
  // Do what you normally do in `verifyClient()` here and then use
  // `WebSocketServer.prototype.handleUpgrade()`.
  let args;

  try {
    args = await getDataAsync();
  } catch (e) {
    socket.destroy();
    return;
  }

  wss.handleUpgrade(request, socket, head, function done(ws) {
    wss.emit('connection', ws, request, ...args);
  });
});

server.listen(8080);

And an even older suggestion, with some potential: https://github.com/websockets/ws/issues/377#issuecomment-420169849
const userRequestMap = new WeakMap();

const server = new ws.Server({
    port,
    verifyClient: (info, done) => {
        const user = authenticateUser(info);
        userRequestMap.set(info.req, user);
        done(user !== null);
    },
});

server.on('connection', (connection, request) =>{
    const user = userRequestMap.get(request);
});

Another one, pretty much the same as the userRequestMap above. From: https://github.com/websockets/ws/issues/377#issuecomment-997195694
const { WebSocketServer } = require('ws');

const wss = new WebSocketServer({
  port: 8080, verifyClient: async ({ req }, cb) => {
    const { headers } = req;
    if (headers.token) {
      const decodedToken = await decodeToken(headers.token);
      // req.headers.decodedToken = JSON.stringify(decodedToken);
      // As noted. The token can just as well be added directly to req
      req.decodedToken = JSON.stringify(decodedToken);
      cb(true);
    } else {
      cb(false, 401, 'Unauthorized');
    }
  }
});

wss.on('connection', (ws, req)=> {
  console.log("on Connection decodedToken ==> ", JSON.parse(req.decodedToken));
});

Need expansion in the if (headers.token) block. Error handling, wrapping in try / catch or chaining.


CB-14348: Add FreeIPA rebuild API

Create an API in the FreeIPA management service for rebuilding a
FreeIPA cluster. Rebuilding creates a new cluster in an environment
with the same configuration of the original source FreeIPA cluster so
that a backup can be restored but this does not restore the backed up
data.
Several internal APIs and database repositories now support a list of
FreeIPA clusters rather than a single cluster. This allows the old
cluster information to be used for the restoration. During cluster
deletion, some cluster information that was previously deleted from
the database is now kept. This is needed in order to fully reconstruct
the original FreeIPA creation request.
This was tested in a local deployment of cloudbreak on 2.49 and 2.50
in Azure and AWS. Unit tests were also added.
See detailed description in the commit message.

This is for ENGESC-11674. I have 2 PRs for this.
https://github.com/hortonworks/cloudbreak/pull/11827 <-- for master
https://github.com/hortonworks/cloudbreak/pull/11826 <-- for 2.49
I know that we normally only put the PR in one place at a time. But I don't want to delay things further on this escalation. We have some tests that will be easier to run in mow-dev. As a result, I want to try and see about getting the fix into mow-dev and mow-int quickly. I know that one of these PRs might get closed, but I wanted to ensure that tomorrow both branches have a PR that has run the pre-commit testing.


Timeouts

I am getting a lot of timeouts
message: 'request to https://stats.nba.com/stats/leaguedashplayerstats?College=&Conference=&Country=&DateFrom=&DateTo=&Division=&DraftPick=&DraftYear=&GameScope
=&GameSegment=&Height=&LastNGames=0&LeagueID=00&Location=&MeasureType=Base&Month=0&OpponentTeamID=0&Outcome=&PORound=0&PaceAdjust=N&PerMode=PerGame&Period=0&Playe
rExperience=&PlayerPosition=&PlusMinus=N&Rank=N&Season=&SeasonSegment=&SeasonType=Regular%20Season&ShotClockRange=&StarterBench=&TeamID=0&VsConference=&VsDivision
=&Weight= failed, reason: read ETIMEDOUT',

Is there some throttling or quotas on the nba endpoints? or is there some way to get around this?

are you making requests from your local machine or from a cloud instance? nba.com blocks ip addresses of known cloud providers by letting requests hang and time out.

I'm running it locally. I'm probably hitting the rate limit. Any chance you know what that is?

No, I think it varies by endpoint. But if I need to run a lot of requests I just try to do 1 per second then walk away and wait for it to finish;
const delay = ms => new Promise(r => setTimeout(r, ms));

const playerInfo = [];
for (const player of players) {
  playerInfo.push(await nba.playerInfo({ PlayerID: player.PlayerID });
  await delay(1000);
}


service broker creation failed

I was able to deploy the service broker using bosh deploy command. While creating the service broker (cf create-service-broker containers containers http:://cf-containers-broker.XX.XX.XX.XX.xip.io), its failing with an unknown error.
Error trace:
REQUEST: POST http://api.<IP_ADDRESS>.xip.io/v2/service_brokers REQUEST_HEADERS: Accept : application/json Authorization : [PRIVATE DATA HIDDEN] Content-Length : 153 Content-Type : application/json REQUEST_BODY: {"name":"cf-containers-broker","broker_url":"http://cf-containers- broker.<IP_ADDRESS>.xip.io","auth_username":"containers","auth_password":"conta iners"} RESPONSE: [500] RESPONSE_HEADERS: content-length : 99 content-type : application/json;charset=utf-8 date : Fri, 19 Feb 2016 09:43:27 GMT server : nginx x-cf-requestid : 40d370ee-688d-4b9f-4138-7f412ed84a5f x-content-type-options : nosniff x-vcap-request-id : 044e8c41-a802-4031-4103-cae15d0527b8::38a71413-31f9-4f9c-a 61b-6c3e9ebe156d RESPONSE_BODY: { "error_code": "UnknownError", "description": "An unknown error occurred.", "code": 10001 }

Hi, I am experimenting the same error. Any hints?

I'm moving the service broker component of docker-boshrelease into https://github.com/cloudfoundry-community/cf-containers-broker-boshrelease. If this issue still persists, please recreate issue. Sorry in advance for closing ticket.


upgrade carbon anayltics and metrics versions

purpose
$ subject

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2087587171

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2087587171
Status: success


Extract increment-application-version --match into own command

The current functionality behind increment-application-version --match should reside in an own command.

Done with 42431f27fad08f492b979ecb613e9fd254d73f15 by renaming the command to application-version and the option to --verify-tag-match.


Clean up a bit before guests come over

@aamontal You may want to close this PR, and instead merge this into your refactoring branch, so you can start adding improved comments.


TEP-0114: Stop serving v1beta1.CustomRun until we align on Retries

Changes

In this change, we stop serving the v1beta1.CustomRun CRD. This is because we are still discussing how to handle Retries in CustomRuns.
Related TEPs:

TEP-0114: Custom Tasks Beta
TEP-0121: Retries

Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[x] Has Docs included if any changes are user facing
[x] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[x] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

/kind cleanup

/test check-pr-has-kind-label

/hold
need to fix the e2e tests

/retest
Those failures don't make much sense at first glance - seems worth a rerun.

@jerop I spun up a cluster locally with this change, and while I didn't get the error here, the controller had this in its logs:
W1109 18:36:14.763454       1 reflector.go:424] k8s.io/client-go@v0.25.3/tools/cache/reflector.go:169: failed to list *v1beta1.CustomRun: the server could not find the requested resource (get customruns.tekton.dev)
E1109 18:36:14.766094       1 reflector.go:140] k8s.io/client-go@v0.25.3/tools/cache/reflector.go:169: Failed to watch *v1beta1.CustomRun: failed to list *v1beta1.CustomRun: the server could not find the requested resource (get customruns.tekton.dev)

(and other issues in the webhook)
We've gotta remove the customrun.NewController() reference from cmd/controller/main.go, and v1beta1.SchemeGroupVersion.WithKind("CustomRun"):   &v1beta1.CustomRun{} from cmd/webhook/main.go to turn off serving for v1beta1.CustomRun. Once I did that, things worked.

/hold cancel
e2e test fixed, many thanks to @abayer!

/lgtm


feat: added a template parser

Copied the parser bits from cfngine. I left the evaluation part out because it doesn't seem to be directly useful for deCDK.
The next step is to implement an evaluator, based on the same principles, but one that converts the AST into resources in a CDK stack. Once we have that, we can remove graph.ts, object-matchers.ts and most of deconstruction.ts.

Nice one! This looks great.
Are there any tests we can copy over from cfngine ? Other comments/suggestions are non-blocking.

I had forgotten about the tests. I copied one, that tests analyzeSubPattern(). The others are about evaluation. In any case, we probably need to add more tests later.


RMM: Add attestation implementation and test command for cli

Implement attestation:

Implement Realm token and CCA token creation,
Use Platform token and private RAK fetched using RMM EL3,
Add simple tests for measurement read, measurement extend, get Realm Attestation Key and get Platform token RSI apis.

Please update the "Islet RMM dependencies" section of https://github.com/Samsung/islet/blob/main/doc/dev-dependencies.md document

Yes, missed that. Done

Could you update dev-dependencies.md at another branch?
Type is split into Buildtime and Runtime.
https://github.com/Samsung/islet/blob/documentation/doc/dev-dependencies.md


tools: Move io utils to cpp

In preparation for more code in that file, which would get unwieldy in a header.

Context: Going to add a hex reader as an alternative to binary data because sometimes we (myself, @spencer-lunarg) find ourselves with an array of 0x... data and it's annoying not being able to directly read that. Spencer's SPIR-V Visualizer has this, which could be replaced by direct support in spirv-dis for example: https://www.khronos.org/spir/visualizer/


Everything is working now.

Now everything is working including the angular part.
We would need to find other sources to study and understand the angular part since Wu Qun's video does not include it.
I still suggest rewriting the implementation using spring boot style and JPA to get rid of the boilerplate codes.

Sorry @JesseZhuang , I don't know why I cannot merge your PR and it says "This branch has conflicts that must be resolved". I tried to use the command line to resolve conflicts but failed. Maybe you should create one new PR.


InvokeAsync deprecated

Hi and thanks for the awesome tool!
After building from latest sources and running, I get the following warning:
"This operation, InvokeAsync, has been deprecated"
Can you please fix it?

@jazzl0ver are u still getting it?

I haven't been using goad since then, sorry.


section cells don't close right away

there is a delay of about 0.5 seconds between click and close.

I think this was a problem before (seems tree related), but I recently took off the animation, which might have distracted from it a bit.  I'll look into this though.

I stand corrected.


Issue #447 dirty state on replace

The dirty state works better.
Unit tests fail on local. I can't get why, I'm missing some insight.

Thanks for working on this!
The changes in SavedStatusService.js and app.js look very good.
For the HistoryService, I had something simpler in mind. What about creating a UUID when we create a state object, add it to the state object. I might be missing something but I don't see why we should refactor the internals of the HistoryService here. Let's discuss!

@GMartigny let me know if you still want to work on this. Otherwise, I might pick it up :)

@juliandescottes No problem, you can take it, it's up to you. I don't have much time currently.

Merged in #471


Update WGPU to version 22

Upgrading to WGPU 22.
Needs naga_oil to upgrade first, I've got a fork that compiles but fails tests, so until that's fixed and the crate is officially updated/released this will be blocked.

naga_oil has been updated to wgpu 22 and is now published. Can you update this PR with the new naga_oil version?

get_capabilities() needs a few changes to be kept up to date with new wgpu features/naga capabilities.
PR for that https://github.com/callym/bevy/pull/1


Double Tap to Zoom When NavigationBar is Displayed

Hi there,
When you are viewing an image with the UINavigationBar still displayed, if you double tap the image, instead of zooming in it will cause the background to change to black and then require the user to double tap another time to zoom. Do you know of any simple fix to this issue to make it more like the iOS Photos app behavior?
Thanks again for this great example project!

@inTact700 Thanks for your report. I fixed the problem in this commit ddf8b8a . Please check it.

@masamichiueta That's perfect, thanks for the quick follow-up I appreciate it!


Cartographer 3D with IMU, odometry, and 1 LiDAR

Hi there,
I am looking to use Cartographer 3D with an IMU, odometry, and 1 LiDAR. I am using the "demo_backpack_3d.launch" as a reference. However, I notice that it has 2 different LiDARs. How do I set my launch file and configuration files to match my needs?
Best,
Vai

Hi,

launch file: Have only one remap tag with your incoming topic name
backpack_3d.lua: num_point_clouds = 1, use_odometry = true
backpack_3d.urdf: Remove the unneeded joint, specify your IMU to base_link rotation (the default 0% chance to be correct for you). Same for odometry.

Also, always start experimenting with 2D first and definitely without odometry first. See the tuning guide.

Great! Thank you.
Another question, I am currently building cartographer in a separate workspace outside of my main ROS workspace. What is the convention for this? Where do I put my launch files?
Best,
Vai

Hi,
I have an error when I am setting use_odometry = true. If I use the same bagfile without odometry, there are no errors. The error I am getting is:
[FATAL] [1523991642.691777084,<PHONE_NUMBER>.740793128]: F0417 12:00:42.000000 15592 sensor_bridge.cc:33] Check failed: frame_id[0] != '/' ('/' vs. '/') The frame_id /camera should not start with a /. See 1.7 in http://wiki.ros.org/tf2/Migration.

Thank you! I solved this issue.
To continue this conversation, the results of including an odometry topic in Cartographer makes it significantly worse. In fact, the resulting path is even worse than just the odometry frame.
This is an image of only the odometry topic. As you can see, there is some error on the turns. The result should also be a closed loop.

Here is a result of the path using Cartographer without odometry. This trajectory seems much more accurate, but the loop closure error is approx 3.5 meters.

Here is the result of using Cartographer with the above odometry. The results are clearly much worse. The position estimate drifts a lot even before the robot actually starts moving. What could be the possible errors?

I believe this is expected as long as your input data issues https://github.com/googlecartographer/cartographer_ros/issues/831 are unresolved.

I fixed that issue by changing the odometry_sampling_ratio to 0.1 -- I no longer have that problem.

hi,everyone！
I would like to ask if I only have a 3D laser radar, how do I set up my launch file and lua file?
thanks.

@wxt-github, please see my previous answer: https://github.com/googlecartographer/cartographer_ros/issues/828#issuecomment-381888864

Thanks for your reply. I'm sorry to reply to you now. I've been trying to modify these files as you said these days, but there are still problems. The more mistakes I make, the more I am modifying them. Do you have a few documents that have been modified to give me a reference? Thank you very much! @gaschler

@vaibhavviswanathan @gaschler
Hi, when I am using Cartographer 3D with an IMU and one LiDAR.
Here is my launch file, the topic name of LiDAR data in my bag is "velodyne_points" and "/imu/data" for IMU data
/home/albert/Desktop/lua.png
Here is the udrf file
/home/albert/Desktop/urdf.png
In lua file, I just change num_point_clouds = 1.
The problem I meet now is below
/home/albert/Pictures/scr.png
Is there anything I miss?
Best
Albert

can you share the configuration files like urdf file? Because I meet some mistakes when i run cartographer with odometry, but it is work with IMU. Thanks.

closing as inactive


Downloading firmware returns 401

Device fails to download update. From logs:
Jul 26 15:29:46 GARDENA-08affc swupdate.sh[579]: > GET /api/download/1 HTTP/1.1
Jul 26 15:29:46 GARDENA-08affc swupdate.sh[579]: Host: <IP_ADDRESS>
Jul 26 15:29:46 GARDENA-08affc swupdate.sh[579]: User-Agent: libcurl-agent/1.0
Jul 26 15:29:46 GARDENA-08affc swupdate.sh[579]: Content-Type: application/octet-stream
Jul 26 15:29:46 GARDENA-08affc swupdate.sh[579]: Accept: application/octet-stream
Jul 26 15:29:46 GARDENA-08affc swupdate.sh[579]:
Jul 26 15:29:46 GARDENA-08affc swupdate.sh[579]: < HTTP/1.1 401 Unauthorized

Fixed in #32


Update Dockerfile with pre-commit fix

Unable to run this with devpod on vscodium, fixed with changing pre-commit install instructions, now tested and working.
[12:05:24] debug Using docker command 'docker'
[12:05:24] debug execute inject script
[12:05:24] debug Received line after pong: done
[12:05:24] debug done inject
[12:05:24] debug done injecting
[12:05:24] debug Done InjectAgentAndExecute
[12:05:24] debug done exec
[12:05:25] debug Successfully connected to container [12:05:25] debug Run outer container tunnel
[12:05:25] debug Execute SSH server command: bash -c '/usr/local/bin/devpod' helper ssh-server --track-activity --stdio --workdir '/workspaces/terraform-modules-library' --debug [12:05:25] debug Execute SSH server command: bash -c cat /var/run/devpod/result.json [12:05:25] debug Successfully parsed result at /var/run/devpod/result.json [12:05:25] debug Forward port localhost:10800:localhost:10800 [12:05:25] debug Execute SSH server command: bash -c '/usr/local/bin/devpod' agent container credentials-server --user 'ubuntu' --configure-git-helper --configure-docker-helper --forward-ports --debug [12:05:25] debug Received ping from agent
[12:05:25] debug Start credentials server
[12:05:25] debug Start watching & forwarding open ports [12:05:25] debug Wrote docker credentials helper to /usr/local/bin/docker-credential-devpod [12:05:25] debug Credentials server started on port 12049... [12:05:25] debug New connection on localhost:10800 (Total: 1) [12:05:25] debug Accepted forward: localhost:10800

Error was
Run command pre-commit-install: pre-commit install... bash: line 1: pre-commit: command not found post create commands: failed to run: pre-commit install, error: exit status 127 devcontainer up: run agent command: Process exited with status 1 run agent command: Process exited with status 1

Thank you @bitbucket90 for your contribution, I appreciate it! Merged!


Git Proxy - Handle UTF-8 output in all environments

Python auto-detects the default string encoding based on several environment variables:
LANG=C.UTF-8
LC_CTYPE=en_US.UTF-8

These are set by default in shells Devbox, and thus the encoding used by default is UTF-8. However, when invoking the git-shim from a shell where these variables are not set or as a subprocess (like from the test-shard CLI) - the default encoding is ASCII. This results in the following error whenever UTF-8 is present in the output of any command (usually a diff)
UnicodeEncodeError: 'ascii' codec can't encode characters in position <x>-<y>: ordinal not in range(128)

This PR fixes the issue by explicitly setting the encoding of the printed output to UTF-8 - so we don't need to rely on it being properly set in the environment or by callers.

how urgent is this? can we merge this after we move devbox to universe?


Add CDNJS version badge in README.md

The badge shows the latest lib version on CDNJS and gives a link of it.

Codecov Report

Merging #167 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #167   +/-   ##
=======================================
  Coverage   98.54%   98.54%
=======================================
  Files           1        1
  Lines         891      891
  Branches      159      159
=======================================
  Hits          878      878
  Misses         13       13

Continue to review full report at Codecov.

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

I'm new at java please help me!! In know some of codes lik Hello world l, string etc.


changes: limit the number of active children lookups

This PR addresses  #22 and #27. The analysis and investigation as well as suggestion nudged by @fergald.
The idea is to limit the number of lookups as previously noted in the TODO.

Instead of waiting for each of $GDRIVE_PROCESSES to finish before the next one, is there go threading library that can be used? I'm not familiar with go at all.

@ikwyl6 @fergald ping.

Thanks @fergald plus everyone else.

Not sure what you're pinging me for BTW but I took a look at the change and
left a comment. If there was anything, let me know.

was just giving you notice of the PR and patch as I am off for a couple of hours in case you needed to use drive to make your backups, please check out master.

FYI regarding pings - I'm "watching" the whole github project so I get all emails anyways.


sbtVersion

(See the guidelines for contributing, linked above)
steps
run: sbt sbtVersion
problem
Console output: [info] 0.13.15
expectation
[info] 1.0.0
notes
sbt version: insert sbt version

What gets printed when you run sbt about in a completely empty directory?
Do you have project/build.properties for your current build?

Here's my output running sbt sbtVersion in fresh /tmp/what:
$ sbt sbtVersion
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512M; support was removed in 8.0
[warn] No sbt.version set in project/build.properties, base directory: /tmp/what
[info] Set current project to what (in build file:/private/tmp/what/)
[info] 1.0.0

What gets printed when you run sbt about in a completely empty directory?
sbt about:
"C:\Users\yuriys.sbt\preloaded\org.scala-sbt\sbt"1.0.0"\jars\sbt.jar"
[warn] Executing in batch mode.
[warn]   For better performance, hit [ENTER] to switch to interactive mode, or
[warn]   consider launching sbt without any commands, or explicitly passing 'shell'
[info] Loading project definition from C:\Users\yuriys\project
[info] Set current project to yuriys (in build file:/C:/Users/yuriys/)
[info] This is sbt 0.13.15
[info] The current project is {file:/C:/Users/yuriys/}yuriys 0.1-SNAPSHOT
[info] The current project is built against Scala 2.10.6
[info] Available Plugins: sbt.plugins.IvyPlugin, sbt.plugins.JvmPlugin, sbt.plugins.CorePlugin, sbt.plugins.JUnitXmlReportPlugin, sbt.plugins.Giter8TemplatePlugin
[info] sbt, sbt plugins, and build definitions are using Scala 2.10.6

Do you have project/build.properties for your current build?
No, I run from work directory

Fixed. It was my fault.

ok. So I somehow messed up the Windows installer, which has happened before too:

https://github.com/sbt/sbt/issues/2181
https://github.com/sbt/sbt/issues/2473

Fixed. It was my fault.

ok.


update ru translation

Hi @AleksandrSokolov! Thank you, this is a lot of work. As i am just about to release 1.0.0, i am reluctant to merge in large new functionality - i would like to merge this post 1.0.0. However, if you want to submit a smaller pull request with only the translation work, i can certainly merge that in for 1.0.0

@glutamate, Thank you for appreciating my work.  Let's do as you suggesting. I'll prepare smaller pull request for ru translation.  Other work we'll integrate later. REST API for DML (data in tables) is more or less ready. DDL API needs to be discussed/finished. Also I need to prepare tests for apis.
You also need to decide on endpoints for apis.

hi @AleksandrSokolov did you have a stand-alone PR with the translation changes? or i can merge in your single ru.json file from here

Hi @glutamate Please merge single ru.json. After v1.0 I'll return with other things.

Some comments @AleksandrSokolov :

Instead of developing new APIs, please just modify server/routes/api.js - its easier to track changes that way and we shouldn't have several parallel APIs. You can just copy your restapi_tables_dml over api.js, you only need to change one require path to utils

Having limit and offset in the API is great, we definitely need that.

IDs are not always Integers! IDs can also be UUIDs. its best to use the primary keys's type's read method to validate. This affects offset and the id of the new GET route. I think we should have more tests for using the API with UUIDs

Similarly, let's add the new methods into restapi_tables_ddl instead of creating a new API


add date to zimfw info [feature request]

Current zimfw info shows: zimfw version: 1.3.2 (previous commit is ccace0c) , is it possible to append the release date after the commit id? for instance zimfw version: 1.3.2 (previous commit is ccace0c on Aug 1, 2020)
just a thought, thanks

Hi @cattyhouse. Good idea, I'll include the compilation date in next releases.
Merry Christmas!


No HOME environment variable on Windows

The code that sets the rational-config-path in early-init.elassumes that there is a HOME-variable. But on Windows this is not true, there is no variable HOME by default.
Emacs looks for it's config in APPDATA and the user home is in USERPROFILE.
Now one can set the environment variable HOME to USERPROFILE, which is also recommended.
So on Windows the early-init should look for a HOME variable and use that. If it doesn't exist it should use APPDATA.
I'm not sure why rational-emacs has to be installed in specific locations and not just use the user-emacs-directory. But that may be by design.

Great information, thanks! Would you make the patch for the fix? I can do it if that is more convenient.
The separate directories are to make things easier for git locations. The eventual user could clone this repo as their emacs config and then in a separate folder clone their personal customization. There may be other ways to handle the same thing, git submodules comes to mind, but that maybe also be suboptimal in other ways. I'll defer to @daviwil  on any further explanation/reasoning.

It would be nice if you do it, I realize I don't know exactly to handle unset variables at the moment.

It would be nice if you do it, I realize I don't know exactly to handle unset variables at the moment.

PR submitted. In the way of an explanation, emacs-lisp (like other lisps) considers nil to be false. Thus (getenv "HOME") will be considered false if it returns nil. So (if (getenv "APPDATA") ...) will return t if there is a value there or nil if not. If it is present, we use it, if it isn't we default to the "HOME" environment variable. Hopefully this covers all relevant operating systems. I also check to see if the system-type is "windows-nt" as the "APPDATA" environment variable only exists on Windows (not Mac or Linux each of which uses "HOME" - which I'm sure you already knew, just trying to be obvious for posterity sake :-) )

@jeffbowman I tried this but now it will only look inAPPDATA and not in HOME as I have set in Windows. I realize that I may have a more complex setup so this might be an edge case.
To me Emacs should first look for config in HOME and if that is set it should continue setting the variable. Only if that doesn't exist it should look for config in APPDATA .
But it's to late for me right now to make any conclusions but I will give it a try tomorrow.

Ah... I missed that nuance... I have updated the logic to check for HOME first, then APPDATA if on a MS Windows machine, and in the worst case just go up a directory from the init.el file.
I'm interested in your feedback. Thanks for testing!

@jeffbowman So it appears that I lied to you. There is in fact a HOME variable by default in Emacs on Windows. I tried rational-emacs on a new fresh installation (Windows Sandbox) and I found out that Emacs has its own HOME variable. That points to C:\Users\<UserName>\AppData\Roaming.
But you can change this by adding the environment value HOME and Emacs will respect that.
When I tried rational-emacs on the fresh Windows it worked as expected, and that surprised me. So I checked the manual. And it states this quite clearly. https://www.gnu.org/software/emacs/manual/html_node/emacs/Windows-HOME.html
So sorry for the confusion, I messed this up. I personally creates an environment variable HOME on my systems so I have forgotten how it worked originally.
So on Windows, by cloning the repository in powershell:
git clone https://github.com/SystemCrafters/rational-emacs $env:AppData/.emacs.d
runemacs.exe

works as intended with rational-emacs.
So there is no need for an exception i early-init.el for Windows. At least regarding to the HOME variable.
Sorry for the confusion.

@sdaaish Thanks for the update. I'll revoke the PR for this then as what we have seems to work.

With the merge of #38 can this be closed?
@sdaaish @daviwil

Yep, thanks @jeffbowman!


[Bug] v0.31.1 Editor icons are missing in ESM build

Reproducible in vscode.dev or in VS Code Desktop?

[X] Not reproducible in vscode.dev or VS Code Desktop

Reproducible in the monaco editor playground?

[X] Not reproducible in the monaco editor playground

Actual Behavior
When building browser-esm-webpack from the samples directory, icons in the editor do not load properly.

In browser-amd-editor, it works fine.
Expected Behavior
Icons should load properly.

This is actually a duplicate of https://github.com/microsoft/monaco-editor/issues/2742.


Fix test running output truncation on async STDIO

For issue https://github.com/mochajs/mocha/issues/333
Note: this does not address the issues with mocha interfaces and other non-test commands, because if we actually waited for the output to get flushed, the default mocha action (running tests) would start to occur. Refactoring needs to happen to fix this.
But this solves the output being cut when the STDIO is async, which is the main use-case.

ping

Yes, sorry.  It's on my list.

It's no problem :) I was just going through all the forks in my account yester to clean them out, haha :D

+1

Thanks


[Issue-26] Customize animations

Introduction
We should make our bottom sheet animations even more customizable than they already are by leveraging the Animation struct that's already in YCoreUI (and used by Y—Snackbar and Y—SideMenu).
Purpose
Fix #26 Use new Animation structure for present / dismiss animations.
Scope

Extend Animation with default values for bottom sheet
Modify Appearance to use Animation instead of separate duration and curve properties
Modify the present and dismiss animators to use the new properties
Update unit tests

Discussion
One thing this allows (which wasn't possible before) is to optionally present bottom sheets using spring animations. We also have the flexibility (should we need it) to have not only different curves but different durations for the present and dismiss animations. The default behavior though is unchanged: animations are 0.3 seconds and .easeIn on present / .easeOut on dismiss.
🎬 Video
(These animations are slowed down by 2x to help them appear better as GIFs)

Regular animation
Spring animation

📈 Coverage
Code
100%

Documentation
100%

@mpospese Also I'm not sure if its just the animated gif but in the spring animation, the background fade seems to be delayed or out of place. It's not smooth as the regular animation. I can put in a jira ticket if we want to keep this improvement in the backlog.

@mpospese Should we update the readme to provide an example of this new functionality?

added. I also remove the source code that had been reproduced in the README (as we had discussed).

@mpospese Also I'm not sure if its just the animated gif but in the spring animation, the background fade seems to be delayed or out of place. It's not smooth as the regular animation. I can put in a jira ticket if we want to keep this improvement in the backlog.

I think it's just the gif. The dimmer animation is on its own curve and unchanged by this change (identical between the two gif's apart from a slightly longer duration in the second one). We could add a ticket if we wanted to add the ability to customize the dimmer animation.


Added info about PM cares fund

With regard to #416 added info of PM cares fund and also added few images in public directory

Similar to #340


Challenge failure metrics

Is your feature request related to a problem? Please describe.
For an as-of-yet unknown reason, we have a Order with two Challenges one of which succeeded and the other failed. We did not note this until ten days later, when we got a warning mail from Let's Encrypt that the certificate would expire in 20 days.
It does not appear that there are any metrics which expose this information so that we would have been able to react on this faster.
Describe the solution you'd like
Some metric on the challenges such that we could alert on the failure. From our perspective, either a counter on the number of failed checks or a gauge of the timestamp when the challenge was issued. The timestamp approach would likely be easier to write alerts with low number of false positives for, since a low number of failures per challenge even when it ultimately succeeds is likely with eg DNS challenges. For example,
certmanager_challenge_issued_timestamp_seconds{name="...", order="...", certificate="..."}<PHONE_NUMBER>
The metric would be removed along with the Challenge object. There will be some metric churn from this, but likely not enough to be problematic compared to the normal Kubernetes pod churn etc.
Describe alternatives you've considered
Currently I can only see this being detected via logs or some script scraping the Kubernetes API for Challenges.
/kind feature

You can achieve this via certificate_expiration_timestamp_seconds?
Our metrics are quite limited we should expand them for sure
/area acme
/priority important-longterm


Use a standard for folder structure

what do you expect for this issue ?
there was an another issue discussing the new folder structure design:
https://github.com/driftyco/ionic-conference-app/issues/98
there were some commits yesterday on implementing the design
https://github.com/driftyco/ionic-conference-app/commit/2be9ca212d74beb82af64982f01ea2f487dc1428

We should go with ionic default

do you mean the app folder outside www ?
https://github.com/driftyco/ionic-conference-app/issues/98 is the new default
the core ionic-cli had already updated to follow this new folder structure

We should use app folder which is good for performance and ease of use.
#98
It has directive folder, there is no such thing in angular2. It's all components.
so, I success

app

components

about

about.js
about.scss
about.html

contact

contact.js
contact.scss
contact.html

providers/services

about

about-provider.js

Placing app folder inside/outside may depends on offline template compiling.

Directives do exist in Angular 2: https://angular.io/docs/ts/latest/api/core/Directive-var.html

Closing this. #98 is how the directory structure will be set by default, any opinions on it can go there. Thanks.


How can I use it with a UITabbarController in Storyboard?

How can I use it with a UITabbarController in Storyboard?
#44 it's not work for me and alse not work in this version.
thanks

#7 it's solved for me
thanks


Update oc_install.robot

temp fix for gcp failure

@tarukumar, okay, wasn't aware that this is just GCP specific; understand. Would be great to check why it behaves differently, though.
Anyway, I still believe that checking whether the dependency operators are installed before actually trying it to install them is still valuable (I suppose it may cause a trouble if the operator is present on the cluster already and we try to install it again - well, at least it was the situation in our case with GCP).
Just to be sure we're on the same page - this PR shouldn't be merged as is, definitely, 'cause it doesn't workaround the issue we saw in the GCP, see my commit I linked in my previous comment.

@tarukumar, okay, wasn't aware that this is just GCP specific; understand. Would be great to check why it behaves differently, though.
Anyway, I still believe that checking whether the dependency operators are installed before actually trying it to install them is still valuable.
Just to be sure we're on the same page - this PR shouldn't be merged as is, definitely, 'cause it doesn't workaround the issue we saw in the GCP, see my commit I linked in my previous comment.

That was intentional to leave that. Also, as i mentioned earlier yes i agree we need to add dependent operator verification and they will come in future not in this pr

Changes in this PR has been merged together in #1069.

That was intentional to leave that. Also, as i mentioned earlier yes i agree we need to add dependent operator verification and they will come in future not in this pr

Intentional to leave that - okay, then I suppose that you were trying to solve a different problem than me which I saw last Friday then.
Regarding the check for dependencies - all right, I probably didn't understand that fully in your previous comment. Okay then.


GUI for skills (Maybe a seperate XSkills mod)?

Describe the solution you'd like
A small, easy GUI, that can be modified (Maybe looks like the Minecraft advancements screen or Vault Hunters skill screen)?

:laughing: This is indeed the direction I'm heading after finishing up the restrictions-based mods. I want to have some sort of AttributeSkills mod for managing RPG-like attributes, a way to configure them at the modpack level, and a way to interact with them at the player/GUI level.

ok 😮💨. I really didn't want to make my own gui when I use this.


UI not loading - Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'goto')

Bug Report
Description
Bug Summary:
UI not loading staying with blank white screen.
Steps to Reproduce:
Install on Win10 standalone - Python 3.10.13, Node 18.16+
Expected Behavior:
Open WebUI starts.
Actual Behavior:
Blank screen. Error in Browser console
Uncaught (in promies) TypeError: Cannot read properties of undefined (reading 'goto')
Environment

Operating System: Windows 10
Browser (if applicable): Chrome 120.0.6099.225, Edge 121.0.2277.112

Reproduction Details
Confirmation:

[x] I have read and followed all the instructions provided in the README.md.
[x] I have reviewed the troubleshooting.md document.
[x] I have included the browser console logs.
[x] I have included the Docker container logs. -- N/A

Logs and Screenshots
Browser Console Logs:

Docker Container Logs:
[Include relevant Docker container logs, if applicable]
Screenshots (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Installation Method
Manual installation. I have two machines one personal and one on corporate network. Identical configuration (Python versions, Node versions, Node package versions). Ollama validated running and reachable on both.
Personal one works, corporate has the issue described here. Corporate has limited internet connectivity.  However transformers have been installed, tested.
Additional Information
Appears to be a SvelteKit promise issue as describe here
https://stackoverflow.com/questions/72186150/why-do-i-get-error-uncaught-in-promise-typeerror-firstnamef-is-null
and here
https://svelte.dev/repl/2b95425c5aec4389bd484cf40a3fd1e5?version=3.48.0
We're failing on the second "await K("/auth")line here, I've never run uvicorn with non-minified debug, would be happy for a pointer to try and learn more.

304's in console I don't see on the personal machine (all 200's there), but possibly unrelated(?).

Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!

Unable to reproduce at all with node v20, if anyone manages to reliably reproduce the issue please let us know!

Thank you, testing now repeated with v21.6.2, same result, will keep digging. Likely to be something to do with our corporate machine configuration, though am struggling to think what ...


layers: Fix command buffer allocation ABA bug (issue #2517)

In core validation layer's DestroyCommandPool API entry function, the
ext layer's API call is executed outside of the lock, and before the
command pool's command buffers are erased from the layer's command
buffer map. That means that between next layer's call and the time the
lock is regained, any other thread can allocate other command buffers.
In particular, it may reuse the memory freed the command, and then the
core validation layer will not insert a new entry in the command buffer
map. So after the lock in regained and the command pool's command
buffers are erased from the map, leaving those allocated with no state,
leading to either crashes or assertions later on. The fix is to move the
release of command buffers before releasing the lock the first, before
calling the next layer's function, such that they will be removed from
the map before any other thread might reuse those addresses.

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

Looking at this now.  The CI failure seems spurious.  Also, if this is a real problem I'll need to update DestroyDescriptorPool similarly.

Fixes #2517


Add emitting of e2e test instance metrics

Issue #, if available:
Description of changes: E2e test results nowadays doesn't provide good observability. This change is aimed to start addressing this issue by adding cloudwatch metrics. It can further allow us to auto cut ticket based on the new e2e test metrics.
Testing (if applicable): manually triggered the e2e test and verified new metrics were emitted correctly
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cherry-pick release-0.19

/lgtm
/approve

/approve


Conclusion: remove pulkitjalan/geoip dev-master

I am getting the following error when running composer update in my project now:
Your requirements could not be resolved to an installable set of packages.
  Problem 1
    - Conclusion: remove pulkitjalan/geoip dev-master
    - Conclusion: remove guzzlehttp/guzzle 6.1.1
    - Conclusion: don't install guzzlehttp/guzzle 5.3.0
    - Conclusion: don't install guzzlehttp/guzzle 6.1.1
    - Installation request for pulkitjalan/geoip dev-master -> satisfiable by pulkitjalan/geoip[dev-master].
    - Installation request for tuurbo/spreedly ~1.5.0 -> satisfiable by tuurbo/spreedly[1.5.0].
    - pulkitjalan/geoip dev-master requires guzzlehttp/guzzle ~6 -> satisfiable by guzzlehttp/guzzle[6.1.1, 6.0.0, 6.0.1, 6.0.2, 6.1.0, 6.1.x-dev].
    - Can only install one of: guzzlehttp/guzzle[6.0.0, 5.2.0].
    - Can only install one of: guzzlehttp/guzzle[6.0.1, 5.2.0].
    - Can only install one of: guzzlehttp/guzzle[6.0.2, 5.2.0].
    - Can only install one of: guzzlehttp/guzzle[6.1.0, 5.2.0].
    - Can only install one of: guzzlehttp/guzzle[6.1.x-dev, 5.2.0].
    - tuurbo/spreedly 1.5.0 requires guzzlehttp/guzzle ~5.2 -> satisfiable by guzzlehttp/guzzle[5.2.0, 5.3.0, 5.3.x-dev].
    - Conclusion: don't install guzzlehttp/guzzle 5.3.x-dev

It used to work fine before.
Why?

tuurbo/spreedly uses guzzle 5 whereas this package uses guzzle 6. Thats your conflict. might be best to fork either this one or tuurbo/spreedly and use the same versions of guzzle.


Add reporter methods for hook start and pass

Hook start and pass events have been absent so far because I couldn't think of a reason why a reporter would want to receive them. However, they are useful if a reporter wants to time hooks, for example. Indeed, we should provide them so that a reporter can get a full picture of the execution.

Coverage increased (+0.7%) to 89.104% when pulling 683697964c46ab81f0b98fac4b5ff674ad1448dd on joebandenburg:hook-start-pass into 4f5baa964ea324550d544c0f49a5d01112d8d898 on cuppa-framework:master.

🚢 it


CLOUD-53134 docker build for cloudbreak-web

@schfeca75 pls review

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


Invalid header in gzip format

We deploy netbox with flux and an OCI repository. flux requires a tar+gzip file to unpack the files correctly: https://fluxcd.io/flux/components/source/ocirepositories/#layer-selector
I have seen that the last 4 version still has tar.gz. However, the current beta versions do not. Can tar.gz be uploaded there as well, please, so that flux can work with it?

Forget it again. I was looking the wrong way.

Thanks for opening this issue @rhizoet.
The OCI registry already follows all requirements by standards.
In fact, I personally use FluxCD as well and everything is working as expected.
Can you please provide the log of the integration?

For sure, here we go:
failed to extract layer contents from artifact: requires gzip-compressed body: gzip: invalid header

Forget it again. I was looking the wrong way.

I'm confused, have you found the problem?

Sorry, I don't have found the problem yet. Do you have a clue, what the error can be?

What are the version of everything?

Netbox chart
FluxCD
Kubernetes

Ok, the problem has been solved. I had mistakenly used OCIRepository instead of a HelmRepository with type: “oci”. As a result, it couldn't pull anything and the error occurred.
Now that I have changed it, the process continues.
Sorry for the false alarm :D


Rework docx parser, add comments to docx

@emanuelschuetze Please make the template pretty ;).
One thing left: The parser cannot handle lists; But this is another PR, because the list handling in ooxml is done in a complex way..

Travis (jshint) failed.

CHANGELOG entry added.


Roll Engine from 68cd4c42b506 to b46b29525cfd (5 revisions)

https://github.com/flutter/engine/compare/68cd4c42b506...b46b29525cfd
2021-01-28<EMAIL_ADDRESS>Roll Skia from b7f5e1b20db1 to ed552f8702ad (8 revisions) (flutter/engine#24006)
2021-01-28<EMAIL_ADDRESS>Roll Dart SDK from a50a89356008 to 3260b2543287 (1 revision) (flutter/engine#24005)
2021-01-28<EMAIL_ADDRESS>Revert "Roll buildroot to 33f05b6c (#23986)" (flutter/engine#24009)
2021-01-28<EMAIL_ADDRESS>Roll buildroot to 33f05b6c (flutter/engine#23986)
2021-01-27<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from flUwG0eOB... to uD1gzvk5P... (flutter/engine#24002)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from flUwG0eOBmOH to uD1gzvk5P8bU
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Commit queue failed; closing this roll.

Commit queue failed; closing this roll.


[FEAT] Remember expand/collapse status of cards

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

I have to click many times to reach a child card.
Describe the solution you'd like
A clear and concise description of what you want to happen.
There is 2 suggestions:

Remember tree status
Add a button like expand/collapse All

Additional context
Add any other context or screenshots about the feature request here.

You may find that this PR helps this problem. It's already been merged to master but no new release has been made since then.


fix: parsing DROP DETACHED to drop statement for alter table

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

22 of 24 (91.67%)  changed or added relevant lines in 2 files are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.007%) to 58.073%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

parser/parser_alter.go
12
14
85.71%

Files with Coverage Reduction
New Missed Lines
%

parser/ast.go
4
53.76%

Totals

Change from base Build<PHONE_NUMBER>:
0.007%

Covered Lines:
5906

Relevant Lines:
10170

💛  - Coveralls


Deploy DRAGEN error using guide

Hi,
I followed the Illumina DRAGEN on AWS Partner Solution Deployment Guide to deploy DRAGEN, but encountered a error during creating stack(DragenStack-ContainerBuild stage).
Some part of error info from codepipeline log file like below

Step 1 : FROM public.ecr.aws/docker/library/centos:centos7.9.2009
114 | centos7.9.2009: Pulling from docker/library/centos
115 | 2d473b07cdd5: Pulling fs layer
116 | 2d473b07cdd5: Verifying Checksum
117 | 2d473b07cdd5: Download complete
118 | 2d473b07cdd5: Pull complete
119 | Digest: sha256:be65f488b7764ad3638f236b7b515b3678369a5124c47b8d32916d6487418ea4
120 | Status: Downloaded newer image for public.ecr.aws/docker/library/centos:centos7.9.2009
121 | ---> eeb6ee3f44bd
122 | Step 2 : RUN rpm -Uvh https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
123 | ---> Running in a9fb22e4266c
124 | curl: (22) The requested URL returned error: 404 Not Found
125 | error: skipping https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - transfer failed
126 | Retrieving https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
127 | The command '/bin/sh -c rpm -Uvh https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm' returned a non-zero code: 1
128 |
129 | [Container] 2024/08/14 23:53:24.507010 Command did not exit successfully docker build --tag ${REPOSITORY_URI}:${TAG} . exit status 1
130 | [Container] 2024/08/14 23:53:24.510321 Phase complete: BUILD State: FAILED
131 | [Container] 2024/08/14 23:53:24.510339 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: docker build --tag ${REPOSITORY_URI}:${TAG} .. Reason: exit status 1
132 | [Container] 2024/08/14 23:53:24.549467 Entering phase POST_BUILD
133 | [Container] 2024/08/14 23:53:24.550509 Running command docker push ${REPOSITORY_URI}:${TAG}
134 | The push refers to a repository [654724916652.dkr.ecr.us-east-1.amazonaws.com/dragen-new-t1-dragenstack-10ln435tg3mi-dockerbucketrepository-p2y6xi7v4qt2-dragen-c4cpmz9xwdp8]
135 | An image does not exist locally with the tag:<PHONE_NUMBER>52.dkr.ecr.us-east-1.amazonaws.com/dragen-new-t1-dragenstack-10ln435tg3mi-dockerbucketrepository-p2y6xi7v4qt2-dragen-c4cpmz9xwdp8
136

I followed the "the Deployment steps" in guide document with default setting. Could you please help to provide some suggestions on this error?
I used AWS Region us-east-1

The container in this error message is based on CentOS 7.
CentOS 7 reached end of life (EOL) on June 30, 2024. Thus the container build will fail without some sort of migration.
According to the maintainer, this asset is on a deprecation path, so I'm not sure how this issue is going to be handled.


It is not marked as "게임중" except for hosts.

this issue is still unresolved, and new players entering the room will still only see the non-host's status as "Ready". i'm sorry if you have a poor understand of Chinese, but if you look at them carefully, you can still see that these are three different states, the two clients on the right side of the picture are all in the game.


Optimize read write lock constructs during translog upload to remote store

Is your feature request related to a problem? Please describe.
While performing OpenSearch Benchmark runs, discovered a potential optimisation that obstructs the add to translog when the translog upload to remote store is ongoing.
Translog add :
https://github.com/opensearch-project/OpenSearch/blob/443cfcaeaa009f82aa544ee7e4b131ffa147a2df/server/src/main/java/org/opensearch/index/translog/Translog.java#L541-L582
RemoteFsTranslog prepareForUpload :
https://github.com/opensearch-project/OpenSearch/blob/443cfcaeaa009f82aa544ee7e4b131ffa147a2df/server/src/main/java/org/opensearch/index/translog/RemoteFsTranslog.java#L239-L251

While performing OpenSearch Benchmark runs, discovered a potential optimisation that obstructs the add to translog when the translog upload to remote store is ongoing.

Can you clarify what the optimization is?

While performing OpenSearch Benchmark runs, discovered a potential optimisation that obstructs the add to translog when the translog upload to remote store is ongoing.

Can you clarify what the optimization is?

Currently the translog upload to remote store is happening within the write lock. I am trying to break it up and move the upload within read lock. #9636 is an attempt to do the same.


Explain Scriptblock GetnewClosure and StrictMode "design"

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
As your bot doesn't allow me to ask a simple follow up question before closing the ticket I probably have to open a new one just to ask this follow up question...
See #20812 for context.
/cc @JamesWTruher

Ok, so breaking the assurance of StrictMode is a feature then? Sounds odd...
The issue is not that it doesn't copy the strictmode setting, but rather that it will cause strictmode to be ignored on invokation time. And it just sounded reasonable to me to have GetNewClosure copy in the strictmode setting.
The alternative is that invoking a scriptblock that had getnewclosure called upon it before will honer strictmode. But that sounded like another can of worms previously because of how it is implemented (it being like a module).
Example code:
PS /> Set-StrictMode -version $PSVersionTable.PSVersion
PS /> $a = { Write-Host "$nonExisting"}
PS /> $a.Invoke()
MethodInvocationException: Exception calling "Invoke" with "0" argument(s): "The variable '$nonExisting' cannot be retrieved because it has not been set."
PS /> $a.GetNewClosure().Invoke()

PS />

As one can see the issue is that the scriptblock appears to have executed successfully even though it should have failed because of the StrictMode.
Expected behavior
StrictMode at least at some point causing the ScritBlock to throw an exception. Either when GetNewClosure is called or when it is Invoked.

Actual behavior
No exception. StrictMode is silently ignored and error going undetected.

Error details
No response
Environment data
.

Visuals
No response

Do not hesitate to read this document so that you increase your level of understanding. The PowerShell team's answer is correct.
https://mdgrs.hashnode.dev/scriptblock-and-sessionstate-in-powershell

Pragmatically speaking:

You cannot enforce strict-mode settings at the time of calling .GetNewClosure(), as only invocation (execution) of the script block will surface any strict-mode violations, given that the runtime conditions aren't knowable ahead of time (e.g., if a global $nonExisting variable happens to exist at invocation time, no strict-mode violation would occur).

The stated design rationale is: The mandate of .GetNewClosure() is solely to capture copies of the local variables - and nothing else.

Changing this behavior now would amount to an unacceptable breaking change.

However, you cold open a feature request for introducing a new .GetNewClosure() overload  - i.e. an opt-in way to support copying the effective strict mode to the dynamic module that underlies the script block returned.

Obviously, there's no guarantee that such a feature will be implemented, but in my estimation it is your only realistic chance to get the behavior you want.

Pragmatically speaking it should just fail on invocation time the same way as it does without GetNewClosure...
(Also there is no global $nonExisting variable in this case, just run the few lines of example code and see for yourself)

Pragmatically speaking, you can continue to be cantankerous, which ensures that you're even less likely to be heard.

Also there is no global $nonExisting variable in this case

Yes, but that is unrelated to the point I made.

I'd like to apologize. It wasn't my intent to be cantankerous. I'm just a little bit annoyed by how the process and interaction within these tickets changed recently. Esp. the bot closing unresolved tickets and the process in itself having become "suboptimal". Or specifically in this case the bot closing the initial ticket before it was actually fully addressed. It kinda felt like bug reports aren't taken seriously anymore...
The initial ticket was closed by saying that a suggested alternative implementation that would address the issue is not going to change as it is "by design" and then also marking the ticket as "resolved" even though it wasn't, just felt kinda condescending. However it probably was not that productive to let the emotions write the follow up ticket...
Coming back to the topic.

Yes, but that is unrelated to the point I made.

Ok, but what did you mean with your very first point then? I understood it the lines of "the .Invoke() already causes an exception", but that's not the case and that's exactly the issue.
(The part ".GetNewClosure should throw an exception with strict mode" was just a crude hacky workaround for the feedback of it not being possible to throw an exception when calling .Invoke, as the new ScriptBlock will be considered similar like a module and modules are treated special in regards to strict mode in order to "protect" libraries.)

Thank you, @agowa - I appreciate your being accountable.
Speaking merely as a fellow user - who just happens to have been around for many years - I empathize with getting frustrated with closure of issues and/or lack of / curt feedback - the recently introduced bot action to auto-close issue certainly doesn't help, and - as of this writing - 428 of my own issues have fallen victim to this.
Unquestionably, this state of affairs is deplorable.
That said, in any given case, it is worth focusing on a productive way forward, which I've tried to guide you toward here.

Ok, but what did you mean with your very first point then? I understood it the lines of "the .Invoke() already causes an exception"

No, my point was that PowerShell's dynamic scoping (for better or - arguably - worse) makes it fundamentally impossible to statically reason about the runtime behavior of a given piece of code.
Therefore, it is categorically impossible to enforce the strict mode currently in effect on a script block at the time .GetNewClosure() is called.
Yes, you could argue that the implementation detail of using dynamic modules to implement closures has unwanted side effects / does not exhibit the behavior you expect, but, as argued in my previous comment, the only sensibly way to change that now - without breaking existing code - is by way of an opt-in mechanism - hence my suggestion to create a feature request (which may or may not see the light of day - that is just a fact of life).

I was in the discussion and for what it's worth I also agree that "by design" feels incorrect. The logic was that its design was purely to capture locals, which is technically true but I think it's way more likely they just weren't thinking about strict mode.
That said, I was arguing for wontfix so the result is the same and thus I didn't fight much. The change would be risky, and tbh it's one in a long list of inconsistencies with strict mode. Separate dialects (like strict mode) are notoriously difficult to maintain, especially when the dialect is less frequently used. My personal opinion is that strict mode was a mistake, a good example of why dialects are not ideal, and that we should not put more work into it.
I know it can be frustrating to get a negative response to a suggestion, especially when it doesn't appear to make sense. It's worth noting however that even for that response, there was 4-8 people on a call talking for at least 15 minutes debating the merits. We don't do a good enough job conveying the amount of effort that went into a decision, but it is a lot more than it appears.

Tbh, strict mode should have been the default state, and the mistake was not making it the default state. Same for allowing automatic module imports for non unique function names (as well as encouraging AGAINST explicit imports declarations). However that ship is sailed.
A way to fix this issue without breaking existing code would by to bump the strict mode version and only then enforce it when Invoking "getnewclosure"-ed script blocks. That way it would throw an exception where expected, not break existing code, but probably cause some ugly code within the underlying ".Invoke" function within C# code to actually know and check for the strict mode and "on the fly" modify the strict mode within the provided script block, but not modules.
Also @SeeminglyScience just to clarify I wasn't "frustrating to get a negative response", that is fine. The issue was within the communication itself (and there in particular with the "auto close as resolved" without having a final answer through the bot). As the one in the original ticket left too many things open for interpretation (like if you actually talked about the entire problem or just "jep, GetnewClosure not including strict mode works as intended, and not noticing that it also hides the exception"). But anyway, thanks for taking time to explain this in more details. However, as "just wontfix" doesn't help anyone, can we at least settle at "acknowledged limitation that needs to be added to the docs" or something?

@agowa, documenting the behavior sounds like a good idea:

The SDK docs are notoriously terse - definitely in this case - because they are auto-generated from comments in the source code.

Thus, to add details would require a PR here.
Not sure what the policies are around that.

A bit more detail can be found in chapter 11 of the PowerShell language spec (which hasn't been updated since v3):

The Open a documentation issue link at the bottom of the page allows you to directly create an issue in the docs repo.
Again, I'm not sure if there are policies around updating the - clearly outdated - spec.


"Extract to function" breaks code with yield

Bug Report
🔎 Search Terms
generator, extract to function
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about generators

⏯ Playground Link
code before the code action
Prints '3'
code after the code action for "Extract to function in global scope"
Prints 'Object { value: 4, done: false }'
💻 Code
Before using the code action:
function* main(): Generator<unknown, void, number> {
    /* region start */
    const x = yield 3;
    const y = yield 4;
    /* region start */

    console.log(x + y);

}

const gen = main();
gen.next()
gen.next(1);
gen.next(2);

Prints '3'
After using the code action:
function* main(): Generator<unknown, void, number> {
    /* region start */
    const { x, y } = yield* newFunction();
    /* region start */

    console.log(x + y);

}

const gen = main();
gen.next();
gen.next(1);
gen.next(2);
function* newFunction() {
    const x = yield 3;
    const y = yield 4;
    return { x, y };
}

Nothing is printed
🙁 Actual behavior
Using the "extract to function" code action on code with generators produces code that does something completely different.
🙂 Expected behavior
Using the "extract to function" code action on code with generators either produces no results or does not change the meaning of the code for unsubtle examples.
I understand that many refactors are not meaning-preserving in general, but this refactor is such that I couldn't find any examples where it does what I expected for code where the area-to-refactor contains yield.

oops! I mis-read. Sorry about that


archway new - fails because of global git credentials

Perhaps it would be better to remove git commit dependencie. For example I do not store global creds and setup It manually (with scripts) for each independent project.
Switched to a new branch 'main'

*** Please tell me who you are.

Run

  git config --global user.email<EMAIL_ADDRESS>  git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: unable to auto-detect email address (got 'user@hp.(none)')
Failed to create project
Process exited with code 128

I think we'll leave it in, but maybe give an option to disable git when creating a project. Something like 'archway new --no-git`

I think we'll leave it in, but maybe give an option to disable git when creating a project. Something like archway new --no-git

mb it's event better to check if smth undet git config --global user.name/email before using thie option?
or use --git option instead of --no-git

The fix for this issue is tracked on #54.


Disallow inferred equivalencies when reasoning.

Make ROBOT fail when the reasoner finds inferred equivalent classes.
As recommended by Chris Mungall (rationale) and NicoMatentzoglu on Slack.

Not sure why the Travis CI check was not even triggered on this PR… But all checks passed on my machine, so I am going to have a leap of faith, assume everything’s fine, and merge anyway.

Yeah, not sure why this happens - somtimes making a small inconsequential change (e.g. deleting a line at the end of a file or something) to add a new commit can trigger it to run, but sometimes not...
The post-merge build has passed anyway, so all good:
https://app.travis-ci.com/github/FlyBase/drosophila-anatomy-developmental-ontology/builds/242008502


Use structs for bit flags in status variables

To enhance code clarity, I think it will be a good idea to use bitfield structs for the status flag variables (e.g. global_0x8e). For example, instead of if(global_0x8e & (1 << 4)), do if(global_0x8e.erase_full). This communicates meaning much better.
An attempt was already made in the code to do this, but unfortunately it had the side effect of increasing the compiled code size due to lack of optimisation by SDCC. Currently, this is not used by default, and is restricted by a #define.
To give an example of the non-optimal code, an if-test on global_0x8e & (1 << 4)) is compiled to:
ldw	x, #_global_0x8e+0
ld	a, (x)
swap	a
and	a, #0x01
jreq	00136$

This can be more compactly written as:
btjf _global_0x8e, #4, 00136$

This problem can be solved by formulating some custom peephole optimiser definitions for SDCC. For instance, the above example could be handled by a rule such as this:
replace restart {
	ldw	x, #(%1 + %3)
	ld	a, (x)
	swap	a
	and	a, #0x01
	jreq	%2
} by {
	btjf	%1+%3, #4, %2
} if notUsed('a' 'x' 'n' 'z')

(Note that multiple arguments to notUsed() are an upcoming feature in SDCC 4.1.0, so for use with earlier versions, it will need to be changed to multiple instances of notUsed(), one per argument.)

Hmm, a spanner in the works is that SDCC sometimes uses different formatting for the emitted assembly instructions.
Sometimes it is ldw x, #_variable+0, and sometimes it is ldw x, #(_variable + 0). Note the added parentheses and spacing! Under what circumstances each variant is emitted by the compiler is yet to be determined.
It may require a duplicate set of rules to handle both cases. :(

Feature request for more homogeneous assembly code formatting filed: https://sourceforge.net/p/sdcc/feature-requests/728/

Another example along the same lines, where the code for a conditional operation involving a bitfield could be smaller, is for busy/polling loops. For instance, when a register is being polled for completion of an operation, like so:
while(!(FLASH_IAPSR & (1 << FLASH_IAPSR_EOP)));

This currently compiles to the following assembly code:
00101$:
    ld a, 0x505f
    bcp a, #0x04
    jreq 00101$

This could be replaced with the following, which is 2 bytes smaller (7 vs. 5) and one cycle quicker (3/4 vs. 2/3, depending on if jump taken):
00101$:
    btjf 0x505f, #2, 00101$

A custom peephole optimizer rule could also be formulated to make this optimisation.


Fix brightness/animation_speed and Add LED functions to FN layer

This PR fixes next_brightness and next_animation_speed being switched around and adds LED functions to the FN layer where they would be in the stock firmware
I like the idea of having a new layer for LED and be able to jump to themes directly but was confused by FN+R/T/Y/U not working initially, I hope this helps more people try the firmware as drop-in replacement

Oh thanks, this is looking useful!
The LedOn Action means something slightly different so far, I think on the original FW it turns the LED chip on automatically when you try and talk to it.
The separate layer was mainly for initial development, much easier with just a toggle so I didn't have to keep holding down the FN key.

Thanks for the feedback!
I did indeed consider that the LedOn function does not quite behave like the original firmware
I will work towards a LedToggle function instead to combine LedOn and LedOff
The original firmware does indeed turn on the LEDs to the last used theme when pressing FN+R, you currently have to switch to the next theme to get LEDs to turn on in this firmware
I've tried sending [0, 0, 0] over serial after LedOn but that does not seem to do the trick, I'm open to suggestions otheriwse I'll try some things until I get the ST-link debugger

I've tried sending [0, 0, 0] over serial after LedOn but that does not seem to do the trick, I'm open to suggestions otheriwse I'll try some things until I get the ST-link debugger

I had the impression that there's no debugging without ST-link & OpenOCD. Could you add your development setup to a CONTRIBUTING.md file or the README? Thanks!

I'm moreso doing trial and error than any actual debugging unfortunately @hdhoang 😅
Your contributions to README actually helped me set up the environment to compile so I have you to thank for that 👍
The only thing that confused me was having to add -2018-03-02 but your PR to fix travis quickly explained that


Uppercase/lowercase/numberic etc, for "at least 1" char

[X] I have looked at the documentation here first?
[X] I have looked at the examples provided that may showcase my question here?

Package version eg. v9, v10:
v10
Issue, Question or Enhancement:
For certain validation, such as "uppercase", "numeric", etc, Is there a way to specify that a given string only needs to contain ONE of these types, instead of ALL.
Code sample, to showcase or reproduce:
// Of course the below doesn't work. Just an example of what I was looking for.
// I can of course write custom validator funcs, just wondering if this if possible without custom funcs.

type NewUser struct {
	Username string `json:"username" binding:"required,alphanum"`
	Password string `json:"password" binding:"required,gt=12,uppercase=oneof,lowercase=oneof,numeric=oneof"`
	Email    string `json:"email" binding:"required,email"`
}

// Or maybe:
type NewUser struct {
	Username string `json:"username" binding:"required,alphanum"`
	Password string `json:"password" binding:"required,gt=12,oneof=uppercase&lowercase&numeric"`
	Email    string `json:"email" binding:"required,email"`
}

In this case, the string "Password1234" would be valid, but "PASSWORD1234" would not.

have you tried this? based on  v10.20.0
Password string `json:"password" validate:"required,gt=12,containsany=uppercase,containsany=lowercase,containsany=numeric"`


Slice.Tools JSON error

I am getting this error whenever I get a redefinition error in a Slice file:
    /Users/bernard/builds/icerpc-csharp/tools/IceRpc.Slice.Tools/IceRpc.Slice.Tools.targets(60,5): error : Error parsing JSON: 'F' is an invalid start of a value. LineNumber: 0 | BytePositionInLine: 0.. JSON content: Failed: Compilation failed with 3 error(s)

This is due to the compiler emitting non JSON diagnostics:
{"message":"redefinition of 'Locator'","severity":"error","span":{"start":{"row":20,"col":11},"end":{"row":20,"col":18},"file":"slice\\Ice\\Locator.slice"},"notes":[{"message":"'Locator' was previously defined here","span":{"start":{"row":14,"col":11},"end":{"row":14,"col":18},"file":"slice\\Ice\\Locator.slice"}}],"error_code":"E012"}
Failed: Compilation failed with 1 error(s)

It used to be (I think) that JSON output was emitted to stdout and the filed summary was sent to stderr. IIRC rust does something similar. I thought that we used to only read from stdout, or at least not emit errors if JSON unmarshaling failed.

No quite correct.
We used to only emit JSON to STDERR for error messages. But now with --telemetry we also emit telemetry info as JSON formatted data to stdout.
I guess the simple is to ignore this non JSON messages from STDOUT as we did before, and just collect the STDOUT JSON messages that has the expected telemetry data.

that JSON output was emitted to stdout and the filed summary was sent to stderr

It's the other way around with slicec, the Compilation failed with ... message is sent to stdout,
and all the errors are sent to stderr (either as JSON or text).

Another, maybe easier fix is to change slicec-cs to emit it's telemetry to stderr instead.

Seems wrong to emit non error data to stderr

Yeah, I'd rather just ignore non-JSON output in the tools.

Fair enough, I agree it'd be weirder, was just pitching ideas!


[Feature] Disable onDoubleTap on MoveWindow widget

Is it possible disable onDoubleTap method (MoveWindow widget) in the next release?

You could just extend the MoveWindow widget for now and overwrite that behavior until it's added to the lib.


support client connection configuration to provide QPS and burst

Signed-off-by: Amir Alavi<EMAIL_ADDRESS>closes #1027

/lgtm

@a7i thank you for doing this! Based on this PR my understanding is that descheduler's HELM chart has no custom env vars/configs to pass this, as the values are hardcoded
QPS:        50,
Burst:      100,

am I missing something?

@dmitry-mightydevops you are welcome!
It can be set via cmdOptions here
cmdOptions:
  client-connection-qps: 50
  client-connection-burst: 200


Consistent context menu

Many things you find in the context menu when right-clicking on a breakpoint (e.g. this) are main items, so they are in no sub-menu. However "Toggle Breakpoint" and "Toogle Debugging" are sub-menus in the "PHP-Debug" menu.
You should be consistent and move all context menu entries inside of the "PHP-Debug" menu. (My context menu is already incredible large thanks to many packages I installed)

The thought behind this, was that if you are right clicking a breakpoint you've already narrowed your "context" to be pretty specific, so we're trying to guess that you might want to adjust breakpoint conditions, etc. If there is community desire to have this adjusted we can make that change.


Fixed multi file and wildcard args

Before it couldn't handle wildcard args for me

@SinanAkkoyun can you provide an example of inputting wildcards? This change seems to have broken wildcard input for me

Reverting this commit fixes wildcard input for me:
python3 utils/convert_safetensors.py /models/model_name/pytorch*.bin

Interesting. What shell are you using?

Just Linux bash

@SinanAkkoyun any info on how you're using this? I'm still reverting this merge for my use case because I can't convert with wildcards anymore.

@turboderp do you mind reverting this commit? If this was fixing a real issue I can look at a better fix but for now it's frustrating that it broke wildcard support

@bartowski1182 That's odd, for me it works with simply specifying: python3 utils/convert_safetensors.py /models/model_name/pytorch* (I can not try it out now, I do not have access to my machine atm)
It seems as if the PR only breaks for your environment, if that's the case you could simply copy the old util script into another directory and run it there to convert

@SinanAkkoyun is that how you would use it? I can't imagine how it would work with a wildcard from the code, since you just run for file in args.input_files:, that doesn't seem to handle using a wildcard at all but would work with a list of files

Idk how but my PR worked for me, perhaps my shell handled that

I can retry in a couple of weeks when I get access to my machine

Just set a simplified version up on the go, tested the input file arg parsing, works fine for fish and bash (ubuntu 20.04)
with * at the end, with *.bin at the end, all work flawlessly

It also works for me (bash). Previously you'd have to run it like python convert_safetensors.py "*.bin" since otherwise *.bin would be expanded by the shell to a list of files matching the pattern. Adding nargs='+' correctly catches that list and so wildcard matching can be done by the shell.
What happens if you run this?
import argparse
parser = argparse.ArgumentParser()
parser.add_argument("filenames", nargs="+", type=str)
args = parser.parse_args()
print(args.filenames)

I've isolated the problem a bit
If I run the code directly from my terminal, it works
If I run it inside a docker container, it doesn't..
I'm not sure how running from a docker container is making it not work, it doesn't make any sense to behave differently, but now that I know what I'm looking for I should have an easier time either figuring out what's broken or figuring out how to fix this code so that it works in both scenarios

Made a fix for it, seems that docker commands won't expand wildcard files like regular bash does, will now work for both:
https://github.com/turboderp/exllamav2/pull/344


Add the ability to return maps and arrays in json format

This will make possible to retrieve multiple values (e.g. location) in a single lookup and use something like  libvmod_jq to extract individual values and/or format it.

Ground work for this committed in rev 028d0bdd1b73460f17f1a4a75a0d2b50d69ac6f2


server: change MAX_GRPC_SEND_MSG_LEN

Set region size to 256MB may cause grpc msg length bigger than 128M.
@zhangjinpeng1987 @disksing PTAL
Signed-off-by: Cholerae Hu<EMAIL_ADDRESS>

@BusyJay Updated to 4x.

LGTM


[history] fix bug that check equals with previous command

ref https://github.com/cockroachdb/cockroach/issues/6172

I confirm that this patch fixes the problem described in https://github.com/cockroachdb/cockroach/issues/6172.

@knz Thanks!


Corrected API definition

See title.

Do we want to use "program" or "programming"? I've heard the latter more, and it's what Wikipedia says. 🤷♂

Doesn't really matter to me. Just need to be something with program(ming) vs provider.
Not the best indicator, but Google results shows the following:
Application Program Interface: 295,000,000 results
Application Programming Interface: 245,000,000 results

Program it is — we can always tweak it later, too.


Request for visualization code

Dear author, hello! I'm sorry to disturb you, but I would also like to have a copy of the same visualization code. If it's convenient for you, could you please send it to me? my email is<EMAIL_ADDRESS>I'm sorry to bother you.

Hello! Thanks for reaching out. Unfortunately the status of the old visualization code is somewhat in limbo at this point... after offline discussion from #14 we determined that the trained model used for the reconstruction doesn't match the weights for the publicly released model (our working code model was trained with a different seed). So the visualization code plus training code for the reconstructor can be found here (training was relatively quick on a single GPU from what I recall), but may also require some updating as it was built to hook into our working code rather than the public code in this repo. I'll leave the following possible recommendations:
- z = model.get_feature_vector(inp.cuda())*np.sqrt(640)
  Be changed to -> z = model.feature_extractor(inp.cuda())
                -> z = z.view(z.shape[0], 25, -1)*np.sqrt(640)
  The reason is that 'FRN' object has no attribute 'get_feature_vector'

- eval_loader = dataloader.meta_test_dataloader(val_path, way=5, shot=5, pre=True)
  Be changed to -> eval_loader = dataloader.meta_test_dataloader(val_path, way=5, shot=5, pre=False, transform_type=0)

- Try removing the np.sqrt(640) scaling factor on the feature vector above.
  Given that the regenerator code is clearly set up for an older version of the model code,
  there might be a scaling mismatch.
  You might also try multiplying by 640 instead of sqrt(640), for the same reason.

(Requesting that we leave this issue open so that future requests can be directed here)

(Requesting that we leave this issue open so that future requests can be directed here)

Okay, thank you very much for your help!


curriculum: add test in React challenge to detect constructor call

Add a test to check the "MyComponent" constructor's parameters (params) and to check that the super function exists in the constructor.
Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #39301

@Sky020 Thinking of how we are currently giving "hints" (targeted tests) in the new project-based curriculum, the hints (similar to the current tests) will give reminders on syntax.  If a previous step in a project introduces a concept or syntax, then following steps may or may not restate the same information, but the hints would be relied upon as the reminder about the syntax.
Applying the same logic here, in a previous challenge, the user has already been told about adding the super call, so I think it is completely fine to not include it in the description/instructions of this challenge.  Since, the instructions give the helpful hint of "Make sure to call the constructor for your component, too." and the FCC console gives even more hints, I do not think it is necessary to spell things out further.


coords_norect.shape[0] = 0.

ValueError
a must be greater than 0 unless no samples are taken
File "/apdcephfs/private_quincheng/LipSync/AD-NeRF/NeRFs/HeadNeRF/run_nerf.py", line 862, in train
coords_norect.shape[0], size=[norect_num], replace=False)  # (N_rand,)
File "/apdcephfs/private_quincheng/LipSync/AD-NeRF/NeRFs/HeadNeRF/run_nerf.py", line 965, in
train()
I found coords_norect.shape[0] = 0.
How to fix this error?

It's because the face rect covers the entire image. You can set sample_rate = -1 in TorsoNeRF_config.txt to avoid the error.

Do you know what could cause this problem?  Is it my video?

 In this case, setting sample_rate = -1 is ok (meaning uniformly sampling in the whole image), or you can adjust the code to judge such cases.

 In this case, setting sample_rate = -1 is ok (meaning uniformly sampling in the whole image), or you can adjust the code to judge such cases.

Thanks!  That's a good explanation.
In addition, can this code use multi-gpus? I try to train my video on one P40 GPU and it will take about 200 hours. The video is only a few seconds long.

Currently the code does not support multi-gpus. You can decrease the training iterations (e.g. 40000 iterations). Note that the results may be bad for such a short video (we usually use videos of 3-5 mins).

Thanks


Way to not issue a SIGTERM signal on Ctrl+c

I'm using the password input in some parts of my application. All other input mechanisms don't exit the program unless I'm on the main menu. When I make the user write an old or new password, and they hit Ctrl+c, the program ends. The problem with this is a) I don't want it to end, I want it to go to the main menu b) I can't execute some cleanup functions since I use a customized exit fn.
Would be nice to have a way to supres this, as an option. Or maybe there's already an easy enough way to achieve this? Please let me know.

Why was this closed?

This could be done through a custom (global?) callback function that users of the library could set before instantiating any dialog components.

Same problem. Would like the program not to exit when ctrl-c is hit during input.

So, after investigating a little, this is not really an issue with the library. It actually catches the ^C and returns an "Interrupted" error. However, before this can happen, the default SIGINT handler exits the program.
In order to work around this, one has to "disable" the signal handler.
I could not find a "good" way to do this. Below's my awkward solution. Notice the need to first setup the SIGINT handler. ctrlc does not provide a way to change the handler after setting it, and signal_hook does not allow setting the signal handler again if you reset to a default (i.e. if you set an empty handler to avoid exiting the program, then reset to the "default" one later, then you cannot set it again if, e.g., you need a new input prompt).
use anyhow::{Context, Result};
use dialoguer::Input;
use signal_hook::{register, unregister, SigId, SIGINT};
use std::io::ErrorKind;

pub fn prompt(p: &str) -> Result<String> {
    with_sigint_disabled(|| do_prompt(p))
}

static mut SIGINT_HANDLER: Option<SigId> = None;

fn with_sigint_disabled<F, R>(f: F) -> Result<R>
where
    F: Fn() -> Result<R>,
{
    disable_sigint();
    let r = f();
    enable_sigint();
    r
}

pub fn enable_sigint() {
    unsafe {
        if SIGINT_HANDLER.is_none() {
            let signal = register(SIGINT, move || std::process::exit(128 + SIGINT)).unwrap();
            SIGINT_HANDLER = Some(signal);
        }
    }
}

fn disable_sigint() {
    unsafe {
        if let Some(s) = SIGINT_HANDLER {
            unregister(s);
            SIGINT_HANDLER = None;
        }
    }
}

fn do_prompt(p: &str) -> Result<String> {
    Input::new()
        .with_prompt(p)
        .allow_empty(true)
        .validate_with(|x: &String| {
            if x.trim().is_empty() {
                Err(format!("{} cannot be empty", p))
            } else {
                Ok(())
            }
        })
        .interact_text()
        .map(|x| x.trim().to_string())
        .map_err(|e| {
            if e.kind() == ErrorKind::Interrupted {
                println!("");
            }
            e
        })
        .with_context(|| format!("{} could not be read", p))
}

Can you try with https://lib.rs/crates/ctrlc?

I tried that one initially. The issue is that this one only lets you set the handler, but not disable it temporarily.
I just dawned on me that instead of disabling the handler, one could use a global flag, which is checked by the handler in order to decide what to do (e.g quit or nothing...).
Anyhow, not an issue with the library I guess. Just unexpected, given that in other languages this works out of the box.
std::string foo;
std::cin >> foo;

Sort of tangential to this, if I CTRL-C out of a selection, then my cursor is not restored.
Is that something I'd have to handle myself with some of the approaches named above?

Sort of tangential to this, if I CTRL-C out of a selection, then my cursor is not restored.
Is that something I'd have to handle myself with some of the approaches named above?

@felipesere I just had this issue and this is how I restored the terminal:
let term = dialogue::console::Term::stderr();
term.show_cursor()?;

Showing the cursor should hopefully be fixed by #149 issue.

Closing this issue since it is not about this library.