feat(examples): add example-with-typeorm

This pull request introduces a new typeorm-service package to the official TurboRepo examples. The aim is to demonstrate the implementation of a robust service layer using TypeORM with a custom dependency injection (DI) mechanism. This example is designed to help developers integrate a more structured backend architecture with their existing Next.js applications, leveraging TypeORM for ORM capabilities.

Hi,
Thank you for your feedback. I have addressed the issues you mentioned:
Fixed the build, test, and lint commands so they now work out of the box.
Upgraded Turborepo to version 2 using npx @turbo/codemod upgrade.
Please let me know if there are any other changes or improvements needed.
Thank you! @anthonyshew

I'm still seeing a lot of errors when I run turbo test.

I'm still seeing a lot of errors when I run turbo test.
This issue occurs because the example user might not have verified the database connection configuration before running the test code.
To address this, I added a comment in the test code:
/**
 *
 * If you have correctly configured the database connection information in 'packages/typeorm-service/src/orm-config.ts',
 * remove this skipIf statement and run the tests.
 */

const todoService = inject(TodoService);

suite.skipIf(true)("Todo", () => {
  let id: Todo["id"];

  test("Insert", async () => {
    const newTodo = await todoService.add("Hello World");

    id = newTodo.id;

    expect(newTodo.complete).toBeFalsy();
  });
});

Additionally, for example users, I have updated the README to include instructions on entering database connection information and provided a MySQL Dockerfile and execution script.
Thank you for your(@anthonyshew ) comment. I have been waiting for your feedback and appreciate you reaching out.

I'd prefer to have these be unit tests, mocking the database call. Is that something you could do?

Allow CI Workflow Run

[ ] approve CI run for commit: 89fac8b92c58da19578510abb9f9cc8f57c72872

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer


About ctx scheduler design

EpollProactor::Run
while (true) {
    task_queue_
    epoll_wait
    algo->SuspendIoLoop // suspend
}

