Automatic User Provisioning - 404 Error

Looks like WebEx may have deprecated the SCIM API? Following these instructions for automatic user provisioning produces a 404 now when testing the API.

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

ID: bd387482-3e21-f53c-d54e-6a853356b511
Version Independent ID: 84781f14-a81a-b0c0-f5c0-2000eb7d08e3
Content: Tutorial: Configure Cisco for automatic user provisioning with Azure Active Directory
Content Source: articles/active-directory/saas-apps/cisco-webex-provisioning-tutorial.md
Service: active-directory
GitHub Login: @zhchia
Microsoft Alias: v-wingf

@Tiberriver256 Thank you for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Note: Unable to assign to @zhchia

@jeevansd  Can you please help here.

It looks like Cisco may have moved WebEx to the CiscoSpark API set.  I was able to get provisioning working within WebEx with https://api.ciscospark.com/v1/scim/[tenant id]/

@Tiberriver256 We have updated the artcile to correctly point to the right SCIM end point, please review.
#please-close


Add module which maps PCRaster operation names to LUE operation names

This will make it convenient for PCRaster users to port their scripts.

@OliverSchmitz FYI

@OliverSchmitz FYI

Empty module is already in. Rest will be handled by #460


[GSoC] Quick navigation algorithm

Bug/issue #, if applicable: NA
Summary
Algorithm and basic Vue components for the new Quick navigation feature. Changes introduced under the quickNavigation flag.

Introduces the QuickNavigationModal component
Flatten index now moved into the app state
Regex pattern for exact and fuzzy string match over the symbols titles

This pr intends to have the algorithm and base components structure for the Quick navigation feature, any other change related to the UI is for testing purposes and will be refactored in upcoming pull requests :)
First pr as part of my GSoC project mentored by @marinaaisa   @franklinsch  and @ bea
Dependencies
NA
Testing
Steps:

Set the quickNavigation.enable flag to true inside theme-settings.json
Open the quick navigation modal component by clicking on the magnifier icon next to the filter input
Type something inside the input bar to trigger the fuzzy search
Assert that the symbols listed correspond to your input

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[X] Added tests
[x] Ran npm test, and it succeeded
[ ] Updated documentation if necessary. NA

@marinaaisa there's anything else needed to merge this pr?

Requesting @franklinsch final look at 😄 but it looks great to me!

@sofiaromorales the demo you showed me looked great! If we're happy with the code, this is good to merge (with the feature flag off by default)

@swift-ci test


Add new APIs and fix bugs

This PR includes several improvements of the web ant plus library. It updates certain dependencies as well as include new APIs and several fixes.
Most importantly it adds new static factory methods to create a USBDriver which essentially bypasses the need to specifically instantiate a GarminStick class instance before a USBDriver can be created. These new methods allow the creation of USBDriver from already paired devices (i.e. no need for selecting from the prompt) and start USBDriver from the USB device selected from the pairing prompt.
It also updates the documentation in the README to reflect the API and corrects some incorrect descriptions

"@vitejs/plugin-react": "^2.2.0",

Thanks for taking a look. The issues raised are totally valid and most of them are silly mistakes, I will fix them shortly. Indeed I should have tested if run dev works... sorry about that.

Thanks for the fix commit! Finally, I would appreciate it if you could run npx prettier --write . / && npx eslint --fix and commit the differences.
When writing or changing a rule, if the developer who implements the change does not apply the fix to the existing file, there will be an extra difference for later development.

Your point is valid and now I remember that I have tried to do running a full lint before doing the PR. The problem is that when I run eslint on all files there are multiple layers of issues (note that these are not only on my branch but on the original master too):

the eslint file is invalid on my machine as it throws this: Environment key "w3c-web-usb" is unknown. Not sure about this error
removing the w3c-web-usb environment allows eslint to run but then there are almost 250 errors.

Just a side note: actually your quoted command npx eslint --fix is a no-op as it needs the list of files to actually lint
For prettier: it adds trailing commas even though trailing commas are none in VSCode, which is due to the fact that running prettier on the command line is outside VSCode so the settings in settings.json is ignored and defaults is all (since version 3.0.0).
I can add a prettierrc.json to set it to none so it works but it was not included in the original project so I did neither. VSCode should format ok when save.
I am happy to make changes, I am not bias towards any kind of formatting (so when adding VSCode formatting settings I was trying to match the original as much as possible) so I would be happy to set whatever you would prefer.
But I will not be able to fix 250+ eslint errors.
Let me know how to proceed: run prettier and add trailing commas as well as update VSCode formatting settings (my preference) or add prettier rule to disable trailingcommas.
PS: I have fixed a typo and removed an unnecessary async that I noticed

@Abasz
I'm sorry for the late reply!
I've merged your kind comments and fixed the code formatting into the master branch.
Please rebase or merge the latest master to your branch and run npm run lint .
If everything is fine, please review request with the push.
https://github.com/8beeeaaat/web-ant-plus/pull/7

Please rebase or merge the latest master to your branch and run npm run lint .

Thanks for this. I will do the rebase and update the PR. Just a side remark:
You understand that this command eslint --fix does not do anything right? I mean that none of the eslint rules are enforced or run by this command. As I mentioned previously eslint cli needs the path to the file which it should lint. So the correct command would be eslint --fix ./**/*.ts, which would lint all .ts files. Again it only would if the .eslintrc.js file would be correct. But it is not as "w3c-web-usb": true is an invalid environment. So effectively you are not running eslint at all even if you run npm run lint

All done.

I updated the npm package!
Thanks for your contributing.
https://www.npmjs.com/package/web-ant-plus/v/1.0.5


PHOENIX-7001: Initial implementation of Change Data Capture (CDC) feature

This commit includes a squash of all the below changes from all the CDC feature PRs and further narrows the diff down by removing non-functional changes for the ease of review. On top of it, the changes have been reworked for the changed state of master, especially the new submodules.

