refactor(tasks): separate job for NAPI benchmark

Not a substantive change. This just prevents the other benchmark jobs showing greyed-out "Build NAPI benchmark" steps, and makes the workflow file easier to follow.

#2782  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite

Most of the CI tasks are stuck in "Waiting for status to be reported". Closing and will re-open as another PR to see if that fixes it.


The style is not applied to the elements of the NodeList

Hello!
I noticed that the items in the NodeList cannot use my own graphical presentation style.
For example, I'm using a dark theme, but the items in this list remain white and it looks pretty unreadable.

I'll add a property for this.

Nice! Thanks for the reply and support of the library!


[Bug] Add prefixes to contentlayer's internal reserved fields

I'm migrating long documents to contentlayer and I find that contentlayer takes up part of the type field and doesn't seem to override this default behavior

Would like to be able to configure a perfix to internally occupied fields to allow externalcontents to migrate without impact

I found the typeFieldName configuration, but it doesn't seem to take effect

I found the typeFieldName configuration, thanks, i will close this


[FLINK-6476] - Table environment register row data stream

Thanks for contributing to Apache Flink. Before you open your pull request, please take the following check list into consideration.
If your changes take all of the items into account, feel free to open your pull request. For more information and/or questions please refer to the How To Contribute guide.
In addition to going through the list, please provide a meaningful description of your changes.

[ x] General

The pull request references the related JIRA issue ("[FLINK-XXX] Jira title text")
The pull request addresses only one issue
Each commit in the PR has a meaningful commit message (including the JIRA id)

[x ] Documentation

Documentation has been added for new functionality
Old documentation affected by the pull request has been updated
JavaDoc for public methods has been added

[x ] Tests & Build

Functionality added by the pull request is covered by tests
mvn clean verify has been executed successfully locally or a Travis build has passed

@fhueske
Please have a look. I inserted tests in scala and java to check the registration of the stream.
For scala - it seemed to work directly if the implicit value is set (i did not know to test this before opening the JIRA).
For java - i have added the needed support in TableEnvironment.
it is not much...i hope i did not miss anything

i will close this PR to push one with only one commit


ControlNeXt-SDXL Inference HTTPError

Hello,
Thank you for providing this work and code.
I was trying to run ControlNeXt-SDXL inference for anime_canny with the provided command.
bash examples/anime_canny/run.sh
I believe I downloaded the pretrained .safetensors weights correctly, and installed libraries correctly, but i got the below error.
loading controlnet from pretrained/anime_canny/controlnet.safetensors
/home/mserna/install/anaconda3/envs/control/lib/python3.8/site-packages/torch/cuda/__init__.py:654: UserWarning: Can't initialize NVML
  warnings.warn("Can't initialize NVML")
controlnext:
  number of parameters: 3526400
  dtype: torch.float32