We know that FiberSchedAlgo::main_cntx_ is inserted into the FiberSchedAlgo::queue_ when FiberSchedALgo::rqueue_ is
empty or IoLoop busy(https://github.com/romange/helio/blob/124e97a30e854e0305277e8d80b1b575612181d0/util/fiber_sched_algo.cc#L50)
Why not replace suspend with yeild. It seems to have no impact on performance and better readability.

Hi @hankai17 . I did not understand, where you suggest replacing suspend with yield?


Ensure that manager services are up & running

Depending on the used network the docker-compose units fail to start because of missing network connection.
Add a post unit after the startup of the system finished to ensure that all services are up and running.
Feb 04 16:57:32 manager docker[30305]: Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io: Temporary failure in name resolution
Feb 04 16:57:32 manager systemd[1]<EMAIL_ADDRESS>Control process exited, code=exited, status=18/n/a
Feb 04 16:57:32 manager systemd[1]<EMAIL_ADDRESS>Failed with result 'exit-code'.
Feb 04 16:57:32 manager systemd[1]: Failed to start manager service managed by Docker Compose.

Workaround:
sudo systemctl start docker-compose@traefik
sudo systemctl start docker-compose@phpmyadmin
sudo systemctl start docker-compose@openstackclient
sudo systemctl start docker-compose@homer
sudo systemctl start docker-compose@netbox
sudo systemctl start docker-compose@manager

Fixed with c2175729db34ae1f1975f3275d671ab089694250


WIP Hetzner private networking

Signed-off-by: Artiom Diomin<EMAIL_ADDRESS>Hetzner private networking

WIP because we also need to add hetzner private networking support to machine-controller

This PR is currently blocked as Hetzner CCM doesn't support private networks
https://github.com/hetznercloud/hcloud-cloud-controller-manager/issues/19
https://github.com/hetznercloud/hcloud-cloud-controller-manager/pull/20
There is a WIP PR to implement Hetzner Networks for machine-controller
https://github.com/kubermatic/machine-controller/pull/627

This issue is not anymore blocked as we have a new release of both machine-controller and Hetzner CCM.
/remove-lifecycle blocked

/hold
I haven't pushed and tested a fix for CCM flags

/hold cancel

/lgtm

/retest


Mini cart header title and close button

Is it possible to add a header with a title and close button to the mini cart like the cart drawer?

@chris-charle everything is possible, you have liquid source file, did you try to make it your self?

@chris-charle everything is possible, you have liquid source file, did you try to make it your self?


TypeError: expected string or bytes-like object in nominatim API client

Describe the Bug

Steps to Reproduce

Go to https://admin.integreat-app.de/testumgebung-reg/pois/de/new/
Input something ?
Submit form
See error

Expected Behavior

A POI should be created and the coordinates should correctly be retrieved from the nominatim api
Actual Behavior

An internal server error occurs
Additional Information

Traceback
Oct 30 09:30:52 ERROR   django.request - 500 Internal Server Error: /testumgebung-reg/pois/de/new/
Traceback (most recent call last):
File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/django/core/handlers/exception.py", line 47, in inner
  response = get_response(request)
File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 181, in _get_response
  response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/django/views/generic/base.py", line 70, in view
  return self.dispatch(request, *args, **kwargs)
File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/django/utils/decorators.py", line 43, in _wrapper
  return bound_method(*args, **kwargs)
File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/django/contrib/auth/decorators.py", line 21, in _wrapped_view
  return view_func(request, *args, **kwargs)
File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/django/views/generic/base.py", line 98, in dispatch
  return handler(request, *args, **kwargs)
File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/django/utils/decorators.py", line 43, in _wrapper
  return bound_method(*args, **kwargs)
File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/django/contrib/auth/decorators.py", line 21, in _wrapped_view
  return view_func(request, *args, **kwargs)
File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/integreat_cms/cms/views/pois/poi_form_view.py", line 166, in post
  if not poi_form.is_valid() or not poi_translation_form.is_valid():
File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/django/forms/forms.py", line 175, in is_valid
  return self.is_bound and not self.errors
File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/django/forms/forms.py", line 170, in errors
  self.full_clean()
File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/django/forms/forms.py", line 373, in full_clean
  self._clean_form()
File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/django/forms/forms.py", line 400, in _clean_form
  cleaned_data = self.clean()
File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/integreat_cms/cms/forms/pois/poi_form.py", line 164, in clean
  latitude, longitude = nominatim_api_client.get_coordinates(
File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/integreat_cms/nominatim_api/nominatim_api_client.py", line 134, in get_coordinates
  if result := self.search(street=street, postalcode=postalcode, city=city):
File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/integreat_cms/nominatim_api/nominatim_api_client.py", line 80, in search
  query_dict["street"] = re.sub(
File "/usr/lib/python3.9/re.py", line 210, in sub
  return _compile(pattern, flags).sub(repl, string, count)
TypeError: expected string or bytes-like object

This is not a new bug, but seems to exist for a while and just occurs in some edge cases.

I tried to find out what the two municipalities did on that date to exactly reproduce it. It only helped me a bit. I noticed that they tried to create

a POI from the event form
a POI without an exact address number (street name 22-24)
a POI in the others category

But I still wasn't able to reproduce it. Maybe one other person can try to reproduce it, and then it might be best to ask the service to ask the municipalities what they were trying to do? :/

It would also be interesting to know who tried to create a poi in the testumgebung today at 09:30:52 UTC...

testumgebung-reg? That would have been me. Why? Did the problem occur at time again?

testumgebung-reg? That would have been me. Why? Did the problem occur at time again?

Yes, this was the original reason why I created the ticket, see the initial traceback of the bug

Ah no, then it wasn't me. I started to reproduce it just after you created the issue. Must have been more like 11:40 then. Ok, then I'm not able to reproduce it

How to reproduce: space in "Street and house number"


Asynchronous, not blocking cache updates don't seem to trigger a UI update

I'm calling a non-blocking async function from a few different client side mutations. The function gets called, the write gets called, the data seems to make its way into the store; however, the UI ends up not updating. Here's what my code looks like:
const asyncSave = debouce((cache, profileId) => {
  fetchgql(...).then(({ data }) => {
    cache.writeData({ id: `Profile:${profileId}`, data: { ... } });
  });
}, 2000, { trailing: true });

...
Mutations: {
  resolverA: (_, { profileId }, { cache }) => {
    ...
    asyncSave(cache, profileId);
    return null;
  },
  resolverB: (_, { profileId }, { cache }) => {
    ...
    asyncSave(cache, profileId);
    return null;
  }
}

So both resolverA and resolverB both call this asyncSave method. Eventually calls stop getting made to asyncSave and 2 seconds later we'll actually call the function. This works, the write works, but after the write, the UI does not update. If I then do something minor in the UI that would trigger a store update, then the update does indeed appear to work.
My guess (without reading the internal apollo code), is that UI updates get triggered after mutations "resolve". However, independent cache updates may not cause re-renders. Is this true? Is there anything else to be done here to make a technique like this work?

@parris  You should include your versions of apollo-cache-inmemory and apollo-client. A lot of changes int those libraries recently that have affected some of what your talking about

@carllippert here are the versions:
   "apollo-cache-inmemory": "^1.2.9",
    "apollo-client": "^2.4.1",
    "apollo-link": "^1.2.2",
    "apollo-link-context": "^1.0.8",
    "apollo-link-http": "^1.5.4",
    "apollo-link-state": "^0.4.1",
    "apollo-local-query": "^0.3.1",

I'm upgrading everything now.

This could be better now - it appears to work a bit better but I can't fully test. The upgrades undid some monkey patching I had done to use immutablejs - hoping link state 1.0 helps with this. Should we close or should we wait?

@parris - just FYI. link-state was merged into Apollo client as of 2.5.0 alpha, so there is no stand-alone link-state any more. There won't be a 1.0. It's in 2.5.0. Not sure you knew that from the comment. :)
Scott

@smolinari I'm not seeing that... what am I missing? Where was it merged in?

@maxschmeling - Here: https://github.com/apollographql/apollo-client/pull/4155
Scott

Thanks @smolinari
I'm going to upgrade to the alpha and see if it fixes my issues with never being able to read updates to the local state data until the app is reloaded.

@maxschmeling
That PR hasn't yet been merged, so I wouldn't expect much currently until it is.
Scott

@smolinari the last comment says it's all .currently available in the alpha release. Hopefully that's true.
https://github.com/apollographql/apollo-client/pull/4155#issuecomment-446041242

Hmm.. ok. Then have at it! :smile:
Scott

I think this is resolved - closing!


FR: Assumed roles by updating the X-Amz-Date header

At the moment, if we have a request with an old X-Amz-Date header, it will receive an expiry error from AWS when using the AssumeRole credential type.
Could you please update the X-Amz-Date header automatically when the AssumeRole role is used?

I'm not able to reproduce this. The original X-Amz-Date header is always removed during signing, here:
https://github.com/anvilsecure/aws-sigv4/blob/afcd81f3ab47e5d71535d97a05af0a91fa339694/src/main/java/burp/BurpExtender.java#L1414-L1417
The AWS SDK then adds a new date header itself. Can you confirm in the Logger tab that the request actually has the original X-Amz-Date header?


Add support for AppFabric Caching

You already support a large number of caching providers (memcache, redis, etc.). One more great one would be AppFabric Caching.

Hi @deadlydog thanks for the suggestion. I had support for AppFabric for some time.
The CacheManager package for AppFabric was not really heavily used and it was a ton of effort to test it because at least the locally installed version was horrible to configure and very unstable.
I dropped it because of that and because Microsoft officially ended working on that cache. They actually say that you should use Redis instead, and I totally agree with that.
See https://en.wikipedia.org/wiki/AppFabric#History.

In April 2015, Microsoft announced that it would end support for AppFabric for Windows Server on 2 April 2016

Yeah I just noticed too that it's going end of life this year, so I agree it's not worth the effort to add it back in. Thanks, I'll close this ticket.


Add the required changes for F-Droid

[X]https://github.com/nullxception/boorusphere/commit/dbaf77192a635821d936e7dbd1545e04ffddc04e : Changes the versioning code scheme from the default abi * 1000 + vercode to vercode * 10 + abi, as requested by the F-Droid dev linsui at https://gitlab.com/fdroid/fdroiddata/-/merge_requests/13506#note_1608664649 This is a breaking change, as updating from the previous version to this one will likely cause issues as the version code here will be smaller than the one of the previous version, will require people to uninstall fully and reinstall. (If there's an backup/restore feature built in the app, this should be fine, if there isn't, this may cause issues)
[X]https://github.com/nullxception/boorusphere/commit/1fc042585c95201ddd673818b6558a2474e8f952 : Add distributionSha256Sum field to gradle wrapper properties to ensure the integrity of the downloaded gradle package, prevents attacks where a malicious or corrupt version would be offered for download on the gradle distribution website. This would fix one of the many annoying warnings about this being missing, presumably all the others are located in dependencies, and while it would be preferable to have them do it as well, I'm not likely to go through all of them one by one to ask them to do the same.
[ ] Reproducible build support : As asked by Izzy at https://gitlab.com/fdroid/fdroiddata/-/merge_requests/13506#note_1501746673 and recommended by F-Droid in general. I am not sure how to fix the specific issue he mentioned but I'm putting it up here so we can figure it out. Will be linking this in the F-Droid Merge Request so they can come help too if possible, as I'm neither an Android or Flutter dev, so this is all a bit beyond me at the moment.
Finally, this PR should close https://github.com/nullxception/boorusphere/issues/152 (can't figure out how to make it close it if merged from here atm though)

@nullxception @izzysoft tagging concerned individuals for now. idk if the f-droid linsui is also the github one so I'm not tagging them rn.

I'm currently not active at F-Droid, sorry. linsui and/or licaon-kter (add the @ before their names if you need to tag them) would most likely be working on this.

@IzzySoft their usernames are the same here as on gitlab? Also, unfortunate news that you're inactive at F-Droid. Still, considering the VerCode change if null merges this you might still need to be included as iirc you still have this app in your IzzyOnDroid repo, and that just smells like it's going to end up being a breaking change (I don't think android will like an "upgrade" from 1k, 2k or 4k to 411, 412 or 414) if it gets in considering the need for that change.

their usernames are the same here as on gitlab?

Yupp. Tested with the @, looks right.

unfortunate news

Since 11/2023, yeah. But you see the reasoning I hope. I was waiting for the situation to be dealt with so I might return, but it doesn't look like it will ever be addressed. I'm still supporting "my" fdroiddata team here and there, mostly "from behind the scenes".

considering the VerCode change

Yupp, the IzzyOnDroid repo would be affected then (auto-updates would stop and I'd have to take manual action; also those having installed the app from here would need to uninstall and reinstall, as Android doesn't permit "downgrades") – so there should be a proper hint in the corresponding per-release changelogs (or maybe even in the app description) to point that out. And I'd need a "ping" when the first such release was made, to take the required actions on my end.

that just smells like it's going to end up being a breaking change

It is. And I don't know why Flutter defaults to such a crazy scheme (ABI * 1000 + vercode) instead to the more sane vercode * 10 + ABI. The latter even allows switching between armeabi and arm64 in both directions when an update comes, theirs does not :man_shrugging:


SimpleHarvest doesn't work with Sandwichable

Hello. For some reason, Sandwichable crops are not right-clickable. This mod has the right tag for Simple Harvest and I set up the config correctly.
{
  "exhaustionPerHarvest": 0.005,
  "additionalLogging": false,
  "crops": [
    {
      "block": "minecraft:wheat",
      "states": {
        "age": "7"
      }
    },
    {
      "block": "minecraft:nether_wart",
      "states": {
        "age": "3"
      }
    },
    {
      "block": "minecraft:carrots",
      "states": {
        "age": "7"
      }
    },
    {
      "block": "minecraft:potatoes",
      "states": {
        "age": "7"
      }
    },
    {
      "block": "minecraft:beetroots",
      "states": {
        "age": "3"
      }
    },
    {
      "block": "sandwichable:cucumbers",
      "states": {
        "age": "4"
      }
    },
    {
      "block": "sandwichable:lettuce",
      "states": {
        "age": "4"
      }
    },
    {
      "block": "sandwichable:onions",
      "states": {
        "age": "3"
      }
    },
    {
      "block": "sandwichable:tomatoes",
      "states": {
        "age": "4"
      }
    }
  ]
}

UPD: If you make a separate datapack for the world with the seeds.json file, then everything starts working as it should. But why isn't the tag loaded directly from the mod? Is this a Sandwichable issue or Simple Harvest? 🤔

@FlamingCherry This is neither of their fault, per se, but it is odd. seeds.json is a tag file that standardizes which items are seeds for the corresponding crop item. Harvest seems to be pushing a convention that all seed items should be marked with this tag, which is a responsibility then put on other modders (in the case of this issue the dev of Sandwichable). I think it's a bit of a redundant convention since you can literally figure out which item is the seed item for the block you're breaking in code. I've done so in the above PR. I also published a build with the fix on my fork here


Job bulk after "Task is starting" log line

What do you mean "Job bulk"?
Which version of the tool are you using?
What OS are you using?
What is the output if you run with debug mode / output on?

I have the same problem.
You have exiftool(-k).exe
To resolve this remove (-k)
Like this exiftool.exe

Is this on Windows?
The intention was that this section of code would catch the case where people do not rename the exe to just be "exiftool.exe".
https://github.com/addshore/facebook-data-image-exif/blob/03846a5bbb47b5bd625de6217723a33403ebbadf/src/com/github/addshore/facebook/data/image/exif/Main.java#L204-L208

Yep Windows 10
Got from the official website

The stand-alone Windows executable does not require Perl. Just download and un-zip the archive then double-click on "exiftool(-k).exe" to read the application documentation, drag-and-drop files and folders to view meta information, or rename to "exiftool.exe" for command-line use. Runs on all versions of Windows.

Interesting, as far as I can see the code should catch cases like this.
Could you provide a screenshot of the input fields before you start the process?
Or turning on debug output might output them once you click start.
I'll leave this ticket open until I can get this fixed when i'm back from traveling.

Should be improved when I release the next version (0.10)

https://github.com/addshore/facebook-data-image-exif/releases/tag/0.10


[ERROR] Tag latest not found in repository docker.io/ibmblockchain/fabric-membersrvc

Using Docker Compose Local to run Hyperledger Network
follow the documentation: https://hub.docker.com/r/ibmblockchain/fabric-peer/
Step 5. Try to run one of the two docker compose files, single-peer-ca.yaml or four-peer-ca.yaml.
Get Error like this:
$ sudo docker-compose -f four-peer-ca.yaml up
WARNING: The ARCH_TAG variable is not set. Defaulting to a blank string.
Pulling membersrvc (ibmblockchain/fabric-membersrvc:latest)...
Pulling repository docker.io/ibmblockchain/fabric-membersrvc
ERROR: Tag latest not found in repository docker.io/ibmblockchain/fabric-membersrvc
Docker Version:
docker-compose version 1.5.2, build unknown
docker-py version: 1.8.0
CPython version: 2.7.12
OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016
System Version:
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04 LTS
Release:	16.04
Codename:	xenial

are you using marbles v3.0 and the connect-a-thon hyperledger network? also were you one of the invited participants? you will need to know a user/password to work with the connect-a-thon flow.
at any rate you may get better help by posting in the connect-a-thon repo instead of marbles.


jetty: 9.4.39.v20210325 -> 9.4.41.v20210516

Motivation for this change
backport jetty-9.4.41.v20210516 to nixos-21.05 to address CVE-2021-28169.
The CVE was addressed by upstream in jetty-9.4.41. See https://github.com/eclipse/jetty.project/security/advisories/GHSA-gwcr-j4wh-j3cq and the release notes https://github.com/eclipse/jetty.project/blob/jetty-9.4.x/VERSION.txt#L22
Closes #128381
(cherry picked from commit 8bfc237eb3bf79b42def350c5cf8b7c673deda79)

Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

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

[ ] Fits CONTRIBUTING.md.

Please target release-21.05.

Done, but I don't see a way to change the base branch in the PR.

Done, but I don't see a way to change the base branch in the PR.

You can change it by editing the PR, it should give you a dropdown list that lets you select the base branch.

Done.


paramiko.transport: ERROR: Socket exception: Connection reset by peer (104)

We sometimes get failures in running tests such as:
test_toggled_outlet_does_not_trigger_fencing_update (tests.integration.shared_storage_configuration.test_power_control.TestHostFencingConfig) ... ERROR
ERROR
Traceback (most recent call last):
  File "/usr/share/chroma-manager/tests/integration/core/api_testcase_with_test_reset.py", line 193, in tearDown
    "==== stopping test %s =====" % self)
  File "/usr/share/chroma-manager/tests/integration/core/remote_operations.py", line 515, in inject_log_message
    self._ssh_fqdn(fqdn, "logger \"%s\"" % message)
  File "/usr/share/chroma-manager/tests/integration/core/remote_operations.py", line 467, in _ssh_fqdn
    return self._ssh_address(address, command, expected_return_code, timeout, buffer)
  File "/usr/share/chroma-manager/tests/integration/core/remote_operations.py", line 436, in _ssh_address
    channel.exec_command(command)
  File "/usr/lib/python2.7/site-packages/paramiko/channel.py", line 60, in _check
    return func(self, *args, **kwds)
  File "/usr/lib/python2.7/site-packages/paramiko/channel.py", line 234, in exec_command
    self._wait_for_event()
  File "/usr/lib/python2.7/site-packages/paramiko/channel.py", line 1103, in _wait_for_event
    raise e
error: [Errno 104] Connection reset by peer

Where the Connection reset is coming from:
test: INFO: SSH address = lotus-56vm5.lotus.hpdd.lab.intel.com, args = {'username': 'root'}
paramiko.transport: ERROR: Socket exception: Connection reset by peer (104)

It would be nice to get some diagnostics about the host to which the connection was that got reset.

Another:
test_off_on_operations (tests.integration.shared_storage_configuration.test_power_control.TestPduOperations) ... ERROR
ERROR
Traceback (most recent call last):
  File "/usr/share/chroma-manager/tests/integration/shared_storage_configuration/test_power_control.py", line 16, in setUp
    super(ChromaPowerControlTestCase, self).setUp()
  File "/usr/share/chroma-manager/tests/integration/core/api_testcase_with_test_reset.py", line 134, in setUp
    "=====" % self)
  File "/usr/share/chroma-manager/tests/integration/core/remote_operations.py", line 537, in inject_log_message
    self._ssh_fqdn(fqdn, "logger \"%s\"" % message)
  File "/usr/share/chroma-manager/tests/integration/core/remote_operations.py", line 489, in _ssh_fqdn
    return self._ssh_address(address, command, expected_return_code, timeout, buffer)
  File "/usr/share/chroma-manager/tests/integration/core/remote_operations.py", line 442, in _ssh_address
    ssh.connect(address, **args)
  File "/usr/lib/python2.7/site-packages/paramiko/client.py", line 338, in connect
    t.start_client()
  File "/usr/lib/python2.7/site-packages/paramiko/transport.py", line 492, in start_client
    raise e
error: [Errno 104] Connection reset by peer

No longer appears to be issue.


Add Qbs view icon

What other Qbs-specific icons do you need?

What other Qbs-specific icons do you need?

We need in resolve, build, clean toolbar icons for the both light and 'darkthemes. Right now I use two iconsresolve&&build` from the CMake plugin.
We need in project, product, group (and, maybe some other, I don't know yet) icons in the project explorer tree for the both light and 'dark` themes. Right now I use some default icons from the VSCode database,


Correct SpinLight animation. https://github.com/GarageGames/Torque3D/…

…issues/1601

Az's change with  #1604 allows a little more flexibility in controlling the animations if we add more options going forward, so I went with that, but for the record, this fix did indeed work as well, so thanks John :)


POST/PATCH must advertise constraints if triples not persisted

Addresses FCREPO-1418

On the whole this looks really nice.
@whikloj ++
Just a few comments in-line, and I do want to make sure I understand how we are publishing the RDF/HTML and if we are doing it efficiently.

Please add a new integration test method to FedoraLdpIT that creates an error case and verifies the created link header.

It would be helpful to have an integration test that verifies:
the existence of the static RDF pages are available in fcrepo-webapp (see: https://github.com/fcrepo4/fcrepo4/blob/master/fcrepo-webapp/src/test/java/org/fcrepo/integration/SanityCheckIT.java)
the existence of the static RDF pages in the codebase, with the proper name, that correlates to the respective Exception classes.

Regarding this SanityCheck, I think that it:

Would need the issue about Grizzly not serving static pages to be resolved first.
Because there are RDF files for a subset of Exceptions (subclasses of ConstraintViolationException), I'm not sure how you would locate those Exceptions.

As always, if you want to give me some Java education on a way to do this, I can add it to the PR. :wink:

See: https://github.com/whikloj/fcrepo4/pull/2
...will look at the SanityIT.java later.

See: https://github.com/whikloj/fcrepo4/pull/3 for the SanityIT.

Resolved with: https://github.com/fcrepo4/fcrepo4/commit/447e56a9546900f62a2f1ad7a75077280072e773


Seg Faults in tsdb.(*querier).Select

Hi, we're getting a lot of segfaults at this location.  I do not know how to find the block it's attempting to sort or how I would un-encode it if I did.  I also do not know the query it's trying to serve.  This is coming from Prometheus (a query made through the API) as you see at the bottom of the stack given, but I figured it would be more appropriate here. I can provide the rest of the stack if you wish, but it seemed irrelevant.
  I went a head and checked that the last time Prometheus updated the vendor/github.com/prometheus/tsdb was the commit before this one.
prometheus, version 2.0.0-beta.0 (branch: dev-2.0, revision: 2b5d9159537cbd123219296121e05244e26c0940)
build user<EMAIL_ADDRESS>build date:       20170712-22:36:27
go version:       go1.8
Please let me know if you need more information.

@fabxc @brian-brazil I apologize if I should have opened this against Prometheus and not the tsdb sub component.  Please let me know if you want me move it.

All good. Based on the stack trace this is in the right place.
Thanks for reporting.
On Tue, Aug 8, 2017 at 9:27 PM Jeff Ohrstrom<EMAIL_ADDRESS>wrote:

@fabxc https://github.com/fabxc @brian-brazil
https://github.com/brian-brazil I apologize if I should have opened
this against Prometheus and not the tsdb sub component. Please let me know
if you want me move it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/tsdb/issues/117#issuecomment-321056930,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEuA8ix-StxNeCuEaUKvoC996pc6Hl5Uks5sWLaGgaJpZM4OwC6g
.

So this is a really odd one to be honest. sort.Sort is known to panic for semantically incorrect comparison function. However, here we have a string slice and are sorting with the sort.Strings function. Strings in the input list cannot even be nil.
I'm lost on what could possibly cause this – also haven't seen it anywhere else before.
Can you reliably reproduce this and possibly print the input to the sorting?

This happens to me often, so I can definitely replicate.  After looking through the code, I'm guess I should print the array here?  I'll try to get the patch deployed in my env and let you know.
By the way, I don't believe any of them are nil, isn't that a different error message (invalid memory address or nil pointer dereference?).
I'll also have to look into where this is happening in a GC cycle. Could it be that while sorting it's referencing a label value that got GC'd? As I say it, it doesn't sound right, but it was my initial thought when I first saw it.

Yea right, that's typically something about invalid memory.
Generally, a referenced value can by definition not be GC'd.
The first guess where we could see this of course would be mmap'd memory. But this occurs in the headIndexReader which purely deals with heap memory.
Second guess would be that it's something caused by Prometheus' retrieval layer playing a few unsafe tricks to prevent loads of memory allocations. But strings we actually pass down to the storage are properly allocated as regular strings.
If we messed this up somewhere, I'd expect this to be a very frequent issue but neither ourselves nor anyone else has reported something like this before.
Also quite unlikely that this would be the first (and only?) place where the issue shows.
Is there anything out of the ordinary about your environment? (Architecture, OS, ...)

Is there anything out of the ordinary about your environment? (Architecture, OS, ...)
I can't image so, we're running CoreOS (1409.7.0 (Ladybug), kernel 4.11.11-coreos) in Amazon as a r4.4xlarge type.
This query is around 280k, which I'm sure others have surpassed.
rate(tsdb_samples_appended_total{}[1m])
this would be the first (and only?) place where the issue shows.
Good question! It runs out labels are all f**ed up for me. I went back and found I'm getting stacks in at least 2 other places all related to labels, so perhaps this does need to go to the prometheus main project.
unexpected fault address 0x7f9397b2b603
fatal error: fault
[signal SIGSEGV: segmentation violation code=0x1 addr=0x7f9397b2b603 pc=0x45a91a]
goroutine 213 [running]:
runtime.throw(0x1c0ab5d, 0x5)
        /usr/local/go/src/runtime/panic.go:596 +0x95 fp=0xc52dda7558 sp=0xc52dda7538
runtime.sigpanic()
     /usr/local/go/src/runtime/signal_unix.go:297 +0x28c fp=0xc52dda75a8 sp=0xc52dda7558
runtime.memeqbody()
         /usr/local/go/src/runtime/asm_amd64.s:1457 +0x8a fp=0xc52dda75b0 sp=0xc52dda75a8
github.com/prometheus/prometheus/pkg/labels.(*Builder).Set(0xc52dda76b8, 0x7f9397b2b603, 0x9, 0x7f93976f97f7, 0x5, 0xc52dda76b8)
        /opt/aeg/go/src/github.com/prometheus/prometheus/pkg/labels/labels.go:222 +0x1d2 fp=0xc52dda7628 sp=0xc52dda75b0
 github.com/prometheus/prometheus/rules.(*AlertingRule).sample(0xc5aacbe300, 0xc542415c00, 0xed118293b, 0xc50df21662, 0x291c580, 0x0, 0
      /opt/aeg/go/src/github.com/prometheus/prometheus/rules/alerting.go:138 +0x1e9 fp=0xc52dda7710 sp=0xc52dda7628
 github.com/prometheus/prometheus/rules.(*AlertingRule).Eval(0xc5aacbe300, 0x7f941f499000, 0xc6524585c0, 0xed118293b, 0xdf21662, 0x291c
        /opt/aeg/go/src/github.com/prometheus/prometheus/rules/alerting.go:263 +0x10ba fp=0xc52dda79f0 sp=0xc52dda7710
github.com/prometheus/prometheus/rules.(*Group).Eval.func1(0x1c0f3b5, 0x8, 0xc5aacbe800, 0xed118293b, 0xc80df21662, 0x291c580, 0x3, 0x
        /opt/aeg/go/src/github.com/prometheus/prometheus/rules/manager.go:306 +0x177 fp=0xc52dda7d58 sp=0xc52dda79f0
github.com/prometheus/prometheus/rules.(*Group).Eval(0xc5aacbe800, 0xed118293b, 0xdf21662, 0x291c580)
        /opt/aeg/go/src/github.com/prometheus/prometheus/rules/manager.go:374 +0x10b fp=0xc52dda7dd8 sp=0xc52dda7d58
 github.com/prometheus/prometheus/rules.(*Group).run.func1()
        /opt/aeg/go/src/github.com/prometheus/prometheus/rules/manager.go:181 +0x7e fp=0xc52dda7e28 sp=0xc52dda7dd8
github.com/prometheus/prometheus/rules.(*Group).run(0xc5aacbe800)
        /opt/aeg/go/src/github.com/prometheus/prometheus/rules/manager.go:206 +0x328 fp=0xc52dda7fa8 sp=0xc52dda7e28
github.com/prometheus/prometheus/rules.(*Manager).ApplyConfig.func1.1(0xc652458600, 0xc5aacbe800)
        /opt/aeg/go/src/github.com/prometheus/prometheus/rules/manager.go:509 +0x52 fp=0xc52dda7fd0 sp=0xc52dda7fa8

and
fatal error: fault
[signal SIGSEGV: segmentation violation code=0x1 addr=0x7f2b8e9a8868 pc=0x45a91a]
goroutine 120 [running]:
runtime.throw(0x1c0ab5d, 0x5)
         /usr/local/go/src/runtime/panic.go:596 +0x95 fp=0xc580df87f8 sp=0xc580df87d8
runtime.sigpanic()
        /usr/local/go/src/runtime/signal_unix.go:297 +0x28c fp=0xc580df8848 sp=0xc580df87f8
runtime.memeqbody()
        /usr/local/go/src/runtime/asm_amd64.s:1457 +0x8a fp=0xc580df8850 sp=0xc580df8848
type..eq.github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.term(0xc580df8910, 0xca4e7fc778, 0x6dcc808e2c3db0a3)
        /opt/aeg/go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/block.go:1 +0xa4 fp=0xc580df8888 sp=0xc580
runtime.mapaccess1(0x1974f40, 0xc97920b9b0, 0xc580df8910, 0x1ace400)
         /usr/local/go/src/runtime/hashmap.go:348 +0x19e fp=0xc580df88d0 sp=0xc580df8888
github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*headIndexReader).Postings(0xc47989fb30, 0xc99d80a87d, 0x9, 0xc99
        /opt/aeg/go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/head.go:689 +0xf2 fp=0xc580df8940 sp=0xc58
 github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*postingsReader).selectSingle(0xc580df8bc0, 0x284b300, 0xc9287ac0
        /opt/aeg/go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/querier.go:226 +0xa1 fp=0xc580df8a70 sp=0x
 github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*postingsReader).Select(0xc580df8bc0, 0xc435c86570, 0x3, 0x3, 0x2
       /opt/aeg/go/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/querier.go:215 +0x104 fp=0xc580df8b38 sp=0
 github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.(*blockQuerier).Select(0xc68dee3270, 0xc435c86570, 0x3, 0x3, 0x285)

I think it may be related to this new alertmanager relabel config feature (given the rule generation stack above).  I've deploy kube state metrics and I'm changing the exported_namespace (that I get from it) into just namespace, but only for alerting.  Kube state metrics itself has a namespace, which I don't change during actual ingestion.
  alert_relabel_configs:
  - source_labels: [exported_namespace]
    regex: (.+)
    action: replace
    target_label: namespace

I'm going to try replacing replacing them during scrape ingestion instead of during alerting.  Perhaps if it stops seg faulting, and if so, it'll clearly be a problem with alert manager relabeling.

First, great to see that someone is testing 2.0 with such a rather heavy load!
The only touching point of alert relabel configs is that it gets its label from the storage. There's no dependency in the other direction.
So if the issue also occurs in the storage first, the cause is more likely to be somewhere in the storage.
I would say that testing it on another instance might be interesting since the hardware memory might be messed up somehow. But since it only occurs for labels, that's a rather unlikely guess.
I currently have  the last beta and the current HEAD running on AWS at 220k samples/sec with rahter heavy querying load. I do not see any panics.

This issue persists, but I'm going to update to 2.0.0-beta.1 that was just released and we'll see what's happening. We're also going to re-architect a little bit (for sharding reasons) so maybe, if it persists that'll shed some light on it.
Also I was thinking it could have something to do with empty or null labels?  I have ec2 discovery where I'm trying to build a label out of ec2 tags and they're only present maybe 95% of the time.
Lastly, testing it on another instance only confirms what you suspect. We're running a pair behind a load balancer and they seg fault seconds apart from each other, I guess because the LB makes the duplicate query on the second one.
In any case, when I update and restructure the deployment, I'll let you know what happens either way.

I upgraded to beta-2.2 and seemed to have traded this for issue 2955. I'm going to close this issue now.

This is back again? See prometheus/prometheus#3217

I just installed beta.5 on Friday and let it run over the weekend, and surprisingly I didn't see it happen. If it does, I'll update this ticket (or the other). Otherwise, no news is good news.
version info:
prometheus, version 2.0.0-beta.5 (branch: HEAD, revision: )
build user:       root@df40cc0bd79b
build date:       20170921-16:23:04
go version:       go1.8.3

Underlying issue got fixed.


Added feature of conflict warming

Coverage increased (+0.3%) to 67.19% when pulling d0ec3252d14322b7df4151927829e93b44944f8d on lproperty:v0.5.2 into 86b97449ce4d589adf76830a2dffd758ea4b85e2 on CS2103JAN2017-T15-B3:v0.5.2.

Coverage increased (+0.3%) to 67.156% when pulling 8db8b2e33be7d1c4a957a676f913e52bf489ad35 on lproperty:v0.5.2 into 86b97449ce4d589adf76830a2dffd758ea4b85e2 on CS2103JAN2017-T15-B3:v0.5.2.


Update main.tf

The provider versions in the original script are no longer supported as Azure has retired the Azure Time Series Insight as of July 2024.
Purpose

Update provider versions.
Does this introduce a breaking change?

[ ] Yes
[X ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information

This issue was resolved 2 weeks ago. Apologies for not replying sooner.


unlable to login when configure dex openldap

installed kubevela core via helm , and enabled addon dex, and only configured openlap.
but when try to login kubevela ,it report like  "Failed to parse authorization request: Unregistered redirect_uri ("https://kubevela.ops.eclincloud.net/callback\")."
repeat:

dex-config:

let me know if need more info, thanks.

dex logs:


Make usage of mini-css-extract-plugin optional

🚀 Feature request
Current Behavior
I have to install mini-css-extract-plugin in order to make Razzle 4 work.
Desired Behavior
Razzle 4 is usable without mini-css-extract-plugin if the project doesn't need that.
Suggested Solution
a) Make createConfigAsync.js to load this plugin only when it's actually used
b) Add a config option to disable css/style handling in default config (and leave it turned on by default for backward compatibility)
Who does this impact? Who is this for?
Projects without css (e.g. using a css-in-js solution).
Describe alternatives you've considered
Haven't tried this, but probably I could create a local mini-css-extract-plugin dummy project and point mini-css-extract-plugin to that folder with file:... in my package.json.
I can also install this package, but technically I don't need that, so... that's why I thought I should point this out.

Ideally every part of razzle should be a plugin. Then have a default set of core plugins.

I think when buildType is set to serveronly or serverless, mini-css-extract-plugin, postcss and html-webpack-plugin should be disabled by default, we can check if package is actually installed and only add in the chain if they're installed


Clear Warning in generated_data

Is this pull request associated with an issue(s)?
Fixes #79
Description
The warning from #79 comes from the fact that no basis set information is actually found in def2-ecp.nw and the ECP specification isn't parsed by our current routine. Given that we don't support ECPs at the moment, that's probably fine. The fix here is in the generate_basis.py file, where there is an added check that skips the generation of a source file for a basis set file where no information was parsed.

🚀 [bumpr] Bumped! New version:v1.0.6 Changes:v1.0.5...v1.0.6


[Client encryption]: Faster validations and string comparisons

Pull Request Template
Description

Switch frequent constants string comparison mode to ordinal
Reduce allocations and validations complexity

Type of change
Please delete options that are not relevant.

[] Bug fix (non-breaking change which fixes an issue)

Closing issues
Contributes to #4678

/azp run


Allow users to select fonts from their local storage

Feature Description
Add selection windows for users to pick font files from their local storage.
Reason for Change
A necessary feature of the A1 release.
Where are the changes needed?
Changes to the home screen or landing page.
Code Snippets
No response
Anything Else?
No response

Good thinking; go for it 🏃


Encore

Hi
I am still reading up on Pony, and - while there's not much software written in it - I've come across Mare and Encore, two languages based on Pony. I am really curious what you think about Encore, written at Uppsala University?
Thanks!
Ben.

I personally don't have much of an opinion on Encore because I haven't looked into it or used it. The Pony runtime is excellent, so in general I think it's great to have multiple languages using it with varying approaches.


add rgbw,dimming light and water sensor

Add three Sengled zigbee devices:

Add Sengled water leak sensor E1L-G7K
Add the init.lua file to the path ~\SmartThingsEdgeDrivers\drivers\SmartThings\zigbee-water-leak-sensor\src\sengled.
Modified ~\SmartThingsEdgeDrivers\drivers\SmartThings\zigbee-water-leak-sensor\fingerprints.yml file, a new device type E1L-G7K is added.
Add Sengled zigbee rgbw bulb E23-N13.
Modified ~\SmartThingsEdgeDrivers\drivers\SmartThings\zigbee-switch\src\rgbw-bulb\init.lua file, a new device type E23-N13 is added.
Modified ~\SmartThingsEdgeDrivers\drivers\SmartThings\zigbee-switch\fingerprints.yml file, a new device type E23-N13 is added.
Add Sengled dimming light bulb E23-N11.
Modified ~\SmartThingsEdgeDrivers\drivers\SmartThings\zigbee-switch\src\zigbee-dimming-light\init.lua file, a new device type E23-N11 is added.
Modified ~\SmartThingsEdgeDrivers\drivers\SmartThings\zigbee-switch\fingerprints.yml file, a new device type E23-N11 is added.

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

Add Sengled water leak sensor E1L-G7K

Modified ~\SmartThingsEdgeDrivers\drivers\SmartThings\zigbee-water-leak-sensor\src\init.lua file, sub-driver named "sengled" is added.

Loop 徐总
zhuge
From: github-actions[bot]
Date: 2023-05-16 22:42
To: SmartThingsCommunity/SmartThingsEdgeDrivers
CC: sengled-gezhu; Author
Subject: Re: [SmartThingsCommunity/SmartThingsEdgeDrivers] add rgbw,dimming light and water sensor (PR #724)
Invitation URL:
https://bestow-regional.api.smartthings.com/invite/akMX6a5znXlb
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Loop 徐总
zhuge
From: zhuge
Date: 2023-05-18 09:38
To: SmartThingsCommunity/SmartThingsEdgeDrivers; SmartThingsCommunity/SmartThingsEdgeDrivers
CC: Author
Subject: Re: Re: [SmartThingsCommunity/SmartThingsEdgeDrivers] add rgbw,dimming light and water sensor (PR #724)
Loop 徐总
zhuge
From: github-actions[bot]
Date: 2023-05-16 22:42
To: SmartThingsCommunity/SmartThingsEdgeDrivers
CC: sengled-gezhu; Author
Subject: Re: [SmartThingsCommunity/SmartThingsEdgeDrivers] add rgbw,dimming light and water sensor (PR #724)
Invitation URL:
https://bestow-regional.api.smartthings.com/invite/akMX6a5znXlb
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Hello @sengled-gezhu
Can you please resolve the conflicts on this PR and also sign the CLA?

Yes, I have modified the previous conflict content and signed the CLA.
zhuge
From: lelandblue
Date: 2023-09-08 21:41
To: SmartThingsCommunity/SmartThingsEdgeDrivers
CC: sengled-gezhu; Mention
Subject: Re: [SmartThingsCommunity/SmartThingsEdgeDrivers] add rgbw,dimming light and water sensor (PR #724)
Hello @sengled-gezhu
Can you please resolve the conflicts on this PR and also sign the CLA?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Thank you. Please also provide unit tests that cover the changes that your looking to add. We require that tests be provided of the new code that is being contributed. Please this page for more information. https://developer.smartthings.com/docs/devices/hub-connected/test-your-driver

Hello @sengled-gezhu In order for this to proceed we need you to add unit test coverage for the changes that your proposing in the init file. Test coverage is in the form of adding unit tests, in a .test file in a new commit on the PR. This is similar to the discussion we have been having with PR : 716.
Thank you for your communication.

1.For rgbw and dimming light, We did not add a subdirectory driver, so we can simply follow the default process for authentication.
2.For water leak sensor device, we have added a. text file to the test directory.

Hello @lelandblue
1.For rgbw and dimming light, We did not add a subdirectory driver, so we can simply follow the default process for authentication.
2.For water leak sensor device, we have added a. text file to the test directory.
zhuge
From: lelandblue
Date: 2023-10-30 21:48
To: SmartThingsCommunity/SmartThingsEdgeDrivers
CC: sengled-gezhu; Mention
Subject: Re: [SmartThingsCommunity/SmartThingsEdgeDrivers] add rgbw,dimming light and water sensor (PR #724)
Hello @sengled-gezhu In order for this to proceed we need you to add unit test coverage for the changes that your proposing in the init file. Test coverage is in the form of adding unit tests, in a .test file in a new commit on the PR. This is similar to the discussion we have been having with PR : 716.
Thank you for your communication.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Hello @lelandblue,
Is there any problem with the certification of Sengled's lights and water leak sensor? Do you need me to do anything?

Yes @sengled-gezhu. You need to provide a profile name in the fingerprint file for the sengled/E23-N11 device. As it is written today, this device would not work when levering your changes.

Hello @lelandblue,
In the ...drivers\SmartThings\zigbee-switch\fingerprints.yml file, we have added the profile names for our dimming-light, where  E23-N11 is the dimming-light, as follows:

id: "sengled/E23-N11"
deviceLabel: Sengled Light par38
manufacturer: sengled
model: E23-N11
deviceProfileName: on-off-level

Hello, @greens,
We have updated the [drivers/SmartThings/zigbee-water-leak-sensor/src/sengled/init.lua] file content， as follows:
{ mfr = "sengled", model = "E1L-G7K" }

@.***
For the E23-N11 product, we added "deviceProfileName: on-off-level" 2 days ago.
Please refer to line 2147 of the drivers/SmartThings/zigbee-switch/fingerprints.yml file,
as shown in the following figure:
zhuge
From: lelandblue
Date: 2023-11-10 01:16
To: SmartThingsCommunity/SmartThingsEdgeDrivers
CC: sengled-gezhu; Mention
Subject: Re: [SmartThingsCommunity/SmartThingsEdgeDrivers] add rgbw,dimming light and water sensor (PR #724)
@lelandblue commented on this pull request.
In drivers/SmartThings/zigbee-switch/fingerprints.yml:

@@ -2135,6 +2135,15 @@ zigbeeManufacturer:
model: ROB_200-011-0
deviceLabel: ROBB SMARRT Zigbee dimmer 2-wire
deviceProfileName: light-level-power-energy

id: sengled/E23-N13

deviceLabel: Sengled Multicolor par38
manufacturer: sengled
model: E23-N13
deviceProfileName: rgbw-bulb

id: "sengled/E23-N11"

deviceLabel: Sengled Light par38
manufacturer: sengled
model: E23-N11

@sengled-gezhu You need to add a line and define the profile that the device should join to here. Please review the capabilities of the E23-N11 device and match it to a profile.
I believe you would want something like:
"deviceProfileName: rgbw-bulb" or "deviceProfileName: on-off-level"
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


Connect UI with the analysis viewer

Problem
We want to render the files from the analysis using the rendering engine in analysis viewer service.
Implementation
The viewer service accepts URL to the output file as URL parameter. It can use other url parameters if needed.
The href with the link should be here:
https://github.com/fbielejec/spread/blob/master/src/cljs/ui/analysis_results/page.cljs#L161
Use the config namespace to set the host part of the link to the URL where the analysis viewer is
Acceptance Criteria
User can click on the results link and is taken to the complete visualisation of his results in a separate browser tab.
He/she can use the Copy button next to the href element to share the URL.
When pasting the URL in a browser window the visualisation can be viewed.

This is implemented in https://github.com/fbielejec/spread/pull/83


No connection could be made because the target machine actively refused it.

ErrorException in SphinxSearch.php line 26:
mysqli_connect(): (HY000/2002): No connection could be made because the target machine actively refused it.

ErrorException in SphinxSearch.php line 26:
mysqli_connect(): (HY000/2002): No connection could be made because the target machine actively refused it.

I am facing the same issue, can anyone please suggest me something on this


minSNR loss weight?

Hi,
I'm wondering if minSNR is compatible with this approach.

They're more likely to sample timesteps from the middle which has a similar effect, I think.


False positive when setting a variable within a condition

In this case the code is derived from j.u.c.atomic.Striped64 so the style is retained. If setting the variable is extracted to buffers = table prior to the condition, then this error does not appear.
error: [NullAway] dereferenced expression buffers is @Nullable
      if (((buffers = table) != null) && ((n = buffers.length) > 0)) {

Interesting!  I'll look into whether we can support this case


Render to Android

Ideally, we'd be able to compile Theodolite to both iOS and Android view systems. We may not be able to reuse all the code we have, but much of it should be able to map well.

@amonshiz are you looking at this?

No, I have not looked at this yet. I did start looking into what the state of the art was for building Swift for Android, and everything seems pretty old. I will check in with @modocache to see if he knows more.

OK, great! Let me know what we need to do here.


Release 0.1.1

Checklist

[ ] Pull request details were added to CHANGELOG.rst
[ ] Documentation was updated (if needed)

Codecov Report

Merging #9 (6af049a) into main (f0390c6) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main        #9   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           62        62
=========================================
  Hits            62        62

Impacted Files
Coverage Δ

src/fastq_filter/__init__.py
100.00% <ø> (ø)

Continue to review full report at Codecov.

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


Abstract memory implementation from the rest of the program

Currently, some functions on the vm rely on the memory structure, so that a change to the structure of the memory implies a change to the logic of the VM's functions. These functions should be changed so that they can become agnostic to the memory structure

Already done


Further simplify collections APIs

Only interfaces are exposed, all implementations and factories moved to internal
Remove int-converting methods from single collection, they seem too unrelated to collections and aren't hard for a user to do. String renamed to Get to better match being part of a collection
Separates Collection from Keyed collection. Previously, we had FindString type methods implemented even on single collections, delegating to FindAll, and similar for views. This is hard to reason about - now the types are precise. Code that needs to handle generically, like ours, can still use a type check for reasonably simple code while the collections themselves become more self-explanatory
Moves AnchoredVar to internal type keyValue

Codecov Report
Base: 77.64% // Head: 77.69% // Increases project coverage by +0.04% :tada:

Coverage data is based on head (c31c198) compared to base (f308794).
Patch coverage: 78.57% of modified lines in pull request are covered.

:exclamation: Current head c31c198 differs from pull request most recent head cc5a2d6. Consider uploading reports for the commit cc5a2d6 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           v3/dev     #608      +/-   ##
==========================================
+ Coverage   77.64%   77.69%   +0.04%
==========================================
  Files         144      144
  Lines        7449     7469      +20
==========================================
+ Hits         5784     5803      +19
+ Misses       1435     1434       -1
- Partials      230      232       +2

Flag
Coverage Δ

default
73.32% <78.27%> (+0.05%)
:arrow_up:

examples
28.62% <51.48%> (+<0.01%)
:arrow_up:

ftw
55.11% <70.23%> (+0.09%)
:arrow_up:

ftw-multiphase
55.21% <70.23%> (+0.09%)
:arrow_up:

tinygo
71.28% <77.67%> (+0.06%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

actions/ctl.go
71.72% <ø> (ø)

macro/macro.go
85.71% <60.00%> (-4.77%)
:arrow_down:

internal/corazawaf/transaction.go
79.92% <66.47%> (-0.26%)
:arrow_down:

internal/collections/named.go
89.28% <71.42%> (ø)

internal/collections/map.go
90.29% <90.29%> (ø)

internal/collections/concat.go
100.00% <100.00%> (ø)

internal/collections/single.go
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Support more file types

[ ] png
[ ] jpg
[ ] matlab files of the cta all sky cam

skimage.io.imread and scipy.io.matlab might help

Each camera implements it's own reading now


Implement Pipe Rendering

[x] Render Static Model Part

[x] Basic Pipes

[ ] Industrial Pipes

[ ] Render Item Flow
[ ] Render Connector activity lights

Static part of basic pipe modell is done.
The method needs to be revised and refined tho.


Setting testnet=1 in config file does not work

Launching with parameter -testnet=1 will work but setting testnet=1 in config file does not boot up the testnet, it goes into mainnet instead.

Resolved in #669


Maven perform release failed with nexus plugin, parent not deployed

Revert nexus at module level to parent

FIxed by #85


Teach no-vars about array destructuring with ignored values

While running this on Airbnb code, I ran into the following error:

TypeError: Cannot read property 'type' of null

Which seemed to happen when encountering array destructuring with
ignored values, like:
var [, foo, bar] = baz;

I fixed this by guarding against this case in a few places.
While I was at it, I also fixed some typos that I happened to notice.

I'm curious what kind of code you guys are writing. This pattern is so bad but I've needed it myself a couple of times. Thanks for the codemod fixes, as always!

It looks like we only had that pattern in a couple of places. One where we were splitting a string and just wanted the second bit, and another where we were doing a regex match and we didn't care about the first element in the array.

Nice, those seem like valid use cases. I didn't even realize one could skip variables in array destructuring, NICE.

@lencioni oh, also, I sent you a message on Facebook if you'd be so kind to respond :)

Good catch :+1:


[Fatal Error] updates.xml:1:1: Premature end of file.

The error is printed during :prepareSandbox
The updates.xml itself looks ok and has the following content:
<application>
  <component name="UpdatesConfigurable">
    <option name="CHECK_NEEDED" value="false"/>
  </component>
</application>

Nevertheless the build finishes successfully.
Environment:
org.jetbrains.intellij" version "0.0.35"
Java 6
IntelliJ IDE 13

0.0.37 is uploaded


Consider adding licence

As the project has no licence, currently the code is all rights reserved by default meaning nobody else is allowed to use it. Consider adding an open source licence to make the project truly open source, if you would like to :)

Thanks for the heads up. Added an MIT license.


fixing logic on test for result success

Ran into issues using latest client-go in wsk cli, all non-error responses reporting as failures.
Fixing error logic in #91

@dubee or @mdeuser - want to add any comments here before merge?


[BUG] volume creation with an invalid FromBackup should fail

Currently if the FromBackup specified backup cannot be found in the backup store, the volume create call will succeed which signals that the volume can be created. This will then lead to a npe in the controller.

e2e test is tracked at https://github.com/longhorn/longhorn/issues/2687

There are 2 ways you can test this:
this one is a little quicker, but less likely to be used by a user.
via a storage class that specifies an invalid from backup
https://longhorn.io/docs/1.1.1/references/examples/#storageclass
This one requires setting up the csi snapshot stuff, if you haven't done this before, have a look at the documentation here:
https://longhorn.io/docs/1.1.1/snapshots-and-backups/csi-snapshot-support/enable-csi-snapshot-support/
via a volume snapshot that specifies an invalid from backup:
https://longhorn.io/docs/1.1.1/snapshots-and-backups/csi-snapshot-support/restore-a-backup-via-csi/#restore-a-backup-that-has-no-associated-volumesnapshot

Still validating, a short testing update on v1.1.2-rc1,
When referencing snapshot content (snapshotHandle) to a non-existed backup location,
kubectl get persistentvolumeclaim
NAME                           STATUS    VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS      AGE
test-restore-existing-backup   Pending                                                                        longhorn          5m30s

With the correct bs:// uri, the pvc can be created from VolumeSnapshot(Content), however I had to delete both VolumeSnapshot and VolumeSnapshotContent resources then re-apply the correct ones. Modifying the path doesn't seems to reflect the change directly, need to check again.

Validation - In progress
Test steps:

Create a VolumeSnapshotContent with source from a none-exist Longhorn backupstore:

source:
    snapshotHandle: bs://test-vol/backup-not-there

Create a VolumeSnapshot referencing volumeSnapshotContentName just created:

  source:
    volumeSnapshotContentName: test-existing-backup

Create a PersistentClaimVolume restore from VolumeSnapshot

  dataSource:
    name: test-snapshot-existing-backup
    kind: VolumeSnapshot

And monitoring the log of longhron-manager, I can see relevant error messages from both csi-provisioner and longhorn-manager:
[longhorn-csi-plugin-7d4ns longhorn-csi-plugin] time="2021-06-30T09:12:37Z" level=error msg="CreateVolume: err: rpc error: code = NotFound desc = cannot restore csi snapshot bs://test-vol/backup-not-there backup backup-not-there unavailable"
[longhorn-manager-fqdds] time="2021-06-30T09:12:37Z" level=warning msg="cannot find backup backup-not-there of volume test-vol"
[csi-provisioner-7dcbc6f5bc-rtwc7] I0630 09:12:37.882395       1 connection.go:186] GRPC error: rpc error: code = NotFound desc = cannot restore csi snapshot bs://test-vol/backup-not-there backup backup-not-there unavailable
[csi-provisioner-7dcbc6f5bc-rtwc7] I0630 09:12:37.882427       1 controller.go:634] CreateVolume failed, supports topology = false, node selected false => may reschedule = false => state = Finished: rpc error: code = NotFound desc = cannot restore csi snapshot bs://test-vol/backup-not-there backup backup-not-there unavailable
[csi-provisioner-7dcbc6f5bc-rtwc7] E0630 09:12:37.882502       1 controller.go:939] error syncing claim "0818b5f3-395b-4b66-b29d-bd94b8c554ad": failed to provision volume with StorageClass "longhorn": rpc error: code = NotFound desc = cannot restore csi snapshot bs://test-vol/backup-not-there backup backup-not-there unavailable
[csi-provisioner-7dcbc6f5bc-rtwc7] I0630 09:12:37.883656       1 event.go:281] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"test-restore-existing-backup", UID:"0818b5f3-395b-4b66-b29d-bd94b8c554ad", APIVersion:"v1", ResourceVersion:"317977", FieldPath:""}): type: 'Warning' reason: 'ProvisioningFailed' failed to provision volume with StorageClass "longhorn": rpc error: code = NotFound desc = cannot restore csi snapshot bs://test-vol/backup-not-there backup backup-not-there unavailable

Also, as mentioned in previous comment the pending volume won't be showed up in Longhorn UI, as result, user will need to check on resource itself or on Rancher UI go to Resources > Workloads > Volumes, then click into the Events to see error.

Since the provisioning of the volume failed, there is no longhorn volume and no associated PV getting created. So the PVC will remain unbound. This is outside of Longhorn therefore we don't need to show anything since there is no pending 'volume'.

@joshimoo thank you for clarifying this for me.
Validation - Passed
Tested on both 1.1.2-rc1 and master-image(longhorn-manager: 27c93ca9)
testing steps
csi-snapshot setup


Define the Concept for history of Digital Twins

TBD

child of https://github.com/eclipse-tractusx/sig-release/issues/635

Obsolete for now


paper template word version

@hitmuri  suggested to seek a way, probably using pandoc, to create a word version from latex directly.
Happy to help have a look when latex is done. We could do manual change on .docx directly if it's easier as well, as a direct conversion can be touchy according to @cpmpercussion's previous hack.

I've tested a few possibilities with pandoc, but nothing that works perfectly yet ... we need to write a pandoc filter that removes the latex commands (\anon ...). I'll keep hacking at it


handbrake: 1.8.1 -> 1.8.2

Description of changes
https://github.com/HandBrake/HandBrake/releases/tag/1.8.2

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Can you please move the app to pkgs/by-name format?

Adding mainProgram = "HandBrakeCLI"; into meta would also be useful

Result of nixpkgs-review pr 335279 run on x86_64-linux 1

1 package built:

handbrake


initial fastlane structure for F-Droid

To fill the gap reported by F-Droid's bot on your RFP. Note: these are the metadata used for your app in my repo. Once you've merged this, I'll tell my updater to check the structures whenever it pulls an update. So should you modify the description, add/update screenshots etc., that will be reflected on my end (and later on F-Droid's) automatically.
Feel free to build on this once merged – and be welcome to use my Fastlane Cheat Sheet to guide you :wink:

Thanks for the PR.
I think I'll have to do something about the Secrets.kt (contains sensitive info) file as it is necessary for building an APK if I want to setup automation.
Will have a look at this and other stuff when I get time, busy these days due to exams.

Whenever you're ready – and sure, first things first!

Yay! Thanks for merging! I've kicked the bot again at the RFP (so it updates and marks Fastlane as available) and also enabled Fastlane updating in my repo.


Remove packing.nfo between -fba and -ls runs?

https://colab.research.google.com/drive/1wjF6tuGZa3opIWpXIYiKJtmpqBVSpj1E?usp=sharing

https://github.com/VasiliBaranov/packing-generation/issues/19

Seems the answer is yes https://github.com/VasiliBaranov/packing-generation/issues/21#issuecomment-680292332

Hi @sgbaird, i think you found all the relevant comments! Sorry, i probably still need to update the documentation.. Will do over the Christmas time!

I've actually just updated the section https://github.com/VasiliBaranov/packing-generation#4-sample-usage , so it shall be much better now. Thanks for noticing!
Best Regards,
Vasili


Fix: Github workflow

Related https://github.com/logseq/marketplace/pull/103
Hi @benjaffe , if you merged this PR, you could create a new tag to rebuild release package :)

Ah yes, thank you! (I've only used huge company's internal build systems, so I'm doing github all wrong :P )

Ok, release should be done now @xyhp915 . Thank you!


[ CREATE ] - Footer

Create the footer as using the example below:
Dont worry about linking the pages for now, we can visit this later once the sections are complete.

IF YOU WISH TO WORK ON THIS, PLEASE CHECK NO ONE HAS CLAIMED IT BELOW, IF NOT CLAIM IT BY COMMENTING

I will work on this

Am through with this task. will push now

I just did PR for this task

@JoshuaCode1 This never got merged in because of a conflict, but I'm looking through it and there are a lot of additions like bootstrap and jquery that aren't needed here. If you want to try pulling the upstream to get the most current version and adding just the footer section back, we can pull this in.

I completed the footer on #207 How do I sync this issue? Thank you for your advice!

@krittiyaclark the message when you create the pull requests has a checklist to be completed as seen here:

These need to be completed and you link it by typing # followed by the number of the issue.

Merged


[angular-ngrx-scss] Kit not deployed to npm correctly

A root cause analysis can be found in the accompanying PR: #221


Feature request : supress warning and error messages

I think it would be helpful if for some users if they don't want info and error messages popping up all the time.
I'm having this problem while working in a restricted environment at office.

Options like this would be helpful:
 'editor.supressWarningMessages' : true

For 1.7 we added an option to hide this warning.

when will the 1.7 update be out?

This week. Meanwhile:
Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: http://code.visualstudio.com/Download#insiders

what is the option that i need to set. any documentation anywhere?

@AkashGutha when you see the warning there should be a button to never show again.

Yes it is working .
And it shows up only if I change the folder or if I reopen vscode . Is this the intended behavior ?

@AkashGutha it will warn you once per workspace but should then remember it for that workspace.

yes, it does that perfectly.  it only pops up if i have the folder closed from menu and open an new folder.

@AkashGutha that is true, it will probably pop up all the time from after you closed a folder. Is that what annoys you still?


Organise (meta)data into data projects

Based on our discussions and documentation in the code, in Sprout (meta)data are grouped into projects.
We should update the code to reflect this organisation.
One example:
In sprout/app/views/projects_id_metadata_view.py we say we want to "view the existing metadata in a project", but then fetch all metadata/tables regardless of the project.

Won't be relevant after refactoring app to use core.


Error when executing

Hello!
I wanted to try your module and I got this error when launching npm run start 👍
D:\electron\surfer-browser>npm run start

><EMAIL_ADDRESS>start D:\electron\surfer-browser
> npm run build && electron ./dist/main.js

><EMAIL_ADDRESS>build D:\electron\surfer-browser
> tsc

[8100:0629/161914.161:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
(node:21480) UnhandledPromiseRejectionWarning: FetchError: request to https://raw.githubusercontent.com/cliqz-oss/adblocker/master/packages/adblocker/assets/ublock-origin/annoyances.txt failed, reason: con
nect ECONNREFUSED <IP_ADDRESS>:443
    at ClientRequest.<anonymous> (D:\electron\surfer-browser\node_modules\node-fetch\lib\index.js:1491:11)
    at ClientRequest.emit (node:events:527:28)
    at TLSSocket.socketErrorListener (node:_http_client:454:9)
    at TLSSocket.emit (node:events:527:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
(Use `electron --trace-warnings ...` to show where the warning was created)
(node:21480) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was n
ot handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode).
 (rejection id: 1)

Hi! It looks like that's an error from the third-party adblocker module provided by cliqz. Maybe they no longer maintain it, or you need to update the module by running npm i @cliqz/adblocker-electron@latest.
If nothing works, you can simply remove the adblocking and the rest of the browser will work fine. To do it, open src/View.ts and delete lines: 5 and 6 and 46, 47, 48.
Anywhere you see adblocker or `ElectronBlocker' or anything like that, you can remove these lines, since the module simply goes 'on top' of the app and is not involved in the logic. But the places I mentioned should be everything.
I will try to work on this later today, so I'll keep you posted and maybe commit a change to the repo.
This is an outdated version of the app btw, I'm building the next iteration of this browser at https://github.com/surferbrowser/surfer. It's a bit different looking though.
PS. it is not a module, but a fully fledged (not really) app.


I would like to build this component

I have experience with building UI designs using figma, for this component I would like to build it with tailwindcss and nextjs.
Here is my portfolio:
Portfolio link

Thanks so much for your interest! Feel free to make a mention of which components you want to work on in that componentxs issue and assign the issue to yourself.


Support SPM, Fix Warnings in Xcode 11.4

Add Package.swift file
Fix a few warnings that hadn't been fixed in the public version
Update the Swift version to 5.0

Closes #69.

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


pubsub: adds basic support

The part of this I'm least keen on is the change of signature in the adapter, from:
func (c *Client) CreateSubscription(ctx context.Context, id string, cfg SubscriptionConfig) (*Subscription, error)

to:
func (c client) CreateSubscription(ctx context.Context, id string, topicID string) (Subscription, error)

The problem is that the SubscriptionConfig struct contains a reference to a pubsub.Topic struct. I'm open to improving this if there are any ideas: taking just the name of the topic sufficed for my basic needs.

The problem is that the SubscriptionConfig struct contains a reference to a pubsub.Topic struct. I'm open to improving this if there are any ideas: taking just the name of the topic sufficed for my basic needs.

This is accounted for IIRC. See nested struct examples in other packages.
ps: I'm OOO next two weeks, so reviews may be a bit slow.
cc @jba who may have some spare time, and designed much of these packages.

I'm working on the CLA, btw. I just need to get our legal team to sign off; that process is underway.

@googlebot I signed it!

Any movement on this? Are there any further changes needed on my side?

Hi @jackwhelpton! Sorry, code reviews are a bit bogged down right now, and some of us are at a summit. Either myself or @hongalex (most likely @hongalex) will get to this ASAP.


added kube version restrictions to rancher chart

Hi, this modification seems to to that bug: rancher/k3d/issues/459
Can you explain why that limitation was added?

Hi, this modification seems to to that bug: rancher/k3d/issues/459
Can you explain why that limitation was added?

Because k8s 1.20 isn't supported by the current Rancher version, and has things that actually don't work correctly.

Because k8s 1.20 isn't supported by the current Rancher version, and has things that actually don't work correctly.

Thanks @vincent99  I will try to downgrade k3s then and should be good to go.  Will update the related issue too if it works.

Thanks @vincent99  I will try to downgrade k3s then and should be good to go.  Will update the related issue too if it works.

It's strange that the latest v4.0 of k3d would use 1.20 if rancher doesn't support it yet.

It's strange that the latest v4.0 of k3d would use 1.20 if rancher doesn't support it yet.

I totally agree!  Many some unexpected problems that show up late in the release process.

I totally agree!  Many some unexpected problems that show up late in the release process.

K3d follows k3s releases and k3s follows kubernetes ones.  None of those are tightly-coupled to Rancher (the product) releases, nor are they necessarily used together.
Rancher has large enterprise users which can't necessarily patch frequently, so it is updated a little more conservatively.
Most of the time this doesn't really matter, because it will work anyway, but in this case 1.20 drops an API field that Rancher uses. So this change was to let you know earlier instead of installing and then finding out.  Until a version that does support 1.20 is available.

K3d follows k3s releases and k3s follows kubernetes ones.  None of those are tightly-coupled to Rancher (the product) releases, nor are they necessarily used together.
Rancher has large enterprise users which can't necessarily patch frequently, so it is updated a little more conservatively.
Most of the time this doesn't really matter, because it will work anyway, but in this case 1.20 drops an API field that Rancher uses. So this change was to let you know earlier instead of installing and then finding out.  Until a version that does support 1.20 is available.


Instructions to boot from NVME SSD drive

Ciao Mattia,
I tried the instructions referenced in the Github website, but it seems like there is a problem already with the 1st line of code: the system doesn't find the files to download (see attached image).
Any suggestion on how to proceed?
Thanks!
Stefano

@Astrostecco that's a long issue with archlinux mirrors, try first to update the package database with sudo pacman -Sy and if fails again with 404, try few times, it should go

it worked, thank you so much!! :)

I had the same issue. I fixed editing the file /etc/pacman.d/mirrorlist:
sudo nano /etc/pacman.d/mirrorlist
replacing the line:
Server = http://mirror.archlinuxarm.org/$arch/$repo
with:
Server = http://eu.mirror.archlinuxarm.org/$arch/$repo
getting it from the mirror list page
Should I get back to mirror.archlinuxarm.org in future?

@teoteo probably not, ther main mirror which is supposed to load balance based on region still redirects to stuff that doesn't work


Suggestion: Multiplier arrows

Ok I think I had a great idea. What's about arrows you can craft like:
1 arrow + 8 stone = 1 stone arrow
1 stone arrow + 8 iron = 1 iron arrow
then gold, smaragd, dia, netherite
Then every custom arrow has an multiplier, for example:

stone *2
iron *3
gold *5
smaragd * 10
dia *25
netherite *50

(just example values, maybe will cause lags if so high)
Then the multiplier is applied to the bows:

Mob bow with dia arrow = 25 Mobs
Explosive bow with smaragd = 10 times bigger explosion
etc.

Maybe you could add a config option for cooldowns where you can set a cooldown for every arrow sort. So the players can't shoot like 10 netherite arrows and spawn 500 mobs in like 30 seconds or so.
And maybe there could be also a config option for the multipliers so the server admin can set them himself to values he want.
I know it's a complicated feature but I think it would be cool. But of course you have not to add it if its too hard for you. Then I will add it when I have time. But if you want to add it yourself and need any help feel free to ask.
(btw sorry for spelling and bad formating typed this fast on mobile ^^)

Well i think it's a good idea too, but this means the plugin will have literally another "life", what about making a new plugin together? I'm new to Java and Spigot so it is complicated for me, but if you want we can collaborate and create UltimateArrows together xD

xD
I see your point but I dont see what use an extra plugin would have. I mean if we put this in an extra plugin the extra plugin would have no other use expect for ubows.

So the only result would by that the user would have to download 2 plugins instead of 1 and the 2nd plugin would be completly uselesd without ubows.

xD
I see your point but I dont see what use an extra plugin would have. I mean if we put this in an extra plugin the extra plugin would have no other use expect for ubows.

Basically, UltimateBows adds new bows, UltimateArrows adds new arrows, we can make it as an add-on and standalone plugin. A player will be able to use only UltimateBows or only UltimateArrows or both.

But what use would a standalone UltimateArrows have?

But what use would a standalone UltimateArrows have?

I explained myself wrong, i meant to make a new plugin that basically adds explosive arrows etc instead of bows, then we could add special arrows in UltimateBows of course.

So like the same plugin expect the bows are default and the arrows add the effects etc.?

If so what would happen if a player shoots an explosive arrow with an explosive bow? Or an teleport arrow with an lava bow. I mean this would mean death to the player lol.

If so what would happen if a player shoots an explosive arrow with an explosive bow? Or an teleport arrow with an lava bow. I mean this would mean death to the player lol.

Ok, didn't think about that lol.
You're right, another plugin isn't really the solution, it's better adding the feature you just proposed.

xD
Leave this issue and add the other features first. I'll think about this a bit and may I'll find a solution.


Imperium not working after installing xeninfo

Fill out the the guided issue template with neccessary and any extra information, thanks!
For the title, follow this example: Tweak - Short Bug Description

Tweak/Theme:
Version:
Device:
iOS Version:

Issue/Bug:

Additional Comments:

Thanks for reporting! Will look into it.

I've tested with XenInfo and had no issues, try going into Imperium settings and re-selecting settings.

i downgraded to 1.3 and it works just fine. Ill try upgrading and reset the
settings.
On Sat, Jul 28, 2018 at 3:48 PM, LacertosusDeus<EMAIL_ADDRESS>wrote:

I've tested with XenInfo and had no issues, try going into Imperium
settings and re-selecting settings.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/LacertosusRepo/LacertosusRepo.github.io/issues/6#issuecomment-408639638,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWeVBG0pQKEEAzoACcSi3v1RtviGHz6hks5uLOoigaJpZM4Vk7nL
.

I tried deleting the setting and reinstalling but it doesn’t work on my 6s. Only 1.3 works.
Sent from my iPhone

On Jul 28, 2018, at 3:48 PM, LacertosusDeus<EMAIL_ADDRESS>wrote:
I've tested with XenInfo and had no issues, try going into Imperium settings and re-selecting settings.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Strange! Ill link an experimental build i have going right now, see if that fixes your issue. Im
guessing its something wrong on my end, not XenInfo. Here is the download.

Issue was my preferences! Not XenHTML. Should be fixed in version 1.5.


Add MVC guidelines and best practices

See: https://github.com/commercetools/sphere-maximilian/commit/b036f38ec9ab3d1c16fdd6e330bab9a8ab4c7f4e#commitcomment-6726975

Done: https://github.com/sphereio/sphere-sunrise/blob/master/GUIDELINES.md


feat: Support Windows and Nightly builds

Make the download more portable to support Windows. Add support for nightly versions.

I cancelled the CI to save capacity, lmk when you debug and want to try again


Middleware not run when source folder is empty

While developing my metalsmith-watch plugin I noticed that a middelware is only run when there is at least one file in the source folder.
I think each plugin should decide what to do in a case of an empty files object.
In the case of my watch plugin it would be to start watching for changes.

Closing this since it's old, but feel free to re-open or submit a PR!


New package: TestReports v0.2.0

Registering package: TestReports
Repository: https://github.com/JuliaTesting/TestReports.jl
Created by: @oxinabox
Version: v0.2.0
Commit: 049c2ace3c41d6f8d48e54bfb94b92bb13bdfc5a
Reviewed by: @oxinabox
Reference: https://github.com/JuliaTesting/TestReports.jl/commit/049c2ace3c41d6f8d48e54bfb94b92bb13bdfc5a#commitcomment-40159188

[noblock]
v0.1 of this package was released for julia 0.6, and was removed from the registry due to not supporting julia 1.0.
But @mmiller-max fixed it up and made it work for modern julia.
This the first release into the General Registry is v0.2.
Thought it is tempting to just go ahead and release it as 1.0

thanks, that worked


Remove pudl postgres database!!

Once we are at the point of converting over fully to data packages, there will be lots of things we need to get rid of which reference the database that will no longer be relevant...

[x] models! all of them...
[x] all the functions tagged with Remove upon removal of pudl_db todo's
[ ] postgres dependencies
[ ] init.py

[ ] the db connections
[x] everything else!

[x] any keep_csv reference

I'm sure there is more...

Hey @karldw! are you using the views for CEMS? It looks like they can be easily converted away from using the models' metadata definition but I figured I should check in with you about it before spending the time converting them.

I'm not! I've moved to an all-parquet workflow. Thanks for checking!
(I agree that it wouldn't be too hard to convert, but there's no need.)


CB-11017 In case of GCP, If we don't send the volume type, we set HDD…

… as default but this type doesn't exist and this leads to an NPE. Validation added and HDD added to the diskTypes list
See detailed description in the commit message.

If someine try to create a GCP datahub without volume type, we convert it to HDD. But this value doesn't exist and we should add the HDD to the mapping list.


Chapter 5, Excercise 10

Hello,
to complete this exercise I directly implemented LinearSVC into the coding of Chapter 2.
As data I used housing_prepared and as labels I used housing_labels.
In the end I just trained the SVM regressor like that:
svm_reg = LinearSVR(random_state=42)
svm_reg.fit(housing_prepared, housing_labels)

The score is quite unusual (compared to RandomForest and Linear Regression):
housing_predictions = svm_reg.predict(housing_prepared)
svm_reg_mse = mean_squared_error(housing_labels, housing_predictions)
svm_reg_rmse = np.sqrt(svm_reg_mse)
svm_reg_rmse

218339.15956036837

Why is it so badly underfitting the data? Why is the error in the exercise 10 so much lower, although the data should be more or less the same (Housing_prepared additionally is scaled, uses the imputer and the OneHotEncoder for Ocean Aprox. and adds some attributes).
thanks

The question states to train a Support Vector Regressor NOT a LinearSVR. There is a significant difference between the two.
To put it simply, imagine fitting a line of best fit into predicting houses prices. We would not expect the house prices to be a linear relationship with any one of the features that we have, concretely, if the number of bedrooms increased would you expect the house price to increase linearly also? Or if the house area increased would the house prices increase linearly too?
Sure, there is a positive relationship between these features but are they linear? Definitely not.
If you do .fit the data with a SVR - don't forget to import first sklearn.svm import SVR - you should see a better model.
Also, the large RMSE error that you have is a great example of poor model selection, assuming the data is linear when the data is actually more complex - everyone has tried to fit a poor model before (me included! 😃)
To put it in more technical language this is a prime example of the Bias/Variance Trade-Off, the 'LinearSVC' generalization error is due to incorrect assumptions about the data causing the model to underfit the training data.
P.S. Don't forget to split your data into training, validation and testing datasets - the validation dataset, amongst many other things, is there so you can eliminate models that have large bias errors such as this one.

Many thanks for your explanation although now I am even more confused :) What is the difference? I thought that SVR can be linear and polynomial.
In chapter 5, topic SVM Regression, it tells "You can use Scikit-Learn’s LinearSVR class to perform linear SVM Regression" and in the solution of this exercise the author used LinearSVR(random_state=42) as well.
Also, when using the training data as stated in the solutions I got excellent results. I only got this bad results when using the prepared data from the chapter. This I do not understand.

