mCODE Radiation Procedure Extractor

Summary
This PR adds a new extractor for mCODE Cancer Related Radiation Procedures.
New behavior
The approach I took for this extractor is similar to the Epic Conditions extractor. It will get all Procedure resources using the regular FHIR Procedure extractor and then will filter that list to only include ones that have a code in the mCODE VS for Cancer Related Radiation Procedures.
Code changes
Adds the new extractor and adds tests for the new extractor.
Testing guidance
Since this extractor uses the FHIR services to get procedures, you'll need to test it using the epic-MEF repo. There is a PR there to help set up your config and instructions to test it out.

I've got a tedTalk prepared and everything, but the short version is that I think the approach to context used here and in @jafeltra's PR needs removal in the short-term and reconsideration in the medium term.
To illustrate, imagine using the MCODESurgicalProcedureExtractor and MCODERadiationProcedureExtractor in tandem, without the generic FHIRProcedureExtractor. The Context-check in the second extractor, our MCODERadiationProcedureExtractor, will check for resources of a type Procedure when deciding if the total FHIRProcedure request is necessary. Since there will be Procedures, namely SurgicalProcedures, we never perform the FHIRProcedure call. This means we won't identify any RadiationProcedures.


Provide a way to determine if an sbt Project is a Scala.js project

It would be convenient if it were possible to determine if an sbt Project is a Scala.js project.
Perhaps something like this (which I have for now in user-land):
import sbt._
import sbt.Keys._

object IsScalaJsProjectAutoPlugin extends AutoPlugin {
  override def requires = plugins.JvmPlugin
  override def trigger = allRequirements

  object autoImport {
    val isScalaJsProject = settingKey[Boolean]("Determines if a project is a Scala.js project")
  }
  import autoImport._

  override def globalSettings: Seq[Setting[_]] = Seq(isScalaJsProject := false)

  override def projectSettings: Seq[Setting[_]] = Seq(
    isScalaJsProject := libraryDependencies.value.exists(_.name == "scalajs-library")
  )
}