loading unet from Lykon/AAM_XL_AnimeMix
Traceback (most recent call last):
  File "/home/mserna/install/anaconda3/envs/control/lib/python3.8/site-packages/huggingface_hub/utils/_errors.py", line 304, in hf_raise_for_status
    response.raise_for_status()
  File "/home/mserna/install/anaconda3/envs/control/lib/python3.8/site-packages/requests/models.py", line 1024, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://huggingface.co/Lykon/AAM_XL_AnimeMix/resolve/main/unet/diffusion_pytorch_model.fp16.pt

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "run_controlnext.py", line 306, in <module>
    log_validation(args)
  File "run_controlnext.py", line 14, in log_validation
    pipeline = tools.get_pipeline(
  File "/home/mserna/projects/ControlNeXt-main/ControlNeXt-SDXL/utils/tools.py", line 64, in get_pipeline
    unet_file = hf_hub_download(
  File "/home/mserna/install/anaconda3/envs/control/lib/python3.8/site-packages/huggingface_hub/utils/_deprecation.py", line 101, in inner_f
    return f(*args, **kwargs)
  File "/home/mserna/install/anaconda3/envs/control/lib/python3.8/site-packages/huggingface_hub/utils/_validators.py", line 114, in _inner_fn
    return fn(*args, **kwargs)
  File "/home/mserna/install/anaconda3/envs/control/lib/python3.8/site-packages/huggingface_hub/file_download.py", line 1240, in hf_hub_download
    return _hf_hub_download_to_cache_dir(
  File "/home/mserna/install/anaconda3/envs/control/lib/python3.8/site-packages/huggingface_hub/file_download.py", line 1303, in _hf_hub_download_to_cache_dir
    (url_to_download, etag, commit_hash, expected_size, head_call_error) = _get_metadata_or_catch_error(
  File "/home/mserna/install/anaconda3/envs/control/lib/python3.8/site-packages/huggingface_hub/file_download.py", line 1751, in _get_metadata_or_catch_error
    metadata = get_hf_file_metadata(
  File "/home/mserna/install/anaconda3/envs/control/lib/python3.8/site-packages/huggingface_hub/utils/_validators.py", line 114, in _inner_fn
    return fn(*args, **kwargs)
  File "/home/mserna/install/anaconda3/envs/control/lib/python3.8/site-packages/huggingface_hub/file_download.py", line 1673, in get_hf_file_metadata
    r = _request_wrapper(
  File "/home/mserna/install/anaconda3/envs/control/lib/python3.8/site-packages/huggingface_hub/file_download.py", line 376, in _request_wrapper
    response = _request_wrapper(
  File "/home/mserna/install/anaconda3/envs/control/lib/python3.8/site-packages/huggingface_hub/file_download.py", line 400, in _request_wrapper
    hf_raise_for_status(response)
  File "/home/mserna/install/anaconda3/envs/control/lib/python3.8/site-packages/huggingface_hub/utils/_errors.py", line 315, in hf_raise_for_status
    raise EntryNotFoundError(message, response) from e
huggingface_hub.utils._errors.EntryNotFoundError: 404 Client Error. (Request ID: Root=1-66c7c8a4-46c442243f4c43af614a7c98;923cfa71-a0e5-469b-8f9f-04c3059bccf8)

Entry Not Found for url: https://huggingface.co/Lykon/AAM_XL_AnimeMix/resolve/main/unet/diffusion_pytorch_model.fp16.pt.

Not sure if some line in the code has an outdated path for HuggingFace or something like that. If I should change some line(s), I can happily do so. Thank you!

My bad. The format of unet in repo Lykon/AAM_XL_AnimeMix is safetensors.
So --use_safetensors argument should be included when running run.sh.
Just fixed.

Thank you for the quick response. I now run into key errors when loading the state_dict for I think UNet2DConditionModel.
The error message when running run.sh is below.
loading controlnet from pretrained/anime_canny/controlnet.safetensors
/home/mserna/install/anaconda3/envs/control/lib/python3.8/site-packages/torch/cuda/__init__.py:654: UserWarning: Can't initialize NVML
  warnings.warn("Can't initialize NVML")
controlnext:
  number of parameters: 3526400
  dtype: torch.float32
loading unet from Lykon/AAM_XL_AnimeMix
Traceback (most recent call last):
  File "run_controlnext.py", line 306, in <module>
    log_validation(args)
  File "run_controlnext.py", line 14, in log_validation
    pipeline = tools.get_pipeline(
  File "/home/mserna/projects/ControlNeXt-main/ControlNeXt-SDXL/utils/tools.py", line 73, in get_pipeline
    unet.load_state_dict(unet_sd, strict=True)
  File "/home/mserna/install/anaconda3/envs/control/lib/python3.8/site-packages/torch/nn/modules/module.py", line 2215, in load_state_dict
    raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
RuntimeError: Error(s) in loading state_dict for UNet2DConditionModel:
        Missing key(s) in state_dict: "conv_in.weight", "conv_in.bias", "time_embedding.linear_1.weight", "time_embedding.linear_1.bias", "time_embedding.linear_2.weight", "time_embedding.linear_2.bias", "add_em
bedding.linear_1.weight", "add_embedding.linear_1.bias",

And so on for many keys (possibly all of them?). I believe I have downloaded the correct safetensor files, but do I need to check again, or do I need to change some lines?
Thank you for your help!

You're right. Loading unet from hf is buggy, so I changed the loading logic and pushed.
By the way, some small bugs in run.sh were fixed.
I hope these bugs doesn't cause too much trouble :D

Thank you for the quick response and fix! This works!


Regex match on receiver query string

Allow for a greedy regex, i.e. backend-crit and backend-warn would both be matched by backend-.*

Closed by #729


build failing due to main.jsbundle.map file in root directory instead of ios

Describe what happened
Caveat: I am not 100% sure if this is an issue with this library, or another part of my build, but wanted to start here.
My expo build is failing on uploading the main.jsbundle.map file to datadog, because that file ends up existing in the root directory of my project, instead of the ios directory. If I manually move the file to the ios directory, the build succeeds. Or, by patching this package with patch-package, I can have this repo specify the SOURCEMAP_FILE to be in the ios directory, which "fixes" the issue.
Steps to reproduce the issue:

expo managed project on expo 48
datadog sourcemap upload using this repo
try building in expo, or run npx expo run:ios --configuration Release locally

Describe what you expected:

I would expect the sourcemap to be created in the same location that the upload attempts to use (and presumably the ios directory, for ios builds)

Additional context

Version of the Expo SDK: 48.0.20
Version of expo-datadog: 48.0.0
Version of @datadog/mobile-react-native: 1.2.1

contents of my patch:
diff --git a/node_modules/expo-datadog/build/plugin/withIosSourcemaps/withIosSourcemaps.js b/node_modules/expo-datadog/build/plugin/withIosSourcemaps/withIosSourcemaps.js
index b739962..25a0eb3 100644
--- a/node_modules/expo-datadog/build/plugin/withIosSourcemaps/withIosSourcemaps.js
+++ b/node_modules/expo-datadog/build/plugin/withIosSourcemaps/withIosSourcemaps.js
@@ -6,7 +6,7 @@
  */
 Object.defineProperty(exports, "__esModule", { value: true });
 const config_plugins_1 = require("@expo/config-plugins");
-const SOURCEMAP_FILE_COMMAND = "export SOURCEMAP_FILE=./main.jsbundle.map";
+const SOURCEMAP_FILE_COMMAND = "export SOURCEMAP_FILE=./ios/main.jsbundle.map";
 const DATADOG_XCODE_COMMAND = `yarn datadog-ci react-native xcode \`\\\"$NODE_BINARY\\\" --print \\\"require('path').dirname(require.resolve('react-native/package.json')) + '/scripts/react-native-xcode.sh'\\\"\``;
 const withIosSourcemaps = (config) => {
     return (0, config_plugins_1.withXcodeProject)(config, async (config) => {
diff --git a/node_modules/expo-datadog/src/plugin/withIosSourcemaps/withIosSourcemaps.ts b/node_modules/expo-datadog/src/plugin/withIosSourcemaps/withIosSourcemaps.ts
index 4202315..4200108 100644
--- a/node_modules/expo-datadog/src/plugin/withIosSourcemaps/withIosSourcemaps.ts
+++ b/node_modules/expo-datadog/src/plugin/withIosSourcemaps/withIosSourcemaps.ts
@@ -7,7 +7,7 @@
 import type { ConfigPlugin } from "@expo/config-plugins";
 import { withXcodeProject } from "@expo/config-plugins";

-const SOURCEMAP_FILE_COMMAND = "export SOURCEMAP_FILE=./main.jsbundle.map";
+const SOURCEMAP_FILE_COMMAND = "export SOURCEMAP_FILE=./ios/main.jsbundle.map";
 const DATADOG_XCODE_COMMAND = `yarn datadog-ci react-native xcode \`\\\"$NODE_BINARY\\\" --print \\\"require('path').dirname(require.resolve('react-native/package.json')) + '/scripts/react-native-xcode.sh'\\\"\``;

 const withIosSourcemaps: ConfigPlugin<void> = (config) => {

I've seen a similar issue in my own project: the expo-datadog xcode script calls datadog-ci, and that script fails because it's looking for a bundlemap in the ./ios directory when it's actually been generated in the root of the project. I've been able to reproduce this by creating a brand new project from scratch with no other plugins except expo-datadog. The minimal example repo is viewable here - but I think you'll need to set up some certificates and mobileprovision etc. to run this, as the bug is only visible when running in a production profile.
However, this repo is slightly different from @sam1463 's set-up, as I'm having this issue in the most recent version of expo-datadog (49.0.0), and I'm running this in EAS locally. I wasn't able to fix this issue with the above patch on the env variable SOURCEMAP_FILE in withIosSourcemaps.js, though. I think this is because the datadog-ci script was looking for the bundle file in ./ios/ios/main.jsbundle.map.
I was able to fix the build in my repo and the example repo by applying the following patch to datadog-ci:
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -175,7 +175,7 @@ class XCodeCommand extends clipanion_1.Command {
         };
         this.getSourcemapsLocation = () => {
             if (process.env.SOURCEMAP_FILE) {
-                return `${process.env.SOURCEMAP_FILE}`;
+                return path_1.join('..', `${process.env.SOURCEMAP_FILE}`);
             }
             if (process.env.EXTRA_PACKAGER_ARGS) {
                 const splitArguments = process.env.EXTRA_PACKAGER_ARGS.split(' ');

...but I'm not planning to open a PR on that repo with this change, heh. I think this is an issue with the way the relative paths are set in the calling expo-datadog script, rather than the datadog-ci or react-native-xcode scripts.

Hi @dprgarner, thanks a lot for providing an example reproducing the error!
I can reproduce it on my end, I am investigating on a fix for expo-datadog and will let you know once it is ready.

Hi @dprgarner @sam1463,
Thank you again for reporting this issue.
I've tested it and it should have been fixed with version 49.0.1 of expo-datadog.
Feel free to reopen the issue if it is not fixed for you.

I've tried out the new package version in my project, and sourcemap uploading is working now. Thanks!


Using aioredis with websockets

While developing a server, I'd like to read/write to redis: I found a package that works with asyncio called aioredis.
    # Now push to redis
    redis = await aioredis.create_redis_pool(
        'redis://localhost',
        minsize=5, maxsize=10,
        loop=asyncio.get_event_loop())

    await redis.publish_json('my_channel_name', msg)

    redis.close()
    await redis.wait_closed()

However I am new to asyncio dev and I don't understand how I can only have 'one redis' connection (not sure whether I need a pool) that can be used in my 'connection processor', from the main documentation. Can I add 'member' variable that I can use from the websocket object
async def handler(websocket, path):
    async for message in websocket:
        # HOW CAN I ACCESS MY redis pool from here ?
        # Should I make it a global, and force or wait for the pool to be created (something like that ?).
        # Or can I add it to 'websocket'
        await process_message(websocket, message)

I've seen that custom example, but I don't know how to fit my 'global' in there. Flask has a way to access 'globals'. Not sure whether what I'm trying to do make sense.
Thanks for any help !

I realized that those questions are more about asyncio ... regardless I've just found aiohttp and it has something called an 'app', that can store things and be accessed from a handler (typical example is with a db connection). That would probably be a nice extension to websockets.

I'd use a global variable. It can be lazily instantiated if that's appropriate (i.e. write a get_redis_connection() that returns the existing connection if there is one, else creates it).

I actually tried such an approach but I was still getting some odd errors that are probably linked with my bad knowledge of asyncio. I should make a small minimal repro case that shows the problem.

I might try another approach using functools.partial. This lets someone attach variable to a function, which is the one passed in. Here's an example with client code, I should try to adapt it for server code.
async def client(url, creds, clientCallback):
    async with websockets.connect(url) as websocket:
        # do stuff
        await clientCallback(websocket)

# where the magic happens, retrieve 'path' from args
async def clientCallback(websocket, **args):
    path = args['path']

    print('hello world', path)

    with open(path) as f:
        for line in f:
            print(f"> {line}")
            await websocket.send(line)

async def hello(url, credentials, path):
    publishClientCallback = functools.partial(clientCallback, path=path)

    # (found that 'parallel' snippet somewhere)
    tasks = []
    N = 5
    for _ in range(N):
        task = asyncio.ensure_future(client(url, credentials, publishClientCallback))
        tasks.append(task)

    done, pending = await asyncio.wait(
        tasks,
        return_when=asyncio.FIRST_COMPLETED,
    )
    for task in pending:
        task.cancel()

Yes, functools.partial came up in similar discussions before, see https://websockets.readthedocs.io/en/stable/cheatsheet.html?highlight=partial#passing-additional-arguments-to-the-connection-handler as well.


Where is the documentation

Hello,
First of all, the helpers are really great.
But, do you plan to write a documentation on how to use these helpers in end-to-end tests?

@FabienDehopre I'm not sure if you've seen their video but it is here
https://www.youtube.com/watch?v=6aPfHrSl0Qk

Of course, I've seen their video about end-to-end tests and blue-harvest at ng-conf18. But we are using blue-harvest at my current job (to make e2e tests easier to write and read) and my management wanted me to write a doc since their is no official written doc.
Now, we have a non-official documentation in our wiki (but it's in french). Maybe I will send a PR with the documentation but it probably won't be 100% correct since I wrote ours by deduction and after seeing the video.

Any updates on documentation?

found the demo project usefull https://github.com/angular-seattle/protractor-new-hope

I'm glad you find blue-harvest useful! This is based on an internal library, which we plan to open source in the next six months or so as a more complete project. We wanted to demonstrate the action helpers style of writing e2e tests for ng-conf, so we released blue-harvest as kind of a preview.
Any documentation PRs would be welcome! We're happy to review and suggest corrections :)

@heathkit oh no.. Don't hold us in suspense for the next 6 months.. Specially when I finally got around to implement blue-harvest screen comparison into our smoketest.. :)


Issue: railway link -p command bug

Unable build project or use arrow keys and environment not built
Description:
When using the railway link -p command, I am unable to select a service using the arrow keys (↑↓ to move). While hitting "Enter" selects the default service, the environment is not built after the selection. This breaks the workflow for linking a project.
Steps to Reproduce:

Run the command railway link -p <project-id>.
Select the project and environment.
When prompted to select a service, the arrow keys do not function.
Hit "Enter" to select the default service.

Expected Behavior:

The arrow keys should allow navigation through the list of services.
Upon selecting the default option (via "Enter"), the environment should be built as expected.

Actual Behavior:

Arrow keys are non-functional, preventing selection of any service.
Pressing "Enter" selects the default service but does not trigger the environment to be built, leaving the project unlinked.

Logs/Terminal Output:
+   03:22:25pm ﬌ railway link -p <project-id>,
> Select a project name-redacted
> Select an environment production
> Select a service Reflex
[↑↓ to move, enter to select, type to filter]

System Information:

Railway CLI version: 3.14.0 (Issue persists across 3.13.0 and 3.14.0)
Installed via Homebrew
macOS version: 14.6.1 (23G93)
Terminal: iTerm2

Workaround Tried:

Reinstalled Railway CLI via Homebrew (brew reinstall railway).
Tried both versions 3.13.0 and 3.14.0.
Arrow keys remain non-functional, and the environment still fails to build even when selecting the default option.

Additional Information:
This is a blocking issue as I cannot link the project or build the environment correctly. Please advise on potential fixes or workarounds. Let me know if any further logs or details are required. Thanks for your help!

Resolved. I just kept uninstalling and reinstalling until it worked. May want to look into it but whatever.


feature request? allow customize the default cgroup root path

As mentioned in the title, there are some usage scenarios that require this capability. we want to build an agent that depends on the crate libcgroups, and we're trying to run it in container as a daemonset workload, so it must mount the host's cgroup root path /sys/fs/cgroup as something like /host/sys/fs/cgroup in the container filesystem.
I'm not sure how to implement this in the current code base. consider this as a feature request or proposal.
If this proposal is accepted, I'll submit a PR on it.

@fengxsong Thanks for your proposal.
It sounds good to me. But don't change the default path for cgroup. It means if the user doesn't pass the path of cgroup, we have to use /sys/fs/cgroup
Here is the default path for cgroup.
https://github.com/containers/youki/blob/6a9c78bb73305f19b9b97886eba38f571aec46ef/crates/libcgroups/src/common.rs#L26

@utam0k  is it ok to redefine the DEFAULT_CGROUP_PATH?
lazy_static! {
    pub static ref DEFAULT_CGROUP_ROOT: String =
        std::env::var("DEFAULT_CGROUP_ROOT").unwrap_or("/sys/fs/cgroup".to_string());
}

since type of DEFAULT_CGROUP_ROOT has changed from &str to String, then some refenced code will need to be changed.

@fengxsong No, please pass it from libcontainer's builder pattern.

@fengxsong can I ask you to make a PR updating docs and the migration guide regarding the changes done in https://github.com/containers/youki/pull/2411 , as it is part of public API of libcgroups ?

@fengxsong can I ask you to make a PR updating docs and the migration guide regarding the changes done in #2411 , as it is part of public API of libcgroups ?

sure, but would you mind pointing out which docs need to be updated?

Closing as completed, docs are also done :+1:


cache_randomness explanation

Hi @ZwwWayne, saw that the latest release uses quite a bit of cache_randomness in the augmentation pipelines. May I know what is the function of these decorators and how it improves from previously without them?
Why does some random augmentation use cache_randomness and some use avoid_cache_randomness ?

You can refer to the docstring in mmcv.transforms.utils. Those decorators can cache the random number and apply them when you want to do the same operations again, like TransformBroadcaster.

Just to clarify, does it mean that if decorated with cache_randomness, the random function/method will return the same value every single time, across every data iteration?
From TransformBroadcaster, I understand that the main purpose of cache_randomness is so that the same random parameter in transformation can be propagated to other inputs. In this case, in the next data iteration (meaning another set of GTs/Imgs), will this random transformation parameter be sampled again or will the same cached value be used?

The random parameter will be fixed only when _cache_enabled is set as True. _cache_enabled is controlled by cache_random_params.


[SC] Discrepancy in arguments order: padding

As seen in the picture below, the order of arguments is different between when the user calls .kr and when the arguments actually go to the server. (This is also true for .process and .processBlocking).
This is a problem because when the docs are built it creates the arguments list based on the ordering in the C++ (which I supposed in this case is the order they get sent to the server), so SCDocs throws an error every time this help file is opened because the Docs order and the object's order are different.
My guess is that changing it in the C++ is nasty and would affect the other CCEs so this should be fixed in SC...which would mean just changing the order of the argument list (and other objects too I believe). I'm happy to do this manually (it's not really that many).
However this would be a breaking change. ...However I think that most users don't specify arguments with out using keywords all the way out to the 7th argument in these cases. Especially because often, the arguments startFrame, numFrames, startChan, numChans are left to defaults so the user would need to use keywords after that anyway. So my guess is it very likely not going to break/affect much code at all.
Since this SC docs overhaul is going to have breaking changes like this, perhaps it should try to be aligned with beta5 so that we can alert users?

Sounds more like it should be fixed in docs. padding is an awkward special-casey  thing that only got added relatively recently, and then only for descriptors. The problem here is that the SC Jinja template / python isn't yet taking account of it.
If the species key in the YAML allows, we may be able to sneak it into the Jinja with a simple conditional. However, IIRC, FluidLoudness is a annoying edge case because it's not a FFT based thing, so the surrounding arguments at that end are slightly different.

It might be easiest to do this in the python post-verification step. I think the only way we can tell is for FluidBuf* objects that have an equivalent Fluid* object whose species is descriptor 😿

😿 Whoa. Ok, that sounds doable though. I'll take a look at it. I'm gonna wait to hear back on the other PR (https://github.com/flucoma/flucoma-docs/pull/41) and issue (https://github.com/flucoma/flucoma-docs/issues/42). In case your thoughts about that guide the path forward.

Oh, it's even worse, upon looking. The index doesn't exist at that point, so the only place we can do cross referenceing is in jinja. Which means a new jinja filter (not terrible), to do the terrible thing.

Or, and hear me out here, we just change the species key of the relevant object to buffer-descriptor (or whatever), so we can then sort this without needing to cross reference. I'd be chill with doing that, because I'm hoping the need for species will be short lived 😬

Yup. Fine by me.

I have no opinion on the best way forward, as long as the main users find it idiomatically sound.

I think this might actually be a C++ problem. In my mind, padding was meant to be added at the end of the parameter tuple for those special cases that needed it, but it seems to appear in the middle of the json. I'm going to put this on hold whilst I investigate...

Indeed I am inserting it somewhere unhelpful, and I remember why I never wanted to see that code ever again 😭 It's much harder (I think) to put it at the end in C++ (it's a magically generated thing). Will fix in Python, not too complication and – besides – the FFT settings need fixing anyway.


ng-class inside ui bootstrap modal

This may be a niche case but I had an issue where inside of a ui bootstrap modal, the ng-class for the selected days was not firing at all. I circumvented the issue by putting an angular variable inside the plain class tag and after scope.generate I did a for each to apply where selected was true. This is my code:
class="text-center  {{day.calendar-highlight}} picker-day"
scope.generate();
angular.forEach(scope.days, function (item, value) {
                        if (item.mdp.selected)
                            item.calendar-highlight= 'calendar-highlight';

                    });

I also added this after the month change to retain the highlighting. There may be a much better way of doing this but I wanted to post so future devs may avoid my headache for past 2 days.

Isn't it a digest problem ?
I don't get why only the ng-class isn't not firing and anything else is working

I am not sure, it could be, I get fuzzy with these modal scopes.

The model is perfectly fine and functionality is fine except for ng-class. I even just put true for evaluation and nothing happens. But like I said, this could be a niche combination, I love the control btw.

Hmm, don't know where it can come from and don't have time to investigate sorry (busy at work).
If you find anything else, let me know ;)


fix: include project description json at both external and internal coordinates.

@jjohannes fyi

Thanks for the heads up. I guess if all tests pass, this change should not cause any problems. I vaguely remember that we already were at a point where the information was duplicated. Before the now commented-out code was added. And that that caused some issue. But  other changes now probably compensate for that. Or my memory is wrong. I don't remember details.
If I should run into anythings suspicious, I'll let you know.


Disabled usage of the POLYGON_MODE_LINE gpu feature in the examples

Fixes #14353
Fixes #14371

Could you also update the 2d_shapes example?

Could you also update the 2d_shapes example?
Updated


Update docker registry cache from inmemory to redis.

It gives Harbor the capability to controll the cache of docker
registry, and the workaround for cache invalidation bug caused
by garbage collection, that is clean cache in GC job.
For more details, see Harbor issue #5078.

Pull Request Test Coverage Report for Build 7605

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 64.992%

Totals

Change from base Build 7604:
0.006%

Covered Lines:
11165

Relevant Lines:
17179

💛  - Coveralls

I'll approve but please open another issue to handle the case when the redis requires a password.
It is important when user wants to integrate with external redis instances.

https://github.com/vmware/harbor/issues/5275


middleware cannot access gin.Context map

My controller calls context.Set(key,value) and my mw is added prior to the timeout mw because I need the response status.  But my mw reads nil for context.Keys.   I think this is due to the following code defined timeout.go:
   	cp := *c //nolint: govet
   	c.Abort()
   	c.Keys = nil

is it plausible to solve with:
                case <-finish:
			...
			c.Keys = cp.Keys

Can you provide a complete example?


doc(diagrams): remove old diagrams, use new git workflow

Changes look good although I wasn't able to test them directly (see #45 for the fix to that).


Configuring brokers

Hi,
I've been trying to get my head around broker configuration, I can't seem to find a way to create subscribers that are durable etc. Always ends up being an auto delete consumer. Are there any examples on how to pass in parameters for a queue for instance? Like setting TTL, Durable, Delivery mode etc.
If not is the only alternative to use a broker client directly? Can the broker be disabled completely? So a custom implementation can be used? I need to be able be able to create things like persistent queues with DLQ's etc, which are an important aspect of many micro services for things like being able to re-play failed messages after deploying a fix etc. And other times if service is down you want the messages to be held by the broker.
Thanks

A broker's durability is entirely dependendent on the underlying implementation. The default broker is just for notifications, there's no persistence. The broker like all other interfaces is pluggable and can be swapped out. You can find plugins in the go-plugins repo which includes brokers like rabbitmq which are durable. Hope that helps.

Hi, I am using the rabbit broker but can only seem to find a way to rename the queue and nothing else. An example or documentation would really help.
Thanks

So found out what was wrong,
looks like broker options can only be applied when using Options().Broker.Subscribe("", handler, rabbitmq.DurableQueue())
But can not be used when using micro.RegisterSubscriber()
Is there any way to get it working with that API? It's more user friendly.

I think @vtolstov has some experience here

Guess I'll wait for his reply, running into brick walls here haha. It's quite confusing. Even when using Broker.Subscribe() I can't figure out how to set the queue name and other parameters apart from whats included.

Can you provide list of options that you need?
We can add it to rabbitmq server.SubscriberOption and after that you can use it.

Can you provide list of options that you need?
We can add it to rabbitmq server.SubscriberOption and after that you can use it.

@vtolstov Thanks, it would be handy for most brokers like nats/rmq/kafka to be able to at lease some of the following, this is speaking from my experience having built several large scale platforms using kube/java microservices over the years. I'm now working on a new one using GO.
For myself right now I would like to be able to set queue arguments, durability, exchange. Though I will be switching to nats streaming once that plugin is available (or will write my own)

Define queue/topic/etc. arguments as a map is acceptable, different brokers have different options like ttl, priorities etc.
2: Should be able to create dead letter queues, this is pretty important in a lot of situations, kafka/rmq/nats streaming or any broker that supports persistence it provides you a way to avoid trying to handle the exception for every use case and store it at the service level, what if the service crashes? If no ack received then your message should retry n times and end up in a DLQ or errors topic etc. optionally of course.
3: Based on above my suggestion is that we should have the option of creating queues/exchanges/whatever (other brokers) separately and pass as configuration to subscribe like use queue name instead of creating new queue etc., there are just too many important variables unless you want to abstract the most important ones away? Which seems like a big hassle for all available permutations and not all brokers support same feature sets. The only reason I use different brokers is for features (cqrs I use kafa, complex routing I use Rabbit, IOT etc. I use Nats)
4: Pretty much all libraries I've played with Nats streaming/Rabbit/Kafka provide a client to do all these things and structs containing all available options when creating topics/queues etc. Maybe these should be left to the user and go-micro just makes the connection/factories available to use based on what broker you have configured. Sure it would result in if broker.Name == 'rabbitmq' then setup everything this way else if kafka do it that way etc. But I don't see much choice there. I understand go-micro is opinionated  but the defaults imo are too limited when you are building very large and complex systems that rely on guaranteed event delivery / retry-ability / error handing / much more and make use of many features that you get for free depending on the broker you use. If you don't want to provide that flexibility then maybe more configuration hooks allowing us to decorate/replace the queue/topic/exchange/etc. creation/configuration and certain points even if we need to do it per broker type (dev/prod) I'm perfectly fine with that, would have to do the same thing in Java etc.

Thanks for your time.

I'm try to add neededo stuff. Please wait

@waeljammal can you say what broker in priority for you with this options? (stan already have that you need)

I have a similar problem on July 30. i used rabbitmq as a plug-in, but can't set durable options. i tried many methods, such as : rabbitmq.DurableQueue()

I have a similar problem .on July 30, i used rabbitmq as a plug-in, but can't set durable option. i tried many methods, such as rabbitmq.DurableQueue(). i dug the source code of go-plugins and found it impossible


Al down fixes

?

Hi, Tobias
Sorry, didn't see it was a forked repo (the one I pushed to). There are
some things I've found in the forked version. First will check the original
one, and if it's still there then will PR.
Regards,
Anna
On Tue, Oct 4, 2016 at 8:36 PM, Tobias Gurtzick<EMAIL_ADDRESS>wrote:

?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/db-migrate/node-db-migrate/pull/420#issuecomment-251315812,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALwU2sMWYGLSIPcF9Be5HnMn1ATBS6Azks5qwgIPgaJpZM4KNFzD
.

--
Best regards,
Anna

Alright, let me know if there are any questions I can help with.


schema.rb has no type for index

When I create an index with:
      index :location, type: :gist

in my migration, it generates:
      index [:location]

In my schema.rb.
The type of the index is lost, and thus the table cannot be restored as postgresql fails with:
ERROR:  data type point has no default operator class for access method "btree"

Hi @kuon,
thanks for reporting the issue.
Unfortunately we're only using the schema dumper from Sequel, which has this kind of limitation (probably because schema.rb is meant to be as database agnostic as possible).
If you want to dump this kind of database specific information you should configure sequel-rails to dump the schema in sql format (using pg_dump for postgresql).
You can do it by setting the following in your config/application.rb:
config.sequel.schema_format = :sql

I see, thanks!


custom fields can not be added to info object

The info section

Test API
1.0.0
Api ....

should be extensible by adding custom fields following the convention x-....
e.g

....
MRP

But build fails with an error saying that tag  is not known.

What exactly are you trying to do?
Add custom Extensions to the @Info annotation?
See #617 if that is the case.


Football heatmap generation

Good starting point for this: https://github.com/binhnguyennus/football-tracking


Wrong requirement version for django-rq

Hello,
I tried to upgrade my netbox from version 2.7.6 to 2.7.7 and the database migration failed with this message:
ImportError: cannot import name 'UnpickleError' from 'rq.exceptions'

After searching I found this https://groups.google.com/forum/#!searchin/netbox-discuss/UnpickleError|sort:date/netbox-discuss/UEbwcPZLOqU/IRm0vPnZAgAJ.
The version in requirements.txt is not correct. Not really a bug of this playbook but ...
Is-it possible to add a task to replace the version of django-rq to 2.3.2 to fix this issue ?
I can do the MR if needed.
Thanks.

See https://github.com/lae/ansible-role-netbox/issues/97#issuecomment-630464594 and https://github.com/lae/ansible-role-netbox/commit/513bd4e6952e4fe3874255877992c9a3a8a3cee0
You can just specify netbox_pip_constraints locally for a quick fix. CI seems to have failed on Debian Stretch only with the above commit and I haven't gotten around to looking into why yet.

Even if I set this in my variables, it does not work:
netbox_pip_constraints:
  # Blacklist pynacl 1.3.0 due to https://github.com/pyca/pynacl/issues/479
  - 'pynacl!=1.3.0'
  # Blacklist django-rq 2.3.1 due to https://github.com/rq/django-rq/issues/421
  # https://github.com/netbox-community/netbox/issues/4633
  - 'django-rq!=2.3.1'

This is due to the version of django-rq used in the old version of netbox.
requirements.txt need to be changed with django-rq==2.3.2 instead of django-rq==2.2.0.
The issue is the same with a fresh install of 2.7.6 for example.

Weird, I only tested against 2.7.12 but it seemed to work against that.
What happens if you add a constraint for rq<1.4.0 instead?
Modifying the requirements.txt file with the role is not something I'm keen on doing in this role, as it causes conflicts in git-based deployments and idempotency issues for stable deployments.

So I found more details.
In old requirements.txt, we are finding django-rq but nothing about rq.
rq 1.3.x is working with django-rq 2.2.x
rq 1.4.x is working with django-rq 2.3.x

Putting this in my variable works for netbox 2.7.x:
netbox_pip_constraints:
  # Blacklist pynacl 1.3.0 due to https://github.com/pyca/pynacl/issues/479
  - 'pynacl!=1.3.0'
  # Blacklist rq 1.3.0 due to https://github.com/rq/django-rq/issues/421
  # https://github.com/netbox-community/netbox/issues/4633
  - 'rq==1.3.0'


pipeline failed when applid TASK <IP_ADDRESS> | PATCH | Ensure audit configuration files are 640 or more restrictive

Describe the Issue
We are using tag 1.1.0 earlier we were able to build with this tag however from past 2 week we are receiving an error :
TASK [rhel9-cis : <IP_ADDRESS> | PATCH | Ensure audit configuration files are 640 or more restrictive] ***
ok: [default] => (item=/etc/audit/audit-stop.rules)
ok: [default] => (item=/etc/audit/auditd.conf)
ok: [default] => (item=/etc/audit/audit.rules)
failed: [default] (item=/etc/audit/plugins.d/af_unix.conf) => {"ansible_loop_var": "item", "changed": false, "item": {"atime":<PHONE_NUMBER>.0140007, "ctime":<PHONE_NUMBER>.7236106, "dev": 66308, "gid": 0, "gr_name": "root", "inode": 25319108, "isblk": false, "ischr": false, "isdir": false, "isfifo": false, "isgid": false, "islnk": false, "isreg": true, "issock": false, "isuid": false, "mode": "0640", "mtime":<PHONE_NUMBER>.0, "nlink": 1, "path": "/etc/audit/plugins.d/af_unix.conf", "pw_name": "root", "rgrp": true, "roth": false, "rusr": true, "size": 358, "uid": 0, "wgrp": false, "woth": false, "wusr": true, "xgrp": false, "xoth": false, "xusr": false}, "msg": "file (/etc/audit/plugins.d/af_unix.conf) is absent, cannot continue", "path": "/etc/audit/plugins.d/af_unix.conf", "state": "absent"}
Could you please help us this to resolve, If we mark this task false what will be the issue or
Expected Behavior
A clear and concise description of what you expected to happen.
Actual Behavior
A clear and concise description of what's happening.
Control(s) Affected
What controls are being affected by the issue
Environment (please complete the following information):

branch being used: devel
Ansible Version: core 2.16.9
Host Python Version: [e.g. Python 3.7.6]
Ansible Server Python Version: [e.g. Python 3.7.6]
Additional Details:

Additional Notes
Anything additional goes here
Possible Solution
Enter a suggested fix here

hi @globalpayments-shoebsyed
Thank you for taking the time to raise this issue. I have added an enhancement, to hopefully stop this from happening in future.
I will be raising the PR to get moved to devel last today.
Many thanks
uk-bolly

hi @globalpayments-shoebsyed
You should find this is now in the main branch and released. I will therefore close this issue off.
many thanks
uk-bolly


githubaction with docker

PR title
Status
READY/IN DEVELOPMENT/HOLD
Description
A few sentences describing the overall goals of the pull request's commits.
Related PRs
List related PRs against other branches:

branch
PR

other_pr_production
link

other_pr_master
link

Todos

[ ] Tests
[ ] Documentation

Steps to Test or Reproduce
Outline the steps to test or reproduce the PR here.
git pull --prune
git checkout <feature_branch>
pytest --showlocals

Impacted Areas in Application
List general components of the application that this PR will affect:

:white_check_mark: Build ebook_homebrew 1.0.497 completed (commit https://github.com/tubone24/ebook_homebrew/commit/f3db0961aa by @)

:white_check_mark: Build ebook_homebrew 1.0.498 completed (commit https://github.com/tubone24/ebook_homebrew/commit/e05d99761d by @)


Backport AxographRawIO into 0.7.x maintenance branch

See discussion in #670.

These changes have already been merged into master with PR #670. If a new release, 0.7.2, is created, only the release notes will need to be merged into master.

I don't know why the Travis test result still shows "Pending" when it passed over 10 hours ago!
As I feared, the CircleCI tests failed, just as they did before I created this PR.
Sigh... 😢

There were a few fixes due to new versions of numpy, matplotlib, etc. after the 0.7.1 release.
e.g. [c0107d4] and [89c2210]
I don't have time to apply those to the 0.7.x branch right now - @jpgill86 could you make a new PR to get the tests passing for 0.7.x?

Thanks @apdavison for the pointers, I'll try it!

#683 passed the tests. After it is merged, I'll rebase this PR onto it.

Ready to merge!

Thank you @apdavison! All looks good from my end. Is there anything else I need to do for the release?


Support release branches

We should be adding release/* branches to our workflow files
and using the branch name to map to a table name.

Some projects that rely on release branches are not able to use the tool atm, so seems worth moving this one up a bit.

Those projects can use the tool!
All that needs to be done is the workflow file needs to be specified to run on any release branch.
on:
  push:
    branches: [ release/* ]

Okay, wonderful! If there are multiple release branches at once, will all commits from each branch go into the single table?

Yes they will. The way around that currently, is to have multiple workflow files for each release branch that passes in a specific table name.
Do we ever write to more than one release branch at a time?
One of the things we can do if we think it's worth it, is to parse the last path component of the release branch and look for a corresponding table.  So a  "release/1.5" branch would look for a table called "Release 1.5" if it couldn't find a table it would default to writing to Unreleased Changes table. (current default if no table name is provided)

@ssawchenko Do you ever have multiple release branches in flight at once?

@ssawchenko Do you ever have multiple release branches in flight at once?

I don't think we have this too often in practice, but in theory I could see a case where we have a release in the works but we need to apply a hotfix/patch to the current release.
ie.

Current release is 5.1
We are doing active dev on release/5.2
Bug comes in and we need to create release/5.1.1

In this case we would have 2 release branches in flight at once, unless we treat patches/hotfixes differently. I'm not sure we've hashed out a naming scheme for patches yet, so it's possible simply adopting a patch/<number> naming scheme would solve this.

@AZielinsky95 IIRC, the Coda API doesn't allow us to create tables, so we'd need to manually add the table with the corresponding release name ahead of the release starting. Am I remembering that correctly?

Yeah that's correct


Follow symlink for mount host path.

This is docker's behavior, we should keep it for backward compatibility.
Also ref https://github.com/kubernetes/kubernetes/issues/52318#issuecomment-328736840.
Signed-off-by: Lantao Liu<EMAIL_ADDRESS>

Apply LGTM based on https://github.com/kubernetes-incubator/cri-containerd/pull/242#pullrequestreview-62071569


Develop Blending Weights function

As a scientist I want a function that generates a set of blending weights so that the weighted blending plugin can use them
Related issues: #35
Acceptance criteria:

Create a function that will generate a simple set of blending weights
Blending weights can be used by the blending plugin
Consult with Tomek for his approach
Unit tests

Assigned Simon (but meaning Caroline)

Closed by #70


Next release?

The current version of the pip package is incompatible with jax>0.4.5 due to the removal of the ShapedArrayRef type from jax._src.state.types. Will the pip package be updated soon to allow compatibility with the latest version of jax again?

Yes working on a release, will hopefully have it out in a few days

Okay I think this may be blocked for a bit. We depend on Triton close to HEAD and there aren't plans for a Triton release that soon. Once Triton is released, we can cut a release.
In the meantime, you can try to manually install jax-triton w/ a newer Triton and a newer JAX.

I had some trouble getting bazel to find my CUDA installation, so I'm just using the version of jax-triton on pip and manually patching it to fix the references to ShapedArrayRef.

FYI I've updated the installation guide. You can now use CUDA installed via pip!

Thanks! It looks like I can install it from source now, although I had to lower my gcc version to 10 to get triton to build. It looks like the add and softmax examples work, but the others crash for various reasons (e.g. I think fused_attention crashes due to https://github.com/openai/triton/issues/1572).


Integration: Expose rest.Config

For now, only the Host field is populated. Going forward we can then add all-the-things clients would need to know for connecting to our ControlPlane/APIServer.
closes #23

How will a vendoring repo ensure compatibility between the version of apimachinery they are vendoring and the version required by this repo?  Will it be necessary to maintain release branches of this repo that track release branches of apimachinery?

/assign

/assign

How will a vendoring repo ensure compatibility between the version of apimachinery they are vendoring and the version required by this repo?
Will it be necessary to maintain release branches of this repo that track release branches of apimachinery?

I think those questions should be answered by CI. I think we should have this framework tested with multiple versions of client-go and by doing so set up some sort of compatibility matrix, something like client-go itself has maybe.
If possible, I'd like to avoid release branches. But if that's the way forward we will figure it out.
Alternatively, we could not depend on rest.Client but expose our configuration in a different way. Right now, the only thing we really need to expose is the URL. But in future I expect there to be more config stuff that will need be handled (TLS, users, ...). And then rest.Config seems to be a natural way to do so. We could also expose our own struct (similar to rest.Config and have users convert to rest.Config themselves if they need that. Also we could look into returning a kubeconfig file(contents).

d5bfdd1 introduces tests against different versions of k8s.io/client-go (which brings in rest.Config).

My question about 'ensuring compatibility' wasn't related to test compatibility so much as vendoring compatibility.  For a repo like k8s.io/api that has release branches, any repo that tracks those branches in its own release branches (e.g. service catalog) will require that other dependencies for a given branch be compatible.  That would be risky even for a single dependency (e.g. client-go), let alone multiple staging repos.
As you say, another option is to duplicate code where necessary to minimize vendoring of the staging repos and any others that use release branches.  I think the cost of this is likely to be higher than release branches, though, since it will impose both a code maintenance burden and a cognitive burden on developers when discrepancies inevitably arise between the code in this repo and the code it is duplicating from one or more of the staging repos.

My question about 'ensuring compatibility' wasn't related to test compatibility so much as vendoring compatibility. For a repo like k8s.io/api that has release branches, any repo that tracks those branches in its own release branches (e.g. service catalog) will require that other dependencies for a given branch be compatible. That would be risky even for a single dependency (e.g. client-go), let alone multiple staging repos.

I am not sure if I understand your concerns correctly.
Right now the CI tests prove that our framework is compatible with all (tested) versions of client-go. That means that -- as long as this stays true -- anyone that has already vendored any of those versions of client-go can vendor our framework?
As soon as our code is not compatible with a specific version of client-go anymore the CI will tell us. And then we can think about introducing release branches.
I feel I am missing your point though ... ?

This PR adds dependencies on k8s.io/api and k8s.io/apimachinery, both of which have release branches.  Where are the tests that ensure compatibility across those repos?

This PR adds dependencies on k8s.io/api and k8s.io/apimachinery, both of which have release branches. Where are the tests that ensure compatibility across the branches for those repos?

I thought the tests run against  specific versions of api and apimachinery because I thought godep would restore the correct version of those. It seems, that is not the case.
Maybe let me explain what I was trying to do:

Remove k8s.io/{client-go,api,apimachinery} from the ./vendor directory
get client-go in a specific version into the $GOPATH
use godep restore ./... to get the dependencies of client-go in there correct version

Now there is a problem with that:
For older versions of client-go (v4.0.0 and lower) godep does not restore the correct versions of k8s.io/api and k8s.io/apimachinery:

k8s.io/api is always at 163903a761b32a51f7cb963cf8c64290e854a3a9, 2018-02-05T21:14:43-08:00
k8s.io/apimachinery is at caa3b27b0fdaa84adc020cd7663afd62777ec9bd, 2018-02-05T18:22:21-08:00 (for v.2.0.0 of client-go, other versions may be correct)

How can I now find out which versions of api and apimachinery should really be used for client-go v2.0.0 for example? I thought I could blindly trust godep ...

Version restored by godep:
Setting client-go version to v2.0.0
found in /home/travis/gopath/src/k8s.io/client-go:
e121606b0d09b2e1c467183ee46217fa85a6b672, 2017-02-13T09:46:50-08:00,  (HEAD, tag: v2.0.0)
found in /home/travis/gopath/src/k8s.io/api:
163903a761b32a51f7cb963cf8c64290e854a3a9, 2018-02-05T21:14:43-08:00,  (HEAD -> master, origin/master, origin/HEAD)
found in /home/travis/gopath/src/k8s.io/apimachinery:
caa3b27b0fdaa84adc020cd7663afd62777ec9bd, 2018-02-05T18:22:21-08:00,  (HEAD -> master, origin/master, origin/HEAD)

Setting client-go version to v3.0.0
found in /home/travis/gopath/src/k8s.io/client-go:
21300e3e11c918b8e6a70fb7293b310683d6c046, 2017-07-05T23:56:09+00:00,  (HEAD, tag: v3.0.0)
found in /home/travis/gopath/src/k8s.io/api:
163903a761b32a51f7cb963cf8c64290e854a3a9, 2018-02-05T21:14:43-08:00,  (HEAD -> master, origin/master, origin/HEAD)
found in /home/travis/gopath/src/k8s.io/apimachinery:
85ace5365f33b16fc735c866a12e3c765b9700f2, 2017-06-13T20:37:36+00:00,  (HEAD)

Setting client-go version to v4.0.0
found in /home/travis/gopath/src/k8s.io/client-go:
d92e8497f71b7b4e0494e5bd204b48d34bd6f254, 2017-07-28T13:53:02+00:00,  (HEAD, tag: v4.0.0)
found in /home/travis/gopath/src/k8s.io/api:
163903a761b32a51f7cb963cf8c64290e854a3a9, 2018-02-05T21:14:43-08:00,  (HEAD -> master, origin/master, origin/HEAD)
found in /home/travis/gopath/src/k8s.io/apimachinery:
1fd2e63a9a370677308a42f24fd40c86438afddf, 2017-07-28T13:45:14+00:00,  (HEAD)

Setting client-go version to v5.0.0
found in /home/travis/gopath/src/k8s.io/client-go:
35874c597fed17ca62cd197e516d7d5ff9a2958c, 2017-09-28T15:13:57-07:00,  (HEAD, tag: v5.0.0, tag: kubernetes-1.8.0)
found in /home/travis/gopath/src/k8s.io/api:
fe29995db37613b9c5b2a647544cf627bfa8d299, 2017-09-21T16:17:36-07:00,  (HEAD, tag: kubernetes-1.8.1-beta.0, tag: kubernetes-1.8.0-rc.1, tag: kubernetes-1.8.0)
found in /home/travis/gopath/src/k8s.io/apimachinery:
019ae5ada31de202164b118aee88ee2d14075c31, 2017-09-25T16:41:55-07:00,  (HEAD, tag: kubernetes-1.8.3-beta.0, tag: kubernetes-1.8.2-beta.0, tag: kubernetes-1.8.2, tag: kubernetes-1.8.1-beta.0, tag: kubernetes-1.8.1, tag: kubernetes-1.8.0)

Setting client-go version to v5.0.1
found in /home/travis/gopath/src/k8s.io/client-go:
2ae454230481a7cb5544325e12ad7658ecccd19b, 2017-10-11T16:15:37-07:00,  (HEAD, tag: v5.0.1, tag: kubernetes-1.8.1)
found in /home/travis/gopath/src/k8s.io/api:
6c6dac0277229b9e9578c5ca3f74a4345d35cdc2, 2017-10-05T14:45:14-07:00,  (HEAD, tag: kubernetes-1.8.2-beta.0, tag: kubernetes-1.8.1)
found in /home/travis/gopath/src/k8s.io/apimachinery:
019ae5ada31de202164b118aee88ee2d14075c31, 2017-09-25T16:41:55-07:00,  (HEAD, tag: kubernetes-1.8.3-beta.0, tag: kubernetes-1.8.2-beta.0, tag: kubernetes-1.8.2, tag: kubernetes-1.8.1-beta.0, tag: kubernetes-1.8.1, tag: kubernetes-1.8.0)

Setting client-go version to v6.0.0
found in /home/travis/gopath/src/k8s.io/client-go:
78700dec6369ba22221b72770783300f143df150, 2017-12-06T10:53:11-08:00,  (HEAD, tag: v6.0.0, tag: kubernetes-1.9.1-beta.0, tag: kubernetes-1.9.0-beta.2, tag: kubernetes-1.9.0)
found in /home/travis/gopath/src/k8s.io/api:
11147472b7c934c474a2c484af3c0c5210b7a3af, 2017-12-01T15:45:52-08:00,  (HEAD, tag: kubernetes-1.9.0-beta.2)
found in /home/travis/gopath/src/k8s.io/apimachinery:
180eddb345a5be3a157cea1c624700ad5bd27b8f, 2017-11-27T09:38:05-08:00,  (HEAD, tag: kubernetes-1.9.1-beta.0, tag: kubernetes-1.9.0-beta.2, tag: kubernetes-1.9.0-beta.1, tag: kubernetes-1.9.0)

I'm not sure why the version isn't being set correctly.
I'm still not clear on how a repo that is using release branches of staging repos is intended to vendor this repo.  Ok, compatibility is being tested.  Is it possible to configure dep, run against a repo that is vendoring this one, to ignore the staging repo dependencies defined in Gopkg.toml for this repo (e.g. via overrides in the vendoring repo Gopkg.toml)?

I'm not sure why the version isn't being set correctly.

There was no k8s.io/api in 4.0.0, and no apimachinery in 2.0.0.

I'm not sure why the version isn't being set correctly.

There was no k8s.io/api in 4.0.0, and no apimachinery in 2.0.0.

Interesting. godep still seems to pull those in.

Interesting. godep still seems to pull those in.

Probably because you reference them in your code. That's the kind of problems you will see when targetting multiple client-go versions in parallel. This asks for trouble in vendoring and compilation.

Probably because you reference them in your code.

We only reference rest.Config directly / knowingly.
Anyway, I am looking into how introducing release branches would look like. But I am currently in a big fight with dep on that.

Ok, we did some experiments on how to potentially vendor this repo (dep managed) into k/k (godep managed). What we found is:

Any version constraints we have set up in the dep world will of course be ignored when vendoring with godep. Thus this package needs to be compatible with "all" versions of it's dependencies.
Generally vendoring a dep managed package into a godep one is possible - given you are OK with 1.
Updating the vendor tree with godep update ... seems to be broken, so it is probably easier to remove all the vendoring stuff and start from scratch with gedep save ...
If we want to stick with dep, release branches won't help, as any version constraints configured by dep will be ignored by godep anyway.

For 1. we can have tests in CI, and we can document which versions of client-go and others we support / test against.
Regarding 3. we can also document that. But actually the problem arises in the package which vendors this one -- and therefore the documentation about this issue may well be overlooked.
So I see two ways how to address that:

Keep using dep and test against different versions of client-go in CI. k/k and other should be able to vendor this package with the list of issues from above. We do not need release branches, at least not right now.
Switch to godep instead of dep. Also introduce release branches, tracking the versions from cleint-go.

Did I miss anything? Any input? Any preference?
@marun @sttts @totherme @pwittrock

@hoegaarden I am not sure why dep+godep is discussed. This is not the problem. There is a general rule:
We cannot vendor any packages depending on client-go and friends into Kubernetes.
This has nothing to do with the vendoring tool used. It has to do with the conflict of the client-go version in k/k's staging/ and an vendored in test-framework that must be compatible with the published k8s.io/client-go. If we change client-go in k/k, we might have to change the test framework outside of k/k. But the test-framework outside of k/k cannot be changed because then it's then incompatible with the published client-go version at k8s.io/client-go. There is no clean process to solve this.
Hence, repeating what @marun just wrote, "using client-go in the test-framework" + "using the test-framework inside k/k" unavoidibly means that the test-framework must live inside k/k as a staging/ repo.
Btw, better don't make assumptions about the vendoring tool. We might switch to dep at some point https://github.com/kubernetes/kubernetes/pull/57795.

Thanks. I think I am starting to understand all the problems with vendoring a staging repo now. Sprry about the confusion and thanks for the explanations and help.
So for now, that means that this cannot be done and I will probably close this PR and the related issue #23. It should be left to the users to create a rest.Config if they need that. I think eventually we will want something like rest.Config, but we need to see how this might look and how it can be achieved without a dependency on client-go.

I see these options:

Accept staging: create a staging directory, update https://github.com/kubernetes/publishing-bot/blob/master/configs/kubernetes-rules-configmap.yaml. Your repo will be published 4 times a day.
put your framework and all the tests self-contained in a docker container and run that from k/k's tests. Alternatively, git-clone the test-framework from the test script. Note though that you still cannot import any other k/k code, it must be completely self-contained.
don't use client-go and friends from the test framework at all. This can mean:

to duplicate the functionality with your own code

to come up with an injection mechanism that is implemented once in k/k (using client-go from k/k) and once in an out-of-k/k repository against the published k8s.io/client-go.
In other words: have k8s.io/test-framework and k8s.io/test-framework-runner and a k8s.io/kubernetes/test/integration/runner.
The first can be vendored because it does not have client-go imports. The second has all client-go imports for standalone mode. The third is the runner implementation inside kube.

Closing this PR because this implementation would not allow to be vendored into k/k.
Thanks all for the feedback!


Developer experience: recommending a default container image

Background
With #2839 and #3021 we are deliberately deprecating the practice of providing a default container image. One reason we have done this is to decouple Testcontainers from (a) a specific docker image, and (b) a specific version of an image.
We want to discourage and eventually block the usage pattern of new AbcContainer() and require all users to specify both the image and the tag for the container they wish to use.
Without doing this, we have no way of ever upgrading the default images safely. The problem is (was) worsened by the fact that new versions of an image involve not just changes to the tag, but changes to the image name or hosting registry, etc.
#3021 focused on letting module authors control the images that the module code is expected to be compatible with, while allowing users to still override that if they have an internal image that they're able to keep compliant with the module's expectations.
Principles we want to stand by

A version bump to Testcontainers should not change docker images silently.
If module code becomes incompatible with older versions of a docker image, we need to have a way to flag this loudly (e.g. fail fast with a noticeable error) rather than silently. The image compatibility checks should be the way to accomplish this in future.

Remaining challenge
We want to have a way for module authors to recommend the image that should be used with their module class.
One easy approach would be to expose this as a public constant, but this has an inherent problem: we would never be able to update the content of this constant without breaking the above principles. If we had a constant for a default image, it's not really any different to providing a no-args constructor all over again.
We need another way; something that is easy for users but does not re-create the version stickiness trap that we're just escaping from.
Ideas
@bsideup and I have discussed the first two of these, and I'd propose using a combination of one or more:

make sure the docs recommend an image in usage examples
recommend an image to use in the Javadocs
do allow a public constant to be exposed, but never allow its value to be changed. We could have a version expressed in the constant name, e.g. ABC_DEFAULT_IMAGE_v5_3 = DockerImageName.parse("abc:5.3") or something like this.
... something else

All of these basically revolve around requiring the user to hardcode the image they want to use at development time.

I agree that the version should be defined by the user.
But we can simplify user's life by providing a default name (without the version).
Not a big deal though but found it convenient to have in #3350 .
I wished we could just use a CTOR(String version) but this CTOR is already used to parse an image name. 😏

What's the status on this one? Asking as this is "preventing" #3350 to be merged.

Sorry, we will get to this, but have many constraints on our time at the moment.


input doesn't "scroll" when content overflows width or height

I'm running the lastest version, 1.21.3
If you press the keys until the input is filled to its width, the input does not scroll to see the most recent value and the end of the value
example:
|               | <- input size
|abcdefge|ijklmnop <- when it overflows
The visible values are always the same, it never scrolls to the most recent.
This happens in the Demos too, with a textarea if you press Enter a couple of times till it "overflows" you won't be able to see what you are typing unless you use the scroll bar to scroll down.

Hello @a40637francisco,
Unfortunately, I don't think this is a simple-keyboard bug. Simple-keyboard doesn't handle input elements (it has an internal input value). Moreover, the demos are just brief examples to get you started.  They're not meant to cover all cases, so developers will need to adapt/improve them to their needs.
I think the question here is essentially: "Why doesn't my input scroll to the left, after I set its value with Javascript", which is a general Javascript question. Here's a few SO posts discussing it:

“scroll” to the end of the input after js modifies input's value.
“Scroll” to the very right of a long text input.

Based on these StackOverflow posts and an example from the docs I came up with this:
https://codesandbox.io/s/github/simple-keyboard/react-simple-keyboard-uc-45-scroll-input-overflow-preventMouseDownDefault/tree/master/
Of course, this sandbox example won't cover all cases. It's meant as an example that you could then adapt/improve as needed.
Regards,
Francisco Hodge


alias a limit_value method

This makes the pager api drop-in compatible with the view code used by Kaminari

ci is red ;(

Fixed.
Apologies, I didn't get the test suite running locally and just pushed the "obviously correct" code. :(

No worries. that's why we have CI :)


library always try to parse reponse as JSON even if errors or no content (DELETE)

While get reponse status code and after check the status code:
if leave_undecoded or not is_success or result.status_code == 204:
return is_success, response.content

Fixed, merged your pull request.


How to override admin interface of plugin extension?

I’m trying to customize one of the hooks file \src\extensions\preview-button\admin\src\hooks\use-preview-data.js but I’m not sure how to override the file with plugin extension. The documentation only show the method for plugin’s server interface but I’m not sure how to customize for admin interface. Anyone know how to solve this ?

Hi @Ruixian1006 To my knowledge, there is not a way to override the admin interface. However, the plugin has recently updated with breaking changes that you should review. Depending on what you are trying to accomplish, the new plugin options may help.


chore: refactor sideinput and redis sink e2e

as per #1674

let's do the deletion, rerun the approval workflow, before merging.


Incorrectly recognized jump table

Binary: Windows 10 looper 64-bit
The lifter reports the following error:
Data cross reference at 14000235b targeting 140000000 does not match any known externals and is not contained within any data segments.

We can see that our backwards scan treated lea     r9, cs:140000000h as the table base, whereas we probably wanted it to use  mov     eax, ds:rva off_1400022FC[r9+r8*4].
IDA Pro recognizes this as a jump table, and mcsema-disass finds the correct jump table to switch on for jmp r9. In the disass log, we get:
  BB: 140002340 in func 140002220 with 7 insts
    I: 140002340
    I: 140002343
    I: 14000234a
    I: 140002352
    I: 140002355
    I: 140002358
    I: 14000235b
      Successors: 140002380, 140002370, 140002384, 1400023a0, 140002367, 14000236b, 1400023b0, 14000236e, 140002390, 140002378, 140002394, 140002364, 140002397, 1400023b8, 140002374, 14000239c, 140002360

Curiously, the memory reference information is missing :-S

Worth noting that the binary's first segment (.text) begins at 140001000. In this case, it might be reasonable to implement a heuristic that tries to match an unresolved reference to the nearest lifted segment address.


[edn/rtl] add bit 2 to ERR_CODE register

The output FIFO added has a related fatal error, but a test bit was not also added at the time.
This is now added.
Fixes #16218.
Signed-off-by: Mark Branstad<EMAIL_ADDRESS>

anybody know how to fix this easily?

anybody know how to fix this easily?

You mean the lint CI error? I will try to trigger a rerun. Does not look like your PR cause it ;)

thanks @cindychip  - I tried all of that but could not edit the comment section that lint was complaining about. I think I will add the fatal error comment and start over again.

aborting again.


tf-m: Fix tf-m-test build issues

Remove unneeded things in the tf-m CMakeLists.txt and renaming things

@d3zd3z : Hi David, can we get this merged?


Missing Option Token from Sequencer

Sequencer
endpoint add_transaction has a second optional parameter token that would create endpoint requests like:
/add_transaction?token={token}

https://github.com/starkware-libs/cairo-lang/blob/0ba3ff59c1c86f2a30adc8fd144eaacb22c48ce9/src/starkware/starknet/services/api/gateway/gateway_client.py#L14
RPC
It seems to me that RPC does not have such an option
How to Resolve:
Add missing token parameter to Sequencer Provider add_transaction using methods

Can work on this one

Sort out do we need this to be implemented for mainet. As deploy go true Acc (UDC) and declare also. Is the whitelist token deprecated?

Confirmed by StarkWare that this is obsolete now!


Fix passing_null_values unit test.

Unit test ui/passing_null_values.rs fails when we run (update line1: //@check-pass to //@run).
Error message is Error: attempted to deref a null Java object pointer

Personal Investigation
When looking at src/null.rs I notice we automatically return Err(NullDref) when we call as_jref (src). My understanding is that anytime we try to fetch the java reference, like preparing inputs for a Java function call (src), it'll automatically return an Err.
Rather than erroring, (I believe) we should just pass the null pointer reference 0x00000000 and cast it to the JavaObject type that the JNI call is looking for. When doing this, and when we run the following test,
let date = java::util::Date::new().execute()?;
let hash_code = date
     .equals(duchess::Null)
     .execute()?;

We still seem to get an Err(NullDeref) error when we call as_jref on duchess::Null. This is weird because we explicitly return Ok(...).
Wrapping and adding printstatments in as_jref still doesn't explain why it's  returning Err.
We add print logs in the as_jref and in the codegen.rs. We also add some tests here:
https://github.com/duchess-rs/duchess/compare/main...nonguyen1:duchess:test/null-pointer
Specifically see https://github.com/duchess-rs/duchess/commit/2e2a9c813ebdd5e6afd8ff77f289a638069df837 for more details
Debugging observation
Running rust-lldb can't easily step and visualize the codegen.rs generated code. It just prints a lot of stack frame details that's not that human readable.

Fixed in https://github.com/duchess-rs/duchess/pull/182


[CSL-983] Send Time Lords and Time Slaves into oblivion

What's missing here? Why is it still WIP?

It's still unclear to me why interpreting the system start as a frame length is useful. Could somebody give me an example of when we would want to do this?
Anyway, I have no issues with this change as it stands, but I do want to request that we remove the SysStart worker and listener modules, as they're no longer necessary.

It's still unclear to me why interpreting the system start as a frame length is useful. Could somebody give me an example of when we would want to do this?

I don't know either. I guess it's needed in benchmarks for some reason. I think only @georgeee can answer, but it may take a lot of time.

Anyway, I have no issues with this change as it stands, but I do want to request that we remove the SysStart worker and listener modules, as they're no longer necessary.

Yes, we should remove all leftovers which are no longer needed, but if this PR is self-contained and doesn't break anything I would rather merge it and remove leftovers as another task.

Yes, we should remove all leftovers which are no longer needed, but if this PR is self-contained and doesn't break anything I would rather merge it and remove leftovers as another task.

Fair enough. I'll approve this.

@gromakovsky it was WIP because it:
• lacked your suggestion to add 2 seconds to the system start time and a comment explaining why this needs to be done;
• wasn't approved.
Now that it is approved, I'll only add one commit with the change I mentioned above, then I'll fix the merge conflict and ping you to merge the PR.

https://issues.serokell.io/issue/CSL-1005


Previous terminal contents aren't cleared when a refresh happens

Testing #119108

Executing clear also only removes the second prompt

Any other details on a repro here? I thought I fixed this bug already but I guess not. Is it consistent?

It happens 100% of the time for me.
Version: 1.55.0-insider
Commit: a6f6b4aa8e3a688d9a5cbcd5df14af511ce2bd8e
Date: 2021-03-23T05:02:44.557Z (13 hrs ago)
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:86.0) Gecko/20100101 Firefox/86.0

Does disabling local echo help?

no, same thing happens with it set to -1


feat: Add Editor Sidebar and components update route

Context
The Live, should handle a way to edit a page component props based on schema(for instance, zod) and update it on storage(supabase).
Solution
This PR brings a lot of parts, listed bellow

Extract the component schemas from components and islands:
The dev.ts script extracts all schemas (zod schema for instance) from each component/island module and adds these values to the DecoManifest. ⚠ Components from subfolders are not listed.
Enable the Editor when query string ?editor is present on request.
List current component props to be edited:
The Editor component mounts a form with all components for this page. Can change props, the order of components and remove it
Allow adding a new component to the current template

Preview
https://github.com/deco-pages/hortifruti/pull/7

TODO: change the zod schema to json schema and use react-jsonschema-form


idea update draft

Hackathon Submission: <PROJECT_NAME>
Name of Team Lead
Enter your full name

GitHub handles of Team Members
Enter the GitHub handles of all your team members (including yourself) as separate bullet points

Are all of your team members registered on our Hackathon Signup page?
This is a mandatory step for all participants to be considered eligible for judging

[ ] Yes
[ ] No

Rules and Code of Conduct
By submitting this PR, you agree to follow our Rules and Code of Conduct.

[x] Yes

Anything Else?
Any other feedback, queries or information you would like to share with us?

https://discord.com/channels/564160730845151244/1298292643217936454  Hi @adityaoberai  I need help with this getting this cors error doing some POC to create a project. Can you take a look?

The submission is ineligible because

There is no demo available
The project repo is empty


PubSub is not defined

vue.esm.js?65d7:566 ReferenceError: PubSub is not defined
at exports.default (pubsubOwner.js?3378:107)
at JXT.use (index.js?c76b:26)
at exports.default (index.js?5fb2:305)
at JXT.use (index.js?c76b:26)
at new Client (client.js?9ce5:64)
at Object.exports.createClient (index.js?73af:10)
at VueComponent.connectToServer ()
this is found in file pubsubOwner.js

sounds like a regression from #23 -- @legastero can you take a look?
You might want to pin the package version until then.

Fixed in 3.2.2. Thanks!

@legastero - Thanks for your quick support.


Request for v2 Tag Release

👋  I've observed that the V2 version lacks a tagged release. Can I kindly request the project maintainers to consider adding an official tag for this release?
Thanks!

Hello,
I created a tag https://github.com/vulcand/oxy/releases/tag/v2.0.0


fix query param depracation and bump streamlit to 1.30

Changes:

Update main.py
changed st.experimental_get_query_params to st.query_params

reason (st.experimental_get_query_params deprecation)
https://docs.streamlit.io/library/api-reference/utilities/st.experimental_get_query_params

Update Pipfile.lock
bumping streamlit version from 1.13 to 1.30

requires testing for breaking changes

This should resolve https://github.com/jrieke/streamlit-analytics/issues/39

@mt-krainski visibility

@jrieke Are you available to take a look at this?
Please let us know if you are still actively maintaining this repo

Hi,
still not working for me. can you please more detail how to do it.
I use streamlit 1.30

@RazHadas
I am hoping to get the change made in streamlit-analytics with this pull request
In the meantime, you can maybe specify in your requirements.txt or pipfile or whichever dependency file you have to use a streamlit version that is prior to 1.30

Thanks for the quick response. I will check it.

I messaged the author on Linkedin but no response so it would seem this project is not maintained...
Perhaps we will need to fork this repo and fix this issues independently but then the issue becomes around publishing the packages via pypi and pip, which I have less experience with but certainly can learn
Ill create an new issue stating this if we take this path
Tag me if you are interested in contributing
#TODO look into the licence of this repo and understand the implications of forking
@jrieke visibility

The analytics is streamlit is really problematic. I already try for few days to get unique page views.

The analytics is streamlit is really problematic. I already try for few days to get unique page views.

Hi @RazHadas
I have reached out to @jrieke on linkedin, here on Github and also just sent them an email to ask about how we can contribute and if the repo is being maintained or not
Without a response from them soon, I will be forking the project and fixing these issue in a new repo
Ill update you if that occurs and place it into this repo as a new issue

Sounds good. I just find script that get ip and screen resolution from user in streamlit, I want to improve the analytics.
By the way, did you manage to work with Google analytics 4 in streamlit?

Note: I am pushing this to my own fork but it seems be to included in this PR
Not sure why that would be tbh
@RazHadas The GA4 integration is something I want to work on in the future


Complex scss highlighting anomalies

I have some scss in SFC like this:
:deep(.el-scrollbar) {
  .reserve-drawer {
    padding: 0 20px;
    .create-btn {
      margin-bottom: 10px;
    }
  }
}
.reserve-edit-form {
  :deep(.el-form-item__content) {
    .el-input-number--mini {
      width: 80px;
    }
  }
}

it is rendered like this, seems not correct. How can I fix it?

The syntax highlight result is consistent with the scss file, please report it to vscode.


Get node syncing status API is missing the is_syncing field

Description
Hi! I'm working with the REST API for Teku. I noticed that in the official documentation for Get node syncing status, there is a field named is_syncing which indicates whether or not the client is still syncing with the beacon chain. However, when I hit this endpoint, the is_syncing field is missing:
$ curl http://localhost:5052/eth/v1/node/syncing
{"data":{"head_slot":"52","sync_distance":"667925"}}

As a workaround, I have to check if sync_distance is within some small margin (e.g. less than 3) in order to determine if the client is still syncing or not.
Steps to Reproduce (Bug)

See example shown above

Expected behavior: [What you expect to happen]
{"data":{"head_slot":"52","sync_distance":"667925","is_syncing":true}}

Actual behavior: [What actually happens]
{"data":{"head_slot":"52","sync_distance":"667925"}}

Frequency: [What percentage of the time does it occur?]
100%
Versions (Add all that apply)

Software version: v21.1.1
Java version: openjdk 14.0.2 2020-07-14
OS Name & Version: Ubuntu 20.04.2 LTS
Kernel Version: Linux dev-pi 5.4.0-1028-raspi #31-Ubuntu SMP PREEMPT Wed Jan 20 11:30:45 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
Virtual Machine software & version: N/A
Docker Version: N/A
Cloud VM, type, size: N/A

I confirm the absence of the  is_syncing field. In a production fully sync node - the result is
curl http://localhost:5051/eth/v1/node/syncing
{"data":{"head_slot":"590150","sync_distance":"0"}}

Hello, I confirm the above and the absence of the is_syncing field. In a production fully sync node the result is:
curl http://localhost:5051/eth/v1/node/syncing
{"data":{"head_slot":"590150","sync_distance":"0"}}

Thanks for reporting this - the is_syncing field was only quite recently added to the standard API and to Teku (in #3528) so it hasn't been included in a release yet.  The API docs appear to be defaulting to lastest/master version - there's a toggle at the top of the page to choose the right version, but unfortunately doesn't look like links to a specific method maintain the version, which may well have led to this confusion.
I'll close this one as the field will be there when the next release goes out but have logged https://github.com/ConsenSys/doc.teku/issues/255 and https://github.com/ConsenSys/doc.teku/issues/256 to get the doc links issue fixed.


New command - Read-DbaBackupHeader

Ignore this one. Gotta redo some stuff. Will close once my changes have been tracked.

Messed up, closed.


Unable to make it work over the VPN

When trying to access the password.yourdomain.com over the VPN, the website is only showing the passcore  logo. It is unable to load the default page.  The site is working internally. Please help me in modifying the page to access through VPN

Do other web pages from the same web server load correctly?
What type of VPN? I can think of three different types straight off. Single point end user or LAN?
What differences are there at the network level when connecting to your organisation over your VPN compared to being directly on the network? (For example, do you have a web proxy in the loop somewhere?) Have you checked this with your IT Infrastructure team?
Is this using the same PC across VPN as on the network, and if not, have you eliminated any possible differences between them? Same web browser?
What happens if you try different web browsers?

Hi Chris,
Please find the answers.
Do other web pages from the same web server load correctly
We have loaded another IIS site with a simple HTML page, and that loads
successfully. We use the VPN to access sites on other IIS and Apache
servers and they work correctly.
What type of VPN? I can think of three different types straight off. Single
point end user or LAN?
It’s a Web Browser based VPN solution – it wraps the page within it’s own
URL and offers it up as a service. Here is the URL pattern:
https://remote.guildgroup.com.au/dana/home/launch.cgi?url=https%3A%2F%2Fpasscore.guildgroup.com.au
What differences are there at the network level when connecting to your
organisation over your VPN compared to being directly on the network? (For
example, do you have a web proxy in the loop somewhere?) Have you checked
this with your IT Infrastructure team?
The key difference is that the connect to this site is via the VPN
Appliance, rather than connecting directly. The VPN is within our DMZ
however, the firewall rules allow direct and open access for this device to
the internal network.
Is this using the same PC across VPN as on the network, and if not, have
you eliminated any possible differences between them? Same web browser?
We have tried this in both Chrome and IE 11 – both work when accessing
directly, neither work when accessing the site via the VPN portal.
We are ready to arrange a call if more information is required.
We have tried this in both Chrome and IE 11 – both work when accessing
directly, neither work when accessing the site via the VPN portal.
Thanks
Sharam
On Fri, Sep 9, 2016 at 7:05 PM, Chris Davies<EMAIL_ADDRESS>wrote:

Do other web pages from the same web server load correctly?
What type of VPN? I can think of three different types straight off.
Single point end user or LAN?
What differences are there at the network level when connecting to your
organisation over your VPN compared to being directly on the network? (For
example, do you have a web proxy in the loop somewhere?) Have you checked
this with your IT Infrastructure team?
Is this using the same PC across VPN as on the network, and if not, have
you eliminated any possible differences between them? Same web browser?
What happens if you try different web browsers?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/unosquare/passcore/issues/39#issuecomment-245859909,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVEXjhtFisl0IGV37QOo58kEg2RbEbu4ks5qoSFIgaJpZM4J4tNn
.

--
sharam shah

Do other web pages from the same web server load correctly ?
We have loaded another IIS site with a simple HTML page, and that loads
successfully. We use the VPN to access sites on other IIS and Apache
servers and they work correctly.
What type of VPN? I can think of three different types straight off. Single
point end user or LAN? It’s a Web Browser based VPN solution – it wraps the
page within it’s own URL and offers it up as a service. Here is the URL
pattern:
https://remote.yourdomain.com/dana/home/launch.cgi?url=https%3A%2F%2Fpasscore.yourdomain
.com
What differences are there at the network level when connecting to your
organisation over your VPN compared to being directly on the network? (For
example, do you have a web proxy in the loop somewhere?) Have you checked
this with your IT Infrastructure team?
The key difference is that the connect to this site is via the VPN
Appliance, rather than connecting directly. The VPN is within our DMZ
however, the firewall rules allow direct and open access for this device to
the internal network.
Is this using the same PC across VPN as on the network, and if not, have
you eliminated any possible differences between them? Same web browser?
We have tried this in both Chrome and    IE 11 – both work when accessing
directly, neither work when accessing the site via the VPN portal. We are
ready to arrange a call if more information is required.
On Tue, Sep 13, 2016 at 10:41 AM, Sharam Shah<EMAIL_ADDRESS>wrote:

Hi Chris,
Please find the answers.
Do other web pages from the same web server load correctly
We have loaded another IIS site with a simple HTML page, and that loads
successfully. We use the VPN to access sites on other IIS and Apache
servers and they work correctly.
What type of VPN? I can think of three different types straight off.
Single point end user or LAN?
It’s a Web Browser based VPN solution – it wraps the page within it’s own
URL and offers it up as a service. Here is the URL pattern:
https://remote.guildgroup.com.au/dana/home/launch.cgi?url=
https%3A%2F%2Fpasscore.guildgroup.com.au
What differences are there at the network level when connecting to your
organisation over your VPN compared to being directly on the network? (For
example, do you have a web proxy in the loop somewhere?) Have you checked
this with your IT Infrastructure team?
The key difference is that the connect to this site is via the VPN
Appliance, rather than connecting directly. The VPN is within our DMZ
however, the firewall rules allow direct and open access for this device to
the internal network.
Is this using the same PC across VPN as on the network, and if not, have
you eliminated any possible differences between them? Same web browser?
We have tried this in both Chrome and IE 11 – both work when accessing
directly, neither work when accessing the site via the VPN portal.
We are ready to arrange a call if more information is required.
We have tried this in both Chrome and IE 11 – both work when accessing
directly, neither work when accessing the site via the VPN portal.
Thanks
Sharam
On Fri, Sep 9, 2016 at 7:05 PM, Chris Davies<EMAIL_ADDRESS>wrote:

Do other web pages from the same web server load correctly?
What type of VPN? I can think of three different types straight off.
Single point end user or LAN?
What differences are there at the network level when connecting to your
organisation over your VPN compared to being directly on the network? (For
example, do you have a web proxy in the loop somewhere?) Have you checked
this with your IT Infrastructure team?
Is this using the same PC across VPN as on the network, and if not, have
you eliminated any possible differences between them? Same web browser?
What happens if you try different web browsers?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/unosquare/passcore/issues/39#issuecomment-245859909,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVEXjhtFisl0IGV37QOo58kEg2RbEbu4ks5qoSFIgaJpZM4J4tNn
.

--
sharam shah

--
sharam shah

it wraps the page within its own URL and offers it up as a service.

I suspect this may be your problem. It might be worth discussing this issue with your VPN Appliance support team. I'm not the author of PassCore, just someone trying to help.
Regards.

Please try with the latest version and let us know if this is still a problem. Reopen the issue if necessary.