To put it in more technical language this is a prime example of the Bias/Variance Trade-Off, the 'LinearSVC' generalization error is due to incorrect assumptions about the data causing the model to underfit the training data.

But I do not use the classifier, I used LinearSVR - regressor.
many thanks

Support Vector Regressors can be both linear and polynomial but the LinearSVR is only linear.

the solution of this exercise the author used LinearSVR(random_state=42) as well.

He later used the SVR, which outperformed the LinearSVR.

prepared data from the chapter.

Has your prepared data been scaled and is the pre-processing being performed using column transformer and a pipeline ?

This I do not understand.

Bias/Variance trade off is covered in the book 👍

But I do not use the classifier.

Oops, that was a typo, has been corrected now 😃

all right, thank you very much for your kind help.

Has your prepared data been scaled and is the pre-processing being performed using column transformer and a pipeline ?

Regarding that, I simply followed the steps from Chapter 2 till I got housing_prepared (except CombinedAttributesAdder(), although it doesn't make any difference). That means:
from sklearn.pipeline import Pipeline
from sklearn.preprocessing import StandardScaler

num_pipeline = Pipeline([
    ('imputer', SimpleImputer(strategy="median")),
    ('std_scaler', StandardScaler()),
])

And:
from sklearn.compose import ColumnTransformer
num_attribs = list(housing_num)
cat_attribs = ["ocean_proximity"]
full_pipeline = ColumnTransformer([
    ("num", num_pipeline, num_attribs),
    ("cat", OneHotEncoder(), cat_attribs),
])
housing_prepared = full_pipeline.fit_transform(housing)

I also tried the SVR today but the score is more than 100k. So I guess the problem is the data.

all right, thank you very much for your kind help.

Has your prepared data been scaled and is the pre-processing being performed using column transformer and a pipeline ?

Regarding that, I simply followed the steps from Chapter 2 till I got housing_prepared (except CombinedAttributesAdder(), although it doesn't make any difference). That means:
from sklearn.pipeline import Pipeline
from sklearn.preprocessing import StandardScaler

num_pipeline = Pipeline([
    ('imputer', SimpleImputer(strategy="median")),
    ('std_scaler', StandardScaler()),
])

And:
from sklearn.compose import ColumnTransformer
num_attribs = list(housing_num)
cat_attribs = ["ocean_proximity"]
full_pipeline = ColumnTransformer([
    ("num", num_pipeline, num_attribs),
    ("cat", OneHotEncoder(), cat_attribs),
])
housing_prepared = full_pipeline.fit_transform(housing)

I also tried the SVR with RandomizedSearchCV today but the score is more than 100k. So I guess the problem is the data.

The data used in chapter 5 is from sklearn which is a prepared version that only requires standard scaling and not OneHotEncoding. Take a look at the notebook: https://github.com/ageron/handson-ml2/blob/master/05_support_vector_machines.ipynb

Thanks for your question @ofe-57 , and thanks to @ashishthanki for the great answers.
Is everything clear now @ofe-57?


Reimplement the MSBuild VSTestTask task based on ToolTask

Description
The MSBuild ToolTask class was designed to help create custom tasks that wraps a command line tool, which is exactly what VSTestTask does (it wraps dotnet.exe exec vstest.console.dll). Using it allows to delete unneeded code while fixing #680.
The console output lost its colorized output (which was expected) but the task gained the ability to be logged.
A bit of maintenance was performed as well, making use of boolean properties where needed (instead of strings), and of ITaskItems for paths (instead of strings as well). Those changes should be compatible with existing usage though.
Unit tests have been refactored as well along the lines of the new implementation (and are all green, obviously). A real world test has been performed on a project of mine that was affected by #680, on Windows 10 only.
This might need further real world testing.
Related issue
Fixes #680

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

I don't seem to be able to execute the failling test on my computer (Visual Studio or CLI) and I fail to see how those are related to my changes. Please advise.

The console output lost its colorized output (which was expected)

Hmm that's a blocker IMHO. We want out colored output even when running from dotnet test.

Would re-run the pipeline, but it has conflicts. I don't see how the failing test would be related to your changes either.

There was no conflict 4 days ago... I'll try and fight my way through git to resolve this (I may learn 1 or 2 things along the way :grin:).
MSBuild always had its own coloring scheme (blue for projects, light gray for command lines, dark gray for command output...) and overriding this would require developing a special case. Note that messages output to the error console show up in red (and obviously fail the task).

There was no conflict 4 days ago... I'll try and fight my way through git to resolve this (I may learn 1 or 2 things along the way 😁).

You just need:
# add a remote pointing to the original repo
# (this is usually called upstream), while your fork is called origin
git add remote upstream  https://github.com/microsoft/vstest.git
# update your forks master to our master
git checkout master
git pull upstream master
# merge your master to your PR branch
git checkout vstesttask
git merge master
# solve conflicts
... <solve>
git add
git commit -m"Merge master"
# push to update the PR
git push

That said, I don't think this would get merged if we would lose the colors.

😁  I love the just followed by 20 git commands

Thanks. I went with a rebase (along the lines of https://github.com/edx/edx-platform/wiki/How-to-Rebase-a-Pull-Request).
You may want to check that I have not messed up too much with your latest commit (I changed some properties to boolean to be consistent with the rest of my PR. You could even use enums for the DumpType arguments...).
As for the color, as I wrote it is inconsistent with MSBuild, but if you insist I'll see what I can do.

From what I can gather it is not possible to log and keep the colored output. You need to choose:

ProcessStartInfo.RedirectStandardOutput (on which ToolTask is based) redirects only the textual output.
There might be a way to implement a custom console redirection routine using the ReadConsoleOutput Windows API, but it seems daunting enough for Windows: I cannot imagine myself handling this stuff cross platform.

Please note that in the case of #680 the reporter would be (understandably IMHO) more interested in a searchable log than in a colored output, and that in my use case (MSBuild on AppVeyor) I don't even have a console output: only a log, which is empty.

Closing this PR since it would affect expected color output.


Missing documentation for fs subsystem

There is no documentation on fcb or nffs.
Specially how it behaves vs flash supported write-block-size...

@nvlsianpu  can you look into this issue as fcb and nffs are owned by you.

@ramakrishnapallala this is less about the specific filesystems and more about the virtual file system interface and fs support in general.

fcb doc is missing - can be take form mynewt.
NFFS is external project as well - currently not well documented, can consider documentation making but, for sure no now.

@nashif  Can we consider this as lack of documentation, not a bug. I would create separate issue for both subjects.

lack of documentation is a BUG :)
I would start here: https://docs.zephyrproject.org/latest/reference/file_system/index.html
This is currently the API only need more content to the file system feature in general. Probably a quick into about the supported filesystems with details to be added later.

I will start on adding more documentation to the API's

Pushed PR: https://github.com/zephyrproject-rtos/zephyr/pull/14796/

@nvlsianpu what about documenting fcb and nffs?

FCB doc I can copy form MyNewt.
NFFS is under fixing now - expects that It will change a lot. I would only refer to its design.txt file and describe its limitation.

@nvlsianpu any updates?

@nvlsianpu ping

I'm Preparing FCB doc right now.

FCB documentation: https://github.com/zephyrproject-rtos/zephyr/pull/17425

FCB is now documented and NFFS is on the path to deprecation, so closing this.