Propose to author to add all her/his papers to an open archive

When an author receives an email asking to release a specific paper, s.he may be willing to release all his/her papers at a time.
Hence, I suggest to add a link to dissem.in in the standard email, suggesting to add the papers missing in open archives (possibly http://dissem.in/search/?authors=).
dissem.in is still under development, as is OAB.

cc @a3nm

Yeah, I think this is a good idea! :)

Thanks for the suggestion, we like the idea too! This is already being discussed in https://github.com/OAButton/discussion/issues/747 :)


Add custom certificate CA support for s3

Signed-off-by: clyang82<EMAIL_ADDRESS>

[ ] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes
use prometheus common tls_config to connect with s3 object store so that we can pass the certificate in.
part of thanos-io/thanos#4820

Verification

@GiedriusS Thanks for your comments. Please take another look.


Make it build again

Hi!
First of all, thanks for the gitlab module. I've made some changes to get it compile again. Also, my limited testing revealed that some API data structures have changed - therefore, I've updated some type definitions. Finally, I've added support for committing changes to files via the API.
Please let me know if there's any issues with my changes. :)

Also could you change the target branch to develop? I'm using the git-flow workflow.


Workspace - Unable to invite a member in a newly created account

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Click the Profile image to open settings for new created account
Navigate to any Workspaces
Go to Members >Manage Members
Invite any email with leading/trailing spaces
Ensure the search shows the result.

Expected Result:
Ensure the search shows the result
Actual Result:
The search isn't shows the result
Workaround:
Unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/148137559-34d5533e-ef20-44c1-a79e-069f42348968.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause
Slack conversation:
View all open jobs on GitHub