4c9827a43 Hari.. PHOENIX-7008 Shallow grammar support for CREATE CDC (#1662)
e5220e01e TheN..  PHOENIX-7054 Shallow grammar support for DROP CDC and ALTER CDC  (#1694)
581e61365 Hari.. PHOENIX-7008 Implementation for CREATE CDC  (#1681)
e2ef88603 Hari.. PHOENIX-7008 Tweaks, fixes and additional test coverage for CREATE CDC (#1703)
5d3fd4033 TheN.. PHOENIX-7074 DROP CDC Implementation (#1713)
7420443d8 Hari.. PHOENIX-7014: Query compiler/optimizer changes along with some PHOENIX-7015 changes (#1766)
da6ddad04 Kadi.. Add an extra delete mutation for CDC
93d586efb Kadi.. Add an extra delete mutation during rebuild for CDC index
f07898f1f Hari.. PHOENIX-7008: Addressing Jira spec and review feedback changes (#1802)
87a2ea101 Hari.. PHOENIX-7008: Fix for parser gap and fix for failing test (#1812)
e395780e9 TheN.. PHOENIX-7015 Implementing CDCGlobalIndexRegionScanner (#1813)

I found usage of maps to keep track of mutations and pre and post images are too complex in ITs. The test code should be easy to read and verify. We need a list of mutations and then check the result CDC against this list of mutations. For example, each mutation can be modeled as a timestamp, mutation type, list of column names and list of values represented as strings. This list can be initialized when it is constructed. Creating upsert and delete statements from this mutation list should be straightforward. Comparing the result of CDC against this list also should simple. The pre and post images can be retrived from the data table using SCN connections and verified against the CDC result.

Now that JSON PR is merged, we can also address it with changes/pre/post image and include some tests for JSON data.

Now that JSON PR is merged, we can also address it with changes/pre/post image and include some tests for JSON data.

Let us open a separate Jira to support complex data types including Array and JSON.

Belated +1


It's possible to cat kube-config and apply together

If you want to programmatically edit the config files
for kubectl, then the config files needs to begin
with three dashes.
This change makes it possible to do
cat deploy/kube-config/influxdb/* \
  | sed 's/amd64/arm/g' \
  | kubectl create -f -

This change is

I signed it.

Does the following command work correctly:
kubectl create -f deploy/kube-config/influxdb/

with dashes?

@k8s-bot ok to test

@piosz Sorry for the delay.

Does the following command work correctly

Yes.

why not just do kubectl apply -f /dir/?

@AlmogBaku Because then I cannot modify the files on the fly. Please read the first post in this thread.

LGTM, please rebase.

/lgtm

@piosz Rebased now.
I have only done this on files I use regularly, but those three dashes are a part of the YAML spec, and theres no reason not to include them. I could go through the other YAML files and add it if you want.


Outputs functionalities

multiple subpanels: this is related with the possibility to run multiple phonopy calculation in aiida-vibroscopy, not yet supported;
dielectric properties not shown
downloadable spectra
interactive raman (Temperature, energy of the incoming light)

for the interactive raman, the user should also have the option to get the single crystal spectra from run_single_crystal_raman_intensities (this should let the user to specify the polarizability vector incoming,outgoing) or powder

@AndresOrtegaGuerrero  exactly, essentially the order of the correction to the force constants, If I am correct... sorry, I had not time to check better.
But I see that in the first case (preprocess_data, 3), you add second derivative correction, in the latter you provide third derivative... So in principle the effect (the pyhisics) is different.
I think that this is not seen by the post process utility, so you can access both spectra, even if one of them is not accurate.
What do you think? It is bad that we cannot have both at the same time, but maybe something can be done at the VibroWorkChain level.


Clients with Last Will prevents the MqttServer from clean shutdown and restart

As soon as there is a client with a last will connected to the MQTT-Server, it's not possible anymore to graceful stop the broker.
There are three symptoms:

An unhandled exception
The TCP-Socket is not closed and therefore it is not possible to start the Broker again
The last will is not executed (not sure if this is true, needs investigation)

The following exception is thrown:
System.OperationCanceledException: The operation was canceled.
   at System.Collections.Concurrent.BlockingCollection`1.TryAddWithNoTimeValidation(T item, Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at MQTTnet.Server.MqttClientSessionsManager.EnqueueApplicationMessage(MqttClientSession senderClientSession, MqttPublishPacket publishPacket)
   at MQTTnet.Server.MqttClientSession.Stop(MqttClientDisconnectType type, Boolean isInsideSession)
   at MQTTnet.Server.MqttClientSessionsManager.Stop()
   at MQTTnet.Server.MqttServer.<StopAsync>d__39.MoveNext()

If the MqttServer should be stopped and there is a client with a last will connected, the MqttServer tries to Enqueue the message with the last will.
Under the hood, this results in a call to BlockingCollection.TryAddWithNoTimeValidation.
This method takes a cancellation token and will throw an exception if cancellation is requested.
As the cancellation is requested during the stop, before calling BlockingCollection.TryAddWithNoTimeValidation, an exception is thrown.
This exception isn't handled and the rest of the code in the MqttClientSessionsManager.Stop() isn't executed.
EDIT:
I can submit a Pull Request but I'm not sure how this should be sovled.

Thank you for the hint. It is. Therefore I close this issue.


[MB-8009] Add logging to routing services counseling flow

Description
This PR adds logging to the MoveRouter service that handles the routing moves to either the TOO or services counseling queues
Reviewer Notes
This PR should be merged after https://github.com/transcom/mymove/pull/6583 . (The diff for this PR is larger than it actually is until the other PR is merged to master)
Setup
Follow the steps outlined in https://github.com/transcom/mymove/pull/6583 to submit a move with and without services counseling available. Once the move is submitted check the logs for success or error messages. If you're using goland you should be able to cmd + F to find certain logs
Acceptance

aws-vault login transcom-gov-milmove-stg
Find CloudWatch and log groups or insights
Search for services counseling logs

Messages

:book:
:link: MB-8009

  Generated by :no_entry_sign: dangerJS against 8c236db39024c32a996146fb4b16769fe1277377

Got a little confused. I reviewed logging from the other PR which is also from this PR.

Got a little confused. I reviewed logging from the other PR which is also from this PR.

Thanks for reviewing this!


Avoiding entire renderer instantiation after the resize of the control

This PR aims to avoid the need to the entire disposal of the renderer when the control resizes.
When resizing, the only important thing is to create a new rendertarget, along with the corresponding framebuffers (disposing old ones, of course). In fact, the d3d9 device can still be used again.
As a note, you can see that the BackbufferWidth and BackbufferHeight are set to 1. In fact, in this use case, the backbuffer is not used, as we're relying on the created rendertargets.

Thank you for your reviews.
See also #24 where I addressed the problem of simplifying the state management between the control and the renderer.

This is superceded and fixed by #24 !


MSVCP140.dll missing on machines without Visual C++ Redistributable for Visual Studio 2015

Program does not run, needs fixing quick.

No workaround was needed, I just had to add msvcp140.dll and vcruntime140.dll to the dir of my program and it automatically loads the dlls.


Add trashman

Hi @veelenga !
This is a simple memory profiler for Crystal applications by @Groogy

@hugoabonizio Yeah, @Groogy shared it on IRC recently. see: https://irclog.whitequark.org/crystal-lang/search?q=trashman

@faustinoaq I tried to run the example code and it doesn't compile, maybe I'm missing something:
...

in src/trashman/analyzer.cr:53: instantiating 'Trashman::AnalyzerRecord:Class#new(Trashman::BaseRecord+)'

      @records << AnalyzerRecord.new record
                                 ^~~

in src/trashman/analyzer.cr:12: undefined method 'Trashman::BaseRecord#callstack()'

    @callstack = record.callstack
                        ^~~~~~~~~

@hugoabonizio I tried it and works very well, you need to compile it using -D ENABLE_TRASHMAN :sweat_smile:
by example:
crystal build src/trashapp.cr -o bin/trashapp -D ENABLE_TRASHMAN -s
Parse:                             00:00:00.000228033 (   0.25MB)
Semantic (top level):              00:00:00.219240208 (  28.43MB)
Semantic (new):                    00:00:00.001315479 (  28.43MB)
Semantic (type declarations):      00:00:00.020433242 (  36.43MB)
Semantic (abstract def check):     00:00:00.002083214 (  36.43MB)
Semantic (ivars initializers):     00:00:00.001399141 (  36.43MB)
Semantic (cvars initializers):     00:00:00.013244145 (  36.43MB)
Semantic (main):                   00:00:00.172640605 (  60.50MB)
Semantic (cleanup):                00:00:00.001059773 (  60.50MB)
Semantic (recursive struct check): 00:00:00.001043762 (  60.50MB)
Codegen (crystal):                 00:00:00.303132300 (  60.62MB)
Codegen (bc+obj):                  00:00:01.189555010 (  60.62MB)
Codegen (linking):                 00:00:00.282836109 (  60.62MB)

Codegen (bc+obj):
 - no previous .o files were reused

Super cool, fun to be featured ^^


[5.8] update type-hint for src/Illuminate/Support/Facades/Crypt.php

add encryptString
add decryptString

fixed https://github.com/laravel/framework/issues/27999

@rentalhost  changed


added installer on windows

By the way we might want to clean up all the unnecessary stuff (like other .exe files, and .ilk/.lib files) while working on this installer.

Another comment - I don't think user should be able to deselect Veles UI component during installation, since it is the only component and it doesn't make sense to continue with installer without it.


Copy K8sServiceAccount from pkg/service to pkg/identity

This PR is the 1st part of:

Moving K8sServiceAccount from pkg/service to pkg/identity #3152

This PR merely creates a copy of K8sServiceAccount from pkg/service to pkg/identity.
The goal is to alleviate the review load from #3152.
Next step: Change import of K8sServiceAccount from pkg/service to pkg/identity #3154

ref #2218


Angular Material select box, Menu button, Mat selection pannel theme switch not working

Hi ,
I am facing issue while working with custom theme. It is not changing to light theme for Material select box panel, Mat menu button and Material selection panel.
ChangeTheme($event) {
//  alert($event)
//  console.log($event);
this.theme = $event;
this.overlayContainer.getContainerElement().classList.remove($event);
this.overlayContainer.getContainerElement().classList.add($event);
console.log("Theme after switching",this.overlayContainer)
}
like this i have implemented theme change functionality. From dev tool i am able to apply color to above component but theme toggling through button not working

Please keep GitHub issues for bug reports / feature requests. Better avenues for troubleshooting / questions are stack overflow, gitter, mailing list, etc.

Please keep GitHub issues for bug reports / feature requests. Better avenues for troubleshooting / questions are stack overflow, gitter, mailing list, etc.


Update README to point to new docs, deprecate old README

Update the README to point to the new ReadTheDocs link
Move the old Elastalert README to a new file to reduce confusion
Add some more text to the new README that covers the essential points of the old README
Some general tidying for readability

A neat view of the new README can be found by browsing the branch directly here.
Some questions:

The Gitter is still actively used, but I don't often see people answering questions on it, mostly people asking questions. Do we still want to link to it?
The FAQ in the old README is useful, but I think it would be better as a ReadTheDocs page. Does this sound OK? If so, I will move the content in the FAQ to ReadTheDocs once this PR is landed.
There are some third party tools mentioned which I haven't bothered moving over. elastalert-docker is obviously still active, so have kept that one in. The Bitsensor Kibana plugin hasn't been updated in years, but the Elastalert Helm chart was updated five months ago. I haven't moved either of these two into the main README - should I?

I agree with all points. I've never been to the gitter community. I think the Discussions that I've enabled on this project is a better location for users to communicate. It's not real-time like chat, but it will make searching easier for people that want to find existing Q/A discussions.
The elastalert-docker project includes an Elastalert helm chart that I maintain, and is available at the helm.jertel.com chart repository. I remember seeing a reference to an Elastalert "server" helm chart at one point. That "server" chart is not something that I think should be included with this project since it's specific to the Bitsensor fork.

The following description should be deleted from README-old.md. Not on yelp/elastalert
Discord
Dingtalk
Chatwork


Remove_all_stubs migrations is failing

Bug Report
If you take a recent snapshot of staging data and run migrations 1.8.0 on it, you get errors on the "remove_all_stubs" change set. Happened to both Walt and me.
ERROR [2019-12-16 21:53:45,199] liquibase.changelog.ChangeSet: Change Set migrations.1.8.0.xml::remove_all_stubs::agduncan failed.  Error: ERROR: update or delete on table "workflow" violates foreign key constraint "fk_checkerid_with_tool" on table "tool"→  Detail: Key (id)=(7652) is still referenced from table "tool". [Failed SQL: DELETE FROM workflow WHERE mode='STUB']
liquibase.exception.MigrationFailedException: Migration failed for change set migrations.1.8.0.xml::remove_all_stubs::agduncan:
     Reason: liquibase.exception.DatabaseException: ERROR: update or delete on table "workflow" violates foreign key constraint "fk_checkerid_with_tool" on table "tool"
  Detail: Key (id)=(7652) is still referenced from table "tool". [Failed SQL: DELETE FROM workflow WHERE mode='STUB']
	at liquibase.changelog.ChangeSet.execute(ChangeSet.java:637)
	at liquibase.changelog.visitor.UpdateVisitor.visit(UpdateVisitor.java:53)
	at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:83)
	at liquibase.Liquibase.update(Liquibase.java:202)
	at liquibase.Liquibase.update(Liquibase.java:179)
	at liquibase.Liquibase.update(Liquibase.java:175)
	at liquibase.Liquibase.update(Liquibase.java:168)
	at io.dropwizard.migrations.DbMigrateCommand.run(DbMigrateCommand.java:68)
	at io.dropwizard.migrations.DbCommand.run(DbCommand.java:55)
	at io.dropwizard.migrations.AbstractLiquibaseCommand.run(AbstractLiquibaseCommand.java:68)
	at io.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:87)
	at io.dropwizard.cli.Cli.run(Cli.java:78)
	at io.dropwizard.Application.run(Application.java:93)
	at io.dockstore.webservice.DockstoreWebserviceApplication.main(DockstoreWebserviceApplication.java:153)
Caused by: liquibase.exception.DatabaseException: ERROR: update or delete on table "workflow" violates foreign key constraint "fk_checkerid_with_tool" on table "tool"
  Detail: Key (id)=(7652) is still referenced from table "tool". [Failed SQL: DELETE FROM workflow WHERE mode='STUB']
	at liquibase.executor.jvm.JdbcExecutor$ExecuteStatementCallback.doInStatement(JdbcExecutor.java:356)
	at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:57)
	at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:125)
	at liquibase.database.AbstractJdbcDatabase.execute(AbstractJdbcDatabase.java:1229)
	at liquibase.database.AbstractJdbcDatabase.executeStatements(AbstractJdbcDatabase.java:1211)
	at liquibase.changelog.ChangeSet.execute(ChangeSet.java:600)
	... 13 more
Caused by: org.postgresql.util.PSQLException: ERROR: update or delete on table "workflow" violates foreign key constraint "fk_checkerid_with_tool" on table "tool"
  Detail: Key (id)=(7652) is still referenced from table "tool".
	at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2440)
	at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2183)
	at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:308)
	at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:441)
	at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:365)
	at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:307)
	at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:293)
	at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:270)
	at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:266)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.apache.tomcat.jdbc.pool.StatementFacade$StatementProxy.invoke(StatementFacade.java:114)
	at com.sun.proxy.$Proxy32.execute(Unknown Source)
	at liquibase.executor.jvm.JdbcExecutor$ExecuteStatementCallback.doInStatement(JdbcExecutor.java:352)
	... 18 more

┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Fix Versions: Dockstore 1.8
┆Issue Number: DOCK-1120

Is probably https://github.com/dockstore/dockstore/commit/bd01556b8347dcb33c5c892f505aa9d03a627be5
Please cherry-pick  and verify

Verified that it works locally for me by cherry-picking that commit.

@denis-yuen was the issue with this that it was trying to delete stub workflows that are checker workflows associated with a tool? Should we just delete the association too?

I guess there are two issues

The migration was failing (the workaround is linked above)
The migration is failing because of odd data (checker workflows that are stubs).

This is a bit of a special case, I think to remove the review label (which I just added), yeah, just see that things seem to be left in a good state using a prod DB with the new migration.
But the ticket should probably be left open until we have an explanation for the odd stub checker workflows.

Confirmed that the migrations work on the prod DB. Looks like there is a single unpublished checker workflow on production that was causing it to fail. All other checker workflows are not stubs.


Add scala.js platform

Fixed by https://github.com/BennyHill/sbt-tls-crossproject/commit/982f3e2504a9ae469b32515ad9b707ddf0ae8fe0


Open source the homepage

I wanted to contribute to the homepage, and don't find its source code.

I believe the homepage is hosted under @bketelsen 's GitHub profile
https://github.com/bketelsen/getfleek.dev

It might be worth mentioning this somewhere. The "Github" icon on the webpage/doc page links to this repo. Thanks


The foreground Services  keeps running even if there is no download task

1. What problem do you get?
Since #1078 and #1082  change the download service  to foreground  service on Android O , these foreground Services  keeps running even if there is no download task （The notification title: "FileDownloader"  content: "FileDownloader is running."）. This will make my users very confused. My suggestion is to add a button to force cancel the foreground in the notification bar or cancel the foreground service after downloaded all the tasks.
2. Which version of FileDownloader are you using when you produce such problem?
1.7.5

This is happening with me too. FileDownloader version 1.7.5

I will handle this issue in 1.7.6. Please be patient, thanks.

When will the 1.7.6 version be released?

@BCsl @virengujariya @Allyns 1.7.6-SNAPSHOT is published, please try it! Look forward to your guys feedback!

Thanks guys. I try 1.7.6-SNAPSHOT and its wrok successfully.


Can't connect to a public server over Tor

Hi, i am trying to connect to a public server though Tor but it doesn't work.
I can connect to any public server, but not with proxy enabled.
I have tried with all the public servers available, on proxy <IP_ADDRESS> port 9050.
I also tried with "localhost" instead of <IP_ADDRESS>, and on port 9150.
The error message i am getting is :
Could not connect: Connection refused: connect. Check if the proxy server is running.
And at the bottom near "Server Preferences", it is written :
Connection failed: Socket Error (Connection refused: connect)
I am on Windows, my sparrow version is up to date (1.8.4), and so is my Tor Browser (13.0.13).
I already tried to reboot.

It seems that some part of the network is refusing your connection. Unfortunately there's nothing Sparrow can do about this - if privacy is important, it may be time to consider running your own node. You can also use a VPN instead of Tor.


Remove als

ALS is an unfortunate acronym choice as it is also the acronym for a fatal disease (Lou Gehrig's disease).
Local tests shows this doesn't have to be abbreviated as the short title, this this PR.

How this looks now locally -

Yeah I realized that as I typed out ansible-language-server a few times in chat. It is long :-)  So I agree it doesn't need to be changed in other places.
...also, new to the project so not sure what's failing in CI?

Yeah I realized that as I typed out ansible-language-server a few times in chat. It is long :-) So I agree it doesn't need to be changed in other places. ...also, new to the project so not sure what's failing in CI?

Don't worry, there are unrelated to your change. As long docs job builds you are fine.
PS. We are working on fixing the broken jobs but not all the changes can be implemented right away.


Define a feature you would like to see implemented in our app

Apply responsive design for different screen sizes on android devices


Update draft6 meta-schema from json-schema.org

Update the local copy of the draft6 meta-schema to match current
json-schema.org version.
Signed-off-by: Rob Herring<EMAIL_ADDRESS>

Hm, interesting, I only pulled that recently, didn't know Draft 6 was getting changes pushed to it.
Thanks though!

Hm, interesting, I only pulled that recently, didn't know Draft 6 was getting changes pushed to it.

Only bugfixes, as in "as originally published, it would fail validation on some valid schemas, and/or misleadingly allow some invalid ones".  I forget what the bug was.  We've had to fix draft-04 a few times as well.

Ah, of course, makes sense.


These runs sure are hot.

Update the dosomething_signup_exists function.
This will fix the problem we are having where it appears users are not signed up for a campaign
because the old signup might not have had the correct run attached to it.
This is not a pretty fix, but sometimes that is ok.
Refs #6095

@mshmsh5000 goooood catch, fixed

Great! :+1: :shipit:


ui: Add higher contrast, alignment and use size hierarchy in the v-card

Higher contrast makes components easier to see, alignment of components to create visual pattern and component size hierarchy to show how important something is

@Robinsondssantos, good to see you here. Please post a screenshot of before and after, so it is easier to see the proposed changes.

@Robinsondssantos, good to see you here. Please post a screenshot of before and after, so it is easier to see the proposed changes.

Before:

After:

Can you address @noreng-jg comments as well?

Can you address @noreng-jg comments as well?

shure

Hey Robinson, thanks for the contribution. I think it would be a good ideia
change the color of the button for "add-device" and "add-rule" buttons to the following
files as you proposed in initial dashboard page,
ui/src/components/firewall_rules/FirewallRulesFormDialog.vue
ui/src/components/device/Device.vue

<v-btn
	...
      class="v-btn--active"
      text
      color="primary"
>

Hey Robinson, thanks for the contribution. I think it would be a good ideia
change the color of the button for "add-device" and "add-rule" buttons to the following
files as you proposed in initial dashboard page,
ui/src/components/firewall_rules/FirewallRulesFormDialog.vue
ui/src/components/device/Device.vue

<v-btn
	...
      class="v-btn--active"
      text
      color="primary"
>

Hey Vagner, good ideia. Should I generate a new pull request?

Hey Vagner, good ideia. Should I generate a new pull request?

It could be in the same pull request, with a new commit, then you could squash your commits into a single one. :)

Hey Vagner, good ideia. Should I generate a new pull request?

It could be in the same pull request, with a new commit, then you could squash your commits into a single one. :)

@noreng-jg I did as you commented, please take a look

I have two considerations before accepting your pull request.

The buttons in "add-rule" and "add-device" should follow the pattern of dashboard, with normal size, so you'll have to add the properties of text, v-btn--active in class and remove the outlined.

like that:
      <v-btn
        class="v-btn--active mr-2"
        text
        color="primary"
        ...
      >

You should also join your commits into a single one.

A suggested commit message for the changes implemented could be:
ui: Change style display presentation for components

Higher contrast for v-main component styling was added followed by
display changes conventions in buttons for "add-rule" and  "add-firewall".

Do you agree @leonardojoao ?

I have two considerations before accepting your pull request.

The buttons in "add-rule" and "add-device" should follow the pattern of dashboard, with normal size, so you'll have to add the properties of text, v-btn--active in class and remove the outlined.

like that:
      <v-btn
        class="v-btn--active mr-2"
        text
        color="primary"
        ...
      >

You should also join your commits into a single one.

A suggested commit message for the changes implemented could be:
ui: Change style display presentation for components

Higher contrast for v-main component styling was added followed by
display changes conventions in buttons for "add-rule" and  "add-firewall".

Do you agree @leonardojoao ?

I have two considerations before accepting your pull request.

The buttons in "add-rule" and "add-device" should follow the pattern of dashboard, with normal size, so you'll have to add the properties of text, v-btn--active in class and remove the outlined.

like that:
      <v-btn
        class="v-btn--active mr-2"
        text
        color="primary"
        ...
      >

You should also join your commits into a single one.

A suggested commit message for the changes implemented could be:
ui: Change style display presentation for components

Higher contrast for v-main component styling was added followed by
display changes conventions in buttons for "add-rule" and  "add-firewall".

Do you agree @leonardojoao ?

Thank you for your considerations, I will do that

Hey @Robinsondssantos. We really appreciate your contribution.
@all-contributors please add @Robinsondssantos for code

Hey @Robinsondssantos. We really appreciate your contribution.
@all-contributors please add @Robinsondssantos for code

Thank you so much @gustavosbarreto


Optimize stFeatureExtraction

Eliminate a O(n^2) operation. Now it is significantly faster.

Thanx alot!

Glad that I helped. Thank you for this useful project!


Return ObjectResult - Without Double Quotes

Is there such thing as a RawResult?  ObjectResult has some annoying behaviour that if you submit a string as the value it will always include double quotes in the response regardless of the ContentType you specify.
I want to ensure no double quotes are included in the response.

I suppose the response is being sent back as json, hence the double quotes. This sounds like a bug. Meanwhile you can return a ContentResult which sends content as it is with text/plain as the content type.

I actually need a dynamic content type based on a number of conditions.

I see. You could add the StringOutputFormatter in the output formatter list. This formatter writes content in text/plain formatter. Since order of formatter matters, make sure to add it before other formatters like json or xml.

This sounds like a bug.

This is not a bug. This comes up from time to time and the recommendation is to use the string output formatter if you want strings to go onto the wire as-is.

This formatter writes content in text/plain formatter

This changed for RC2. If the returned object is a string, it can write any content type.

I actually need a dynamic content type based on a number of conditions.

If you can give us more information about what you're trying to do we can help.

Sounds like RC2 has a way to return a ContentResult and make sure it doesn't include double quotes around string values, with the additional control of setting the content type?
Let me know if I understand that correctly.
Which means I'll have to wait to upgrade since I'm buried in building in RC1.

Sounds like RC2 has a way to return a ContentResult and make sure it doesn't include double quotes around string values, with the additional control of setting the content type?

This has been around forever: https://github.com/aspnet/Mvc/blob/master/src/Microsoft.AspNet.Mvc.ViewFeatures/Controller.cs#L471
ContentResult will just write out your text verbatim.

@rynowak I think you should reconsider this.
I was bitten by it today in RC2.
StringOutputFormatter writes returned string verbatim to the output.
But this makes no sense:
**Request**
Accept: application/json

**Response
Content-Type: application/json

Hello World <-- this is no JSON

As you can see, the server does advertise that it is serializing JSON in Content-Type but the response body is not JSON. Also, the client requested JSON exclusively but gets a 200 OK with no JSON content.
This can only be seen as a bug as the response as a whole is clearly invalid.
I think moving the StringOutputFormatter after JsonOutputFormatter would be reasonable and fix this.
For the use case where I want to return manually serialized JSON verbatim from my Action, ContentResult is there for that and indicate intent. Returning a string is too ambiguous to override the proper content type serialization.

I agree, this doesn't seem right or useful.

@jods, see https://github.com/aspnet/Mvc/issues/4945#issuecomment-230555683
We're planning to change this behavior for 2.0.
I'm going to close this issue because I've already got a long-winded explanation including our future plans in #4945


feat: Improve currently used rules, add more hooks checks

Description
This PR adds more useful rules, fixes issues with existing rules and cleans up the eslint config file structure.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix CJS imports

https://github.com/solana-labs/solana-program-library/pull/3529 for Wallet Adapter

Published.


STL Sorting in String

Is your feature request related to a problem? Please describe.
Here a shortcut method with less time complexity given which is using STL ( Standard template library).
We can sort the activities according to their finishing time so that we always consider the next activity as the minimum finishing time complexity.
Describe the solution you'd like

Use a specific header file.
add a loop.
Use sort function.

Additional context
It can be added in Sorting -Algorithms folder of C++ directory. I will solve it in C++ ,Please assign it to me @Kumar-laxmi @Arun9739

Kindly raise issues pertaining to algorithm and not for working of library functions


Skip the first row in the excel file

How to skip first row
S/No. | RADET Period (yyyy-mm-dd) | State | LGA | Facility Name | LAMIS UIDPatient Id | Hospital Num | Household Id | Unique Number | Sex | Marital Status | Weight (Kg) | Date of Birth (yyyy-mm-dd) - this is the header i.e first row
Error: FormatException: Date of Birth (yyyy
dart-sdk/lib/internal/js_dev_runtime/private/ddc_runtime/errors.dart 266:49 throw
dart-sdk/lib/_internal/js_dev_runtime/patch/core_patch.dart 229:5 parse
packages/radet_calculator/screens/web/dashboad_radet_screen.dart 230:44
packages/flutter/src/widgets/framework.dart 1114:30 setState
packages/radet_calculator/screens/web/dashboad_radet_screen.dart 131:11 pickFile
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 45:50
dart-sdk/lib/async/zone.dart 1653:54 runUnary
dart-sdk/lib/async/future_impl.dart 147:18 handleValue
dart-sdk/lib/async/future_impl.dart 766:44 handleValueCallback
dart-sdk/lib/async/future_impl.dart 795:13 _propagateToListeners
dart-sdk/lib/async/future_impl.dart 430:9 callback
dart-sdk/lib/async/schedule_microtask.dart 40:11 _microtaskLoop
dart-sdk/lib/async/schedule_microtask.dart 49:5 _startMicrotaskLoop
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 166:15

@justkawal

@yinkyAde this will help
int i = 0;
for (var row in excel.tables[$yourSheetName]!.rows) {
if (i != 0) {
//do something here
}
}


feat: update ui with rerun simulation functionality

What new features does this PR implement?
Please summarize the features that this PR implements. As relevant, please indicate the issues that the PR closes.

Adds re-run button in dispatch.overview.

:tada: This PR is included in version 9.53.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


compact: Ensure downsampled chunks are not larger than 120 samples; stream downsampling more

During bug fixing on https://github.com/thanos-io/thanos/pull/2528 I found that downsampling always encodes whatever is given in the block into huge chunks. This can lead to inefficiency during query time when only a small part of chunk data is needed, but store GW needs to fetch and decode everything.
See: https://github.com/thanos-io/thanos/blob/55cb8ca38b3539381dc6a781e637df15c694e50a/pkg/compact/downsample/downsample.go#L141
AC:

Downsampled chunks are not larger than 120 samples
Chunks are expanded on demand in iterator.

If no one is working on this issue, can I have a try? @bwplotka

I assume you are not on it right? (: Just making sure, so others can help as well (:

Yeah, apologies for keeping blocked, I am not working on it currently 😅

I am happy to work on this.

Still relevant AFAIK.

Hi, I still want to work on this. I will get back to you guy soon.

Is this still valid? If not, which PR fixed it?

I think this is still valid

Hi, two questions I have about this issue.

There is already a limit of 140 samples per chunk for downsampled chunks here. I guess the performance should be similar to 120 samples?

What's the benefit of Chunks are expanded on demand in iterator.? I see that we need to expand all the chunks before the downsampling anyway.  So what is the doing it on demand?

Thanks!

There is already a limit of 140 samples per chunk for downsampled chunks here. I guess the performance should be similar to 120 samples?

Yes, performances should be similar and 140 should be a problem. However, I'm wondering if that 140 value was a "typo" of 120 or intentional 🤔

Does not matter 120 / 140. If there is check I might miss it and all good (: Let's double check.

What's the benefit of Chunks are expanded on demand in iterator.? I see that we need to expand all the chunks before the downsampling anyway. So what is the doing it on demand?

What I mean is to not expand all of chunks and only then process query, just instead one, process sample, then another and process those and another etc... (streaming)

Still valid

Still valid

Hey @bwplotka
Can you elaborate on this - link

What I mean is to not expand all of chunks and only then process query, just instead one, process sample, then another and process those and another etc... (streaming)

#4275 fixes this


Updates for iOS in-context signup support

Reviewer: @GioSensation
Asana: https://app.asana.com/0/0/1204874198702028/f
Description
Passes a new flag when autofill is opened to let the native side know if in-context signup is available.
On successful response, updates autofill state and re-renders icon.
Steps to test
Test in conjunction with https://github.com/duckduckgo/iOS/compare/anya/ios-incontext-email-promotion

What's happening with this? Anything left to do before it's merged?


fix: removed an empty line in the .gitignore file

Checklist:

[ x] I have read and followed the contribution guidelines.
[ x] I have read and followed the how to open a pull request guide.
[ x] My pull request targets the main branch of freeCodeCamp.
[ x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Hey @PrinceMahdi
Thank you for opening this pull request.
This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.


fix control characters instead of spinner on Windows

I was having the same issue as in #52, seeing control characters in Windows.
It turns out an easy fix is to use the line feed character \r to process the lines in Windows.
Another issue I had though, was I wanted to use the os.Stderr and the coloring had a bad time dealing with this, so I added another if-statement to take out coloring if using os.Stderr.

Wow, this is an awesome PR. Thank you very much! I'll take a look at it this evening.

Thanks for this!


Flaw in the return type

Hi!
First of all, I want to thank you for the excellent implementation of system facades for symphony!
I found a small bug, not even a bug, but a shortcoming:
1x: Method "Symfony\Component\HttpKernel\Bundle\Bundle::boot()" might add "void" as a native return type declaration in the future. Do the same in child class "Lagdo\Symfony\Facades\FacadesBundle" now to avoid errors or add an explicit @return annotation to suppress this message.

  1x: Method "Symfony\Component\HttpKernel\Bundle\Bundle::build()" might add "void" as a native return type declaration in the future. Do the same in child class "Lagdo\Symfony\Facades\FacadesBundle" now to avoid errors or add an explicit @return annotation to suppress this message.

  1x: Method "Symfony\Component\DependencyInjection\Compiler\CompilerPassInterface::process()" might add "void" as a native return type declaration in the future. Do the same in implementation "Lagdo\Symfony\Facades\DependencyInjection\Compiler\CompilerPass" now to avoid errors or add an explicit @return annotation to suppress this message.

in Symfony 7.1 context.
I would be grateful if you fix it.

Hi,
That issue cannot be fixed on the 2.3.* release of this package, because it has to be compatible with older Symfony and PHP versions.
I've released a new version 3.0.0 for Symfony >=7.0 only.

@feuzeu Excellent! Thanks a lot!


Adding version as param in script

Summary of the Pull Request
What is this about?
I need to modify __version__.py for every change and then build using build_cli.ps1. Introducing this change I can invoke it like build_cli.ps1 -version "<version_number>
PR Checklist

[ ] Applies to work item: #xxx
[x] CLA signed. If not, go over here and sign the CLI.
[ ] Tests added/passed
[ ] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Info on Pull Request
https://www.cyberciti.biz/faq/bash-shell-find-out-if-a-variable-has-null-value-or-not/
What does this include?
Validation Steps Performed
How does someone test & validate?
Can be tested by running .\build_cli.ps1 -version "1.3.1-78b655501368ce5e78bda632834f2e5ecdfd1bbb" and .\build_cli.ps1

Testing in progress.


Create docs project framework

We don't have a standard framework for understanding the purpose and value of docs projects and scoping the work. This slows us down.
We should create a wiki page with the important questions to think through as you plan a docs project. These questions should help writers build confidence that a project is focused right and adding the right value. It will also help with alignment and collaboration.

Created: https://cockroachlabs.atlassian.net/wiki/spaces/PROD/pages/158040072/Docs+Project+Planning+Framework. We'll start using in for the next projects and iterate.


fix datetime range

Can one of the admins verify this patch?

How do I reproduce this issue? Please let me know the steps. Thank you.

Please use the schedules in demo.js to reproduce. Thank you. @dongsik-yoo
demo.js.zip

Thank you for your effort and PR. But this data must be TZDate type, not number type. So I could reproduce this issue with your event data and I found a code problem. We will fix this by different solution.
datetime.js
    convertStartDayToLastDay: function(d) {
        var date = new TZDate(d);
        var isStartOfDay = datetime.isStartOfDay(d);

        return isStartOfDay ? date.setDate(date.getDate() - 1) : date;
    },

Thank you.

I'll fix this on #471. Close this.


Dev only configs and deployment modules

Why
We'd like to have smaller deployment images. Marking dev-only dependencies as such will allow us to remove them from deployment.
What changed

Added a dev section to module definitions
Moved packages into the replit section
Added deploymentModules output for the flake
Use deploymentModules to build ocis
Removed productionOverrides

Previously we could build for Python 3.10 for development with:
nix build .#'"python-3.10"'

which is just short for
nix build .#modules.'"python-3.10"'

Now you can build a module for deployment:
nix build .#deploymentModules.'"python-3.10"'

Building an oci layer will use the deployment module if you are at this commit or later:
nix build .#all-phony-oci-bundles.'"python-3.10:v27-20231003-f0f410c"'

Test plan

Make sure new output JSON files are not changed from the previous one because of this upgrade
Make sure OCI images contain the contents of the deployment images
Make sure deployments are not broken for any of the templates we maintain

Rollout
Describe any procedures or requirements needed to roll this out safely (or check the box below)

[ ] This is fully backward and forward compatible

After reverting the productionOverrides change, most modules stayed the same. Only exceptions are node-with-prybar, python-with-prybar, and swift.


Hi, Ping, let's make Ultimate Instagram Tool!

Hi, ping! Sorry about writing here in issues but I couldn't find any your contact.
My name is Daniil and I'm the head of Instagrambot organisation. Let's work together for a big and powerful Instagram tool. Contact me if you want to unite our forces.
https://t.me/okhlopkov
<EMAIL_ADDRESS>Let's work together.

@ohld
Your issue report does not conform to the issue template that has been specified for this repo:
https://raw.githubusercontent.com/ping/instagram_private_api/master/.github/ISSUE_TEMPLATE.md
Please edit your issue to comply with the template requirement.
This issue will be closed after 24 hours if no followup action is taken.

[This comment is auto-generated. ref=notemplate]

Still waiting for your response.

@ohld You have already posted here before, but I'll repeat myself to be clear. I'm absolutely do not support botting and am therefore not interested.


isAfter Validation

Hi,
 var test = moment("04-05-2016", "DD-MM-YYYY", true).isAfter("04-07-2016");
 var test = moment("04/05/2016", "DD/MM/YYYY", true).isAfter("04/07/2016");

test return TRUE!
with "YYYY-MM-DD" works.
Please can someone tell me what the issue!
Thanks

This is because your second date, in your after, is not specifying a format. You should be getting a deprecation warning about construction falling back to JS date. What this means is that the browser is interpreting that string however it wants. Moment has no control over this.
In this case, the browser is probably interpreting 04-07-2016 as April 7 2016 (US Style), instead of the European style you wanted it interpreted as. Since May is in fact after April, you get the result you are seeing.
Instead, just change to the following:
moment("04-05-2016", "DD-MM-YYYY", true).isAfter(moment("04-07-2016", 'DD-MM-YYYY'))
false

moment("04-05-2016", "DD-MM-YYYY", true).isAfter(moment("04/07/2016", 'DD/MM/YYYY'))
false


SSH Local Forward

Hello,
My goal is to access an http server listening only to localhost through the bastion.
kind of ssh -L 9090:localhost:9090 server42
I tried to :
ssh -L 9090:localhost:9090 -t admin@bastion -- someuser@server42
But without success.
I've found in (bastion) /etc/ssh/sshd_config there is
AllowTcpForwarding no
Setting to yes didn't help.
Is it a good idea to change th bastion sshd_config ? Is there a better way ?
PS: the http server is https://cockpit-project.org

Posted to wrong repo


update fake_driver

What this PR does / why we need it:
This PR is used to update fake_driver so it can be used to create batch of storages.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

There are some configurations, you can add it like below:
[fake_driver]
fake_pool_range=1-200 # Means pool number for each storage is a random number between 1 and 200.
fake_volume_range=1-2000 # Means volume number for each storage is a random number between 1 and 2000.
fake_api_time_range=0.1-0.5 # Means each API from driver to device cost time is randome between 0.1 and 0.5.
fake_page_query_limit = 500 # Means page limitation is 500 which will be used for batch volume list.

Codecov Report

Merging #204 into master will decrease coverage by 0.72%.
The diff coverage is 34.21%.

@@            Coverage Diff             @@
##           master     #204      +/-   ##
==========================================
- Coverage   41.80%   41.08%   -0.73%
==========================================
  Files          64       64
  Lines        4296     4311      +15
  Branches      485      490       +5
==========================================
- Hits         1796     1771      -25
- Misses       2425     2465      +40
  Partials       75       75

Impacted Files
Coverage Δ

dolphin/drivers/fake_storage/__init__.py
37.07% <34.21%> (-18.48%)
:arrow_down:

dolphin/drivers/driver.py
56.52% <0.00%> (-11.23%)
:arrow_down:

dolphin/cryptor.py
72.72% <0.00%> (-4.20%)
:arrow_down:

dolphin/wsgi/common.py
64.28% <0.00%> (-3.46%)
:arrow_down:

dolphin/task_manager/tasks/task.py
26.92% <0.00%> (-2.71%)
:arrow_down:

dolphin/api/validation/validators.py
44.35% <0.00%> (-1.74%)
:arrow_down:

dolphin/api/v1/storages.py
73.33% <0.00%> (-1.22%)
:arrow_down:

dolphin/api/common/__init__.py
28.35% <0.00%> (-1.06%)
:arrow_down:

dolphin/api/common/wsgi.py
22.64% <0.00%> (-0.82%)
:arrow_down:

dolphin/context.py
73.46% <0.00%> (-0.54%)
:arrow_down:

... and 11 more

LGTM


Report build status to FinishBuild

If depot build returns an error, the CLI will report {"status": "error"} to the API, otherwise {"status": "success"}

https://app.planetscale.com/depot/depot/deploy-requests/7


If loop is provided, don't do cleanup

If a loop parameter is provided to run(), don't do any of the cleanup steps. In this scenario, the caller is indicating that they need to do custom things with the loop, and the loop is created elsewhere. Therefore it should be cleaned up elsewhere as well.  Also we should not shutdown the exectutor, nor cancel the currently pending tasks.  Perhaps all we do is return after run_forever() unblocks.

Since an executor can also be provided, we should probably have a parameter for whether to shutdown the executor too.
Actually, the more I think about it, if the caller provides an executor, then we should not shut it down. Better to have the caller manage their own executor.

I'm closing this.  aiorun has now gotten some usage and nobody has asked for or supported this idea.


register

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/121639
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.7 -m "<description of version>" 015271525e6ab15a875577f6b435ff6e5ba0d011
git push origin v0.2.7


fix(dashboard): Fix scroll behaviour in DashboardBuilderSidepane

Fix wrong scroll behaviour in CHARTS tab on DashboardBuilder
BEFORE
https://user-images.githubusercontent.com/29536522/182790268-5a25504a-db20-4658-94cc-147e89698346.mov
AFTER
https://user-images.githubusercontent.com/29536522/182790485-6b356690-5d2b-40d5-b4d8-71498704adb7.mov
TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API
@michael-s-molina @kgabryje @lyndsiWilliams

@michael-s-molina @kgabryje @lyndsiWilliams @hughhhh Can you review it?

/testenv up

/testenv down


[BUG] Entra ID Risks Module - Values are set to null instead of 0

This make logic app Control Actions fails if we check for UserFailedMFACount or UserMFAFraudCount or SuspiciousActivityReportCount  greater than 0 as Null is not an integer.
https://github.com/briandelmsft/STAT-Function/blob/48f9183ac44d0415c28813d6279f4f7a281b3276/modules/aadrisks.py#L20C3-L22C56
This is only when the data has accounts which do not exist in Entra ID (I think?).

@piaudonn how do you think we should handle this?  On the one hand the check may not be performed based on the input settings to the module, so in that case null makes sense.  And, if someone is turning off the check, they really shouldn't be evaluating it.  But, if the check is performed and there's no data, I think 0 is the right outcome, but isn't that already happening?
https://github.com/briandelmsft/STAT-Function/blob/48f9183ac44d0415c28813d6279f4f7a281b3276/modules/aadrisks.py#L62-L68

@piaudonn after our discussion I looked into this issue further with the unenriched entities in mind.  If the entity is found via IdentityInfo, the base module still then takes that UPN and goes to the graph to finish the enrichments, if the graph call fails it is passed as a 'RawEntity' only.  If we don't find it via IdentityInfo it is also passed as a 'RawEntity' only.
If it's a 'RawEntity' only, this module doesn't touch it as there won't be an id property:
https://github.com/briandelmsft/STAT-Function/blob/48f9183ac44d0415c28813d6279f4f7a281b3276/modules/aadrisks.py#L15-L17
If there's no entities processed, we don't execute the sums:
https://github.com/briandelmsft/STAT-Function/blob/48f9183ac44d0415c28813d6279f4f7a281b3276/modules/aadrisks.py#L85-L92
and the return will look like this:
{
  "AnalyzedEntities": 0,
  "FailedMFATotalCount": null,
  "HighestRiskLevel": "",
  "MFAFraudTotalCount": null,
  "SuspiciousActivityReportTotalCount": null,
  "ModuleName": "AADRisksModule",
  "DetailedResults": [],
  "RiskDetectionTotalCount": null
}

which is coming from the class definition:
https://github.com/briandelmsft/STAT-Function/blob/48f9183ac44d0415c28813d6279f4f7a281b3276/classes/__init__.py#L420-L431


Support options on matcher or response

Some options are to do with matching and some to do with responding, e.g.
mock('http://example.com', 200, {
  delay: 1000, // response
  headers: {head1: 'head1'}
})

I propose supporting this as well
mock({
  matcher: 'http://example.com',
  headers: {head1: 'head1'}
}, 200, {
  delay: 1000
})

The principle motivation for this is to allow using the - now quite wide range - of matching options within the first matcher parameter, therefore keeping an intuitive api: .mock(matchingStuff, respondingStuff). At present the following is the case .mock(someMatchingStuff, someRespondingStuff, someMoreMatchingStuff), which means it's harder to see at a glance what the mocking behaviour is.
Note that supporting merging response options into the second parameter is not in this proposal as it would be a breaking change (some edge cases in decisions made about whether to treat an object response as config or a json response)
This might not be the best solution to address this concern

May also want to think about aliasing url to matcher - if we're going down the route of enabling a 'matcher config object' as the first parameter, then url feels like a good catch all name for all the string matchers

Question - should ALL options be possible to specify on the first parameter
Or should there be friendly errors when the user uses an option in the wrong place


cmd/cue: have a single source of truth for cli docs

Originally opened by @mpvl in https://github.com/cuelang/cue/issues/9
This likely means that the cli docs should be generated from the tool code.

My 2c: I think we should start moving towards all canonical documentation being on the website. Go already started doing this with https://go.dev/ref/mod, for example. Then go help modules is a short summary with HTTP links, rather than dozens of pages printed out to the terminal, which overwhelm almost anyone.
I also feel like markdown-like styling is helpful. Headers, links, code blocks, and so on. That is technically possible on the terminal with something like man pages, but I think web pages are generally more accessible to the majority of users, particularly when there is so much information.
We could and should keep cue help, but its contents should be limited in size and complexity. Packagers or distros could always ship the HTML pages alongside cmd/cue so that all the docs are available offline.

Adjacent to this issue, https://alpha.cuelang.org/docs/reference/cli/ is now available.

I believe we should close this due to the work that has already happened and in favor of automating the structure of https://cuelang.org/docs/reference/cli/ via https://github.com/cue-lang/cue/issues/3204.


CIF: Emissions Intensity Report Enhancements

This EPIC captures lower priority program area enhancement requests for the emissions intensity form.

Closing EPIC as complete.


Prettys the code samples on the README

Obviously optional and completely decorative, I thought I'd pretty up the syntax of the code samples.

thanks for this. I've updated my README.md file with your pretty syntax directly without the pull/merge thing.


Elasticsearch chart throws errors

Is this a request for help?:
Not really
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Bug report

Version of Helm and Kubernetes:

helm version
Client: &version.Version{SemVer:"v2.6.1", GitCommit:"bbc1f71dc03afc5f00c6ac84b9308f8ecb4f39ac", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.6.0", GitCommit:"5bc7c619f85d74702e810a8325e0a24f729aa11a", GitTreeState:"clean"}

kubectl  version
Client Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.6", GitCommit:"4bc5e7f9a6c25dc4c03d4d656f2cefd21540e28c", GitTreeState:"clean", BuildDate:"2017-09-15T08:51:09Z", GoVersion:"go1.9", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.4+coreos.0", GitCommit:"4bb697e04f7c356347aee6ffaa91640b428976d5", GitTreeState:"clean", BuildDate:"2017-08-22T08:43:47Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

Which chart:
incubator/elasticsearch
What happened:
After spinning up the ES cluster, the cluster seems responsive, but the data node logs are full of these errors:
[2017-09-20 14:46:54,249][WARN ][io.fabric8.elasticsearch.discovery.kubernetes.KubernetesUnicastHostsProvider] [logging-efk-es-elasticsearch-client-2081390332-fdfzr] Exception caught during discovery: An error has occurred.
io.fabric8.kubernetes.client.KubernetesClientException: An error has occurred.
        at io.fabric8.kubernetes.client.KubernetesClientException.launderThrowable(KubernetesClientException.java:57)
        at io.fabric8.kubernetes.client.dsl.base.BaseOperation.get(BaseOperation.java:125)
        at io.fabric8.elasticsearch.cloud.kubernetes.KubernetesAPIServiceImpl.endpoints(KubernetesAPIServiceImpl.java:35)
        at io.fabric8.elasticsearch.discovery.kubernetes.KubernetesUnicastHostsProvider.readNodes(KubernetesUnicastHostsProvider.java:112)
        at io.fabric8.elasticsearch.discovery.kubernetes.KubernetesUnicastHostsProvider.lambda$buildDynamicNodes$0(KubernetesUnicastHostsProvider.java:80)
        at java.security.AccessController.doPrivileged(Native Method)
        at io.fabric8.elasticsearch.discovery.kubernetes.KubernetesUnicastHostsProvider.buildDynamicNodes(KubernetesUnicastHostsProvider.java:79)
        at org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing.sendPings(UnicastZenPing.java:335)
        at org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$2.doRun(UnicastZenPing.java:249)
        at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.SocketTimeoutException: connect timed out
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
        at java.net.Socket.connect(Socket.java:589)
        at com.squareup.okhttp.internal.Platform.connectSocket(Platform.java:101)
        at com.squareup.okhttp.internal.io.RealConnection.connectSocket(RealConnection.java:137)
        at com.squareup.okhttp.internal.io.RealConnection.connect(RealConnection.java:108)
        at com.squareup.okhttp.internal.http.StreamAllocation.findConnection(StreamAllocation.java:184)
        at com.squareup.okhttp.internal.http.StreamAllocation.findHealthyConnection(StreamAllocation.java:126)
        at com.squareup.okhttp.internal.http.StreamAllocation.newStream(StreamAllocation.java:95)
        at com.squareup.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:281)
        at com.squareup.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:224)
        at com.squareup.okhttp.Call.getResponse(Call.java:286)
        at com.squareup.okhttp.Call$ApplicationInterceptorChain.proceed(Call.java:243)
        at io.fabric8.kubernetes.client.utils.HttpClientUtils$3.intercept(HttpClientUtils.java:110)
        at com.squareup.okhttp.Call$ApplicationInterceptorChain.proceed(Call.java:232)
        at com.squareup.okhttp.Call.getResponseWithInterceptorChain(Call.java:205)
        at com.squareup.okhttp.Call.execute(Call.java:80)
        at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:210)
        at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleGet(OperationSupport.java:205)
        at io.fabric8.kubernetes.client.dsl.base.BaseOperation.handleGet(BaseOperation.java:510)
        at io.fabric8.kubernetes.client.dsl.base.BaseOperation.get(BaseOperation.java:118)
        ... 11 more

What you expected to happen:
As far as I can tell it's working, but I certainly expect the logs not to be riddled with warnings
How to reproduce it (as minimally and precisely as possible):
I used the latest chart and all the default values except for data.storageClass:
helm install --name logging-efk-es incubator/elasticsearch --set data.storageClass=standard --namespace logging
Anything else we need to know:
I swapped over to https://github.com/clockworksoul/helm-elasticsearch ; this doesn't have the errors, but also doesn't support persistence. Though he says it's coming soon...

@jyoungs Could you please confirm that your elasticsearch is really working?
I see this message, when trying to interact with it
{"error":{"root_cause":[{"type":"master_not_discovered_exception","reason":null}],"type":"master_not_discovered_exception","reason":null},"status":503}```

It looks like ES is trying to access the kubernetss API on port 80, those getting a connection timeout:
tcp        0      1 <IP_ADDRESS>:60004       <IP_ADDRESS>:80            SYN_SENT
Why wouldn't it try to access it using 443?
Thanks!

The problem has been solved, can be closed, thank you


When will the code be released? Thanks.

Unfortunately, we have some delay in releasing the code. We sincerely regret the inconvenience. We have the updated the readme.

2 months...already

Thank you so much for the patience. The preliminary version for the imagenet dataset is available in the imagenet folder.


where i find primary_ca and backup_ca ? please help me, i use universal-lwmqtt example

how i add primary_ca and backup_ca?

It depends on your board but in general, these are stored in ciotc_config.h unless you are using the MKR-1000 board in which case the CA is set using the firmware updater.  Some notes are in the documentation, please reopen if you see an error.

thanks


Support reordering work items

Support drag and drop for mouse support, and shortcuts like "Ctrl + Cursor Up/Down".
Move children when moving a parent

Agreed this would be a valuable feature; being able to reorder work items as your creating them allows them to be created in the sequence you want, but you may not decide on the sequence until you finish typing in all the items and can think about them as a whole, before hitting Save.


what is the standardized distributed training method for pytorch-operator

Hi，I have been deployed pytorch-operator for distributed training on k8s cluster, and struggled with this issue for a while.
Here is my yaml.
( my k8s can only schedule two nodes, named gpu-233 and gpu-44, all the command in my case is excuted on the node of gpu-233. I just did it the same way in mpi-operator successfully )

In my case, i have two nodes named gpu-233 and gpu-44 with 3 nvidia gpus and 1 nvidia gps respectly, and wanna start two distributed training process, one should be excuted by the node "gpu-233" with one gpu on the pod "mmpose-master-0", and another one should be excuted by the node "gpu-44" with one gpu on the pod "mmpose-worker-0"
After "kubectl apply -f my_yaml" for a while, when submitting "kubectl logs mmpose-worker-0", i can see no log info from the pod of worker, while the pod of master prints correct logs by the same command. At the same time, i found both the nodes of "gpu-233" and "gpu-44" has occupied one gpu respectly, which can be confirmed by  "kubectl-view-allocations -r gpu".
Thus, i infer that the pod of worker has applied for node "gpu-44" and occupied one gpu successfully, but did not excute the torch.distribute.launch successfully.
the info about pod of worker are shown below:
submitting "kubectl describe pod mmpose-worker-0"

After a period of time, the pod of worker report error, and the logs about error is shown below:

I know there have been a bundant of  topics about distributed training with torch.distribute.launch in pytorch-operator, and your project members have left a lot of patient responses on these topics, I have to say thank you guys for such great works!
But please forgive my carelessness, i did can not found an explicit standardized method to launch an distributed training with specific nodes and gpus.
Do you think, what's going wrong in my case? @tenzen-y @johnugeorge
Thank you in advance ! any hints would be helpful to me~

You may try to understand how MASTER works, you have 2 pods with different IPs, how they can talk to each other, it comes the master service.
In your case, you setup your MASTER in <IP_ADDRESS> which means setup the master service locally, then the 2 pods will wait for another peer to join since NNODES=2 means each master should wait 2 nodes to start.

@kuizhiqing Thanks for your reply my frined~
the available docs about config of pytorch-operator is insufficient for me, and my background knowledge on deloying pytorch-operator is based on mpi-operator, where "launcher" declares the command to launch training, and "worker" calls resources.
But it seems different in pytorch-operator.
I don't know if "MASTER_ADDR" "MASTER_PORT"and "node_rank" should be manually setted like what in my yaml ?
Supposing i’m going to deploy distributed training with 2 nodes(gpu-233 and gpu-44) with one gpu per node, how should i modify the above yaml？

@deepanker13 Hi, thanks for your kind help~ could you please give me another link? cause it is out of date [https://lambdalabs.com/blog/multi-node-pytorch-distributed-training-guide](url)

You can probably access the link via https://lambdalabs.com/blog/multi-node-pytorch-distributed-training-guide.

@ThomaswellY
You can  access the link via https://lambdalabs.com/blog/multi-node-pytorch-distributed-training-guide.

@tenzen-y
Thanks for your help ! I have read https://lambdalabs.com/blog/multi-node-pytorch-distributed-training-guide carefully, I think its a good reference of applicating distributed training on k8s clusters with inter-connected baremetal servers, but It lacks of the methods of how to applicate the distributed training by training-operator, more specifically how to write the yaml (that's the whole points of this repo right?)
There are several related discuss founded in the repo, like: https://github.com/kubeflow/training-operator/issues/1713 and https://github.com/kubeflow/training-operator/issues/1532, both of them use the same way of launching distributed training like [ "/bin/bash","-c","python3 -m torch.distributed.launch" ……] as what i did in the yaml , and the way their yaml are structured have not been rejected or criticized by other community member.
TBO, my friend, @deepanker13, the yaml you posted above did not consists of any explicit command about torch.distributed.launch or specifying args like "node_rank" ,"nproc_per_node" and so on. So i have to kindly doubt whether this  will work in my case.
you have mentioned "change the entrypoint and cmd to :-ENTRYPOINT ["python3",relative path to your script according to work dir] CMD []", and i have seen this standardized command for launching distributed training in training-operator before, would you mind give me a more concrete example yaml ?

@ThomaswellY I have followed the official documentation https://www.kubeflow.org/docs/components/training/pytorch/
and the example given in it in Creating a PyTorch training job section
, where we don't need to mention torch.distributed.launch.
https://github.com/kubeflow/training-operator/blob/master/examples/pytorch/simple.yaml

@deepanker13 Sorry my friend, the link you pointed is out of date, do you mean this sample yaml? https://github.com/kubeflow/training-operator/blob/master/examples/pytorch/simple.yaml
however there is no dockerfile……

@ThomaswellY please try this link
https://github.com/kubeflow/training-operator/blob/master/examples/pytorch/simple.yaml

@deepanker13 Thank you for your kind help, my friend~
The yaml you provide did work, but only works on one-node-one-gpu training.
The central issue is still remained to be solved.
how to modify that yaml to start distributed train?
Iet me paste the main part of the yaml below:

as you can see, it applies for two pods(master and worker), master occupies two gpus, and worker occupies one gpu.
In my opinion, if this yaml really deployed an distributed training successfully, it should involves with three processes, two appened on master pod, and one happened on worker pod.  the logs printed on these two pods should be intuitively different.
But let to show the logs printed on these two pods:

In fact it's exactly the output of the single-gpu traing on my baremetal server.
It seems the process happened on these two pods are totally same ! this is not distributed training at all.
And script of minist.py is too simple, it's seems not designed for distributed training, or maybe it can achieve it with quite lots of modification, and how to modify it is what i have been seeking from begin to end.
@johnugeorge @kuizhiqing I really want to know, did train-operator has ever provided any example yaml of distributed training on pytorch-operator?
If not, what's advantage of  pytorch-operator compared to submitting "bash dist_train.sh" on baremetal server, which is also easy to use with torch.distributed.launch

@ThomaswellY  How did you conclude that there is no distributed training?
DistributedDataParallel won't start unless all participating nodes have joined https://github.com/kubeflow/training-operator/blob/master/examples/pytorch/mnist/mnist.py#L136
You can check examples in https://github.com/kubeflow/training-operator/tree/master/examples/pytorch


Test for monetary values

Trello card
Identify monetary values
Context
We need to identify where we use monetary values (e.g. £123,456) in our markdown and html files, so they can be moved to the values/variables system
Changes proposed in this pull request
New tests to scan markdown and html files for monetary values
Guidance to review
NB: These tests will not pass until the hard-coded values are removed
Pre-election period restrictions

[x] This change is permitted within the constraints of the pre-election period guidelines

DO NOT MERGE
these tests will not pass until the html/markdown files are corrected.

The code looks fine, but is it a "feature test"? Do we want to continue running it on every build, or is it more of a one-off thing to find instances of monetary values in static files? If the latter, I think it would be better as a Rake task.
Or if we want to run the check on a specific cadence (eg every day or week) it could be a job, added to the crontab. Apply has some examples of this sort of thing. https://github.com/DFE-Digital/apply-for-teacher-training/blob/main/app/workers/detect_invariants_daily_check.rb

@carlosmartinez good questions; I think we definitely do want to run this on every build (it's actually fairly quick to run) to immediately catch any new monetary values entering our content. I don't think a schedule will work well in this case: failing content could successfully be merged into the master branch if this test only ran on a daily/weekly schedule. And a rake task will be tricky for our content creators, who mainly rely on github actions to pickup issues rather than a local development environment.
We have similar content checks to verify URLs do not contain our hostname or "localhost" - these are defined as feature tests and run on build, and work effectively to alert the team when there are issues.

@carlosmartinez good questions; I think we definitely do want to run this on every build (it's actually fairly quick to run) to immediately catch any new monetary values entering our content. I don't think a schedule will work well in this case: failing content could successfully be merged into the master branch if this test only ran on a daily/weekly schedule. And a rake task will be tricky for our content creators, who mainly rely on github actions to pickup issues rather than a local development environment.
We have similar content checks to verify URLs do not contain our hostname or "localhost" - these are defined as feature tests and run on build, and work effectively to alert the team when there are issues.

Thanks. That makes sense. I feel like they're not really feature tests, and should probably run as a separate build step, but if there's precedent then 👍 to proceed!


spargebra-0.2.0 alpha3 < spargebra v0.2.8

crate spargegra released with oxigraph 0.3.0 is newer than the version released with oxigraph v0.4.0 alha.3.

Thank you for reporting this! Fix: #818

This has been fixed in follow-up alpha releases. https://crates.io/crates/spargebra/versions


[Question] How did you use vector in the kernel?

Hey,
I've looked into the project and seen something interested, I saw you used std::vector (specifically in shadow_hook.cpp in SharedShadowHookData struct to keep all the hooks and later to iterate over them)
And I was interested since I remembered that c++ STL and kernel doesn't go very well,
I tried to create a new file in the ddimon project and use std::vector but in compile time I got errors about using c++ exceptions in kernel (with /kernel flag).
Couldn't found any difference between my file to the existing one in the project (no file properties difference from what I saw).
So I was wondered how did you able to use std::vector in the kernel and without the compiler throw errors.
Thanks for the help,
Mor.

Hi,
To compile code with STL (containers), kernel_stl.h needs to be included before including any STL headers. Please try with the header and let me know if that works for you.
Thank you,

It does compile now, however I had some problems.
After isolating the problem it seems that std::vector is not working if the std::vector variable is a class variable.
I instead created pointer to the vector and initialize it using "new" in the initialize function,
when I'm done I use delete of course.
There is another thing that i've seen happening, wierdly happening only when using the ddimon (without any of my additional code) - I use WinDBG to track debug prints. Sometimes after using WinDBG and closing it while ddimon is installed I reopen it and try to capture kernel debug output and I get this message:

Only after restarting I can use WinDBG again. Did you experience something like this / do you know why it's happening?

Hi,
As for the first issue. are you using the vector inside a global object? If you place a std::vector object directly as a global object, its contractor should be called, but I am not sure when it is placed inside a plain struct (w/ no constructor). Can you share the struct declaration?
For the issue with DebugView, does this happen only when DdiMon (or HyperPlatform) is loaded? I have seen the same issue on Windows 10, but I seemed to happen regardless of if you installed DdiMon.

I think the constructor of std::vector is just not being called since creating class object is not calling the constructor of the class (this is the reason for the seperate initialize function),
to create the class object I allocate it using ExAllocatePoolWithTag and than in the initialize function I create the std::vector and save it's pointer.
If I use it as a class member:
class container
{
public:
	container(); // If I create class object this is not being called
	~container(); // Neither is this

	bool add_module(module* app_module);
	module* get_module(void* addr);
	bool is_in_container(void* addr);

	bool initialize();
	void finalize();
private:
	ModulesMap* m_modules_map;

	std::vector<module*> m_modules; // I instead use std::vector<module*>* to later create the std::vector
};

and the initialize function:
bool
container::initialize() {
	m_modules_map = static_cast<ModulesMap*>(ModulesMapInitialization());
	if (nullptr == m_modules_map) {
		return false;
	}

	m_modules = new std::vector<module*>;

	return true;
}

and just use it as:
m_modules->push_back(app_module);
The second issue:
I do use windows 10 for testing, you are right I recheck and it seems it happens after I open windbg second time with kernel debugging turn on.

Thank you for sharing the code. Right, constructor would not be called when ExAllocatePoolWithTag() or anything other than 'new' is used. It is an expected behaviour. If you use new or construct an object on stack or as a global object, its constructor should be called. To avoid new/delete, this can be an option.

Yeah I remember trying to use new but without kernel_stl functionality it didn't work, therefor I used allocation function instead of just creating class object (new that I know I can use new I will convert the code).
I have another unrelated question: When I install ddimon I see some lag in the programs running (the most obvious is gui apps), so for example if I run calc and move it's window fast it seems smooth but after I install ddimon and move the window it seems like it's stuttering.
I thought it might be the hooks, but after disabling them it still seem to stutter.
Have any idea why this is happening / what part of the hypervisor causing it?

You are welcome.


Step by step entry points

Besides the ignite-ui command without arguments, the same should be possible via:

ignite-ui new: Also starts the guide from project creation
ignite-ui add: Starts directly at the Add component/template step

Question: Should the add version also loop like it would after creating project to allow adding multiple views?

@damyanpetev Answer: No. Single view is all that is required.

@bazal4o moving the task to Sprint 3

@SlavUI  After a discussion with @kdinev , finally add will loop like it would after creating project. This gives the option to add additional components afterwards.


Fix typo in property name in sample

@eNeRGy164,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/add-ins/authenticate-a-user-with-an-identity-token.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Thanks again!


Where did .tag go in alpha.6?

With the release of alpha.6 it appears .badge was reintroduced and .tag was removed. The documentation still says .tag should be used; yet it does not exist.
https://v4-alpha.getbootstrap.com/migration/#labels-badges-and-tags
Possible merge error?

This was already fixed: #21565

Figured it was either doc error (docs always seem to lag the release), or merge as that has happened before with alpha.4.
Cheers!


Update to Factorio 2.0

Update to Factorio 2.0

I already did update this mod to Factorio 2.0 and I can send it to you.
If you have no intentions of doing so, I would appreciate info, so I can publish on my own., People deserve to have this excellent mod,

If you want to make LEP+ 2.0 be my guest.
It's MIT so all I need is credit for whatever you keep from my version.
PS: yeah, and once you get used to it all you start making lua mistakes in other languages.

Thank you, I already published new updated version, because I saw that people really love this mod and were waiting
https://mods.factorio.com/mod/Lighted-Poles-Plus
If you don't plan to update and don't have objections about how I used it, from now on, I will maintain it, because like others, I can not play Factorio without this mod


Add support for building Linux AppImage binary.

This PR adds support for building the Linux AppImage binary during CI workflow.
Overview
The workflow file is .github/workflows/appimage.yml and is structured as follows:
Step 1: Checks if the docker container exists or needs to be updated, if not, go to Step 3.
Step 2: Builds the appimage/docker/Dockerfile  for compiling packetry and creating an appimage.
Step 3: Runs pretty much the same workflow as the rust.yml workflow to compile & test packetry inside the docker container.
Step 4: Invokes a custom action appimage/action.yml to build the Linux AppImage binary.
Step 5: Uploads the Linux AppImage binary artifact.
Docker Image Notes

Docker image has two args:

GTK_VERSION sets the version of GTK sources to be downloaded and built.
NODE_VERSION sets the version of node to install for the use of Swatinem/rust-cache@v2

I took great care to build the image with minimal use of USER root but it turns out that was wasted because
GitHub Actions does not support containers running as anything but root:

Worse than that, it overrides $HOME for the root user with /github/home which of course causes all the
things to fail.
But even more worse than that, if you have the bright idea to provide /github/home in your container, GitHub actions will happily delete the contents.
Workaround is a combo of overriding the containers /etc/passwd to change root home dir to /github/home during the container build and then copying everything you need into $HOME before running the workflow.
Also see: https://github.com/actions/checkout/issues/1014

Docker images are stored on ghcr.io and have private visibility.
Docker images are named & tagged according to <repo>-gtk-<gtk-version>:<branch> so we don't run into issues when working on branches or PR's.

Outstanding issues

[x] Licenses
[ ] Configure DOCKER_REGISTRY_TOKEN for the packetry repo.
[ ] Desktop Icon File

Closed in favour of main-repo branch so it can actually be tested.


Unexpected behaviour if "type" is not specified for table

If you accidentally omit the "type" (geometry type) key in your mapping file, you get the postgres error Invalid type name "(2)", as imposm3 tries to execute this command:
SELECT AddGeometryColumn('import', 'osm_tablename', 'geometry', '3857', '', 2);
I'd say ideally the mapping file schema should be validated on import to avoid this failing halfway through a long -import -write job.

It is now an error if type is not set and it will exit immediately.


Resolve issue 39

@dz333
Changed e.to.mergeStmts(nstmts, false) to allow recv stmt gets prepended.

Great! Can you add a test to the src/test/tests/branchesCheck folder with the example from the issue (or something similar)?
See the other tests in that directory for how to specify solution files (that go in src/test/tests/branchesCheck/solutions) and memory files to specify the memory initial state for simulation (src/test/tests/branchesCheck/memInputs).
Once you add the test file I can also help make sure it's running properly.

Great! Can you add a test to the src/test/tests/branchesCheck folder with the example from the issue (or something similar)? See the other tests in that directory for how to specify solution files (that go in src/test/tests/branchesCheck/solutions) and memory files to specify the memory initial state for simulation (src/test/tests/branchesCheck/memInputs).
Once you add the test file I can also help make sure it's running properly.

Thanks for the feedback.
I have added some test files. Not sure if these tests are good. I tried to run the tests locally but there are some issues with my local bsc simulator.

I've merged it into main with a fix for the solution file

Thanks! @dz333


Disabled Qute language id pop-up after first appearance

Disabled Qute language id pop-up after first appearance and removed documentCache
Fix for #451
Signed-off-by: Alexander Chen<EMAIL_ADDRESS>

LGTM. I wouldn't mind confirming but this should disable the popup after the first time.

LGTM. I wouldn't mind confirming but this should disable the popup after the first time.

Yep, working as intended:

Something I noticed however: I was debugging workspaceTrust, and after disabling and re-enabling to test vscode-xml fix, the quarkus.tools.propertiesLanguageMismatch was set to ignore, even though the default is forceQuarkus. I never configured the setting, and even cleared my workspace cache before testing the untrusted workspace, so it seems unusual for this to happen. Thoughts?

LGTM. I wouldn't mind confirming but this should disable the popup after the first time.

Something I noticed however: I was debugging workspaceTrust, and after disabling and re-enabling to test a vscode-xml fix, the quarkus.tools.propertiesLanguageMismatch was set to ignore, even though the default is forceQuarkus, so the language id was never forced. I never configured the setting, and even cleared my workspace cache before testing the untrusted workspace, so it seems unusual for this to happen. Thoughts?

Then let's merge this.
Disable Language Updating will set it to ignore https://github.com/redhat-developer/vscode-quarkus/blob/master/src/extension.ts#L128 .

Disable Language Updating will set it to ignore https://github.com/redhat-developer/vscode-quarkus/blob/master/src/extension.ts#L128 .

Ah so I must have disabled it once.


Contributing ... or is this abandoned?

Pushing a year since the dependency called out was announced as deprecated: https://github.com/DataDog/dogapi
Would this repo/plugin/handler be considered obsolete or abandoned? If so, I'd like to work on an update ... or maybe there's a better repo. There's a ton of new capabilities available through the dogapi-rb gem that would require some updates to a datadog handler. Tough part is the namespacing in the Lita community to not mess up the community.
Help ... thoughts? :smile:

Happy to accept PRs!  I should probably look through and give this some care and feeding as well, it's been a while.

@desktophero A question - what features / functionality are you looking for?  Two reasons this plugin hasn't evolved much:

The discovery process for a metric or graph is usually so much faster to do in the DD UI and then push back to Slack via @slack-foo mentions.

Auto-completing metric names is a serious pain with all of the current chat services.  Github's way around this with their chatops work was to create a custom client that could auto-complete, which is a little outside the scope of this plugin.  :)

One of the things I was thinking about, was an "alias" command, because the common use case "what's up with this box?" has a few fixed sets of graphs, right?  CPU/Memory/Disk/Network, etc.  And so on, for other questions ("what's the work queue pipeline's status?", etc) all could have a basic alias that took a key/value argument for simple things.

I would like to see it updated. reason: It would be cool to be able to react on some incoming webhook and push out the data to a slack channel. this would fit into the 'alias' category as well. I'm doing some PoC around Continuous Delivery and could see this step as a follow up automated push right after finishing the smoke test for deployment.

@desktophero - BTW, the deprecated dependency you mentioned is for DataDog's Python library.  Even though the gem is named dogapi, the actual library this Ruby plugin uses comes from https://github.com/DataDog/dogapi-rb, which seems in active use to me.


how to use parameters

After reading the documentation, it's unclear to me how to reference parameters (corresponding to "ref:" in cloudformation). Could you add some more documentation?

Hey Trond -- Absolutely, I appreciate the feedback! Not sure how deep you dove through the website, but the Module Digest page goes a bit more into Intrinsic Functions like Ref (and includes an example using Add-FnRef as well!). Below are some handy links, examples, and details around how I approached writing this module.

Useful pages on Intrinsic Functions and overall usage (i.e. remember to surround functions in parentheses when using it directly as a parameter value for another function):
Module Digest: http://vaporshell.io/docs/digest#intrinsic-functions
Function Glossary for Intrinsic Functions: http://vaporshell.io/docs/glossary/#intrinsic-functions
Tips & Tricks: http://vaporshell.io/docs/tips

Example
You can store functions in a variable then add the variable to another function's parameter as the value (top section - useful if you might be placing that same function elsewhere in your config) or call the function directly as a parameter (See the KeyName' parameter on New-VSEC2Instancebelow). ForAdd-FnRef, the Ref` parameter is positional so you can save some typing by just including the ref value right after, as done below as well:
$template = Initialize-Vaporshell

<# Add InstanceSecurityGroup, RegionMap and KeyName here #>

$RegRef = Add-FnRef $_AWSRegion
$ImgId = Add-FnFindInMap -MapName "RegionMap" -TopLevelKey $RegRef -SecondLevelKey "AMI"
$SecGrps = Add-FnRef "InstanceSecurityGroup"

$Ec2Ins = New-VSEC2Instance -LogicalId "MyInstance" `
                            -SecurityGroups $SecGrps `
                            -ImageId $ImgId `
                            -KeyName (Add-FnRef "KeyName")

$template.AddResource($Ec2Ins)

When building this module, I wanted to make function names as predictable as possible given the amount of options to include in CloudFormation templates. I grouped Vaporshell functions as close to AWS documentation's grouping of them, i.e. Intrinsic Functions, Resource Types, Property Types, Resource Attributes, etc. I also tried to follow naming conventions when building each "group" of functions within Vaporshell:

Intrinsic functions

Add-FnfunctionName, i.e. Add-FnRef, Add-FnGetAtt, Add-FnGetAZs
Ref is a unique case since it's listed as an intrinsic function, but AWS did not name it Fn::Ref

Condition functions

Add-ConfunctionName, i.e. Add-ConAnd, Add-ConEquals

Resource types

New-VStypeName, i.e. New-VSEC2Instance, New-VSAutoScalingAutoScalingGroup

Resource properties

Add-VSpropertyName, i.e. Add-VSApiGatewayApiKeyStageKey, Add-VSAutoScalingAutoScalingGroupTagProperty

Serverless Application Model

Same as Resource / Property Types, except these use "SAM" instead of "VS" in the function name
New-SAMApi, New-SAMFunction, New-SAMSimpleTable
'Add-SAMApiEventSource, Add-SAMS3LocationObject`

Vaporshell core functions

All have "Vapor" or "Vaporshell" in the name. These typically involve working with the template object, i.e. Initialize-Vaporshell, New-VaporResource, etc.

Hopefully this helps! I've worked most of this into the docs on the website I believe, but any and all feedback/criticism/etc is appreciated!!
Let me know if this answers your question and if you have any suggestions my way for improving the documentation!

Ah, that makes sense. Just didn't look in the right place. The template I looked at takes a parameter but doesnt use it, that's probably what threw me off.

No worries! Seems odd for someone to add in a parameter to their template that doesn't get referenced elsewhere, but to each their own ¯_(ツ)_/¯