Acceptance tests: cucumber

Run with:
bundle exec rake features

@njam Gave this a try - having some issues here. First run seemed to stall at some point with an error message:
    Examples:
      | box             | provider   |
      | debian/wheezy64 | virtualbox |
      expected "bundle exec vagrant up --provider virtualbox" to be successfully executed (RSpec::Expectations::ExpectationNotMetError)
      features/dns_resolution.feature:21:in `When I successfully run `bundle exec vagrant up --provider virtualbox`'
      features/dns_resolution.feature:16:in `When I successfully run `bundle exec vagrant up --provider <provider>`'
      |

^C
Exiting... Interrupt again to exit immediately.

Cancelling this was apparently a mistake, there seems to be "somewhere" a vagrant lockfile or something similar around (cant find it, though):
    Examples:
      | box             | provider   |
      | debian/wheezy64 | virtualbox |
      Unable to destroy vagrant environment:
      You appear to be running Vagrant outside of the official installers.
      Note that the installers are what ensure that Vagrant has all required
      dependencies, and Vagrant assumes that these dependencies exist. By
      running outside of the installer environment, Vagrant may not function
      properly. To remove this warning, install Vagrant using one of the
      official packages from vagrantup.com.
      An action 'destroy' was attempted on the machine 'default',
      but another process is already executing an action on the machine.
      Vagrant locks each machine for access by only one process at a time.
      Please wait until the other Vagrant process finishes modifying this
      machine, then try again.

      If you believe this message is in error, please check the process
      listing for any "ruby" or "vagrant" processes and kill them. Then
      try again.
       (RuntimeError)
      ./features/support/env.rb:10:in `block (2 levels) in <top (required)>'
      features/dns_resolution.feature:21:in `When I successfully run `bundle exec vagrant up --provider virtualbox`'
      features/dns_resolution.feature:16:in `When I successfully run `bundle exec vagrant up --provider <provider>`'

Running the test can obviously take quite some time - because it's starting and destroying boxes.
But you mentioned that in your case it really stalled. Unfortunately I noticed that cucumber/aruba's debugging output is not too useful. For example if a command fails they don't show the command's output… I will look into trying to change that.
Are you sure the test was stalled? I.e. no CPU was used anymore?
When you cancelled the test the cleanup behaviour was triggered (vagrant destroy). But vagrant failed because it detected another vagrant command still running (probably vagrant  up). You need to clean this up manually by running for example pkill -f vagrant.

@njam Yes, tried those, to no avail, also ps aux|grep vagrant or |grep ruby didnt show anything - thats why I suspected a lockfile. Will debug this further. :)

Hmhmhmhm… I was experiencing troubles with this "locking" mechanism in previous Vagrant versions, but not anymore with the current 1.7.4. Just in case you're on an older version.

It looks like the vagrant up already fails.
Could you try manually on a console?
Create a Vagrantfile:
    Vagrant.configure('2') do |config|
      config.vm.box = 'debian/wheezy64'
      config.vm.hostname = 'my-host.my-tld'
      config.vm.network :private_network, ip: '<IP_ADDRESS>'

      config.landrush.enabled = true
      config.landrush.tld = 'my-tld'
    end

Then start it up:
bundle exec vagrant up --provider virtualbox

@njam Lol - when I tried this just now, everything suddenly works, including the originally failing tests. The only change I did yesterday was to codesign the ruby binary here in osx in between to finally get rid of the osx security alert during every vagrant start. I guess this was for some reason affecting the tests, too - cant reproduce it for now.
In any case: lgtm. As soon as I am able to reproduce the issue, I'll debug further, but as of now, the tests work completely. :dancers:

I opened a ticket on aruba to display the command's output on failure: https://github.com/cucumber/aruba/pull/335
I've adjusted the tests a bit, adding checks for DNS resolution with the custom resolver and also the host's and the guest's resolver.
I'm not sure why, but I have to flush OSX' DNS resolver for the tests to succeed. I hope this is not a general problem, but something with my setup…
@fh wdyt?

I opened a ticket on aruba to display the command's output on failure: https://github.com/cucumber/aruba/pull/335
I've adjusted the tests a bit, adding checks for DNS resolution with the custom resolver and also the host's and the guest's resolver.
I'm not sure why, but I have to flush OSX' DNS resolver for the tests to succeed. I hope this is not a general problem, but something with my setup…
@fh wdyt?

I've added some basic acceptance tests that cover the DNS resolution functionality of landrush with a virtualbox VM. You can run them with:
bundle exec cucumber

They succeed for "debian/jessie64", but fail for "ubuntu/wily64". This is actually a problem of our IP detection (on wily we pick up the address of an additional LXC interface that is present). This could be fixed by https://github.com/phinze/landrush/pull/122.
I would suggest to merge something like what is on this branch, so we can test other branches with it.
@fh @ahpook @strzibny @bexelbie wdyt?

I am tempted to close this pull request in this form. @njam WDYT?

I think it would be great to have acceptance tests for landrush.
Agree with your concerns.
I will adjust this branch to be cross-platform compatible very soon, wdyt?

I think it would be great to have acceptance tests for landrush.

+1, btw have you looked at vagrant-spec. I used it for other vagrant plugins as well. It is not perfect, in particular I dislike that the "core" tests are always visible. On the other hand it is quite intuitive and offers black box testing of your plugin. IMO with less effort than cucumber.

Agree with your concerns.

Cool

I will adjust this branch to be cross-platform compatible very soon, wdyt?

Sure. It would be nice to see a couple of more tests then as well to see a bit better how much effort it is to write new tests/features and back them up with step definitions.
Have you uses Cucumber a lot? I am a bit skeptical towards this whole "executable specification" thing. I think dhh words almost come to my mind when I hear Cucumber:

Don’t use Cucumber unless you live in the magic kingdom of non-programmers-writing-tests (and send me a bottle of fairy dust if you’re there!)

I don't have much experience with cucumber. I've written the same tests as these with vagrant-spec: https://github.com/vagrant-landrush/landrush/pull/145. See also https://github.com/vagrant-landrush/landrush/issues/136 for more information.
Any input welcome!

I don't have much experience with cucumber. I've written the same tests as these with vagrant-spec: #145. See also #136 for more information.

Interesting. I will have a look at both. Any idea why issue #136 is closed? Nothing seems to be merged yet in regards to acceptance tests. In fact I just created #180 to track and discuss this, but it seems we might be better off re-opening #136. WDYT?
For now I will still close this particular pull request, since we agree that in its current form we don't want to merge it.

agree!

Will be continued in: https://github.com/vagrant-landrush/landrush/pull/182
(can't reopen pull request if the first commit changed)


How to test graphql on supabase local development

if graphql api available in local development, what's the endpoint?

If you created a local supabase project with the supabase CLI the endpoint would be
http://localhost:54321/graphql/v1 \

I'll request that info be added to the output of supabase status so its clearer how to get started locally
A full request might look like
curl -X POST http://localhost:54321/graphql/v1 \
    -H 'apiKey: YOUR_API_KEY' \
    -H 'Content-Type: application/json' \
    --data-raw '{"query": "{ accountCollection(first: 1) { edges { node { id } } } }", "variables": {}}'

I'm going to close the issue but please continue responding or re-open if you have any trouble with that

@olirice apologies, a somewhat related question: i'm assuming the pg_graphql extension should create the corresponding Query and Mutation entries whenever a table migration is applied locally? I'm using the Supabase CLI but I'm not able to query the newly created tables, nothing shows up in GraphiQL Docs under the root types either. is there a manual step perhaps? my Discord Q is here.

i'm assuming the pg_graphql extension should create the corresponding Query and Mutation entries whenever a table migration is applied locally?

yes, that's right

I'm using the Supabase CLI but I'm not able to query the newly created tables, nothing shows up in GraphiQL Docs under the root types either. is there a manual step perhaps?

as soon as a table is created it should be visible through GraphQL, there is no manual step to refresh your GraphQL schema.
It sounds like something is preventing them from being visible. The requirements for a table to be visible in GraphQL are

the table has a primary key
the schema containing the table is on the querying user's search_path

assuming that you are querying as anon or authenticated the any table on the public schema should be visible within GraphiQL.
To test that, please create the following table and check if you're able to see it in GraphiQL through Supabase Studio.
create table public.book(
  id int primary key,
  title text
);

in the GraphiQL explorer, you should see

if you don't see that, please include the results of the following queries in your response so I can help debug

Role search pathes

SELECT
	r.rolname,
	d.datname,
	sc.v
FROM
	pg_db_role_setting rs
	LEFT JOIN pg_roles r
		ON r.oid = rs.setrole
	LEFT JOIN pg_database d
		ON d.oid = rs.setdatabase,
	unnest(rs.setconfig) sc(v)
where
	sc.v ilike '%search_path%'

Supabase CLI version

supabase --version

pg_graphql local version version

select * from pg_available_extensions where name like 'pg_graphql'

(screenshot of) docker image versions

docker ps

great!

the only curious thing is the nulls coming back from your query -- assuming not expected? the supabase --version is 1.50.4. pg_graphql version is 1.1.0.

that all looks great. the nulls aren't an issue
let me know if you run into anything else


Should we remove explicit IDs from our translation strings?

At some point in the past, setting an ID on internationalization strings was mandatory. Consequently, all our strings have an id defined that we set manually.
This changed at some point, and today if you omit the id, formatjs will automatically generate a hash. The docs actually recommend relying on that hash rather than providing explicit IDs:

During extraction, we'll preserve explicit declared IDs and insert a hash as an ID for messages without. We recommend against explicit IDs since it can cause collision.

I'm wondering whether we should adapt our practices. So far, here are the arguments I see:
Pros for removing ids

Will facilitate developer's lives when writing new strings (one less thing to worry about)
Solves the duplicates problem, no need to look in en.json / copy-pasting any more when re-using strings

Cons for removing ids

The id often gives some context to translators about where this string is coming from (eg. when they see order.expired, they understand that the string Expired refers to an order). This could be solved by relying on the description field that is normally meant for that, but that would require some adaptations to our files format.
Would completely reset all our translations if we enforce it on existing strings. Though there may be a clever way to notify Crowdin about the move and makes sure it re-uses existing strings.
We sometimes use keys for grouping (eg. Expense.Status.Approved, Expense.Status.Rejected, etc). That's nice when reviewing the file.

Conclusion
No strong conclusion for me so far. It looks like removing ids would bring many benefits, and we probably can find workarounds for most of the cons.

Thanks for posting this issue. I vote for the removal of the ids; it makes sense and keep things simple. 😉

Would completely reset all our translations if we enforce it on existing strings.

Clear blocker to remove ids for past entries for now. On the other end, ok to already skip ids for new strings.

Thanks for the feedback! So for now, it seems that the next steps could be:

Relax our policy on IDs today by not requiring them for new strings
Find out if there's a way to migrate existing strings without losing all the translations. I suspect something like this may be possible with a process like this:

Merge Crowdin PR to make sure we're in sync, pause all translations and PRs merge
Open a new PR that migrates all the IDs, in en.json but also in locale files (fr.json, es.json, etc.). Achieving so might require a bit of work.
On Crowdin's website, manually upload the updated language files for all locales
Resume normal activity

Closing this as it seems we concluded with https://github.com/opencollective/opencollective/issues/4697#issuecomment-921858385


Missing images in documents

Documents in docs/component have some images missing. The problem is with using relative path "../../images/" instead of correct "../images".

Should be working now.
What browser are you using?
Both Chromium Version 53.0.2785.143 and Chrome Mobile Version 54.0.2840.68 displayed the images without problem before the fix.
Local documentation using mkdocs serve now has an incorrect path for images, I will have to dig into that.

Chrome 54.0.2840.71, Mobile Chrome 54.0.2840.68 and Microsoft Edge 38.14393.0.0

Can you link me the src of an image not being displayed?

For examples: https://github.com/AoDevBlue/MaterialValues/raw/master/MaterialValues/images/components_bottomnavigation_spec_fixed2.png

Oh, I see!
The docs/ folder is only used to generate the documentation available here.
Thank you for the information, I added a disclaimer here.

Thank you for a clarification.


Add support to specify kid field in non jwk url alg types

The problem faced currently?
As space cloud supports parsing JWT tokens with multiple secrets. It tries to parse token with all the available secrets by which it takes a performance hit, it will be great if the token specifies which secret to use to parse the token.
How can we solve it?
JWT standard supports providing kid in the header of JWK token, so while adding a secret in space cloud we can also take a kid param. While parsing token we will look for a kid header & if the kid is present in token we try to use the specific secret to parse the token.

If you want this feature to be implemented, give it a thumbs up reaction, so that we can determine which features are important to you.
👍

Done


apps: make use of OSSL_STORE for generalized cert and CRLs loading

This generalizes the load_certs(), load_cert(), and load_crls() functions used by the CLI apps ca, cmp, cms, ocsp,
pkcs12, s_client, s_server, smime, verify, and x509 taking advantage of the OSSL_STORE mechanism.
This allows loading not only in PEM format but also in DER and PKCS#12 format and loading also from URIs.
It also enables using passwords for certificate input files, using a new -passcerts option of pkcs12
and, as far as it makes sense, any existing password input options for other apps.
This supersedes the core of my old PR #4930.
This is also strongly related to #12643.
Checklist

[x] documentation is added or updated
[x] tests are added or updated

I think this finalizes a lot of what I did in #7390.  When this is merged, I'll revisit that one to see what remains.

I think this finalizes a lot of what I did in #7390. When this is merged, I'll revisit that one to see what remains.

Ah, I was not aware of that PR!
At times I think it would be good to have a mechanism that points out overlaps between existing PRs,
or even better, that could be used to detect if a planned change could overlap with existing PRs.

Ah, I was not aware of that PR!

No matter, I'm actually glad to see someone else doing this, that indicates the desire for this change.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

This is ready to be merged

This is ready to be merged

Done - thanks @levitte

At times I think it would be good to have a mechanism that points out overlaps between existing PRs,
or even better, that could be used to detect if a planned change could overlap with existing PRs.

gerrit code review will link to changes that conflict or are "related to" the change in question.  (I am not 100% sure of the details of what determines those relationships, and it might be configurable, but I think that the conflicts are actual 'git merge' failures and the "related"ness is parent/child relationships.

At times I think it would be good to have a mechanism that points out overlaps between existing PRs,
or even better, that could be used to detect if a planned change could overlap with existing PRs.

gerrit code review will link to changes that conflict or are "related to" the change in question.

This sounds interesting!
Are there plans to integrate this with GitHub or OpenSSL?


Update cx-Freeze dependency

What does this address?
Updates cx-Freeze from 6.15.10 to 6.15.16.
Fixes the failing action here: https://github.com/Owen-Splat/LAS-Randomizer/actions/runs/10075768709/job/27854724650
> python setup.py build
Traceback (most recent call last):
  File "setup.py", line 2, in <module>
    from cx_Freeze import setup, Executable
  File "C:\hostedtoolcache\windows\Python\3.8.10\x64\lib\site-packages\cx_Freeze\__init__.py", line 12, in <module>
    from .command.build_exe import BuildEXE as build_exe
  File "C:\hostedtoolcache\windows\Python\3.8.10\x64\lib\site-packages\cx_Freeze\command\build_exe.py", line 13, in <module>
    from cx_Freeze.freezer import Freezer
  File "C:\hostedtoolcache\windows\Python\3.8.10\x64\lib\site-packages\cx_Freeze\freezer.py", line 32, in <module>
    from .parser import ELFParser, Parser, PEParser
  File "C:\hostedtoolcache\windows\Python\3.8.10\x64\lib\site-packages\cx_Freeze\parser.py", line 28, in <module>
    lief.logging.set_level(lief.logging.LOGGING_LEVEL.ERROR)
AttributeError: module 'lief._lief.logging' has no attribute 'LOGGING_LEVEL'
Error: Process completed with exit code 1.

How did/do you test these changes?
I re-ran the action with the change and it ran successfully: https://github.com/CovenEsme/LAS-Randomizer/actions/runs/10076999231

Sorry, I didn't see this and have already updated all dependencies based off your Discord message. Closing


Feedback Tool - Mark as fixed/delete action drop-down

As a Super User I want to have access to an action column added to the feedback tool so that I can archive it or delete feedback.
Acceptance criteria: Super Users can select an action from a dropdown menu to either delete feedback (hard delete) or archive it.
When the user selects delete feedback comment will be deleted permanently.
Superusers can click a button that says "View Archive" and can see the archived feedbacks.
When the user selects “Archive,” then "Archived” text will appear. Feedback can still be deleted.
Link to prototype:
https://xd.adobe.com/view/0102c78c-586a-4e00-8945-86d50f8a1af6-5451/screen/f96d7acf-296d-4cf5-b55c-7b6febe90d3d
NOTE: please consider "Mark as resolved" instead as "Archive"

Hey team! Please add your planning poker estimate with Zenhub @aforde-aot @djnunez-aot @jadmsaadaot @saravanpa-aot @VineetBala-AOT

There was some slight change to this card that might confuse users. If the "Mark as Resolved" drop-down archive the feedback (and applies to ideas as well as issues, which cannot technically be "resolved") it would make more sense to change this option in the drop-down to "Archive".
@djnunez-aot will make that update.


docs: translate hello world page

Translating Hello World page of the Docs section to Gujarati.

@3sanket3 and @ron4ex, need your feedback on a few words, e.g. JavaScript is not translated into Gujarati જાવાસ્ક્રિપ્ટ. Just wondering which way do you think we should keep, for language or library names?

રિએક્ટ or React
જાવાસ્ક્રિપ્ટ or JavaScript

We should go with React and JavaScript rather than their Gujarati translations. This is because we want to preserve English words for APIs like React.Component. So let's just consider them as programming jargon and keep them as they are.
This also applies to other words like Node, DOM.

Make sense. Thanks, @ron4ex, for the confirmation.


Add the destination in the gomoddirectives text

Right now the error printed is
go.mod:11:1: replacement are not allowed: golang.org/x/term (gomoddirectives)
replace golang.org/x/term => github.com/ldemailly/term v0.0.0-20240809182630-68dd89eaaf9e
^

for
replace golang.org/x/term => github.com/ldemailly/term v0.0.0-20240809182630-68dd89eaaf9e

it would be a lot more useful if it was
go.mod:11:1: replacement are not allowed: golang.org/x/term => github.com/ldemailly/term (gomoddirectives)

so exclude rule could be written based on trusting the destination of the replace and not the source
originally https://github.com/golangci/golangci-lint/issues/4896

Your use case is related to a specific context, I'm not sure about the balance between the value and the maintenance of this kind of option.
I can understand why you want that but it's also the result of shared configuration (that I considered a bad practice, it's my opinion) and a one-off action (that you can allow temporarily).
I don't see in which other context this option is useful but I can miss something, so I will wait for other user feedback.

how is the error message having only half of the information a specific context issue? what is the harm if the message had the other half like I'm suggesting?

It's the same thing for the message.
For me, an option is the best approach to handle that instead of relying on something that is not inside the linter.
The "destination" is only useless in the large majority of the cases.

(ps yes this is not the golangci-lint's repo but that's where it's used)

You must stop with your subtext immediately.
I can understand frustration, and we can disagree and discuss, but what you're doing isn't a discussion.
I tried to understand your problem, I spent time on it, I tried to provide an answer that fits your need and my vision of the solution, so please change your approach.


fix resize issue and commit the dist

Fix resize issue

Want to flag that this is a problem I've run into as well. Would be keen to get this merged into mainline!

Sorry. I should have replied to this soon.  I'll close this PR as the code that fix this is found in the issue #54


[5.3] Unify join and builder syntax

This is a massive cleanup of the join clause (~200 lines of production code removed). The idea is to extend the query builder and reuse its functionality instead of duplicating it. This has multiple benefits:

no need to duplicate the logic for where clauses
simplified join compilation (by reusing where clause compiler)
unified syntax between join clause and query builder (i.e. "=" operator is now optional, access to additional clauses like whereRaw, whereSub, ...)

The only breaking change is the removal of $where boolean parameter in the on clause and the removal of some public JoinClause properties.

Would there be any issues with using methods available on Builder that wouldn't necessarily be valid in a join statement? I'm thinking of methods like select, orderBy, or groupBy.

They will be ignored, same as with nested where... Currently nothing is stopping you from writing:
User::where(function($query){
    $query->orderBy('foo');
})->get();

I first wanted to extract where builder in a separate class and use it for nested wheres & joins, but it would make merging 5.2 -> 5.3 a nightmare.
The only problem is if you introduce non-where bindings - the query would fail in both cases.

Totally agree with @acasar in this regard. Seems a really good feature to have in 5.3

Looks good. Thanks!


Use multi line for trait bounds when they don't fit in a single line

Closes #1168 and closes #1642.
This PR is a simple workaround for the time being. After the discussion in https://github.com/rust-lang-nursery/fmt-rfcs/issues/80 settled, we should be able to add options and whatnot to rewrite_trait_bounds.

Added a test for #1168.

Closing in favor of #1647.


HDFS-15561. Fix NullPointException when start dfsrouter

NOTICE
dfs.federation.router.monitor.localnamenode.enable is true by default,
but it always add it to namenode heartbeat service, so the log file is full of exception information.
java.lang.IllegalArgumentException: java.net.UnknownHostException: null
	at org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:447)
	at org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:171)
	at org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:123)
	at org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:95)
	at org.apache.hadoop.hdfs.server.federation.router.NamenodeHeartbeatService.getNamenodeStatusReport(NamenodeHeartbeatService.java:248)
	at org.apache.hadoop.hdfs.server.federation.router.NamenodeHeartbeatService.updateState(NamenodeHeartbeatService.java:205)
	at org.apache.hadoop.hdfs.server.federation.router.NamenodeHeartbeatService.periodicInvoke(NamenodeHeartbeatService.java:159)
	at org.apache.hadoop.hdfs.server.federation.router.PeriodicService$1.run(PeriodicService.java:178)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:514)
	at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:300)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
	at java.base/java.lang.Thread.run(Thread.java:844)
Caused by: java.net.UnknownHostException: null

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 37s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
34m 33s
trunk passed

+1 :green_heart:
compile
0m 41s
trunk passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
compile
0m 37s
trunk passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

+1 :green_heart:
checkstyle
0m 27s
trunk passed

+1 :green_heart:
mvnsite
0m 40s
trunk passed

+1 :green_heart:
shadedclient
15m 18s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 38s
trunk passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
javadoc
0m 54s
trunk passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

+0 :ok:
spotbugs
1m 13s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
1m 12s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 30s
the patch passed

+1 :green_heart:
compile
0m 31s
the patch passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
javac
0m 31s
the patch passed

+1 :green_heart:
compile
0m 29s
the patch passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

+1 :green_heart:
javac
0m 29s
the patch passed

+1 :green_heart:
checkstyle
0m 17s
the patch passed

+1 :green_heart:
mvnsite
0m 31s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
14m  1s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 33s
the patch passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
javadoc
0m 50s
the patch passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

-1 :x:
findbugs
1m 14s
hadoop-hdfs-project/hadoop-hdfs-rbf generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

_ Other Tests _

+1 :green_heart:
unit
8m 28s
hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 28s
The patch does not generate ASF License warnings.

86m 50s

Reason
Tests

FindBugs
module:hadoop-hdfs-project/hadoop-hdfs-rbf

Load of known null value in org.apache.hadoop.hdfs.server.federation.router.Router.createLocalNamenodeHeartbeatService()  At Router.java:in org.apache.hadoop.hdfs.server.federation.router.Router.createLocalNamenodeHeartbeatService()  At Router.java:[line 558]

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2284/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2284

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux ccda73ed3592 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 0d855159f09

Default Java
Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

findbugs
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2284/1/artifact/out/new-findbugs-hadoop-hdfs-project_hadoop-hdfs-rbf.html

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2284/1/testReport/

Max. process+thread count
2844 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-rbf U: hadoop-hdfs-project/hadoop-hdfs-rbf

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2284/1/console

versions
git=2.17.1 maven=3.6.0 findbugs=4.0.6

Powered by
Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

@lamberken  are you still working on this issue? If not can I take it on? Thanks!

@lamberken are you still working on this issue? If not can I take it on? Thanks!

Hi @fengnanli, closed the patch.


Fix: Ethereum extrinsic size is accounted twice for proof size

Ethereum extrinsic size is accounted twice for proof size, this PR substracts that cost once.

IIUC, the Ethereum extrinsic size is accounted for twice:

Additional Gas is applied based on the Ethereum transaction size, which is then converted through GasWeightMapping.
The size is also accounted for in SelfContainedCall's CheckWeight.

Is my understanding correct? Since SelfContainedCall isn’t designed to be used exclusively with pallet-ethereum, unconditionally subtracting it from actual_weight could result in unexpected behavior. Should we consider adding conditions or refining the logic here?

https://github.com/polkadot-evm/frontier/pull/1490#issuecomment-2283599749 Check this for some deep thought behind this change. I need more time to figure out if this is the best solution.


Proposal: Diagram control with Lottie animation

Proposal: Network/Graph/Flow-Chart visualization with Lottie animation

Summary
A Win UI control that inspire creative presentation of complex and data-rich information using a wide range of Fluent Design features: composition, animation and material
Rationale
Currently there is no WIN UI diagram control similar in features to that of GoXam.
There are a few open source options: NetworkView, GraphX, etc
None of the existing diagram control, commercial or open-source, takes advantage of the opportunities for modern design
We would like to challenge Microsoft to inspire us how creative integration of Lottie animation upon clicking on node, creative composition layout, and fluent design will lead to the next generation of effective and engaging information communication.

I would like to see an out-of-box control with similar capabilities as Telerik's Diagram control.

@ryandemopoulos could u pls feedback what kind of information will help u to justify how to move forwards this feature requests out from freezer in feature tracking to next step?

Thanks for filing this; sorry the delay in responding.
Controls like this would be awesome to add to WinUI; however, they also represent a substantial investment that we probably can't take on any time soon just due to competing priorities.  (the investment is both in the designing of the control, as well as the implementation)  My sense is that they are also somewhat niche compared to general-purpose controls like Numberboxes and Input Validation, etc, which makes the ROI harder to justify compared to the other stuff we're working on at the moment.
For really complex controls like this we usually focus more on enablement of middleware & 3rd party control vendors to be able to create this stuff.  For example, investment in things like this: https://github.com/microsoft/microsoft-ui-xaml/issues/686#issue-443011730  (was just recently moved to the Back Burner, which is a staging ground for eventual implementation).  Things like 3DModelViewer will at least enable folks to create these experiences in the absence of us creating full E2E solutions for diagramming, charting, etc.
For now, I'm going to keep this idea around in the freezer.  If we see an uptick in interest or need for this work, I'd be happy to chat about thawing this item down the road.

Another reference for diagram control: https://www.syncfusion.com/uwp-ui-controls/diagram


WIP: Adds role_allows_session_tag

Description
Change allows to control via parameter if sts:TagSession statement is added into role assume document
Motivation and Context
The change is required for a lot of people using GithubActions and relying on this repository structures for controlling IAM. Without this additional workarounds are required to fully use the solution.
Fix #152
Breaking Changes
There are no breaking changes
How Has This Been Tested?

[ ] I have tested and validated these changes using one or more of the provided examples/* projects

@lorengordon I think that is exactly what we should be doing! Spot on :) And since we are on the subject should we not also update master/modules/iam-assumable-role/main.tf#L36 with trusted_role_actions ?

Makes sense to me, but I'd defer to Anton. I feel like that's probably the only change needed, and the rest can be undone?
Ok - lets wait for input from Anton - then it would be just making a new small patch PR. For the rest I will close the PR and we can comment on the linked issue that the solution is there out of the box

I agree, let's make it trusted_role_actions as variable with current value as default.


Add description to ASO role assignment

https://tools.hmcts.net/jira/browse/DTSPO-12611
This change:

Adds a description attribute to the role_assignment resource for ASO, to allow two clusters to manage the resource by including the cluster number in the name.

Failing build example: https://dev.azure.com/hmcts/CNP/_build/results?buildId=345707&view=logs&j=ae32586c-a9fb-5009-45b6-4375cbbc84da&t=6bfac74f-3a8d-5161-9f74-e350fd8357c8
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

@thomast1906 updated this to be something less tricky, description will force replacement if it's changed also, and allows us to distinguish between 00/01 resources. Any thoughts?


Make the link clickable

I didn't notice it as part of #125, as it shows fine on GitHub, but the Jekyll Markdown formatting doesn't make the url automatically a link.

It's a simple fix, so I am going to merge it.


1.1 Implementation

Improvements and bugfixes for 1,1!

Just need to get a final once-over. On target for the 11th.


Use Azure to build for macOS and Linux

Workaround the backlogs for Travis CI and CircleCI by switching macOS and Linux builds to Azure. Ensure that Azure is able to upload the packages as well.

Checklist

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

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


[CI][Go] The verify-rc-source-integration-macos-conda-amd64 job fails building cdata_integration for go

Describe the bug, including details regarding any error messages, version, and platform.
The following job:

verify-rc-source-integration-macos-conda-amd64

Has been failing for a long time with:
~/work/crossbow/crossbow/arrow/go/arrow/internal/cdata_integration ~/work/crossbow/crossbow/arrow/go ~/work/crossbow/crossbow/arrow ~/work/crossbow/crossbow
package github.com/apache/arrow/go/v15/arrow/internal/cdata_integration: build constraints exclude all Go files in /Users/runner/work/crossbow/crossbow/arrow/go/arrow/internal/cdata_integration
Failed to verify release candidate. See /var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/arrow-HEAD.XXXXX.y35Ie57h for details.
Error: Process completed with exit code 1.

It is being built with TEST_INTEGRATION=1 so the following is currently executed and is where it fails:
  pushd go
  go get -v ./...
  if [ ${TEST_GO} -gt 0 ]; then
    go test ./...
  fi
  go install -buildvcs=false ./...
  if [ ${TEST_INTEGRATION_GO} -gt 0 ]; then
    pushd arrow/internal/cdata_integration
    case "$(uname)" in
      Linux)
        go_lib="arrow_go_integration.so"
        ;;
      Darwin)
        go_lib="arrow_go_integration.dylib"
        ;;
      MINGW*)
        go_lib="arrow_go_integration.dll"
        ;;
    esac
    go build -buildvcs=false -tags cdata_integration,assert -buildmode=c-shared -o ${go_lib} .
    popd
  fi
  go clean -modcache
  popd

See: https://github.com/apache/arrow/blob/main/dev/release/verify-release-candidate.sh#L914-L942
Component(s)
Continuous Integration, Go

This is affecting the maintenance branch for 15.0.0 but it does seem to be an issue with the verification script and doesn't seem to be a blocker for the release in my opinion.


feat: generate advertisement data dynamically

Modified the Bleno.startAdvertisingWithEIRData signature to accept a function that returns the payload, instead of just the payload itself. Backwards compatibility is preserved.
The payload function is called at intervals of 1000ms, and is called with the previous payload as an argument.

Closing in favour of https://github.com/GRITSpot/bleno/pull/2


[Plugin][FR]: Publish to Local Directory

Issue validation

[X] I checked the issue to prevent duplicate

Is your feature related to a problem ?
I know the name of the plugin is Obsidian "GitHub" Publisher, but it would be great to have an option to export it locally to a directory. I plan on hosting via other platforms, for which I need to process the notes before uploading. Which I plan to do via Windows PowerShell.
The plugin already does the majority of work of formatting the notes. So, if the plugin could have an option to export to a local directory, it would be fantastic!
What solution do you want to see ?
An option to export to local directory.
Describe the alternative you've considered
NA
OS
Windows, Linux
Anything else?
NA
Plugin version
5.7.0
Obsidian version & debug log
SYSTEM INFO:
	Obsidian version: v1.2.8
	Installer version: v1.1.9
	Operating system: Windows 10 Home Single Language 10.0.22621
	Login status: not logged in
	Insider build toggle: off
	Live preview: on
	Legacy editor: off
	Base theme: dark
	Community theme: AnuPpuccin v1.4.2
	Snippets enabled: 9
	Restricted mode: off
	Plugins installed: 27
	Plugins enabled: 26
		1: Tag Wrangler v0.5.8
		2: Templater v1.16.0
		3: QuickAdd v0.23.0
		4: Advanced Tables v0.18.1
		5: Frontmatter Tag Suggest v0.4.1
		6: Natural Language Dates v0.6.1
		7: Periodic Notes v0.0.17
		8: Dataview v0.5.55
		9: Supercharged Links v0.9.6
		10: Calendar v1.5.10
		11: Editor Syntax Highlight v0.1.3
		12: Style Settings v1.0.3
		13: Excel to Markdown Table v0.4.0
		14: Bible Reference v1.6.0
		15: Outliner v4.6.7
		16: Book Search v0.5.10
		17: Media DB Plugin v0.5.1
		18: Minimal Theme Settings v6.3.1
		19: Recent Files v1.3.5
		20: Paste image rename v1.6.1
		21: Github Publisher v5.7.0
		22: ePub Reader v1.0.2
		23: Quiet Outline v0.3.15
		24: Obsidian Git v2.19.1
		25: Excalidraw v1.9.0
		26: Obsidian markdown export v1.0.8

RECOMMENDATIONS:
	Custom theme and snippets: for cosmetic issues, please first try updating your theme and disabling your snippets. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.
	Community plugins: for bugs, please first try updating all your plugins to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community plugins.

As I said multiple time : it's too much complicated to allowing local folder.
It's will be a total rewrite of the plugin and I don't have the time nor the envy to do it.


KUDU-2273: Flink connector for Kudu

closing this..
the connector can be found in https://github.com/apache/bahir-flink/tree/master/flink-connector-kudu


Making it easier to contribute

I've made a few minor changes to make it easier for contributors.

This would close #133

Thanks for closing that one out.
Opps.  That was sent to master.  I'll fix that.  It's helpful to make PR's off of DEV branch.


feat: Update latest images tags to 3.0.0

Update docker-compose examples to use image tags 3.0.0 instead of latest
Closes: #228

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-examples/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[ ] I have fully tested (add details below) this the new feature or bug fix (if not, why?)

Testing Instructions

git clone this pr
follow the instructions from README.md

The docker-compose.original is there intentionally in order to show the difference between the original and modified docker-composes

ok, i can revert those back but then you have to keep track of version from this to the next release? IMO, it is too much burden for developer


docs: add vulnerability report verifier design doc

Description
What this PR does / why we need it:

adds vulnerability report design doc

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Fixes #
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Helm Chart Change (any edit/addition/update that is necessary for changes merged to the main branch)
[x] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] Does the affected code have corresponding tests?
[ ] Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
[ ] Does this introduce breaking changes that would require an announcement or bumping the major version?
[ ] Do all new files have appropriate license header?

Post Merge Requirements

[ ] MAINTAINERS: manually trigger the "Publish Package" workflow after merging any PR that indicates Helm Chart Change

This is a copy of the original doc that was shared on hackmd

Thanks for this good example, and I would update this doc change as well


Question on how to go about using casl + mikro-orm together

Hi, I understand that there is a @ucast/sql package, but mikro-orm also supports MongoDB queries. And that made me think, could we possibly use const { rulesToQuery } = require('@casl/ability/extra') to construct accessibleBy?
If that's the case, would you recommend that people who want to use casl and mikro-orm together go down the rulesToQuery -> mongo operator -> mikro-orm route, or the @ucast/sql -> raw sql -> mikro-orm route?
Thanks

I think the proper way is to use SQL adapter, don't know how good MikroORM at translating MongoDB query to SQL. Anyway, having SQL under the hood can allow to add more complicated operators.


fix: open-autonomy submodule version

fix: open-autonomy submodule version

Please add a make command or docs which do this in the right order


Expand/Collapse not working

I'm using like this:
@Override
    public void onSectionClick(int section) {
        Log.d("SECTION", "CLICKED: " + section);
        if (productsRecyclerAdapter.isSectionExpanded(section)) {
            productsRecyclerAdapter.collapseSection(section);
        } else {
            productsRecyclerAdapter.expandSection(section);
        }
        productsRecyclerAdapter.notifyDataChanged();
    }

Tried with collapseAllSections() still not working

Hi, @witalobenicio. Please remove productsRecyclerAdapter.notifyDataChanged() line. It should work.
When you call collapseSection(section) `expandSection(section)methods your adapter will be notified about changes inside these methods. There is no need to callnotifyDataChanged()method. Moreover, callingnotifyDataChanged()` method will initiate recreating all your sections, thus all your sections will be expanded by default.

Thanks @zhukic it's working now.

Just one doubt? There's a way to maintain the status of section with the notifyDataChanged()?

@witalobenicio No, there is no way.


[Angular/Admin] BOOK-64 More Localization + Profile Picture for Admin Users

@Norhan605 Amazing Job 👍🏻


Create WIKI page for DID/X.509

@talltree added https://wiki.trustoverip.org/display/HOME/X.509+PKD+Interop

comments from v1 draft - closing


hello world:evaluate, bazel Compile problems

When I run bazel build tensorflow/lite/micro/examples/hello_world: evaluate command, hint I ERROR: /home/cc/.cache/bazel/_bazel_cc/8824d82e11d18421e8c81fd1a75e4939/external/tflm_pip_deps_markdown/BUILD.bazel:22:11: no such package '@tflm_pip_deps_importlib_metadata//': The repository '@tflm_pip_deps_importlib_metadata' could not be resolved: Repository '@tflm_pip_deps_importlib_metadata' is not defined and referenced by '@tflm_pip_deps_markdown//:pkg'. But my conda environment contains the importlib_metadata package (importlib-metadata           6.7.0) .  python: 3.9 bazel:5.3.0
I am new to this project. Thank you very much for your help

Resolved, I switched to python3.10


Eventhubs track2 preview one - fix 1

Small fixes of sample code
Fix a small issue in EPH

Can one of the admins verify this patch?


Count error on LfmHelpers.php in PHP 7.2

Due to PHP 7.2 can not count non-countable items it shows error in  LfmHelpers.php on line 395:
count(): Parameter must be an array or an object that implements Countable

Thank you for reporting this. We should fix this before next release. A quick solution will be to set value of php_ini_overrides as an empty array in config/lfm.php.

Fixed in v2.0.0-alpha.


Ability to set root path as passthrough

Hey,
maybe i am missing something, but it seems not to be possible to set the path to "/" and at the same time enable passthrough for "/", so that the root of the Url doen't have to be authenticated.
Am i right, or am i missing something?
Edit:
Forgot to mention WHY this isn't working. When both set to "/" all other routes are unauthenticated too. Although they are not set to passthrough.

Setting path to /  means authenticate all routes. Another way to say this is authenticate all child routes of / including the /. Setting passthrough to /  means do not authenticate any routes.
If you for example want to only authenticate routes starting with /api do something like following:
$app->add(new \Slim\Middleware\JwtAuthentication([
    "path" => "/api", /* or ["/api", "/admin"] */
    "secret" => "supersecretkeyyoushouldnotcommittogithub"
]));

So, it's not possible?
Scenario: I Want / and /service to pass through but any other route behind / like f.e. /test should be authenticated.

You can either list all the folders ie. paths you want to authenticate in the path parameter. Or you can write your own rule class. It just needs to implement RuleInterface and return boolean true if you want to authenticate. Return boolean false if you do not want to authenticate. Use the stock RequestPathRule as an example.

ah, that makes sense!
Thanks


randyridge/subscription findings

various catches to prevent unobserved task exceptions, tried to prevent the exceptions by checking websocket state
See #3891

/AzurePipelines run


Follows and Notifications

As a user, I want to know when a bill, organization, or legislator I'm following does something interesting so I can stay informed and better participate in my community.
Once a user starts following something, updates will appear in a feed on their personal dashboard, shown after login. They can also configure daily or weekly email digests per-topic.
The feed shows all updates, and each item has a viewed status.
Figma Designs
Notes

[x] Remove public checkbox on edit profile, wire up public setting to the modal
[x] Add notification preference to the profile hook. type is null | "daily" | "weekly" | "monthly"
[x] Wire up profile hook to notification preference
[x] Create Follows section on the edit profile page
[x] Add Follow buttons to the bill details page and organization page

[x] Add button to bill details
[x] Add button to organization page

Here are the figma designs: https://www.figma.com/file/oMNmgiqDGTMco2v54gOW3b/MAPLE-Soft-Launch-(Jan-2023)?node-id=3232%3A37232

We made some headway with the backend design. @DevByAthi and @gerlinp

For the newsfeed, actions to display include:
For followed orgs: any time an org adds testimony (new or revised)
For followed bills: 1) any time new testimony is added, and 2) and bill history status change

@gerlinp is going to be picking up the newsfeed page work, as we discussed splitting out the newsfeed from the notifications. Will create a separate ticket to track. This week he's focusing on the frontend components for the page, building off #918

Wonderful!!
On Tue, Feb 7, 2023 at 9:32 PM Alex Ball @.***> wrote:

@gerlinp https://github.com/gerlinp is going to be picking up the
newsfeed page work, as we discussed splitting out the newsfeed from the
notifications. Will create a separate ticket to track. This week he's
focusing on the frontend components for the page, building off #918
https://github.com/codeforboston/maple/pull/918
—
Reply to this email directly, view it on GitHub
https://github.com/codeforboston/maple/issues/502#issuecomment-1421892290,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARANGSF6CGR46JUSNTNC26TWWMATFANCNFSM5XVHSC3A
.
You are receiving this because you commented.Message ID:
@.***>

@mertbagt is currently blocked on building out email templates. We need to decide on the templating system we'll use to generate emails, then can develop the templates in parallel with the backend wiring.

I will be spending a few hours on this on Saturday if anything comes up!
@gerlinp

add getNotifications to DbService to fetch a paginated list of the user's notifications, sorted by most recent
use react-async-hook to call the db service function from the newsfeed page, and render the newsfeed using the data.
You can use the firestore console to manually create notifications for testing, or write a script to do that.

@mertbagt

WIP email template code
Try using handlebars for the email templates.
Ideally we can render the templates in storybook and from the cloud function.
For getting started, feel free to develop with whatever works and we can work together to integrate it

Tracking backend work in #952


cast images to float16 if FLOAT16 is used or image is already float16

#6506
#6378
#4206

I support this direction, but tests are failing

Thoughts on adding DISABLE_FLOAT16, as mentioned by @chenyuxyz in #4206, to upcast all float16 to float32?
Would something like STRICT_FLOAT=1, which forces dtype to be DEFAULT_FLOAT and makes it immutable, be a better approach?


Remove trailing references from ManagedArray and Heap

This is a companion PR to https://github.com/CesiumGS/cesium/pull/8883 that removes trailing references when elements are removed from ManagedArray and Heap.

Thanks for the pull request @lilleyse!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

@IanLilleyT updated

@IanLilleyT added checks to the setters

Merged. Thanks @lilleyse


Fixed: Themes provides link to partymgr in headers (OFBIZ-11703)

(OFBIZ-11703)
removed:  to viewprofile

This can be useful for allowed users, others can't that's all. A message would help, but that's not what did Pierre. He simply removed the possible fonctionnality, closing


"Default target masked." during initialization.. /bin/plymouth missing?

Influx has been running fine, now on all of my devices I'm seeing the same log errors while booting:
 influx  Systemd init system enabled.
 influx  systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
 influx  Detected virtualization docker.
 influx  Detected architecture arm.
 influx  Set hostname to <raspberrypi3-ef93f16>.
 influx  File /lib/systemd/system/systemd-udevd.service:34 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
 influx  Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
 influx  Default target masked.
 influx  Trying to load rescue target...
 influx  You are in rescue mode. After logging in, type "journalctl -xb" to view
 influx  system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"
 influx  to boot into default mode.
 influx  Press Enter for maintenance

If I run journalctl I find this at the end:
Jul 11 16:52:26 raspberrypi3-ef93f16 systemd[96]: rescue.service: Executable /bin/plymouth missing, skipping: No such file or directory
-- Subject: Process /bin/plymouth could not be executed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The process /bin/plymouth could not be executed and failed.
--
-- The error number returned by this process is 2.
Jul 11 16:52:51 raspberrypi3-ef93f16 kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jul 11 16:52:51 raspberrypi3-ef93f16 kernel: brcmfmac: power management disabled

It appears as if the wifi isn't ready, although the device is using it properly in all other respects. One thing to note is that this is running in a docker container, but it's been running fine for months. I'm using the npm influxdb module.
Any thoughts on what this might be?

Turns out this was due to the debian install I was using as the base image for the docker container. Something must have changed. I switched to a different base OS and influx came up fine.


Support adding grammars at runtime

Hello!
I'm the author of vscode-language-babel and I'd love to be able to support configurable tagged template literal grammar extensions. In order to do this, I'd need to be able to add grammars based on the users configuration instead of in the contributes.grammars field.
I've noticed the vscode-textmate library used within vscode has the methods I would need but they don't seem to be public. Would a feature like this be possible to expose to extension authors?

@alexr00 would it be possible to get an update on this issue?

would love to see some movement or workaround for this

Ah man @vscodetriage-bot! This is a pretty advanced feature. The average user will have a hard time foreseeing the benefits such a feature could offer.
I'm talking to a bot. 🤦

yeah that sucks. we have to round up 20 votes from vscode grammar extension devs...


bug with moving comma at the end of a line

Follow-up from Issue #102
This is incorrect behavior. The comma at the end of the line should not be moved.

The current behavior is clearly buggy, but I wonder if Standard Clojure Style should remove commas at the end of lines entirely? Not sure of a case where it makes a lot of sense to keep a comma at the end of a line.

I wonder if Standard Clojure Style should remove commas at the end of lines entirely?

I am leaning toward "Standard Clojure Style should treat eol commas as whitespace and remove them"

Yes, and imo this aligns with the Clojure Style Guide. The "Optional Commas in Maps" section has a map with each entry on separate lines and no commas, and a map with both entries on one line and a comma between. Regardless of thoughts on the latter, the former indicates that commas shouldn't be at the end of the line.

Fixed with PR-107


Web page error after modifying the sample program

I'm not very familiar with compiling to web pages.
I can run the sample program normally, but as long as I modify the title or any string in app.rs, the browser will report the following error, and it will go blank and cannot display anything. I guarantee that the modified content is correct, because everything runs normally on this machine. But it doesn't work properly on the web page. I can even open the wasm link directly and it is normal.
I have tried before
http://<IP_ADDRESS>:8080
http://<IP_ADDRESS>:8080/index.html
http://<IP_ADDRESS>:8080/index.html#dev
The results are all the same.
error message
Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/html". Strict MIME type checking is enforced for module scripts per HTML spec.
The resource http://<IP_ADDRESS>:8080/eframe_template-a5ff6bdc28275b99_bg.wasm was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate as value and it is preloaded intentionally.

dev tools -> application -> clear site data should fix this. not sure what exactly goes wrong in the service worker, haven't been able to reproduce

I've been able to get around this by commenting out the fetch eventListener code in sw.js, haven't had time to debug why (I'm on firefox/linux).

I had the same problem as OP and have a bit more information.
I had the same error message.  To make sure it wasn't something I had done, I cloned eframe_template and built it as is.  The first error message was complaining about eframe_template_.js.  The second was complaining about the .wasm file.
What I learned is that when I did a hard reload, it would all work.  When I made a change and trunk rebuilt and told the app to reload, it pulled up an index.html which had a different hash in the file name.  I think that originally that file did exist, but when I cleaned everything up (trunk clean) and removed the dist directories, it was gone and was not regenerated.  In fact, no files in the directory (including the target directory) referenced the hash.  But again, if I reloaded (because of a change or just by pressing Ctrl-R) it would revert to that hash, which didn't exist and result in a blank gray screen.
Since the file with that name didn't exist, it looks like trunk just served my index.html as text/html.  This is what caused the first error message.  It was trying to interpret my index.html as javascript, seeing that it was text/html, and refusing.
Following @amPerl's advice, I brought up the dev tools, selected the "Application" tab at the top, clicked on "Storage" (for me it was not selected by default), and then selected "Clear site data".  I don't remember if I just reloaded or hard reloaded at that point, but then things started working.
I wasn't able to figure out where it was getting the bogus hash from, but based on @amPerl's comment, I guess the service worker must have a reference in a cache somewhere which the "Empty cache and Hard Reload" option on Chrome's reload button did not clear.
So far, the problem hasn't recurred, but I haven't done much testing (or much development) since the fix.  If I figure out what triggered in the first place, I'll report back (though there's a lot I don't know about all of this, so we'll see if I can figure anything out).
I'm not sure what my original trunk version was, but I upgrade while debugging and it now reports 0.19.2.
Outside of the eframe_template directory, rustc reports:
$ rustc --version
rustc 1.77.2 (25ef9e3d8 2024-04-09)
In the eframe_template directory, it reports:
$ rustc --version
rustc 1.76.0 (07dca489a 2024-02-04)
(because of the rust-toolchain file).
I've been testing with eframe_template version: ab640bea8
Hope that helps.

Hi, more information that partially relates.  Upon a fresh clone of this repo, I was not having success with trunk serve of the template site locally <IP_ADDRESS>:8080.  I would also get stuck on just the gray loading screen and spinny arrows.  The F12 devtools --> Debugger panel would show problems with retrieving resources and unable to confirm sha384 for resources.
After much digging, I'm pretty sure my issues are related to the latest Firefox 128.0, and the "filehash" mentioned above, although I'm having some trouble pinning it down exactly (I'm not up to speed with everytihng needed here yet).  I sort of got the site to load via a different solution from above and sharing since I was not finding the following information elsewhere:
In developer tools, under debugger the main error I keep getting is "NetworkError .. unable to load", this was due to no match on the SHA384 of embedded <script>  _inline code_ </script>  in index.html.
I tried but failed:

F12, clear local storage/cookies and or Ctrl+R / Ctrl+F5.
Faking the <script integrity=sha384-___ crossorigin="anonymous> from the expected sha384.
Moving the index.html inline script serviceWorker .. window.addEventListener('load'.. 'sw.js. ..) into a separate load.js and generating a integrity sha384, as per this dev example.
Did not want to remove the security by allowing CORS from any and all subdomains.
use of url #dev did not seem to change the behavior -- i.e. still didn't work.
Compiling for Debug or Release didn't seem to change anything.
A few related posts etc around the web when searching for related topics.

What did work

I got varied results between Firefox Private mode or normal, sometimes the template site would load in private (could see the pattern), but definitely wouldn't load in normal mode.
I was able to just open the site via the direct url: http://<IP_ADDRESS>:8080/eframe_template-3b95fdc63b82a9f0_bg.wasm, as per contents of the trunk built dist/ folder.
Loading the website under IPv6, [::1]:8080 and hitting "trust this and subdomains for [::1]" -- from there IPv6 would always work.
Back on IPv4 in my case (but I don't understand it yet) was under F12 devtools --> Application --> Service Workers, I hit the Unregister button and it seems the site now loads fine every time.  However the Service Worker no longer shows up:

Ubuntu 22.04, rustc 1.76.0, Firefox 128.0.  Developing, using terminal from VSCode 1.91.1.

solved by disabling filehash in Trunk.toml
[build]
filehash = false

Sorry for being away for so long. In fact, I later used local development and then deployed it to the server, and it didn't have much impact.
And I can't reproduce this problem now.


Compatibility with 2015 TVs?

Hi @kdschlosser , first of all, thanks for your job, its amazing :)
I'm user of 2015 tv (43j5500) and the script doesn't works for this version.
Can you tell me how we can pair with the tv please?
I try with --host x.x.x.x but doesn't works, is needed some special flag to this version?
If the last version doesn't works fine with this tv, do you know what version or from which date can I download a compatible version please?
PS. I haven't executed RUNME.py because this is a generic compatibility version, but if you need it please tell me.
Thank you.

you need to use the develop branch. This library is very much still in development so the command line bits are not functional just yet.
if you follow what is going on in #106  you will know when I update the code in the develop branch. the RUN_ME.py is going to run all kinds os tests between the library and the TV and report anything that is not running properly and any errors that may come about.


GLEE Pro for video config files

Greetings,
Can you please share the GLEE Pro config files for video tasks in order to reproduce the results reported?
Thanks and Regards

@iFighting @wjf5203 @wjf5203 Any update on this?


pick pick #41292 #41589 #41628 #41743 #41845 #41857 #41902 #41601 #41667 #41751

Proposed changes
pick #41292 #41589 #41628 #41743 #41845 #41857 #41902 #41601 #41667 #41751

run buildall


Bug in creating Private Preview release plan

Yoga and I were helping the Network security perimeter team this morning.  I created a Private Preview release plan for them but I am getting an error when I access the API readiness milestone app.
Triage work item:  https://dev.azure.com/azure-sdk/Release/_workitems/edit/18608
Release plan work item:  https://dev.azure.com/azure-sdk/Release/_workitems/edit/19044
There does not seem to be an API Spec work item created for the release plan.

The cloud flow responsible for creating this Triage work item failed with error message: "The field 'Service Lifecycle' contains the value 'In Development' that is not in the list of supported values"
Looking to see what happened

Found the error. Fix and deployed to DEV.

Deployed to Prod


--lock-session doesn't work with a bookmark

$ ./pgweb --lock-session --bookmark=server
Please provide connection url

$ cat .pgweb/bookmarks/server.toml
url = "postgres://postgres:postgres@localhost:5432/postgres"

Works without --lock-session.

Thanks will take a look

There's also a --lock-session related question in #195. Seems like --lock-session works with --url only.

This is fixed in master. Please give it a try.

I have never compiled before so I tried following (on Debian) and got the build error shown below.
cd workspace
git clone https://github.com/sosedoff/pgweb.git
cd pgweb
sudo apt-get install golang-go
export GOPATH=~/.gocode
export GOBIN=$GOPATH/bin
export PATH=$GOPATH:$GOBIN:$PATH
make setup
make dev

main.go:12:2: cannot find package "github.com/sosedoff/pgweb/pkg/api" in any of:
	/usr/lib/go/src/pkg/github.com/sosedoff/pgweb/pkg/api (from $GOROOT)
	/home/kiblomqv/.gocode/src/github.com/sosedoff/pgweb/pkg/api (from $GOPATH)

Im not sure why you're getting the error, perhaps older version of go? Anyways, to simplify testing - i attached a binary that you could try.
pgweb_linux_amd64.zip

Thanks! I got it working and the fix is working too.
Here's the instructions if somebody else is struggling with the build. Read the installation instructions from https://golang.org/doc/install. I did the following steps:
wget https://storage.googleapis.com/golang/go1.7.3.linux-amd64.tar.gz
sudo tar -C /usr/local -xzf go1.7.3.linux-amd64.tar.gz
export PATH=$PATH:/usr/local/go/bin

mkdir -p $HOME/workspace/go
export GOROOT=$HOME/workspace/go
export GOPATH=$HOME/workspace/go
export PATH=$PATH:$GOROOT/bin

go get github.com/sosedoff/pgweb
cd workspace/go/src/github.com/sosedoff/pgweb
make setup
make dev


Use standard.js for code formatting

By using a standard set of JS formatting conventions, forks and mirrors of pepperoni will be less likely to run into merge conflicts every time they pull from the pepperoni upstream.
http://standardjs.com/

I'm often declaring vars and then destructuring in blocks below, so apparently I can't use standard.
e.g.
let a, b;

if (cond1) {
  const c = (something)
  [a, b] = (whatever) // borked
}

@emmby thanks for the suggestion. StandardJS looks mostly okay, but it has some opinions we simply can't agree with, e.g. no semicolons.
Its relentless no-customisation philosophy doesn't really suit us either - many users of Pepperoni will want to adapt the code style to their organisation's shared conventions, and we want to enable that.
That said, we could have a review of our .eslintrc and see if we could replace much of it with a default preset - this one is something I've written and upgraded from the pre-preset era :)

The nice thing about using an existing standard instead of inventing your own is that it's easy for everyone to use.  Standardjs has an ecosystem of tools built around it such as https://github.com/maxogden/standard-format.  With standard and standard-format, it's easy for anyone to 1) verify their code style is consistent (and build that check into tests), and 2) reformat it if necessary.
In addition, since pepperoni is a starter kit rather than a library, it's expected that users will be writing their own code in coexistence with pepperoni's code.  You're unlikely to get everyone who uses pepperoni to use your particular styling rules, which means that very pepperoni-based codebase is going to have a mix of pepperoni styles and other styles.  This means that everyone who wants to use pepperoni will run into issues when they pull new functionality from pepperoni.
While you obviously can't solve this for everyone who uses pepperoni, you can use an existing, popular standard so that anyone who uses that standard will have a smooth ride.  Using custom style rules guarantees that no one will have a smooth ride :)
If there's a different standard you want, that's fine too.  I just encourage you to pick the one that's most popular and meets your needs so that the widest swath of your community will be able to pull in all the great updates in pepperoni.


Fixes a bug in writetable's append parameter.

Previous to the fix, the following resulted in an error:
using DataFrames
df = DataFrames.DataFrame(a = @data([1, 2]))
filename = "testme.csv"
isfile(filename) && rm(filename)
writetable(filename, df, append = true)
writetable(filename, df, append = true)
ERROR: LoadError: KeyError: key "Column names don't match names in file"
not found
The changes in abstractdataframe/io.jl resolve the issue.
A test for this particular case has been added in test/io.jl

The tests from statsmodel.jl fail which was unaffected by my changes. Any comments/reviews welcome.

Would be nice if this bug could be fixed soon ...

apologies @pfarndt I did not realise that @nalimilan had reviewed this and had forgotten about the issue.
after reading @nalimilan's reviews it seems that I'll need to get back to the code and make improvements before I resubmit. @nalimilan is this codebase still relevant given the grand changes to DataFrames? I'll need to fetch the latest changes and see if the issue persists. I should be able to look into it during the weekend.

According to https://github.com/JuliaData/DataTables.jl/issues/10 it seems like writetable is being replaced with CSV.writetable - @pfarndt, would CSV.jl work for you?

CSV.jl works for me - however writeable as some extra code that in case one appends rows to a file

checks the identity and order of the column names
automatically outputs a header in case the file is empty

This becomes handy if one aggregates results in a cvs/tsv file. Would be nice to have this in CSV as well.

Please file an issue in CSV.jl then.

readtable writetable are now deprecated.


fix anchor tags for PyPI description

I believe there is a solution mentioned towards the bottom of the page here: https://github.com/pypa/readme_renderer/issues/169

this worked! however, there are still a few more cases of broken anchor tags on page. go through the entire page and fix.

I THINK I got all of these...


Metadata 2

Codecov Report

Merging #151 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #151   +/-   ##
=======================================
  Coverage   92.53%   92.53%
=======================================
  Files         139      139
  Lines        2250     2250
  Branches      124      124
=======================================
  Hits         2082     2082
  Misses        168      168

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 189e81d...250ab72. Read the comment docs.


Right click context menu and mark

It is suprising to me that you can't mark an item in the right click menu. I would set  the current right clic menu as an info submenu in the current left click context menu, and alway  display the left click menu.
This way all the actions are always available and the most used ones (marking) are easier to use.
I'd keep the current behavior for displaying the context menu: always on right clic and on left click on the check column.

I dont understand @Nodd


Add function handling to the ChatBot

Preamble
Right now the exit function is handled right in carousel.py in an ad-hoc fashion. This is terrible for extensibility. We instead want each Bot to know how to handle the functions that it defines.
Summary
Move execution of the ChatBot's exit_application function to the Interpreter itself.
Requirements

Code for handling exit_application is no longer in carousel.py

Planning on doing this a different way. Closing this ticket for now.


Change copywrite symbol

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

This is a duplicate of #26123

Hey @blisscreates
It seems that similar changes have already been accepted earlier for this article you're editing, sorry about that. 😓
If you feel you have more to add, please feel free to open up a new PR.
Thanks again! 😊

If you have any questions, feel free to reach out through Gitter or by commenting below. 💬


Feature request: Pass input value to onType event

Thank you so much for porting this to Vue 3!
I'd like to propose to pass the input value as a parameter to the onType event. In our case, we want to push this to our backend.

Thank you so much for porting this to Vue 3!
I'd like to propose to pass the input value as a parameter to the onType event. In our case, we want to push this to our backend.

Your are welcome, I published version 3.0.2 with your changes 😉


Create "smart" algorithm policy

Many older keys carry self-signatures made using SHA-1.
We should create a smart policy, which takes the signature creation date into consideration and allows self-sigs using SHA-1 up to a certain date. As switch date we could use the same date many other products use when phasing out SHA-1.
That way, we would be far more compatible with older keys, while still disallowing the use of SHA-1 right now and in the future.

This is now implemented for Hash Algorithms.


Dump documents based on document schema or layer association

Idea: It would be great if the dump tool supported the dumping of documents based on schema or layer association.
Use case: An atlas has a number of schemas, including one for creating people documents. The atlas owner wants to make a second atlas, and copy all people documents to the new atlas (while maintaining existing doc and rev ids). Being able to dump only documents associated with the schema.people would allow the atlas owner to restore these dumped documents to the new atlas.

This change would be contained within the "dump" command of the Nunaliit command line tool. This appears useful and not too onerous.


Please refer to the original source code

This only contains the SDK part of the motion driver. The full source code is available at
https://github.com/albe/psp-motion-driver

Thank you for reporting this - the repo should now have all the missing files.

Thank you for reporting this - the repo should now have all the missing files.


Added missing pattern validator message in Polish

please squash your commits into one and prefix the commit message with Localisation


TypeError: Cannot read properties of undefined (reading 'call')

Bug report
When building an application for production in complex dependency chains some dependencies that are required by the application can be accidentally tree shaken causing the application to not load.
What is the current behavior?
Webpack will tree shake a file/dependency accidentally causing the application to not load with the error ->
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'call')
    at u (bootstrap:19:32)
    at 75282 (reservationRuleUtil.js:39:5)
    at u (bootstrap:19:32)
    at 87962 (profileParseUtil.js:64:5)
    at u (bootstrap:19:32)
    at 8407 (availabilityFilterChips.js:3:109)
    at u (bootstrap:19:32)
    at 93439 (914.ede21470d6d91f13d1b5.js:1:220)
    at Function.u (bootstrap:19:32)

If the current behavior is a bug, please provide the steps to reproduce.
Clone the repro git repository (I have made the repo private as this project contains some code that I do not want to publicly share. This is a high priority issue for us at my company though, so we are willing to share the code with individuals that are looking to debug the problem).
I have created three branches with a different version of webpack installed in each and committed the node_modules folder (sorry about the size of the clone)... This was necessary due to some of the libraries required to debug being only on a private npm registry.
The first branch has the last working version of webpack that this project works on ->
https://github.com/bmarti44/webpack-tree-shaking-issue/tree/version/5.24.0
Then the version of webpack where things started braking ->
https://github.com/bmarti44/webpack-tree-shaking-issue/tree/version/5.24.1
Finally the latest version (things are still broken with the very latest) ->
https://github.com/bmarti44/webpack-tree-shaking-issue/tree/version/5.80.0
What is the expected behavior?
The application should build in production mode with all default optimizations without issue.
Other relevant information:
webpack versions: 524.1-5.80.0
Node.js version: 16.15.1
Operating System: macOS Monterey
Additional tools:
It looks like there has been another report of this issue here  -> https://github.com/webpack/webpack/discussions/15369
Diff of changes that I've been looking over (I've been trying to nail it down to the exact commit) -> https://github.com/webpack/webpack/compare/v5.24.0...v5.24.1

A few more notes - the npm start command caches like crazy. Make sure you clear caches in between each build (or have your devtools opened with caching turned off) otherwise you won't see changes.
Also, the error appears in this bit of code ->
// The require function
function __webpack_require__(moduleId) {
	// Check if module is in cache
	var cachedModule = __webpack_module_cache__[moduleId];
	if (cachedModule !== undefined) {
		return cachedModule.exports;
	}
	// Create a new module (and put it into the cache)
	var module = __webpack_module_cache__[moduleId] = {
		id: moduleId,
		// no module.loaded needed
		exports: {}
	};

	// Execute the module function
	__webpack_modules__[moduleId].call(module.exports, module, module.exports, __webpack_require__); // THIS LINE

	// Return the exports of the module
	return module.exports;
}

So, __webpack_modules__[moduleId] is undefined (which should probably not be the case).

This code is webpack import code, how many entrypoints do you have and how many  chunks your generate (check you import all of them on page)

One entry point ./src/index.ts but the number of chunks generated from webpack 5.24.0 to 5.24.1 changed quite a bit (looking at my local web folder and network traffic).
In webpack 5.24.0 ->
main.sha.js
611.sha.js
578.sha.js
914.sha.js
549.sha.js
787.sha.js
In webpack 5.24.1 ->
main.sha.js
578.sha.js
539.sha.js
914.sha.js
My entrypoint index.ts ->
if (process.env.NODE_ENV === 'development') {
  require('preact/debug');
}

import 'raw-loader!./index.html';
import './components/app';

./components/app ->
/* eslint-disable @typescript-eslint/no-explicit-any */
import { FunctionalComponent, render } from 'preact';
import { Suspense, lazy } from 'preact/compat';
import { HashRouter, Navigate, Route, Routes } from 'react-router-dom';
import { whenDocumentReady } from 'ojs/ojbootstrap';

// Custom pages
const Availability = lazy(() => import('./pages/Availability/availability'));
const ReservationOverview = lazy(() => import('./pages/ReservationOverview/reservationOverview'));

/**
 *  Example app component for RAPID applications.
 *
 *  @returns JSX for the root of the applications.
 */
export const App: FunctionalComponent = () => {
  return (
    <div id="appContainer" class="oj-web-applayout-page">
      <Suspense fallback={<div />}>
        <Routes>
          <Route path="/" element={<Navigate to={'/advance-search'} />} />
          <Route path="/advance-search" element={<Availability />} />
          <Route path="/reservation-overview" element={<ReservationOverview />} />
        </Routes>
      </Suspense>
    </div>
  );
};

whenDocumentReady().then(() => {
  render(
    <HashRouter>
      <App />
    </HashRouter>,
    document.querySelector('#gbu-app-root') as Element
  );
});

and finally one of my pages ->
/* eslint-disable @typescript-eslint/no-unused-vars */
import type { h } from 'preact';
import { usePage, usePageHeader } from '@gbu/rapid-providers';
import { AvailabilityAdvancedSearch } from '@hgbu/rsv-components';
import { Logger } from '@hgbu/rsv-providers';
import { useNavigate } from 'react-router-dom';
import type { SalesRoomRateCriteria } from '@hgbu/rsv-models';

/**
 *  Availability Advanced Search Page for customer contact center.
 *
 *  @returns JSX for the Availability advanced search page.
 */
export const AdvanceSearch = (): h.JSX.Element => {
  usePageHeader({
    pageTitle: 'New Reservation',
    displayOptions: {
      goToParent: false,
    },
    showHeader: false,
  });

  usePage({
    parentId: 'advance-search',
    layout: 'edgeToEdge',
  });

  const navigate = useNavigate();

  function onClickSelectRoomRateForBooking(route?: string, salesRoomRateCriteria?: SalesRoomRateCriteria): void {
    Logger.info(`Clicked on the select room rate for booking so navigation to ::  ${route}`);
    if (route) navigate(route, { state: { criteria: salesRoomRateCriteria as SalesRoomRateCriteria } });
  }

  return <AvailabilityAdvancedSearch dummy="" onSelectRoomRateForBooking={onClickSelectRoomRateForBooking} />;
};

export default AdvanceSearch;

No issues in dev mode/with optimizations turned off. As mentioned https://github.com/webpack/webpack/discussions/15369 is probably the same issue I'm facing. Also this SO issue seems very similar as well.

You can try to enable runtime chunk or disable optimization to undestand where is a bug, I will look at this late

Okay will give the runtime chunk a try and also try disabling the optimizations one at a time

Tried runtime chunk on webpack 5.24.1 and am getting the same error. New chunk order is ->
runtime.sha.js
main.sha.js
539.sha.js
578.sha.js
914.sha.js
I will continue disabling optimizations and let you know the results.

Went through each of the optimizations and set them to false one at a time, here are the results... This was on webpack 5.24.1
concatenateModules: false - resolves the issue
sideEffects: false - error persists
usedExports: false - error persists
flagIncludedChunks: false - error persists
removeEmptyChunks: false - error persists
innerGraph: false - error persists
mangleExports: false - error persists
mergeDuplicateChunks: false - error persists
minimize: false - error persists

hm, maybe we have regression somewhere here https://github.com/webpack/webpack/commit/f96194e0f64ead3eb2cd36e93d95039a897174f1

perhaps... i just reverted ModuleConcatenationPlugin.js (only that one file) and reran the build - the error was resolved.
i can go through and start reverting it line by line to see if  i can trace it down/nail it to something concrete?

@bmarti44 yeah, feel free to do it, it will help

I'm still narrowing it down further but if I take the _tryToAdd method from 5.24.0 and port it to 5.24.1 then the issue is resolved. Will continue to nail it down in that method (there are quite a few changes).

Traced it down further to the changes done to incomingConnections here -> https://github.com/webpack/webpack/commit/5c42b918b438916add040531266f8d88c604427d#diff-2c41050379dc600b1a2db89ef0f270b32e7fdd8139702f36ba96f03d53e3cfd0L611
current diff of the changes i made ->
diff --git a/node_modules/webpack/lib/optimize/ModuleConcatenationPlugin.js b/node_modules/webpack/lib/optimize/ModuleConcatenationPlugin.js
index e602119f..7aeb7ee0 100644
--- a/node_modules/webpack/lib/optimize/ModuleConcatenationPlugin.js
+++ b/node_modules/webpack/lib/optimize/ModuleConcatenationPlugin.js
@@ -571,65 +571,31 @@ class ModuleConcatenationPlugin {

 		const moduleGraph = compilation.moduleGraph;

-		const incomingConnections = moduleGraph.getIncomingConnectionsByOriginModule(
-			module
-		);
-
-		const incomingConnectionsFromNonModules =
-			incomingConnections.get(null) || incomingConnections.get(undefined);
-		if (incomingConnectionsFromNonModules) {
-			const activeNonModulesConnections = incomingConnectionsFromNonModules.filter(
-				connection => {
-					// We are not interested in inactive connections
-					// or connections without dependency
-					return connection.isActive(runtime) || connection.dependency;
-				}
-			);
-			if (activeNonModulesConnections.length > 0) {
-				const problem = requestShortener => {
-					const importingExplanations = new Set(
-						activeNonModulesConnections.map(c => c.explanation).filter(Boolean)
-					);
-					const explanations = Array.from(importingExplanations).sort();
-					return `Module ${module.readableIdentifier(
-						requestShortener
-					)} is referenced ${
-						explanations.length > 0
-							? `by: ${explanations.join(", ")}`
-							: "in an unsupported way"
-					}`;
-				};
-				statistics.incorrectDependency++;
-				failureCache.set(module, problem); // cache failures for performance
-				return problem;
+		const incomingConnections = Array.from(
+			moduleGraph.getIncomingConnections(module)
+		).filter(connection => {
+			// We are not interested in inactive connections
+			if (!connection.isActive(runtime)) return false;
+
+			// Include, but do not analyse further, connections from non-modules
+			if (!connection.originModule) return true;
+
+			// Ignore connection from orphan modules
+			if (chunkGraph.getNumberOfModuleChunks(connection.originModule) === 0)
+				return false;
+
+			// We don't care for connections from other runtimes
+			let originRuntime = undefined;
+			for (const r of chunkGraph.getModuleRuntimes(connection.originModule)) {
+				originRuntime = mergeRuntimeOwned(originRuntime, r);
 			}
-		}

-		/** @type {Map<Module, readonly ModuleGraph.ModuleGraphConnection[]>} */
-		const incomingConnectionsFromModules = new Map();
-		for (const [originModule, connections] of incomingConnections) {
-			if (originModule) {
-				// Ignore connection from orphan modules
-				if (chunkGraph.getNumberOfModuleChunks(originModule) === 0) continue;
-
-				// We don't care for connections from other runtimes
-				let originRuntime = undefined;
-				for (const r of chunkGraph.getModuleRuntimes(originModule)) {
-					originRuntime = mergeRuntimeOwned(originRuntime, r);
-				}
-
-				if (!intersectRuntime(runtime, originRuntime)) continue;
-
-				// We are not interested in inactive connections
-				const activeConnections = connections.filter(connection =>
-					connection.isActive(runtime)
-				);
-				if (activeConnections.length > 0)
-					incomingConnectionsFromModules.set(originModule, activeConnections);
-			}
-		}
+			return intersectRuntime(runtime, originRuntime);
+		});

-		const incomingModules = Array.from(incomingConnectionsFromModules.keys());
+		const incomingModules = Array.from(
+				new Set(incomingConnections.map(c => c.originModule))
+			).sort(compareModulesByIdentifier);

 		// Module must be in the same chunks like the referencing module
 		const otherChunkModules = incomingModules.filter(originModule => {
@@ -659,40 +625,67 @@ class ModuleConcatenationPlugin {
 		}

 		/** @type {Map<Module, readonly ModuleGraph.ModuleGraphConnection[]>} */
-		const nonHarmonyConnections = new Map();
-		for (const [originModule, connections] of incomingConnectionsFromModules) {
-			const selected = connections.filter(
-				connection =>
-					!connection.dependency ||
-					!(connection.dependency instanceof HarmonyImportDependency)
-			);
-			if (selected.length > 0)
-				nonHarmonyConnections.set(originModule, connections);
-		}
-		if (nonHarmonyConnections.size > 0) {
+		const nonHarmonyConnections = incomingConnections.filter(
+			connection =>
+				!connection.originModule ||
+				!connection.dependency ||
+				!(connection.dependency instanceof HarmonyImportDependency)
+		);
+		if (nonHarmonyConnections.length > 0) {
 			const problem = requestShortener => {
-				const names = Array.from(nonHarmonyConnections)
-					.map(([originModule, connections]) => {
-						return `${originModule.readableIdentifier(
-							requestShortener
-						)} (referenced with ${Array.from(
+				const importingModules = new Set(
+					nonHarmonyConnections.map(c => c.originModule).filter(Boolean)
+				);
+				const importingExplanations = new Set(
+					nonHarmonyConnections.map(c => c.explanation).filter(Boolean)
+				);
+				const importingModuleTypes = new Map(
+					Array.from(importingModules).map(
+						m =>
+							/** @type {[Module, Set<string>]} */ ([
+							m,
 							new Set(
-								connections
-									.map(c => c.dependency && c.dependency.type)
-									.filter(Boolean)
+								nonHarmonyConnections
+									.filter(c => c.originModule === m)
+									.map(c => c.dependency.type)
+									.sort()
 							)
-						)
-							.sort()
-							.join(", ")})`;
-					})
+						])
+					)
+				);
+				const names = Array.from(importingModules)
+					.map(
+						m =>
+							`${m.readableIdentifier(
+								requestShortener
+							)} (referenced with ${Array.from(
+								importingModuleTypes.get(m)
+							).join(", ")})`
+					)
 					.sort();
-				return `Module ${module.readableIdentifier(
-					requestShortener
-				)} is referenced from these modules with unsupported syntax: ${names.join(
-					", "
-				)}`;
+				const explanations = Array.from(importingExplanations).sort();
+				if (names.length > 0 && explanations.length === 0) {
+					return `Module ${module.readableIdentifier(
+						requestShortener
+					)} is referenced from these modules with unsupported syntax: ${names.join(
+						", "
+					)}`;
+				} else if (names.length === 0 && explanations.length > 0) {
+					return `Module ${module.readableIdentifier(
+						requestShortener
+					)} is referenced by: ${explanations.join(", ")}`;
+				} else if (names.length > 0 && explanations.length > 0) {
+					return `Module ${module.readableIdentifier(
+						requestShortener
+					)} is referenced from these modules with unsupported syntax: ${names.join(
+						", "
+					)} and by: ${explanations.join(", ")}`;
+				} else {
+					return `Module ${module.readableIdentifier(
+						requestShortener
+					)} is referenced in a unsupported way`;
+				}
 			};
-			statistics.incorrectModuleDependency++;
 			failureCache.set(module, problem); // cache failures for performance
 			return problem;
 		}

Yeah, PR welcome

@bmarti44 Hello, any news? Maybe you can find a code which leads to the problem?

hey @alexander-akait! PR -> https://github.com/webpack/webpack/pull/17103
I am triple checking the changes on my local but the diff there appears to resolve my issue (it is at least easier to read).

Ugh, I need to fix the email address in my key... Lemme fix up a few things and continue to test and will finalize for Monday.

closing per https://github.com/webpack/webpack/pull/17103 duplicate ModuleConcatenationPlugins defined...

Just a note that I'm having the exact same error as this, I do not have any ModuleConcatenationPlugins defined, yet  concatenateModules: false resolves my issue.


P677: work on page of "Web Components standard" is discontinued

The link near the bottom of "Web Components standard", which is linked to this page:
http://www.w3.org/TR/components-intro/
And on this page it said:
"Work on this document has been discontinued and it should not be referenced. Numerous online resources about Web Components are available, including the Web Components wiki."
Maybe a link to another resource should be replaced with?

Thanks, now linking to MDN instead.


Add zf-hal as a development requirement

When running composer with --prefer-lowest and an empty vendor/ directory, an error occurs. This is due to the fact that while zf-apigility-admin requires zf-hal 1.4.2 or up, it is a development requirement. However, zf-apigility is a production requirement, and the 1.3 version specified requires zf-hal 1.4.1 or up. As a result, composer determines that there is a conflict, and the lower, 1.4.1 version of zf-hal will not satisfy the requirements of zf-apigility-admin, and thus fails.
Adding zf-hal as a development requirement, and pinning it to version 1.4.2, solves the issue.

Coverage remained the same at 51.143% when pulling fba6d2e0022abfdf0c70e2bed09ee0f7a292d90f on weierophinney:hotfix/dep-constraints into d524484d3591a1d2c58e6fc46ad6af7f081e699d on zfcampus:develop.


feat(msw): support using OpenAPI example/examples fields as MSW values

Status
READY
Description
Resolves #922.
Adds support for OpenAPI's example and examples fields to be used as MSW values. Handles example refs, as well as every variation of the example/examples fields described in the docs.

Rebased to fix a conflict.

Hello, from my tests and what I understand from this PR, it seems like we only mock the first example of a list. I think it would be an amazing feature to mock all examples in order to avoid having to create custom mocks when performing tests. What do you think ?


Clean up ExpressJS services

Tests are failing due to terminology failures at:
https://r4.ontoserver.csiro.au/fhir/ValueSet/$expand?url=http://hl7.org/fhir/ValueSet/administrative-gender
https://r4.ontoserver.csiro.au/fhir/ValueSet/$expand?url=https://healthterminologies.gov.au/fhir/ValueSet/australian-states-territories-2
https://r4.ontoserver.csiro.au/fhir/ValueSet/$expand?url=http://fhir.telstrahealth.com.au/tcm/ValueSet/ARE
Merging in given these issues have been reported to Ontoserver team.


When generating validations struct pkg references needs to be preserved

Problem statement
if I generate the structs into ./specs-go and validations in ./specs-go/validation then types in the validation directory aren't referencing types in specs-go and I get not declared errors
Swagger specification
Steps to reproduce

or put it another way - there could be a way to name the validation only files with a _validation suffix, does it work?

I went with the fie suffix for now, the packages require a bit more work

Thanks a lot!

Can we leave this  open for the pkg work which could be done in the future?

@casualjim  I believe that this refers to a time before I was born with this project, and codegen structure has changed much since that time.
It does not look relevant any longer, does it?

Closed as no longer applicable


Add config to toggle between using Self and actual type names in assists

Currently, our assists sometimes use Self, sometimes use the type name without consistency(I think so at least, might be wrong on this). There is no clear guideline on when to use either so currently its usually just preference of the developer. We should help out here by allowing people to choose whether our assists should always use the types name, or if the assist should prefer using Self where applicable.
https://twitter.com/brendanzab/status/1478496314597920769

Some features like https://github.com/rust-analyzer/rust-analyzer/issues/6404 would need more logic to avoid mixing Self and T in the same place: either some autodetection (and settings ignoring) or more advanced editing of such code places is needed.

Ye good point, we should try to also do some heuristical guessing for which to choose in some situations, similar to how we do with import granularity guessing https://github.com/rust-analyzer/rust-analyzer/pull/8873


Fix bug with hanging app on startup

This PR kills two birds with one stone.
bird #1: the app hanging when the docker daemon was not set (actually happened whenever there was an error before the gui started polling events)
bird #2: the process kill function now checks to see if the process is actually there before trying to kill it

Codecov Report

Merging #8 into master will decrease coverage by 0.03%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master       #8      +/-   ##
==========================================
- Coverage   18.12%   18.09%   -0.04%
==========================================
  Files          12       12
  Lines        1048     1050       +2
==========================================
  Hits          190      190
- Misses        852      854       +2
  Partials        6        6

Impacted Files
Coverage Δ

pkg/commands/os.go
32.24% <0%> (-0.36%)
:arrow_down:

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 588ff79...d317bc3. Read the comment docs.