Triggered auto assignment to @chiragsalian (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Shall look into this today

Reproduced the same on dev. I bet this is similar to this issue - https://github.com/Expensify/App/issues/6945. Investigating.


S2 Color - Deprecation of negative-subdued-background tokens

Description
Marked the the following tokens in Tokens Studio for deprecation:

negative-subdued-background-color-default ( --> points to negative-subtle-background-color-default)
negative-subdued-background-color-hover
negative-subdued-background-color-down
negative-subdued-background-color-key-focus

Changes were made in light and dark sets and variables were synced in S2/Variables with the latest updates.
For more information, view Jira ticket.

Motivation and context
These tokens were deprecated because the tag "error" variant has been deprecated and are no longer needed in the system. A new "subtle" token has been added for the in-line alert use case.

Related issue

Types of changes

 [ ] Patch (bug fixes, typos, mistakes; non-breaking change which fixes an issue)
 [X] Minor (add a new token, changing a value, deprecating a token; non-breaking change which adds functionality)
 [ ] Major (deleting a token, changing token value type, renaming a token by deprecating the old one; fix or feature that would cause existing functionality to change)
Checklist:

 [X] I have signed the [Adobe Open Source CLA](https://opensource.adobe.com/cla.html).
 [X] I updated the token in all applicable sets. This applies if updating, adding, or deleting a token that has data across different sets (for example, if the value differs across color themes.)

TESTING spectrum2
READING spectrum-tokens: /spectrum-tokens/packages/tokens/src/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-colors/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-non-colors/
STUDIO SYNC SUMMARY
UPDATED METADATA - SPECTRUM UUID: spectrum2/alias/dark.Alias.background.semantic.negative-subdued.🚫 default

SPECTRUM SYNC SUMMARY
NEW TOKENS: (1) negative-subdued-background-color-default/dark
MODIFIED TOKENS: (1) negative-subdued-background-color-default/light
DEPRECATED TOKENS: (4) negative-subdued-background-color-default, negative-subdued-background-color-hover, negative-subdued-background-color-down, negative-subdued-background-color-key-focus
CHANGED VALUES: (1) negative-subdued-background-color-default

TEST COMPLETE

TESTING spectrum2
READING spectrum-tokens: /spectrum-tokens/packages/tokens/src/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-colors/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-non-colors/
STUDIO SYNC SUMMARY
UPDATED METADATA - SPECTRUM UUID: spectrum2/alias/dark.Alias.background.semantic.🚫 negative-subdued.default

SPECTRUM SYNC SUMMARY
NEW TOKENS: (1) negative-subdued-background-color-default/dark
MODIFIED TOKENS: (1) negative-subdued-background-color-default/light
DEPRECATED TOKENS: (4) negative-subdued-background-color-default, negative-subdued-background-color-hover, negative-subdued-background-color-down, negative-subdued-background-color-key-focus
CHANGED VALUES: (1) negative-subdued-background-color-default

TEST COMPLETE

TESTING spectrum2
READING spectrum-tokens: /spectrum-tokens/packages/tokens/src/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-colors/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-non-colors/
SPECTRUM SYNC SUMMARY
DEPRECATED TOKENS: (4) negative-subdued-background-color-default, negative-subdued-background-color-hover, negative-subdued-background-color-down, negative-subdued-background-color-key-focus
CHANGED VALUES: (1) negative-subdued-background-color-default

TEST COMPLETE


Cleanup defmt tags

This adds a write tag to identify format strings from user-defined write! invocations, and splits up the fmt tag into prim for primitives, and derived for #[derive(Format)]-generated strings. This allows tools to distinguish user-controlled format strings from generated ones.

bors r+

bors r+


Fix typo in analytics tracking czi_user

Description

I noticed this bug while investigating erroneous data while looking at the maps analytics. Unfortunately this may have impacted previous analyses by not filtering out czi_users properly, but only when logAnalyticsEvent was called.
Second change is an improvement to fetching contigs. Also tested.

Tests

Use Segment Debugger extension to see the request sent properly.

Thanks! That makes sense.
On Wed, Nov 4, 2020 at 8:59 AM Jonathan Sheu<EMAIL_ADDRESS>wrote:

@jshoe commented on this pull request.
In app/assets/src/api/analytics.js
https://github.com/chanzuckerberg/idseq-web/pull/2557#discussion_r517493030
:

@@ -25,7 +25,7 @@ export const logAnalyticsEvent = async (eventName, eventData = {}) => {
// see traits_for_segment
admin: traits.admin,
biohub_user: traits.biohub_user,

   czi_user: traits.biohub_user,

Wait sorry, for some reason I think I misunderstood or mistyped. czi_user
should definitely not overlap/include biohub_user. I think users_clean DOES
include Biohub users.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/chanzuckerberg/idseq-web/pull/2557#discussion_r517493030,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOHZ3JVBVCU3CW7EULNJIDTSOGB7XANCNFSM4IUNUNQQ
.

--
Amy Krystosik
Data Scientist
Science Initiative
650-400-9308
www.chanzuckerberg.com


Request Body containing a number close to Number.MAX_SAFE_INTEGER has the number transformed to a string

I have checked the following:

[X] I use the newest version of bruno.
[X] I've searched existing issues and found nothing related to my issue.

Describe the bug
Creating a request with a body like this:
{
  "max":<PHONE_NUMBER>740991
}

Sends this request:
> GET /x
> X-Tunnel-Auth-Token:
> x-tunnel-workflow: api
> content-type: application/json
> data {"max":"9007199254740980"}

Note the quotes around the number on the last line.
I consider this a bug. It is not documented behavior, and causes non-obvious errors. The api I was testing reported an invalid request error, and it took me hours to find out that Bruno was the culprit, because it changed the datatype of the number to string.
I investigated why this is happening (theory):
here json-bigint is used to parse the request body and pass it to axios. However, axios does not correctly serialize it back to the same string as the input. I believe JSONBig.stringify must be used to ensure correct conversion.
Alternatively, just giving axios the input string without ever parsing it might be an option.
Note: the req.body object in the script context already has the field as a string..
.bru file to reproduce the bug
meta {
  name: Bug
  type: http
  seq: 2
}

get {
  url: /bug
  body: json
  auth: none
}

body:json {
  {
    "max":<PHONE_NUMBER>740991
  }
}

Screenshots/Live demo link
n/a

Closing in favor of #2767 , sorry for the spam.


Fix multiple content issues

Vi have several issues with duplicated content, caused by e.g dead links, duplicate titles and so on.

I fixed some of the issues, but the remaining is caused by #901.


Broadcast a message

In the Readme under Broadcast from elsewhere you use Websockets but that's not available, what should I use?
I've seen the broadcast function is in https://hexdocs.pm/web_socket/WebSocket.Events.html#content but what should ref be?

Oh nvm seems it's just the handle I se in the router, sorry :)

Seems still not working, this is my code:
router
  socket "/socket", MyApp.WebsocketController, :handle

  def start_link do
    Logger.info("Starting http server")
    Plug.Adapters.Cowboy.http(__MODULE__, [], port: 4000 dispatch: dispatch_table())
  end

handler
defmodule MyApp.WebsocketController do
  def handle(:init, state) do
    {:ok, %{state | use_topics: false}}
  end

  def handle(:terminate, _state) do
    :ok
  end

  def handle(message, state) do
    {:reply, message, state}
  end
end

in my code I do
    message = WebSocket.Message.build("data", data_object)
    json = Poison.encode!(message)
    WebSocket.Events.broadcast!(:handle, json)

but nothing gets received on the websocket client browser

Thanks for the report, @alex88! Looks like the README needs some updating :)
What's your client code look like? Are there any errors displayed in your application's console?
To be honest, there's a good chance the library needs updating. I haven't really messed with it for 2 years, outside of updating some reps. The tests pass, but they're definitely not comprehensive. It also looks like only 1/2 of the examples are working, with the "Topics" example being the one that isn't working. When running the "Topics" example, I'm seeing the following error which closes the open connection:
21:08:42.471 [error] Process #PID<0.300.0> raised an exception
** (ErlangError) erlang error: [reason: {:badkey, :event, %{"data" => "WebSocket rocks", "event" => "topic:a"}}, mfa: {WebSocket.Cowboy.Handler, :websocket_handle, 3}, stacktrace: [{WebSocket.Cowboy.Handler, :get_args, 2, [file: 'lib/web_socket/cowboy/handler.ex', line: 160]}, {WebSocket.Cowboy.Handler, :websocket_handle, 3, [file: 'lib/web_socket/cowboy/handler.ex', line: 98]}, {:cowboy_websocket, :handler_call, 7, [file: 'src/cowboy_websocket.erl', line: 588]}, {:cowboy_protocol, :execute, 4, [file: 'src/cowboy_protocol.erl', line: 442]}], msg: {:text, "{\"event\":\"topic:a\",\"data\":\"WebSocket rocks\"}"}, req: [socket: #Port<0.6875>, transport: :ranch_tcp, connection: :keepalive, pid: #PID<0.300.0>, method: "GET", version: :"HTTP/1.1", peer: {{127, 0, 0, 1}, 51972}, host: "localhost", host_info: :undefined, port: 4000, path: "/topic", path_info: :undefined, qs: "", qs_vals: :undefined, bindings: [], headers: [{"upgrade", "websocket"}, {"connection", "Upgrade"}, {"host", "localhost:4000"}, {"origin", "http://localhost:4000"}, {"pragma", "no-cache"}, {"cache-control", "no-cache"}, {"sec-websocket-key", "VGivwKe/ASv7UfD7JGdk5g=="}, {"sec-websocket-version", "13"}, {"sec-websocket-extensions", "x-webkit-deflate-frame"}, {"user-agent", "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/603.2.5 (KHTML, like Gecko) Version/10.1.1 Safari/603.2.5"}], p_headers: [{"sec-websocket-extensions", [{"x-webkit-deflate-frame", []}]}, {"upgrade", ["websocket"]}, {"connection", ["upgrade"]}], cookies: :undefined, meta: [websocket_version: 13, websocket_compress: false], body_state: :waiting, buffer: "", multipart: :undefined, resp_compress: false, resp_state: :done, resp_headers: [], resp_body: "", onresponse: :undefined], state: %WebSocket.Cowboy.Handler.State{action: :handle, conn: %Plug.Conn{adapter: {Plug.Adapters.Cowboy.Conn, :...}, assigns: %{}, before_send: [], body_params: %Plug.Conn.Unfetched{aspect: :body_params}, cookies: %Plug.Conn.Unfetched{aspect: :cookies}, halted: false, host: "localhost", method: "GET", owner: #PID<0.300.0>, params: %Plug.Conn.Unfetched{aspect: :params}, path_info: ["topic"], peer: {{127, 0, 0, 1}, 51972}, port: 4000, private: %{}, query_params: %Plug.Conn.Unfetched{aspect: :query_params}, query_string: "", remote_ip: {127, 0, 0, 1}, req_cookies: %Plug.Conn.Unfetched{aspect: :cookies}, req_headers: [{"upgrade", "websocket"}, {"connection", "Upgrade"}, {"host", "localhost:4000"}, {"origin", "http://localhost:4000"}, {"pragma", "no-cache"}, {"cache-control", "no-cache"}, {"sec-websocket-key", "VGivwKe/ASv7UfD7JGdk5g=="}, {"sec-websocket-version", "13"}, {"sec-websocket-extensions", "x-webkit-deflate-frame"}, {"user-agent", "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/603.2.5 (KHTML, like Gecko) Version/10.1.1 Safari/603.2.5"}], request_path: "/topic", resp_body: nil, resp_cookies: %{}, resp_headers: [{"cache-control", "max-age=0, private, must-revalidate"}], scheme: :ws, script_name: [], secret_key_base: nil, state: :unset, status: nil}, plug: TopicController, use_topics: true}]
    (cowboy) src/cowboy_websocket.erl:642: :cowboy_websocket.handler_call/7
    (cowboy) src/cowboy_protocol.erl:442: :cowboy_protocol.execute/4

While I'm not 100% sure yet, I have an idea about what is causing this issue. I'll try to get this fixed as soon as I can.

No worries @slogsdon, unfortunately I had to switch to Phoenix just for the websocket feature (deadlines can't wait 😞 )
On the client side I was just using new Websocket(url) and then the regular onmessage, onclose callbacks.
However when I was saying that I didn't receive any message, I was looking in the chrome devtools in the websocket connection's frames tab, so unless there's something messed up with topics (which should be disabled and honestly I don't know how they work) I don't know why it wasn't working.
I've checked the Websocket.Events code and the maybe_send is actually sending the message but I haven't debugged further than that!

@alex88 Looks like it was easier than I thought. There was a change in Poison's decode functionality that changed JSON keys from atoms to strings, so it was interfering with how I was trying to use that data. I've pushed a fix via 1fcec4c619db50312a510095c52b15dd1ec450fc, but I'm currently looking to find a nice way to write some integration tests to cover this and the rest of the library.

As a note, I had intended on shipping this library with this JavaScript helper to aid in the message format for topic support, which may or may not be of use if you end up coming back from Phoenix. At the current state, the innards of the library expects the raw message sent between the server and client to contain an event property to contain topic information and a data property to contain any application data for the event.

With your current js client you mean? Because from the code seems anything would have been ok

Yeah, anything would be valid at this current on both the client and server with any event and/or message. I was only bringing the client library up for the thin wrapper it provides now. The endgame for this library (if it gets to that point) is to provide some conventions for both server and client message formats where the default acts as it does today.


Automated Package Upgrade

:tada: This PR is included in version 6.0.110 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add Swagger and Swagger UI support

The swagger ui with api docs should be at /swagger-ui.html (untested, I don't have http service set-up locally).
EDIT: Now tested:

Signed-off-by: Tomas Slusny<EMAIL_ADDRESS>

Closing in favour of #7847 as I got it to decent state


How to Handle Vanity Route with Future States?

Hi all,
I'm using UI Router future states along with webpack and ocLazyLoad to dynamically download and execute modules. In my future state factory for each module, I register the entire state tree for the module using UI Router's $stateProvider.
My question is about the order in which states are registered. Given the following future states:

/jobs
/{username}

The future state loading works correctly if I visit /jobs first, and then navigate to /chris.  However, if I visit /chris first, the /{username} state is registered with UI router before /jobs, so when I navigate to /jobs it attempts to load the /{username} route.
Is there any way to make sure /{username} always comes last, even if /jobs is registered after?
Thanks!

I think that's a tricky one.  This is a  problem core to ui-router itself, which is in turn exposed by future state registration order.
My best idea is to register ONE future state (i.e., /{username}) and then register BOTH states in the proper order with your Future State Factory.


Allow own dictionaries

This PR will fix multiple issues.

Up to now hyphenation of words with capital letters was borked as not all patterns could be found due to the patterns all being lowercase.
It allows easily and more intuitively to add own dictionaries to the hyphenator not based on locale but based on a file-path.

This addresses and fixes #49


remove the dark mode toggle?

Do we expect users to click on this link or use their system defaults?

It’s possible to do this with some hacky CSS, but it’s pretty brittle and I expect it would break months from now with some future VitePress release. So I filed https://github.com/vuejs/vitepress/issues/3946, and I think wait for that or do nothing.

closed by https://github.com/observablehq/plot/pull/2109


Invalid values for 'Min Hosts'

The following test was run with a single node server with a db associated with a single forest. When the documents were being written, the host was shutdown but job kept running. DO we want to handle these scenarios to ensure the value for 'Suspend Time for Host Unavailability'  is greater than or equal to 1 ?
ihb2.setBatchFailureListeners(
 new HostAvailabilityListener(dmManager, ihb2)
 .withSuspendTimeForHostUnavailable(Duration.ofMinutes(2))
  .withMinHosts(0)
);

I don't understand the question.  In this scenario, I would think that in this scenario every two minutes the withForestConfiguration on the batcher should be called with an updated ForestConfiguration from the server.

I am sorry, I meant the values for 'minHosts'. Will it make sense to have 'minHosts' set to 0 or a negative number ? Should we restrict its values to >=1  (or >=0 ? ) ?

yes, I'll put a check in that minHosts must be > 0

Verified that an exception is thrown if minHosts < = 0


invalid mount config for type "bind"

Fix issues where bind mount fails if path does not exist on the host machine. This is related to how drone-runtime changed how it configured docker volumes when invoking the Docker API.

Oh nice! wondered if it was something to do between drone/docker/moby...
For others, this was our quick workaround in the meantime:
volumes:
  - name: tmp
    host:
      path: /tmp
  - name: cache
    host:
      path: /tmp/cache_${DRONE_COMMIT_BRANCH}/vendor

steps:
  - name: prime-cache-folder
    image: alpine:latest
    commands:
      - mkdir -p /lib/var/tmp/cache_${DRONE_COMMIT_BRANCH}/vendor
    volumes:
      - name: tmp
        path: /lib/var/tmp

- name: cache-dep-restore
    image: drillster/drone-volume-cache
    settings:
      restore: true
      mount:
        - /drone/src/github.com/drone/drone/vendor
    volumes:
      - name: cache
        path: /cache

this is fixed right now in v1.2.2 and in master but you need to use a feature flag to enable. This should be passed to the agent (or the server in single-server mode)
DRONE_FEATURE_VOLUME_SET=true

volumes are tricky because there are 4 different types (tempfs, bind mount, data volume and npipe) and I placed this behind a feature flag to reduce change of regression. I will remove the feature flag in 1.3.0 once I have confirmation that it is working as expected for people.

Setting the feature flag solved the issue for me on 1.2.3 while using named volumes :+1:

removed feature flag and merged into master, available in :latest and will be available in 1.3 which should be tagged today or tomorrow.

How to use it with the gitness ?
I can't figure it out for several days.


zh-translation:2015-07-00-Announcing-First-Kubernetes-Enterprise.md

The file has been modified.
This is the second submission to release-1.14.

/assign @bradtopol


Retry on transient errors

Describe the feature
This has come up in here before. Sometimes transient errors occurs and it would be nice if dbt could automatically retry on those occasions. Right now, those transient errors causes our nightly dbt pipeline to fail, which is blocking downstream pipelines.
Specifically we're dealing with some hard to track dns resolution problems in our network setup which causes some flakiness.
Describe alternatives you've considered
Our dbt pipeline is run from an airflow DAG and the only way to retry is to re-run the DAG which runs the entire dbt pipeline. We could implement better support for running only specific models in our production environment so we can fix the problem faster, however this would still require manual work and cause a significant delay as it wouldn't take place until someone notices the problem in the morning.
Additional context
We're using redshift, but the problem is not related to a specific database.
Who will this benefit?
Everyone that deals with networking and other operational issues.
Are you interested in contributing this feature?
We don't mind contributing on this.
The first problem is identifying which errors are transient (worth retrying) and which are not: https://www.psycopg.org/docs/errors.html
It might be a good idea to leave this decision to the user and let the user configure a retry strategy (but provide a sensible default)

@jtcohen6 what if instead of trying to identify all the things transient errors for all the different connectors, you were able to define a list of exceptions you want to retry on in the profiles.yml?

I'm going to leave this in the current repo, but since the required changes are adapter-specific, it's likely that we'll want to open issues in the adapter repos as well.
(In the case of Redshift, too, the change would probably involve connections.py in dbt-postgres, which is still in this repo)

Would love this functionality as well.
Here's a specific use case.
We are using RDS Aurora Serverless, which has auto-scaling built-in.
When it starts to scale it kicks off connections.
And it starts to scale every time there is load, which is often the case when refreshing lots of dbt models at once.
And then it kicks dbt out and the entire run fails because of maybe one or two failed models, as they were disconnected.
And our runs happen every few hours. By then RDS had scaled down already. And when dbt runs next time, it fails again.
In the end we have pretty much every run fail in some way. The only time it does not fail when the cluster was already scaled out due to some other jobs triggering the scaling event.
To work around that we'll implement forced scaling before dbt runs. But I wish there was just a way to retry certain errors, like disconnects.

I stumbled across this issue as I was debugging some sporadic timeouts when running dbt on our Redshift cluster. I'm commenting to reinforce the need for this issue with my current situation:
From the Redshift connection logs I can see when dbt attempts to connect, and these attempts are successful. However, after about 10 seconds, dbt reports a timeout error (consistent with the default connection_timeout parameter from the postgres adapter). Moreover, the Redshift connection logs also show that the connections dbt started stay up for longer than 10 seconds, which indicates this could be due to transient network problems.
Having the ability to immediately retry when connecting would be very useful for us. At the time, we are relying the status:error workaround but this requires the overhead of restarting our dbt tasks.
Thanks for everything!

👍 on this issue, we are hitting this with Databricks too

same problem happened to us. (with Databricks)

Same issue here using sources that are secured views provided through a Snowflake datashare. Once every 24 hours, the views are dropped and re-created. I don't know why it doesn't happen in a single transaction but the net result is that the views are unavailable for a few seconds. If a job relying on that source happens to be running at that time, it will fail and return an error.
Either a retry logic or any other way to handle this situation gracefully would be great!

Some sort of retry at the model level would be helpful. I have a model in Amazon Aurora PostgreSQL that calls a SageMaker endpoint for ML inferences. Sometimes there are invocation timeouts from the endpoint being too busy, resulting in a failed dbt model. The endpoint autoscales, so simply re-running the model usually works.
I would really like some sort of option that I can apply to specific models, to retry a model N times before considering it as failed.

Hi, How did you'll get through this? Apparently, we are also receiving the below error. And this is intermittent as well, since it works fine the very time the same model is triggered.

Hi, how did you'll get through this? We are facing the similar issue on Redshift now when random reboots happen. We would love to have the retry option in dbt cloud jobs.

Database Error in model data_inspection (models/exposure/tableau/product/data_inspection.sql)
16:28:24    SSL SYSCALL error: EOF detected
16:28:24    compiled Code at target/run/analytics/models/exposure/tableau/product/data_inspection.sql
could not connect to server: Connection refused

There is the dbt retry command since 1.6.0. See #7299 and About dbt retry command.

Our use case is similar to @kinghuang: we have some specific models that we would like to retry upon failure (any failure). We have UDFs calling external services, and so many different transient issues can happen (service issues, network issues, etc.).
The dbt retry command is not ideal as it involves some overhead in order to orchestrate the retries.
Ideally, we'd be looking for something like this:
{{ config(
  retries=2,
  retry_delay=30
) }}

The above would mean: if the model fails, wait 30 seconds and then try again, up to a maximum of two times.
It's a fairly simple feature, and it would benefit everyone.


AMv2 "Send Alert" effect/functionality

The purpose of this is to add an AMv2 effect type that is similar to the "Send alert" option that Discord's builtin AutoMod has. It allows for mod teams to log AMv2 events (with an optional custom message) that may require additional review before an action is taken rather than relying on automatic actions alone.
The reason a custom message was included is to allow mod teams to include extra context or role pings to go along with the alert.
Examples
Here is an example of what it looks like in the UI:

Here is an example of what it looks like when a rule is triggered (custom message left blank):

This is not much different from the existing Send Message effect, why not add a checkbox like "Include trigger message info" to it rather than a whole new effect?

This is not much different from the existing Send Message effect, why not add a checkbox like "Include trigger message info" to it rather than a whole new effect?

The key difference to me looks to be that this is more for the mods and the sendMessage effect is more for the user who triggered the automod. IIRC you cannot have two of the same effect in a rule.

This is not much different from the existing Send Message effect, why not add a checkbox like "Include trigger message info" to it rather than a whole new effect?

The key difference to me looks to be that this is more for the mods and the sendMessage effect is more for the user who triggered the automod. IIRC you cannot have two of the same effect in a rule.

I agree, and I feel like if included in the regular send message effect rather than separating it to an entirely separate rule, people would start asking for more customization. Keeping it as a separate rule enforces that it is a specific purpose built effect for mod review.
That said,

IIRC you cannot have two of the same effect in a rule.
You can, they are deliberately de-duplicated currently: https://github.com/botlabs-gg/yagpdb/blob/85ca471658f78ccbebd3364611b8e2a39cd943cb/automod/effects.go#L873-L875

people would start asking for more customization

I'm not sure I agree, if it's only a checkbox whether to include log info. Just my opinion though :)

the sendMessage effect is more for the user who triggered the automod

Fair, though I'm not sure when you'd want a message to the user sent to another channel. That's mainly what makes these seem redundant to me.

The key difference to me looks to be that this is more for the mods

Yeah this is how I imagined it would be used for most cases. I wasn't sure what to do with the autodelete and ping user checkboxes in sendMessage so I added it as a separate one.
I'm also still not sure what the default behavior should be for when channel == nil if we keep it separate. Should leaving channel nil effectively disable the mod alert?

Meh just let it send to current channel, could make it useful for testing your triggers and conditions


Mark guessed columns

Columns that are imported (without import dialog) should get a visual marker/flag. You have to change the lineupjs library.

Done.


No module named 'django.utils.six'

On first trial, I get No module named 'django.utils.six'
Should probably update the dependencies to include this modules.

Which version did you install?
Could you provide a traceback?


Webpack hot - error on processing fonts

Bug report

What is the current behavior?
When using webpack with the hot command it throws a directory exception on processing the font files. The issue only occurs when using the hot command.
Currently I'm using Laravel Mix as webpack wrapper and I believe the issue is caused by webpack and not by the Laravel Mix package (unconfirmed).
The following error occurs when running the hot command:
C:\wamp64\www\project\node_modules\webpack\lib\util\fs.js:141
                throw new Error(
                ^

Error<EMAIL_ADDRESS>is neither a posix nor a windows path, and there is no 'dirname' method defined in the file system
    at dirname (C:\wamp64\www\project\node_modules\webpack\lib\util\fs.js:141:9)
    at C:\wamp64\www\project\node_modules\webpack\lib\Compiler.js:790:19
    at arrayIterator (C:\wamp64\www\project\node_modules\neo-async\async.js:3467:9)
    at timesSync (C:\wamp64\www\project\node_modules\neo-async\async.js:2297:7)
    at Object.eachLimit (C:\wamp64\www\project\node_modules\neo-async\async.js:3463:5)
    at emitFiles (C:\wamp64\www\project\node_modules\webpack\lib\Compiler.js:536:13)
    at C:\wamp64\www\project\node_modules\webpack\lib\util\fs.js:182:5
    at Immediate.<anonymous> (C:\wamp64\www\project\node_modules\memfs\lib\volume.js:684:17)
    at processImmediate (internal/timers.js:461:21)

Steps To Reproduce:

Using Laravel Mix Version: 6.0.0-beta.17
Installing the @fortawesome/fontawesome-pro package
Running mix watch --hot

What is the expected behavior?
I expect webpack to complete the build process and serve the result.

Additional information:
The exception occurs when it tries to process the following input:
absPath = \fonts\brlnsr-webfont.eot
https://github.com/webpack/webpack/blob/a62ddbd0e72ba3684e9fa25e30cd40324381feeb/lib/util/fs.js#L133-L145
I was able to solve the problem by changing line 138 from
https://github.com/webpack/webpack/blob/a62ddbd0e72ba3684e9fa25e30cd40324381feeb/lib/util/fs.js#L138
to
} else if (absPath.startsWith("\\") || absPath.length > 1 && absPath[1] === ":") {

However I'm not sure if this is the correct solution for the problem / if there is a root cause.
Other relevant information:
webpack version:  5.11.1
Node.js version: v14.15.3
Operating System: Windows 10 19041.685
Additional tools: Laravel Mix

Please create reproducible test repo, maybe bug on laravel mix side, can't reproduce using pure webpack without extra boilerplates

Please create reproducible test repo, maybe bug on laravel mix side, can't reproduce using pure webpack without extra boilerplates

We have a report of a very similar problem at https://github.com/jupyterlab/jupyterlab/issues/9819 (but in our case, with the join method). It does seem like using UNC paths (which are windows paths that start with \\, not with <drive>:) falls through to the error case instead of being caught in https://github.com/webpack/webpack/blob/a62ddbd0e72ba3684e9fa25e30cd40324381feeb/lib/util/fs.js#L138

@jasongrout yep, bug :disappointed: Feel free to send a fix

@jasongrout yep, bug 😞 Feel free to send a fix

See https://github.com/webpack/webpack/pull/12714. Thanks!


Add soroban-example-dapp and js-sdk to terraform

So the contributors could request reviews and assign themselves to the ticket

https://github.com/stellar/terraform/pull/2650


Catch SSHException and try to use scp...

@mboersma

Please also update the setup.py and history file. The new version should be 2.3.4. The version 2.3.3 has been finalized in the ignite release.

Base on the CI warning, I made a change to the history file. However, the setup.py also needs to be updated. The version should be set to 2.3.5


Day after tomorrow is not working correctly

The code below is incorrectly suggesting that the second date in the list is occurring tomorrow.
I am using rrules to generate the date instances and convert them with the timezone package.
    final now = tz.TZDateTime.now(tz.UTC);
    final startOfDay = tz.TZDateTime.from(
      DateTime(
        now.year,
        now.month,
        now.day,
      ),
      tz.local,
    ).toUtc();
    print(now);
    // -> flutter: 2024-02-08 17:33:55.557756Z
    print(widget.plant.wateringNotificationDates(startOfDay).take(3));
    // -> flutter: (2024-02-08 16:00:00.000Z, 2024-02-10 16:00:00.000Z, 2024-02-13 16:00:00.000Z)
    print(widget.plant.wateringNotificationDates(startOfDay).take(3).map((e) => e.toLocal().relativeTime(context)));
    // -> flutter: (1 hour ago, tomorrow, in 4 days)

I'm running into the same issue - both dates that are tomorrow and the day after tomorrow return "tomorrow" when using relativeTime. Did you end up finding a fix or workaround?


Use network-status annotation instead of networks-status

The latter is deprecated and removed in the latest CRC image NAD client library.

recheck
It failed to pull passwords from tripleo machine, this is before the code changed.

recheck

recheck

recheck


fixes name displayed when removing models

Thanks for contributing! I've added Grunt-cli to Travis so the builds should pass again.


BUG: CustomIntegration not using Pass Phrase when generating Signature

Good Day
On line 34 of payfast-php-sdk\lib\PaymentIntegrations\CustomIntegration.php
The signature is generated as:
$signature = Auth::generateSignature($data);
But it needs to be:
$signature = Auth::generateSignature($data,PayFastPayment::$passPhrase ?? null);
Otherwise the error: "Generated signature does not match submitted signature." occurs

Thank you, updated in v1.0.1

No, Thank You!


Invalid 'dependsOn' attribute should fail BuildADFTask

We are using the BuildADFTask to validate the ADF files in our CI pipeline, but if there is a pipeline in which an activity has a dependsOn attribute on an activity that does not actually exist, the validate step succeeds even though when run the pipeline will fail.
Is this a bug in the Data Factory itself, or can it be fixed in this task?
Example pipeline:
{
    "name": "pipeline1",
    "properties": {
        "activities": [
            {
                "name": "Wait1",
                "type": "Wait",
                "dependsOn": [],
                "userProperties": [],
                "typeProperties": {
                    "waitTimeInSeconds": 1
                }
            },
            {
                "name": "Wait2",
                "type": "Wait",
                "dependsOn": [
			{
				"activity": "does-not-exist",
				"dependencyConditions": [
					"Succeeded"
				]
			}
		],
                "userProperties": [],
                "typeProperties": {
                    "waitTimeInSeconds": 1
                }
            }
        ],
        "annotations": []
    }
}

It validates, but produces this error when run:
ErrorCode=InvalidTemplate, ErrorMessage=The template validation failed: 'The 'runAfter' property of template action 'bad_lossScope' contains non-existent action: 'employmentScope'

Our yml:
- job: 'adf'
  displayName: 'Data Factory'
  pool:
    vmImage: 'windows-latest'
  steps:
    - task: SQLPlayer.DataFactoryTools.BuildADF.BuildADFTask@1
      displayName: 'Validate ADF files'
      inputs:
        DataFactoryCodePath: '$(System.DefaultWorkingDirectory)/data-factory'

It isn't clear to me whether this task is using the same functionality as the 'validate all' button in the UI, I'm confused by the readme: it has a 'Build only' section, and then a 'Validate & Export ARM Template' section which mentions the azure-data-factory-utilities npm package, but also a 'Build only' action of which I don't know whether it is the same as the 'Build only' of the previous section. I looked in the source and it does seem like some checks are implemented in this repo.

There are two actions you can choose from in this task:

"Build": "Build only (simple validate)",
"Export": "Validate & Export ARM Template"

The build (default) is developed internally and has nothing to do with Microsoft's "Validate All" button known from UI.
This is your case as you did not specify Action parameter.
Currently, the task does NOT support the validation of activities dependencies.
It does it for ADF objects dependencies (like pipeline, dataset, linked service, etc).
Export executes export command from Microsoft's (npm) library, which includes validation operation as well.
This action is a counterpart of "Validate All" button known from ADF UI.
In the readme file both sections are mentioned:
https://github.com/SQLPlayer/azure.datafactory.devops#buildtest-azure-data-factory-code

Build only
Validate & Export ARM Template

The build (default) is developed internally and has nothing to do with Microsoft's "Validate All" button known from UI.

That was not clear from the readme, but I understand. The functionality seems quite similar to me.

Currently, the task does NOT support the validation of activities dependencies.

That's indeed what I found out, but I can understand if you don't want to implement it, because the Data Factory 'Validate All' button hasn't implemented this either. We'll just implement our own check for that, then.

In the readme file both sections are mentioned:

Build only
Validate & Export ARM Template

Of course I saw this, but now from your comment I can guess that the 'build only (validate)' of item 1 refers to the internally developed 'build only' of the previous section, and it is not the same as the 'validate' from item 2.
It isn't clear to me yet whether this is the PublishADFTask or the BuildADFTask that has this 'Action' parameter, but I guess I can try out both.
Basically it is not clear to me from the readme what yml code I should use, the way I now do it is first use a DevOps pipeline to add these tasks using the UI, and then view the yml, which also works.
Thanks for the support!

Thanks for your comments, I really appreciate it.
You're probably right - the documentation might be sorted out and enhanced in some section (especially this one), which I will do in my spare time.
If you're happy to share your code with me and adopt it in this module, you're welcome.
Let me know if you prefer to just send me the code or make the changes and create PR on your own.

Thanks, I can also help with the documentation, I can create a PR later today.
I'm not very fluent in PowerShell, so I will have a look next week or so if I can figure it out the code, and if so I'll create a PR for sure!


Rewritten my information

Changed my information can you review and merge. Then delete this branch.

Thanks!


hypercore v5  support

started SLEEP (hypercore v5) support, but missing something in the replicate function.

close, but tests are still failing now with this:
/Users/karissa/node_modules/hypercore-archiver/node_modules/hyperdrive-encoding/index.js:24
  if (!enc) throw new Error('Unknown message type: ' + toTypeString(type))
            ^

Error: Unknown message type: unknown
    at getEncoding (/Users/karissa/node_modules/hypercore-archiver/node_modules/hyperdrive-encoding/index.js:24:19)
    at Object.decode (/Users/karissa/node_modules/hypercore-archiver/node_modules/hyperdrive-encoding/index.js:32:13)
    at /Users/karissa/node_modules/hypercore-archiver/tests/archive.js:52:28
    at onread (/Users/karissa/node_modules/hypercore-archiver/node_modules/random-access-file/index.js:107:25)
    at FSReqWrap.wrapper [as oncomplete] (fs.js:681:17)
npm ERR! Test failed.  See above for more details.

and test/feed.js with
/Users/karissa/node_modules/hypercore-archiver/node_modules/hypercore/lib/replicate.js:269
  this.stream.want({start: 0}) // TODO: don't just subscribe to *EVERYTHING* hehe
             ^

TypeError: Cannot read property 'want' of null
    at Peer.ready (/Users/karissa/node_modules/hypercore-archiver/node_modules/hypercore/lib/replicate.js:269:14)
    at /Users/karissa/node_modules/hypercore-archiver/node_modules/hypercore/lib/replicate.js:24:10
    at /Users/karissa/node_modules/hypercore-archiver/node_modules/hypercore/index.js:113:15
    at apply (/Users/karissa/node_modules/hypercore-archiver/node_modules/thunky/index.js:44:12)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)

@karissa I think I fixed the content issue, we had to change how we were doing the decoding of the index block. But... something is still broken with the decoding. I think we need to catch an error that we aren't right now but can't quite figure it out where the test error is coming from:
# add new feed key
ok 28 changes error
ok 29 changes feed get error
ok 30 one block in change feed
ok 31 changes key okay
ok 32 changes type add
ok 33 add event key okay
ok 34 add error
ok 35 archived event key okay
ok 36 feed get error
ok 37 feed block: 0 is correct
/Users/joe/node_modules/hypercore-archiver/node_modules/protocol-buffers/compile.js:32
      throw new Error('Groups are not supported')
      ^

Error: Groups are not supported
    at skip (/Users/joe/node_modules/hypercore-archiver/node_modules/protocol-buffers/compile.js:32:13)
    at Object.decode (eval at <anonymous> (/Users/joe/node_modules/hypercore-archiver/node_modules/generate-function/index.js:55:21), <anonymous>:33:16)
    at /Users/joe/node_modules/hypercore-archiver/node_modules/hypercore/index.js:967:18
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)
npm ERR! Test failed.  See above for more details.

That's about all my brain can handle for the day!

Going to take a stab at it. Found a few reference issues
https://github.com/mafintosh/protocol-buffers/issues/38
https://github.com/mafintosh/protocol-buffers/issues/44

If its any consolation, it works! :P

OK I added some testing to the tests/archive.js -- I realize that if you add the valueEncoding in index.js, the archive test pass, but if you remove valueEncoding, these new archive tests fail.
So the Group bug comes when you're trying to read a hypercore as though its a hyperdrive, because protobuf is trying to decode a string using message.Index
So we need some way to specify (or see inside) if a feed is a hyperdrive and encode the values accordingly if so.

I think I got it in there, tell me what you think

We should bump version to v4?

@karissa i investigated your bug in hypercore today. it is a bug on my side but it is caused by the fact that the first hypercore shared is not the same which it should be. you prob just need to guard some async logic to make sure that happens. ping me if this makes no sense :)

@karissa updated the test. I was having trouble with the old test and the feeds weren't ever added to the archiver.
This one is a bit more explicit about the adding + replication. BUT still having trouble replicating the second feed.
However, it doesn't look like it's related to the order - they are getting opened and replicated in the correct order. Still digging in...

OK Yeah, that test looks better, nice!

Here's the change to allow archiver.get to optionally use timeout.
commit 8b1059478b31c8e21fe6eb3b821458d8e54c7e68
Author: Chia-liang Kao<EMAIL_ADDRESS>Date:   Thu Apr 20 14:24:29 2017 +0800

    allow feed.get options

diff --git a/index.js b/index.js
index fd925ae..6ad17b2 100644
--- a/index.js
+++ b/index.js
@@ -165,7 +165,8 @@ function create (opts) {
     })
   }

