Some of the VL53L5CX examples require ulab?

The VL53L5CX motion and object tracking examples report
from ulab import numpy
ImportError: 'no module named 'ulab'
I copied over the firmware / bin file as per, https://learn.pimoroni.com/article/micropython-and-vl53l5cx#installing-vl53l5cx-firmware
Pi Pico plugged into a breakout garden and flashed with pimoroni-pico-v1.21.0-micropython.uf2
I want to use this module with an Inventor 2040 W. I’m working on a Rover build with two Micro Metal Gear Motors. There is no option to swap out the Pico W. What now?

Sorted, got a test build with ULAB included that worked a charm.
https://github.com/pimoroni/pimoroni-pico/actions/runs/8553250722


getCroppedImage returns different size for smaller bitmaps

When bitmap size is greater than view's dimensions, the returned bitmap is cropped correctly.
If ImageCropView has bitmap with size smaller than view's size, the bitmap is scaled up to fit view dimensions, but .getCroppedImage() method returns the unscaled bitmap.
Is there any way to return the bitmap with size as seen in the ImageCropView?

I think I don't need
If you wanna, please develop and pull request :)

If you want, you can create scaled up bitmap after getCroppedIamge.
    Bitmap cropBitmap = ImageCropView.getCroppedIamge();
    int width = cropBitmap.getWidth();
    int height = cropBitmap.getHeight();
    int newWidth = 300;
    int newHeight = 300;
    float scaleWidth = ((float) newWidth) / width;
    float scaleHeight = ((float) newHeight) / height;

    Matrix matrix = new Matrix();
    matrix.postScale(scaleWidth, scaleHeight);
    Bitmap resizeBitmap = Bitmap.createBitmap(cropBitmap, 0, 0, width, height, matrix, false);


[1.20.1] Needs a 1.20.1 release

Release for 1.20.1 please

Does the 1.20 version work? I'll try to do it when I get home.

It likely does, however with the client I use (as well as modpack I made) it wont use it as it's version says 1.20


[Task]

Description
Now sofa rpc depends on the lower version of alibaba dubbo. We need to upgrade the sofa rpc version. The higher version depends on apache dubbo3.
Task List

Upgrade sofa rpc version support
Upgrad and test pass in shenyu-examples/shenyu-examples-sofa
Upgrad and test pass in shenyu-integrated-test/shenyu-integrated-test-sofa shenyu-integrated-test/shenyu-integrated-test-k8s-ingress-sofa

assign me , pls , i wanna help

assign me , pls , i wanna help

welcome, has assigned to you.

assign me , pls , i wanna help

welcome, has assigned to you.

thx 😊


Can you provide all the code？

Dear author, hello. I was greatly inspired by your paper recently. I encountered some problems when trying to reproduce it. I saw that several files such as preprocessing in the code were not uploaded. Could you please provide these code files? I would be very grateful!

Thank you for your recognition of our work. A lot of pre-processing work was done a long time ago, and I'm sorry that we haven't perfected this. If you need it, we can discuss what you need in detail. We can use wechat or just email (my wechat is thucscyrrr).
---- Replied Message ----
| From | @.> |
| Date | 09/08/2024 20:56 |
| To | @.> |
| Cc | @.***> |
| Subject | [caiyunrui/lora-mer] Can you provide all the code？ (Issue #1) |
Dear author, hello. I was greatly inspired by your paper recently. I encountered some problems when trying to reproduce it. I saw that several files such as preprocessing in the code were not uploaded. Could you please provide these code files? I would be very grateful!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


DOM methods prepend(), append(), before(), after(), replaceWith()

Please see
https://twitter.com/html5/status/724816231136661504
and
https://dom.spec.whatwg.org/

+1

@Ugoku Just as a tip for the future: Instead of posting "+1" you can alternatively click on "Add your reaction" (or click on an existing reaction).

I know, but @Fyrd recently said that GitHub doesn't support that in its API yet, so "+1" comments are prefered for the time being.

+1

Now available at http://caniuse.com/#feat=dom-manip-convenience


Proof of concept of a bare-metal soc implementation.

This is more work in progress than anything else, and this doesn't compile yet. There's things to clean up in grpc, for instance, the fact we assume that sockaddr exists in the name resolver.
Ideally, we should be able to link a dummy binary with LWIP-like API calls, and leave that as a build test for Jenkins.

Can one of the admins verify this patch?

Oh, also, BoringSSL would never compile with this. PolarSSL needs to be supported for that.

Can one of the admins verify this patch?

Removing assignment since it's unlikely I'll look at this for a while.


deps: switch from steveej/gexpect to coreos/gexpect

Fixes #1733.

I'm hesitating because the file gexpect_tests.go was removed. godep must've decided that it's not needed. I"m surprised to see this behavior but I agree with godep here, as we don't run 3rd party functional tests.

The previous switch on ThomasRooney/gexpect -> steveeJ/gexpect didn't delete gexpect_tests.go: https://github.com/coreos/rkt/commit/75054eb023f70547e4c178112332e335e786f8ac
I don't know why.

godep changed behaviour with test files recently: https://github.com/tools/godep/commit/87fb5cdc4cbd6f0150f2e58087e235e843065304
I think it is fine to remove gexpect_tests.go if the tests pass.


🐛 BUG: build wasm filenames not as expected

Which Cloudflare product(s) does this pertain to?
Wrangler
What version of Wrangler are you using?
2.13.0
What operating system are you using?
Windows, WSL and Linux
Describe the Bug
After not running wrangler for a couple months, I tried to deploy and encountered the following error:
> npx wrangler publish --dry-run
 ⛅ wrangler 2.13.0
--------------------
Running custom build: cargo install -q worker-build && worker-build --release
[INFO]: Checking for the Wasm target...
[INFO]: Compiling to Wasm...
    Finished release [optimized] target(s) in 0.36s
[INFO]: Installing wasm-bindgen...
[INFO]: Optimizing wasm binaries with `wasm-opt`...
[INFO]: Optional fields missing from Cargo.toml: 'description', 'repository', and 'license'. These are not necessary, but recommended
[INFO]: :-) Done in 1.65s
[INFO]: :-) Your wasm pkg is ready to publish at C:\Users\mcrai\Documents\Git Repos\mattcraig.tech\build.
X [ERROR] Could not resolve "./index_bg.wasm"

    index_bg.js:1:22:
      1 │ import * as wasm from './index_bg.wasm';
        ╵                       ~~~~~~~~~~~~~~~~~

1 error
Error: esbuild exited with status exit code: 1

X [ERROR] Command failed with exit code 1: cargo install -q worker-build && worker-build --release

Looking at the build directory, it appears that index.wasm is being generated but no index_bg.wasm, which is causing esbuild to fail.
I have not made any changes to my code or build configuration, just tried re-running workflows that worked 2 months ago with an updated version of wrangler.

I was previously on wrangler 2.1.9, but the issue was present on both 2.1.9 and after upgrading to 2.13.0.
It appears the underlying issue was with the worker crate. I was using the v0.0.9, but the wasm-bindgen dependency was still on v0.2.78. The latest version of worker-build, v0.0.9, is only compatible with wasm-bindgen v0.2.84 onwards, which is where the change to wasm import replacement occurs that is causing the resolution to fail. Upgrading to worker v0.0.15 updated the wasm-bindgen dependency to v0.2.84 and fixed the error.
It seems like there's a dependency link missing somewhere in this chain. worker pins the version of wasm-bindgen that it depends on, but worker-build is free to upgrade even when it's no longer compatible with the version of wasm-bindgen used. It seems like worker-build is implicitly depending on a specific version of wasm-bindgen (or a version of worker) that isn't declared as a dependency.


Feature request: update all charts of an helmfile without having to create a manifest of each of them

Is your feature request related to a problem?
To update the different charts of an helmfile, we need to create an updatecli manifest for each of them.
We also need to keep track of which of them are covered by an updatecli manifest.
Describe the solution you'd like
Ability to specify once to updatecli we want to check/update all helm charts of an helmfile.
Proposed format, with the introduction of helmfile kind:
title: "Bump helm charts versions of publick8s"
sources:
  default:
    kind: helmfile
    spec:
      # either a local path
      file: clusters/publick8s.yaml
      # or a public url
      url: https://github.com/jenkins-infra/charts/blob/main/clusters/publick8s.yaml
targets:
  updateChartsVersions:
    name: "Update all charts versions"
    kind: helmfile
    spec:
      file: clusters/publick8s.yaml
    scm:
      github:
        user: "{{ .github.user }}"
        email: "{{ .github.email }}"
        owner: "{{ .github.owner }}"
        repository: "{{ .github.repository }}"
        token: "{{ requiredEnv .github.token }}"
        username: "{{ .github.username }}"
        branch: "{{ .github.branch }}"

Describe alternatives you've considered

N/A
Additional context

To update the charts used in these two helmfiles, we have all these updatecli manifests: https://github.com/jenkins-infra/charts/tree/main/updatecli/updatecli.d/charts
All of them are similar, and could be IMO factored in one manifest for these helm charts version update. (This is not the case for the docker image versions bump, as we need to search info in different places)

Now that the autodiscovery is ready, I can have a look to this issue if needed.
Considering that there is no way to clearly identify Helmfile configuration, I am not considering the helmfile crawler to be running by default. Instead we'll need to enable it using a configuration.
So proposed Updatecli manifest
# A scm configuration can be specified so Updatecli browse the git repository content.
scms:
    default:
        kind: github
        spec:
        # ...
pullrequests:
    default:
       kind: github
       spec:
       # ....

autodiscovery:
     # Optional configuration to specified the scm configuration used in generated manifest
     scmid:
     # Optional configuration to specified the pullrequest configuration used in generated manifest
     pullrequestid:

     crawlers:
         helmfile:
            # default false
            enabled: true

            # Optional, mutually exclusive with only
            ignore:
              - path: <specifies path to ignore>

            # Optional, mutually exclusive with ignore
            only:
              - path: <only explore this path>

            # OptionDefault scm directory or local if nothing specified
            rootdir: <override directory to analyze>

The rule would be
If we find a yaml file with the following content
repositories:
    - name: example
      url: https://mychart

releases:
    - chart: example/mychart
      version: 1.0.0

Then we generate the manifest
title: "Bump {{ helmChart Name }} Helm Chart Version"

# if `scmid` is specified in autodisccovery configuration
scms:
  {{ scmid }}:
    kind: github
    spec:
      {{ scmid spec }}

sources:
  {{ chartName }}:
    name: Get latest {{ chartName }} version
    kind: helmchart
    spec:
      url: {{ chartRepositoryUrl }}
      name: {{ chartName }}

