refactor(batch): Use futures-async-stream to implement MergeSortExchange executor

Signed-off-by: d2lark<EMAIL_ADDRESS>Implement MergeSortExchange using Executor2 trait
PLEASE DO NOT LEAVE THIS EMPTY !!!
Please explain IN DETAIL what the changes are in this PR and why they are needed:

Summarize your change (mandatory)
How does this PR work? Need a brief introduction for the changed logic (optional)
Describe clearly one logical change and avoid lazy messages (optional)
Describe any limitations of the current code (optional)

Checklist

[x] I have written necessary docs and comments
[x] I have added necessary unit tests and integration tests

Refer to a related PR or issue link (optional)
close https://github.com/singularity-data/risingwave/issues/1939

CI is running: https://github.com/singularity-data/risingwave/actions/runs/2267790619

Thanks!


AsciiString.contentEqualsIgnoreCase does not work correctly for AsciiString comparison

Netty Version: master (6c0fef133baa4afce11953110a6947732d87ec8e)
AsciiString.contentEqualsIgnoreCase fails when checking for equality between two AsciiString objects. For example
// returns true, should return false
new AsciiString("foo").contentEqualsIgnoreCase(new AsciiString("bar"));

The issue is due to the following line
I think I've tracked this down to the following commit: https://github.com/netty/netty/commit/ba6ce5449ee852b782dde9a11933f6a09b123e22
Pull request to follow

Fixed by https://github.com/netty/netty/pull/4565


How to enable new UI

There is no search bar and home button after installation like the search bar shown in photos.
Btw
I like your musical taste.
I like Vikram Too.
Arambikkalama?😂

Run spicetify config experimental_features 1 in powershell
and spicetify apply in powershell.
then open experimental features menu and search new home, choose enable center option.
relaunch spotify

run this windows script to install nord spotify without any errors. because i can see some errors from your pic

Btw I like your musical taste. I like Vikram Too. Arambikkalama?😂
Thank you❤ Arambikkalam 😂. Tamil ahh?

It is working now. Thanks for helping out.
Btw Tamil than broo😂❤🔥

When i connected my laptop to my monitor the the title bar seems to be a little bigger than the options below.

Feel free to send be a screenshot

Btw Tamil than broo😂❤🔥
❤

What page ?
Spotify and Spicetify ?
offline or auto update version ?


Add unhealthy message to sdk

Currently game servers send health checks every few seconds and if they stop they become unhealthy. I think an unhealthy method should be added for times when the game server knows it's in a bad state. It should be sent once and the server marked unhealthy.

Interesting idea! Curious though - if you know you are unhealthy, why not call Shutdown() and self terminate?
At least at this stage, that will end up happening anyway. Or are you looking to use the Unhealthy state for something?

With unhealthy you know something has happened and maybe should investigate. I think shutdown should be used when a match is over and the game ended normally.

That's a fair point - but that would mean Unhealthy would show up in the resource state, and the event list - which would only be persistent until the resource got deleted - so not that long? At which point, it's gone.
You may be better off just doing some of your own process logging before Shutting something down, and alerting/introspecting/analysing on the aggregated logs?
Curious - is there precedent for this anywhere else? (i.e. Gamelift, i3d, etc?).
I'm also thinking about visualisations etc - and if you mark it as Unhealthy, it could definitely show up there.
Also curious - what sort of situations would you see this happening in -- wherein you know the gameserver is no longer healthy?

I don't have a specific use case and I you are right that the resource will get deleted right after. Visualisations would be great.

@nikibobi Are we happy to close this one ? I also leaning toward metrics on logging to alert on gameserver failure as this will last longer than kubernetes state.

@Kuqd yes, you are right that a more persistent solution is better.


Port #7106 to master

Ports the fix of #7093 from #7106 to master.
Note that there are some additional changes that were not in #7106, namelly renaming EmitOutput.diagnostics to EmitOutput.declarationDiagnostics to avoid confusion, and making it internal as it is already exposed in getPreEmitDiagnostics.
also some changes to simplify our return code processing in tsc.ts.

:+1:


Change input sequence contract to match JavaScript iterators

Currently, the input sequence is passed in as a function whos contract requires that on invocation either the next character is returned or null to signal the end of the sequence.
We should consider changing this interface to match the Iterator as defined by JavaScript. See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Iteration_protocols for details.
The benefit would be that consumers can use Array.prototype.values() instead of building a custom function. There may be an additional performance benefit as well but I haven't measured that yet.
Thoughts?

Even better: why not inject an array directly? Getting the input item would then only be a lookup in the array instead of a function invocation.


zero-units

Hello!
Is it possible to remove units when a value is 0
from
background-position:0px -94px;

to
background-position:0 -94px;

This is a duplicate of https://github.com/Ensighten/grunt-spritesmith/issues/89, https://github.com/twolfson/spritesheet-templates/pull/43, and https://github.com/twolfson/spritesheet-templates/issues/11.
We suggest that this is entering CSS optimization territory and encourage developers to use another CSS optimization task after spritesmith to handle reducing variable sizes (e.g. 0px -> 0). Here are some tools to evaluate:

https://www.npmjs.com/package/grunt-csso

Wrapper for http://bem.info/tools/csso/

https://github.com/begriffs/css-ratiocinator


D.marin/ktlint

What does this PR do?
Update Ktlint to 0.45.1 and use a dedicated runner image
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #1081 (581817c) into develop (7df131c) will increase coverage by 0.08%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##           develop    #1081      +/-   ##
===========================================
+ Coverage    83.19%   83.26%   +0.08%
===========================================
  Files          272      272
  Lines         9279     9268      -11
  Branches      1494     1488       -6
===========================================
- Hits          7719     7717       -2
+ Misses        1143     1136       -7
+ Partials       417      415       -2

Impacted Files
Coverage Δ

...datadog/android/coil/DatadogCoilRequestListener.kt
100.00% <ø> (ø)

...com/datadog/android/compose/InteractionTracking.kt
73.55% <ø> (ø)

...in/com/datadog/android/glide/DatadogGlideModule.kt
94.74% <ø> (ø)

.../com/datadog/android/ktx/coroutine/CoroutineExt.kt
75.86% <ø> (ø)

...kotlin/com/datadog/android/DatadogEventListener.kt
98.48% <ø> (-0.02%)
:arrow_down:

...n/kotlin/com/datadog/android/DatadogInterceptor.kt
93.67% <ø> (ø)

...atadog/android/core/configuration/Configuration.kt
98.70% <ø> (ø)

...n/com/datadog/android/core/internal/CoreFeature.kt
91.60% <ø> (ø)

...tadog/android/core/internal/net/CurlInterceptor.kt
83.33% <ø> (ø)

.../android/core/internal/net/DataOkHttpUploaderV2.kt
97.62% <ø> (ø)

... and 23 more

Nice job. One quick thought, we might want to remove the ktLint Gradle plugin which mentions a different version of ktLint and might return different reports when ran locally

Indeed, updated


[Compute] vmss create: Add --scale-in-policy

Issue #10949

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[ ] I adhere to the Command Guidelines.

OK. I will add --scale-in-policy to update command.


The connector file is not up to date