Example output:
> show isScalaJsProject
[info] str/*:isScalaJsProject
[info] 	false
[info] strJs/*:isScalaJsProject
[info] 	true
[info] strRoot/*:isScalaJsProject
[info] 	false

Was this removed in 1.0? Is there an alternative we can use?

It was superseded by crossProjectPlatform.value == JSPlatform, offered by sbt-crossproject.


Refactor rngs ppf

Refactors the RNG refactor to use slots, and to use ppf as an alternative solution to the repeated slot handling code.

In almost all cases, the "standard" solution works fine: take the basic method (e.g. rng.uniform(low, high, size)), where size=n if not using UIDs, and size=sim.people.slot[uids].max()+1 if using UIDs.
The only case in which this doesn't work is if there are repeated slots and array (or callable) parameters. Now what happens in this case is that:

The number of random numbers drawn are as before: size = sim.people.slot[uids].max()+1
The quantile for each slot is drawn: qq = rng.random(sze)
The slots in use are pulled out: qqs = qq[slots]
These are then mapped to the actual distribution via the inverse CDF, aka PPF, e.g.: rvs = scipy.stats.uniform(low, high).ppf(qqs)

Two agents who share the same slot will have exactly the same quantile, but they can still map to different values since the distribution parameter values can be different. Even though calling ppf is typically slower than generating new random numbers, since this is only for a corner case, and since ppf is only called for the slots that are in use, it should be as fast or faster than the other implementation.
For known issues, see https://github.com/starsimhub/starsim/issues/422

Note also that Bernoulli and Poisson need special handling as p=0 and lam=0, respectively, do not use random numbers.

Note also that Bernoulli and Poisson need special handling as p=0 and lam=0, respectively, do not use random numbers.

Would this still be an issue on this branch? If so could you write a test demonstrating it?


safety feature for protecting against faulty clients resulting 'too many open files'

My 8-node etcd cluster started dying one by one with logs like this.
2015/06/06 21:52:41 sender: error posting to 6b7bf4d1bfed0b88: dial tcp: lookup machine1 on <IP_ADDRESS>:53: dial udp <IP_ADDRESS>:53: too many open files
2015/06/06 21:52:41 sender: the connection with 6b7bf4d1bfed0b88 became inactive
2015/06/06 21:52:41 etcdserver: failed to purge wal file open /etcd-data/member/wal: too many open files

After re-starting the cluster, I found out that it was one of the clients that were not closing the tcp sessions. Doing a netstat on one of the client machines, shows some hundred lines of these.
tcp        0      0 <IP_ADDRESS>:46329          <IP_ADDRESS>:2379          ESTABLISHED -
tcp        0      0 <IP_ADDRESS>:34365          <IP_ADDRESS>:2379          ESTABLISHED -
tcp        0      0 <IP_ADDRESS>:44023          <IP_ADDRESS>:2379          ESTABLISHED -
tcp        0      0 <IP_ADDRESS>:44853          <IP_ADDRESS>:2379          ESTABLISHED -
tcp        0      0 <IP_ADDRESS>:46100          <IP_ADDRESS>:2379          ESTABLISHED -
tcp        0      0 <IP_ADDRESS>:55834          <IP_ADDRESS>:2379          ESTABLISHED -
tcp        0      0 <IP_ADDRESS>:49015          <IP_ADDRESS>:2379          ESTABLISHED -
tcp        0      0 <IP_ADDRESS>:44655          <IP_ADDRESS>:2379          ESTABLISHED

My question is,
Is there any way that I can setup etcd servers to protect against these faulty clients using up all my fd's?  Maybe set a shorter timeout for established TCP sessions? Set a limit per ip?

Now that we have an authorization API one thing we can do is limit the number of connections a single client can make (thoughts @barakmich?). We also intend to reserve fds in the future (https://github.com/coreos/etcd/issues/2477#issuecomment-87766974).

Help on either of these ideas would be appreciated @difro

ok. I still have the faulty client binary lying around here, so maybe I can test new stuff ?

etcd stop accepting client conns when it reaches pre-set limit and leaves enough fds for internal usage now. See https://github.com/coreos/etcd/pull/3219 for more details.
You are welcome to test this with your client binary. I have tested it with amounts of clients at the same time and it works fine. :)


Print screen is out of date

In "Access storage accounts as a trusted service with managed identities", the print screen is out of date.
Storage account firewall now has the "Resource instances" feature, which has no documentation yet.
It's also ambiguous if it's possible to restrict by IP AND managed identities, or if you can only use managed identities since no public IPs are present in the picture.

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

ID: bc1a51f6-730a-6077-6f9d-90afeaceed20
Version Independent ID: 6d012a9a-5fbd-fd18-9656-c42e88bac5d0
Content: Connect to Azure Blob Storage - Azure Logic Apps
Content Source: articles/connectors/connectors-create-api-azureblobstorage.md
Service: logic-apps
GitHub Login: @ecfan
Microsoft Alias: estfan

Hello @rpalves,
Thank you for your feedback! We have assigned this issue to the author to review further and take the next course of action.

Hi @rpalves,
Thanks for providing this feedback! We've created a doc work item on our backlog to address this work. We'll close this item for now, but report back when the doc is updated.
@ChaitanyaNaykodi-MSFT: #please-close


Issue with image links that are having GET methods in the url bar

So let's say I have this piece of code

And then send the next URL image to the Node Js server to check it's mime type
https://static.independent.co.uk/s3fs-public/thumbnails/image/2017/09/12/11/naturo-monkey-selfie.jpg?w968h681
Bug: The function is returning null because of the "?w968h681" part of the url which is a GET request to resize the image.
When I remove that GET request the mime type is returned with no problems at all.

The image is correctly detected when I download it locally, so the problem is in your logic, not image-type. I would not recommend trusting that the chunk is large enough. You should explicitly ask for a large enough chunk. See the example in the readme on how to do it correctly: https://github.com/sindresorhus/image-type#usage

Did as it's said in your example and if I put it in a loop for over more than one image I get this error


failed to read or create private key

server start fail
2023-11-29T16:52:35+08:00 TRC DNS configuration loaded dns_config={"ExitNodeFilteredSet":null,"FallbackResolvers":[{"Addr":"<IP_ADDRESS>"}],"Nameservers":["<IP_ADDRESS>"]}
2023-11-29T16:52:36+08:00 INF No private key file at path, creating... path=
2023-11-29T16:52:36+08:00 FTL ../../../home/runner/work/headscale/headscale/cmd/headscale/cli/server.go:21 > Error initializing error="failed to read or create private key: failed to save private key to disk: open : no such file or directory"
but my config file have
# Listens over UDP at the configured address for STUN connections - to help with NAT traversal.
# When the embedded DERP server is enabled stun_listen_addr MUST be defined.
#
# For more details on how this works, check this great article: https://tailscale.com/blog/how-tailscale-works/
stun_listen_addr: "<IP_ADDRESS>:3478"
# Private key used to encrypt the traffic between headscale DERP
# and Tailscale clients.
# The private key file will be autogenerated if it's missing.
#
private_key_path: /var/lib/headscale/derp_server_private.key

2023-11-29T20:10:17+08:00 TRC DNS configuration loaded dns_config={"ExitNodeFilteredSet":null,"Nameservers":["<IP_ADDRESS>"],"Proxied":true,"Resolvers":[{"Addr":"<IP_ADDRESS>"}]}
2023-11-29T20:10:18+08:00 INF No private key file at path, creating... path=
2023-11-29T20:10:18+08:00 FTL go/src/headscale/cmd/headscale/cli/server.go:21 > Error initializing error="failed to read or create private key: failed to save private key to disk: open : no such file or directory"

The config example file is missing the private_key_path. It was removed on this commit.

I had the same error, when trying to start the service it sent me the error that it could not create the key or that the directory did not exist. All tests I am doing are on an OS: Rocky Linux 8.9 (Green Obsidian) x86_64
Kernel: 4.18.0-513.11.1.el8_9.x86_64.
At first I thought it was SElinux that was blocking me, but after analyzing the logs, I realized that it was not the cause of my headache, I was analyzing the configuration file and everything was fine, there was no error syntax, and I followed all the possible solutions referred to and none of them worked for me. I still had the message:
FTL ../../../home/runner/work/headscale/headscale/cmd/headscale/cli/server.go:21 > Error initializing error="failed to read or create private key: failed to save private key to disk: open : no such file or directory".
So as a final task, I set out to change the version of headscale from 0.22.3 to v0.23.0-alpha3, once the change was made, I finally have Headscale running.

Same error, after changing from 0.22.3 to 0.23.0-alpha9, Headscale run successfully.

I have the same error but would like to stay on 0.22.3
What can I do?

Your ideas are to stay in the official version without going up to the
alpha version, that's how it is. If so, I would like to know what
version of the operating system you are using, this way only the
committees that were corrected from the alpha version would be added.
El dom, 12 may 2024 a las 16:21, n0valis @.***>)
escribió:

I have the same error but would like to stay on 0.22.3
What can I do?
—
Reply to this email directly, view it on GitHub
https://github.com/juanfont/headscale/issues/1624#issuecomment-2106393095,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUBJH5YKGJIUOQ4DXOVKPWTZB7TPPAVCNFSM6AAAAAA77C36JWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGM4TGMBZGU
.
You are receiving this because you commented.Message ID:
@.***>

--
Ricardo Alexander Lopez Medina
  GNU/Linux 1999-2021

Redhat, CentOS, CL, Fedora,OpenSuse,FreeBSD,RockyLinux,AlmaLinux

Your ideas are to stay in the official version without going up to the alpha version, that's how it is.

I think my fault was to not thouroughly check the config.yaml I forgot to check the changes between versions.
Starting with a fresh config.yaml form 22.3 resolved the issue

Having this issue with a fresh install and the default example config. Ill be using a reverse proxy and have no path set.

I was having this exact same issue after using a modified config-example file. Using build 0.23.0-alpha9 also solved the issue for me :)

Looks like thats the issue @Xopher00 - ty.


Pavel

setValue bug fixed

@paveltech Thanks for your efforts , but this issue had already been solved in version 1.0.2  you can check it


Different Behavior of tf.raw_ops.SquareDifference+tf.raw_ops.Cos with jit_compile=True

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
2.14.0
Custom code
Yes
OS platform and distribution
Ubuntu 22.04.3 LTS (x86_64)
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
11.8
GPU model and memory
GPU 0: NVIDIA GeForce RTX 2070 GPU 1: NVIDIA GeForce RTX 2070 GPU 2: NVIDIA GeForce RTX 2070 GPU 3: NVIDIA GeForce RTX 2070
Current behavior?
When the tf.raw_ops.SquareDifference+tf.raw_ops.Cos operation is invoked within a tf.function with JIT compilation enabled (jit_compile=True), it produces different results compared to the same operation called without JIT compilation. This inconsistency is observed when the code is executed on a CPU device.
Standalone code to reproduce the issue
import tensorflow as tf
import traceback

class Network(tf.Module):
    def __init__(self):
        super().__init__()

    @tf.function(jit_compile=True)
    def __call__(self, x):
      real_part = tf.random.normal([1], dtype=tf.float32)
      imag_part = tf.random.normal([1], dtype=tf.float32)
      tensor = tf.complex(real_part, imag_part)
      tensor = tf.cast(tensor,dtype=tf.complex64)
      x = tf.raw_ops.SquaredDifference(y=x, x=tensor)
      x = tf.raw_ops.Cos(x=x, )
      return x

m = Network()
real_part = tf.random.normal([8, 2], dtype=tf.float32)
imag_part = tf.random.normal([8, 2], dtype=tf.float32)
tensor = tf.complex(real_part, imag_part)
tensor = tf.cast(tensor,dtype=tf.complex64)
inp = {
    "x": tensor,
    }

with tf.device('/CPU:0'):
    tf.config.run_functions_eagerly(True)
    no_op_res = m(**inp)
    tf.config.run_functions_eagerly(False)
    with tf.device('/CPU:0'):
        op_res = m(**inp)

    tf.debugging.assert_near(tf.cast(no_op_res, tf.float64), tf.cast(op_res, tf.float64), atol=0.001, rtol=0.001)

Relevant log output
File "/home/guihuan/LLM/results/tf-2/2023-10-22-20-21/test.py", line 34, in <module>
    tf.debugging.assert_near(tf.cast(no_op_res, tf.float64), tf.cast(op_res, tf.float64), atol=0.001, rtol=0.001)
  File "/home/guihuan/.conda/envs/night/lib/python3.9/site-packages/tensorflow/python/util/traceback_utils.py", line 153, in error_handler
    raise e.with_traceback(filtered_tb) from None
  File "/home/guihuan/.conda/envs/night/lib/python3.9/site-packages/tensorflow/python/ops/control_flow_assert.py", line 102, in Assert
    raise errors.InvalidArgumentError(
tensorflow.python.framework.errors_impl.InvalidArgumentError: Expected 'tf.Tensor(False, shape=(), dtype=bool)' to be true. Summarized data: b''
b'x and y not equal to tolerance rtol = tf.Tensor(0.001, shape=(), dtype=float64), atol = tf.Tensor(0.001, shape=(), dtype=float64)'
b'x (shape=(8, 2) dtype=float64) = '
-0.9023030400276184, -0.8812462687492371, -0.6324461102485657, ...
b'y (shape=(8, 2) dtype=float64) = '
-0.8898392915725708, 0.49911314249038696, -0.15750333666801453, ...
(night) guihuan@heyuan2:~$

@sachinprasadhs,
I was able to reproduce the issue on tensorflow v2.14 and tf-nightly. Kindly find the gist of it here.

I observe similar result in both jit_compile = True and jit_compile = False, since when compiling with JIT takes different code path and involves fusion operation and casting dtype to specific dtype, based on all these conditions, you can't expect the same result with JIT and without JIT.
Also when you are involving random number in the operation, it will give different result for each run.
Attaching the Gist here for comparison. Thanks!


Update OneSignalPushAdapter.js [Parameters support]

OneSignal Parameters can now be passed as described in the documentation: https://documentation.onesignal.com/v2.0/docs/notifications-create-notification

@mithleshjs seems that the tests are failing, looks like you're breaking backwards compatibility


Pagination feature

Hi I would like to share this feature that I am currently working on for the TableView which is pagination, currently the pagination works fine for basic data loading, but I still continue to fix conflicting issues with sorting and filtering.
NOTES:

I added a Listener interface for the AbstractTableAdapter which notifies when any changes on row, column and cell items occurs. I will also update the filtering implementation to use the listener instead of storing the original data into another class. Don't worry, I didn't change any of your code/implementation of the TableView, I only added extensions.
I will not submit a PR yet unless sorting and filtering issues are resolved.

Functional:

Pagination on standalone data loading, meaning dataset is not modified yet by sorting or filtering.
Go to page functionality.
Loading next and previous pages.
Loading number of items per page which can be set.

Bugs:

Sorting and filtering conflicts.
No retention of sorting and filtering on pagination actions, any filter or sorting is lost on page changing.
Filtering only applies to current page.
Sorting only applies to current page.
Many more...

Thank you @jeremy-ingenuity,
I haven't finished to review the changes. But there are some wrong usages on your codes that may cause some bugs that you listed. And I've noted for you.
As soon as the review process is over, I will share the notes to you on github.
However, the process will not be done today because of my busy schedule. So, that would be great to release the new version next week. Thus, we may fix the bugs during this time.
Have a nice weekend

I have an updated preview here with the implemented number of items to be displayed per page.

@evrencoskun Thank you! I'll continue to improve this if I also have free time. It's okay, no pressure man. Have a nice weekend also.

@jeremy-ingenuity, I've reworked sorting recently and moved the sorting state into the Column Header Cell (was in the recycler before), this might fix some issues, like the retention.

Hi @jeremy-ingenuity ,
0.8.6 version which has got paging and filtering functionallies,  has been released. I have also updated the README. However, these topics need more explanations for developers.
For example; the steps to implement these functions would be very useful for developers like sorting topic
Thank you 👍

Hi @evrencoskun , good day! Thanks for the update. Don't worry, I will help in providing comprehensive documentation and implementation updates for the features of the TableView. I will help update the README and submit a PR when I have free time.

Perfect :)
Have a nice day


add prifddinas plugin

Removes some clutter from prif

I think this line may be incorrect, as that object is named "Flax". LGTM otherwise

I've updated the plugin removing that line -- I wanted to remove some ground decoration and got the object ID instead. In the end I removed the code to remove the ground decorations (rocks, grass, etc) as the perf didn't change at all and it has a significant visual impact


Rabbit integration for /users/password

Waterline RabbitMQ Adapter

https://github.com/waterlinejs/rabbitmq-adapter

RabbitMQ Adapter for Sails and Waterline (AMQP 0.9). Implements the Waterline pubsub interface. The RabbitMQ Adapter does not support persistence on its own, and should always be used with another adapter, such as sails-mongo or sails-postgresql. This module is maintained in collaboration with Michigan Community College Association.

waterline-rabbitmq-simple

https://github.com/DevAlien/waterline-rabbitmq-simple

rabbitmq adapter for sails/waterline, removed a lot of functionality from sails-rabbitmq
RabbitMQ Adapter for Sails and Waterline (AMQP 0.9). it is based on sails-rabbitmq I had to modify to fit our needs, there's just a simple PUSH.

Just to note:DevAlien/waterline-rabbitmq-simple is just a fork of waterlinejs/rabbitmq-adapter.

Simple integration is finished in #93.


Wifi contacts DW2-Wi-Fi not working after latest HACS update. v3.0rc1.

Wifi contacts DW2-Wi-Fi not working, showing as unavailable in Home Assistant but work ok in Ewelink App after latest HACS update. v3.0rc1.

I have just rebooted my wifi and they have come back. however they are now not changing state. i think this issue relates to issue #666 as they are  now not changing state on the Ewelink app.


fix(story): always return true for watch_users_reels

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Additional documentation e.g. usage docs, etc.:

please merge against development branch

Travis tests have failed
Hey @kevinjulian,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.
1st Build
View build log

     $PRE_COMMIT_CMD

[INFO] Initializing environment for https://github.com/pre-commit/pre-commit-hooks.
[INFO] Initializing environment for https://github.com/psf/black.
[INFO] Initializing environment for https://gitlab.com/pycqa/flake8.
[INFO] Initializing environment for https://github.com/asottile/pyupgrade.
[INFO] Installing environment for https://github.com/pre-commit/pre-commit-hooks.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
[INFO] Installing environment for https://github.com/psf/black.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
[INFO] Installing environment for https://gitlab.com/pycqa/flake8.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
[INFO] Installing environment for https://github.com/asottile/pyupgrade.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
Fix End of Files.........................................................Passed
Trim Trailing Whitespace.................................................Passed
Check docstring is first.................................................Passed
Check Yaml...............................................................Passed
Debug Statements (Python)................................................Passed
Check python ast.........................................................Passed
black....................................................................Failed
- hook id: black
- files were modified by this hook

reformatted /home/travis/build/instagrambot/instabot/instabot/api/api.py
All done! ✨ 🍰 ✨
1 file reformatted, 112 files left unchanged.

flake8...................................................................Passed
pyupgrade................................................................Passed
pre-commit hook(s) made changes.
If you are seeing this message in CI, reproduce locally with: `pre-commit run --all-files`.
To run `pre-commit` as part of git workflow, use `pre-commit install`.
All changes made by hooks:
diff --git a/instabot/api/api.py b/instabot/api/api.py
index 16f6a4a..3242290 100644
--- a/instabot/api/api.py
+++ b/instabot/api/api.py
@@ -272,7 +272,6 @@ class API(object):

             elif (
                 self.last_json.get("error_type", "") == "checkpoint_challenge_required"
-
             ):
                 # self.logger.info("Checkpoint challenge required...")
                 if ask_for_code is True:
@@ -1702,14 +1701,22 @@ class API(object):

     # ====== DIRECT METHODS ====== #
     def get_inbox_v2(self):
-        data = json.dumps({"visual_message_return_type": "unseen", "persistentBadging": "True", "limit": "0"})
+        data = json.dumps(
+            {
+                "visual_message_return_type": "unseen",
+                "persistentBadging": "True",
+                "limit": "0",
+            }
+        )
         return self.send_request("direct_v2/inbox/", data)

     def get_presence(self):
         return self.send_request("direct_v2/get_presence/")

     def get_thread(self, thread_id, cursor_id=None):
-        data = json.dumps({"visual_message_return_type": "unseen", "seq_id": "40065", "limit":"10"})
+        data = json.dumps(
+            {"visual_message_return_type": "unseen", "seq_id": "40065", "limit": "10"}
+        )
         if cursor_id is not None:
             data["cursor"] = cursor_id
         return self.send_request(

TravisBuddy Request Identifier: 611b92f0-500f-11ea-99fd-116f3aa85035

Why did you close

Hey @kevinjulian,
Something went wrong with the build.
TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.
View build log
TravisBuddy Request Identifier: 482f4440-5167-11ea-8223-a57e93791187


Need to clear eofbit in the ifstream of the NativeFile before seekg

Hi, nice library. I'm using it to read a binary file and jumping back and forth using Seek.
For the NativeFile implementation, seekg() call was failing because the eofbit was set, so I added a call to m_Stream.clear() right before m_stream.seekg() and that worked.
Not sure if it's the best implementation but just a heads up.

Interesting, I'll investigate that. BTW, do you have this issue on windows platform?


Fixed dark text on dark background for access code

Makes the access code text white in dark mode

thanks for doing this! i knew about this, and it is pure negligence that i didn't fix it when i updated that game code component a few weeks ago. will get this in once i get a moment. hopefully soon.


MD5 calculation

Hi,
It's not clear to me if we can use milo to hash files on the disk.
Also, I would very much appreciate an MD5 hashing function.
Best,

Excellent 👌 what do you think about adding MD5 next to all the sha ?

Will consider it, meanwhile if speed is your concern note that on relatively new x86-64 cpus, sha-160 and sha-256 can be hardware accelerated and in this library they are.


Add support for pure JavaScript modules

This PR implements support for pure JavaScript modules and also upgrades Bower to a version without security vulnerability.

For pure JS files, I guess we should process the files with babel, or buildbot won't run on non ES6 browsers (e.g mobile :-/)


attention_bias_lower_triangle of _fast_decode seems to have no effect

Since attention_bias_lower_triangle has negative infinity in strictly upper triangle entries only, it has no contribution to bias in _fast_decode. Why is line 307-308 needed?
https://github.com/tensorflow/tensor2tensor/blob/103d0571ef48d82b61aae67cd61d716738f9fcfe/tensor2tensor/models/transformer.py#L307-L308
https://github.com/tensorflow/tensor2tensor/blob/103d0571ef48d82b61aae67cd61d716738f9fcfe/tensor2tensor/models/transformer.py#L319

I verified decoder_self_attention_bias is equal to 0 through a toy problem, but I haven't done anything more than that. Anyway, thanks for your feedback.


Document the version of LinkingLines sent for review with tag

Part of https://github.com/openjournals/joss-reviews/issues/6147
You have stated that version v.2.1.0 of LinkingLines is to be reviewed. You have created a GitHub release accordingly. However, there is no git tag representing this revision of the LinkingLines repository. I would suggest creating a git tag that represents the correct revision. If the latest commit on master represents the version to be reviewed, you can tag it with git tag and push the tag with git push --tags.

Thank you. added a 2.1.0 tag


Improve PDF ingestion performance

While reading in a larger database of PDF files I noticed that in between the GPU activity there were idle times when only one CPU-core was working @ 100%. The reason for this was pdftoppm from the pdf2image package. After some research I found the thread_count option for convert_from_path and ran some experiments.
This is the experiment code (in a Jupyter notebook):
import os
import tempfile
from pdf2image import convert_from_path

byaldi_path = <PATH_TO_PDFS>

for item in os.listdir(byaldi_path):
  with tempfile.TemporaryDirectory() as path:
    print(item)
    images = convert_from_path(byaldi_path + item, thread_count=1, output_folder=path)

My sample folder had PDFs with about 2800 pages. The conversion time with the default thread_count=1 was:
CPU times: user 1.84 s, sys: 4.63 s, total: 6.47 s
Wall time: 4min 58s

Using a thread_count of 4 this improved to:
CPU times: user 1.43 s, sys: 6.26 s, total: 7.69 s
Wall time: 2min 36s

And finally with the flexible thread_count that depends on os.cpu_count() the time went down to:
CPU times: user 1.33 s, sys: 6.33 s, total: 7.65 s
Wall time: 2min 11s

One thing to note: Under macOS the default ulimit is too low for larger PDF files open in parallel with TemporaryDirectory so macOS users should adjust it before reading in larger amounts of long PDFs using ulimit -n 10000 (for example). This StackOverflow question was very helpful.

PS: The tempfile solution is from the pdf2image documentation.read())-,OR%20better%20yet,-import%20tempfile%0A%0Awith). It seems to be way more gentle on the memory as well. In my trials it seemed to be necessary to supply a output_folder argument otherwise the thread_count argument would not have any effects.

I ran the indexing speed comparison an A100 with 12 cores now:
thread_count=1:
CPU times: user 631 ms, sys: 723 ms, total: 1.35 s
Wall time: 3min 41s

thread_count=4:
CPU times: user 212 ms, sys: 754 ms, total: 966 ms
Wall time: 58.3 s

thread_count=os.cpu_count()-1:
CPU times: user 185 ms, sys: 770 ms, total: 955 ms
Wall time: 37 s


Fix seek chunked messages

Motivation
This is the implementation of https://github.com/apache/pulsar/issues/12402.
Currently, when we send chunked messages, the producer returns the message-id of the last chunk. This can cause some problems. For example, when we use this message-id to seek, it will cause the consumer to consume from the position of the last chunk, and the consumer will mistakenly think that the previous chunks are lost and choose to skip the current message. If we use the inclusive seek, the consumer may skip the first message, which brings the wrong behavior.
Here is the simple code(in java) used to demonstrate the problem.
var msgId = producer.send(...); // eg. return 0:1:-1

var otherMsg = producer.send(...); // return 0:2:-1

consumer.seek(msgId); // inclusive seek

var receiveMsgId = consumer.receive().getMessageId(); // it may skip the
first message and return like 0:2:-1

Assert.assertEquals(msgId, receiveMsgId); // fail

For more context, please see PIP-107
And I find that f# client has already stored all chunk message ids in MessageIds.chunkMessageIds. We can use this field to implement the ChunkMessageId feature like in java.
There is still work left in this PR to serialize the ChunkMessageId. To be consistent with the behavior of the Java client, when we serialize and deserialize messageIDs or compare messageId, the comparison for chunkMessageIds only needs to compare the message id of the first chunk if the message is a chunked message. Like below:
match m.ChunkMessageIds, this.ChunkMessageIds with
| Some mchunkMessageIds, Some thisChunkMessageIds when mchunkMessageIds.Length > 0 && thisChunkMessageIds.Length > 0 ->
                        mchunkMessageIds.[0] = thisChunkMessageIds.[0] // We need to check the first chunk message id if the message is a chunkd message
| _, _ -> true

We need to update the pulsar proto file before proceeding with the rest of the work. What is the correct way to generate the code for the proto? I found that the code I generated using protoc is very different from the existing generated code. Are the parameters not set correctly?
Modification

Fix consumer inclusive seek for chunked message
Add compare for the first chunk message id in MessageId.

The code is generated using this site https://protogen.marcgravell.com/ , you'll also need to update generated modifiers from public to internal.


Packwiz

Mod name
Packwiz
Curseforge link

Modrinth link

Other link
https://github.com/comp500/packwiz
What it does
Makes MultiMC pack autoupdate, vanilla launcher support in the future
Why should it be in the modpack
Updates are good
Why shouldn't it be in the modpack
Setup may complicate things, especially when I update the pack
Categories

[ ] Performance optimization
[ ] Graphics optimization
[ ] New feature
[ ] Optifine parity
[x] Fixes a bug/dependency
[ ] Replaces an existing mod

Additional details

Going to wait until it gets the promised rewrite, seems a bit unstable for now.

Currently distributed as a GH-exclusive experiment.
Considered uploading to Curseforge as well, but that would require updates to stay on top and pack updates (unlike mod list updates) are rarely needed for this.


Log filename with [update] or [ignore] flags during --write process.

Output example with yarn format:all

Also I was experimenting with console.time / console.timeEnd loggers - but it made output too noisy.

Add custom duration calculation (excluding file read and write time)

Thanks, this is really cool. I just gave some feedback. I'm not really sure how it should look like but I think we can make it better :)

I'd like to get @jlongster approval as we are adding a new dependency.

Replaced it with custom func https://github.com/jlongster/prettier/pull/584/files#diff-970aecfd974e4b7ebfc40bf6329bb7b2R71 is it looks good?

We depend on babel-code-frame, which depends on chalk, so using chalk for the colors would not be a big deal, would it? That would also allow for a correct “supports color” check: https://github.com/chalk/chalk#chalksupportscolor

Replaced with chalk, I guess I will need to squash this PR at the end 🤧.

Please change it so it always prints the filename first before doing anything, and print to the raw buffer so it doesn't add a newline. Then you can add additional info afterwards using chalk.

This also needs a rebase :)

@jlongster ooh now we have --debug-check, done!

Awesome, thanks! Merging and I'll test it out locally.


HOTT-788 - Move country selector out of tabs

Jira link
HOTT-788
What?
I have added/removed/altered:

[x] Moved the country selector on the commodities page to outside of the tabs because we will soon have a third tab with a country selector on
[x] Replaced the translation texts for the fields with a single version for XI and single version for UK
[x] Dropped knowledge of the users tab from the country_selector_text
[x] Added javascript to assign the hidden 'anchor' field prior to submitting the 'select country' form - this wont work for the non-js case, but tabs don't work for the non-js case either
[x] Changed the search controller to sanitise the tab anchor it will pass through instead of white listing it - this was because it was redirecting from overview and footnotes tabs back to the export tab - the controller doesn't need to know which anchor its redirecting the user to, just needs to ensure its not an open redirect which sanitisation will achieve
[x] [Drive by fix] - the submit button on the country selector in the non-js scenario was not correctly formatted so added the govuk-button class to it

Why?
I am doing this because:

There is a rules of origin tab coming which will also require a country selector.

Have you? (optional)

[x] Reviewed view changes with stake holders
[x] Validated mobile responsive behaviour of view changes

Deployment risks (optional)

Non I'm aware of

You alright to add some screenshots @jebw?

@willfish :point_up: I've updated the description with some :+1:


Using undefined or DEFAULT authMechanism fails

Following the 3.8.22 update (possibly the bump of the mongodb driver), we started getting connection issues (see below).
I'm unsure if this is actually a Mongoose bug, or if it's from the MongoDB driver but figured it's best to report it here, since this is the module we're using directly.
It seems like the issues appear after in the following scenario:

connect :+1:
disconnect :+1:
connect :bug:

Interim(?) solution
Specifying an authMechanism in the connection options resolve the issue, even when using 3.8.22.
Possible issue
It seems like the issue appears around line 700 in /mongodb/lib/mongodb/db.js, where there's inconsistency in the if-statements. If the provided authMechanism is set to DEFAULT, it will cause an error.
Adding some logging shows that the authMechanism seems to be reused the next time Db.prototype.authenticate() is invoked, causing it to throw an error since it doesn't support an incoming value of DEFAULT.
Notes:

We're using a wrapping module to manage shared connections, but that hasn't changed for a long time. This module reuses existing connections to the same DB (across a top-level module and its submodules).
Stepping down to 3.8.21 resolved the problem

Error log
{
    "timestamp": "2015-01-26T21:02:49.149Z",
    "name": "",
    "hostname": "",
    "pid": 42219,
    "level": 40,
    "err": {
        "name": "Error",
        "message": "only GSSAPI, PLAIN, MONGODB-X509, SCRAM-SHA-1 or MONGODB-CR is supported by authMechanism",
        "stack": "Error: only GSSAPI, PLAIN, MONGODB-X509, SCRAM-SHA-1 or MONGODB-CR is supported by authMechanism\n    at Db.authenticate (./node_modules/mongoose-connection/node_modules/mongoose/node_modules/mongodb/lib/mongodb/db.js:690:23)\n    at NativeConnection.Connection.onOpen (./node_modules/mongoose-connection/node_modules/mongoose/lib/connection.js:458:13)\n    at ./node_modules/mongoose-connection/node_modules/mongoose/lib/connection.js:421:10\n    at ./node_modules/mongoose-connection/node_modules/mongoose/lib/drivers/node-mongodb-native/connection.js:217:5\n    at ./node_modules/mongoose-connection/node_modules/mongoose/node_modules/mongodb/lib/mongodb/db.js:294:11\n    at process._tickDomainCallback (node.js:486:13)"
    },
    "msg": "only GSSAPI, PLAIN, MONGODB-X509, SCRAM-SHA-1 or MONGODB-CR is supported by authMechanism",
    "v": 0
}

Opened a pull request for this in the driver https://github.com/mongodb/node-mongodb-native/pull/1246
Thanks for pointing this out!

This was fixed for 4.0.0-rc2. I'll see about backporting this to 3.8.x for next release.


Issue installing Atom on Ubuntu Mate on Pi3 - error: 'E: Unable to locate package atom'

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
[Description of the issue]
Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Expected behavior: [What you expect to happen]
Actual behavior: [What actually happens]
Reproduces how often: [What percentage of the time does it reproduce?]
Versions
You can get this information from copy and pasting the output of atom --version and apm --version from the command line. Also, please include the OS and what version of the OS you're running.
Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.

Thank you for contributing!
We don't support Atom on the Raspberry Pi. While we would love to support Atom on all possible platforms, our resources are finite so we have to draw a line somewhere. You can find out more information about Atom on ARM and links to other community efforts on https://github.com/atom/atom/issues/7822.
Additionally, we require the issue template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests. Please open a new issue and fill out the template for us.
Thanks for understanding and meeting us half way :grinning:

you can build an unofficial version of atom for a armv7 architecture (rpi) at hypersad/atom-armv7l repo


Finish effort to use complete python path

Someone changed '| python' to '| /usr/bin/python' somewhere and it broke some stuff.  This fixes the rest of the unchanged instances to match.

@johneiser Yep that was me. Thanks for catching this.


ODR failure due to missing inline for vectorization-related functions

Title says it all. If hnswlib is included in multiple source files, we observe linking errors like:
CMakeFiles/libtest.dir/src/find_nearest_neighbors.cpp.o: In function `cpuid(int*, int, int)':
/home/luna/Code/knncolle/build/_deps/hnswlib-src/./hnswlib/hnswlib.h:29: multiple definition of `cpuid(int*, int, int)'
CMakeFiles/libtest.dir/src/Hnsw.cpp.o:/home/luna/Code/knncolle/build/_deps/hnswlib-src/./hnswlib/hnswlib.h:29: first defined here
CMakeFiles/libtest.dir/src/find_nearest_neighbors.cpp.o: In function `xgetbv(unsigned int)':
/home/luna/Code/knncolle/build/_deps/hnswlib-src/./hnswlib/hnswlib.h:32: multiple definition of `xgetbv(unsigned int)'
CMakeFiles/libtest.dir/src/Hnsw.cpp.o:/home/luna/Code/knncolle/build/_deps/hnswlib-src/./hnswlib/hnswlib.h:32: first defined here
CMakeFiles/libtest.dir/src/find_nearest_neighbors.cpp.o: In function `AVXCapable()':
/home/luna/Code/knncolle/build/_deps/hnswlib-src/./hnswlib/hnswlib.h:54: multiple definition of `AVXCapable()'
CMakeFiles/libtest.dir/src/Hnsw.cpp.o:/home/luna/Code/knncolle/build/_deps/hnswlib-src/./hnswlib/hnswlib.h:54: first defined here
CMakeFiles/libtest.dir/src/find_nearest_neighbors.cpp.o: In function `AVX512Capable()':
/home/luna/Code/knncolle/build/_deps/hnswlib-src/./hnswlib/hnswlib.h:81: multiple definition of `AVX512Capable()'

etc.

I believe this should be easily fixed by adding an inline at the start of every function's definition, e.g.
inline void cpu_x86::cpuid(int32_t out[4], int32_t eax, int32_t ecx) {
    __cpuidex(out, eax, ecx);
}

This includes all the DISTFUNC-based functions in the space_*.h headers.

Hi @LTLA,
This has fixed in #383 , right? I guess we can make a release for that.

Oh, great. I only ever pull from your master in my builds, so I didn't see that. Would be great to get #383 in there.
Interesting that the PR uses static to resolve ODR issues, as opposed to inline. I'd speculate that inline would yield smaller binaries because static forces each translation unit to have its own local copy of the function. But I don't really know. Probably doesn't matter.

I see. Thanks for noting! Probably inline would be a better fit.


App from Baidu showcase

Hello friends,
Thank you for publishing your work to the community!
I see baidu showcase here https://github.com/baidu/mobile-deep-learning/blob/master/baidu_showcase.gif , but I cannot find link to this app. Where can I download this app to my ANDROID phone?
Thank you

Visit http://mo.baidu.com/, & enjoy it!


No Documentation for modeltype ModelStateDictionary created

In a api i return the WebApi ModelStateDictionary if validation errors occur.
The Method is annotated like this:
[SwaggerResponse(400, Type = typeof(ModelStateDictionary)
Now I can see taht 400 is generated as response but no model oder modelschema is shown  for this case in the documentation.
What am I doing wrong?

Any help?

Being a dictionary, that specific type is described in the outputted swagger json as follows:
schema: {
    type: "object",
    additionalProperties: {
        $ref: "#/definitions/System.Web.Http.ModelBinding.ModelState"
    }
}

While this is the correct way to describe dictionary / map types in Swagger, the swagger-ui does not appear to support documentation of schema's that use "additionalProperties". It has been reported through the following issue but you may want to add a +1 to give things a little push.
https://github.com/swagger-api/swagger-ui/pull/990
It's worth noting that you can wire up your own custom description for that type as follows but I'm not sure that really helps
c.MapType<ModelStateDictionary>(() => Schema { ... });


how can I get the 3D coordinate for each node？

Hi！Thank you for your awesome repo，which helps me a lot！
But I got a further question，I would like to know the 3D coordinate for each node，what should I do with the ’translation‘，’rotation‘ and ’scaling‘ ？
Maybe this question is beyond the repo itself，but the reference code on Internet is so poor，hope you could give me an answer or some clues
Thank you！

Are you asking about how to get the translation, rotation, and scaling of a node within an FBX file?
If so, please refer to the sample code below:
https://github.com/segurvita/fbx_sdk_python_sample/blob/master/show/show_attribute.py

Or, are you asking about how to get the world coordinates of a node?


[BUG]:Getting Cannot read properties of undefined (reading 'Symbol(drizzle:Columns)') after adding a new column

Report hasn't been filed before.

[X] I have verified that the bug I'm about to report hasn't been filed before.

What version of drizzle-orm are you using?
0.36.4
What version of drizzle-kit are you using?
0.28.1
Other packages
No response
Describe the Bug
After adding a new column to my table ti keep getting Cannot read properties of undefined (reading 'Symbol(drizzle:Columns)') i have tried dropping column recreating schema but not avail keep getting the error again and again . I am generating the schema using code by generate and migrate stratergy

Could you give me the schema (or at least the table that's causing the issue) before and after? Also, when do you get this error? In the ORM? In Kit? What command did you run?


Any update ?

Any update ?

Also checking for an update.  Apple now wants ANE's to have universal iOS libraries (for 64 bit) and this does not meet that requirement.  Is there another place this update may be?


AngleSharp removes first

I tried with the latest alpha as well as the stable release when I run the following program to simply let an IDocument take in HTML snippet, then output it through document.Body.InnerHtml. But the result is missing my style tag.
using AngleSharp;
using System;
using System.Threading.Tasks;

namespace ConsoleApp1
{
    public class Program
    {
        public static void Main()
        {
            MainAsync().GetAwaiter().GetResult();
        }

        private static async Task MainAsync()
        {
            string body = @"

this is a heading

some text
";

            var config = Configuration.Default;
            var context = BrowsingContext.New(config);
            var document = await context.OpenAsync(req => req.Content(body));

            Console.WriteLine(document.Body.InnerHtml);
        }
    }
}

The output of the above is, notice the first

I am not sure how you reach the conclusion that what you wrote as expected outcome is the right outcome.
I guess you need to read the HTML spec.
Long story short; before submitting a bug please check in your browser to have a reference. Its the same behavior as AngleSharp. All good.


Optional payload in ActionCreator?

Hello, thanks for the library!
I've got a question regarding async action creator. What if my action should receive no params?
export const FETCH_TEAMS = 'FETCH_TEAMS';
const fetchTeams = actionCreator.async<
	{}, // <- here, how can we specify to be optional?
	Array<Team>,
	AxiosError
>(FETCH_TEAMS);

// how i can handle it how
fetchTeams.started({});
fetchTeams.done({
  result: teams,
  params: {}
});

// how it would be nice to handle, but now i see errors in this case
fetchTeams.started();
fetchTeams.done({
  result: teams
});

Thanks in advance!

Unfortunately, I don't know of a way to make it possible. We added support for it here but had to revert it due to a way TS resolves overloaded signature, which broke async action creators with payload.
If you find a solution that works, please let me know.
Meanwhile, I recommend you to make a wrapper that wraps functions returning promises and dispatches async actions automatically. See typescript-fsa-redux-thunk, typescript-fsa-redux-saga.

Related discussion: https://github.com/Microsoft/TypeScript/issues/14400

Similarly, empty actions return undefined payloads:
import actionCreatorFactory from 'typescript-fsa';
const actionCreator = actionCreatorFactory();

const action = actionCreator('ACTION');
console.log(action())  // {type: 'ACTION', payload: undefined}

It's possible for us to fix both by adopting the following syntax:
const emptyAction = actionCreator.empty('ACTION');
console.log(emptyAction())  // {type: 'ACTION'}

type Success = string;
type Error = string;
const asyncAction = actionCreator.emptyAsync<Success, Error>('ACTION');
console.log(asyncAction.started())  // {type: 'ACTION_STARTED'}
console.log(asyncAction.done('success'))  // {type: 'ACTION_DONE', payload: {results: 'success'}}
console.log(asyncAction.done('failure'))  // {type: 'ACTION_FAILED', payload: {results: 'failure'}}

Benefits of doing it this way:

Empty actions will be a little cleaner.
Doesn't affect the existing API.
No need to do asyncAction.started({})
If https://github.com/Microsoft/TypeScript/issues/14400 ever gets released, it'll be easy to deprecate.

Cons:

Expands our supported API surface area

I would rather not expand the API because of TS shortcomings.
The undefined payload can be easily fixed at runtime, not the typing side.
I'm thinking about just making a payload parameter optional This would make it a bit less type-safe, but at least it would get easier to express things. For instance, the built-in typings for Promise do the same:
// in PromiseConstructor interface

new <T>(executor: (
  resolve: (value?: T | PromiseLike<T>) => void,
  reject: (reason?: any) => void
) => void): Promise<T>;

Fixed in 3.0.0-beta-1.

You can look how it's done in redux-handler. See .action() and .action<T>()

Thanks everyone 👍


Updating mbed-os to mbed-os-5.13

Description

updating mbed-os to mbed-os 5.13
for fix build error, due to missed some request macros like 'MBEDTLS_PSA_CRYPTO_C'
Pull request type

[x] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Breaking change

Hi, we already updated to the latest Mbed OS 5.13.x.
I'll close this pull request.


nix-ld: 1.2.1 -> 1.2.2

Diff: https://github.com/mic92/nix-ld/compare/1.2.1...1.2.2
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.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.

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

1 package built:

nix-ld

Don't forget to merge commits next time please.

Oh you squashed it, then it's perfectly fine. Sorry for the noise.


[stable/cockroachdb] Increase the default disk size to 100GB

In the past I had problems with Minikube not accepting large disk sizes,
but it no longer seems to be a problem on more recent versions, so let's
default to something a little more reasonable here.
Signed-off-by: Alex Robinson<EMAIL_ADDRESS>Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

ping @foxish @prydonius


uses auto serialization of form

Thanks to https://github.com/hopsoft/stimulus_reflex/issues/199 we can now use magic form parameters and simplify this expo example.
Interestingly you have to call params in your reflex, or the params will not be available to the Validationscontroller see https://github.com/hopsoft/stimulus_reflex_expo/compare/master...RolandStuder:form_using_params?expand=1#diff-1adfcc167ad3f17d87f671757d65bccbL5

This is great! Thanks.
Note that https://github.com/hopsoft/stimulus_reflex/pull/249 will address the need to explicitly invoke params.


Use proper scale, fixes scaling issues with data regions

#1061
#1357

Current coverage is 64.09% (diff: 100%)

Merging #1891 into master will not change coverage

@@             master      #1891   diff @@
==========================================
  Files             1          1
  Lines          4406       4406
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           2824       2824
  Misses         1582       1582
  Partials          0          0

Powered by Codecov. Last update 955fdd6...069ed2d

Tried in the context of my chart and it works perfectly.
Hopefully we can get your fix merged soon.
Cheers for looking into this!


IPv6 Support

[ ] Test plan
[ ] Test and verify
[ ] Automation

This still a yet to be finalize plan for IPv6 support


[CARBONDATA-2432][Build] Add bloomfilter datamap to carbondata assembly jar

Currently after build, the generated carbondata assembly jar does not contain bloomfilter datamap. This PR fix this.
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[x] Any interfaces changed?
NA

[x] Any backward compatibility impacted?
NA

[x] Document update required?
NA

[x] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
NA
- How it is tested? Please attach test report.
NA
- Is it a performance related change? Please attach the performance test report.
NA
- Any additional information to help reviewers in testing this change.
NA

[x] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.
NA

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4457/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/4710/

LGTM


25-test_req.t broke in master on NonStop with explicit start/end dates

This looks like a new regression post-3.3. Looking for help resolving it.
25-test_req.t ........................... 101/?
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
C field []:AU
SP field []:
L field []:Brisbane
O field []:CryptSoft Pty Ltd
OU field []:.
CN field []:Eric Young
email field<EMAIL_ADDRESS>../../util/wrap.pl ../../apps/openssl req -x509 -new -text -config ../../test/test.cnf -key ../../test/testrsa.pem -not_before today -not_after today -out self-signed_explicit_date.pem => 0
not ok 109 - explicit start and end dates
# ------------------------------------------------------------------------------
#   Failed test 'explicit start and end dates'
#   at test/recipes/25-test_req.t line 614.
25-test_req.t ........................... Dubious, test returned 1 (wstat 256, 0x100)

can you bisect to see when this was introduced?

I've just merged a fix to the explicit start/end date tests by Viktor. Can you please try fresh master branch?

Fixed at 4e3c1e6206


sharing technical details

Hello, thank you for providing such great work! I would like to know if you have any plans to share technical details or have corresponding research papers available? For example, details on data cleaning and pre-processing, training equipment, and training time.

Hi, thanks for your interest in our work! Details will be released later. Please stay tuned.


Link root workspace to compact tree by default

The compact tree view only works for more recent experiments. Andreas and I were talking about coming up with a versioning system to help here.

For now, as a workaround, it might make sense to check the createdAt for the root workspace, and then use that to determine whether to link to the old tree view or the new compact tree view.

what would the cutoff date be? the introduction of the compact subtree, or does it work on earlier experiments than that?

OK cutoff date is 2019-04-08 20:52:17.841+00. But even among trees created on or after this date, we need to know whether they're oracle trees or not. Currently, because we lack a taxonomy for trees and/or experiments, we can only use something like duck typing here. I would probably see if the root workspace is eligible for a malicious oracle.
So, to sum up, if a tree was created after the cutoff date, and has a root workspace that's eligible for a malicious oracle, then associate it with the compact tree view, otherwise associate with the old tree view.
And we should probably note somewhere that this needs to be cleaned up after a good workspace classification scheme is introduced.

Buttons get smashed if the window's width is reduced.

Actually, I would just remove the button that navigates to the workspace.

And probably also remove the "Tree" nav button too, just keeping the text link. We can run this change by @stuhlmueller before merging.

UI looks good.


Single spa react not loading in IE11

Getting some error in IE when I try loading the single spa app.
Unable to locate the error. as its not even breaking at the lifecycle methods.
added promise polyfill. Then promise error was removed. But then also not loading in IE11
Pls help getting the single spa loading in IE. Its a react application

Here's a code sandbox that shows single-spa-react working in IE11.
https://codesandbox.io/s/prod-framework-ror7c?file=/index.html
You need to polyfill both Promise and fetch for SystemJS, single-spa, and single-spa-react to work. If you're still seeing errors after that, then it's likely a problem with your code or one of the other dependencies.

In this example, there is no importing of another application to this. Can you show an example of importing a react application to this application? Both react and that works in IE11?

No I can't create examples on demand for you. As the person reporting the issue, it's your job to prove that there's a problem. So could you please provide a demonstration of the issue?

It was because of some local security setting in internet explorer. It was working fine in prod environment.
Following the below steps helped it to work find in IE 11 local.
https://social.technet.microsoft.com/Forums/en-US/04f9da4a-fdf2-4cae-aaec-9f74335ff27c/how-to-get-ride-of-this-error-on-ie-11-browser-securityerror-failed-to-connect-to-websocket?forum=ieitprocurrentver

However the demo apps given in the documentation are not working in IE. For the users reference, it would be helpful if those examples are working in IE11 as well.
@joeldenning you need not create a new demo application and I didn't demand for it.


Fix check-dependencies to use dep check

What this PR does / why we need it:
check-dependencies should fail when vendor is directly updated without updating Gopkg.toml.  To have that, we should be using dep check instead of dep status.
Ref:

https://golang.github.io/dep/docs/daily-dep.html#key-takeaways
https://golang.github.io/dep/docs/ensure-mechanics.html#staying-in-sync

Related https://github.com/kubermatic/kubermatic/pull/3422
NONE

/assign @alvaroaleman

/lgmt
/approve

/lgtm

/retest

/retest

/retest

/retest

/retest
On Tue, May 7, 2019 at 5:50 PM kubermatic-bot<EMAIL_ADDRESS>wrote:

@nikhita https://github.com/nikhita: The following test failed, say
/retest to rerun them all:
Test name Commit Details Rerun command
pull-machine-controller-e2e-digitalocean 6f0cc0b
https://github.com/kubermatic/machine-controller/commit/6f0cc0b6b84370b7aa11574315d02f50c2bcda56
link
https://prow.loodse.com/build/prow-data/pr-logs/pull/kubermatic_machine-controller/524/pull-machine-controller-e2e-digitalocean/1125732639949459457 /test
pull-machine-controller-e2e-digitalocean
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubermatic/machine-controller/pull/524#issuecomment-490056091,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD24BUBSALKTIZEH6ZEDVZLPUFXZBANCNFSM4HLFKOMQ
.

/retest


Add alpha channel support

Checklist

[x] Code is up-to-date with the master branch.
[x] yarn test (npm run test) passes with this change.
[x] The new commits follow conventions explained in CONTRIBUTING.md

Description of Change
I took a crack at adding alpha support. The only public interface changes are the addition of an optional boolean alpha prop to display the alpha slider and toggle parsing of alpha values from the text inputs, as well as an extension of the color constructors to accept 4/8-digit hex strings, an additional a property on rgb/hsv colors, and four-value arrays.
There should be no breaking changes unless a user was already passing in 4/8-digit hex strings, four-value arrays, or objects with a alpha channels, in which case those will now be round-tripped appropriately instead of truncated. Since that behavior would technically be a violation of the previous interface I think it's up to you how you want to handle that.
The utils are updated to handle the alpha channel if present/not undefined. There's a new alpha slider component below the hue slider that's only visible if the alpha prop is passed in. And the text inputs will correctly parse and display alpha values if they are provided. If no alpha value is set, the components return the colors without an alpha value.
Absolutely willing to go back and forth on this if it's not up to snuff for the project! I'd been looking for a TypeScript-based color picker for a while and couldn't find one quite as clean as yours.

I'd be concerned that existing users using regular non-alpha colors might be accidentally impacted by the picker suddenly returning alpha values; for example if ColorRGB.a defaults to 255 then gets converted into a hex string before returning to the end user it would be an eight-digit hex string ending in ff instead of the six-digit hex string it is now. This way the 4-channel results are only introduced if the alpha prop is present and/or the a property is present. The alternative would be to introduce a breaking change where alpha values and eight-digit hex strings are always returned even if the alpha prop isn't present, which seems very risky to me.

Great feedback! I'll implement those changes and update the PR. Making the range 0-1 for alpha makes sense; I'll need to add a bit of extra work in parsing the RGB/HSV text fields since they currently only accept integer values. Something to look out for after the PR is updated.

Updated to resolve the feedback, except for things I was unsure about. I tried to reduce some duplicated code as well.

Updated! Should address those bits of feedback.


discussion: graceful scale-in the cluster

In Scale Service and Low-level Scaling Interface on Meta Service, we've defined the expected behavior of scaling-in a compute node from a cluster:

Inform the meta service to not schedule new streaming jobs in the compute node.
Repeatedly migrate or scale-in the actors from this compute node to the remaining ones.
Kill the compute node manually or by the external operator.

@ALeitert previously found that scaling in the cluster did not work fluently in Scaling Behaviour, since most of the functionalities mentioned above are not implemented yet. For each step, we may pick up some of the lacks here and describe the solution here:

Inform the meta service to not schedule new streaming jobs in the compute node.

We need a special status of REMOVE_SOON and tell the scheduler to ignore the compute nodes with this status. An RPC interface is required and an extra UI operation in the dashboard might be necessary for on-premises deployment.

Repeatedly migrate or scale-in the actors from this compute node to the remaining ones.

This can be achieved by RescheduleFragment RPC in the scale service, and risectl reschedule in CLI, but it requires the full knowledge of the parallel unit mechanism of RisingWave. To make it easy to use, a dashboard operation may also be necessary.

Kill the compute node manually or by the external operator.

We should handle signals like SIGINT and SIGTERM for compute nodes, for checking the status of the compute node and unregistering self to the meta service. In this way, we don't need to rely on the heartbeat timeout to exit and are able to make everything more seamless. (See also the recommendations of Flink's Elastic Scaling)

Hey @BugenZhao, Is there an update regarding this task? 😄

According to the new-proposed design of the high-level scaling interface, gracefully scale-in the cluster will consist of two procedures: cordon and delete-worker.


Take Ownership of Homebrew package

https://formulae.brew.sh/formula/jabba

see https://github.com/Homebrew/homebrew-core/pull/119263

This would require a formal statement from the original owner/project, or sufficient time and reputation to build up.
https://github.com/Homebrew/homebrew-core/pull/119263#discussion_r1058403931

Thanks @nicerloop for starting this, I'll see if I can get a response on the original repo owner to confirm the new project.

Done: of https://github.com/Homebrew/homebrew-core/pull/119263


Adding Fixed Advisory GHSA-4v7x-pqxf-cx7m for sig-storage-local-stati…

…c-provisioner

$ wolfictl scan -r sig-storage-local-static-provisioner
📡 Finding remote packages
🔎 Scanning "/var/folders/kl/q9mydw095ln5s7wj971qcrx40000gn/T/x86_64-sig-storage-local-static-provisioner-2.7.0-r1-4171202138.apk"
✅ No vulnerabilities found
🔎 Scanning "/var/folders/kl/q9mydw095ln5s7wj971qcrx40000gn/T/aarch64-sig-storage-local-static-provisioner-2.7.0-r1-2106674389.apk"
✅ No vulnerabilities found


Freezing in video

When we start a stream, it is freezing the video. This happens in some devices when the resolution is equal or greater than 1280x720.
rtmpCamera1.prepareVideo(720, 1280, 30, 1500x1024, false, 180)
I tried changing the bitrate and the problem continues

What view are you using, SurfaceView, TextureView or OpenglView?
Can you tell me device models and Android API version?
Did you try with camera2 or use other view?

now OpenglView, but I tested SurfaceView it and the problem occurred.
Model Device: Moto G4 Plus Android 7.0.

Only freeze with SurfaceView?
Can you show me logcat?

I did changes to camera1 buffer to buffer mode. This affect to rtmpCamera1 and rtspCamera1 stream if you use surfaceview or textureview.
Please get last commit and let me know if the problem is solved. If not send me a logcat

I will go test and return with feedback

it is still happeing in moto g4 plus 7.0

@rkoshti What configuration are you using? show me your prepareVideo, prepareAudio and view used.

still happening for me on Pixel 2:
videoRTMP.prepareVideo(1280, 720, 30, 2000 * 1024, false, 90);
videoRTMP.prepareAudio(96 * 1024, 44100, true, false, false);

bitrate is in the range of (2000...4000) * 1024 and Im using a SurfaceView

I can't reproduce your case with my devices. First of all I need know:
When you call startStream, the app is frozen or only preview?
Try the following things:

Use openglview instead of surfaceview.
Record video instead of start stream to discard encoder initialize freeze.
Write a log per line in startStream method to know the line that freeze you app and report me the line that cause your app freeze to try fix it.


chore(wsl): use Windows native way to yank and paste.

#731

I will review this a bit later the night, sorry about the inconvenience.

I will review this a bit later the night, sorry about the inconvenience.

No problem and no hurry :)

tested. Seems working fine.


automatically-updating-install-job

--> Automatically updates install job when the generation of the cd does not match the cd generation in job's annotations.

/ok-to-test

Needs a rebase on master and to remove the WIP designation.

/lgtm

/retest

/retest


kube-apiserver incomplete SAN for earlier provisioned Control Plane nodes

What kind of request is this (question/bug/enhancement/feature request):
Bug.
Steps to reproduce (least amount of steps as possible):
Provision a Custom cluster
Add at least two Control Plane nodes
Result:
The first Control Plane node will have an incomplete SSL certificate for kube-apiserver: it will contain only its IP address/DNS record in its SAN, yet it will be balanced with the other kube-apiserver, leading to sporadic SSL errors.
Other details that may be helpful:
This can be confirmed by running openssl x509 -text -noout -in /etc/kubernetes/ssl/kube-apiserver.pem | grep DNS on the first Control Plane node. This certificate should be the same as on the last provisioned Control Plane node, yet it isn't.
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.1.8
Installation option (single install/HA): single install

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Custom
Machine type (cloud/VM/metal) and specifications (CPU/memory): VM (8 CPU, 16 GB RAM)
Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"clean", BuildDate:"2019-03-26T00:04:52Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.5", GitCommit:"2166946f41b36dea2c4626f90a77706f426cdea2", GitTreeState:"clean", BuildDate:"2019-03-25T15:19:22Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

Client:
 Version:           18.09.4
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        d14af54
 Built:             Wed Mar 27 18:34:51 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.4
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.8
  Git commit:       d14af54
  Built:            Wed Mar 27 18:01:48 2019
  OS/Arch:          linux/amd64
  Experimental:     false

Duplicate of https://github.com/rancher/rancher/issues/16151


usize doesn't get colored like u64 does

Since it's numeric, it should get colored blue

fixed now


Feature Request: Implement a maxLength property on sap.m.ComboBox

OpenUI5 version: All
Browser/version (+device/version): All
Feature Request: Implement a maxLength property on sap.m.ComboBox. As ComboBox can handle manual input, it makes sense that there should be an optional limit on the length.
(In #1134 it was requested to move "maxLength" to "InputBase" but this was rejected. However, in the comments it was discussed that this would make sense for ComboBox, as the only child of InputBase for which this really makes sense - see https://github.com/SAP/openui5/issues/1134#issuecomment-1078866799).

Hello @mydoghasfleas ,
Thank you for sharing this finding. I've created an internal incident<PHONE_NUMBER>. The status of the issue will be updated here in GitHub.

The case will be evaluated by SAPUI5 developers, but clarify the usage of the maxLegth property in your case, as https://github.com/SAP/openui5/issues/1134#issuecomment-1078866799 specifies that the feature is not needed as it can be implemented with the public API (events and methods fired while typing in the sap.m.ComboBox)

The case will be evaluated by SAPUI5 developers, but clarify the usage of the maxLegth property in your case, as #1134 (comment) specifies that the feature is not needed as it can be implemented with the public API (events and methods fired while typing in the sap.m.ComboBox)

I think that needs to be clarified: using events to achieve this would be a workaround, but it is not an elegant solution.
The need for such a feature should be pretty self-explanatory: As a ComboBox can be used to enter additional values, it stands to reason that one may want to limit the length of that input as with the Input control.
Consider the fact that the list of values may have a limit, but this is controlled by the developer. But the developer has no control over what the user inputs if they decide to enter an auxiliary value.

Hi @mydoghasfleas ,
After discussion with our architects and UX colleagues, we will have to reject this requirement. Having such input length limitation will interfere with other features that the control provides and we do not see it as part of the implementation of the sap.m.ComboBox control.
Best Regards,
Hristo


edit_datasets

Hello, from your edit_dataset file, it can be seen that the example_pair and image_query you constructed belong to the same prompt. Could this lead to their content being overly similar, potentially causing some unintended effects on the training results?

Hello, I also tried the version of sampling two compelte seeds (prompts) each time, one for examples and one for query-ouput pair. Both the two versions work. With more data and tasks, I think different prompts would help more.


Modified some code and comments

Modified some comments to be a bit more clear. Removed some unnecessary code, such as setting the encoding to utf8 (which is done by default since Python3.1.5 see PEP 686)
I've also taken the formatting changes done by #47 and applied them here.

Slightly modified the README

Looks good to me


Fix mount command

What changes are proposed in this pull request?
Followup to https://github.com/Alluxio/alluxio/pull/17606
Ensures the MountCommand uses BaseFileSystem as its client.
Why are the changes needed?
FileSystem.Factory.create(FileSystemContext, FileSystemOptions) can never return BaseFileSystem. This is because FileSystemOptions can only be created through FileSystemOptions.Builder.fromConf(AlluxioConfiguration) which always sets the ufsFileSystemOptions. FileSystemOptions.Builder.setUfsFileSystemOptions does not accept null. Therefore, FileSystemOptions.mUfsFileSystemOptions is never Optional.empty(). This means that these lines never return BaseFileSystem.
The previous assert (mFileSystem instanceof BaseFileSystem); statement only works if java -ea is used when running the FileSystemShell. Since -ea is not a standard option, the assert was always avoided, but upon inspection (and turning on the -ea option) it fails systematically.
This PR ensures that MountCommand always uses BaseFileSystem like it is supposed to.
Does this PR introduce any user facing changes?
No.

failed to push directly to the upstream branch so create a duplicate PR #17697. Rushing for the release cut


Two Pointers: Check whether a given string is a Valid Palindrome in C++

I have recently created a pull request for this issue.

I have recently created a pull request for this issue.

Thanks, good work

I have recently created a pull request for this issue.

You can help with other issues as well :)


ad-3.template now requires KeyPairName

Deploying this quickstart started failing last week due to submodules being updated.
The following resource(s) failed to create: [ADStack]. . Rollback requested by user.
2020-03-09 01:07:05 UTC-0600	ADStack	CREATE_FAILED	Parameters: [KeyPairName] must have values
2020-03-09 01:07:04 UTC-0600	ADStack	CREATE_IN_PROGRESS	-

This is the commit that broke things:
Submodule quickstart-microsoft-activedirectory updated from f1b70b to d69ddf
Over on the quickstart-microsoft-activedirectory project, they added the KeyPairName parameter to the AD-3 template in that range.

This has been done


Logging in reconciler-test is clumsy

The logging in this library is all over the place. The following packages are used to log messages:

testing
zap
fmt
log
k8s.io/klog

As this library is test focused, it would be a good idea to feed all logs to testing package. The testing package loggers automatically works when doing a parallel testing, so the messages will end up in appropriate test report. Also, testing loggers print messages only in case of failure, or if -v test flag is used.
I think the best solution would be to set up zaptest.NewLogger, so that it will feed all messages to appropriate testing.T object, and allow using fast, leveled, and structured logging across codebase.
/kind cleanup

/assign

/reopen
/remove-lifecycle stale


Intel16 Upstreaming

Merges commits in master as of 9/28/23 into the intel16 branch
Request to merge these back into master

@soneryaldiz - couple questions -

Are there any (known) changes that would/ should break compatibility with the PDK package?
Do you guys have some internal edition that renders this irrelevant?
Overall - do ya want intel16 merged?

Marking as a draft; this needs a massage just to compile, at least for me.
And pending the questions about whether the project wants it.

@dan-fritchman , I am fine with merging intel16 to master.
Do you mean internal edition of ALIGN-Public? No, we use the public repository as well.

Great thanks.
And I suppose my question really breaks in two, regarding

(a) ALIGN itself - which you've answered. And
(b) The PDK package - which is perhaps better reserved for a different forum.

OK after testing in my own setup, this looks ready to merge.

It seems the CircleCI tests fail because it's a fork, and they attempt to clone the source from this repo.
Let me know what if anything you wanna do there.


Add PEASS

I added PEASS (Privilege Escalation Awesome Scripts SUITE) which provides privilege escalation tools for Windows and Linux/Unix and MacOS.
It is getting pretty well know in the Cybersecurity community, and it is really handy so I guess it earned its place here.

I have no idea what your talking about . I have no idea what was evening happening at the time
Sent from my iPhone

On Jun 29, 2021, at 6:42 AM, Pablo Lecolinet @.***> wrote:

I added PEASS (Privilege Escalation Awesome Scripts SUITE) which provides privilege escalation tools for Windows and Linux/Unix and MacOS.
It is getting pretty well know in the Cybersecurity community, and it is really handy so I guess it earned its place here.
You can view, comment on, or merge this pull request online at:
https://github.com/trimstray/the-book-of-secret-knowledge/pull/217
Commit Summary
Add PEASS
File Changes
M README.md (1)
Patch Links:
https://github.com/trimstray/the-book-of-secret-knowledge/pull/217.patch
https://github.com/trimstray/the-book-of-secret-knowledge/pull/217.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


feature request: make Workbook::new accept &Path

Feature Request
Workbook::new should accept &Path or PathBuf instead of &str.

Good suggestion. I'll look into it.

I thought about this for a while and I'd prefer to keep new() as constructor from simple strings since that will work for most people, most of the time, and it simplifies the documentation.
On the other hand Path is better for the times when a simple string path doesn't work and in particular for folks on Windows who can encounter different hurdles with back/forward slashes and network paths.
So as a compromise I've added a new_from_path() constructor. I've pushed this to main and it works as follows:
use rust_xlsxwriter::{Workbook, XlsxError};

fn main() -> Result<(), XlsxError> {
    let path = std::path::Path::new("workbook.xlsx");
    let mut workbook = Workbook::new_from_path(&path);

    _ = workbook.add_worksheet();

    workbook.close()?;

    Ok(())
}

Try it out and let me know what you think.
I'm also going to try to add a new_from_file() constructor for File type instances. However, that is trickier from a lifetime/ownership point of view.

This feature is now in rust_xlsxwriter  version 0.8.0: https://rustxlsxwriter.github.io/changelog.html
Thanks for the suggestion. Closing.


Check if jaxb version 2.3.1 can be replaced by jakarta.xml.bind-api

In the mvnrepository, it is indicated that the jaxb-api is succeeded by the Jakarta XML Binding API. We have to see if this works in the ots-parser-xml project and what the side effects are.
The jaxb-api is not updated since 2018, where the Jakarta XML Binding API has regular releases; the latest being from March 2024.

The jaxb-api also still uses javax.annotation-api that has been replaced by jakarta.annotation-api. Therefore, the POM file n ots-parser-xml has a dependency:
    <dependency>
      <groupId>javax.annotation</groupId>
      <artifactId>javax.annotation-api</artifactId>
      <version>1.3.2</version>
    </dependency>

whereas jakarta.annotation-api version 3.0.0 (a much later version) is already included in the entire OTS project.

A first check shows that updating JAXB is not straightforward. We might have to do some smaller tests first to see how to integrate JAXB itself, the maven-jaxb2 plugins, the org.glassfish.jaxb/jaxb-runtime library, and the org.jvnet.jaxb2.maven2/maven-jaxb2-plugin that are now all interacting in a way that defies partial upgrades of one of the tools.

The project ots-opendrive uses the latest definitions, plugins and libraries for JAXB. This can be ported to ots-xml.

Next step will be to get the actual parsing done with the latest library, to make, e.g., the parsing of an XML file work again using the newly generated classed from the XSD-file. What the code needs is an "Implementation of Jakarta XML Binding-API", e.g., the glassfish one -- we have to see if that is indeed the best option.

Next step will be to get the actual parsing done with the latest library, to make, e.g., the parsing of an XML file work again using the newly generated classed from the XSD-file. What the code needs is an "Implementation of Jakarta XML Binding-API", e.g., the glassfish one -- we have to see if that is indeed the best option.

Indeed the glassfish parser added again, but now the latest version 4.0.5:
      <dependency>
        <groupId>org.glassfish.jaxb</groupId>
        <artifactId>jaxb-runtime</artifactId>
        <version>${jaxb.version}</version>
      </dependency>

Demos are running; unit tests of ots-xml work. Al JAXB parsing has been updated to the latest version.


Rewrite make_function_panel to not touch function internals

Minor fix to avoid reading function internals – should make it a bit easier to merge #225

tested this locally with a complex app and the output looks identical :)


Update BR release version and admin container

Issue #, if available:
Description of changes:

Adding BR 1.25.

Updating release version based on https://github.com/bottlerocket-os/bottlerocket/releases/tag/v1.12.0

Updating host containers based on https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/models/shared-defaults/public-host-containers.toml

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/cherrypick release-0.14


PathSchemeSelectionTests broken

PathSchemeSelectionTests, DynamicSchemeTests, and IdentityExternalClaimsTests are all failing with errors like
http://aspnetci/viewLog.html?buildId=454232&tab=buildResultsDiv&buildTypeId=XPlat_Linux_UbuntuUniverseCoreCLR
[00:00:06] :	 [Step 3/4]   AuthSamples           |   System.InvalidOperationException: Cannot find reference assembly 'System.ComponentModel.Composition.dll' file for package System.ComponentModel.Composition
[00:00:06] :	 [Step 3/4]   AuthSamples           |      at Microsoft.Extensions.DependencyModel.Resolution.ReferenceAssemblyPathResolver.TryResolveAssemblyPaths(CompilationLibrary library, List`1 assemblies)
[00:00:06] :	 [Step 3/4]   AuthSamples           |      at Microsoft.Extensions.DependencyModel.Resolution.CompositeCompilationAssemblyResolver.TryResolveAssemblyPaths(CompilationLibrary library, List`1 assemblies)
[00:00:06] :	 [Step 3/4]   AuthSamples           |      at Microsoft.Extensions.DependencyModel.CompilationLibrary.ResolveReferencePaths(ICompilationAssemblyResolver resolver, List`1 assemblies)
[00:00:06] :	 [Step 3/4]   AuthSamples           |      at System.Linq.Enumerable.SelectManySingleSelectorIterator`2.MoveNext()
[00:00:06] :	 [Step 3/4]   AuthSamples           |      at Microsoft.AspNetCore.Mvc.Razor.Compilation.MetadataReferenceFeatureProvider.PopulateFeature(IEnumerable`1 parts, MetadataReferenceFeature feature)
[00:00:06] :	 [Step 3/4]   AuthSamples           |      at Microsoft.AspNetCore.Mvc.ApplicationParts.ApplicationPartManager.PopulateFeature[TFeature](TFeature feature)
[00:00:06] :	 [Step 3/4]   AuthSamples           |      at Microsoft.AspNetCore.Mvc.Razor.Internal.DefaultRazorReferenceManager.GetCompilationReferences()
[00:00:06] :	 [Step 3/4]   AuthSamples           |      at System.Threading.LazyInitializer.EnsureInitializedCore[T](T& target, Boolean& initialized, Object& syncLock, Func`1 valueFactory)
[00:00:06] :	 [Step 3/4]   AuthSamples           |      at Microsoft.CodeAnalysis.Razor.CompilationTagHelperFeature.GetDescriptors()
[00:00:06] :	 [Step 3/4]   AuthSamples           |      at Microsoft.AspNetCore.Razor.Language.DefaultRazorTagHelperBinderPhase.ExecuteCore(RazorCodeDocument codeDocument)
[00:00:06] :	 [Step 3/4]   AuthSamples           |      at Microsoft.AspNetCore.Razor.Language.DefaultRazorEngine.Process(RazorCodeDocument document)
[00:00:06] :	 [Step 3/4]   AuthSamples           |      at Microsoft.AspNetCore.Razor.Language.RazorProjectEngine.Process(RazorProjectItem projectItem)
[00:00:06] :	 [Step 3/4]   AuthSamples           |      at Microsoft.AspNetCore.Mvc.Razor.Internal.RazorViewCompiler.CompileAndEmit(String relativePath)
[00:00:06] :	 [Step 3/4]   AuthSamples           |      at Microsoft.AspNetCore.Mvc.Razor.Internal.RazorViewCompiler.OnCacheMiss(String normalizedPath)

@javiercn can you take a look?
cc @ryanbrandenburg

What was the resolution here?

https://github.com/aspnet/AuthSamples/pull/39


Any efficient solution for serializing RoaringBitmap Arrays with Kryo?

Any efficient solution for serializing RoaringBitmap Arrays with Kryo?

Kryo usage is documented in the README.md file.
Reopen if the README does not answer your question.


Cannot use this library with vite

I just did npm install ... and then vite started complaining with
[w:]   ✘ [ERROR] Failed to resolve entry for package "tanstack-table-export-to-csv". The package may have incorrect main/module/exports specified in its package.json. [plugin vite:dep-scan]
[w:]
[w:]     node_modules/esbuild/lib/main.js:1374:21:
[w:]       1374 │         let result = await callback({
[w:]            ╵                      ^
[w:]

Fixing package.json to indicate the "main" is "index.js" instead of "index.ts" (which doesn't exist) seems to fix the issue.
regards
Emmanuel

@briot
Fixed
Try again

Thanks.  I did experiment before I created this issue by modifying the file directly in node_modules/, so it works indeed.

Thank you too!


Fix responsive header by defining view port scale

@pavitrabhalla worked with Damien to address (what we believe to be) the final responsiveness issues.
Changes

Added 1 line to each page to specify the scale for the viewport (so that our min/max screen size settings would have an impact when viewing on mobile devices)
Made a couple tiny content changes to fix display of bottom nav buttons

Test Plan

Tested this on the latest Chrome for Mac + discovered the mobile device simulator to make sure everything works nicely on Chrome for iOS (which it does look nice)
Tested this in mobile Safari in the iOS Simulator and it looks nice

:+1:


Can't set two paths to the same file

I'm passing a config that looks like this
...
'paths': {
...
'eaf.util': 'my/eaf/core',
'eaf.core':'my/eaf/core'
...
}
core.js defines both 'eaf.util' and 'eaf.core' by name.
I also have a module that is like this:
define('domain.base', [..., 'eaf.util', 'eaf.core'...], function (...
Trying to load this last module with curl results in "Promise already completed."  To get around this, I replaced the throw with a return.  Not sure of all the dangers, but I'm just trying to get curl working and am purty frustrated at this point, I have to say.  fyi, I'm trying to migrate from http://jsclass.jcoglan.com/ loader pattern, which is why it seems paths are the shortest path to success.

Hey Toby,
Sorry about the frustration.
What version of curl.js are you using.  I assume it's 0.5.4?  Also, there should be another error in addition to the "Promise already completed" error.  If you're using Chrome dev tools or Firebug, check the Network/Net tabs to see if curl.js tried to fetch a file at the wrong location.
In the meantime, I'll set up a test case to see if your hypothesis is correct: curl can't handle when two module ids that map to the same url are listed in a single dependency list.
-- John

Hey Toby,
I created the following gist to try to reproduce the issue.  This super simple test case succeeds.  Do you see anything with that test case that can be modified to better mimic your project?  https://gist.github.com/1695074
Here are some potential gotchas I see from your code snippets.  I can't tell from your snippets whether they apply or not, but I thought I'd list them anyways:
a) it looks like you are not using packages, either explicit or implicit.  The module id, "eaf.util", looks like it could mean module "util" in package "eaf".   "eaf.util" on the other hand is just a top-level module to AMD.
This is fine under simple projects.  However, if you start using relative paths within your modules, curl.js won't know what to do.  Relative paths need a parent folder or package name to work correctly.  If you are not using relative paths in your modules, then this is not the problem.
curl.js doesn't currently throw an exception when it hits this situation.  We need to fix this.
b) You are naming your modules (e.g. the 'domain.base' id above).  This is only recommended for special circumstances: it limits how you can structure your folders and where you can locate your modules.  curl.js throws an exception if the id of a module doesn't match the location it was fetched from.
Unfortunately, it's way too easy to mix the concepts of urls and module ids in your paths.  For instance, if curl tried to load a module located at "js/my/core" and the core module declares its name as just "my/core", then curl.js will assume it got the wrong module and throw an exception.
The way to fix this is to either set the baseUrl to "js" or to create a path to map "my" to "js/my" (or map "my/core" to"js/my/core" if that's the only module you want mapped).  curl.js will look at the map and know that you've specified a special location for that folder (or module).
Better yet: don't name your modules at all.  It's a lot easier if you don't.
I hope this message helps!
-- John

Thanks for the attention to this issue.
Yes, I'm using version 0.5.4 of curl, and version 11 of chrome browser.
The network tab shows all success.  I'm assuming you're thinking there would be a 404 or something.  No such "luck," I guess.  Here is the stack behind the error:
Uncaught Error: Promise already completed.

            resolve.rejectcurl.js:237

            resolvecurl.js:253

            loadScript.argscurl.js:427

            fetchDep.then.completedcurl.js:620

            completecurl.js:243

            resolvecurl.js:224

            resolvecurl.js:253

            loadScript.argscurl.js:427

            fetchDep.then.completedcurl.js:620

           completecurl.js:243

           resolvecurl.js:224

           resolvecurl.js:253

           completecurl.js:243

           resolvecurl.js:224

           resolvecurl.js:253

           define.load.orderjs.js:112

           processjs.js:50

I'm using a mix of AMD and non-AMD modules, as you can see by the reference to js.js.  I may not have the problem statement correct (i.e. this issue may be a non-issue).  Certainly, your gist seems to indicate this.  I tried to complicate your gist to be a bit more like what I'm doing, but still got no errors.  But I didn't complicate it to the point of mixing AMD and non, so that may be the root issue, or, that is, how I'm mixing them.  I may just post up exactly what I'm doing, but since github is blocked at work right now, it's a little more challenging than a matter of uploading.  I'll probably just work around that.
About your second comment, I suppose I could treat eaf as a package, but I don't think not doing so should be an issue.
Ultimately, it may just be that I'm trying to fight this framework without much hope of winning.  You see, I rather like j coglan's approach: that you claim dependencies to actual apis, not paths.  You tell (configure) the loader where to find those apis, but in your own api, you keep all references to other apis, and leave the physical layout out of it.  I didn't really want to abandon his loader, but it seems that AMD is the new way, and for the most part I was just going to start using your wire.js and figured migrating to AMD might be the only way to do so.
Anyway, I guess I'm trying to hold on to what I think is the best of the j coglan (or whomever he may be modeling after) world, and merge that with what's best of the AMD world.  He sticks strictly to api, and AMD (helps to) keep everything out of the global space.  Therefore, I'm setting a path for all of my apis, with the key being the api, thinking this will allow me to essentially keep path stuff out of my own module dependencies.
Perhaps this is all possible, and I'm tripping up in trying to use so many non-AMD modules.  This is another good thing about the approach that j coglan took.  Sorry, just saying... more a critique against AMD than curl anyway.
Anyway, thanks again.  I'll try to get more detail and either close this and open another issue, or provide something more helpful in this one.

Hello Toby,
Thanks for the additional information!  Wow, I can't believe that github is blocked at work.  How can you get anything done?  :)
Anyways, mixing AMD and non-AMD files/modules is not easy.  I apologize for the lack of documentation in this area.  Here are some things that come to mind:
a) The js! plugin has been updated since 0.5.4.  The version in the dev branch on http://github/cujojs/curl has one important bug fix (#30) and a new feature.    If you specify the !exports=global_var option at the end of the resource id, it will pass that to dependent modules:
define(['js!my/nonAMDmodule.js!exports=some_global_var', function (some_global_var) { /* ... */ });