conditions:
  # Extra protection in case the target file changed between the detection and apply
  {{ chartName }}:
    name: "Ensure {{ chartName }} chart is specified"
    kind: yaml
    scmid: default
    spec:
      file: {{ filename }}
      key: {{ identified_key }}
      value: {{ repositoryNAme }}/{{ chartName }

targets:
  {{ chartName }}:
    name: "Update {{ chartName }} chart version"
    kind: yaml
    scmid: default
    spec:
      file: {{ filename }}
      key: {{ identified_key }}

# If pullrequestid is specified in autodiscovery configuration`
pullrequests:
  default:
    kind: github
    scmid: {{ scmID }}
    spec:
      labels:
        - dependencies
        - accountapp

This would generate new manifests isn't it? Which then will have to be updated?
Your solution is a nice workaround for this FR, but in the end I'd prefer a new kind: helmfile, more simple and short IMO.


Create .gitignore

Hey,
A .gitignore was missing here. I used a standard C template provided by github to generate this one. It's particularly useful when using libmseed as a git submodule as otherwise the parent repository will remain in an unclean state after  `make!
Regards
Marius

Cool, I'll add a copy to the next major release version as well.  Thanks Marius!


Add my ecr repo

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: TerryHowe
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Added local search feature.

Hi @probberechts ，Thank you for the open source cactus-dark，I very love it，I recently added local search feature，Hope to be added to cactus-dark，I have added instructions to the README.md . here are some demos:

PC：

iPad：

iPhone 6：

Galaxy S5：

Responsive：

Live demo
hackfun

Thanks! Local search seams a good idea and it could be useful for some people (especially if you have a lot of blog posts). However, I think it should be framed more like an option in the README, instead of being part of the basic installation procedure. Also, I will probably make a couple of small design changes before I merge.

OK，Thx.


Add kami to TechEmpowered framework benchmarks

I've copied the go-raw/goji implementations and modified it for kami here: https://github.com/someone1/FrameworkBenchmarks/tree/master/frameworks/Go/kami
I was wondering if there was any interest in tweaking this so that it uses kami in a more "production" kind of way. As you can see I added a middleware to add the Server response header vs setting per handler as it seems like the way you'd tackle this in any framework. I don't know if there's really more to do here but I thought I'd ask before putting in a PR. I don't really use the context object in anyway, would it make sense to use it to get the database object vs using a global variable in an actual production application?

Looks good... I'm not sure how fair the other benchmarks are, but as long as they are on the same page.
As far as putting global stuff in your context, that's up to you. Some people say it's an anti-pattern to store configuration etc in the context and you should only put request-specific stuff in there, but I think it comes down to personal preference.

Looks like we're in the latest benchmarks, thanks a lot!


Create signup page

Create sign up page.
Depends on #9

I'd be happy to work on this. You can assign me.

Perfect, thank you @im-machakata. Go for it. The first step is to clone the repository and set up a local development environment on your machine.

@im-machakata as discussed in the WhatsApp group, someone implemented the user sign-up feature at the last meetup(I apologise for that again). This issue still needs more work however, it would be nice to have unit tests to test the signup functionality, make some improvements to it and also to have it documented. Are you interested in working on any of these related tasks?

@im-machakata as discussed in the WhatsApp group, someone implemented the user sign-up feature at the last meetup(I apologise for that again). This issue still needs more work however, it would be nice to have unit tests to test the signup functionality, make some improvements to it and also to have it documented. Are you interested in working on any of these related tasks?

I'm not good with unit tests. I'll see if I can document it, thanks.

I'm not good with unit tests. I'll see if I can document it, thanks.

@im-machakata No problem. What do you think of the new sign up page? Were you able to check it out?
The best place to add Front End documentation is the readme file in the frontend folder. We need to write the docs in such a way that anyone new to the project will know what pages and paths have been worked on. I suggest creating a section that lists the pages and the URL links to them using the following template as a guide:
Project Name
Project Description
Pages

Sign Up Page
Home Page

Sign up and Sign in functionality in the backend is implemented and needs to be hooked up to the frontend


Crash in 0.15 due to system ordering ambiguities

Using the lastest main and:
            PhysicsPlugins::default()
                .build()
                .disable::<IntegratorPlugin>()
                .disable::<SolverPlugin>()
                .disable::<SleepingPlugin>(),

I get the following crash:
   0: bevy_ecs::schedule::schedule::schedule
           with name=PhysicsSchedule
             at /home/alercah/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_ecs-0.15.0/src/schedule/schedule.rs:379
   1: bevy_ecs::system::function_system::system
           with name="avian2d::schedule::run_physics_schedule"
             at /home/alercah/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_ecs-0.15.0/src/system/function_system.rs:65
thread 'main' panicked at /home/alercah/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_ecs-0.15.0/src/schedule/schedule.rs:383:33:
Error when initializing schedule PhysicsSchedule: Systems with conflicting access have indeterminate run order.
25 pairs of systems with conflicting data access have indeterminate execution order.
Encountered a panic in system `bevy_app::main_schedule::FixedMain::run_fixed_main`!
Encountered a panic in system `bevy_time::fixed::run_fixed_main_schedule`!
Encountered a panic in system `bevy_app::main_schedule::Main::run_main`!

I can try to further minimize if need be.

This should be fixed by #577.


Error while building deployment on third party package installation

Hi, I'm trying to develop a wallet for tezos using npm package (npmjs.com/package/conseiljs). I have installed the package in an existing app(which is perfectly working in Zeit) and redeployed it without any code changes. It got failed during the build (https://zeit.co/clove/clove-wallet/3ft8v0a0i?redirect=1).
Steps to reproduce the error :
Take any working app or create-react-app
npm i conseiljs
deploy in Zeit

you may catch the error during deployment.
Please help me in fixing this?

I got an error Failed to initialize libusb. when I have require('conseiljs') in my build script.
Is there a reason you need to access a USB device?


"Xcode alone is not sufficient on Sierra" (again)

These steps don't always apply...
Please always follow these steps:

[X] Confirmed this is a problem with running a brew command and not brew installing or the post-install behaviour of one or more formulae? If it's a formulae-specific problem please file this issue at the relevant tap e.g. for Homebrew/homebrew-core https://github.com/Homebrew/homebrew-core/issues/new
[X] Ran brew update and retried your prior step?
[X] Ran brew doctor, fixed all issues and retried your prior step?
[no] Ran brew config and brew doctor and included their output with your issue?

To help us debug your issue please explain:

What you were trying to do (and why)

brew install <anything>

What happened (include command output)

I can't include command output. Sometimes you file the issue after you've fixed your problem.
Copied from: https://github.com/Homebrew/brew/pull/3453#issuecomment-350098129
The error message for this patch is terribly confusing and diverts people from the actual problem/solution.

brew: “Xcode alone is not sufficient on Sierra”

versus:

xcode-select: “command line tools are already installed”

There needs to be a proper distinction between "Xcode alone" vs "you don't have the latest SDK"...
Also, why do I need the latest SDK if I'm building for my current OS revision? Especially considering the SDK version doesn't determine build-ability? 99+% of the ports don't even touch the SDK, do they?

What you expected to happen

The thing to install, even tho my CLT doesn't include 10.13 (since I'm on 10.12 AND I'm trying to install something that doesn't even remotely touch the SDK (like heroku, which uses node).

Step-by-step reproduction instructions (by running brew commands)

Be on OSX < latest
Have Xcode + CLT installed and up to date for that version of OSX.
brew update
brew install heroku (or whatever)
sudo xcode-select --install
Get confused that 5 says that it is already installed.
Update Xcode
Get confused that there is STILL no update to CLT and 4 keeps erroring out.

I wound up having to sudo rm -rf /Library/Developer/CommandLineTools and re-running 5. A newer version does not show up in software update. Presumably because softwareupdate knows its up to date for my OS version?

Please don't file issues about problems you've already solved.

This problem isn't solved. The error message is wrong and deceiving. I had to dig into the code to figure it out that it was lying about the problem. Please reopen.

Besides, I'm not the only one with this issue. Why shouldn't I file an issue? It helps everyone.

@zenspider Your conduct on our issue tracker is not acceptable.

Please reopen this issue. zenspider's complaint is legitimate and I do not even begin to understand the treatment they're receiving. I see nothing rude or insulting about zenspider's ticket or subsequent response. This ticket was closed inappropriately; zenspider did not solve the issue they were complaining about, they merely fixed their local installation so they don't see the error anymore.


TypeError: this._throw is not a function

Any time I enter an incorrect stock symbol, I get this error:
TypeError: this._throw is not a function
Yet it still works when I give a correct stock symbol. Do you know how I can resolve this issue?

I got the same issue here. The issue is that the this scope is not working properly under the promise. This can be fixed by either referencing the proper root this, or you can just comment out the error handling and wrapping your code into a try/catch block.

I forked this repo and made changes to the error handling so you don't need to comment out the source code. I changed this._throw(9, error);  to reject("No hit with your query") on row 157 in dist/stocks.js. This might not be the correct way to solve the problem but it seems to work for me. The error message might be bad aswell. Feel free to comment better solutions!
You can install this package with this little change using npm install --save davidsoederberg/stocks.js.

I forked this repo and made changes to the error handling so you don't need to comment out the source code. I changed this._throw(9, error); to reject("No hit with your query") on row 157 in dist/stocks.js. This might not be the correct way to solve the problem but it seems to work for me. The error message might be bad aswell. Feel free to comment better solutions!
You can install this package with this little change using npm install --save davidsoederberg/stocks.js.

Your solution is better than mine. I just wrote a separate script that checked if the stock quote was valid before passing it to stocks.js.


Switch views

Is there an option to switch between views without closing or opening any? For example, from 1->2->3->4->5 to 5->1->2->3->4 (top view).

There is a method named replace works just like your requirement. But there is an issue with the method, so please wait until it is fixed. Thank you for using my library.


Add method to fetch movie details

Add method to fetch movie details

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (b9cc7aa) to head (f90eb18).

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #26   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines          228       262   +34
  Branches         6         6
=========================================
+ Hits           228       262   +34

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add support for termux118

This package is now a dependency of jsonschema v4.18.0,, and of jupyter notebook==7.
It takes time to compile rpds_py for source code,,which make problem when pip install notebook=7 in termux platform.
https://www.reddit.com/r/termux/comments/157mw29/comment/k6ibrlf/?utm_source=share&utm_medium=web2x&context=3
Would be possible to add a wheel for termux on Android in the repository's Github Action?
May this should be the problem of maturin..... instead of rpds......

I'd love to, but as far as I know, this still isn't possible. Specifically (and I'm being lazy and not looking for the issues to link you to, but you likely can find them yourself) Termux does not support any wheel ABI tags which PyPI allows uploading. You can check what it wants by running pip debug --verbose in your Termux environment, where you'll see that Termux is only supporting linux_aarch64 tags, which are nonstandard, and not supported by PyPI (because they don't work on most or even many linuxes in a standard way). The standard way is manylinux (or muslinux) wheels which are already supported.
My recommendation here is to either make use of one of a few "termux wheels" repositories which do allow uploading these nonstandard wheels, or to help discuss upstream what would be needed to standardize things so that Termux uses something PyPI can support uploads for (I'm not sure what the status of getting manylinux to work on Termux for example is).
Going to close given the above, but happy to hear follow-ups or to revisit when things improve upstream, though it's likely that when that happens things will work out of the box here.


dispatch some events

notify should dispatch event on returned object on closed, opened and clicked

I implemented those in my fork, which I made a pull request for: https://github.com/cgross/angular-notify/pull/15
If you need it before it is pulled into this repository check it out from: https://github.com/snrlx/angular-notify
I hope, it works as you expect :)


Twitter Feeds can be dragged into third party provider accounts

Once a Twitter feed is added to a local account it can be dragged into a Feedbin account (for example).
My understanding is that this should be restricted.

How do we want to handle the scenario where a user is dragging a Folder that has mixed Feeds where some are Twitter and some are Web Feeds? Should we allow the drag and error on the drop for the Twitter feeds (as happens today)? Should we disallow the drop all together?
Now that I think about it, do we even need handle this in the drag-n-drop code at all? You will get a "Feed Not Found" error if you do try to drop a Twitter feed on another type of account because it isn't a valid RSS feed. I feel like we are adding code for something that isn't a problem at all.

Even though Twitter is ending its free API, Twitter feeds will still exist in people’s subscriptions, even if they’re inert. That said, I’m not sure, though, that any special behavior is needed here. Needs more thought.


[Portal][base] Convert code to TypeScript

[x] I have followed (at least) the PR section of the contributing guide.

Converting Portal to Typescript - closes #34719

Please run yarn typescript locally and solve all the type errors.
Then, run yarn prettier to autoformat the code.

Please run yarn typescript locally and solve all the type errors. Then, run yarn prettier to autoformat the code.

I am on it. @michaldudak

I am working on resolving the comments today.

@akshaya-venkatesh8 can I work on this issue (https://github.com/mui/material-ui/issues/34719) as there is no recent activity in this pr

@sai6855 Since there was no response for a couple of days, feel free to start working on this.

Great thanks, I'll start.

Closing this in favor of #35657


Texture bug

Hi fewizz, how are you going?
I recently noticed a strange behavior ; when i break a block with an id higher than 4096 the micro-textures appear to look like something different from that block, like if you was breaking a totally different block.
Here are some example:

I don't know if there is something that can be done to fix this, like a client side visual fix; btw this is not fortunately a really bad issue.
I'm still using the last version of neid 1.4.3 that you gave me.

download latest version from curse

Is that still compatible with worldedit?

should


Restart CI for failed jobs

I am helping out with the QA process and applied a filter using status:failure and see over 1500 open PRs with red Xs indicating something failed.  The following types of errors are showing up in this list.
Unable to find './azure-pipelines.yml'

Travis CI errors involving folder names with upper case letters.
Example:

Warning: TODO - Define Testing.
Error:
Upper case characters found in 3D, all folder names must be lower case
Found in :
/home/travis/build/freeCodeCamp/freeCodeCamp/guide/english/3D

I know the one Travis CI error involving the folder issue can be resolved by manually restarting the build, because @Bouncey fixed the offending folders, but the sheer volume of these would be a pain to do manually.  Is there an automated solution to rebuild these?

Here is another error I am seeing:

@Bouncey @raisedadead Do you have any ideas for how we could do an automatic rebuild of these failing PRs? I think it would be worth the time to figure out such a way since this has come up a lot in the past and manually triggering these builds isn't a great use of our contributors' scarce time.

@Bouncey , @raisedadead I found travis-ci/travis.rb#344 on how to restart the build process for PRs which failed. This would make it so that no one has to manually restart the 1500+ PRs which have failed in the last 2 days due to the uppercase folder issues @Bouncey fixed earlier today. Not sure if this particular solution will work, but it gives me hope there is a way to automate these. Another option uses Python.

I manually restarted about 50 a few hours ago and about 20-30 this morning.  I finally decided to give up in hopes of an automated solution.

Sorry, I contributed to one of them by not having the file named index.md, which I think I understood after reading the log a second time. I was responding to the Hactoberfest mailing. I was perhaps being to hasty.

I have left a cron job running on a VM. The output from the machine is available over stream here: https://seashells.io/v/xQUVgC5E This might take a long long time.

The output may not make much sense, but I did use the Python script. It should be able to restart the builds. Let's see how it goes.

That said, I am afraid of hitting some limit or the other over 2000+ restarts.

The jobs are restarting. I hope in a few hours everything will be queued.

The restart of most buils is complete. 575 of them did not go thru.

@raisedadead What criteria was used to chose which of the 1500+ to rebuild?  I ask, because I am still seeing serveral which original failed for having uppercase names (i.e. the 3D and Tableau folders) which was fixed by @Bouncey.  It does not appear the builds for these PRs were restarted.
Here are two such examples:
https://github.com/freeCodeCamp/freeCodeCamp/pull/23772
https://github.com/freeCodeCamp/freeCodeCamp/pull/23771
Maybe another script could restart the build for these types?

Hi @RandellDawson
Firstly thanks a ton for spending so much time and efforts on the manual audit. 👏!
I'll try to clarify as much as I can for the benefit of all the @freeCodeCamp/moderators

...seeing several which original failed for having uppercase names...

These indeed need restarts or fixes as you already figured out. We have a test now, that will fail these for lack of correct naming of the files. This is a VALID failure. Lets discuss on the automation in our meeting later today.

...cancelled because the "Auto Cancellation" feature is currently enabled,...

I have enabled auto cancellation for PRs and branches to avoid the strain on the CI.
Two scenarios will cancel the builds on PR:

If a PR is closed without merge.
Fresh commits were added to the PR,

The previous build if pending to run will get cancelled. If additional commits are added the last job in the queue is run, which will correspond to the latest commit on the PR. This reduces the no of jobs on the CI.
A rare side-effect of this is: If a PR is accidentally closed and re-opened, then a restart is required. A moderator can do so when they notice it.

...Error: One or more locations are missing, all are required...

You would notice this is most likely to happen on PRs that have a merge conflict. We have merged a fix that will for the error. These PRs may have been made before the fix: https://github.com/freeCodeCamp/freeCodeCamp/pull/24587 and hence need a rebase. Which basically means either getting the conflicts to be resolved.
The best way to address this, is to ask the OP of the PR to close and re-open, since the files are conflicted anyways.

@raisedadead the following error has started popping up in some of the recent Travis failures:

Failed Tests: There were 6 failures
Use @each to Map Over Items in a List
✖ Your .blue-bg class should have a background-color of blue.
✖ Your .black-bg class should have a background-color of black.
✖ Your .red-bg class should have a background-color of red.
✖ Your .blue-bg class should have a background-color of blue.
✖ Your .black-bg class should have a background-color of black.
✖ Your .red-bg class should have a background-color of red.
total:     4015
passing:   4009
failing:   6
duration:  2m 29.6s

@Nirajn2311 @raisedadead recently solution for SASS challenge was added, but tests can't check a solution for SASS, only pure HTML/CSS/JS. I work on it and going to make PR soon.

As @Nirajn2311 commented I am getting same error for Travis CI

Use @each to Map Over Items in a List
  ✖ Your .blue-bg class should have a background-color of blue.
  ✖ Your .black-bg class should have a background-color of black.
  ✖ Your .red-bg class should have a background-color of red.
  ✖ Your .blue-bg class should have a background-color of blue.
  ✖ Your .black-bg class should have a background-color of black.
  ✖ Your .red-bg class should have a background-color of red.

PR #27608

@raisedadead the following error has started popping up in some of the recent Travis failures:

Failed Tests: There were 6 failures
Use @each to Map Over Items in a List
✖ Your .blue-bg class should have a background-color of blue.
✖ Your .black-bg class should have a background-color of black.
✖ Your .red-bg class should have a background-color of red.
✖ Your .blue-bg class should have a background-color of blue.
✖ Your .black-bg class should have a background-color of black.
✖ Your .red-bg class should have a background-color of red.
total:     4015
passing:   4009
failing:   6
duration:  2m 29.6s

Same error for CI for me

made a PR #27716

Guys, if the script has been run fully, #21951 hasn't rebuilt

@RandellDawson I noticed many of the PR's I've been removing have already been restarted to fix broken builds, which is awesome! Thanks for writing this script.
Do we still need this issue to stay open or can we close it?

@QuincyLarson I believe this issue has been resolved by this PR.  I will let @raisedadead make the final determination.


Generate the topology diagram

The agent failed to produce topology information for linked data and invocation information for the database

Emm... Can you give us more information? I can not get a clue from comment above.

Please refer to https://github.com/naver/pinpoint-c-agent/issues/34

Ok, thanks.


ImportError: DLL load failed: Une routine d’initialisation d’une bibliothèque de liens dynamiques (DLL) a échoué.

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):  Windows 10
TensorFlow installed from (source or binary):  ?
TensorFlow version: 2.1.0
Python version: 3.7
Installed using virtualenv? pip? conda?: pip
Bazel version (if compiling from source): ?
GCC/Compiler version (if compiling from source): ?
CUDA/cuDNN version: 10.2
GPU model and memory: NVIDA Geforce GTX 950, 2Go

**  the problem**
Hello I installed tensorflow this morning, but the import does not work. Can anyone help me here? Thx
import tensorflow as tf
Traceback (most recent call last):
  File "C:\Users\tgalt\AppData\Roaming\Python\Python37\site-packages\tensorflow_core\python\pywrap_tensorflow.py", line 58, in <module>
    from tensorflow.python.pywrap_tensorflow_internal import *
  File "C:\Users\tgalt\.p2\pool\plugins\org.python.pydev.core_<IP_ADDRESS>001101138\pysrc\_pydev_bundle\pydev_import_hook.py", line 24, in do_import
    module = self._system_import(name, *args, **kwargs)
  File "C:\Users\tgalt\AppData\Roaming\Python\Python37\site-packages\tensorflow_core\python\pywrap_tensorflow_internal.py", line 28, in <module>
    _pywrap_tensorflow_internal = swig_import_helper()
  File "C:\Users\tgalt\AppData\Roaming\Python\Python37\site-packages\tensorflow_core\python\pywrap_tensorflow_internal.py", line 24, in swig_import_helper
    _mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
  File "C:\Users\tgalt\AppData\Local\Programs\Python\Python37\lib\imp.py", line 242, in load_module
    return load_dynamic(name, filename, file)
  File "C:\Users\tgalt\AppData\Local\Programs\Python\Python37\lib\imp.py", line 342, in load_dynamic
    return _load(spec)
ImportError: DLL load failed: Une routine d’initialisation d’une bibliothèque de liens dynamiques (DLL) a échoué.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<input>", line 1, in <module>
  File "C:\Users\tgalt\.p2\pool\plugins\org.python.pydev.core_<IP_ADDRESS>001101138\pysrc\_pydev_bundle\pydev_import_hook.py", line 24, in do_import
    module = self._system_import(name, *args, **kwargs)
  File "C:\Users\tgalt\AppData\Roaming\Python\Python37\site-packages\tensorflow\__init__.py", line 101, in <module>
    from tensorflow_core import *
  File "C:\Users\tgalt\.p2\pool\plugins\org.python.pydev.core_<IP_ADDRESS>001101138\pysrc\_pydev_bundle\pydev_import_hook.py", line 24, in do_import
    module = self._system_import(name, *args, **kwargs)
  File "C:\Users\tgalt\AppData\Roaming\Python\Python37\site-packages\tensorflow_core\__init__.py", line 42, in <module>
    from . _api.v2 import audio
  File "C:\Users\tgalt\.p2\pool\plugins\org.python.pydev.core_<IP_ADDRESS>001101138\pysrc\_pydev_bundle\pydev_import_hook.py", line 24, in do_import
    module = self._system_import(name, *args, **kwargs)
  File "C:\Users\tgalt\AppData\Roaming\Python\Python37\site-packages\tensorflow_core\_api\v2\audio\__init__.py", line 10, in <module>
    from tensorflow.python.ops.gen_audio_ops import decode_wav
  File "C:\Users\tgalt\.p2\pool\plugins\org.python.pydev.core_<IP_ADDRESS>001101138\pysrc\_pydev_bundle\pydev_import_hook.py", line 24, in do_import
    module = self._system_import(name, *args, **kwargs)
  File "C:\Users\tgalt\AppData\Roaming\Python\Python37\site-packages\tensorflow_core\python\ops\gen_audio_ops.py", line 9, in <module>
    from tensorflow.python import pywrap_tensorflow as _pywrap_tensorflow
  File "C:\Users\tgalt\.p2\pool\plugins\org.python.pydev.core_<IP_ADDRESS>001101138\pysrc\_pydev_bundle\pydev_import_hook.py", line 24, in do_import
    module = self._system_import(name, *args, **kwargs)
  File "C:\Users\tgalt\AppData\Roaming\Python\Python37\site-packages\tensorflow\__init__.py", line 50, in __getattr__
    module = self._load()
  File "C:\Users\tgalt\AppData\Roaming\Python\Python37\site-packages\tensorflow\__init__.py", line 44, in _load
    module = _importlib.import_module(self.__name__)
  File "C:\Users\tgalt\AppData\Local\Programs\Python\Python37\lib\importlib\__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "C:\Users\tgalt\AppData\Roaming\Python\Python37\site-packages\tensorflow_core\python\__init__.py", line 49, in <module>
    from tensorflow.python import pywrap_tensorflow
  File "C:\Users\tgalt\.p2\pool\plugins\org.python.pydev.core_<IP_ADDRESS>001101138\pysrc\_pydev_bundle\pydev_import_hook.py", line 24, in do_import
    module = self._system_import(name, *args, **kwargs)
  File "C:\Users\tgalt\AppData\Roaming\Python\Python37\site-packages\tensorflow_core\python\pywrap_tensorflow.py", line 74, in <module>
    raise ImportError(msg)
ImportError: Traceback (most recent call last):
  File "C:\Users\tgalt\AppData\Roaming\Python\Python37\site-packages\tensorflow_core\python\pywrap_tensorflow.py", line 58, in <module>
    from tensorflow.python.pywrap_tensorflow_internal import *
  File "C:\Users\tgalt\.p2\pool\plugins\org.python.pydev.core_<IP_ADDRESS>001101138\pysrc\_pydev_bundle\pydev_import_hook.py", line 24, in do_import
    module = self._system_import(name, *args, **kwargs)
  File "C:\Users\tgalt\AppData\Roaming\Python\Python37\site-packages\tensorflow_core\python\pywrap_tensorflow_internal.py", line 28, in <module>
    _pywrap_tensorflow_internal = swig_import_helper()
  File "C:\Users\tgalt\AppData\Roaming\Python\Python37\site-packages\tensorflow_core\python\pywrap_tensorflow_internal.py", line 24, in swig_import_helper
    _mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
  File "C:\Users\tgalt\AppData\Local\Programs\Python\Python37\lib\imp.py", line 242, in load_module
    return load_dynamic(name, filename, file)
  File "C:\Users\tgalt\AppData\Local\Programs\Python\Python37\lib\imp.py", line 342, in load_dynamic
    return _load(spec)
ImportError: DLL load failed: Une routine d’initialisation d’une bibliothèque de liens dynamiques (DLL) a échoué.

Failed to load the native TensorFlow runtime.

Previous steps :
I had a problem of dll before this bug so I followed the log instrusction and I installed some stuff to have msvcp140_1.dll
then i notice I did not have CUDA installed so I installed cuda, then i got this bug.

@Thomas-Galtier
Could please downgrade the cuda version and try, please refer to this link to help you resolve the issue, please confirm if it helps.
below are list of similar issues
#36167 #36151 #36138 #36054 #36045 #36020 #36003 #35988 #35903 #35880 #35865 #35805 #35789 #35773 #35772 #35767 #35766 #35749 #35721 #35618 #35204#22823

I downgraded to CUDA 10.0. Now I have the error message ImportError: cannot import name 'audio' from 'tensorflow_core._api.v2' (C:\Users\tgalt\AppData\Roaming\Python\Python37\site-packages\tensorflow_core\_api\v2\__init__.py)

I tried cuda 10.0 and 10.1 it did not help.

@Thomas-Galtier
Did you install the Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, and 2019?
According to the docs at https://www.tensorflow.org/install/pip,
Install the Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, and 2019. Starting with the TensorFlow 2.1.0 version, the msvcp140_1.dll file is required from this package (which may not be provided from older redistributable packages). The redistributable comes with Visual Studio 2019 but can be installed separately:
Go to the Microsoft Visual C++ downloads,
Scroll down the page to the Visual Studio 2015, 2017 and 2019 section.
Download and install the Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 for your platform.
Make sure long paths are enabled on Windows.

Install the 64-bit Python 3 release for Windows (select pip as an optional feature).
Tensorflow 2.1.0 is compiled using MSVC 2019, which appears to require an additional DLL.

Yes i did. The msvcp140_1.dll is on my computer...

Is your python 64 bits? Does your CPU support AVX?
Closing as duplicate.
https://github.com/tensorflow/tensorflow/issues/36167#issuecomment-577886156
#36167 #36151 #36138 #36054 #36045 #36020 #36003 #35988 #35903 #35880 #35865 #35805 #35789 #35773 #35772 #35767 #35766 #35749 #35721 #35618 #35204

Sorry, closed by mistake. I see you already installed the latest MSVC.
So questions left to triage are: are you using a 64 bits Python? Does your CPU support AVX?

Yes its a python 64 bits. How do I know is my CPU support AVX?

@Thomas-Galtier
please let us know if this is still an issue

@Thomas-Galtier
please update as per above comment

I did not manage to make it work on windows so I switched to linux and it worked

Is there any update about this issue. I still have it and no able to use tensorflow. Thanks


managedresources/registry: improve stability in key ordering during serialization

How to categorize this PR?

/area quality
/kind enhancement
What this PR does / why we need it:
This PR enhances the managedresources/registry tests to ensure that map keys are ordered during serialization. It also copies the yaml.v2 package to the third_party directory and applies an upstream PR that fixes instability in key ordering. This fix is already included in yaml.v3 but it is not part of yaml.v2. We observed issues with inconsistent ordering after the merge of immutable secrets for managed resources which relies on the fact that encoding of k8s objects will be consistent. The inconsistent ordering of .meta.annotations and .meta.labels led to the continuous creation of managed resource secrets during reconciliation.
@rfranzke , thanks for reporting!
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

NONE

/assign
/hold
@dimityrmirchev and I are currently in discussion that this might not work in all cases.

/test pull-gardener-e2e-kind-migration

/retest-required

/approve


add static asserts for device iterators

resolves #392

I grepped for DeviceIterator in the code and added BOOST_STATIC_ASSERTs at all the places. It is possible that I might have missed some places as I am not intimately familiar with the codebase. Please let me know if there are places I have missed.

Actually, you missed all the places (algorithm) it needs to be and added it to one place (algorithm) that doesn't need that (copy handles all 4 cases: device->host, host->device, device->device, host->host).

 BOOST_STATIC_ASSERT(is_device_iterator<Iterator>::value); check would need to be added in all algorithms (except copy  or other if they already handle all cases) on the top level. For example:
template<class InputIterator, class OutputIterator, class UnaryOperator>
inline OutputIterator transform(InputIterator first,
                                InputIterator last,
                                OutputIterator result,
                                UnaryOperator op,
                                command_queue &queue = system::default_queue())
{
    BOOST_STATIC_ASSERT(is_device_iterator<InputIterator>::value);
    BOOST_STATIC_ASSERT(is_device_iterator<OutputIterator>::value);
    return copy(
               ::boost::compute::make_transform_iterator(first, op),
               ::boost::compute::make_transform_iterator(last, op),
               result,
               queue
           );
}

@jszuppe I have made the changes, the patch is still incomplete and needs more work. Pushing it so that you can have a look and let me know if what I am doing is correct. Will add asserts to remaining algorithms once you review this.

Well, at the first glance, I'd say it looks ok. I'll review it later this week. However, before merging I need to resolve https://github.com/boostorg/compute/issues/764 in develop branch.

@jszuppe Sure, no problem. I have completed the patch from my side.

Please rebase on develop.

Done

Coverage remained the same at 71.793% when pulling 7dfba4cca4e1b1babe1545c7243e1e3e7bc8cc56 on lakshayg:static_assert into 4650541e3b25d71073242a9757415140c2bb6705 on boostorg:develop.

In some places you removed detail::is_buffer_iterator<BufferIterator>::value in the 2nd commit, detail::is_device_iterator::value` wouldn't work there?

Done


ros2

Hi, I see that you have the ros2 version of the code, but there is no tutorial for running the code, can you please make the tutorial for the ros2 version public?

Hi,
Sorry, the migration is not yet complete.


case when unix_timestamp(xx) query data result wrong

Backend
VL (Velox)
Bug description
select plan_depart_tm, assigned_tm,case when (unix_timestamp(plan_depart_tm)-unix_timestamp(assigned_tm))/3600>=48  then -2 else 0 end from xx
2023-07-16 15:20:00     2023-07-07 09:24:25     0
Spark version
3.2.1
Spark configurations
No response
System information
No response
Relevant logs
E20230815 13:58:50.553767 325101 Exceptions.h:68] Line: ../../velox/functions/lib/DateTimeFormatter.cpp:1452, Function:buildJodaDateTimeFormatter, Expression:  Specifier A is not supported., Source: USER, ErrorCode: UNSUPPORTED
E20230815 13:58:50.553875 325101 Exceptions.h:68] Line: ../../velox/functions/lib/DateTimeFormatter.cpp:1452, Function:buildJodaDateTimeFormatter, Expression:  Specifier A is not supported., Source: USER, ErrorCode: UNSUPPORTED

@loukey-lj thanks for reporting, this commit may help to fix the issue on unix_timestamp, but it missed 1.0
https://github.com/oap-project/gluten/commit/6f6fd0dabb8df0bcde0c2b37a20fb9a5674093b1
Thanks, -yuan

We have solved it internally


after call to initControls(), removed AttributionControl still has listeners

When calling initControls the existing AttributionControl is removed and a new one created. But now any action which cause 'layeradd' to be fired will eventually call _update() on the removed AttributionControl, which throws an exception since this._map is null.
I tried this with firefox, on the master branch, and also on umap.openstreetmap.fr
Steps to reproduce:

Edit a user interface option, triggering the form's callback to initControls()

Set a custom map layer, triggering a call to initTileLayers(), which leads to the exception.
L.S.AttributionControl<._update@leaflet.storage.controls.js:427:1
L.Control.Attribution<.addAttribution@leaflet-src.js:8165:3
L.Control.Attribution<._onLayerAdd@leaflet-src.js:8206:4
L.Mixin.Events.fireEvent@leaflet-src.js:473:6
L.Map<._layerAdd@leaflet-src.js:2256:3
L.Map<.addLayer@leaflet-src.js:1713:4
.selectTileLayer@leaflet.storage.js:407:13
.initTileLayers@leaflet.storage.js:395:13
L.Storage.FormBuilder<.buildField/<@leaflet.storage.forms.js:700:17
L.Mixin.Events.fireEvent@leaflet-src.js:473:6
L.Storage.ElementHelper<.sync@leaflet.storage.forms.js:32:9
L.S.ElementHelper.BlurInput<.sync@leaflet.storage.forms.js:157:13
L.DomEvent.addListener/handler@leaflet-src.js:6403:11

I'm not sure where to clean up its listeners, though. I'm trying to call initControls in my import patch, #97, which breaks when I then call initTileLayers(). But like you can see above, it's also user-triggerable.

Thanks, I'll have a look :)


Resource requests and limits for components

We need to add resource requests and limits, for better management of the assigned CPU and memory, inside the Kubernetes cluster.

Capability is added with #2541


Update golang.org/x/crypto (CVE-2021-43565)

Version v0.0.0-20211202192323-5770296d904e of golang.org/x/crypto fixes
a vulnerability in the golang.org/x/crypto/ssh package which allowed
unauthenticated clients to cause a panic in SSH servers.
Reference:
https://github.com/golang/go/issues/49932
https://github.com/golang/crypto/commit/5770296d904e90f15f38f77dfc2e43fdf5efc083
https://bugzilla.redhat.com/show_bug.cgi?id=2030787
https://bugzilla.suse.com/show_bug.cgi?id=1193930
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-43565

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

Fixed CVE-2021-43565

I haven't found any docs on how CVEs are handled in KubeVirt. Shall we document it somehow or just mention in the release notes? @rmohr , @davidvossel , @vladikr , WDYT?

I haven't found any docs on how CVEs are handled in KubeVirt. Shall we document it somehow or just mention in the release notes? @rmohr , @davidvossel , @vladikr , WDYT?

The guide is here: https://github.com/kubevirt/kubevirt/blob/main/SECURITY.md. And if you click on the Security button of github you get here: https://github.com/kubevirt/kubevirt/security. Does that work for you?

/retest
/lgtm
/approve

@vasiliy-ul maybe add to the release note that we are not affected and just fix the reporting.

I haven't found any docs on how CVEs are handled in KubeVirt. Shall we document it somehow or just mention in the release notes? @rmohr , @davidvossel , @vladikr , WDYT?

The guide is here: https://github.com/kubevirt/kubevirt/blob/main/SECURITY.md. And if you click on the Security button of github you get here: https://github.com/kubevirt/kubevirt/security. Does that work for you?

Ooops... probably I need more coffee :) thanks for pointinting me to the docs

@vasiliy-ul maybe add to the release note that we are not affected and just fix the reporting.

sure

and our CI cache seems to be corrupted again. :/ Wiping it.

@vasiliy-ul maybe add to the release note that we are not affected and just fix the reporting.

Does it look better now?

Does it look better now?

Hm, I think it makes sense to write something like Updated the dependencies to include the fix for CVE-2021-43565, KubeVirt is not affected.

Does it look better now?

Hm, I think it makes sense to write something like Updated the dependencies to include the fix for CVE-2021-43565, KubeVirt is not affected.

Ah, you wanted to mention it explicitly... Updated.

/retest

Ah, you wanted to mention it explicitly... Updated.

Yes, but it is open for discussion. What do you think? I personally like when I see if a vulnerability affects my installation or if it is "just" a maintenance task.

Ah, you wanted to mention it explicitly... Updated.

Yes, but it is open for discussion. What do you think? I personally like when I see if a vulnerability affects my installation or if it is "just" a maintenance task.

I think it makes sense to mention if its 100% clear that the installation is not affected. With statically linked dependencies its not always obvious though if the vulnerable code path is triggered in some scenarios. So perhaps some caution is needed with the 'affected' statement.

/retest

/cherry-pick release-0.48
picking it for 048 because it also includes https://github.com/golang/go/issues/37278 which I want to have to connect to modern configured ssh servers.


add POINTERDOUBLETAP mask for BaseCameraPointerInput observer

Make observer of BaseCameraPointerInput check POINTERDOUBLETAP with respect of _pointerInput function that handles this type by call overrided onDoubleTap method

Also, I had problem with this file, because it has LF line endings 😕


Seg Fault at Startup

I installed a fresh copy of emirge onto my subshell, and when I tried to run the example files I kept getting Seg Faults, akin to the following. I am running Linux on a WSL subshell on my Acer laptop.
Choose platform:
[0] <pyopencl.Platform 'Portable Computing Language' at 0x7fcc00dd2008>
Choice [0]:
[ACER:08543] *** Process received signal ***
[ACER:08543] Signal: Segmentation fault (11)
[ACER:08543] Signal code: Address not mapped (1)
[ACER:08543] Failing at address: (nil)
[ACER:08543] [ 0] /lib/x86_64-linux-gnu/libpthread.so.0(+0x128a0)[0x7fcc046ee8a0]
[ACER:08543] [ 1] /lib/x86_64-linux-gnu/libc.so.6(__isoc99_fscanf+0x6d)[0x7fcc039ba2bd]
[ACER:08543] [ 2] /home/dshtey2/CEESD/heatMirge/emirge/miniforge3/envs/dgfem1/lib/libpocl.so.2.6.0(+0x6b117)[0x7fcc00d5d117]
[ACER:08543] [ 3] /home/dshtey2/CEESD/heatMirge/emirge/miniforge3/envs/dgfem1/lib/pocl/libpocl-devices-pthread.so(pocl_pthread_init+0xc3)[0x7fcc001812a3]
[ACER:08543] [ 4] /home/dshtey2/CEESD/heatMirge/emirge/miniforge3/envs/dgfem1/lib/libpocl.so.2.6.0(pocl_init_devices+0x699)[0x7fcc00d58479]
[ACER:08543] [ 5] /home/dshtey2/CEESD/heatMirge/emirge/miniforge3/envs/dgfem1/lib/libpocl.so.2.6.0(POclGetDeviceIDs+0x79)[0x7fcc00d352c9]
[ACER:08543] [ 6] /home/dshtey2/CEESD/heatMirge/emirge/miniforge3/envs/dgfem1/lib/python3.8/site-packages/pyopencl/../../../libOpenCL.so.1(clGetDeviceIDs+0x54)[0x7fcba2db9764]
[ACER:08543] [ 7] /home/dshtey2/CEESD/heatMirge/emirge/miniforge3/envs/dgfem1/lib/python3.8/site-packages/pyopencl/_cl.cpython-38-x86_64-linux-gnu.so(+0x5bfd9)[0x7fcba2b0afd9]
[ACER:08543] [ 8] /home/dshtey2/CEESD/heatMirge/emirge/miniforge3/envs/dgfem1/lib/python3.8/site-packages/pyopencl/_cl.cpython-38-x86_64-linux-gnu.so(+0x6e1be)[0x7fcba2b1d1be]
[ACER:08543] [ 9] /home/dshtey2/CEESD/heatMirge/emirge/miniforge3/envs/dgfem1/lib/python3.8/site-packages/pyopencl/_cl.cpython-38-x86_64-linux-gnu.so(+0x2ba91)[0x7fcba2adaa91]
[ACER:08543] [10] python3(PyCFunction_Call+0x54)[0x557f9ecb3a34]
[ACER:08543] [11] python3(_PyObject_MakeTpCall+0x31e)[0x557f9ecacb8e]
[ACER:08543] [12] python3(+0x1b028e)[0x557f9ed3928e]
[ACER:08543] [13] python3(_PyEval_EvalFrameDefault+0x4c93)[0x557f9ed5b053]
[ACER:08543] [14] python3(_PyEval_EvalCodeWithName+0x9be)[0x557f9ed377be]
[ACER:08543] [15] python3(_PyFunction_Vectorcall+0x378)[0x557f9ed384c8]
[ACER:08543] [16] python3(_PyEval_EvalFrameDefault+0x4c93)[0x557f9ed5b053]
[ACER:08543] [17] python3(_PyEval_EvalCodeWithName+0x9be)[0x557f9ed377be]
[ACER:08543] [18] python3(_PyFunction_Vectorcall+0x378)[0x557f9ed384c8]
[ACER:08543] [19] python3(PyObject_Call+0x5e)[0x557f9ecadaae]
[ACER:08543] [20] python3(_PyEval_EvalFrameDefault+0x21b1)[0x557f9ed58571]
[ACER:08543] [21] python3(_PyEval_EvalCodeWithName+0x2c3)[0x557f9ed370c3]
[ACER:08543] [22] python3(_PyFunction_Vectorcall+0x378)[0x557f9ed384c8]
[ACER:08543] [23] python3(_PyEval_EvalFrameDefault+0x92f)[0x557f9ed56cef]
[ACER:08543] [24] python3(_PyEval_EvalCodeWithName+0x2c3)[0x557f9ed370c3]
[ACER:08543] [25] python3(PyEval_EvalCodeEx+0x39)[0x557f9ed38149]
[ACER:08543] [26] python3(PyEval_EvalCode+0x1b)[0x557f9eddea3b]
[ACER:08543] [27] python3(+0x2722de)[0x557f9edfb2de]
[ACER:08543] [28] python3(+0x1277db)[0x557f9ecb07db]
[ACER:08543] [29] python3(_PyEval_EvalFrameDefault+0x92f)[0x557f9ed56cef]
[ACER:08543] *** End of error message ***
Segmentation fault

As an additional note, I have installed an earlier iteration of emirge and had no issues running the examples or making my own; this issue only started after downloading the most recent version.

As an additional note, I have installed an earlier iteration of emirge and had no issues running the examples or making my own; this issue only started after downloading the most recent version.

WSL1 or 2? (WSL1 is not supported.)

WSL1 or 2? (WSL1 is not supported.)

According to Powershell I am running version 2

According to Powershell I am running version 2

So, I find it a little suspicious that you used a new version of emirge, yet these errors appear to indicate that your code is still using an environment called dgfem - which I think has gone away some time back.
Every install of MIRGE-Com using emirge will install a whole new environment (called "ceesd", by default i think).  One needs to make sure to activate it by doing source emirge/config/activate.sh before running any examples.
Could you send along the output of conda env list?  Maybe it will provide some clues.

So, I find it a little suspicious that you used a new version of emirge, yet these errors appear to indicate that your code is still using an environment called dgfem - which I think has gone away some time back.
Every install of MIRGE-Com using emirge will install a whole new environment (called "ceesd", by default i think).  One needs to make sure to activate it by doing source emirge/config/activate.sh before running any examples.
Could you send along the output of conda env list?  Maybe it will provide some clues.

So, I find it a little suspicious that you used a new version of emirge, yet these errors appear to indicate that your code is still using an environment called dgfem - which I think has gone away some time back.

dgfem1 🙂 .
It was a fresh clone of emirge, Installed with ./install.sh --conda-prefix=<existing conda install> --env-name=dgfem1. The env was activated properly.

So, I find it a little suspicious that you used a new version of emirge, yet these errors appear to indicate that your code is still using an environment called dgfem - which I think has gone away some time back.

dgfem1 🙂 .
It was a fresh clone of emirge, Installed with ./install.sh --conda-prefix=<existing conda install> --env-name=dgfem1. The env was activated properly.

Here is my output:
# conda environments:
#
                         ~/Docs/emirge/miniforge3
                        ~/Docs/emirge/miniforge3/envs/dgfem
base                     ~/Docs/heatMirge/emirge/miniforge3
ceesd                    ~/Docs/heatMirge/emirge/miniforge3/envs/ceesd
dgfem                    ~/Docs/heatMirge/emirge/miniforge3/envs/dgfem
dgfem1                *  ~/Docs/heatMirge/emirge/miniforge3/envs/dgfem1
                         ~/miniforge3

Here is my output:
# conda environments:
#
                         ~/Docs/emirge/miniforge3
                        ~/Docs/emirge/miniforge3/envs/dgfem
base                     ~/Docs/heatMirge/emirge/miniforge3
ceesd                    ~/Docs/heatMirge/emirge/miniforge3/envs/ceesd
dgfem                    ~/Docs/heatMirge/emirge/miniforge3/envs/dgfem
dgfem1                *  ~/Docs/heatMirge/emirge/miniforge3/envs/dgfem1
                         ~/miniforge3

I would try installing a fresh env, ie. without --conda-prefix=<existing conda install>

I would try installing a fresh env, ie. without --conda-prefix=<existing conda install>

I suspect it might start working if he activates the new ceesd environment.

I suspect it might start working if he activates the new ceesd environment.

I suspect it might start working if he activates the new ceesd environment.

dgfem1 is the correct env. See above.

I suspect it might start working if he activates the new ceesd environment.

dgfem1 is the correct env. See above.

I would try installing a fresh env, ie. without --conda-prefix=<existing conda install>

@dshtey2 This might be worth a try. Just make sure to set your PATH so it picks up the new conda instead of the old one.

I would try installing a fresh env, ie. without --conda-prefix=<existing conda install>

@dshtey2 This might be worth a try. Just make sure to set your PATH so it picks up the new conda instead of the old one.

I'm suspecting this PR might be a part of the problem: https://github.com/illinois-ceesd/mirgecom/pull/200

I'm suspecting this PR might be a part of the problem: https://github.com/illinois-ceesd/mirgecom/pull/200

I would try installing a fresh env, ie. without --conda-prefix=<existing conda install>

@dshtey2 This might be worth a try. Just make sure to set your PATH so it picks up the new conda instead of the old one.

I just ran another fresh install, this time setting the PATH to the new conda directory, but to no avail

I would try installing a fresh env, ie. without --conda-prefix=<existing conda install>

@dshtey2 This might be worth a try. Just make sure to set your PATH so it picks up the new conda instead of the old one.

I just ran another fresh install, this time setting the PATH to the new conda directory, but to no avail


TS90010 error: Type 'Observable' is not assignable to type 'Observable'. Two different types with this name exists, but they are unrelated.

Hi
First of all, thanks for an excellent write up of Angular Model Pattern. I love it!
I just switched to using the npm module instead of just having a single file in my code, and now I'm getting this typescript error (followed the tutorial to the point). Anyone know's whats up?
private userModel: Model<Person>;
  public user$: Observable<Person>;

  constructor(private modelFactory: ModelFactory<Person>) {
    this.userModel = modelFactory.create(
      {
        id: null,
        createdAt: null,
        firstName: null,
        fullName: null,
        lastName: null,
        updatedAt: null
      }
    );
    this.user$ = this.userModel.data$;
  }

Hi ! It must be somehow two different versions of RXJS in use. Library uses "rxjs": "^5.4.2" What are you using ? Maybe we can make RxJS a peer dependency instead any ideas ?

Hi. Thanks for the prompt reply. I think this had to do with me upgrading typescript to the latest version - apparently there are stricter type checks there. See e.g. https://github.com/Microsoft/TypeScript/issues/16786
Not sure how to fix this long term, but for me it worked to make sure my package.json had the same versions of everything as the latest angular-cli (including typescript 2.3.x).
PS - not sure which RXJS I used, but I think it was 5.4.x at least
Cheers

So does it now work for you ? Without need to change ngx-model's version of RxJS ?

Yes it works when downgrading typescript to 2.3.4. I suspect that it'll reappear the moment angular switches to version 2.4+ though.
Feel free to close the ticket if you think it's better to look at it when/if it becomes a problems in later angular versions.
Cheers

Hey! Rxjs was moved to peerDependencies and version 2.0.0 was release can you please try it with that newer typescript in your project?


Support random() in batch queries

Is your feature request related to a problem? Please describe.
Handy for generating testing data.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

The corresponding setseed function seems non-trivial. Note the following query is actually deterministic:
test=# select case n when 1 then setseed(0.4) else null end, random() from generate_series(1, 10) as t(n);
 case |       random
------+---------------------
      |  0.6722690410337004
      |  0.9936586191615264
      | 0.19947461195735405
      |    0.90340354600701
      |   0.516998156895498
      |  0.7913052710048887
      |   0.531550972556847
      | 0.48302401286537666
      | 0.14525565255427209
      | 0.19221106009513123
(10 rows)

So what random() really does in PostgreSQL is mutating a session-level variable:
https://www.postgresql.org/docs/16/sql-set.html#:~:text=TO value.-,SEED,-Sets the internal
https://github.com/postgres/postgres/blob/REL_16_1/src/backend/utils/misc/guc_tables.c#L3695-L3704
https://github.com/postgres/postgres/blob/REL_16_1/src/common/pg_prng.c#L232-L234
Of course we can provide a weaker random() function first without the ability to generate deterministic sequence given a seed.
cc @wangrunji0408 may be more familiar with RNGs given experience working on madsim.

So what random() really does in PostgreSQL is mutating a session-level variable:

Of course we can provide a weaker random() function first without the ability to generate deterministic sequence given a seed.

Either LGTM.


sixth commit

fixed bullet points not displaying
made block links dark blue
removed section borders
made title backgrounds dark
added image to article title

:+1:


Python 2 to 3 Class Definition

In later versions of Python 2, it became popular to use the "new" class type, which meant switching from this class definition:
class Thing:

to this:
class Thing(object):

According to the setup.py file in this repo, this project is purely Python3.  In which case, the "new" class type is default, and this (object) is unnecessary.

Thanks! I had been using these as a sort of when's-the-last-time-someone-touched-this measure, but I think the time has come. Honestly, fewer than I'd have expected.

Yeah, it was only about 10% of the classes in the repo.
Also, if you're interested, I have a little Git/Bash script that you can run on a repo to see which files haven't been touched in the longest time:
https://antineutrino.net/2018/08/30/git-cleanup


Bump up version for release

For v0.4.0 release

Codecov Report

Merging #143 (fdd6a23) into master (107dd8e) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #143   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           20        20
  Lines          949       934   -15
=========================================
- Hits           949       934   -15

Impacted Files
Coverage Δ

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

pgmax/infer/bp.py
100.00% <0.00%> (ø)

pgmax/factor/factor.py
100.00% <0.00%> (ø)

pgmax/fgraph/fgraph.py
100.00% <0.00%> (ø)

pgmax/fgroup/fgroup.py
100.00% <0.00%> (ø)

pgmax/vgroup/vgroup.py
100.00% <0.00%> (ø)

pgmax/infer/bp_state.py
100.00% <0.00%> (ø)

pgmax/infer/bp_utils.py
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Help adding ImGui using CPM

Hello, I have tried using cpm to add the ImGui module to my c++ project.
Different methods I've tried.
CPMAddPackage(
  NAME imgui
  GITHUB_REPOSITORY ocornut/imgui
  GIT_TAG v1.88
)

CPMAddPackage(
  NAME imgui
  GITHUB_REPOSITORY ocornut/imgui
  VERSION 1.88
)

CPMAddPackage("https://github.com/ocornut/imgui/archive/refs/tags/v1.88.zip")

Thanks for any support you can give me :)

Correct me if I'm wrong, but I'm pretty sure ImGui does not come with any project file using any build system whatsoever. Given that, you'll likely have to create the targets yourself or add the sources to an existing one using the variable imgui_SOURCE_DIR that points to where CPM cloned it.

I use this:
<EMAIL_ADDRESS>
add_library(imgui STATIC
    ${imgui_SOURCE_DIR}/imgui.cpp
    ${imgui_SOURCE_DIR}/imgui_demo.cpp # optionally comment this out
    ${imgui_SOURCE_DIR}/imgui_draw.cpp
    ${imgui_SOURCE_DIR}/imgui_widgets.cpp
    ${imgui_SOURCE_DIR}/imgui_tables.cpp
)
target_include_directories(imgui INTERFACE ${imgui_SOURCE_DIR})
target_compile_definitions(imgui PUBLIC -DIMGUI_DISABLE_OBSOLETE_FUNCTIONS) # optional imgui setting
set_target_properties(imgui PROPERTIES FOLDER third-party) # optoinal IDE dir


Links not working across repos

See: https://github.com/Unibeautify/unibeautify/issues/208
The last comment where steven points to another repos issue is not linking

Bug Report Dump (Auto-generated)

Version 1.22.0<PHONE_NUMBER>)
Device: iPhone 6s (iOS 12.0.1)
TestFlight: false

Might be the dash?
Sent with GitHawk

Looking at this!

Thanks @BrianLitwin !

Sent with GitHawk

This is fixed.


Refactor/omnicompletion

This PR decouples the two modes of omnicompletion, make them easier to understand and reuse. It also adds additional tests and includes some minor improvements (see the particular commits).

Thanks!


Run CI on 1.x

Is your feature request related to a problem? Please describe.
We need to be running CI on main, and 1.xm, as they will be diverging (1.x will be 1.1 and main will be 2.0), including backward compatibility tests. In the future we'll want CI to automatically start running on 2.x.
Describe the solution you'd like
Make CI on main = CI on 1.x.

Can the CI be configured to run on any branch in addition to main that ends with .x so we don't have to keep creating issues to enable CI in 2.x, 3.x ... ?

@bbarani

This has a corresponding https://github.com/opensearch-project/opensearch-build/issues/39.

I believe this can be closed as a duplicate to https://github.com/opensearch-project/opensearch-build/issues/350.
@dblock thoughts?

I've renamed to "run gradle checks on 1.x"

I think we can close this issue - gradle checks currently run for any branch as long as 'start gradle check' comment is made on the PR.
I've opened a separate issue to make the gradle check job public.
We also have an existing issue for setting up randomized testing that will be branch specific.


fix: dwy specific env setup

This PR is a follow up to #773

[x] Addresses the issue in full
[ ] Addresses only certain aspects of the issue

Description
This PR adds the necessary arguments to doorway files for the LIMIT_CLOSED_LISTING_ACTION variable to be used correctly.
How Can This Be Tested/Reviewed?
This is best tested by a code review.
Author Checklist:

[ ] Added QA notes to the issue with applicable URLs
[ ] Reviewed in a desktop view
[ ] Reviewed in a mobile view
[ ] Reviewed considering accessibility
[ ] Added tests covering the changes
[ ] Made corresponding changes to the documentation
[ ] Ran yarn generate:client and/or created a migration when required

Review Process:

Read and understand the issue
Ensure the author has added QA notes
Review the code itself from a style point of view
Pull the changes down locally and test that the acceptance criteria is met
Either (1) explicitly ask a clarifying question, (2) request changes, or (3) approve the PR, even if there are very small remaining changes, if you don't need to re-review after the updates

Only other spot I thought about was config.yml but curious if we're trying to have all env vars in there or only those that are needed? Since I'm noticing a reduced set and tests passing, I did not include it but let me know if people think otherwise!


Set wrapped for Python 2

This makes ddt work like Python 3's functools.wraps, and also like mock on both Python 2 and Python 3.
I've been working on a nose plugin to clear attributes that might be leaking memory, and this makes it possible.

FYI @cpennington

Current coverage is 100% (diff: 100%)

Merging #45 into master will not change coverage

@@           master   #45   diff @@
===================================
  Files           1     1
  Lines         106   107     +1
  Methods         0     0
  Messages        0     0
  Branches        0     0
===================================
+ Hits          106   107     +1
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update 969c915...15c28ff

Thanks for this.

Wow, thanks for the speedy merge! Any chance of getting a new release?

I'll release later after son's bedtime protocol is over ;)

Just released as 1.1.1

Sweet! thanks so much.


[Candidate 1v1 Arizona Airfield ZH v1] Supply stashes to the left have wrong brightness

Issue Description
Supply stashes to the left have wrong brightness.
Expected behavior
Supply stashes have proper brightness level.
Screenshots
Bad

Good

Fixed - all trees removed. New version v2 will be on GR.org topic


Add Clouds to sky In Minecraft by user

Users can add light Clouds
option key on the keyboard 4 to change to light clouds
Right-click on the mouse to build as normal

Since 4 and 5 are used for another issue to build trees and leaves, I'll use 6 to clear light clouds!


Java's Abstract Syntax Tree (AST)

Proposed title of article
Java's Abstract Syntax Tree (AST)
Introduction paragraph (2-3 paragraphs):
The abstract syntactic structure of source code written in a programming language is represented as a tree.
The tree's nodes each represent a construct found in the original code.
Abstract syntax trees (ASTs) are data structures frequently used in compilers to represent the structure of program code. They have several applications in compilers. An AST is usually the outcome of a compiler's syntax analysis phase. It frequently serves as an intermediate representation of the program as it passes through the various phases that the compiler required, and it has a significant impact on the compiler's ultimate output.
Key takeaways:
-Traversing ASTs
-Transforming ASTs
-Printing ASTs
References:
N/A

Good topic @masese911  - approved. Please make sure your article is unique and adds value to what is available in the official documentation.


Is it possible to find not NULL column?

I am going to realize something like that:
SELECT * FROM country WHERE "housing" is not NULL
Can you help with it?

table = Table( ... )
query = Query.from_(table).select('*').where(table.housing.notnull())

@twheys notnull() is giving me the wrong query.
table = Table("Houses")
query = Query.from_(table).select("*").where(table.housing.notnull())

outputs the following
SELECT * FROM "Houses" WHERE NOT "housing" IS NULL

Getting the same error as @dashmug above.  I am trying to write "is not null" as well, is there any workaround for this at the moment?

I have a hacky workaround:
table = Table("Houses")
query = Query.from_(table).select("*").where(table.housing.notnull())
query_string = query.get_sql().replace('"housing" IS NULL', '"housing" IS NOT NULL')

But yeah, this is a blatant bug that needs to be fixed ASAP

This shouldn't make a difference. NOT (foo IS NULL) and foo IS NOT NULL should return the same thing. The parentheses are only added for the sake of clarity, but are not necessary I believe.

You can run a query like this to check and see it returns nothing:
(select housing from Houses where not housing is null)
intersect
(select housing from Houses where housing is not null);


Add tests

It is important to figure this out soon, so that new code that goes in will see a precedent that they should be using tests.

Despite my best efforts -- 3 grueling days of deep diving into IJ test framework code -- I've come to the conclusion that tests simply aren't worth it at this point.
I tried creating IJ light tests, but those are super hacky. They barely resemble a real project, and there's no trivial way, or at least clearly documented way, to add dependencies on real libraries (which I wanted to do with Kobweb stuff). They are also single module projects only, and I am sure I will want to test multi-module projects soon.
I tried creating an IJ heavy test using Gradle, but that was a failure as well -- I simply could not figure out how to get the Gradle project to sync and not leak resources. All the example code online I could find with IntelliJ Gradle tests used internal helper methods that were not available to mere mortals like myself.
So at this point, I'm just going to lean on manual QA for now. The Kobweb plugin is relatively small and probably will be for its lifetime. Most of (all of?) its actions will all be isolated into one-off commands that will just work or they won't.
I'm very sad about this but my time as a solo dev is limited and I'm already fighting the IJ APIs enough just to get the plugin working :) The test framework is very bad -- it's a relic of the past with random fixtures and fixture settings all over the place that you have to magically know how to set, and even then, things don't quite work sometimes. The original way that JB tested their stuff using JUnit3 is awful, and it pervades almost all of their tests to this day. Booooo.

Oh well intellij being intellij again


Add 'SocksSocket' to SOCKS5

A part of  #1006

Thanks. Did you take a look at my last comment in #1006? I don't think we want/need to subclass socket.socket.


Create install/update script

scrip should be able to follow installation steps with ability to parametrise configuration
It should receive URL param to patch REACT_APP_API_URL and APP_FRONTEND_URL in .env file
and params for api/ui/migration image  in docker-compose.yml
if possible add checks if docker and docker-compose are installed
Install scenario
download default docker-compose.yml
download default .env
patch .env
start
Update scenario
stop containers
patch docker-compose.yml
start

I'll take a look.

As for update scenario. I think it is mote suitable to give an update option to the user. For a full update - it is possible to re-run setup script. For a custom image update - it can be done manually and saved in version control system - so it's trackable.

I've had a go at completing Alex's work in #159.


Invalid xml file : optArguments_new.xml

Dear,
I do get this error systematically when I run runBNG, for and xml file that should be made by runBNG i suppose. But when I want to look at this file, the file itself doesn't exists.
ERROR: Invalid xml file /scratch/popmet_tmp/BDG_205/BIONANO/refaln/optArguments_new.xml: StartTag: invalid element name, line 115, column 10 (line 115)
Stephane
the whole error log:
========================================== De novo assembly starts =============================================
Start date: Fri Aug 20 16:23:44 CEST 2021
The data generation platform is: irys
The bnx file is: /scratch/popmet_tmp/BDG_205/BIONANO/INRAE_Pnigra_BDG_Div7_raw.bnx
The digested reference is: polished_genome_CTTAAG_20kb_5labels.cmap
The minimum molecule length is (Kb): 100
The minimum label on a molecule is: 8
Maximum backbone intensity is: 0.6
The path to Bionano Solve folder is: /home/strom/bin/bionano/pipeline/Solve3.6.1_11162020
The path to Bionano RefAligner folder is: /home/strom/bin/bionano/pipeline/Solve3.6.1_11162020/RefAligner/11442.11643rel
The number of threads is: 8
Large jobs maximum memory (GB) is: 128
Small jobs maximum memory (GB) is: 8
The number of threads for each subjob is: 2
The number of iterations is: 5
False Positive Density (/100Kb) [FP]: 2.0
False Negative Rate (%/100) [FN]: 0.10
ScalingSD (Kb^1/2) [sd]: 0.0
SiteSD (Kb) [sf]: 0.1
RelativeSD [sr]: 0.03
The genome size (Mb) is: 420
The xml file is: /home/strom/bin/bionano/pipeline/Solve3.6.1_11162020/RefAligner/11442.11643rel/optArguments_nonhaplotype_irys.xml
The output directory is: refaln
Prerun Tests:
1 ERRORS
0 WARNINGS
Disabling autoNoise during rough Assembly
ERROR: Invalid xml file /scratch/popmet_tmp/BDG_205/BIONANO/refaln/optArguments_new.xml: StartTag: invalid element name, line 115, column 10 (line 115)
Pipeline Version: $Id: Multithreading.py 11646 2020-09-25 16:50:59Z Elam $
EXITING: See errors
End date: Fri Aug 20 16:23:47 CEST 2021
===============================================================================================================

Hi @stephrom,
As you used the old bionano data, you may try runBNG v1.03, which can be found in Releases
The old bionano scripts and tools can be found at http://doi.org/10.5281/zenodo.4661675


Extended XP bar

The XP bar can go above the limit to level up because in order to level up the player has to do the Level up move. If the character has more experience points than the limit to level up, the excess will be added to the amount of experience that the character has on the new level.
But on the app, the XP bar cannot go above the limit and the only option, for now, is to level up immediately when the character reaches that limit.

Definitely room for improvement for that whole area. I'm considering adding something like a session log, with ability to mark XP, which will work out most of the logic there (something like "pending" XP points that will transfer once "session over" is used)

Fixed in v2.0


SEEDSDT-1030

add additional settings for pages that have menu icons. Added icon for no upcoming events when that page will be use in case of no events.

@jdeanquin-dg  @ginchauspe  The corresponding ticket will remain open because there are WP changes will have to be made once our code is deployed to production.


Rename IMG_20240722_181217.jpg to excel_certificate.jpg

if you want to upload your certificate , accept my pull request.

accept pull request


liveview 0.17 support introduces compile time dependencies

I believe https://github.com/surface-ui/surface/blob/master/lib/surface/base_component.ex#L62 introduces various compile time dependencies. I just cleaned up my project to get rid of the troublesome so-called "compile-connected" dependencies and with the latest version (as of time of writing this is d80b3e347537d07990d7cd2d3be7495a2af1fad1) many compile dependencies returned.
Is there another way to implement liveview 0.17 support without the need for these require statements? Maybe generate another module at compile time to avoid requiring the original module?

Hi @dvic!

I believe https://github.com/surface-ui/surface/blob/master/lib/surface/base_component.ex#L62 introduces various compile time dependencies.

Yes. Currently, module components (as opposed to pure function components ) must be defined as compile-time dependencies so we can do static checking based on the information introspected from those components. This has always been the case. One exception recently discovered was that if you're using Surface, running on elixir v1.13, due to some compiler optimizations, some of those dependencies will not be created, bringing a bunch of problems. That was the reason we needed to change the way we force the dependencies in BaseComponent.

Is there another way to implement liveview 0.17 support without the need for these require statements? Maybe generate another module at compile time to avoid requiring the original module?

Yes. I'm already working on a unified Declarative API for both Surface and Liveview that will introduce a separate compiler that will do those checks without the need to add compile-time dependencies. Until then, we need those dependencies.
Besides the created dependencies (which is expected), are you facing any other issue? Errors? Warnings? Out-of-sync modules?, etc.

Yes. Currently, module components (as opposed to pure function components ) must be defined as compile-time dependencies so we can do static checking based on the information introspected from those components. This has always been the case. One exception recently discovered was that if you're using Surface, running on elixir v1.13, due to some compiler optimizations, some of those dependencies will not be created, bringing a bunch of problems. That was the reason we needed to change the way we force the dependencies in BaseComponent.

We are indeed on Elixir 1.13. Not sure how it was done before, but surface 0.6 did not introduce compile dependencies when I call a component inside another component (reported by mix xref trace).

Besides the created dependencies (which is expected), are you facing any other issue? Errors? Warnings? Out-of-sync modules?, etc.

I haven't had a lot of time to play around with it so can't say anything on that but so far I haven't encountered any issues. The only thing that affected us is that we had some selectors on phx-click in our tests and this of course also changed with the JS API, but that was an easy fix.
But in terms of impact of this change: changing one file required previously 42 files to be compiled, I worked a full day to get this down to one file and I succeeded (eliminating all troublesome compile-connected dependencies). I just checked with the latest version of Surface: it's now compiling 150 files 😅.
We do have a large project and I have to evaluate how this impacts day-to-day development but at a first glance it's not looking good. Before my refactoring, we had around 150 of these "compile-connected" dependencies, after my refactoring it was down to 0 (ignoring some valid compile-connected dependencies), and now it's back up again to 692 dependencies.

We are indeed on Elixir 1.13. Not sure how it was done before, but surface 0.6 did not introduce compile dependencies when I call a component inside another component (reported by mix xref trace).

Surface 0.6 should introduce the same compile-time dependencies in elixir < 1.13.

I just checked with the latest version of Surface: it's now compiling 150 files...
...we had around 150 of these "compile-connected" dependencies, after my refactoring it was down to 0 (ignoring some valid compile-connected dependencies), and now it's back up again to 692 dependencies.

Do those dependencies make sense? I mean, are those 150 files defining components that inject the same component you're changing? If not, please let me know. It could be a bug.

Surface 0.6 should introduce the same compile-time dependencies in elixir < 1.13.

I just checked and I can confirm that it doesn't (both on 1.12 and 1.13), the command I'm running is: mix xref trace my_file.ex --label compile.

Do those dependencies make sense? I mean, are those 150 files defining components that inject the same component you're changing? If not, please let me know. It could be a bug.

Yes this particular example makes sense, it's not a bug, this was the sidebar component (on almost all live views) :)
But the problem is also in other places: changing something in one of our contexts context -> 151 files (before: 1 file). This is something that I expected because of the nature of these "compile-connected" dependencies. Just to be clear: what I mean with this is to depend at compile-time on something that has a large runtime dependency tree below itself. We have a few components that are used across the system (storing phones, emails, URLs) that especially cause problems in this situation. When every component introduces a compile-time dependency you automatically have to recompiled if any of it's runtime dependencies change.

@dvic if that has become something really annoying in terms of compilation time, there are a few things you could do to improve the situation until we introduce the new API. For instance:

Identify the most critical dependencies (the ones that most commonly triggers those recompilations)
Convert some of them into function components. The downside is that by doing this you lose any compile-time check, however, it might be worth it until we release Liveview v0.18 and Surface v0.8, which should be the first versions with the new API.

We may also release a patch version before v0.8 that could do some optimization in that regard. We had to start with a very conservative approach to guarantee that the information we have about the dependencies are up-to-date but there's room for improvements even before the new API is released. We'll start checking on that as soon as we release v0.7 this week.

@dvic if that has become something really annoying in terms of compilation time, there are a few things you could do to improve the situation until we introduce the new API. For instance:

Identify the most critical dependencies (the ones that most commonly triggers those recompilations)

Convert some of them into function components. The downside is that by doing this you lose any compile-time check, however, it might be worth it until we release Liveview v0.18 and Surface v0.8, which should be the first versions with the new API.

Thanks for the suggestion, will definitely consider that!

We may also release a patch version before v0.8 that could do some optimization in that regard. We had to start with a very conservative approach to guarantee that the information we have about the dependencies are up-to-date but there's room for improvements even before the new API is released. We'll start checking on that as soon as we release v0.7 this week.

Good to hear! Looking forward to the v0.7 release :)

Just an update: unfortunately we've not been able to upgrade yet (the suggestions did not help enough to significantly reduce the compilation times).

We may also release a patch version before v0.8 that could do some optimization in that regard. We had to start with a very conservative approach to guarantee that the information we have about the dependencies are up-to-date but there's room for improvements even before the new API is released. We'll start checking on that as soon as we release v0.7 this week.

Now that v0.7 is released, are there any concrete plans for improving this aspect of v0.7? If there is anything I can do to help, please let me know. We would love to switch to Surface 0.7 / LV 0.17 :)
Out of curiosity, one more thing about something you previously mentioned:

Currently, module components (as opposed to pure function components ) must be defined as compile-time dependencies so we can do static checking based on the information introspected from those components. This has always been the case.

I just double checked, and Surface v0.6 does not create compile-time dependencies, at least for the sample of (live) components in our project I tried this (using mix xref trace). Are there particular conditions in which case these dependencies were created that you know of?

Hey @dvic!
I started to isolate the cases where we actually need a compile-time dependencies between components. So far, I found these:

Using macro components
Using components implementing the translate/2 callback
Components using contexts
Components receiving props or slots

The one with greatest impact is certainly #4 so it will be the first to be addressed by moving all static validations regarding props and slots to the surface compiler, which only runs after compilation.

Hey @dvic!
I started to isolate the cases where we actually need a compile-time dependencies between components. So far, I found these:

Using macro components
Using components implementing the translate/2 callback
Components using contexts
Components receiving props or slots

The one with greatest impact is certainly #4 so it will be the first to be addressed by moving all static validations regarding props and slots to the surface compiler, which only runs after compilation.

Awesome! Let me know if you want me to try out some version of this wip on our big project to see the effect in practice (or in any other way I can help).

Hi @msaraiva! One question: are the changes you have planned regarding #4 dependant upon https://github.com/phoenixframework/phoenix_live_view/pull/1747? If so, do you have any idea if there's a timeframe for merging that PR? (it's been open since november) We're reassessing our decision not to upgrade (we're encountering more and more lv 0.16/0.17 dep incompatibilities) but before we do that I thought to ask about the latest updates/plan.
Thanks! And once again, if there's anything I can do to help please let me know!

Hi @dvic!

are the changes you have planned regarding #4 dependant upon https://github.com/phoenixframework/phoenix_live_view/pull/1747?

No. They can be done independently. As a matter of fact, we already started working on #4. We should have a PR for that one very soon.

Just wondering if we will see more on this when LV 0.18 drops?

https://github.com/surface-ui/surface/pull/653
seems to be fixed with this @dvic (at least for me and a few other users on Slack).
this will be released independently of LV 0.18

#653
seems to be fixed with this @dvic (at least for me and a few other users on Slack). this will be released independently of LV 0.18

Yup, fixes it for us as well! Major win 🎉

Fixed in https://github.com/surface-ui/surface/pull/653


Updated ViralConsensus to v0.0.5

@robertaboukhalil Woops, thanks for catching that! Will do ASAP. Should I also add v0.0.4, which is also in its own branch on the ViralConsensus repo?

It's not required, but if you want it to be accessible on the CDN, then yes please!

Great, thanks! Just added it to this PR

Also realized that I didn't add example files for 0.0.4 and 0.0.5, so I just added those now. So hopefully should be good to go! Please let me know if you need anything else

Just fyi this is erroring out: https://github.com/biowasm/biowasm/issues/97, I'll investigate it more closely later this week


chore: bdd-nh-1590065484 to 0.0.1

chore: Promote bdd-nh-1590065484 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Enhancement: Additional Libraries via Options

The ability to use other Javascript libraries will be important in the future, as OpenJSCAD.org matures in functionality and popularity. Currentlly, Processor.addLibrary(path) is available but there are some alternatives.

Support 'libraries' as an option to OpenJsCad.Processor()
Support 'libraries' as an option to Processor.setJsCad()
Support a callback routine on Processor, allowing other routines to execute JUST BEFORE eval() is called.
A combination of the above

Closing as enhancements were made with release 0.5.0

Support 'libraries' as an option to OpenJsCad.Processor()
Support additional 'libraries' via Processor.addLibrary(library)

Note: This only applies to asynchronous processing of JSCAD scripts.