Hi, it seems that the .mez file was not recompiled after the last feature was added (https://github.com/pichlerpa/PowerBITrinoConnector/pull/11)
I tried compiling it myself as per README.md, but got this:
 *  Executing task: c:\Users\micha\.vscode\extensions\powerquery.vscode-powerquery-sdk-0.2.3-win32-x64\.nuget\Microsoft.PowerQuery.SdkTools.2.114.4\tools\MakePQX.exe compile

Unexpected exception:
System.IO.FileNotFoundException: Could not find file 'C:\Users\micha\PowerBITrinoConnector\Trino\C%EF%80%BA%EF%81%9CUsers%EF%81%9Cmicha%EF%81%9CAppData%EF%81%9CLocal%EF%81%9Cvscode-sqltools%EF%81%9CData%EF%81%9C.node-runtime'.
File name: 'C:\Users\micha\PowerBITrinoConnector\Trino\C%EF%80%BA%EF%81%9CUsers%EF%81%9Cmicha%EF%81%9CAppData%EF%81%9CLocal%EF%81%9Cvscode-sqltools%EF%81%9CData%EF%81%9C.node-runtime'
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
   at System.IO.Compression.ZipFileExtensions.DoCreateEntryFromFile(ZipArchive destination, String sourceFileName, String entryName, Nullable`1 compressionLevel)
   at MakePQX.Tasks.TaskStash.<>c__DisplayClass2_0.<BuildMezProject>b__0(String oneRelativePath)
   at System.Collections.Generic.List`1.ForEach(Action`1 action)
   at MakePQX.Tasks.TaskStash.BuildMezProject(String nullableProjectDirectory, String directoryName, String fileName)
   at Microsoft.Mashup.MakePQX.Program.<>c__DisplayClass4_1.<Main>b__5()
   at Microsoft.Extensions.CommandLineUtils.CommandLineApplication.Execute(String[] args)
   at Microsoft.Mashup.MakePQX.Program.Main(String[] args)

 *  The terminal process "c:\Users\micha\.vscode\extensions\powerquery.vscode-powerquery-sdk-0.2.3-win32-x64\.nuget\Microsoft.PowerQuery.SdkTools.2.114.4\tools\MakePQX.exe 'compile'" terminated with exit code:<PHONE_NUMBER>.
 *  Terminal will be reused by tasks, press any key to close it

@trymzet you need to open the "Trino" folder within VS for the compilation to work as outlined in step 2.

The compiled MEZ includes now the last changes from https://github.com/pichlerpa/PowerBITrinoConnector/commit/4ef9df47655facbff1c5b0309c8c299f1a3a6788 and is up-to-date.


Make timesteps work in the standard way when Huber loss is used

Tested with SDXL LoRA.
When Huber loss is selected, the sampled timestep is the same for the entire batch. This PR changes the behavior to match what is used for L2 loss.
Instead of passing a scalar huber_c around, turn it into a batch sized Tensor object.

I think we can make some additional changes to more easily integrate Huber loss into the upcoming SD3/Flux work:

Split method get_timesteps_and_huber_c to separate timestep sampling from Huber "delta" calculation, this would simplify getting the Huber values in the Flux trainer later.
Add a explicit message stating that SNR schedule is not supported in models where this concept does not apply

@kohya-ss Should this be merged as-is or can I implement the above changes?

After spending an afternoon going thru a rabbit hole, I concluded that the current Huber loss code is simply incorrect.
This is the textbook definition of Huber loss (from wikipedia):

This is a piecewise defined function. What we have in the code is:
loss = 2 * (torch.sqrt((model_pred - target) ** 2 + huber_c**2) - huber_c)

Which is not the same and appears to be an approximation, at best. The code seems to be identical to a version that exists in the diffusers package, which is probably the source.
Looking at the PyTorch internal implementation we have:
z = (input - target).abs()
loss = torch.where(z < delta, 0.5 * z * z, delta * (z - 0.5 * delta))

It matches the textbook definition.
I've been getting some inconsistent results in Flux using Huber loss when following the recommendations in the original paper. I suspect this might be one of the causes.
Smooth L1 loss seems to have the same problem outlined above.
I am currently testing changes to use the same logic as PyTorch currently does.

After some additional measurements I think the current formulation and defaults for Huber schedule are not suitable for use in Flux.
The primary reason being that mean latent loss term (and variance)  is much higher than what we find in prior models (like SDXL).
A default like huber_c=0.1 is too low for either constant or exponential schedules. A quick measurement of typical average latent abs(predicted - target) values gave me around ~0.5 (std deviation ~0.4). This means a Huber delta of 0.1 will result in applying a MAE-like estimation to most latent values.
If I understand the math correctly, given that MAE grows linearly this means we'll get smaller gradient magnitudes, on average, when compared to MSE (which has quadratic behavior). As a result the learning gets severely dampened.  I've done a few test runs with different huber_c values and could see a correlation between the parameter value and the effectiveness of the training over a preset number of steps.
When it comes to the exponential schedule we have an additional problem. The current formulation (per the paper) is:
delta = exp(log(delta_0) * t)

Where delta_0 is the huber_c parameter and t is the sampled timestep (normalized to [0,1]). This means delta has an upper bound of 1.0 (when delta_0 <= 1.0) and this leads to a problem similar to the constant schedule case.
We need a way to control the upper bound of this function, probably with an additional s parameter, like delta = s * exp(log(delta_0) * t) or by shifting t like delta = exp(log(delta_0) * (t + s)).

Thank you for this PR.

@kohya-ss Should this be merged as-is or can I implement the above changes?

I think this PR can be merged as is.

After spending an afternoon going thru a rabbit hole, I concluded that the current Huber loss code is simply incorrect.

I don't fully understand the mathematical background, but kabachuha, the author of #1228 said "Pseudo-Huber Loss" in huggingface/diffusers#7527, so I think this difference is intentional.
Are the results significantly different and can we be sure that Wikipedia's implementation is better?

In the last few days I've been testing both approaches, both seem to work well enough. The the problems I was facing (in Flux testing) seem to be related to the current Huber schedules and default values, which are inadequate for the new model. I have another set of proposed changes but I'll leave that for a later PR.


KAFKA-5378: Return LSO in FetchResponse plus some metrics

cc @ijuma @junrao Let me know if you think the metric changes are reasonable.

@hachikuji : Thanks for the patch. LGTM. I will let you merge it.


[aes/rtl] Fix AscentLint lint errors and an Xcelium compile error

This PR fixes a large series of lint errors in AscentLint and a compile error in Xcelium introduced with the recent switch to the
multi-rail FSM implementation.
This fixes lowRISC/OpenTitan#9608.

Thanks a lot @mwbranstad for checking this out. Glad to hear it solves the issues. Yes indeed, the patch is much bigger than I was hoping for. Partially because with the first version some new lint errors in Verible lint occured. I will merge this once CI passes.


Error in create_policy Execution Due to Incorrect tenant_id Key Extraction in schema.rb

Description:
This issue addresses an issue where an error occurs when executing the create_policy statement after specifying tenant_id as a string and running the generated schema.rb.
Environment:

Ruby 3.3.5 (2024-09-03 revision ef084cc8f4) [arm64-darwin23]
Rails 7.1.4
PostgreSQL 16.4

Issue:
When creating a tenant_id as a bigint, the result of "qual" is:
(tenant_id = (NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text))::bigint)

When creating a tenant_id as a varchar, the result of "qual" is:
((tenant_id)::text = ((NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text))::character varying)::text)

In this PR, code has been added to extract the key for tenant_id from this string. However, in the case of varchar, it retrieves (tenant_id)::text, resulting in the following output in schema.rb:
create_policy "users", partition_key: "(tenant_id)::text"

When this schema.rb is loaded, an error occurs at the create_policy statement:
bin/rails aborted!
(tenant_id)::text column is missing in users

Resolution:
The main purpose of the changes in this PR is to modify the key name for tenant_id. Given that no special specification is required when creating a policy, the following output in schema.rb should suffice:
create_policy "users"

Fix code
diff --git a/lib/activerecord-tenant-level-security/schema_dumper.rb b/lib/activerecord-tenant-level-security/schema_dumper.rb
index a258c3b..9c94232 100644
--- a/lib/activerecord-tenant-level-security/schema_dumper.rb
+++ b/lib/activerecord-tenant-level-security/schema_dumper.rb
@@ -39,7 +39,7 @@ module TenantLevelSecurity
     private

     def convert_qual_to_partition_key(qual)
-      matched = qual.match(/^\((.+?) = /)
+      matched = qual.match(/^\(*([a-zA-Z0-9_]+)(?:\)::[a-zA-Z0-9_]+)*\s*=/)
       # This error can occur if the specification of the 'tenant_policy' in PostgreSQL
       #   or the 'create_policy' method changes
       raise "Failed to parse partition key from 'pg_policies.qual': #{qual}" unless matched

I have also added the code for verification.
# Migration files
# --------------------------------------------------------
# db/migrate/20240918004701_create_tenants.rb
# --------------------------------------------------------
# class CreateTenants < ActiveRecord::Migration[7.1]
#   def up
#     create_table :tenants, id: false do |t|
#       t.string :id, limit: 26, primary_key: true
#       t.string :name
#     end
#   end

#   def down
#     drop_table :tenants
#   end
# end
#
# --------------------------------------------------------
# db/migrate/20240918092205_create_users.rb
# --------------------------------------------------------
# class CreateUsers < ActiveRecord::Migration[7.1]
#   def up
#     create_table :users, id: false do |t|
#       t.string :id, limit: 26, primary_key: true
#       t.references :tenant, null: false, foreign_key: true ,type: :string
#       t.string :email
#       t.string :name
#     end
#     create_policy :users
#   end

#   def down
#     drop_table :users
#   end
# end
#
# --------------------------------------------------------
# schema.rb
# --------------------------------------------------------
# ActiveRecord::Schema[7.1].define(version: 2024_09_18_092205) do
#   # These are extensions that must be enabled in order to support this database
#   enable_extension "plpgsql"

#   create_table "tenants", id: { type: :string, limit: 26 }, force: :cascade do |t|
#     t.string "name"
#   end

#   create_table "users", id: { type: :string, limit: 26 }, force: :cascade do |t|
#     t.string "tenant_id", null: false
#     t.string "email"
#     t.string "name"
#     t.index ["tenant_id"], name: "index_users_on_tenant_id"
#   end

#   add_foreign_key "users", "tenants"

#   create_policy "users"
# end

class TestSchemaDumper
  include TenantLevelSecurity::SchemaDumper

  def self.convert_qual_to_partition_key(qual)
    new.send(:convert_qual_to_partition_key, qual)
  end
end

int_qual = "(tenant_id = (NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text))::bigint)"
string_qual2 = "((tenant_id)::text = ((NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text))::character varying)::text)"

# Usage examples
int_result = TestSchemaDumper.convert_qual_to_partition_key(int_qual)
print("IntType [#{int_result == 'tenant_id'}] result: #{int_result}\n")
string_result = TestSchemaDumper.convert_qual_to_partition_key(string_qual2)
print("StringType [#{string_result == 'tenant_id'}] result: #{string_result}\n")

Run results
IntType [true] result: tenant_id
StringType [true] result: tenant_id

PR https://github.com/kufu/activerecord-tenant-level-security/pull/25

Thank you for reporting this.
This change makes sense, but I understand it's a compatibility issue. Instead of applying this fix, you can also migrate your policies by following the steps below.
https://github.com/kufu/activerecord-tenant-level-security/pull/16#issuecomment-1503111326
This is the best option as it also addresses the issue of no good execution plan being chosen.
If we can easily fix the issue of (tenant_id)::text being mistakenly selected as the partition_key, I would not be opposed to merging #25. However, as pointed out in https://github.com/kufu/activerecord-tenant-level-security/pull/25#discussion_r1808028056, the current logic for extracting the partition key is somewhat ambiguous. Given this, it may be better to drop support for the old policy and return a more clear error message.
What do you think about this, and if there are any reasons why you can't migrate to the new policy?

I have reviewed the relevant PR.
As a premise, we are building a new service and are using "character varying(26)" for the tenant_id.
I confirmed that, by setting AlterPolicies in the PR to
TENANT_ID_DATA_TYPE = "character varying(26)"

the following output SQL is executed:
ALTER POLICY tenant_policy ON task_queues
  USING (tenant_id = (NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text))::character varying(26))
  WITH CHECK (tenant_id = (NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text))::character varying(26));

Before applying this to everything, I plan to directly execute the above SQL on PostgreSQL.
The policy definition before execution:
\d users
-- omitted --
POLICY "tenant_policy"
  USING (((tenant_id)::text = ((NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text))::character varying)::text))
  WITH CHECK (((tenant_id)::text = ((NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text))::character varying)::text))

The policy definition after execution:
\d users
POLICY "tenant_policy"
  USING (((tenant_id)::text = NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text)))
  WITH CHECK (((tenant_id)::text = NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text)))

As a result, the policy is set with (tenant_id)::text, and when dumped, schema.rb outputs create_policy "users", partition_key: "(tenant_id)::text".
Am I misunderstanding something in relation to this PR? Do we expect any changes in the output of schema.rb as a result of this new policy migration?

Hmm, that seems like strange behavior.
There seems to be a bit of an issue with the implementation of AlterPolicies, but putting that aside, queries that perform a cast to character varying(26) seem to always get cast to text in PostgreSQL.
activerecord_tenant_level_security_test=# CREATE POLICY tenant_policy ON string_employees AS PERMISSIVE FOR ALL TO PUBLIC USING (tenant_id = NULLIF(current_setting('tenant_level_security.tenant_id'), '')::character varying(26)) WITH CHECK (tenant_id = NULLIF(current_setting('tenant_level_security.tenant_id'), '')::character varying(26));
CREATE POLICY
activerecord_tenant_level_security_test=# \d string_employees
                  Table "public.string_employees"
  Column   |         Type          | Collation | Nullable | Default
-----------+-----------------------+-----------+----------+---------
 tenant_id | character varying(26) |           |          |
Policies (forced row security enabled):
    POLICY "tenant_policy"
      USING (((tenant_id)::text = ((NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text))::character varying(26))::text))
      WITH CHECK (((tenant_id)::text = ((NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text))::character varying(26))::text))

We should start by investigating whether this case would cause estimation problems and why such a cast is occurring.

Testing tenant_id as integer, character varying(26), and text
Integer Case
CREATE TABLE IF NOT EXISTS sample_integer (
  tenant_id integer,
  id integer
);

-- Add 1000 rows for tenant_id = 1
INSERT INTO sample_integer (tenant_id, id) VALUES (1, (generate_series(1,1000)));

-- Add 1000 rows for tenant_id = 2
INSERT INTO sample_integer (tenant_id, id) VALUES (2, (generate_series(1,1000)));
ANALYZE sample_integer;

EXPLAIN SELECT * FROM sample_integer
WHERE tenant_id = NULLIF(current_setting('tenant_level_security.tenant_id'), '')::integer;

Result:
                                          QUERY PLAN
----------------------------------------------------------------------------------------------------
Seq Scan on sample_integer (cost=0.00..54.00 rows=1000 width=8)
  Filter: (tenant_id = (NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text))::integer)
(2 rows)

Character varying(26) Case
CREATE TABLE IF NOT EXISTS sample_char (
  tenant_id character varying(26),
  id integer
);

-- Add 1000 rows for tenant_id = "1"
INSERT INTO sample_char (tenant_id, id) VALUES ('1', (generate_series(1,1000)));

-- Add 1000 rows for tenant_id = "2"
INSERT INTO sample_char (tenant_id, id) VALUES ('2', (generate_series(1,1000)));
ANALYZE sample_char;

EXPLAIN SELECT * FROM sample_char
WHERE (tenant_id)::text = ((NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text))::character varying(26))::text;

Result:
                                          QUERY PLAN
----------------------------------------------------------------------------------------------------
Seq Scan on sample_char (cost=0.00..49.00 rows=1000 width=6)
  Filter: ((tenant_id)::text = ((NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text))::character varying(26))::text)
(2 rows)

Text Case
CREATE TABLE IF NOT EXISTS sample_text (
  tenant_id text,
  id integer
);

-- Add 1000 rows for tenant_id = "1"
INSERT INTO sample_text (tenant_id, id) VALUES ('1', (generate_series(1,1000)));

-- Add 1000 rows for tenant_id = "2"
INSERT INTO sample_text (tenant_id, id) VALUES ('2', (generate_series(1,1000)));
ANALYZE sample_text;

EXPLAIN SELECT * FROM sample_text
WHERE (tenant_id)::text = NULLIF(current_setting('tenant_level_security.tenant_id'), '')::text;

Result:

                                          QUERY PLAN
----------------------------------------------------------------------------------------------------
Seq Scan on sample_text (cost=0.00..44.00 rows=1000 width=6)
  Filter: (tenant_id = NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text))
(2 rows)

Omitting Explicit Casting for text

EXPLAIN SELECT * FROM sample_text
WHERE tenant_id = NULLIF(current_setting('tenant_level_security.tenant_id'), '')::text;

Result:

                                          QUERY PLAN
----------------------------------------------------------------------------------------------------
Seq Scan on sample_text (cost=0.00..44.00 rows=1000 width=6)
  Filter: (tenant_id = NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text))
(2 rows)

Results
In terms of cost, the sequence was: text < character varying(26) < integer.
Summary
PostgreSQL's current_setting function returns a text value, as shown by the following command:
SELECT pg_typeof(current_setting('tenant_level_security.tenant_id'));

Result:
pg_typeof
-----------
text
(1 row)

Given that the return type of current_setting is text, if we want to minimize the casting cost in comparisons (e.g., when comparing the value returned from current_setting('tenant_level_security.tenant_id')), it is more efficient to have the tenant_id columns in the relevant tables defined as text.
According to the PostgreSQL documentation (https://www.postgresql.org/docs/current/datatype-character.html), there is no performance difference between different character types like character varying(n) and text.
However, actual performance can vary based on factors such as:

Data distribution
Indexing
The actual number of rows

Taking all factors into consideration, it seems preferable to use text for tenant_id in cases where the tenant ID is represented as a string.

Additional Information
We have updated the Tenants table and all tenant_id columns to use the text data type and have confirmed that everything works as expected.
\d users
-- omitted --
POLICY "tenant_policy"
  USING ((tenant_id = NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text)))
  WITH CHECK ((tenant_id = NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text)))

Even without this PR, since the type of current_setting and tenant_id are the same, there is no need for explicit type conversion, and the output of schema.rb is now correct.
EXPLAIN SELECT * FROM sample_text
WHERE tenant_id = NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text);

Result:
                                          QUERY PLAN
----------------------------------------------------------------------------------------------------
Seq Scan on sample_text (cost=0.00..44.00 rows=1000 width=6)
  Filter: (tenant_id = NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text))
(2 rows)

The execution plan remains unchanged as tenant_id is now defined as text.
We are planning to continue using tenant_id defined as text in the current version. While this PR might be necessary for cases where tenant_id is defined with a string type other than text, we believe it is unnecessary when using the text data type.
Thank you very much for all your support.

While this https://github.com/kufu/activerecord-tenant-level-security/pull/25 might be necessary for cases where tenant_id is defined with a string type other than text, we believe it is unnecessary when using the text data type.

Yeah, at this point, the definitely better solution is to use the text data type.
Whether or not we should merge #25 depends on whether or not we should allow types like character varying(26) in this gem. If it is unavoidable to cast the left side as (tenant_id)::text, PostgreSQL may misestimate the row count and may not choose a better execution plan. See also https://tech.smarthr.jp/entry/2024/01/18/110929 (Japanese)

I checked the linked page (I'm Japanese, so I'm more comfortable with Japanese^^). It seems that when using text, bigint, or uuid, the policy conditions are set in a way that avoids casting on the left side. However, for character varying, even if it is defined like this:
ALTER POLICY tenant_policy ON users
USING (tenant_id = (NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text))::character varying(26))
WITH CHECK (tenant_id = (NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text))::character varying(26));

It gets internally converted to:
POLICY "tenant_policy"
  USING (((tenant_id)::text = ((NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text))::character varying(26))::text))
  WITH CHECK (((tenant_id)::text = ((NULLIF(current_setting('tenant_level_security.tenant_id'::text), ''::text))::character varying(26))::text))

So, if you're going to use a string type, it's wise to avoid character varying. If someone is working in an existing environment where the type is already set, it might be helpful to inform them of this behavior.

Whether or not we should merge #25 depends on whether or not we should allow types like character varying(26) in this gem.

Considering that we were able to identify this issue, I believe that not applying this PR  could also be a valid decision


[feature request] battery full border color.

Hi.
I like this repository a lot, and I am willing to help with this feature request.
I would like to add a color option for the border when the battery is full.
However, I am not sure how to test those changes in my live qtile session and thus I am not sure how to make sure the changes take effect.
If this idea sounds good, would you mind describing or linking to a description on how to change and test this lib?

It's certainly possible to do.
You'd need to add some new parameters to defaults, one for the border colour and one to set the level for treating the battery as "full".
Then, you just need to add some logic to this section to check whether the battery is full:
https://github.com/elParaguayo/qtile-extras/blob/159eb19b9e796b7b685c8806c40cca709ed25f59/qtile_extras/widget/upower.py#L300-L304

Glad to hear a positive response.
What are the best practices for developing and testing this module? Just run pip install . -e in the repo?

Each to their own. I use a virtual environment linked to my development versions of qtile and qtile-extras and I run it in a separate tty.


dotnet publish broken because dotnet-ef is no longer part of sdk since 3.0

Entity Framework SQL script generation is part of the publish process of .net core applications. This is now broken since 3.0 because dotnet-ef is no longer part of the sdk.
The sql script generation target is defined in Microsoft.NET.Sdk.Publish.TransformFiles.targets file in the SDK. It uses GenerateEFSQLScripts msbuild task which underneath executes dotnet ef.
Steps to reproduce
Create a new project. Add a db context. Modify the project to include:
<ItemGroup>
  <EFMigrations Include="FullName.Of.DbContext" />
</ItemGroup>

Then run dotnet publish. It fails with Entity Framework SQL Script generation failed.

Further technical details
EF Core version:
Database provider: (e.g. Microsoft.EntityFrameworkCore.SqlServer)
Target framework: (e.g. .NET Core 3.0)
Operating system:
IDE: (e.g. Visual Studio 2019 16.3)

@ArturDorochowicz To publish with EF, please install the global tool first.


Update fido2-compatibility.md

Formatting of OS names to be consistent and match vendor stylisation. Changed abbreviation for Azure Active Directory from "Azure AD" to "AAD" as this is what is used within the table immediately below.

@theonlycoder : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

Hi @theonlycoder . Thanks for you contribution. "Azure AD" is the correct term, so we have updated the table accordingly and changed the capitalization of "macOS" as well. I am closing this PR but the changes will be reflected on the page soon via an internal update.

#please-close


[R-301] make llm and embeddigns required

currently we use a lot of default llms - this makes Ragas very hard to change. We need to make all the llms and embeddings required so that users explicitly pass them
From SyncLinear.com | R-301

100% agree. There have been a lot of issues opened regarding this problem and the issues its causing that are preventing people from producing testsets. I believe we should remove all the default llms and require users to pass in their llms/embeddings. I am happy to help in this effort, but would like to talk to a maintainer about the vision going forward.

hey @hunter-walden2113 definetly - this is my cal cal.com/jjmachan/huddle - feel free to book some time there. Lookin forward to chatting 🙂

hey @hunter-walden2113 while this PR is would help a lot - it will also break a lot of code we have now. So we are putting this on pause and will take this up before v0.3


Fluent API and TestRule improvements

Hi guys,
here are some improvements into the direction, which has been described by @berndruecker. I tried to change as little code as possible to allow for needed modifications.
Some general remarks / questions:

I added commons.lang in order to get a standard builder interface (I believe you use it without it).
Using ThreadLocal to store the current Engine instance prooved successfully in bpm.assert
The general test code is more compact
It could be reasonable to create a getter for the engine inside the DMNEngineRule
Mixing FluentInstance with FluentBuilder seems a little confusing to me (see your withContext method). What is the reason to use the builder pattern here and not to work on the FluentInstance of the DmnEngineAssertionContext directly?
I just added the parameterless decision() method, but I believe decision(id) is also an interesting option, if multiple decisions can be parsed from the same decisionResource
Currently, static assertions is initilized inside of the DmnEngineRule, but it could be a better idea to separate these concerns by creating a ChainRule with DmnEngineRule as innerRule.
Before changing your code, I sketched an API of my choice and came to different Assertion classes. My choice was to create fluent classes around DmnEngine, DmnDecision and DmnDecisionResult. (Your choice is DmnEngine, DmnDecisionResult, DmnDecisionOutput and DmnDecisionOutputEntry). I believe it is a better choice to implement smarter Conditions working on DmnDecisionOutput and DmnDecisionOutputEntry and avoid too many fluent assertion classes - you don't need to rebuild the API hierarchy by the fluent instance 1:1.

Wow, great, thanks!
A note on  commons.lang:
we should not have that as a runtime dependency since the dmn engine (same as the bpmn engine) will be used in a shared classloader (when deployed along with a shared engine) and it may result in conflicts with user / app server libs

Hi Simon,
thanks for your pull request and ideas. But as Daniel already explained I don't want to add a dependency on commons lang to the engine either.
However I really appreciate your input regarding testing and will take this as a starting point when I rewrite the engine. Just to let you know I currently don't work on the DMN engine itself. The current state is an early prototype to evaluate some ideas. It can actually evaluate some sort of DMN but it isn't to be expected that this code will actually be shipped as the first alpha of the camunda DMN engine. Currently I'm working on the integration of this prototype in the camunda BPM platform, which will give us more insights what kind of API is required by this integration. And after that is finished I will return to the DMN engine and try to sketch and implement a more reasonable API which also includes a user friendly test infrastructure.
This should not discourage you to submit further suggestions how to improve the engine and the API.  As I really value any feedback on this topic. Especially from a usability perspective.
Cheers,
Sebastian

Hi Sebastian,
My fault with commons.lang3, I just removed it. Do you have an idea of a timeframe, when you expect first implementations in the BPM platform?
Are you interested in alternative assertion implementation to show you the different cut of Fluent Instances?
Kind regards,
Simon

Hi Simon,
currently there is already a integration of DMN as a script language in the platform. So you can reference a DMN resource and execute it as a script task. I now will add functionality to use a Business Rule Task in the same way you can use Call Activities and Process/Case Tasks to reference a decision by key and version. I plan to finish the first version of this integration during the next week. But no guarantee on this.
Of course I'm interested in ideas how an user friendly testing approach can be implemented.
Cheers,
Sebastian

Hi Simon,
I will close this pull request for now. But I will use it as reference if I ever find time to work on the testing again. Nevertheless thanks again.
Cheers,
Sebastian


API for usages by VM family, Workspace & Compute

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[x] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[x] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[x] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

New Usage API with detailed breakdown of usage by VM Family, Workspace and Compute

Added a new API usagesbyvmfamily
Added a new defintion UsageByVMFamily extending an existing Usage definition, with some new properties
Added new example for the API

Validation
{ message: 'Semantically validating  specification\machinelearningservices\resource-manager\Microsoft.MachineLearningServices\stable\2018-11-19\machineLearningServices.json:\n',
level: '\u001b[32minfo\u001b[39m' }
{ message: 'No Errors were found.',
level: '\u001b[32minfo\u001b[39m' }

Automation for azure-sdk-for-python

Automation for azure-sdk-for-ruby

Can one of the admins verify this patch?

Automation for azure-sdk-for-js

Automation for azure-sdk-for-go

Automation for azure-sdk-for-java

This swagger isn't referenced in the README.md file, can you please add it?

Please also look at the model validation failures for operation ID MachineLearningCompute_Update.

Is this to be replaced by PR: https://github.com/Azure/azure-rest-api-specs/pull/6173?

This PR is not needed any more. removing ARM labels. The owner will abandon this one.

Closing per comments.

Hi, @nkalpana. The PR has be closed for a long time and it's related branch still exist. If no further used for over 14 days, I will delete this related branch. Please tell me if you still need this branch.

Hi, @nkalpana. The PR has be closed for a long time and it's related branch still exist. Please tell me if you still need this branch or i will delete it in 14 days.


How to get 'sbert_x.pt' and other files for new dataset ?

If I want to train model on other dataset, how can I get model parameter file such as 'sbert_x.pt' in the dataset, it seems that there are no code for this.

Thank you for your reply, but what is the input text template for embedding? I think this is different from the paradigm for Q&A. I have tried some, but it doesn't work well.

Hi,
May I ask how one would obtain the .jsonl files? Also the file processed_data.pt for a new dataset?
Thank you for your time.

Hi, due to variations in the raw data formats across different datasets, we don't have a single unified function for generating processed_data.pt. To create processed_data.pt for new datasets, you only need to generate a Data instance in PyG format, ensuring that edge_index is included in this instance.  And ensuring data.label_texts to include all label name, data.raw_texts to include node text feature if you want to train on node description task.
In general, we follow the guidelines from this repo to generate the edge_index.
To create the *.jsonl file, the main task is to generate the node sequence that represents the structure surrounding each node using template in *.jsonl. You can use our get_fix_shape_subgraph_sequence_fast function in utils/data_process.py to generate the node sequence.

After obtaining the processed_data.pt, sampled_2_10_test.jsonl, sampled_2_10_train.jsonl, and sampled_2_10_val.jsonl files for a new dataset, could you please let me know what additional steps I should take to run experiments in the "single focus" setting for the node classification task on these datasets?

If I want to train model on other dataset, how can I get model parameter file such as 'sbert_x.pt' in the dataset, it seems that there are no code for this.

Hi, have you solved this problem? I also want to know what text is used for embedding.
Thanks!


Can't reply/quote a message sending a file

In both Telegram and WhatsApp, if I try to reply/quote a message sending a file, the file is sent, but there's no quote.
nchat-5.1.13

Hi @fulalas - thanks for reporting an issue. This should be addressed by above commit / v5.1.29.


Introducing Amazon S3 shuffle in AWS Glue / AWS Big Data Blog

URL: https://aws.amazon.com/blogs/big-data/introducing-amazon-s3-shuffle-in-aws-glue/
Review (1-2 sentences): Good explanations of how shuffle works, how it uses local disks, how to track it in AWS Glue UI, what problems we can potentially have and how to escape it.

Published in Digest #14


Upgrade Key Module

Custom Documentation:

[ ] The purpose of the module
[ ] Explanation of the real world users and their role/interactions with the module
[ ] Key logic, processes, or assumptions that happen within the module
[ ] Details on how a module easily integrates with other associated modules

Rust Docs:

[ ] Available storage items and what they hold
[ ] Public Functions
[ ] Internal Functions

upgrade-key should be removed from SRML

Pull request to remove this module is here:
https://github.com/paritytech/substrate/pull/2018


Create New Branch feature/head from develop

Create a new branch feature/head from the develop branch.

Create a styles.css file in the project's root directory and add the provided styles.

Include the styles by adding the provided code snippet inside the <head></head> section.

I have created a new branch feature/head from the develop branch and made the following changes:

Added the 'styles.css' file to the project's root directory and included the provided styles.

Once the changes were completed, I merged the feature/head branch into the develop branch.


Drop Node v6 and v11, add Node v12

v6 ended in April 2019.
v8 will end soon on June 1, 2019.
https://github.com/nodejs/Release

Also "node": ">=0.10.0" in package.json is still correct?
https://github.com/TehShrike/deepmerge/blob/4177f6cb791a33116aa39945eeaccadc76d6add9/package.json#L20-L22

That engines is not correct.  In the past I think it was used as an awkward stand-in for "we compile to ES5"


Chore/status site title

close #8.
close #4.

close this in favor of https://github.com/ninetydays/Upptime/pull/9


Write down rules for patching training frameworks

We have rules for submitting training results using patched frameworks. Can we write them down clearly?

I believe this is handled by the existing availability rules.
Patch is a sw component. If it's public, versioned, and supported it's
Available. If it's not, it's not.
On Tue, Nov 3, 2020 at 7:16 AM David Kanter<EMAIL_ADDRESS>wrote:

Assigned #62 https://github.com/mlperf/policies/issues/62 to
@petermattson https://github.com/petermattson.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/mlperf/policies/issues/62#event-3953387970, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AIIVUHISITQ7ZVXNLSPERTTSOANEDANCNFSM4TI34EOA
.

shall we close this? @TheKanter

Yes, let's close.


will this model recognizes line text , if so , how to use this model for line htr?

could you reply me on this?

Hi! This model performs recognition only at the word level. For line HTR, you will need to first perform line detection and then use a text detection algorithm to segment the line into individual words. For instance, you can explore Faster R-CNN. After this, you can proceed with AttentionHTR for word recognition.

Thank you very much , for your response.
On Fri, Mar 10, 2023 at 2:58 PM Ekta Vats @.***> wrote:

Closed #6 https://github.com/dmitrijsk/AttentionHTR/issues/6 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/dmitrijsk/AttentionHTR/issues/6#event-8716334162, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AKMEC7H5CTK7ZMTQLLLEQXDW3LX2JANCNFSM6AAAAAATVDR5UE
.
You are receiving this because you authored the thread.Message ID:
@.***>


Prefer shell built-in alias rather than wrapped script

Because of zsh completions don't run on wrapped script(Anyway bash doesn't suggest completions even through aliases...). And writing wrapped script for all aliases is an annoy task.
And I can drop fish to simplify the task if I need. I didn't use fish in these years. I can keep fast zsh in these days.
ref: https://github.com/kachick/times_kachick/issues/184, GH-819, GH-173

Several build log as https://github.com/kachick/dotfiles/pull/924, building fish completions taking longtime. I wish this issue also makes better them ...


Error Uploading Branding Image for Agency

 Issue by demory
Wednesday May 02, 2018 at 11:59 GMT
Originally opened as https://github.com/catalogueglobal/datatools-ui/issues/98

Error when trying to upload PNG from computer:

Image taken from https://www.centro.org/images/default-source/logos/centro-header-logo-larger.jpg?sfvrsn=0

 Comment by landonreed
Thursday May 03, 2018 at 22:45 GMT

@demory, can you confirm that this is still occurring for you with the latest commits?  It seems to work fine locally for me.

 Comment by landonreed
Monday May 07, 2018 at 18:58 GMT

Fixed in https://github.com/catalogueglobal/datatools-server/commit/cf144d76b7db69690e7030288998aea99ea30f6e and https://github.com/catalogueglobal/datatools-server/commit/6cd9a76b1231944a09961740c9eca3d9dab63459


npm install -g machinomy [fails]

A bunch of unmet peer dependencies
├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>(git+https://github.com/ukstv/node-homedir.git#c12f20b3e0b0f2cdf745cfda241ef3702c098098)
│ └─┬<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>(git+https://github.com/frozeman/bignumber.js-nolookahead.git#57692b3ecfc98bbdd6b3a516cb2353652ea49934)
├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>└── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.

The issue was discussed with @vans163 in Gitter.
As a result - created FAQ wiki section.


Add Support for WASM Exceptions

There are plans to add support for exceptions in WAMR. Are there any plans to add support to the WASI-SDK tool chain to support Native WASM Exceptions?
(edit: fix link)

The rough plan is to look at Emscripten's port of libunwind to see if it can be either ported to upstream LLVM, or if not, ported to wasi-sdk. I don't know of anyone working on this yet.
It's also worth noting that Wasm Exceptions are not yet standardized; currently the proposal is in phase 3.

As Dan mentioned, the easy part is enabling exceptions in the compiler (e.g. passing -fwasm-exceptions).   The more compex/nuanced part is getting libc++abi/libunwind configured correctly.
To see that current differences from upstream that were made in emscripten you can take a look here: https://github.com/emscripten-core/emscripten/blob/main/system/lib/libcxxabi/readme.txt.  Specifically check out the link at the end that shows you the diffs from upstream llvm 16: https://github.com/llvm/llvm-project/compare/llvmorg-16.0.4...emscripten-core:emscripten-libs-16

Whooha...  Rockstar's both of you, and I've got some reading to do. Thanks for the pointers. Let me take a look.

There's also a draft PR with initial support for this in #198, which you may be interested in.

I have a plan to upstream the current libc++abi/libunwind changes to the upstream LLVM. I think it can happen within a couple months if having this is a priority; the timeline can depend on the receptions from the reviewers though.
By the way there is a discussions going on (https://github.com/WebAssembly/exception-handling/issues/280) which can change the spec itself. I don't think the library side will change much with this though.

Thank you for the wait. Wasm EH's libcxxabi/libunwind changes have now been upstreamed:
https://github.com/llvm/llvm-project/commit/e6cbba749490a20127359a3fbd05d8db7faef535
https://github.com/llvm/llvm-project/commit/058222b2316615194c089f2bc68d11341f39d26e

Just wanted to check, would WASM exceptions make sense for implementing C setjmp / longjmp (i.e., how postgres uses them to implement exceptions), or are they too different and only make sense with language-native exceptions like in C++? If the latter, is there currently no plan that would be able to support setjmp / longjmp in WASI?

I think you should be able to lower SjLj to exceptions.

Indeed, wasm exceptions is how we've always envisioned setjmp/longjmp would work.

Thanks for confirming! I implemented stack unwind for wazero
https://github.com/tetratelabs/wazero/pull/1808
and look forward to trying it out with wasi SDK (from my reading of the thread it isn't quite ready yet for use with the published SDKs)

What does -fwasm-exceptions do? Adding or removing that makes no difference, I still end up with
wasm-ld: error: /var/folders/74/djsf8lv965l2tkgr29ybpz4h0000gn/T/lib-858918.o: undefined symbol: __cxa_allocate_exception
wasm-ld: error: /var/folders/74/djsf8lv965l2tkgr29ybpz4h0000gn/T/lib-858918.o: undefined symbol: __cxa_free_exception
wasm-ld: error: /var/folders/74/djsf8lv965l2tkgr29ybpz4h0000gn/T/lib-858918.o: undefined symbol: __cxa_throw

thx

I found that llvm 17 was branched off end of June and above exception patches were merged mid September, so we need to wait for llvm 18 (should branch off today, first RC on Friday) or upgrade to a git version.

The -fwasm-exceptions flag allows the compiler to output the try / catch and other exception handling instructions in WebAssembly bytecode.  But it is up to the language implementation to determine how these instructions are used.
Languages aren't used to dealing with WASM exception instructions. Instead they traditionally use setjmp / longjmp, C++ is a good example of this. Therefore the language's supporting library (also confusingly called the C++ runtime) needs to be updated to use exception handling.
When the C++ compiler encounters an exception in the code you are attempting to compile, behind the scenes it generates calls to it's runtime library to implement the exception handling. It is inside the runtime library that the exception instructions are used.
The error your seeing is an error generated by WASI-SDK, which bundles the C++ runtime library, the version of the library supplied by WASI-SDK doesn't include the three functions listed above - which are all designed for exception handling.
So when you compile C++ with an exception in your code, the compiler generates it faithfully, with calls to functions in the C++ runtime library which do not exist, this is why, at link time you get the error message you mentioned.
The Emscripten folks have worked on this and have an update which includes the C++ runtime functions we're missing. I understand they were hoping to upstream this to LLVM, and then WASI-SDK would be able to pull this down.  - I'm not sure of the current state of this work, @sunfishcode and @aheejin and, I think the best folks to be able to help on that front.

That is a great explanation, thank you.

The library code has been already upstreamed, as I commented in https://github.com/WebAssembly/wasi-sdk/issues/334#issuecomment-1730976179. But given that Emscripten uses our custom build system and not the LLVM's CMake build system, how it works well with the native LLVM has not been well tested and you might need some adjustment on the build files. I'm not familiar with what build system WASI uses (Is that the LLVM's or something separate?), but that will require changes as well. For example, from libunwind we only use Unwind-wasm.c and nothing else: https://github.com/emscripten-core/emscripten/blob/4aefde3f78e0d3d6327105b123c99dbe3283f779/tools/system_libs.py#L1635

Indeed, llvm already uses wasm exception to implement SJLJ, when wasm exceptions are enabled, so it should just work once we enable exceptions.

do you mean to use saveSetjmp getTempRet0 etc for WASI as well?

Indeed, llvm already uses wasm exception to implement SJLJ, when wasm exceptions are enabled, so it should just work once we enable exceptions.

do you mean to use saveSetjmp getTempRet0 etc for WASI as well?

Right, and this seems to have been moved to compiler-rt in Emscripten: https://github.com/emscripten-core/emscripten/blob/main/system/lib/compiler-rt/emscripten_setjmp.c
Even though the file name says 'emscripten', some of the functions in there are also used by Wasm SjLj handling (which is, SjLj handling using the instructions in the Wasm EH proposal) That file was newly added in Emscripten and didn't come from the compiler-rt in LLVM.
I understand this is getting confusing somewhat, which I think stemmed from that Emscipten uses its custom build system.. I guess we should consider making LLVM's CMake system to reflect the Emscripten setup. In the meantime, this is the list of library files created/modified for Wasm EH in Emscripten:
compiler-rt:
https://github.com/emscripten-core/emscripten/blob/main/system/lib/compiler-rt/emscripten_setjmp.c (created)
libc++abi:
https://github.com/llvm/llvm-project/blob/main/libcxxabi/src/cxa_personality.cpp (modified)
https://github.com/llvm/llvm-project/blob/main/libcxxabi/src/cxa_exception.cpp (modified)
https://github.com/llvm/llvm-project/blob/main/libcxxabi/src/cxa_exception.h (modified)
libunwind:
https://github.com/emscripten-core/emscripten/blob/main/system/lib/libunwind/src/Unwind-wasm.c (created)

Indeed, llvm already uses wasm exception to implement SJLJ, when wasm exceptions are enabled, so it should just work once we enable exceptions.

do you mean to use saveSetjmp getTempRet0 etc for WASI as well?

Right, and this seems to have been moved to compiler-rt in Emscripten: https://github.com/emscripten-core/emscripten/blob/main/system/lib/compiler-rt/emscripten_setjmp.c
Even though the file name says 'emscripten', some of the functions in there are also used by Wasm SjLj handling (which is, SjLj handling using the instructions in the Wasm EH proposal) That file was newly added in Emscripten and didn't come from the compiler-rt in LLVM.
I understand this is getting confusing somewhat, which I think stemmed from that Emscipten uses its custom build system.. I guess we should consider making LLVM's CMake system to reflect the Emscripten setup. In the meantime, this is the list of library files created/modified for Wasm EH in Emscripten:
compiler-rt: https://github.com/emscripten-core/emscripten/blob/main/system/lib/compiler-rt/emscripten_setjmp.c (created)
libc++abi: https://github.com/llvm/llvm-project/blob/main/libcxxabi/src/cxa_personality.cpp (modified) https://github.com/llvm/llvm-project/blob/main/libcxxabi/src/cxa_exception.cpp (modified) https://github.com/llvm/llvm-project/blob/main/libcxxabi/src/cxa_exception.h (modified)
libunwind: https://github.com/emscripten-core/emscripten/blob/main/system/lib/libunwind/src/Unwind-wasm.c (created)

thank you.
i did an experiment to use sjlj with wasi. it seems working well.
https://github.com/yamt/garbage/tree/master/wasm/longjmp
(i wrote the runtime (rt.c) by myself because i didn't know where emscripten version was.)

https://github.com/WebAssembly/wasi-libc/pull/467


Roadmap somewhere ?

More of a question than an issue :
Is there a clear roadmap somewhere about where you want to go with next.js ?
Next5 is 1 day old but I didn't found any info about what you are going to do for v6 ?

The post about Next5 is here: https://zeit.co/blog/next5
There isn't a public roadmap about Next6 but you can follow the branch canary for updates.

We don't have a public roadmap at the moment. When it's made public you'll see it on our blog zeit.co/blog 👍


Remove usage of pandas grouper in groupby

The method _compute_sum_of_squares accesses the grouper from pandas which is deprecated with 2.2 and will be removed soonish
This whole method looks odd to me, like it isn't really necessary. Can someone from cudf (@rjzamora maybe?) comment what the cudf comment in this function refers to? Maybe we can get rid of this method altogether?

This whole method looks odd to me, like it isn't really necessary... Maybe we can get rid of this method altogether?

Are you saying that _compute_sum_of_squares should be simplified, or that we should be calling something different in _build_agg_args_var? I can probably get on board either way - just want to clarify.

Can someone from cudf (@rjzamora maybe?) comment what the cudf comment in this function refers to?

Some relevant discussion can be found in https://github.com/dask/dask/pull/6186, but the cudf-related comments generally refer to two things: (1) The original groupby(...).apply logic was very bad for GPU performance, and somewhat bad for CPU performance. (2) In order to perform the pow(2) operation on all rows at once, we need to extract the original ddf.groupby(...) arguments so that we can re-run the grouping on the modified data - This information is accessed differently in pandas vs cudf.
Now that pandas is deprecating grouper, is there an alternative way to extract the original arguments passed to groupby?
Perhaps a reasonable alternative is to simply add a "_grouping_kwargs" attribute to the result of _groupby_raise_unaligned so that we can always extract this information in a consistent way?


Reuploaded package tarball filename includes '-reupload'

Describe the bug
I'm pretty sure this is not a bug but i didn't found any information on warehouse documentation about this behavior.
So i'm parsing the package releases files from the Legacy API (/simple/<project>/) and in results for html5lib package i found that its 1.0 release tarball is named html5lib-1.0-reupload.tar.gz. I assume this is the correct behavior but i didn't found any explicit documentation about it.
Expected behavior
I was not expecting reuploaded package filename to be marked with -reupload although it seems accurate.
I'm just wondering if there is any explicit documentation about it and if there was other similar behavior for other specific cases ?
To Reproduce

Make a request to the Legacy API for the endpoint /simple/html5lib/
In the 'files' search for the 1.0 release item
Look at the tarball filename

My Platform

Python 3.10
I'm doing this parsing from a tool which check about requirements informations
The tool is using requests package to make a request to the Legacy API in JSON format

This is generally not expected behavior, at least anymore. The release in question is almost 7 years old ("Released: Dec 7, 2017") and there's a fair amount of cruft from times when we did less validation of file ames, metadata, etc. This seems to be one example.

Ah ok thanks, but i suppose these package release filename won't never change so i need to still supporting it, no ?

Yes, this is what was originally uploaded, and we don't (usually) make corrections.

Thanks for the informations


Cloud mongo support fix

Changes

added dnspython module to Python 2 vendor which is required for mongodb+srv schema
added maya and houdini to python 2 vendor prelaunch hook
modified order of import from env_tools

couldn't we put it there as submodule?


🐛 Bug Report: Creating customs test, can't import @backstage/plugin-scaffolder-node-test-utils

📜 Description
I want to create a test for my custom action. After reading the docs on how to write tests, i ran into an issue.
When creating the test the createMockActionContext from @backstage/plugin-scaffolder-node-test-utils is not found. I can find the package in the node_modules, but the createMockActionContext can't be used.
The error is as follows Cannot find module '@backstage/plugin-scaffolder-node-test-utils' from 'plugins/scaffolder/actions/merge-azure-pipeline.test.ts' i've listed the reproduction steps below.
👍 Expected behavior
It should find the module @backstage/plugin-scaffolder-node-test-utils and i should be able to use the createMockActionContext
👎 Actual Behavior with Screenshots
Cannot find module '@backstage/plugin-scaffolder-node-test-utils' from 'plugins/scaffolder/actions/my-test.test.ts
👟 Reproduction steps
npx @backstage/create-app@latest
cd into the project
from the root of the project run:
yarn --cwd packages/backend add @backstage/backend-test-utils @backstage/plugin-scaffolder-node-test-utils
create the file packages/backend/src/plugins/scaffolder/actions/my-test.test.ts
add the following content to the file
import { createMockDirectory } from '@backstage/backend-test-utils';
import { createMockActionContext } from '@backstage/plugin-scaffolder-node-test-utils';
import { createMyAction } from './my-action';

describe('test:action', () => {
  const workspacePath = createMockDirectory().resolve('workspace');
  const mockContext = createMockActionContext({
    workspacePath,
  });
  it('should foo', async () => {
    const action = createMyAction();
    await action.handler({
      ...mockContext,
      input: {
        myInput: 'foo',
      },
    });

    expect(true).toBe(true);
  });
});

When running yarn test my-test i'm getting the following error:
Cannot find module '@backstage/plugin-scaffolder-node-test-utils' from 'plugins/scaffolder/actions/my-test.test.ts'
📃 Provide the context for the Bug.

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else

I encountered the same issue and already spent a few hours on it.
package.json
  "devDependencies": {
    "@backstage/backend-test-utils": "^0.3.3",
    "@backstage/cli": "^0.25.0",
    "@backstage/plugin-scaffolder-node-test-utils": "^0.1.0-next.0",
    "@types/dockerode": "^3.3.0",
    "@types/express": "^4.17.6",
    "@types/express-serve-static-core": "^4.17.5",
    "@types/luxon": "^2.0.4"
  },

Cannot find module '@backstage/plugin-scaffolder-node-test-utils' from 'plugins/scaffolder/actions/folder-copy.test.ts'

The issue is an invalid package.json config. @backstage/plugin-scaffolder-node-test-utils ships only a cjs file but in the package.json it references an esm file as the entrypoint:

The publishConfig needs to be updated as well: https://github.com/backstage/backstage/blob/master/plugins/scaffolder-node-test-utils/package.json#L9


added a confirm modal using $uibModal

commented the previous $mdDialog, and replaced it with a $uibModal on top of it. Line >> 233

awesome!


Update silencer-lib, silencer-plugin to 1.7.13

About this PR
📦 Updates

com.github.ghik:silencer-lib
com.github.ghik:silencer-plugin

from 1.7.8 to 1.7.13
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.ghik" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.github.ghik" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #619.


Remove stream.pipeline(); on("close", resolve) workaround

Since the following bug in nodejs fs core module was fixed https://github.com/nodejs/node/issues/31776 we need to get rid of the following workaround  as per https://github.com/nodejs/node/issues/31776#issuecomment-586274923 https://github.com/rust-analyzer/rust-analyzer/blob/77d27c67c1dadce4abe7a6a97c0b73eaa3706e60/editors/code/src/installation/download_file.ts#L44-L50
ACHTUNG! Wait until vscode officially migrates to relevant nodejs version where this is fixed, update our vscode version requirements and only then remove the workaround.
Current version 1.42 of vscode uses nodejs 12.4

History of the bug and its detection: https://github.com/rust-analyzer/rust-analyzer/pull/3092#discussion_r378191131
We probably need to wait until vscode adopts nodejs 13.x+ version.

VSCode is now on Node v14, is this still needed?


Add core model classes (User, Place, Annotation, and LABrand colors)

Hard-coded the class properties until API client is working. Also updated license.

 Set up common Models


Setup the repo

This PR pretty much sets up the repo all around:

Add a bit more detail into the README. We can consider adding more once the image has been pushed.
Add the Dockerfile

Any feedback on the author metadata field? Is this the right email address? I didn't include a maintainer label either - should we?
I more or less followed spell-check.yaml and used the base rocker/tidyverse and installed spelling. But, I didn't specify the repo with , repos = c(CRAN = '$CRAN'))". Should I add this?

Add a GHA

I mostly followed the default setup but infused with our creds as specified here. I didn't include the docker metadata step found in that linked GHA since this is a much smaller potatoes image.
Let me know where the workflow can be tweaked!

Also note that I set up this repo with the MIT license. Any thoughts there?

Getting closer!
Also thinking of next steps, I'm not entirely sure how directories/OS will work between a dictionary file stored in the repo we're spell checking, and the spell check script itself. My sense is since we've placed the script as an executable in a directory that is presumably in $PATH, we maybe don't have to think about it at all and things will just...work?

I'm not filing it as a PR to this branch just yet, but I could if you like it.

I don't see a good reason not to really? Helps move things along, can't hurt!

I love it, for now at least.


Skipped some tests when running against Azure

Coverage decreased (-0.05%) to 75.401% when pulling 8b7fb35caa4845152d65153bd5243b66b0956afc on yitam:azTests into f4ad2ae1d4df544246cae7bb6b30ee353b3d4843 on Microsoft:dev.

Codecov Report

Merging #874 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #874   +/-   ##
=======================================
  Coverage   80.37%   80.37%
=======================================
  Files          25       25
  Lines        7649     7649
=======================================
  Hits         6148     6148
  Misses       1501     1501

Continue to review full report at Codecov.

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


[BEAM-3644] Disable verbose typecoder warnings.

These are mostly noise for end-users, but are a lot more frequent
for non-direct runners that actually use coders.
Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand:

[ ] What the pull request does
[ ] Why it does it
[ ] How it does it
[ ] Why this approach

[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @charlesccychen

LGTM.


Use the same naming in odd specification and odd platform

e.g. in specification we have DataEntityType, which is mapped to DataEntitySubType in platform

Discussed with @Leshe4ka and decided that this task is not our priority, closing it now

@damirabdul it's still a task to do. We will move it to another milestone


Dependabot "update-type" not available in metadata retrieved for PR using dependabot/fetch-metadata@v1

Hello, I have the same issue like this person: Dependabot "update-type" not available in metadata retrieved for PR using dependabot/fetch-metadata@v1
For example here: https://github.com/simonschaufi/php-libkml/actions/runs/8285139412/job/22672206081
Run<EMAIL_ADDRESS>  with:
    github-token: ***
    skip-commit-verification: false
    skip-verification: false
Parsing Dependabot metadata
Outputting metadata for 1 updated dependency
  outputs.dependency-names: rector/rector
  outputs.dependency-type: direct:development
  outputs.update-type: null
  outputs.directory: /
  outputs.package-ecosystem: composer
  outputs.target-branch: main
  outputs.previous-version:
  outputs.new-version:
  outputs.compatibility-score: 0
  outputs.maintainer-changes: false
  outputs.dependency-group:
  outputs.alert-state:
  outputs.ghsa-id:
  outputs.cvss: 0

As you can see, outputs.update-type is always null
This is my workflow: https://github.com/simonschaufi/php-libkml/blob/main/.github/workflows/dependabot-auto-merge.yml
Is there some misconfiguration or is this really a bug?

Similar but not the same: #339. On that bug report it's about the v prefix but in my case there is a simple version bump without the v prefix.

@Nishnha could you give me some information about this issue?

@simonschaufi
It seems that update-type is generated from the version information in the commit message as shown below.
However, there are cases where the version information is not included in the commit message, in which case update-type becomes null.
https://github.com/dependabot/fetch-metadata/blob/325b863556700e5e4d4ec23381993ef460dd8379/src/dependabot/update_metadata.ts#L58-L82
In the above example, the commit message was as follows.
Updates the requirements on [rector/rector](https://github.com/rectorphp/rector) to permit the latest version.
- [Release notes](https://github.com/rectorphp/rector/releases)
-<EMAIL_ADDRESS>
---
updated-dependencies:
- dependency-name: rector/rector
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>
There are two possible solutions.
1, Get the version information from somewhere other than the commit message (such as the title of the PR).
2, Modify the commit message so that the version information is always included (probably needs to be modified in other repositories).
@Nishnha
I could not decide which option is better and would appreciate your opinion.
This also occurs in the latest v2 as well as v1.

I think option 1 is the easier and better solution here.

Hi are these PRs that address a security update? We don't include the update-type for security updates at the moment.

To add more context, so far we've purposefully avoided exposing update-type as we don't want to advertise that the repo getting the PR might have an open vulnerability.
I realize security by obscurity isn't great, and technically someone could figure this out themselves by cross-referencing CVE data with library versions... but still, let's not make the bad guys job easier.
One idea we've considered is that the risk is much lower for innersource/private repos, so we could optionally expose it for them. But suddenly this gets a bit more complicated and requiring more engineering time and so far it's not that frequently requested by users.

Hi are these PRs that address a security update? We don't include the update-type for security updates at the moment.

Nope. We are seeing it for regular dependency updates, too.
Interestingly only for those who Updates the requirements on X to permit the latest version. and not the Bumps x from y to z.

This used to work and just seeing that update-type is set to null after I enabled group security updates.
@simonschaufi could this also be your case? There is an existing issue


fix partitionKeyValueRanges type in SasTokenProperties.ts

added type partitionKeyValueRanges

API changes have been detected in @azure/cosmos. You can review API changes here
API changes
-     partitionKeyValueRanges: [];
+     partitionKeyValueRanges: string[];


Call a callback method

It would be great to have the ability to call a custom callback method after sorting. Right now, I have to dig inside the source =(

Pull requests implementing events are welcome.
At the moment, you can use observers and check whether sort_order value was changed.


Enforce hosts whitelist on REST API

Description
To mitigate DNS rebinding attacks, the REST API should validate the Host header matches one of the whitelisted hostnames.
This should be similar to the Besu --host-whitelist: https://besu.hyperledger.org/en/stable/HowTo/Interact/APIs/API/#host-whitelist although I don't believe we need to support the special "all" or "none" magic values --rest-api-host-whitelist= would be the equivalent of "none" and just use * as the only value for all.

This documentation is now available here:
https://docs.teku.pegasys.tech/en/latest/Reference/CLI/CLI-Syntax/#rest-api-host-whitelist

Posting here as a minor request but supporting netmask as well such as <IP_ADDRESS>/24 could be useful.


Feature request: create a loading component

Description
Create an indicate loading and progress states.

i will do pls assign me

@rodgeraraujo Can I work on it?

@ShashankRawatgit92 I will assing you. @Nimanita If you prefer, you can work on this new feature #11 .

@rodgeraraujo Thank you but already one person has volunteered for it before me.So please assign me issue #12 .I found it very interesting.


Remote debugging not working

No matter what instructions I follow, I can't get vscode-php-debug to work.
No breakpoints, no log-outputs... nothing!
Am I missing something?
Nginx is configured to point http://phpclient.local to /var/www/html/phpclient
Within phpclient directory is an importer directory, with an index.php.
Calling: http://phpclient.local/importer simply shows no debugging output within VSCode.
Docker for Mac with php-fpm image
PHP version:  7.2
XDebug version: 2.6.0
Adapter version:  1.12.3
Your launch.json:
{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Listen for XDebug",
            "type": "php",
            "request": "launch",
            "port": 9001,
            "pathMappings": {
                "/var/www/html/phpclient/importer": "/Users/add/Projects/Web/phpclient/importer",
            },
            "log": true
        },
        {
            "name": "Launch currently open script",
            "type": "php",
            "request": "launch",
            "program": "${file}",
            "cwd": "${fileDirname}",
            "port": 9001
        }
    ]
}

XDebug php.ini config:
xdebug.remote_enable=On;
xdebug.remote_autostart=On;
xdebug.remote_connect_back=1
xdebug.remote_port=9001;
xdebug.idekey="VSCODE";
xdebug.remote_log="/tmp/xdebug.log";

XDebug logfile (from setting xdebug.remote_log in php.ini):
Log opened at 2018-07-21 11:53:22
I: Checking remote connect back address.
I: Checking header 'HTTP_X_FORWARDED_FOR'.
I: Checking header 'REMOTE_ADDR'.
I: Remote address found, connecting to <IP_ADDRESS>:9001.
I: Connected to client. :-)
-> <init xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" fileuri="file:///var/www/html/spwien/importer/index.php" language="PHP" xdebug:language_version="7.2.7" protocol_version="1.0" appid="8" idekey="VSCODE"><engine version="2.6.0"><![CDATA[Xdebug]]></engine><author><![CDATA[Derick Rethans]]></author><url><![CDATA[http://xdebug.org]]></url><copyright><![CDATA[Copyright (c) 2002-2018 by Derick Rethans]]></copyright></init>

-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" status="stopping" reason="ok"></response>

Log closed at 2018-07-21 11:53:22

Log opened at 2018-07-21 11:53:23
I: Checking remote connect back address.
I: Checking header 'HTTP_X_FORWARDED_FOR'.
I: Checking header 'REMOTE_ADDR'.
I: Remote address found, connecting to <IP_ADDRESS>:9001.
I: Connected to client. :-)
-> <init xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" fileuri="file:///var/www/html/spwien/index.php" language="PHP" xdebug:language_version="7.2.7" protocol_version="1.0" appid="9" idekey="VSCODE"><engine version="2.6.0"><![CDATA[Xdebug]]></engine><author><![CDATA[Derick Rethans]]></author><url><![CDATA[http://xdebug.org]]></url><copyright><![CDATA[Copyright (c) 2002-2018 by Derick Rethans]]></copyright></init>

-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" status="stopping" reason="ok"></response>

Log closed at 2018-07-21 11:53:23

Adapter logfile (from setting "log": true in launch.json):
<- launchResponse
Response {
  seq: 0,
  type: 'response',
  request_seq: 2,
  command: 'launch',
  success: true }

Ok...  solved the issue.
Since I'm using -dns <IP_ADDRESS> in my docker-compose.yml, I had to configure php.ini as follows:
xdebug.remote_connect_back=0
xdebug.remote_host=<IP_ADDRESS>; my internal host IP

AND, I also had to remove the -ports 9001:9001 from the docker-compose.yml


Add react polyfills for IE

Summary | Résumé
This PR adds polyfills for IE11 as well as stable browsers (>0.2% global usage)

I am not sure what I should be looking for in order to test this (not sure what specific issues we had), but I do have access to Browserstack so happy to take a look once I know what to look for!

Looks great now, layout, left indent, etc.
Submit doesn,t seem to run though, get back to the same page without seeing confirmation. tx


Error When Compiling with Teensyduino 1.58+

Hardware description: Teensy 4.1 and Teensyduino 1.58.0
Installation type: micro_ros_setup
Version or commit hash: Galactic, https://github.com/micro-ROS/micro_ros_arduino/commit/e7bd525cad256cd5fb36f1cae98b39cf1a6dba69

Steps to reproduce the issue

Install Arduino 2.0.4.
Add https://www.pjrc.com/teensy/package_teensy_index.json to Additional Boards Manager
Add teensy rules to /etc/udev/rules.d/00-teensy.rules
Replace platform.txt with https://raw.githubusercontent.com/micro-ROS/micro_ros_arduino/galactic/extras/patching_boards/platform_teensy.txt
Attempt to compile code for Teensy 4.1

Expected behavior

successful compilation

Actual behavior

Additional information
The above image is from Arduino 1.8.19. I had the same error for 2.0.4.  I was able to successfully compile when using Teensyduino 1.57.2. This seems like a problem specific to Teensyduino 1.58+.

Subscribing for future updates: I'm dealing with the same issue on a Teensy 3.2. I'm linking another issue thread on PJRC's website that I've been updating as I try to figure it out. Best of luck.

@CaseyGymnast I solved this by using Arduino 2.0.4 and Teensyduino 1.57.2.  In arduino 2, you can choose older teensyduino versions.  It'll take more time for me to find out the micro ROS distribution that matched but I believe I used v2.0.4-galactic.

Hi guys,
We have just updated the repository to support Teensyduino 1.58.x, deprecating the 1.57.2 support.
Please take a look to the latest commits and try them out, will add a release with the update once the feedback is positive.

@Acuadros95 that is great to hear! I will verify next week and let you know.  Thank you!

Yes, I'm having issues with Teensy 4.0 and Arduino IDE 2.1.1
It won't upload the precompiled libraries.

WARNING: library micro_ros_arduino claims to run on stm32, OpenCR, Teensyduino, samd, sam, mbed, esp32, mbed_portenta architecture(s) and may be incompatible with your current board which runs on avr architecture(s).
Library micro_ros_arduino has been declared precompiled:
Using precompiled library in /home/russ/Arduino/libraries/micro_ros_arduino/src/imxrt1062/fpv5-d16-hard
/home/russ/.arduino15/packages/teensy/tools/teensy-compile/11.3.1/arm/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/bin/ld: /home/russ/Arduino/libraries/micro_ros_arduino/src/imxrt1062/fpv5-d16-hard/libmicroros.a(librmw-validate_full_topic_name.c.obj): in function rmw_validate_full_topic_name': validate_full_topic_name.c:(.text.rmw_validate_full_topic_name+0xbe): undefined reference to __locale_ctype_ptr'
/home/russ/.arduino15/packages/teensy/tools/teensy-compile/11.3.1/arm/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/bin/ld: /home/russ/Arduino/libraries/micro_ros_arduino/src/imxrt1062/fpv5-d16-hard/libmicroros.a(librmw-validate_node_name.c.obj): in function rmw_validate_node_name': validate_node_name.c:(.text.rmw_validate_node_name+0x5e): undefined reference to __locale_ctype_ptr'
/home/russ/.arduino15/packages/teensy/tools/teensy-compile/11.3.1/arm/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/bin/ld: /home/russ/Arduino/libraries/micro_ros_arduino/src/imxrt1062/fpv5-d16-hard/libmicroros.a(librcl-validate_topic_name.c.obj): in function rcl_validate_topic_name': validate_topic_name.c:(.text.rcl_validate_topic_name+0x46): undefined reference to __locale_ctype_ptr'
/home/russ/.arduino15/packages/teensy/tools/teensy-compile/11.3.1/arm/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/bin/ld: validate_topic_name.c:(.text.rcl_validate_topic_name+0xb6): undefined reference to __locale_ctype_ptr' /home/russ/.arduino15/packages/teensy/tools/teensy-compile/11.3.1/arm/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/bin/ld: validate_topic_name.c:(.text.rcl_validate_topic_name+0x164): undefined reference to __locale_ctype_ptr'
collect2: error: ld returned 1 exit status


[Doc] Add import Option 2 in the Material Icons page

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡
https://mui.com/components/material-icons/
Right now the following page allows you to 1-click copy the import. Which is very useful to search for an icon and import it immediately. However it only offers Option 1, which is not our prefer way of importing.
Options reference from the usage section: https://mui.com/material-ui/icons/#usage

Motivation 🔦

Option 2 is a much better Dev Experience, we use Tree Shaking and bundle size isn't much of an issue for us in the first place, efficient development is.

I feel like I'm missing some key information to make sense of this issue. What are "Option 1" and "Option 2"?

I have added a link and image to the description. Hopefully that should be clearer !


Location fields (organizational profile) not usual address fields

When you add a location of for example an organizational profile, the fields to enter are not very usual for an address. See below:

That there is a location name make sense, especially for addresses in the global South, but the rest (other than country) don't really make a lot of sense.
I would suggest to change to:

Location name
Address
City
Postal code
Country.

removed coordinates fields, added the others + province / region (if we ask to provide and address we might as well do it completely)


Added uoggmk.by

IT related course is offered by the college: http://www.uoggmk.by/specialities/spec_pk.html
Official domain proof: http://whois.domaintools.com/uoggmk.by

@gvitali lib/domains/by/uoggmk: Your request has an incorrect file path format, please ensure the request follows     the repository rules set out at the bottom of this page and change     it accordingly or start a new one.     If you are unable to make a pull request with the instructions provided, please send an email to<EMAIL_ADDRESS>mentioning the URL of this request in the message.


Haystack 2.x integration

Library doesn't work with haystack-ai (haystack 2.x) because of farm-haystack (haystack 1.x) dependency. Is there a plan to integrate with haystack 2.x?
https://github.com/deepset-ai/haystack/issues/6652
Appreciate.

Hi! For now I haven't had time to familiarize with haystack 2 so I'm not currently planning to do the integration. Anyhow, If I see I have time in the future I might and in the mean time any pull requests with these changes are welcome :)


Add Command Line Interface

Add a CLI so people can run and see tests from their CL. Make sure to allow for windows, linux & mac.

I'm going to close this until Windows brings out their new command line unless there is a desperate need for it. Makes life easier on myself.


Fe hands on 5

Metric
Value

alert_status
b:white_check_mark: OK/b

bugs
0

code_smells
2

reliability_rating
A (0 Bugs)br/Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)br/Note: A being best, E being worst

vulnerabilities
0


Adkernel: documenting monetix alias

🏷 Type of documentation

[x] update bid adapter

📋 Checklist

[x] Related pull requests in prebid.js or server are linked -> https://github.com/prebid/Prebid.js/pull/11264

Note: already released in 8.43, so will merge after the gpp_sids is provided.


Failed to activate the all-times-you-know package

[Enter steps to reproduce below:]

...
...

Atom Version: 1.7.4
System: Mac OS X 10.11.5
Thrown From: all-times-you-know package, v0.6.1
Stack Trace
Failed to activate the all-times-you-know package
At url.format is not a function

TypeError: url.format is not a function
  at AllTimesYouKnowView.refresh (/Users/bi/.atom/packages/all-times-you-know/lib/all-times-you-know-view.coffee:56:17)
  at AllTimesYouKnowView.refresh (/Users/bi/.atom/packages/all-times-you-know/lib/all-times-you-know-view.coffee:1:1)
  at new AllTimesYouKnowView (/Users/bi/.atom/packages/all-times-you-know/lib/all-times-you-know-view.coffee:21:6)
  at Object.module.exports.AllTimesYouKnow.activate (/Users/bi/.atom/packages/all-times-you-know/lib/all-times-you-know.coffee:37:32)
  at Package.module.exports.Package.activateNow (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:183:20)
  at /Applications/Atom.app/Contents/Resources/app.asar/src/package.js:156:32
  at Package.module.exports.Package.measure (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:92:15)
  at /Applications/Atom.app/Contents/Resources/app.asar/src/package.js:149:26
  at Package.module.exports.Package.activate (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:146:34)
  at PackageManager.module.exports.PackageManager.activatePackage (/Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:538:21)
  at /Applications/Atom.app/Contents/Resources/app.asar/node_modules/settings-view/lib/package-manager.js:389:60
  at exit (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/settings-view/lib/package-manager.js:73:16)
  at triggerExitCallback (/Applications/Atom.app/Contents/Resources/app.asar/src/buffered-process.js:215:47)
  at /Applications/Atom.app/Contents/Resources/app.asar/src/buffered-process.js:222:18
  at Socket.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/buffered-process.js:100:18)
  at emitOne (events.js:82:20)
  at Socket.emit (events.js:169:7)
  at Pipe._onclose (net.js:469:12)

Commands
     -3:33.9.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -2:52.8.0 settings-view:check-for-package-updates (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)

Config
{
  "core": {
    "customFileTypes": {
      "source.ini": [
        ".buckconfig",
        ".flowconfig"
      ],
      "source.json": [
        ".arcconfig",
        "BUCK.autodeps"
      ],
      "source.python": [
        "BUCK"
      ]
    },
    "disabledPackages": [
      "tree-view",
      "activate-power-mode"
    ]
  },
  "all-times-you-know": {
    "size": "o",
    "tags": "nature"
  }
}

Installed Packages
# User
all-times-you-know, v0.6.1
auto-indent, v0.5.0
autocomplete-json, v1.11.0
editorconfig, v1.4.1
javascript-snippets, v1.2.1
language-javascript-jsx, v0.3.7
minimap, v4.24.2
nuclide, v0.139.0
sync-settings, v0.7.2
terminal-plus, v0.14.5

# Dev
No dev packages

Close this because of flickr-background.


Need to be able to restrict payloads of search to small # of fields

In the map display, I need to be able to efficiently get all of the title + locations of all of the cases for example, but without fetching body, and all of the other metadata on cases.
This will be a frequent query, as it'll happen on the home page.  I suspect we want a simplified version of search_cases.sql etc which only returns fields we know we need.  A hackier version is to do the full SQL search, but trim the results before they go over the slow wire.

I dealt with this with /search/map so I don't need it urgently.

Generally for search results, what fields do we need? My best guess:

id
title
type (case/method/organization)
lead image
last updated

Does that look right?

Author name and id would be good too.  And bookmarked by current user or not.

Cool, thanks!

Oh, original author, most recent edited by, or both?

Ah. Hmm.  never mind.  The mockup don't need it now, so let's assume we don't need them later. YAGNI.

Fixed, for full-text searches, in issue #83. Faceted search will fix this as part of #60 and/or #53


examples/with-app-directory not working when upgrade to latest next and reactjs

I cloned the react-translate/examples/with-app-directory and use latest next, react, next-translate. checkout this repo https://github.com/chhornponleu/next-translate-app-dir-demo.
What happened?
http://localhost:3000 and http://localhost:3000/en works, while http://localhost:3000/ca, http://localhost:3000/es got error 404.
What did you expect to happen?
http://localhost:3000/ca, http://localhost:3000/es should render using the selected locale
Are you willing to submit a pull request to fix this bug?
Not sure if I am capable of it.

Looks rare @chhornponleu, I cloned your repo and works fine:

The repo example is also in Codesandbox and works fine https://codesandbox.io/p/sandbox/next-translate-app-dir-fw68h2?file=%2Fsrc%2Fapp%2Fpage.tsx&selection=[{"endColumn"%3A1%2C"endLineNumber"%3A6%2C"startColumn"%3A1%2C"startLineNumber"%3A6}]
Also, I try it the current next-translate example now locally with Next.js 13.2 and Next-translate-plugin 2.0, and is working fine 😅
Would you provide more info about your SO, node version, etc?
I tried with Node.js v16.19.0 and v18.13.0 and both work fine. Thanks to report it!

I have the same problem even using the next-translate-plugin version 2.0.2:

It only accept if change defaultLocale config for that specific lang.
OS: W11 with WSL1
Node: 16.17.1
NPM: 8.15.0

It looks like a middleware problem... I'm going to take a look at the problem. Thanks to report it

@aralroca @chhornponleu
With aralroca's report about can be the middleware, I debugged and maybe found the problem: request.nextUrl.href is using the lang code in the pathname part but when it is not the defaultLocale it's not using.

Probably the fix, for me is now working fine.
import { NextResponse } from 'next/server'
import type { NextRequest } from 'next/server'
import i18n from '../i18n'

export function middleware(request: NextRequest) {
  const locale = request.nextUrl.locale || i18n.defaultLocale

  request.nextUrl.searchParams.set('lang', locale)

 // THIS LINE
  request.nextUrl.href = request.nextUrl.href.replace(`/${locale}`, '')

  return NextResponse.rewrite(request.nextUrl)
}

I abstracted the app dir logic into next-load library, if somebody wants to load different things than translations in an easy way 😊 If you try please give some feedback 🙏
The idea is to use next-load package to support also layout, template, loading, etc. Next-load is still in 0.x and is a good way to try and find the best solution + support to integrate next-load in libraries as next-translate before next-load 1.0
Bye the way, I close the issue, already fixed by @marcelotk15 . Thanks

I believe the 404 in non default languages returned again after 13.4.0.
I didn't had time to investigate further, but it seems that now the problem is not in the middleware.
The middleware seems to be working well, removing locale from the href and path and adding it as searchParam. But the the route don't match.
If you add a new [lang]/page.tsx it works. The problem should be in the routing itself.
I will try to investigate further tonight

Hey bro, I'm using the latest version of nextjs, and found that next-translate doesn't work anymore, and 404 appears when I click to access .
codesandbox address ： https://codesandbox.io/p/sandbox/next-translate-app-dir-forked-vp5r4n?file=%2Fpackage.json&selection=[{"endColumn"%3A20%2C"endLineNumber"%3A13%2C"startColumn"%3A11%2C"startLineNumber"%3A13}]

@fernandojbf @lynn1286 , the PR solving this is already implemented for https://github.com/aralroca/next-translate-plugin/issues/21 @alvesvin, probably should be fixed in the next release


Auto synchornization using API key

Currently ADMIN has to login before synchronizing the calendar. This should be
done automatically. Instead of JSON oauth, use API key.

2ab1440e..f0d9ec03 (and some other commits before this)
implements it.


Update examples

Update package deps for the examples. Only issue remaining is "Premature close" on many of the examples.
Added readme to explain usage of Proxy examples.

I get
Error: Missing `pino-pretty` module: `pino-pretty` must be installed separately

on the server-side-rendering example. do you see the same?
Pino is a logging module used by fastify. Likely that update requires that you also add a separate dependency on pino-pretty.

What command did you run to get this?

clinic bubbleprof --on-port 'node server-side-rendering/stories.js' -- node server-side-rendering/server

(though the --on-port flag isn't the thing that crashes for me, just clinic bubble -- node server-side-rendering/server has the same effect.)

I can see that issue now. I've added pino-pretty to the package.


[ALLUXIO-2126] The javadoc in FileInStream.java for the variable mPos can be one line

https://alluxio.atlassian.net/browse/ALLUXIO-2126
I Merged the javadoc in FileInStream.java for the variable mPos into one line.

Can one of the admins verify this patch?

LGTM