-  function get (key, cb) {
+  function get (key, opts, cb) {
+    if (typeof opts === 'function') return get(key, {wait: false}, opts)
     key = datKeyAs.buf(key)
     var discKey = hypercore.discoveryKey(key).toString('hex')
     keys.get(discKey, function (err, key) {
@@ -176,18 +177,14 @@ function create (opts) {

       noContent.get(discKey, function (err) {
         if (!err) return done(null)
-        feed.get(0, {
-          wait: false
-        }, function (err, data) {
+        feed.get(0, opts, function (err, data) {
           if (err) {
             if (err.notFound) return done(null)
             return cb(err)
           }
           var decoded = tryHyperdrive(data)
           if (decoded.content || !feed.length) return done(decoded.content)
-          feed.get(feed.length - 1, {
-            wait: false
-          }, function (err, data) {
+          feed.get(feed.length - 1, opts, function (err, data) {
             if (err) {
               if (err.notFound) return done(null)
               return cb(err)

Rewrote the entire thing. Latest npm release (4) has v5 support


Delete event

Subject: Delete event
Description:
I can't find how to delete events
Results:
delete button
Backend version: develop-0023fa73
Frontend version:
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Page: https://couchers.org/event/2047/bi-weekly-meet-up/edit
User: lf106 (11345)

not a bug


Make noarch

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Makes this package noarch.
pip check will fail due to the incorrectly specified requirements of transformers 3.5.1 wich is why I removed it again.
Most parts are generated by Grayskull.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@ndmaxar @oblute @rluria14 Just gently bumping this again, thanks!

Pinging this again. Also, let me know if you'd like some help with maintaining this package.

@conda-forge-admin, please rerender

Changes are applied and tests are passing. Thanks for the review @isuruf


Tabular: Added as_multiclass parameter to predict_proba

Issue #, if available:
https://github.com/openml/automlbenchmark/pull/109
Description of changes:
Added as_multiclass parameter to predict_proba
Now it is much easier for users to get the correct label corresponding to True/False in binary classification by specifying as_multiclass=True and adding values to predictor.class_labels and predictor.class_labels_internal for binary classification.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-447-1 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-447/1/index.html

Job PR-447-2 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-447/2/index.html


Fix loading scripts from other scripts

This fixes issue #149.

One small nit, but looks good

Looks great, thanks!


Add ability to dump TabularResult data as CSV

Add .toCSV() method to TabularResult.  Should be able to use the existing CSVWriter pretty easily.

If you want to fetch as CSV you can use the Tablesaw session and then call .write().csv on the table returned


Updated Homepage link which was broken

Hello. The homepage link was broken and I realised it while reading the webpage on https://haskell-alex.readthedocs.io/en/latest/about.html#

I am fixing all http links in the docs in 44ace12 (#247)


About "original_logits" and "outputs" issues

When calculating top1 and top5, why use "original_logits" instead of "outputs"? Although this does not affect the training process, I found that the top1 obtained with "original_logits" will be much larger than the top1 obtained with "outputs". This is exactly the opposite of my expectations. Why is that?

When calculating top1 and top5, why use "original_logits" instead of "outputs"? Although this does not affect the training process, I found that the top1 obtained with "original_logits" will be much larger than the top1 obtained with "outputs". This is exactly the opposite of my expectations. Why is that?

Hello!
I have the same problem with you. Why using "original logits" instead of "outputs" during calculating? Have you already known the answer?  Thx :)


BSD currency is define in iOS sdk

Hello. When using the --swift-friendly flag, the currency is converted to property with the BSD name, but in iOS sdk there is already a define with the same name in header file param.h.

Hi, you have a couple of options.

--swift-friendly = --static-accessor-methods --nullability --class-properties
You could try by only using --static-accessor-methods --nullability

If you want the benefits of class properties, you could add BSD to the list of reserved names. The property will be named BSD_. If you are using the released distribution, you can update the reserved names by updating this file
com/google/devtools/j2objc/reserved_names.txt
in
path_to_j2objc/lib/j2objc.jar

Here is an example of listing the file:
$  jar -tf lib/j2objc.jar | grep reserved
com/google/devtools/j2objc/reserved_names.txt
Let us know if the second option works for you and we will consider adding BSD to reserved_names.txt in the next release.

Second options is perfect worked.

Hi, you have a couple of options.

--swift-friendly = --static-accessor-methods --nullability --class-properties
You could try by only using --static-accessor-methods --nullability
If you want the benefits of class properties, you could add BSD to the list of reserved names. The property will be named BSD_. If you are using the released distribution, you can update the reserved names by updating this file
com/google/devtools/j2objc/reserved_names.txt
in
path_to_j2objc/lib/j2objc.jar

Here is an example of listing the file:
$ jar -tf lib/j2objc.jar | grep reserved
com/google/devtools/j2objc/reserved_names.txt
Let us know if the second option works for you and we will consider adding BSD to reserved_names.txt in the next release.

Second options is perfect worked.

There is also define EMPTY in the header utmpx.h


Changed de-allocated VM check

Changed de-allocated VM check from Primary IP Configuration to MacAddress.  Signed-off-by: Shaun Laughton<EMAIL_ADDRESS>

Thanks Shaun I appreciate the effort, but the PR is carrying some commits that should be here, the DCO is missing and will probably need some unit tests which might be tricky if you are not a golang dev.

This still needs a DCO.

We have decided to close this PR during our bug scrub as it has been inactive for a long time. Please reopen it with proper DCO if you still need need this.


Timestamp Bug

Hi, I am using the openlaw js client and it seems like the timestamp is incorrect I am assuming its supposed to be a unix timestamp? This is the response I get when calling executing await apiClient.getTemplateVersions(openLawConfig.templateName, 20, 1);

In unix this would be:

In the documentation as well, this timestamp is similar:

Hi @javaadpatel I've run these inputs through Date() and they appear OK.
new Date(1571759717000)
Tue Oct 22 2019 16:55:17 GMT+0100 (British Summer Time)
new Date(1537509029000)
Fri Sep 21 2018 06:50:29 GMT+0100 (British Summer Time)

@jtrein, it does work when using Date but I think that's just a caveat of how javascript's Date function works, because I think it works using milliseconds. The actual input<PHONE_NUMBER>000 is not a valid unix timestamp.
var date = new Date(UNIX_Timestamp * 1000)
so the actual unix_timestamp would be<PHONE_NUMBER>. If this is how its intended to be used then that's fine, i just thought it was a unix timestamp.

Hi @javaadpatel you're correct. We could be more clear about this in our documentation, perhaps. Since it is a JS library targeting a JS client, operating in milliseconds is the valid way (as you've alluded to). 🙂


bug: Mixtral chat throwing a 400

Version
1.4
Describe the bug

Expected behavior
Not throw a bug
Additional context
No response

Did this happen on self-service/PLG? I can't repro neither with 1.4.3 nor with the latest unstable 😬

Hm not seeing this anymore. closing as can't repro


Improve tauri integration

I just finished running Atomic-Server in tauri: ihttps://github.com/joepio/atomic-data-rust/issues/215
But some front-end stuff could be improved

[x] Open outgoing links in normal browser
[x] Show back / forward buttons while running in Tauri
[ ] Explore cool features
[ ] Remember window location

I just came across atomic. Very cool project. I was searching github how to integrate tauri and actix. In my case I wanted to send messages between tauri and actix so I kept looking. I found this approach. Sharing just in case it would be inspirational.

Thanks for sharing, @iilyak ! I ended up doing this, which means spinning up a runtime in a non-blocking Tauri async runtime.

I'll keep this issue on hold as Tauri is no longer functional. Blocked by: https://github.com/joepio/atomic-data-rust/issues/246

Tauri is working again, so this issue wont be on hold anymore.


Isaac Sim 4.0.0 Support

Wondering if Isaac Sim 4.0.0 is in the works and if we'll be able to use Isaac Lab tools with Pegasus

I'm working on it. Check the branch dev_isaac_4.


Enable Aurora to run impurity transport simulations for AUG

This PR is part of a new project to enable use of Aurora at AUG and also make OMFIT more accessible/useful at IPP.
This PR begins with a simple function that allows construction of a proxy for the EFIT geqdsk dictionary built by OMFIT. I've also written an example script in the "examples" directory to illustrate how everything can work.
Further refinements may be useful/needed.
The next step in this work is to add AUG spectroscopic diagnostics to the ImpRad module in OMFIT, which uses Aurora for forward modeling.
Many thanks to @tardini for his help with aug_sfutils!

Right now something in the automatic testing is failing -- it seems to be an issue on the cython side in scipy... Unless someone can help here and identify the issue, I'm going to wait before merging into master, hoping that the issue is solved upstream.


Versioning

Hey,
I would like to lock the version of the fastp linux binary I am using when downloading it from http://opengene.org/fastp/fastp. Is it possible to include the respective version in the URI -
0.21.0 as of now - and if not, could you please include it? Another way could be to tag the newest version here in the repo - I think the last version tag is 0.20.1. Thanks a lot!
Martin

I second this request and would like to suggest that the binary is distributed via GitHub releases. So that users know exactly what version of fastp is present in the binary, and so that releases are stably tracked through GitHub.
When I build docker image for programs such as fastp, I prefer to download binaries from the GitHub release to aid in reproducibility.

I second this request and would like to suggest that the binary is distributed via GitHub releases. So that users know exactly what version of fastp is present in the binary, and so that releases are stably tracked through GitHub.
When I build docker image for programs such as fastp, I prefer to download binaries from the GitHub release to aid in reproducibility.


Merge v2.1.2-ga into release/2.1

Merges the v2.1.2-ga tag into the release/2.1 branch. We didn't push directly into the release/2.1 branch to preserve green CI.
Once this is merged, we'll tag the result v2.1.2.
/cc @dleeapho @dseefeld @crummel

error: Server does not allow request for unadvertised object<PHONE_NUMBER>872e659ff226d515cc72ae9bf4fa42
Fetched in submodule path 'src/cli', but it did not contain<PHONE_NUMBER>872e659ff226d515cc72ae9bf4fa42. Direct fetching of that commit failed.

CLI doesn't have its commit available yet.

When https://github.com/dotnet/cli/pull/9633 goes green, I'll merge and let you know.

@dotnet-bot test this please

error: Server does not allow request for unadvertised object d4541b21dcb0cb15c5ec49c38354bde46e3eaea4
Fetched in submodule path 'src/corefx', but it did not contain d4541b21dcb0cb15c5ec49c38354bde46e3eaea4. Direct fetching of that commit failed.

It looks like corefx doesn't have its commit available, yet.

@dotnet-bot test this please

@dotnet-bot test this please

@dotnet-bot test this please
ProdCon feed should be set up now.


Locality bonus sorting

Hi I wonder why cmp wont show the most obvious suggestion first:

Is there way to boost weight of buffer words that are closes to currently edited lines?  So that  words from line above get most priority? Then less and less the further we go.
There is something in docs about sorting but I cant figure out how these parameters are working:

{
compare.offset,
compare.exact,
compare.score,
compare.kind,
compare.sort_text,
compare.length,
compare.order,
}

And if they would help at all in above case.

I think this is important but it is difficult from performance concerns.

I also encounters this problem that nvim-cmp not always put the most matched item on the top of the list.

I think nvim-cmp always puts the best matching item. (In the screenshot above, all offset_ prefixed items are` the best match``.
nvim-cmp doesn't care about "locality", but it's just "enhancement or new feature", not a problem.

I think it is best to give an option that enables sortation by length.  For example, the offset is the most matching one according to the typed word.

You can disable LSP's sort_text sorting.
local cmp = require('cmp')
cmp.setup {
  sorting = {
    comparators = {
      cmp.config.compare.offset,
      cmp.config.compare.exact,
      cmp.config.compare.score,
      cmp.config.compare.kind,
      -- cmp.config.compare.sort_text,
      cmp.config.compare.length,
      cmp.config.compare.order,
    }
  }
}

@d0u9  length comparator seems not useful. Below example with only length  comparator :

at|    cmp suggest  at  - does not save any key presses
att|     cmp suggest  attr - does not help - I would have to tab 6 times to get to correct suggestion see image below)

If we got  'attribute_node' suggested, then it saves me time of typing in of 12 characters   |ribute_nodes.
The most helpful suggestion I managed to get are with following setup
comparators = {
	compare.score, -- based on :  score = score + ((#sources - (source_index - 1)) * sorting.priority_weight)
	compare.offset,
	--compare.order,
	--compare.sort_text,
	-- compare.exact,
	-- compare.kind,
        -- compare.length,
}

It is correctly suggesting 'attribute_node' right after second letter I typed in   - at|.

I'm not sure if I understand the comparators   - but It looks like enabling more  of them, just give you more results - but the quality (probability of result being what I need) is not increasing at all.     It works like:

score results   +  offset results  + sort_text results  etc.

But it  could / should work like:

filter_by_proximity (  filter_by_sort_text( score.results )  )   #  get results based on cmp 'sources', then filter these by similarity/distance to user input,  then maybe filter again by weighting by locality bonus (or frecency).

It is different for each person.
The users are free to customize it.
The nvim-cmp is based on the VS Code sorting logic and some of the customization. For example, VSCode does sort by alphabetical but nvim-cmp sort by length.

I'm glad you made the settings you expected. 👍🏼

I think ddc-around (also available in deoplete) is interesting, which selects the candidates from flanking lines. It might be nice if similar source is made here.

The ranking is implemented in sorter-rank instead of ddc-around.

Wouldn't, architecturally, locality be responsibility of the LSP server?

The best @dmitmel did it.


[HttpClient] Remove deprecated HttpClientContext, migrate to HttpClient

are we removing all the deprecated stuff now?

I'd say V2, since this is a real breaking change


Uses versions.yaml to define builder base versions

Issue #, if available:
Description of changes:
Had a conversation with @danbudris about automating the golang version updates. Switching to a yaml file should make that automation, as well as manual updates, much easier.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

/lgtm


Is my use case a good fit for sophia?

In the scope of the Rust ecosystem, is Sophia a good choice for serializing Hydra into JSON-LD?
My end goal is to create a wrapper around an existing Rust web framework (maybe Warp?) that makes it easy to generate Hydra JSON-LD documentation automatically from Rust source code with minimal effort. I know that there are many projects for serializing to JSON, but getting the JSON-LD semantics correct would be extremely helpful.
From the documentation I've looked at so far, I'm not quite sure if this project is a good choice to build on top of or not. Do you recommend looking for a different crate? Are there any hydra crates I've overlooked?

In the scope of Rust, I would say sophia is your best choice currently.
As far as I understood, Hydra it's basically a vocabulary for describing Web APIs. For building up an RDF-graph sophia is totally suited and has many convenient things to do so, e.g. namespace!() to declare your vocabulary inside Rust code.
As far as JSON-LD support goes, you might have seen the sophia_jsonld crate. It might not be very mature as it can only serialize expanded JSON-LD at the moment but it is a good point to start. In the end, the only missing thing for from the RDF-side of your project is to implement a proper JSON-LD compaction algorithm to have a nice serialization.
There are other crates about JSON-LD (https://crates.io/search?q=json-ld, https://lib.rs/search?q=json-ld), however, none of them is as well maintained as sophia and most are only concerned with JSON-LD directly and do not cover the RDF part.

@brycefisher nice project, I'm looking forward to trying that!
@MattesWhite summed it up pretty well. You can either construct an RDF graph using the implementations provided by Sophia, or maybe have your own types implement the Graph trait to avoid duplicating information.
Then indeed, you can generate expanded JSON-LD with the serializer provided in sophia_jsonld. Compacting it to a more idiomatic form is the job of JSON-LD's compaction algorithm, which has no implementation in Rust for the moment, AFAIK.
However, I have been in contact with @timothee-haudebourg, who is working on an implementation of JSON-LD. Hopefully I'll find some time to contribute to this one during the summer, but I guess Timothée can use any help he can find :wink:.

This is great info and great news! Thanks so much. I think I still need to get up to speed on JSON-LD syntax and semantics, but it sounds like this is the crate for me. Many thanks!!

Help is indeed welcome :smiley:
I'm working on the compaction algorithm on a dedicated branch. I had to take a break from JSON-LD but I should resume development relatively soon.


create signup page

add register user page so someone can create an account

Output

https://github.com/jjackson0228/Pawsitive-Connection/pull/57


Close panel if opened-prop is set to false

Fixes #3206

Thanks, but any fixes should be done in src files src/phenome/components/panel.jsx not in package. Can you change it there instead?

But this is a F7 vue specific issue. It does not affect the core library. I can't find any vue related code inside the src folder. In src/phenome/components/panel.jsx there are no vue watch methods. The  framework7-vue repository also looks not like the right place as it says "deprecated" on top...

This file src/phenome/components/panel.jsx is generated to that Vue component file

Ah I see :+1: . Alright changed it inside the panel.jsx

Thanks! 👍


Fixing bugs in vizapp

I've started to apply some of the changes outlined by #290 , but there's still lots that needs to be done

[ ]  Refactor sensitive volume calculation and debug why initialization takes so long
[ ] Move redshift calculation to initialization of Foreground object as one of its attributes
[ ] Make points on VT plot more visible

Moved the redshift computation to the front of the VT calculation loop, but this still takes long enough that we won't want it to be done every time we change our mass distribution, so it should probably be moved to the Foreground initialization to pay the cost once fully up front.
@EthanMarx I know we talked about some other fixes/additions we would like the vizapp to have yesterday but I can't seem to think of them now. Any additional to-do's this PR should have?

I don't think anything for this PR. I'll open up issues for the other items.

Should we get these bug fixes merged in and address the other points separately?

Yeah I think so, having this be so slow is a real bummer when you have some results you want to analyze

I think this just needs to be rebased on main to pull the isort update

Yeah I have a couple more slight optimizations I've made locally, I'll get things fixed and then push to get this merged ASAP


How to create reader with separator and options?

Hi,
trying to create a reader with following setup:
var sep = Sep.New(',').Reader(o => o with { o.DisableColCountCheck = true }).FromFile(filename);
best
wiman

Hey @nwiman, thanks for reporting this issue, there is a lack of overload for this! I am looking into it.


Enumerate log file targets and multiline config

Using more than one prospector allows us to configure the openstack
services with multiline log parsing. This prevents us from applying
that same logic to non-OpenStack services (which will mess up log
shipping). It also allows us to define multiline rules for each of
the services we hope to ship to logstash with multiline log messages.
Filebeat will ignore directories/paths that do not actually exist on
the host so we can safely enumerate all of the services we want to
apply multiline parsing to in one prospector.
We do have to, however, ensure that paths do not overlap with the
prospectors. Filebeat explicitly calls this out as "undefined"
behaviour.
Included near the multline configurations are play.golang.org links so
others can experiment with what we used to test the multiline regular
expressions. Also, given the complexity and widespread use of our
OpenStack multiline expression, we've attempted to thoroughly document
it.
Connects rcbops/u-suk-dev#261

RPC-AIO-Liberty-PR: Fail

RPC-AIO-Ceph-Liberty-PR: Fail

RPC-AIO-Liberty-PR: Fail

This is working acceptably in the lab, there may be some tweaking require but it is a very good start.  Well done @sigmavirus24 :+1:

For now it looks nice. I'll re-test on my aio.

@evrardjp I removed input_type: log per your request.

The code seems fine and I see multiline content in my kibana. However, I didn't fully test it.
It looks generally ok.
If it passes gates, it has my 👍


oneMKL's CMake Does Not Detect SYCL Support when Compiled with intel/llvm

Summary
oneMKL uses CXX_COMPILER_NAME to detect SYCL support.  This means that if a user compiles their own copy of intel/llvm, SYCL support is not detected and the MKL::MKL_SYCL library will not be available.  (The CXX_COMPILER_NAME is by default Clang.)
Users can force set SYCL_COMPILER with -DSYCL_COMPILER=ON, which will make the MKL::MKL_SYCL library available.  However, with CLANG_COMPILER also set, the intel_thread backend is also made available.  This elicits a compiler warning:
bbrock@ortce-skl22:~/src/distributed-ranges/build/examples/shp$ make -j
Consolidate compiler generated dependencies of target fmt
Warning: Using MKL::MKL_SYCL* targets with intel_thread may have potential composability problems on CPU device with other SYCL kernels.
[  5%] Building CXX object _deps/cpp-format-build/CMakeFiles/fmt.dir/src/os.cc.o

Which seems to indicate this is still a sub-optimal solution.
Version
oneMKL develop branch.
Environment

Running on a system with two SPRs and 8 PVC GPUs.
Both production oneMKL 2024.0 and oneMKL develop.
Ubuntu 22.04 LTS
Fresh intel/llvm

CMake output
Steps to reproduce

Compile fresh intel/llvm
Compile a project, including oneMKL via CMake (in my case distributed ranges)

Observed behavior
Build fails due to MKL::MKL_DPCPP/MKL::MKL_SYCL library not being available.
Expected behavior
I expect SYCL support to be detected by oneMKL and the build to succeed.

I implemented a first stab at this in a new PR #450.  It is based on oneDPL's CMake and modifies MKL's MKLConfig.cmake to explicitly check for support for the -fsycl flag and SYCL headers.


No provider for darwin_arm64

After switching to a M1/M2 Mac the provider isn't built with darwin_arm64 support.
│ Error: Incompatible provider version
│
│ Provider registry.terraform.io/robgmills/ipinfo v1.0.0 does not have a package available for your current platform, darwin_arm64.
│
│ Provider releases are separate from Terraform CLI releases, so not all providers are available for all platforms. Other versions of this provider may have different platforms
│ supported.

I'm hoping #1 fixes this. Thanks for the provider!


fix: fix flaky tests, cleanup code

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.4%. Comparing base (c4ce0fa) to head (e3bb9c3).
Report is 3 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files

Files with missing lines
Coverage Δ

schema-registry-api/src/domain/schema/version.rs
93.5% <ø> (+4.6%)
:arrow_up:

... and 18 files with indirect coverage changes

Issue with minimal version is reported here: https://github.com/TrueLayer/reqwest-middleware/issues/204


IOWebSocketChannel.connect use protocols parameter can not work

    final WebSocketChannel channel = IOWebSocketChannel.connect('ws://localhost:7070/ws/',protocols: ['xmpp']);

but the IOWebSocketChannel connect method not use protocols yet :
 WebSocket.connect(url.toString(), headers: headers)
 factory IOWebSocketChannel.connect(url,
      {Iterable<String> protocols,
      Map<String, dynamic> headers,
      Duration pingInterval}) {
    var channel;
    var sinkCompleter = new WebSocketSinkCompleter();
    var stream = StreamCompleter.fromFuture(
        WebSocket.connect(url.toString(), headers: headers).then((webSocket) {
      webSocket.pingInterval = pingInterval;
      channel._webSocket = webSocket;
      sinkCompleter.setDestinationSink(new _IOWebSocketSink(webSocket));
      return webSocket;
    }).catchError((error) => throw new WebSocketChannelException.from(error)));

    channel = new IOWebSocketChannel._withoutSocket(stream, sinkCompleter.sink);
    return channel;
  }

pls fix it

I don't understand what the issue is about,
but if it is a bug or feature request it should be reported in https://github.com/dart-lang/web_socket_channel/issues
otherwise better ask on StackOverflow.


Collisions with Dynamic Trimesh

I am pretty new to Cannon, and I still have difficulty understanding the way collision works. My application requires me to use the undocumented Trimesh object3D structure. One such trimesh object is generated on the fly for each frame and is required to collide/ contact with a static rigid box. I have setup parameters for collision, similar to examples in the documentation for other types of object3D bodies.
world.defaultContactMaterial.contactEquationStiffness = 1e9;
world.defaultContactMaterial.contactEquationRelaxation = 4;
var physicsMaterial = new CANNON.Material("slipperyMaterial");
var physicsContactMaterial = new CANNON.ContactMaterial(physicsMaterial, 														physicsMaterial, 0.0, 0.3);
world.addContactMaterial(physicsContactMaterial);
objectBody.linearDamping = 0.1;
objectBody.velocity.set(0.1,0,0.1);
objectBody.angularVelocity.set(0,0,0);
I have also setup nominal linear velocities for the dynamic body, that are updated each frame with trimesh recalculation, while the other object is static. They also have equal masses of 0.5 (also tried higher values). During the collision the dynamic trimesh just passes through the static body, without moving it. Can you possibly let me know what parameters I would need to verify and what additional collision/ intersection/ contact calls that I would need to make, in order to ensure that the objects dont pass through each other, but get moved as a result of motion of the dynamic trimesh body. Also number of iterations is kept high for precise calculations
Thanks

Also, number of iterations is kept high for precise calculations

Hi,
Trimesh vs Box collision is not implemented yet. How about using a sphere instead? Or 8 compound spheres?

I am sorry, but do you mean Trimesh vs Sphere collision? or approximating the trimesh with spheres? any pointers to do this will be helpful

Sorry. I meant approximating the box with spheres. In that case they would collide. Approximating the trimesh with spheres would work too.
Is the trimesh vertices changing over time?

Yes, thanks for the info. The trimesh is too complex and is also changing over time. I will update this post on how approximating the other object works out

It's been a while, how's it going with that mesh?


feature request: CARGO_TARGET_DIR_PREFIX

If the CARGO_TARGET_DIR environment variable is set, then cargo will use that as the target directory.  However, that variable can't be shared between different workspaces.  Thus, anybody who wants to use it must modify his environment every time he switches workspaces.
It would be better for Cargo to support a CARGO_TARGET_DIR_PREFIX variable that is used to calculate the full target directory and can be shared between all workspaces.  I propose doing this exactly like FreeBSD's ports tree uses the WRKDIRPREFIX variable:

If neither CARGO_TARGET_DIR nor CARGO_TARGET_DIR_PREFIX is set, then Cargo will use ${PWD}/target as the target directory.
If CARGO_TARGET_DIR_PREFIX is set but CARGO_TARGET_DIR isn't, then Cargo will use ${CARGO_TARGET_DIR_PREFIX}/${PWD}/target as the target directory.  If it doesn't exist, then Cargo will create it, along with any missing parent directories.
If CARGO_TARGET_DIR is set, regardless of whether CARGO_TARGET_DIR_PREFIX is, then Cargo will use that for the target directory.

For example:
rustacean@server:~/src/rust/foo$ sudo mkdir /cargo
rustacean@server:~/src/rust/foo$ sudo chmod 1777 /cargo
rustacean@server:~/src/rust/foo$ export CARGO_TARGET_DIR_PREFIX=/cargo
rustacean@server:~/src/rust/foo$ cargo build
...
rustacean@server:~/src/rust/foo$ ls /cargo/home/rustacean/src/rust/foo/target
debug
rustacean@server:~/src/rust/foo$ cd ../bar
rustacean@server:~/src/rust/bar$ cargo build
...
rustacean@server:~/src/rust/bar$ ls /cargo/home/rustacean/src/rust/bar/target
debug

This feature will facilitate the following uses for developers with multiple workspaces:

Sharing source code amongst multiple machines with different OSes or architectures, which each need their own target directories.
Sharing source code via NFS for convenience or backup purposes, but building on local filesystems for speed (storing sources on NFS is plenty fast, but storing objects on NFS is very slow).
Saving storage space by using RAID protection only for source, not objects
Building from read-only source directories
Building and testing from noexec source filesystems

+1 for this feature request. I just noticed how huge the target/ directory can become, seemingly even more so with recent advances in incremental build support (although I haven't compared to the bad old days).
It's a big deal for me for the backup process mentioned above but there is probably one more argument in favor of having something along the lines of CARGO_TARGET_DIR_PREFIX (that I can't see how to implement properly with CARGO_TARGET_DIR) and that is:

Reducing unnecessary write cycles on an SSD. All target/ data can easily go to a ramdisk backed directory.

I started working on this feature, mostly for my own benefit. But in case someone is interested:
For 0.27: https://github.com/d-e-s-o/cargo/commit/05d4f25eff716d67310bc1ecd70df56c5e6f90a2
For HEAD: https://github.com/d-e-s-o/cargo/commit/4ad0efaa7931c756a25f442e91d129eb6d47856c
I can bring this issue to conclusion if there is interest (and some guidance with respect to Windows support). But that probably needs some discussion first, given the proposal state the feature is in (and I am unsure about the exact procedure to go through, as I am new to the project; so that would require some hand holding :D)

I'm still very interested in this feature.  I can't help with Windows, though.  But would you like me to test your branch with my setup?

I'm still very interested in this feature. I can't help with Windows, though. But would you like me to test your branch with my setup?

Sure! More exposure can't hurt.
I am mostly looking for some statement from the Cargo team, though @alexcrichton . Should I just create a pull request and everything is discussed there? I suppose a lagging Windows version will be a problem, so some sort of clarification on that front would be useful.

@alexcrichton does this feature needs a RFC/e-RFC to be accepted? That would be immensely useful to me :)

Yes I suspect this will need at least some discussion beyond what's in this issue before landing, perhaps through an RFC.

can you direct me to the proper avenue for discussing this before I sink time into a RFC document?
internals? zulip? discord?

One conceptual issue I encountered through continued usage is the following: its now possible that multiple users set CARGO_TARGET_DIR_PREFIX, each potentially setting it to the same directory.
I do that for root and my local user user. Let's assume CARGO_TARGET_DIR_PREFIX is /tmp/rust, but that only /tmp exists (not /tmp/rust). Now if I build a project from user first, that may create /tmp/rust/home/user/.... Note here that /tmp/rust is created with user as the owner. Because root (typically) has write access in user created directories everything is fine when root now builds a project whose artifacts reside in, say, /tmp/rust/root/....
But once we swap the order and root builds first, /tmp/rust will be owned by root and user is not able to create /tmp/rust/home in it. While that is expected and logical, it's not a great user experience, I'd argue. I guess we could create directories as world writable? But it seems icky. Haven't found a good solution yet. Perhaps the solution is just to document that behavior, but I see that as last resort.

I think the main thing is not necessarily going with this specific solution, but actually document the problem and try to gather possible solutions.

One conceptual issue I encountered through continued usage is the following: its now possible that multiple users set CARGO_TARGET_DIR_PREFIX, each potentially setting it to the same directory.
I do that for root and my local user user. Let's assume CARGO_TARGET_DIR_PREFIX is /tmp/rust, but that only /tmp exists (not /tmp/rust). Now if I build a project from user first, that may create /tmp/rust/home/user/.... Note here that /tmp/rust is created with user as the owner. Because root (typically) has write access in user created directories everything is fine when root now builds a project whose artifacts reside in, say, /tmp/rust/root/....
But once we swap the order and root builds first, /tmp/rust will be owned by root and user is not able to create /tmp/rust/home in it. While that is expected and logical, it's not a great user experience, I'd argue. I guess we could create directories as world writable? But it seems icky. Haven't found a good solution yet. Perhaps the solution is just to document that behavior, but I see that as last resort.

Yes, @d-e-s-o that's a probably.  The best solution is to set the sticky bit on the prefix directory.  So the first time you created it, chmod 1777 /tmp/rust.  Now, both root and user can happily create subdirectories.

@qmx I suspect internals would probably be best

See also #11156

Closing in favor of #11156 as that has more discussion.  While the title is slightly different, the discussion goes more broad.


Allow owner to approve or disprove oembed content suggested for API

Mirror the user flow for connecting an API to an organization
Consider also if there should be an approval panel that contains both suggested APIs and suggested content

Closing since it is only the API owner who is able to add the content


Concept list does not match all glosses in TULED on EDICTOR

It turns out that the ENGLISH glosses in etc/concepts.tsv, which were directly taken from our Concepticon, where they had been submitted, following the blog post, do only in 428 cases match the concepts in TULED in EDICTOR.

To understand the problem:
from cltoolkit import Wordlist
from pycldf import Dataset
from lingpy import *

wl = Wordlist([Dataset.from_metadata("cldf/cldf-metadata.json")])
conceptsA = []
for c in wl.concepts:
    conceptsA += [s.name for s in c.senses]

conceptsB = [row[2] for row in csv2list("etc/concepts.tsv")][1:]

for concept in [c for c in conceptsB if c not in conceptsA]:
    print(concept)

The result shows the concepts which are in the concept list but not in TULED / EDICTOR:
BABAÇU (Attalea speciosa)
BABY CARRIER
BLUE-AND-YELLOW MACAW (Ara ararauna)
BRAZIL NUT (Bertholletia excelsa)
BRAZILIAN CEDAR (Cedrela odorata)
DAUGHTER OF WOMAN
EMBAUBA (genus Cecropia)
GRIDIRON
HOPLIAS (genus)
INGA (genus)
LARGE-BULLET-ANT (subfamily Paraponerinae)
MOUNTAIN SOURSOP (Annona montana)
PIUM (simuliidae)
RED-AND-GREEN MACAW (Ara chloropterus)
SON OF WOMAN
TAPIOCA
TAYRA (Eira barbara)
WAX
WRISTBAND

Sorry. Just saw: my run fixes this.


docs: add "OWASP API Security Top 10 2023" to Security Guidelines

Needs #8652
Description

add "OWASP API Security Top 10 2023"

Frankly, CI4 offers very few features for API Security.
Checklist:

[x] Securely signed commits
[] Component(s) with PHPDoc blocks, only if necessary or adds value
[] Unit testing, with >80% coverage
[x] User guide updated
[] Conforms to style guide

This is the last PR for v4.4.8.
Review, please.


About the ignoreConflict parameter in the method searchCourse

ignoreConflict - whether or not to ignore course or time conflicting course sections. Note that a section is both course and time conflicting with itself.
Q1: If ignoreConflict = false, does it mean that to filter out those course sections in this semester (indicated by semesterId) having conflicts with the course sections the specific student  (indicated by studentId)  enrolling in?
Q2: If Q1 is true,  whether or not the courseConflict covers previous enrolled courses? In other words, is courseConflict relevant to semester?  For example, if student A enrolled and passed a course B in semester 1, then can A search a course section b belonging to course B in semester 2? And what about the student A fail the course B?
In addition,
Q3: ignoreMissingPrerequisites : whether or not to ignore courses with missing prerequisites.
What is the meaning of missing prerequisite? The courses with null preresquisite?  The courses with prerequisite unmatching with the specific student?

Filter out when ignoreConflict is true instead of false.

does it mean that to filter out those course sections in this semester (indicated by semesterId) having conflicts with the course sections the specific student (indicated by studentId) enrolling in

Yes.

is courseConflict relevant to semester?

Yes.

What is the meaning of missing prerequisite?

The student hasn't pass all the prerequisites of that course.

But in my consideration, ignoreConflict  = true means I should ignore the conflicts, i.e. do not figure out the conflicted courses

ignoreConflict = true means the results should ignore the conflicting courses.


Poll at 1Hz for robot description until it is found.

This commit safeguards against the case where a robot description only becomes available as a ROS parameter after rviz loads. A timer is used to poll for the robot description at 1Hz until it is found. As soon as the robot description is found, then the timer is stopped.

Implemented via d171d8239.


Version 1.1.0 release

Changed

Added support for version v1-21.4.01 of the DocuSign Click API.
Updated the SDK release version.

Closing this and trying to create a new PR.


Error on running stryker on a React Native project

Is your feature request related to a problem? Please describe.
StrykerJS supports React project (cf see there), however it doesn't seems to support React Native ones.
Adding mutation testing on a RN project could improve the quality of testing and code on mobile apps.
Describe the solution you'd like
When running stryker run on a RN project, no errors are thrown. Currently, here is the bug thrown:

@alvessteve thanks for opening this issue. It seems an error to do with copying the file to the sandbox. This is unusual. Can you provide a reproduction repository ?

thank you for the quick response @nicojs. Here is the example i used: https://github.com/alvessteve/stryker-react-native

Thanks, @alvessteve, and sorry it took so long for me to return to you.
Unfortunately, I can't reproduce your issue. With some minor changes, it works for me. See https://github.com/alvessteve/stryker-react-native/pull/1

no worries ! :)
Thank you for having taken the time to check the issue and making the PR. I see much better what changed.


BBMetalTransformFilter is NOT working as expected

First, I would like to thank @Silence-GitHub for creating this library.
The library is working really good.
I'm using BBMetalTransformFilter in a project. but it's not very smooth and takes huge amount of memory that the app get crashed if multiple gestures read at once. I'm reading user's gestures which is applied to BBMetalView. Pan, Pinch and Rotation gestures. What happens is when only a single gesture is allowed to be read it doesn't work smoothly i.e either goes out of the frame or very slow. And when multiple gestures are allowed to be read the memory jumps up very much (more than 1.5GB) that it crashes the app. here is my transformation code :
@objc func handlePan(_ gesture: UIPanGestureRecognizer) {
        let translation = gesture.translation(in: bbMetalView)

        var transform = transformFilter.transform
        transform = transform.translatedBy(x: translation.x, y: translation.y)

        transformFilter.transform = transform
        imageSource.transmitTexture()
    }

    @objc func handlePinch(_ gesture: UIPinchGestureRecognizer) {
        var transform = transformFilter.transform
        transform = transform.scaledBy(x: gesture.scale, y: gesture.scale)

        transformFilter.transform = transform
        imageSource.transmitTexture()
    }

    @objc func handleRotation(_ gesture: UIRotationGestureRecognizer) {
            var transform = transformFilter.transform
            transform = transform.rotated(by: gesture.rotation * .pi / 180)

            transformFilter.transform = transform
            imageSource.transmitTexture()
    }

Any help will be appreciated.
Thank You!

Reset gesture after updating transform.
For pan
gesture.setTranslation(.zero, in: gesture.view)

For pinch
gesture.scale = 1

For rotation, maybe you should calculate manually.
Set transform filter fitSize false. If it is true, the filter will consume a lot of memory when the image scales large.
transformFilter.fitSize = false

To remain the same center while pinching, please try version 1.1.11 and set BBMetalTransformFilter anchorPoint (0.5, 0.5).

Thank You very much for your response @Silence-GitHub .
The memory problem largely got solved. it is not going to 2GB anymore but still when I first touch the image it goes from 115MB to 409MB right away. though it doesn't increases after that.
One more thing I would like to point out and that is if I translate the image at some rotation angle and then translate, it's not translation in the right direction. I guess the transform matrix is not multiplied in correct order.
Thank you @Silence-GitHub for the support you are providing. I really appreciate it.


make kube-proxy.log less verbose.

Currently, kube-proxy log every iptables packet filter rules every 5 seconds, which generates huge amount debugging logs at default logging level. This is mitigating #3943. In #3943, one user also reports an Accept failed too. I couldn't reproduce the issue, but looks like many users are running into this disk full issues caused by too much logging without issues anyway. Will continue reproducing Accept_Failure issue.

LGTM


update llama.cpp and expose onDone callback for LlamaProcessor

there is a bit of conflicting due to updated binding


Can't find ./dist/index.js when ./dist/index.min.js exists

Just built a project that was using pdf2pic, and came across an odd build error.
Error: Cannot find module './dist/index.js'
    at Function.Module._resolveFilename (module.js:548:15)
    at Function.Module._load (module.js:475:25)
    at Module.require (module.js:597:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/my-utility/node_modules/pdf2pic/index.js:3:18)
    at Module._compile (module.js:653:30)
    at Object.Module._extensions..js (module.js:664:10)
    at Module.load (module.js:566:32)
    at tryModuleLoad (module.js:506:12)
    at Function.Module._load (module.js:498:3)

When I look in pdf2pic in node_modules, I see node_modules/pdf2pic/dist/index.min.js, not index.js. Is this intentional and I'm missing some config or is this a bug? It's like the published pdf2pic distribution is broken and it's not looking for the minified version.

Hi, I didn't notice it the time I made changes with the transpiler, a fix has been pushed and published, that should work now. Thanks :+1:


Runtime error introduced via one of the latest changes?

Hi Derek,
I have been getting this bug while running the code via FabSim:
RuntimeError:
local() encountered an error (return code 2)while executing 'ssh -Y -p 22 arindam@localhost '/bin/true || true && /home/arindam/Dropbox/Brunel/FACS/FabSim/FabSim3/localhost_exe/FabSim/results/klaipeda_localhost_1/RUNS/extend-lockdown-1-0.475/klaipeda_localhost_1_extend-lockdown-1-0.475.sh''
The exact command I ran was
fabsim localhost covid19_ensemble:cheshire_east,TS='extend-lockdown',TM='1',cores=1,replicas=1,ci_multipliers=0.3,simulation_period=100
I see this bug since the update to the code about 4 days ago.

Hi Arindam.
Your syntax is actually wrong here. You should use:
flh covid19_ensemble:configs='cheshire_east',TS='uk-forecast',TM='0',cores=1,replicas=1,simulation_period=100,starting_infections=460,job_wall_time=1:00:00,solver=pfacs
You can freely change the other parameters of course, but the first one has to be configs. This is not correct in the current documentation, so I will update this now.

The documentation is now updated. Arindam, would you be able to test this?

The documentation is now updated. Arindam, would you be able to test this?

The error still persists.

Note that I should probably update the TS/TM functionalities such that it triggers different measures.yml files. Perhaps I should rename names like 'uk-forecast' to actual names of measurement yml files?

Yes and yes! That would be very very useful.

Hi Arindam.
Can you please paste in the full output of your command here in the thread, rather than just the tail? Then I will be able to better diagnose the underlying issue.

Hi Derek,
The error with the last part of the output is as follows:
Transport: t 98 p_inf 6.0767680283333435e-06, inf_ext_pas 192321.5, # of infections 5.
98 8/6/2020 1.0 1.0
[382505      9     12   2117     35      0      5      0      0]
total visits: 553873
0 1282.5
[382505      6     14   2118     35      0      0      0      0]
Transport: t 99 p_inf 6.0768312182407525e-06, inf_ext_pas 192321.5, # of infections 2.
99 9/6/2020 1.0 1.0
[382503      8     14   2118     35      0      2      0      0]
/home/arindam/Dropbox/Brunel/FACS/FabSim/FabSim3/localhost_exe/FabSim/results/cheshire_east_localhost_1/RUNS/extend-lockdown-1-0.475/cheshire_east_localhost_1_extend-lockdown-1-0.475.sh: 32: Syntax error: redirection unexpected
Traceback (most recent call last):
File "/home/arindam/Dropbox/Brunel/FACS/FabSim/FabSim3/fabsim/bin/fabsim", line 46, in
sys.exit(fabsim_main.main())
File "/home/arindam/Dropbox/Brunel/FACS/FabSim/FabSim3/fabsim/base/fabsim_main.py", line 150, in main
env.exec_func(*env.task_args, **env.task_kwargs)
File "/home/arindam/Dropbox/Brunel/FACS/FabSim/FabSim3/fabsim/base/decorators.py", line 74, in wrapper
return func(*args, **kwargs)
File "/home/arindam/Dropbox/Brunel/FACS/FabSim/FabSim3/plugins/FabCovid19/FabCovid19.py", line 208, in covid19_ensemble
run_ensemble(loc, sweep_dir, **args)
File "", line 91, in run_ensemble
File "/home/arindam/Dropbox/Brunel/FACS/FabSim/FabSim3/fabsim/base/fab.py", line 1112, in run_ensemble
job_scripts_to_submit = job(
File "/home/arindam/Dropbox/Brunel/FACS/FabSim/FabSim3/fabsim/base/fab.py", line 667, in job
job_submission(dict(job_script=job_script))
File "/home/arindam/Dropbox/Brunel/FACS/FabSim/FabSim3/fabsim/base/fab.py", line 918, in job_submission
run(
File "", line 73, in run
File "/home/arindam/Dropbox/Brunel/FACS/FabSim/FabSim3/fabsim/base/networks.py", line 153, in run
return manual(cmd, cd=cd, capture=capture)
File "", line 73, in manual
File "/home/arindam/Dropbox/Brunel/FACS/FabSim/FabSim3/fabsim/base/networks.py", line 221, in manual
return local(pre_cmd + "'" + manual_command + "'", capture=capture)
File "", line 51, in local
File "/home/arindam/Dropbox/Brunel/FACS/FabSim/FabSim3/fabsim/base/networks.py", line 59, in local
raise RuntimeError(
RuntimeError:
local() encountered an error (return code 2)while executing 'ssh -Y -p 22 arindam@localhost '/bin/true || true &&  /home/arindam/Dropbox/Brunel/FACS/FabSim/FabSim3/localhost_exe/FabSim/results/cheshire_east_localhost_1/RUNS/extend-lockdown-1-0.475/cheshire_east_localhost_1_extend-lockdown-1-0.475.sh''

Ah, could you paste in the contents of the file cheshire_east_localhost_1_extend-lockdown-1-0.475.sh ?
There could be an error there.

I am just checking my local run, and the script is as follows:
no batch system
cd /home/csstddg/FabSim3/localhost_exe/FabSim/results/cheshire_east_localhost_4/RUNS/uk-forecast-0-0.475
/bin/true || true
copy files from config folder
config_dir=/home/csstddg/FabSim3/localhost_exe/FabSim/config_files/cheshire_east
rsync -pthrvz --inplace --exclude SWEEP $config_dir/* .
copy files from SWEEP folder
rsync -pthrvz --inplace $config_dir/SWEEP/uk-forecast-0-0.475/ .
if [ -z "/home/csstddg/facs" ]
then
echo "Please set $facs_location in your deploy/machines_user.yml file."
else
export PYTHONPATH=/home/csstddg/facs:$PYTHONPATH
fi
/usr/bin/env > env.log
current_dir=${PWD##*/}
start_time="$(date -u +%s.%N)"
mpirun -np 4 python3 /home/csstddg/facs/run.py --generic_outfile --location=cheshire_east  --transition_scenario=  --transition_mode=-1  --ci_multiplier=0.475  --output_dir=.  --data_dir=covid_data  --starting_infections=460  --start_date=1/3/2020  --simulation_period=500
end_time="$(date -u +%s.%N)"
elapsed="$(bc <<<"$end_time-$start_time")"
echo "Total Executing Time = $elapsed seconds"
... it seems like the error on your platform happens on the second to last line there.

My recommendation would be to go into the results directory, and start this script manually using ./cheshire_east_localhost_1_extend-lockdown-1-0.475.sh
You'll then initially get the same error probably, but you can then try to fix the syntax on line 32 to figure out which setup will work. Once you have a syntax that works correctly while retaining the functionality, I can then test it on my platform.
If it then works on my platform as well, we can update the template for pfacs, and then fix the problem for good :).

Just add
#!/bin/bash

at the beginning of the script.
I commented out the python execution line to debug and it works there. I have now started running the script with the python execution. I will let you know if it succeeds.

Adding the above-mentioned line to the shell script solves the problem for me. Can you update the template accordingly?

Fixed for localhost using this change: 8ea375de62c1e47770934c45ae2d2d480177c146
No template change needed, I just changed a default config setting :).
Can you try to see if it works?

Nicely done! :)