b) Non-AMD modules require the .js extension in version 0.5.4.  IIRC, the plugin works a bit differently in 0.6, but I'd plan to include them, anyways.
c) If your non-AMD modules depend on AMD modules, you can get into bad situations fast.  The !order option on the js! plugin does not wait for AMD modules!  For this reason, it's probably easier to migrate the "leaf nodes" in your dependency graph before the core files.
d) There are a few third-party plugins that help deal with these issues.  I have not tried them with curl.js, but the depend! plugin looks like it should work:
depend!: https://github.com/millermedeiros/requirejs-plugins/blob/master/src/depend.js
use.js: http://tbranyen.com/post/amdrequirejs-shim-plugin-for-loading-incompatible-javascript
wrap.js: http://geddesign.com/post/16561192290/introducing-wrap-js
It'd be great to see your code (or a close facsimile) so we could offer more/better help.
Coglan's approach is interesting. It makes sense to me.  After all, paths are just another implementation detail that should be abstracted/hidden.  That sounds similar to the approach I had before @briancavalier introduced me to IOC.  My focus was on the APIs.  APIs are still important when using IOC, of course, but because you've moved the details of the APIs to a small set of declarations and adapters, it's easier to deal with shifting APIs.
-- John

I've seen some people abstract/contain the non-AMD dependencies into one (or more) AMD modules.  Inside the AMD container, all of the non-AMD modules are loaded in the correct order.  Outside of the AMD container, order no longer matters.

Yeah, they switched firewalls and they lost the exception to github.  We're mostly a .net shop and I'm the only one that really uses github, so it's a one man battle right now.
Thanks, I'll try the dev branch version and see if that clears it up.
I noticed that about the .js extension requirement.
Might look into that depend! plugin.  Thanks for the heads up.
Kind of waiting to see if the man will open up github, so it will be easier to upload, so hopefully soon with a more accurate representation of broken code.  I also haven't invested the time to learn github really well--being shamelessly lopsidedly consumerish--so I'll probably be setting things up the hard way.
So you're blaming @briancavalier for corrupting you?:)  Did Coglan win you back over from the dark side?  It would be nice to see wire not depend on AMD--fall back to seeing if the module is a global, or something.  If I can't get this stuff working in fairly short order, there is jsfIoc, but the cujo pack seems like it's got a lot to offer.
About your last comment, yeah, perhaps with some creative packaging, I could wrap all the non-AMD modules in a define or something.  Not sure what else you might mean by abstract/contain.

We're also investigating UMD-formatted modules (AMD + CJSM with node extensions), and old school name-spaced global objects.  Thoughts?