[wip] feat: add error codes

List of error codes (so far):
- validation_failed # Check the invite email thing
- bad_json
- email_exists
- phone_exists
- bad_jwt
- not_admin
- no_authorization # When there's a missing header
- user_not_found
- session_not_found
- flow_state_not_found
- flow_state_expired
- signup_diabled # Check Signups not allowed for otp
- user_banned
- over_email_send_rate
- over_sms_send_rate
- provider_email_needs_verification # Potentially distingush between already sent and newly sent
- invite_not_found # Check with user_not_found similar cases
- bad_oauth_state
- bad_oauth_callback
- unsupported_oauth_provider
- unexpected_audience
- last_identity_not_deletable # Or rename
- email_conflict_identity_not_deletable
- identity_already_exists
- email_provider_disabled
- phone_provider_disabled
- too_many_enrolled_mfa_factors
- mfa_factor_name_conflict
- mfa_factor_not_found
- mfa_ip_address_mismatch
- mfa_challenge_expired
- mfa_verification_failed
- mfa_verification_rejected
- insufficient_aal
- captcha_failed
- saml_provider_disabled
- manual_linking_disabled
- sms_send_failed
- email_not_confirmed
- phone_not_confirmed
- reauth_nonce_missing
- saml_relay_state_not_found
- saml_relay_state_expired
- saml_idp_not_found
- saml_assertion_no_user_id
- saml_assertion_no_email
- user_already_exists
- sso_provider_not_found
- saml_metadata_fetch_failed
- saml_idp_already_exists
- sso_domain_already_exists
- saml_entity_id_mismatch
- conflict
- provider_disabled
- user_sso_managed # User data can only be updated via SSO
- reauthentication_needed
- same_password

Very nice and granular error codes! This will bring the DX of Supabase's authentication module much closer to that of Firebase. Great work. 😎

Very nice and granular error codes! This will bring the DX of Supabase's authentication module much closer to that of Firebase. Great work. 😎

Note that at this point these are just extractions, they're not definitive in shape or form.

would be great if we can create an ErrorCode type for this instead of using normal strings for ease of maintainability

Furthermore, changing status codes is not a backward incompatible change as the client library does not care about status codes. It only cares about 5XX vs 4XX.

Furthermore, changing status codes is not a backward incompatible change as the client library does not care about status codes. It only cares about 5XX vs 4XX.

I would argue that changing status codes is a backwards incompatible change; if there is no stability in the provided error codes, then there isn't much value in them.

Furthermore, changing status codes is not a backward incompatible change as the client library does not care about status codes. It only cares about 5XX vs 4XX.

I would argue that changing status codes is a backwards incompatible change; if there is no stability in the provided error codes, then there isn't much value in them.

I agree, but there was never an official contract about error codes with GoTrue/Supabase Auth. Yes, we can pretend that there is an implicit contract in this case, and that would be true, but that means it's impossible to even change capitalization in error messages, or ever evolve them.
This is why right now we're adding an official, maintainable error strategy by using error strings that won't be easily renamed, with a versioning strategy, and a proper framework for using the correct HTTP codes.
Once this gets merged, the official contract is:

Error codes (and optional payloads assumed by the error codes, like weak_password) only change based on requested API version.
Error messages can change at any time. They are a developer aid, not a message to be shown to users (though you can show them if that works for you).
HTTP status codes are unlikely to change, but may in certain cases (400 <-> 422 <-> 404). They represent proper HTTP semantics, and shouldn't be relied strictly upon in your application.

is this only for auth-js ? and supabase-js not included?

This is currently "@supabase/supabase-js": "^2.41.1"

@mashwishi From your code snippet I don't really understand how that log message is getting generated, but I believe that AuthApiError object will have a code property on it you can use.
Something like this:
console.log(response.error.code);

@mashwishi From your code snippet I don't really understand how that log message is getting generated, but I believe that AuthApiError object will have a code property on it you can use.
Something like this:
console.log(response.error.code);

Will test that out today.

@mashwishi From your code snippet I don't really understand how that log message is getting generated, but I believe that AuthApiError object will have a code property on it you can use.
Something like this:
console.log(response.error.code);

that's weird.


i find that there are two types of clients, I have a lot of write requests, which is more efficient?

1. my first question:
use jdbc：
https://github.com/ClickHouse/clickhouse-java/blob/main/examples/jdbc/src/main/java/com/clickhouse/examples/jdbc/Basic.java
use client:
https://github.com/ClickHouse/clickhouse-java/blob/main/examples/client/src/main/java/com/clickhouse/examples/jdbc/Main.java
I have a lot of write requests, and need to write in batch mode,  so  which is more efficient?  can  any one tell me, thanks!
2. my second question:
dose client support config retry count ?  i want retry 3 times when write to ck error

@z7658329
as far as I may see from their code and documentation:

just client  - is client abstraction of  http/file/grpc client. It is not wrapped with JDBC API
jdbc - is "just client" wrapped with JDBC

Performance will depend on your use case and the destination your are writing to. Would you describe it more?


Update Resources.resx.lcl

Translation recommendations.

"Encoding": "正在編碼" -> "編碼".
"Fallback Encoder": "後援編碼器" -> "備援編碼器".

Summary of the Pull Request
Translation recommendations only.
PR Checklist

[ ] Applies to #xxx
[ ] CLA signed. If not, go over here and sign the CLA
[ ] 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
[X] None of the above.

Info on Pull Request
This is the first time I pulled a request.
Only one file was modified.
Validation Steps Performed
It is supposed that it will break nothing with texts changed only.

Please make first a issue. And for localisation issues our localisation teams take care of it.

Content from the README.md
October 2020 Update
Our goals for 0.25 release cycle was to focus on stability, accessibility, localization and quality of life improvements for both the development team and our end users. Our first end to end localization pass has been done. We know it isn't perfect but we are in 17 languages now. If you find an issue, please file a localization bug.

For localization issues, please send localization bug.


types(ui/snackbar): add BasicAttributes

Checklist

[ ] Fix linting errors
[ ] Tests have been added / updated (or snapshots)

Change information

Codecov Report

Merging #635 (9d84ba0) into dev (7d421bc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #635   +/-   ##
=======================================
  Coverage   95.41%   95.41%
=======================================
  Files         217      217
  Lines        5255     5255
  Branches      982      982
=======================================
  Hits         5014     5014
  Misses        232      232
  Partials        9        9

Continue to review full report at Codecov.

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


:refreshVersionsMissingEntries allows to migrate an existing projet

🚀 Description
Add a task refreshVersionsMissingEntries that populates the versions.properties file with all hardcoded versions, including plugins.
This is mostly a refactoring of something that was done inside :buildSrcLibs
I have a magic regex to make the build use the placeholder version here ==> https://regexr.com/5ti1j
🧪 How Has This Been Tested?
It was tested in projects like

https://github.com/kotest/kotest/pull/2280
https://github.com/necatisozer/kotlin-analytics/pull/1
https://github.com/pavlospt/refactored-umbrella/pull/21
https://github.com/kittinunf/fuel/pull/811

✅ Checklist

[x] I have read the guidelines for the development process
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

@LouisCAD sorry for the git mess. It should be all good now. Famous last words.


⚠ Samsung has degraded performance

In 5591c95, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2020 ms

Resolved: Samsung performance has improved in bb728ee.


Remove most of the autonomous path overshoot (saves 1.5 seconds from the demo path)

Demoed infront of the team


refactor: add total distance in log message

resolve #3203

@yuichiroaoki @mattsse how do you feel about including this as a logging field, and not part of the message?

like
info!(target: "downloaders::bodies", %distance, "Downloading bodies {range:?}");

?
yeah that's actually better


Import List Entity Error

Dear LUIS Team,
I have exported the LUIS model as a json file.
Inside the List Entity, if a normalized value does not have any synonyms, it has the format of:
{
          "canonicalForm": "some list entity",
          "list": []
},

However, if I try to add an additional list entity with the same format in json file and import, I got the message of
Import version failed
10:16 AM
BadArgument: One or more synonyms are empty or whitespaces.
Would be glad to know how to deal with this import error. Thank you.

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

ID: 3103f3e3-bbbf-9083-f948-4116512b38a4
Version Independent ID: 578c9874-d637-b232-aa61-7f06c3ffa86a
Content: List entity type - LUIS - Azure Cognitive Services
Content Source: articles/cognitive-services/LUIS/reference-entity-list.md
Service: cognitive-services
Sub-service: language-understanding
GitHub Login: @diberry
Microsoft Alias: diberry

@irishun Thanks for the question. Could you please provide the .json that was used for import? Did the import of the format as mentioned in this example failed?

@irishun Could you please let us know if you got a chance to review the json used for import?

My app.json for a list entity for schema v7.0.0. is:
  "closedLists": [
    {
      "name": "FruitList",
      "subLists": [
        {
          "canonicalForm": "Apple",
          "list": [
            "red",
            "green"
          ]
        }
      ],
      "roles": []
    }
  ],

The app.json labeled utterance that uses this utterance is
    {
      "text": "i would like a red apple",
      "intent": "None",
      "entities": []
    }

@diberry  Thanks for sharing the json. @irishun We will now proceed to close this thread. If there are further questions regarding this matter, please tag @RohitMungi-MSFT in your reply.


Share uploaded image does not work

Uploading and sharing an image does only work partially:
The message is created in the channel. The linked title shows the picture if I click it.
However, the picture itself is not shown directly in the message as well as the private file is not listed as "shared file" in the slack web interface. Instead it is listed as private file and I can share it manually which works fine.
I'm using the following code:
_self.slack = Slacker()
...
  res = _self.slack.files.upload(filename,channels=_self.slack.channels.get_channel_id('#general'))
  resParsed = json.loads(str(res))
  url = resParsed["file"]["url_private"]
  attachments = [{"title": "Overview", "title_link": url, "text":"test", "image_url":url}]
  _self.slack.chat.post_message("#general", "Overview",as_user=True,  attachments=attachments)

Please help.

After endless tries my conclusion is that there must be a bug.
I've solved the problem by switching to https://github.com/slackapi/python-slackclient
Here the issue was solve within a minute, because I only need to upload the file
slack.api_call('files.upload', channels='#general', filename='pic.png', file=open(filename, 'rb'))
In the slack channel the new upload is mentioned automatically and it's content is unfurled.


Fix hyperlink to tf.Tensor guide.

cc: @jvishnuvardhan
Followup to #36775.

Fix hyperlink to tf.Tensor guide.
Add brief intro of eager and graph modes.

@googlebot I signed it!

Bump.  Could you please review?  Thanks.

@jraman Can you please check lamberta's comments and keep us posted? Thanks!

@lamberta, thank you for your review.  I have addressed your comments.
cc: @gbaned

Bump.  Could you merge please?  Thanks.
cc: @gbaned

Just checked on it. It's in-flight but this process can take while because of our internal CI (cl/299268631)

@lamberta, @gbaned
Any update?  Sorry to bother you, but it's almost four days since CI was last checked.  Thanks.


Setup mdx example site to Netlify

Depends on #122
Similar to #97

Closed by #127, the site can be found on gatsby-remark-oembed-mdx.netlify.com


feat: Support python contexts, add default in-memory connection

Context:
with glaredb.connect() as con:
    con.execute("select 1")

Adds sql and execute as top-level functions using an in memory db. Meaning you can now do this:
import glaredb

glaredb.sql("select 1")

@scsmithr is this good to go? looks like It needs a rebase.

I'll fix the rebase and take this over.

I'll fix the rebase and take this over (if that makes sense)

That sounds good to me. I think I stopped this because I wanted to the address the sql/execute thing first (which you merged).


Add Nicequest and Fooducate as easy

Adding Nicequest and Fooducate (both of them easy).

Thanks for your contribution!


migration symfony 5 and 6 PHP 8.1

Migrate php version for being able to be usable for symfony 6

I have problem with the coding standard of the CI, do i make a exemption for these error ?

Did you try your changes locally?
I just checked and it looks like SonataMediaBundle and FOSCKEditor bundle aren't compatible with Symfony 7 yet. As they are dependencies of this bundle, this bundle cannot be marked as compatible with Symfony 7 if SonataMediaBundle, FOSCKeditorBundle and probably other aren't upgraded before.
Also, it looks like FOSCKeditorBundle doesn't support CKEditor 5, and that CKEditor 4 has been EOLed: https://github.com/FriendsOfSymfony/FOSCKEditorBundle/issues/242
For this bundle to be useful, FOSCKeditorBundle must be made compatible with CKEditor 5.

Thanks @pauljosephkrogulec


Add ctf web tool

Burp Suite https://portswigger.net/burp/freedownload

@ziednamouchi I don't think you have the right commit in the diff for this PR. It is showing my own commit  from sometime back.

Closing as inactive


Add Phone Layout

https://github.com/hearsilent/KUAS-AP-Material/commit/79b30e2f2c2b0b28abd4dcdf255372a9ac9ad775


新增自定义Source URL会出现跨域问题

新增自定义Source URL会出现跨域问题
[Embedded Page] Access to XMLHttpRequest at 'http://api.nuget.xxx.com/v3/index.json' from origin 'vscode-webview://ac62e103-7ae7-4b26-99da-0acff509a042' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

add Access-Control-Allow-Origin' header or wait for https://github.com/pcislo/vscode-nuget-gallery/pull/26


Recursive delete of OData Service Collection.

Relevant issue : https://github.com/personium/personium-core/issues/69

Solved in v1.5.6.


proposal: need an interface or function to translate old resource objects

backgroup
At present, for ApisixRoute Ingress ... resource update, we use the TranslateUpstream method to translate old objects. This method requires parsing the latest services to build objects, resulting in data inconsistency.
Due to the wrong construction of upstream objects, upstream cannot be deleted, resulting in object redundancy.
proposal
Implement an interface or function for related resources

Get route object from cache.
Using route to construct Upstream and PluginConfig.
Compare and write APISIX.

dependencies

[ ] ApisixRoute #1177
[ ] Ingress
[ ] Gateway

[ ] HTTPRoute
[ ] ...

#1050 Or we can realize the function of regularly cleaning up redundant objects in upstream.

Using route to construct Upstream and PluginConfig.

why we need this one?

Using route to construct Upstream and PluginConfig.

why we need this one?

Because the route object contains upstream_ id and plugin_id. For delete event, we only need these fields


Nested Searching

When itereating an array from a search result and applying another search in a ITEM,  it retrive results form the entire document.
let cfes = xpath.select("//*[local-name(.)='CFE']", doc)
for (let cfe of cfes){
  let Encabezado = xpath.select("//*[local-name(.)='Encabezado']", cfe)
}

The only workaround I found untill know is adding this line of code inside the for loop
cfe = new dom().parseFromString(cfe.toString())...
let cfes = xpath.select("//*[local-name(.)='CFE']", doc)
for (let cfe of cfes){
  cfe = new dom().parseFromString(cfe.toString())
  let Encabezado = xpath.select("//*[local-name(.)='Encabezado']", cfe)
}

But surely is not the most efficient way of doing this.
Is there a cleaner way fo achieving the same?

It's searching the whole document because you're using an absolute path. Use a relative path instead:
let Encabezado = xpath.select(".//*[local-name(.)='Encabezado']", cfe)

@JLRishe Thank. that work perfectly!

This answer is correct, and I wanted to add a clarifying example because I was confused about the exact usage. Hopefully this will help someone with the same question.
XML
<?xml version="1.0" encoding="UTF-8"?>
<outer>
  <middle wanted="false">
    <inner>This is not the text I wanted</inner>
  </middle>

  <middle wanted="true">
    <inner>This is the text I want</inner>
  </middle>
</outer>

Javascript
var xmlString; //populate this with the XML above; for example you could use fs.readFile in Node.js
var domParser = new DOMParser();
var doc = domParser.parseFromString(xmlString, "application/xml");

var wantedMiddleNode = xpath.select("/outer/middle[@wanted='true']", doc)[0];
var wantedText = xpath.select("./inner/text()", wantedMiddleNode);

console.log("inner text = " + wantedText); //prints node text = This is the text I want

I was confused because even though wantedMiddleNode.toString() returns
<middle wanted="true">
  <inner>This is the node I want</inner>
</middle>

you have to query wantedMiddleNode without the top-level <middle> element, ./inner/text(), instead of ./middle/inner/text().
If you want your queries to be portable regardless of whether you're using an entire document or just a child element, you can start all your queries with ./.

@Aldaviva The ./ in your example doesn't actually add any benefit. It's necessary in ponyesteves' case because he's using // and // will traverse the whole document if there isn't something before it.
In your case inner/text() would suffice.

Ah okay. I reran my tests without the leading ./ and it still works. I must have changed something else at the same time I added the ./ and falsely attributed the fix to the wrong change.


Question | Is there any way to get the details of the new layer on layer change?

Hi,
First off great work with the plugin.
Plugin works perfect but I wonder if there is anyway to get the layer property of the layer that changed. In example
Lets say we have two layers one for satellite and one for classic street map. Satellite is loaded first and when I changed it to Street map, I need some kind of event trigger with parameters includes layer property of Street map layer config.
I am asking this because I am trying to use this plugin with an another plugin: Leaflet-MiniMap . So I need this event so that I can tell my minimap controller to switch street view as well when I changed the basemap from satellite to street.

Hi, how are you?
Ok, i will add this feature

Hi, this improvement was implemented on version 1.0.6


legendTemplate missing from 2.0?

Will you be bringing back support for legend templates? In 1.0 you could use legendTemplate to add all sorts of additional functionality, like highly interactive charts.
For example, we used legendTemplate to make the legend for product sales trends clickable so you could drill into different product lines and areas and the chart would automatically rebuild with new parameters.
Maybe we're missing something but it doesn't look like there is any support for legend templates in 2.0.
Thank you for your time.

@Jaded-Design the templates have been replaced by callback functions.
To change the html legend, in your config:
{
  generateLegend: function(chartInstance) {
    //return html legend string here
  }
}

Wow, not sure how I missed this... My apologies.
Thanks for the quick response.

i use generateLegend callback, but it never triggered. How you resolve the problem @Jaded-Design? can you share your code here? Thank you very much.

@codeice following is mime:
document.getElementById("barChart").onclick = function(evt){
//.getElementsAtEvent(evt): get the legend which you click
let activePoints = barChartObj.getElementsAtEvent(evt);
//.getElementAtEvent(evt): return the active element which you click
let activeElement = barChartObj.getElementAtEvent(evt);
console.log(activeElement);
console.log(activePoints);
activePoints.map(item => {
console.log(item._model.datasetLabel, item._model.label);
});
};

barChart, which is the id of canvas of chart.


validation: add checks for newly-added proofs params

Additional params added here. This section shows the checks that smart-contracts team did manually that need to be added to the Superchain Registry
Details on some of the new params (work with proofs team to fill in the gap):

Fault Game Genesis Output Root: will be the same for all chains deploying straight to permissioned, but not necessarily for existing chains that upgrade to permissionless fault proofs
Fault Game Genesis Block: Zero for all chains that use fault proofs (permissioned or permissionless) since genesis, but unsure what it should be for chains upgrading to fault proofs
Fault Game Absolute Prestate: for all new chains we expect this value, but it changes with new op-program releases (I am unsure how frequently those are)
Large Preimage Proposal Challenge Period: Must be the same for all chains, whether new or existing
Minimum Large Preimage Proposal Size, Bond Withdrawal Delay, Game Clock Extension, Max Game Clock Duration, Fault Game Split Depth, Fault Game Max Depth: Must be the same for all chains, whether new or existing

Fault Game Genesis Output Root for permissioned game only chains can be anything - makes sense to require it to a specific and obviously wrong value like 0xdead....  For permissionless games this should be verified as being the correct output root for the canonical block at Fault Game Genesis Block and that the block is finalized. When configuring the chain it should be set to a fairly recent finalized block but is otherwise arbitrary.
Fault Game Absolute Prestate - should verify that this matches the hash of a op-program release - may want to require it to match a governance approved op-program release for mainnet chains. We verify that the prestate build is reproducible so have a list of versions and their hashes in https://github.com/ethereum-optimism/optimism/blob/a2653a38946e697ef4f1a76b62d9d77acd8a8cad/.circleci/config.yml#L1079-L1106 - would be quite happy to start pulling that list from somewhere better and maybe it could be shared. We do want to include builds that aren't yet governance approved in the list we test though.  There's also a script to rebuild all released prestates: https://github.com/ethereum-optimism/optimism/blob/52d0e60c16498ad4efec8798e3fc1b36b13f46a2/op-program/scripts/build-prestates.sh

@mds1 what level of chain should all of these new param checks be run against? The options are:

universal (all chains)
standard chain candidates (not yet standard, but intend to be at some point)
standard chains

My thinking would be "standard chain candidates" (and stricter, so standard chains also), but would like to confirm with @ajsutton

Definitely for standard chains since the configurability.md part of specs is intended to be the definition of standard chains.
So I think it also makes sense to apply to standard chain candidates at least to flag something that's not yet standard. I assume that part of becoming actually standard means checking that no invalid withdrawals were ever allowed. Getting these config params wrong can lead to dispute games resolving incorrectly and invalid withdrawals if no-one steps in. The same can happen by just not running challenger or a malicious permissioned proposer/challenger though so I don't think we need to worry about bad historic configurations since we have to check for potential abuse anyway.
Universal chains seems incredibly broad so not really sure what threshold of checks would/should apply there. They may well have reasons to change a bunch of the params from the fixed value for standard configs, and if they're using permissioned game then the genesis output root and absolute prestate may not be set correctly so those checks probably don't mean much.
So yeah, standard chain candidates and stricter makes sense to me.

@mds1 @ajsutton
It sounds like we need to detect whether a chain is using permissioned vs permissionless fault proofs, and base some expected results on which flavor of fault proofs is used. What is the best way to tell [1] that a chain is using fault proofs and [2] which type of fault proof is used? Are there any smart contracts methods I can query that would give me that information directly? Or should I imply it from the existence of PermissionedDisputeGame and maybe some other contract addresses in the chain's config?

OptimismPortal.respectedGameType would tell you what's currently in use (0 is permissionless, 1 is permissioned). But it may be better to relax checks for chains that don't have an implementation for the permissionless game at all (DisputeGameFactory.gameImpls(0) is the 0 address).

@mds1 @ajsutton getting closer but have a few more questions:

OptimismPortal.respectedGameType would tell you what's currently in use (0 is permissionless, 1 is permissioned)

Will use this to determine permissionless vs permissioned. I can then use that info to pass the arg to this AnchorStateRegistryProxy.anchors(uint32) call.

Should we exclude all checks on the PermissionedDisputeGame contract for chains where the call to OptimismPortal.respectedGameType indicates the chains is using permissionless?

may be better to relax checks for chains that don't have an implementation for the permissionless game

Can you explain this a bit more? Which validation checks could be relaxed?

Fault Game Genesis Output Root for permissioned game only chains can be anything - makes sense to require it to a specific and obviously wrong value like 0xdead.... For permissionless games this should be verified as being the correct output root for the canonical block at Fault Game Genesis Block and that the block is finalized. When configuring the chain it should be set to a fairly recent finalized block but is otherwise arbitrary.

In the context of the validation checks, is there a distinction between "permissioned game only" chains and "permissioned with option to turn on permissionless"? Or are there only two categories: [1] permissioned and [2] permissionless?
For op-mainnet I called AnchorStateRegistry.anchors(1), since this chain is on permissioned proofs based on the OptimismPortal.respectedGameType return value. However, instead of getting a root hash of 0xdead000000000000000000000000000000000000000000000000000000000000 as expected based on the notion doc, I got 0xa4988434f3931ecf3169f182985899e9ee9d615c8e905af4c03c79df6d25562a. Any idea what is causing that discrepancy?
For permissionless Fault Game Genesis Output Root check: how do I determine if the output root is correct? That output root hash should match a block hash of a l2 block? Where do I find the l2 block number? I see the PermissionedDisputeGame.l2BlockNumber() function, but is that the right one to call for a permissionless chain?

I added a file here that keeps track of all the op-program prestate hashes that will allow the Fault Game Absolute Prestate to pass. This follows a pattern we have established for tracking standard config values in other checks. Would it be acceptable to add a step to the op-program release flow to update that file with new release version+hash?

Should we exclude all checks on the PermissionedDisputeGame contract for chains where the call to OptimismPortal.respectedGameType indicates the chains is using permissionless?

No, chains using permissionless may need to switch back to permissioned if there are issues, so we want to know that it is correctly configured and ready to go.

Can you explain this a bit more? Which validation checks could be relaxed?

Mostly you'd skip all the checks for permisisionless since it doesn't exist.  You don't need op-program to be a standard value (though it's recommended still to make upgrading to permissionless later easier). The anchor state for the permissioned game would be allowed to be either a correct finalized output root or something like 0xdead. If permissionless games are deployed, even if they're not active, we could require all games types to have a valid finalized output root and not allow 0xdead.

In the context of the validation checks, is there a distinction between "permissioned game only" chains and "permissioned with option to turn on permissionless"? Or are there only two categories: [1] permissioned and [2] permissionless?

You could boil it down to just two categories but they would be whether the permissionless game type is deployed or not. Which game is currently in use doesn't matter (the guardian can change that), which game types are available is meaningful (ProxyAdminOwner has to change that).  As mentioned above, you could make checks on the permissioned game a bit more strict if permissionless is deployed but you don't need to. It sounds like it's probably better to keep it simple and just enforce certain checks on the permissionless game (if present) and the slightly relaxed checks on the permissioned one (eg accept invalid anchor state root).

For op-mainnet I called AnchorStateRegistry.anchors(1), since this chain is on permissioned proofs based on the OptimismPortal.respectedGameType return value. However, instead of getting a root hash of 0xdead000000000000000000000000000000000000000000000000000000000000 as expected based on the notion doc, I got 0xa4988434f3931ecf3169f182985899e9ee9d615c8e905af4c03c79df6d25562a. Any idea what is causing that discrepancy?

I think this was answered in discord but for the record, the AnchorStateRegistry is updated when games of that type resolve as valid.  So for permissioned games we should allow it to start with something like 0xdead but as it updates it will become a valid safe output root which will almost certainly also be finalized unless L1 fails to finalise for at least 3.5 days. If an invalid proposal incorrectly resolves as valid the AnchorStateRegistry will be updated with that invalid output root and the Guardian will need to step in to fix it (as well as blacklist the game to prevent withdrawals etc), so during incidents you may see the check fail because of an invalid anchor state until it gets fixed.

For permissionless Fault Game Genesis Output Root check: how do I determine if the output root is correct? That output root hash should match a block hash of a l2 block? Where do I find the l2 block number? I see the PermissionedDisputeGame.l2BlockNumber() function, but is that the right one to call for a permissionless chain?

The AnchorStateRegistry should return both the output root and L2 block number it comes from. It returns a OutputRoot struct which is the output root hash and the l2 block number. So just AnchorStateRegistry.anchors(<gameType>) should give you the inputs.  Checking the output root is correct depends on having access to the RPC for an op-node instance which can be hard to find.
Both PermissionedDisputeGame and FaultDisputeGame expose a l2BlockNumber() function which is the L2 block number the proposal is for but that may not be the one that's in the AnchorStateRegistry and it will only be set for actual games, not the implementation contract you get back from DisputeGameFactory.gameImpls.
In general, I wonder if superchain-registry is the right place to be trying to check the anchor state. It makes sense to me for it to check the initial anchor state (the Fault Game Genesis Output Root) specified in the deploy config, but continually monitoring the anchor states as they update feels more like a security response kind of monitoring. The superchain-registry doesn't try to monitor that all withdrawals are valid for example. We do want that monitoring, this just doesn't seem like the right place.


plane-outline icon is not ouline

as you closed my first issue and asked me to report based your issue template, I have to say I'm using Ionicons in my react native app and I realized that plane-outline icon is not actually outline.
Current behavior:
plane-outline Icon is not outline
Expected behavior:
plane-outline should be outline

@nimamyscreen Thanks for the issue! We ask that issues be reported through our template so that we have enough information to understand and reproduce the issue. :) Where are you seeing the plane not using outline? Is it only in the browser at http://ionicframework.com/docs/v2/ionicons/? Here is what I'm seeing on that page:

If you're seeing the incorrect icon in your React Native app - could you give us some more information on how you're including and using Ionicons? Thanks in advance!

this is so weird, I'm using exactly the same link in my browsers (Chrome,Firefox) but the Icon is not outline.

Hey @nimamyscreen , on my macbook pro with both the latest stable version of chrome, the latest stable version of firefox and the latest stable version of safari I see the correct icons. Are you on a windows machine?

Hello all! As it seems it has been a while since there was any activity on this issue i will be closing it for now. Feel free to comment if you are still running into this issue. Thanks for using Ionic!

I am also experiencing this issue on iOS device.
You can reproduce and see that "plane-outline" is not outline on either Xcode simulator or real device.

Thanks @oleh-kolinko! I was able to reproduce it from an iPhone in Safari. I don't believe this is something that will be fixed, since we have redesigned ionicons and the latest version doesn't include outline icons: http://ionicons.com/
I will confirm this with @bensperry.


AttributeError: module 'pytorch_metric_learning.losses' has no attribute 'MINDSSC'

Thank you for your code.
Please me ask about which "pytorch_metric_learning.losses" version did you use or how do we solution this problem? Because I faced the error when type " python  l2r_2021_convexAdam_task2_docker.py "

I also used:

pip install pytorch_metric_learning==1.0.0 or 0.9.99 or 0.9.98 but all had the above error.

Thank you.

You need to include our MIND-Loss function from our voxelmorph fork https://github.com/multimodallearning/voxelmorph/blob/389274436263ef0cd9a32a566f12bf7f048f6843/pytorch/losses.py#L106
in the next version we'll directly include this code

Thank you @mattiaspaul, I fixed that error.
Allows me ask something more. I am wondering, has the training processing in your code? Normolly in my limit knowlege, the first we must to do training step to have the checkpoint and then do the test step.
My status:
With your code, I typed "python l2r_2021_convexAdam_task2_docker.py" and we have extremely the results, as following:

When do we the train dataset?

Thank you very much @mattiaspaul .

@tphankr hey，I am a beginner and I want to reproduce this code, but after reading the paper, I don't know what to do. Can you leave an email address to help me

@tphankr I also encountered the same problem, have you solved this problem?

We have updated our codebase: You can find the MIND computation here:
https://github.com/multimodallearning/convexAdam/blob/980a450758e8621a41b07c4d259910dae3f58118/src/convexAdam/convex_adam_MIND.py#L22C5-L22C6
Please do not hesitate to open another issue if needed!


Google services available?

I have built ungoogled-chromium 80.0.3987.149 from the AUR, and I see that (at least) 3 google services can be enabled (with the GUI), although disabled by default. What happened? In previous releases this didn't occur, and google ~botnet~ services couldn't be enabled at all.

3 google services can be enabled

Which exactly?

Also, what specifically in the GUI are you referring to? chrome://settings?

Also, what specifically in the GUI are you referring to? chrome://settings?

Yes.

Which exactly?

Plus, the "Allow Chromium sign-in" option can be enabled.

I don't remember off the top of my head if we removed them at some point, but doing so would only benefit us cosmetically. All the underlying code is either patched out or broken by domain substitution.
Do you find that these services contact Google when you enable them?

Do you find that these services contact Google when you enable them?

Enabling google services didn't make a difference here, so no, they don't contact Google. I have tested it with mitmproxy.
It's just weird to see these options being available.

Actually this is a duplicate of #369. Closing as such.


Python3 support

Builds off of the virtualenv PR to add support for python3. Runs tests via tox against python2.7 and python3.4.
Drops support for python2.6, although this could be added back pretty easily. Also removed the Makefile from the virtualenv PR, as tox handles the initialization/testing process. To run tests, simply run tox.

This is not complete because it will fail with a bytes/str error when you try to make a post/get. If you can add the appropriate handling for that so it works in both Python 2.6+ and Python 3.3+ then it's good to go!

For clarification, the issue is that actual API requests will have unicode conversion errors in python3.x
Are those not covered in the unit tests? I'm guessing because they need sailthru credentials or something?

Yes, there will be byte/str conversion errors in Python 3 because of the requests library and how we format the data. The unit tests only cover functional things and avoids connecting to the requests library by mocking.

Fixed & tested send and get_user against py2.7 and 3.4. Anything else that should be tested?

I'll have to test your changes but your changes look good; You may want to test sending a CSV file via the Job update call, to make sure the multipart request works in Py2 and Py3.

We've never used that feature at our company, so I'd be hesitant to test it out given I don't know how it's expected to work. Could you guys test it?

I get the following error when I run to:
FAIL: test_signature_string (test_sailthru_client.TestSailthruClientFunctions)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/isaulvargas/sailthru-python-client/test/test_sailthru_client.py", line 42, in test_signature_string
    self.assertEqual(c.get_signature_string(_dict, secret), expected)
AssertionError: b'123456LinuxMacNoneSolaris' != '123456LinuxMacNoneSolaris'

----------------------------------------------------------------------
Ran 8 tests in 0.307s

FAILED (failures=1)
ERROR: InvocationError: '/Users/isaulvargas/sailthru-python-client/.tox/py34/bin/nosetests -v'

How about I kill this PR? The back-and-forth indicates that this isn't stable enough to be accepted into mainline. We'll maintain our python3-compatible fork and use it in production. If issues arise, we'll fix them there, and hopefully I can open a new PR in the future that necessitates less critique.

I will merge this pull request once I finish testing it and I am satisfied it works with Python 2.7 and Python 3.4. I think the failing test is a minor issue that can be fixed later.

I was able to successfully import a list, so this is good enough. I will merge this soonish.

Merging today. I will have to make a few changes unrelated to your ticket before I upload to PyPI.

Cool, thanks @Dude-X !


Unusual paragraph and span in a figcaption

Issue Summary
In the case of adding a figcaption to a Code card, a paragraph with the attribute dir='ltr' is introduced. This unusual paragraph, occurring only in this case, disrupts the theme formatting.

Additionally, a  element with the style white-space: pre-wrap; is included — this also appears to be undesirable. The span element is added to every figcaption, not just those within the code element.

Steps to Reproduce
Add a Code card with a figcaption, then check the code.
Ghost Version
5.75.1
Node.js Version
18.12.1
How did you install Ghost?
localhost
Database type
SQLite3
Browser & OS version
All
Relevant log / error output
No response
Code of Conduct

[X] I agree to be friendly and polite to people in this repository

HI @fueko
I would like to fix this issue. Can you please assign it to me?

I saw the new  element is saved into database as well, not just auto-generated by code:
 This is the caption
Screenshot:

At first I thought this was a new standard for saving caption. Glad it is a bug... :D

HI @fueko I would like to fix this issue. Can you please assign it to me?

Hey there,
Have you worked on it? It seems the issue is still persisting.

@daniellockyer Hello, I would like to upvote this bug. Or at least, confirm it's a bug or intented caption format?

span's are expected and not a bug, themes should cope both with and without span being present.
p is little unexpected but it should be considered possible within themes because content is free-form - especially when using markdown or html cards - so those eventualities should be taken into account when styling.
@fueko do you see p embedded in fig captions frequently? If so are you able to determine if that happens in any specific cases?

Hi @kevinansfield, I must admit that I don't follow this closely, but checking quickly, I see the
 attribute in gallery cards, video, and elements using the helper<EMAIL_ADDRESS>


Microsoft.ApplicationInsights.WorkerService does not log traces even after specifying override in config

Dear team,
I have a .net core Worker service for which I had configured App Insights using the below snippet in my ConfigureServices method:
 services.AddLogging(builder =>
 {
     builder.AddConsole();
     builder.AddDebug();
     builder.AddApplicationInsightsWebJobs(options =>
     {
         options.ConnectionString = configuration.GetConnectionString("ApplicationInsights");
         options.EnableLiveMetrics = true;
     });
 });

Using this (the above snippet uses the Microsoft.Azure.WebJobs.Logging.ApplicationInsights package which I know is related to another repo, but bear with me)  I was only able to see traces and exceptions in my logs. I wanted to setup telemetry to track my dependency calls as well. So after reading up, I tried to use and configure the ApplicationInsights.WorkerService library instead of the above package. So my new setup looked like below:
   var aiOptions = new ApplicationInsightsServiceOptions
   {
       EnableAdaptiveSampling = false,
       ConnectionString = configuration.GetConnectionString("ApplicationInsights")
   };

   services.AddApplicationInsightsTelemetryWorkerService(aiOptions);

My dependency telemetry started showing up, but now my traces disappeared.
Following your documentation here, I provided a specific override for ApplicationInsights in the configuration(with the "Information" level enabled) , but this did not work either. I still only saw the dependencies in my logs.
The only way I got both my traces and dependencies working is to use both the packages and configure them very specifically in the following order:
 services.AddApplicationInsightsTelemetryWorkerService(aiOptions); //This has to go first
services.AddLogging(builder =>
 {
     builder.AddConsole();
     builder.AddDebug();
     builder.AddApplicationInsightsWebJobs(options =>
     {
         options.ConnectionString = configuration.GetConnectionString("ApplicationInsights");
         options.EnableLiveMetrics = true;
     });
 });

Can you please check why the logging of traces does not work? I would expect that only the WorkerService SDK is required since it has all the providers required according to the documentation.
Further information on my setup:
.Net Core 8.0
Project SDK used -> Microsoft.NET.Sdk

https://github.com/microsoft/ApplicationInsights-dotnet/tree/develop/examples/WorkerService There is an example shared in this repo. Is that no working? i.e is that not capturing Logs?

@cijothomas In the example you shared, do you mean the use of some CustomTelemetryProcessor? Other than that, the example looks pretty similar to what I had done above.
One question, does the fact that we are not using the Worker SDK but only the .Net SDK make a difference? That's something I did not try.

In the example you shared, do you mean the use of some CustomTelemetryProcessor?

No. telemetry processor is just shown for example, and has no impact to telemetry pipeline.
Have you confirmed if the shared example is working or not?

I faced the same issue when I was trying to follow the console app instructions. This is what saved me: https://stackoverflow.com/questions/77565541/logs-not-appearing-in-application-insights-for-azure-functions-v4-with-net-8/77948360


Seperate block height restrictions and feature activation

This PR moves the helpers to get the lastest block height etc. into utilsbitcoin, and the block height restrictions, as well as the allowed input and output types into rules.
The enum BLOCKHEIGHTRESTRICTIONS was flattened to plain numbers.
From here on, I see a few options:

move the block restrictions into a namespace, which would allow something like mastercore::consensus::P2SH_BLOCK

provide public getters, such as IsEnabled_P2SH()

introduce seperate restrictions for each network (i.e. main, test, regtest)

refine and introduce a structure like Params() (see: chainparams.h, chainparams.cpp, chainparamsbase.cpp)

To go on with #104, it could basically go like this: old, already enabled features remain to have hardcoded const int block height restrictions, while the not-yet-enabled features are changed to int. There could be a function like EnableFeature_XXX(int block), which would update these values.

Sorry for not responding to this one sooner - I agree with your sentiments here bud and have cleaned up some local ideas to fit in with your PR here.  It's a WIP but let me know what you think of https://github.com/zathras-crypto/omnicore/commit/fec622ae843f69b6a80a29e3539464d1f257f692.
Thanks as always mate!

On the first glimpse it looks very clean and good. I'll give it a in-depth look and more thoughts later.
Can you please create a PR for it, so we have a place of discussion? :)

Sure dude, #129

I've looked over #129 and it looks extremely good.

Given that #129 builds on top of this PR, should I close or merge this?

I consider building on top of this PR as implicit ACK, thus the merge. :)

Whoops, looks like I introduced an issue upstream:
diff --git a/src/qt/metadexdialog.cpp b/src/qt/metadexdialog.cpp
index 6838871..9ebf2c1 100755
--- a/src/qt/metadexdialog.cpp
+++ b/src/qt/metadexdialog.cpp
@@ -17,6 +17,7 @@
 #include "omnicore/parse_string.h"
 #include "omnicore/pending.h"
 #include "omnicore/sp.h"
+#include "omnicore/rules.h"
 #include "omnicore/tally.h"
 #include "omnicore/utilsbitcoin.h"

I'll wait, until my local build finished, then I'm going to push the fix.


feat(localization): add nerf_based_localizer

Description
Add the NeRF Based Localizer package.
https://github.com/autowarefoundation/autoware.universe/assets/28504069/3869dbd0-60bc-497e-ab79-9e6f684391f8
Tests performed
It has been confirmed that logging_simulator works with the trained data and rosbag shown in README.md.
A quantitative comparison in rosbag for ar_tag_based_localizer is shown in the table below.

Method
Mean Error[m]
Notes

NeRF Based Localizer
0.123
Initial pose is provided by GT

AR Tag Based Localizer
0.624
Initial pose is provided by GT

YabLoc
0.535
-

NDT
0.055
-

Effects on system behavior
It does not affect autoware unless you download libtorch properly.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

This pull request will create a new dependency on libtorch, so it is difficult to know how to handle that. I think it could be rejected and closed. It is important that once it went out as a pull request and was discussed.
I have not yet fixed spell check, linter, etc., but if there is a chance that the merge will be possible, I will do.

@SakodaShintaro I think that's a reasonable speculation. IMHO it seems OK since CMake won't be built as long as libtorch is not found, but how about creating a Discussion or ask perception team internally?

In my environment, the build failed due to atomicAdd().
I added the following code into hash_3d_anchored.cu based on this link, and it successfully built.
__device__ float atomicAdd(__half * a, float b)
{
  bool uplo =
    ((unsigned long long)a) &
    2;  // check if the atomic is for the upper or lower 16-bit quantity in the aligned 32-bit item
  unsigned * addr = reinterpret_cast<unsigned *>(
    ((unsigned long long)a) & 0xFFFFFFFFFFFFFFFCULL);  // get the 32-bit aligned address
  unsigned old = *addr;
  unsigned val;
  do {
    val = old;
    float newval = __half2float(__ushort_as_half(
                     uplo ? ((unsigned short)(val >> 16)) : ((unsigned short)(val)))) +
                   b;
    unsigned short newval_s = __half_as_ushort(__float2half(newval));
    unsigned newval_u = val & (uplo ? (0x0FFFFU) : (0xFFFF0000U));
    newval_u |= uplo ? (((unsigned)newval_s) << 16) : (newval_s);
    old = atomicCAS(addr, old, newval_u);
  } while (old != val);
  return __half2float(__ushort_as_half(uplo ? (old >> 16) : (old)));
}

In my GPU, I could not run it at 1x speed with the default settings, but I was able to perform localization! :clap:
(This video shows a demo of rosbag played at 0.3x speed, converted to 12x speed.)
https://github.com/autowarefoundation/autoware.universe/assets/24854875/23b65489-c222-488c-bdd5-095754a31a46

The problem about atomicAdd may be described in the following page.

The 32-bit __half2 floating-point version of atomicAdd() is only supported by devices of compute capability 6.x and higher.

https://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html#atomicadd
It may be possible to speed up the process by changing the following constant from 1024 to 512, but I will try this later as I suspect there are other variables that will need to be changed if this is changed.
https://github.com/autowarefoundation/autoware.universe/blob/2d995d03187c56d88de8fba879c986303c7da4d5/localization/nerf_based_localizer/src/nerf/points_sampler.hpp#L28

The problem about atomicAdd may be described in the following page.

The 32-bit __half2 floating-point version of atomicAdd() is only supported by devices of compute capability 6.x and higher.
https://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html#atomicadd

My GPU is a GeForce GTX 1080ti with compute capability 6.1, and it seems like atomicAdd() for __half is not available.
Now I understand. Thanks for sharing the information. :+1:

It may be possible to speed up the process by changing the following constant from 1024 to 512, but I will try this later as I suspect there are other variables that will need to be changed if this is changed.

This is the result in my environment.

MAX_SAMPLE_PER_RAY
Localize Time

1024
200ms

512
140ms

256
100ms

Exposing MAX_SAMPLE_PER_RAY as a YAML file would be convenient for users. :pray:

Fixed so that sample_num_per_ray can be set from yaml file.

sample_num_per_ray
Average Process Time [ms]
Average Score (the higher the better)

1024(default)
96.9
152.4

512
59.8
147.2

256
36.2
131.8

Accuracy is somewhat reduced, but speed is improved.

Wonderful work!. Is there some reference paper about this nerf-based localization methods?

@Gatsby23
Thank you for your interest!
NeRF Part
The code added in this pull request is primarily based on the implementation of F2-NeRF. You can find more information here: https://totoro97.github.io/projects/f2-nerf/
F2-NeRF can be summarized as Instant-NGP enhanced with spatial partitioning via Octree and Warping.
However, this pull request omits the spatial partitioning and Warping using Octree, a key innovation of F2-NeRF, due to the following two drawbacks:

The initialization process requires about a minute, leading to a time-consuming startup each time.
It was challenging to backpropagate gradients to the Camera pose for pose optimization.
Therefore, the process implemented here is almost equivalent to that of Instant-NGP.

NeRF-based Localization Part
This pull request supports two methods of using NeRF for self-localization:

Scattering self-pose in a Monte Carlo fashion and scoring them by comparing the image reconstructed by NeRF with the actual image.

Ref. Loc-NeRF

Calculating self-pose through differentiation when reconstructing with NeRF.

Ref. iNeRF

Neither is a complete reproduction of the paper, but rather a reference of ideas.
I hope this information will help you.

@Gatsby23 Thank you for your interest!
NeRF Part
The code added in this pull request is primarily based on the implementation of F2-NeRF. You can find more information here: https://totoro97.github.io/projects/f2-nerf/
F2-NeRF can be summarized as Instant-NGP enhanced with spatial partitioning via Octree and Warping.
However, this pull request omits the spatial partitioning and Warping using Octree, a key innovation of F2-NeRF, due to the following two drawbacks:

The initialization process requires about a minute, leading to a time-consuming startup each time.
It was challenging to backpropagate gradients to the Camera pose for pose optimization.
Therefore, the process implemented here is almost equivalent to that of Instant-NGP.

NeRF-based Localization Part
This pull request supports two methods of using NeRF for self-localization:

Scattering self-pose in a Monte Carlo fashion and scoring them by comparing the image reconstructed by NeRF with the actual image.

Ref. Loc-NeRF

Calculating self-pose through differentiation when reconstructing with NeRF.

Ref. iNeRF

Neither is a complete reproduction of the paper, but rather a reference of ideas.
I hope this information will help you.

That's really impressive. Beacuase two of the reference paper is worked at a small space. It's really interesting it can worked on a large environment.

Thank you very much. However, it can be said that this method is still in the validation stage, as it has not been fully evaluated to see if it can cover such a large area as a huge city.
NeRF and Gaussian Splatting have developed remarkably in recent years, and there is a possibility that their performance will be enhanced by incorporating methods such as neuralsim and DrivingGaussian.
I look forward to further developments in this area.

In recent years, techniques such as 3D Gaussian Splatting have emerged, and we believe it would be better to start implementing it with offline tools rather than starting with the Autoware runtime, so we are closing this pull request.


schedule Remove wait schedule time in pipeline query engine

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall

run buildall

https://github.com/apache/doris/pull/24247


issues about the code

Hi! Thanks for releasing the code. I re-implement the code and found that the result is not as good as what the paper has demonstrated. There is a gap between two results especially the car. I follows the step Readme has pointed out. Can you release the data used in the experiment? (data in baidu yun are the not sliced ones, I think they are not the data used in the experiment)

Hi! Thanks for releasing the code. I re-implement the code and found that the result is not as good as what the paper has demonstrated. There is a gap between two results especially the car. I follows the step Readme has pointed out. Can you release the data used in the experiment? (data in baidu yun are the not sliced ones, I think they are not the data used in the experiment)

Sorry for the late reply. I have just seen the message. I don't have the plan to merge code from openmmlab. I noticed that openmmlab have supported the two datasets(vai and potsdam). In fact，data preprocess is very important to get higher precision.  I recommend you to use this repo instead of implement model in openmmlab. There are much difference in data preprocess.
I only upload trained models to baiduyun. The date used in experiment all have been uploaded to ai studio

If you want to merge this pull，code conflicts should be taken into consideration carefully.

How to visualize and save test set data，When I run the visual command, I get the following error:

How to visualize and save test set data，When I run the visual command, I get the following error:

You can try to run pip install -e .. In your screeshot, you use original mmseg, which doesn't support four channel image.

How to visualize and save test set data，When I run the visual command, I get the following error:

You can try to run pip install -e .. In your screeshot, you use original mmseg, which doesn't support four channel image.

thanks ，I would try . I use  the command python tools\test.py configs\edft\segformer_mit_fuse-b0_256x256_80k_vai.py mit_fuse_b0.pth --eval mIoU --show  ，then an error about the number of channels was reported.

How to visualize and save test set data，When I run the visual command, I get the following error:

You can try to run pip install -e .. In your screeshot, you use original mmseg, which doesn't support four channel image.

I seemed to have run this command at first，but it still didn’t work.

How to visualize and save test set data，When I run the visual command, I get the following error:

You can try to run pip install -e .. In your screeshot, you use original mmseg, which doesn't support four channel image.

and now it raise this error

How to visualize and save test set data，When I run the visual command, I get the following error:

You can try to run pip install -e .. In your screeshot, you use original mmseg, which doesn't support four channel image.

How to enter the mmsegmengtation package in the conda environment

Or run the pip install -e . command directly in the created virtual environment?
do you know how to solve it,thanks.

Hello, I directly downloaded your code and dataset and ran it, I found that the error did not come to pretrain/mit_b0.pth, so I went to segformer and downloaded the mit_b0.pth, in the case that I did not change any parameters, I ran python tools\train.py configs\edft\segformer_mit_fuse_b0_256x256_80k_vai.py, on both 1050ti and 3090 are more than 71, is it a problem with the pre-trained model or something else, please guide.

hi,Can you give me your contact information? I want to communicate with you.

+v cx3245299704

How to visualize and save test set data，When I run the visual command, I get the following error:

You can try to run pip install -e .. In your screeshot, you use original mmseg, which doesn't support four channel image.

hi , I have clone the EDFT again ,but when I run the command to show ,it's still report this error ,can you tell me how to solve it !thanks!

How to visualize and save test set data，When I run the visual command, I get the following error:

You can try to run pip install -e .. In your screeshot, you use original mmseg, which doesn't support four channel image.

hi , I have clone the EDFT again ,but when I run the command to show ,it's still report this error ,can you tell me how to solve it !thanks!

Can you try out the branch "merge to master"? You should make sure mmseg official repo running well.


Add auth_level functionality

A simple addition to authentication functionality.
An optional min_auth_level to check if multi factor authentication is used

Thanks for the PR!  In principle this looks good; I'll test it and merge is if everything checks out.
Could you maybe tell me a bit about how you're using pam-weblogin?  We've developed the server/weblogin-daemon part mainly for testing (we have a separate implementation as part of a larger system in https://github.com/SURFscz/SBS), so I'm curious if you're using this in production.  If so, it might be worthwhile to add unittests etc for the weblogin-daemon etc.

We are looking into using it in production, but we don't do so right now. Right now we are experimenting on our test cluster and we are looking for a simple solution that can manage MFA and ssh key handling since our IDM offers MFA, but no ssh key handling.


Fix logic for when numberOfFailedTests is 0

No failed tests but the presence of numberOfFailedTests meant that the AND test failed when numberOfFailedTests was 0

Plz merge sir, thanks!


Is this code compatible with tensorflow 1.1

I would like to use this code but not sure if it works with tensorflow 1.1
Does it?
Thanks

@cristinasegalin
Yes, the latest code has supported the TF 1.2 version


Crop Image functionality

Ticket: #627
In this PR, I added image crop action
EDL
Button:
  label: Crop Image
  onTap:
    cropImage:
      id: cropImageId
      source: ${cameraId.files[0].path}
      options: { title: Crop your Image, format: jpg, quality: 80 }
      onComplete:
        executeCode:
          body: |
            //@code
            console.log("Image Cropped Successfully");

Image:
  id: displayCroppedImageId
  source: ${cropImageId.file.path}

@vinothvino42 this is a specialize behavior that doesn't make sense for anything else with Image. Instead of making the user wire things up. Simply have a CropableImage.

@vinothvino42 this is a specialize behavior that doesn't make sense for anything else with Image. Instead of making the user wire things up. Simply have a CropableImage.

@vusters @amin-nas
So let's say we're cropping an image with the CroppableImage widget.
Then we've to create a new separate ensemble page with croppable and some buttons. Is it a really good user experience?
Why do we need the CroppableImage widget? It's used only for cropping and not often too. So why not just have an cropImage action that will open the crop page by default with the image file path and get the file object once it's done.

cropable image has more properties so you don't want to pollute Image which is very simply. The ImageCropper can handle its own popup - you don't need another screen for it:
ImageCropper:
  source:
  overlayWidget:          # in case you want to overlay a button or some notification to tell the user the image is editable
  onCropped:                # call Action to send the updated image to the back end

@vusters I just updated it. Can you check my new changes
View:
  header:
    title: Image Cropper
  styles:
    scrollableView: true
  body:
    Column:
      styles:
        gap: 24
        padding: 24
      children:
        - ImageCropper:
            id: imageCropperId
            source: example.png
            cornerDotColor: red
            maskColor: blue
            cornerRadius: 25
            onStatusChanged:
              executeCode:
                body: |
                  //@code
                  console.log("Status Changed: Status");
                  if (event.data.cropStatus == "ready") {
                    console.log("Image Ready - ");
                    console.log(event.data.path);
                    displayCroppedImageId.source = event.data.path;
                  }
            onCropped:
              executeCode:
                body: |
                  //@code
                  console.log("Image Cropped Successfully");

        - Button:
            label: Crop Image
            onTap:
              executeCode:
                body: |
                  //@code
                  imageCropperId.crop();

        - Image:
            id: displayCroppedImageId
            source: ${event.data.path}

@vinothvino42 @amin-nas how about the below. There is no need for a separate widget. The ImageCropper on its own is sufficient (using cropOnTap=true). However there will be case when you want to trigger it manually (e.g. wrap the ImageCropper and overlay the Button in a Stack).
- ImageCropper:
    id: myCropper
    source: ...
    styles: ...
    options: ...                      # all the crop options go here
    cropOnTap: true|false    # default TRUE to initiate the crop on tap, FALSE to trigger it manually
    onCropped:                    # initiate an action, e.g. server call to update the cropped image

- Button:
     label: Crop Image
     onTap: |
       myCropper.crop();

@vusters Can you check this EDL?
View:
  header:
    title: Image Cropper
  styles:
    scrollableView: true
  body:
    Column:
      styles:
        gap: 24
        padding: 24
      children:
        - ImageCropper:
            id: imageCropperId
           source: example.png
            styles:
              {
                cornerDotColor: green,
                maskColor: blue,
                cornerRadius: 25,
                height: 120,
                width: 100,
                borderWidth: 1,
                fit: cover,
              }
            onCropTap: true
            onCropped:
              executeCode:
                body: |
                  //@code
                  console.log("Image Cropped Successfully");

        - Button:
            label: Crop Image
            onTap:
              executeCode:
                body: |
                  //@code
                  imageCropperId.crop();

So after cropping the image, I need to set the cropped image to the ImageCropper itself? No need to expose a file path like ensemble.data.file to the user?

@vusters Can you check this EDL? I updated it.
View:
  header:
    title: Image Cropper
  styles:
    scrollableView: true
  body:
    Column:
      styles:
        gap: 24
        padding: 24
      children:
        - ImageCropper:
            id: imageCropperId
           source: example.png
            styles:
              {
                cornerDotColor: green,
                maskColor: blue,
                cornerRadius: 25,
                height: 120,
                width: 100,
                borderWidth: 1,
                fit: cover,
              }
            onCropTap: true
            onCropped:
              executeCode:
                body: |
                  //@code
                  console.log("Image Cropped Successfully");

        - Button:
            label: Crop Image
            onTap:
              executeCode:
                body: |
                  //@code
                  imageCropperId.crop();

So after cropping the image, I need to set the cropped image to the ImageCropper itself? No need to expose a file path like ensemble.data.file to the user?
Yes, the ImageCropper's source will change to the cropped image. However on the action onCropped, the user may need to use File upload to upload the newly cropped image. In that case there has to be a way for the user to access the file. See how FileUpload is used to make it consistent there

Make sure you use cropOnTap name or something that makes sense. We are saying we will initiate the cropping when the user tap on the widget. What you had there "onCropTap" does not make sense.

@vinothvino42 this was approved last week. Please merge and close.


Try and rewrite your userJSON method using a completion handler.

It works the way you have it, but I think it would be helpful to create a new completion handler and rewrite the method. Look at the tweetsFrom method for an example.

I will think of another way to achieve that. Thanks!


Substrate TransactionTag usage and usecae

Need a solution to resolve the coordination of extrinsics relayed from different relayers.

Replaced by https://github.com/darwinia-network/bridger/issues/239


feat: update boost deps

update boost deps to fix build error due to empty glob headers

@mvukov @hofbi Could you review this PR?


remove left side-bearing adjustment for \not, fixes #44

I'm going to start a fresh PR for this.

@edemaine this is ready for review again.

@edemaine thanks for the review.


error: '_Set_ptr_rep_and_enable_shared' is a private member of 'std::shared_ptr'

V8Update fails at the "Building V8" step. Here's the log file I found: build-Win32-Release.log
Please advise.
Windows SDK version as seen in "C:\Program Files (x86)\Windows Kits\10\SDKManifest.xml": 10.0.26100.0
Visual Studio version as reported by Visual Studio Installer: 17.12.2

Hi @AnsisMalins,
We tested V8Update in ClearScript 7.4.5 with those exact Visual Studio and Windows SDK versions and did not encounter any issues.
A couple of possibilities:

Are you making any modifications to V8 or ClearScript prior to building?
Are you invoking V8Update in a Visual Studio Developer Command Prompt?
Do you have the "Desktop development with C++" Visual Studio workload installed?

Thanks!

Ah-ha! I was trying to build version 7.4.2. It is not great that older versions become unbuildable so quickly, but okay, 7.4.5 builds fine, I'll update to it.


Add back matter switch fingerprints

Generic fingerprints for the OnOff Switch, Dimmer Switch, and Color Dimmer Switch device types were removed because they require bindings to work correctly, and we do not currently support bindings (removed here: https://github.com/SmartThingsCommunity/SmartThingsEdgeDrivers/pull/1003). These generic fingerprints were removed in favor of having these devices join as matter-thing until binding support is added. However, the Matter Test app does currently have support for OnOff Switch, Dimmer Switch, and Color Dimmer Switch devices, but with the removal of these generic fingerprints these devices just show up as matter-thing. We want to add back these fingerprints so that these test app devices show up correctly in the SmartThings app.
https://smartthings.atlassian.net/browse/BUG2-624

@tpmanley what are your thoughts on adding these fingerprints back for the sake of testing with the Matter Test app?


Mail::Address parser breaks on domains which begin with a comment

For user input formatted like Mail::Address.new("someone@(comment)net") or Mail::Address.new("someone@(comment).net"), Mail::Address will emit an ArgumentError (bad value for range):
> Mail::Address.new("someone@(comment)net")
Traceback (most recent call last):
        7: from /Users/ticky/.rbenv/versions/2.5.0/bin/irb:11:in `<main>'
        6: from (irb):16
        5: from (irb):16:in `new'
        4: from /Users/ticky/.rbenv/gems/2.5.0/gems/mail-2.7.0/lib/mail/elements/address.rb:30:in `initialize'
        3: from /Users/ticky/.rbenv/gems/2.5.0/gems/mail-2.7.0/lib/mail/elements/address.rb:192:in `parse'
        2: from /Users/ticky/.rbenv/gems/2.5.0/gems/mail-2.7.0/lib/mail/parsers/address_lists_parser.rb:32930:in `parse'
        1: from /Users/ticky/.rbenv/gems/2.5.0/gems/mail-2.7.0/lib/mail/parser_tools.rb:9:in `chars'
ArgumentError (bad value for range)

This appears to be because it tries to find the string indexes of the domain part, and fails to do so. This should probably emit a more useful Mail-specific error.
Tested on Ruby 2.5.0 with mail 2.7.0

This appears to work properly with Ruby 2.7.


Add classes

Hi Code Reviewer👋
In this PR:
-⭐Set-up Rubocop
-⭐Set-up RSpec GitHub Action
-⭐Following GitFlow.
-⭐Create class Person.
-⭐Create class Student.
-⭐Create class Teacher.
-⭐Each class is saved in a separate file.

Hey @skyv26, Thanks a lot 💯 for your efforts in reviewing my code, I really appreciate it 😃 .


Transparency does not bake correctly

When baking with transparency, areas that should be entirely opaque are baked with a very slight amount of transparency, ruining all transparency blend modes other than cutout, as the character now becomes slightly transparent.
Example, also happens if transparency is baked as a separate texture:

I've just pushed a potential fix for this, could you give it a shot? (development branch)

I've just pushed a potential fix for this, could you give it a shot? (development branch)

Seems to work great, both separate texture and diffuse alpha transparency are fully working as expected now!

Excellent!


[WebGL] Create a convenient subclass of WebGLNode

WebGLNode is fully general, allowing the developer to supply custom fragment + vertex shaders.  It therefore takes a lot of webgl boilerplate just to do something simple.  Let's create a subclass of WebGLNode that is optimized for showing a bunch of images.
A custom WebGLNode may still be required for neuron since the simulation has zoom & clipping.

Would that be better served by scenery images and the WebGL renderer?

Scenery nodes incur an amount of overhead that can be avoided when using CanvasNode or WebGLNode for noninteractive objects.  If we can minimize the overhead or if it is already low enough, then I think scenery nodes + webgl renderer is best.  Otherwise, we may need to resort to CanvasNode + WebGLNode.

Now that Scenery supports WebGL images out-of-the-box and you have had time to use WebGLNode, can you recommend whether any work here is needed?

Let's close this issue but keep in mind if we are duplicating code in WebGLNode subclasses in the future, it may be an opportunity to factor out.


Introducing inconsistency when adding special tokens to a ModularTokenizer

Describe the bug
When we add special tokens to a ModularTokenizer, we first discover which of the new tokens are already part of the ModularTokenizer. To this end we consider the special tokens of the first subtokenizer alone, assuming all subtokenizers are consistent.
This, however, is not necessarily the case. For example, consider a second multitokenizer (Z) that was created from the first one (Y) by adding another subtokenizer (A). The first multitokenizer (Y) then was updated with additional special tokens, then all its subtokenizers were updated, but subtokenizer A was not (since it's only part of Z and not of Y). Next time multitokenizer Z is loaded, it will no longer be consistent - its subtokenizer A will be missing special tokens.
Moreover, if we try to add the missing tokens to Z, we'll fail because they're found in its first subtokenizer.
Possible solutions:
A. Test a ModularTokenizer for consistency each time it's loaded.
- If it is not consistent, add a consolidation function that will identify missing tokens (and their IDs) from each subtokenizer and add them, if possible (throwing an exception if not). Alternatively, the consolidation part may be optional, and we can just throw an exception that the ModularTokenizer is inconsistent and must be consolidated.
B. Test ModularTokenizer for consistency each time before it is changed (e.g. by add_special_tokens), and consilidate it if needed/possible
Fuse-Drug version
Fuse-Drug version/tag/commit used.
Python version
Exact Python version used. E.g. 3.8.13
To reproduce
Steps to reproduce the behavior.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Make sure not to include any sensitive information.
Additional context
Add any other context about the problem here.

It's only an issue with the extended modulartokenizer

after huddle:  extend https://github.com/BiomedSciAI/fuse-drug/blob/542778c8bc12d56125ab05d9024842e7d028da24/fusedrug/data/tokenizer/modulartokenizer/modular_tokenizer.py#L546 to work between sub-tokenizers of two modular tokenizers, and add the test to the Jenkins run.

The problem is not that acute, since the two tokenizers we use - modular_AA_SMILES_single_path and bmfm_extended_modular_tokenizer sit in different directories.
Initial manual solution would be to run special token addition code on both tokenizers each time, and to add a Jenkins test that compares them during commit.

Initial manual solution would be to run special token addition code on both tokenizers each time, and to add a Jenkins test that compares them during commit.

Maybe a better solution would be to add an "add special tokens to all tokenizers" script, so users will no need to follow the more complicated path of running the add-special-tokens twice or thrice.


Ensure Sandbox resources are always deleted from Azure after Sandbox is deleted from Sepes

Kristoffer has seen that sometimes azure resources are not deleted properly. need tests/monitoring to ensure it happens
Visit sepes (any env)
Select or Create a Study
Select or Create a Sandbox
Optional: Wait for sandbox creation to complete (unsure if this is relevant for reproducing)
Delete the Sandbox
Sandbox is deleted from Sepes and one is redirected to the Study page
Vist Azure portal after a while (10 mins) and notice that relevant resource group is not deleted
When visiting Activity Log for the resource group, one might find a "Delete resource group" there, but it's not carried through
Theories:
I suspect this might might only happen when one is deleting a Sandbox while it's under construction, so since Sepes is setting up a Azure resource at the time, the delete operation is blocked.
Especially if the Sandbox is deleted while Sepes  is creating a Bastion, which is a long running task that might collide with the delete operation
Actions to take regardless
We should add additional fields to SandboxResources:
We currently have "Deleted and DeletedBy", we should add "Marked for deletion" and "MarkedForDeletionBy"
We can also just use the operations-table for this: A  Resource is marked for deletion if is a unfinished "Delete" operation, and "Really deleted" when this operation is completed
We need a way for Sepes to ensure resource is actually deleted, and that Sepes keeps tryng further before giving up. It should also notify some admins if deletion failed
Questions:
When a Sandbox is deleted, maybe it can still be visible until it has been fully deleted (All Azure resources deleted) to those wo know the Id. So the user is not redirected away from the page, but can pay attention to the Resources being deleted.

See if we can make a test that tries to recreate the problem

Closing this as it is a duplicate of #343


Suggested feature: custom modules

It's me again with another suggestion.
It would probably be pretty hard to implement, but i was thinking it might be nice to be able to take a graph and compress it down to a single object, using the IO summary as the IO of the module.
It would help readability a lot when designing complex factories.
For instance, I did this mall build, where the science, maintenance, construction parts, vehicle parts and microchip production could be reduced to single modules.
============================Mall============================
DAXFBCIC$eNqFlUuPEzEMgP9Lzj4kduJMekOLhLiw7PulHkoFW6QuLyEu1f5
3nOkkzjBh9xZ7vvE78cF8NauHg_lmVga_GzA_RMRhCOAcujWYX_nDb_mwNSs
Cszcr9wwTf1r4EJLwrvIXR57n_MYVPlkLKfKEb9AsEHIxZpO4ZNQtcmoZPF8
yLkXMDBXmrDL8pvjCRMApTsiofyFbsuQbnFwnsijRcwoFsR0kkBVkKHHd9_I
LFqK1BbnT0L8UhGICcsUK746hh3novC04cwQKFf9s_gFT7ZBMAIVSNf70ygB
YthA00qtX-s8yL8H7F3rrkiCcUrF42UUiDFj7ECoS3moFBeHiKLzrFDnlVtX
xuD1G7v-XKA_SkmIPbzr2SOzFEhReV4J2OpIJsNigpy7hAOt1op96P0IZQkI
WIyXuDXfqQ1EQ4mV9GmQg8KE66lphkiGsVU4a7ocJSY6BlbjvERG8K82kux4
hNaGSDt0uCbkI4qUSNz3CtV6ue4QXLzXdqyXhB269XPYJ72q2Fz0itV7OlwR
G21bsrEfMcvnYI6j1cqrTv58IC4jFQnjqtNZKwcqdJd95hPOQses804-FYJs
gUr3Jux4SPJBa6SMJfHzZSn5hUousxzsqu2s_5urW-ad8lgdfvuXf43Ggs5L
GTEdlrEqpcf2LIdazPBr1PECqZ1k3tgpOdqSfbA5ebUoovG4lteshtLbUSZ5
-tYzSuSYdeQtoJqH-RzmGKuFMcq2EsrNKsCem0Y6rsaPGvtot1eIIQ5NjI-R
HKsyy5DbaRoqtYGeczLmWEGdglrSKOABqs1A2o9ZUti1pTckBaRUJgbTCREB
aN9n1pBmQbEX1TgykkZGsVo2FBiCNhWS-bVsVr7F46Vqaqpq2taqeasM2d6p
tWhDvVR2ahllVc9NeN16ZnVkdzKPIJ-_lav2RVff8_BevnG93

This feature is quite complex in both  implementation cost and usability. I guess just wrapping is not enough, there must exists possibility to look what is inside, unwrap and edit.
Actually, I have multi-select and copy-paste on todo list, maybe I will try to use your idea to implement mass factory management, but this may be implemented in far future, because of complexity.

I was thinking having a place where you paste a copy code from another
window and it creates a process node for it.
Yes being able to dynamically go in and change things would be great, but
as a first step this would be enough to make a very modular system.
On Mon., May 8, 2023, 14:06 Alexey Usov, @.***> wrote:

This feature is quite complex in both implementation cost and usability. I
guess just wrapping is not enough, there must exists possibility to look
what is inside, unwrap and edit.
Actually, I have multi-select and copy-paste on todo list, maybe I will
try to use your idea to implement mass factory management, but this may be
implemented in far future, because of complexity.
—
Reply to this email directly, view it on GitHub
https://github.com/doubleaxe/daxfb-calculator/issues/4#issuecomment-1538813224,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABBNRBYWVKIMM5YSHSX3L53XFEY3DANCNFSM6AAAAAAXYFWAT4
.
You are receiving this because you authored the thread.Message ID:
@.***>


HTML encoded strings

Exported strings aren't HTML encoded. For example:

Ampersands & Co. <3

Should be rendered as:

Ampersands & Co. <3

Yes, you are totally right, @goblindegook. I will fix it right away.
Thank you very much for letting me know!

@goblindegook, I committed this change [https://github.com/marisaroque/sketch-markup-listify/commit/9917f081ed84d6db0025ae4b8608e1c63171123a].
I think it's fixed now. I'll close the issue.
Thank you again!

Looks good! I made a couple of suggestions, basically just stuff you can remove from your code without worry.
Thanks!


Incorrect external link on "Sandoll"

Hi, this is a staff of Sandoll and we found out that external link of "Sandoll" above is incorrect.
Clicking "Sandoll' will leads to some kind of spam site which definitely not is our link.
Please redirect "Sandoll" link to below address.
http://www.sandoll.co.kr/?lang=en_US

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

ID: 91d203fe-edb5-7fd0-88f1-40a688aee010
Version Independent ID: 42388cb3-6080-2322-5f5f-5111f3b70ffb
Content: Registered typography vendors - Typography
Content Source: typographydocs/vendors/index.md
Product: typography
GitHub Login: @mijacobs
Microsoft Alias: mijacobs

Thank you. Please email us to make the changes so can confirm the request is from the owner of the ID

Dear Mr./Ms. Ali
Thank you for your reply.
We are checking internally about our vendor ID and Password for Microsoft
Vendor system.
Is there any other way that we can request the correction?
Correct url for Sandoll is "http://www.sandoll.co.kr/?lang=en_US"
Best Regards
Lenny
2019년 5월 30일 (목) 오전 10:25, Basit Ali<EMAIL_ADDRESS>작성:

Thank you. Please email us to make the changes so can confirm the request
is from the owner of the ID
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/typography-issues/issues/234?email_source=notifications&email_token=AMDERPNSRVR4KAVTBDNDDQTPX4UIZA5CNFSM4HNVMOBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWRCLVI#issuecomment-497165781,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMDERPNM3BRZHA5YMORQRODPX4UIZANCNFSM4HNVMOBA
.

Hello,
To update your Vendor ID or any other part of your foundry email<EMAIL_ADDRESS>with the updated information.
Source: https://docs.microsoft.com/typography/vendors/register
For verification purposes it is helpful to send this information from the email address registered to the vendor.


Tooltip?

Does sleek-dashboard provides standard ways of showing tooltips (for button, or helps etc)?

https://getbootstrap.com/docs/4.0/components/tooltips/


Day of year

Displays the day of year on the calendar, and adds toggle buttons.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Allowing continuous and discrete variable on AWS batch

Hi there,
Great package! I was wondering how to optimize with continuous as well as discrete(integer) variables  at the same time. Is this possible?
Also, to evaluate my function.. the problem _evaluate is rather processor intense...would I be able to send the work to something like AWS batch to run the def _evaluate portion of the problem to speed up the solution?
Thanks!
Phylroy

Currently, mixed variable optimization is not supported out of the box. However, it can be manually incorporated by writing custom operators (sampling, crossover, mutation).
I am working on the new release right now, which I will release in the end of this month most likely, and there mixed variables will be included. Also, a tutorial will be provided on the homepage. The implementation is based on defining operators, for instance a crossover, with a mask which defines the variable types and the corresponding crossover implementation for each variable type in a dictionary.
The _evaluate function takes a list of individuals.  In between you can use any possible speedup. For example, if you choose a population size of 100 then you can easily distribute those 100 evaluations on a cluster and then, finally, when the solutions are evaluated store the results in out["F"] and out["G"] (if constraints are present). This is one advantage of population-based optimization that parallelization can be implemented without modifying the algorithm itself.

Hi there!  We, too, would like to use pymoo for a continuous+discrete variable search.  We will be looking forward to the next release.  Thanks for your hard work.
-Bill

I have released the new pymoo version 0.3.1.
A small example: https://pymoo.org/tutorial/mixed_variable_problem.html
Please let me know if this covers all you need.

Julian

Looks gorgeous. Thank you very much, Julian, I appreciate it!


feat: allow to specify Java major version

This PR adds an optional input to specify the Java major version to use to run jenkins-maven-cd-action.
Its default value is set to 11 for now, should be updated to 17 when Jenkins controllers will require minimum Java 17 version.
Example of call to use JDK17:
# Note: additional setup is required, see https://www.jenkins.io/redirect/continuous-delivery-of-plugins

name: cd
on:
  workflow_dispatch:
  check_run:
    types:
      - completed

permissions:
  checks: read
  contents: write

jobs:
  maven-cd:
    uses: jenkins-infra/github-reusable-workflows/.github/workflows/maven-cd.yml@v1
+  with:
+    java-version: 17
    secrets:
      MAVEN_USERNAME: ${{ secrets.MAVEN_USERNAME }}
      MAVEN_TOKEN: ${{ secrets.MAVEN_TOKEN }}

Related jenkinsci-dev mailing list thread: https://groups.google.com/g/jenkinsci-dev/c/11P2B9s67tw/m/buquLnLeAwAJ

You happy to merge and release @lemeurherve?
create a release for the latest tag using github ui and clicking the github button to add changelog.
then retag the v1 tag to match the tag created using github releases

Why not run with 17 now? Simpler.

Why not run with 17 unconditionally? Simpler.

I prefer asking as I don't want to make all plugin cd actions fail.

Yes you should be able to build any plugin using JDK 17. The POM will effectively pass -release 11 to tools. In fact most Jenkinsfiles do not use JDK 11 at all any more (only 17 & 21), and for purposes of the CD release workflow it is even less important to run on the older JDK because the only reason to include JDK 11 in Jenkinsfile would be to run tests on 11 (in case there is some subtle behavioral difference) yet the CD workflow skips all tests.

Thanks for the detailed response!
Changed the pull request to a java version bump.

Yes you should be able to build any plugin using JDK 17. The POM will effectively pass -release 11 to tools. In fact most Jenkinsfiles do not use JDK 11 at all any more (only 17 & 21), and for purposes of the CD release workflow it is even less important to run on the older JDK because the only reason to include JDK 11 in Jenkinsfile would be to run tests on 11 (in case there is some subtle behavioral difference) yet the CD workflow skips all tests.

I believe this is quite a change of scope for the PR which should be shared on the mailing list + the associated issue.
As devil is in the details, would be worth it to plan and announce this change so at list it would be visible (a PR discussion is never visible except by the author and reviewers).

I've posted a comment in #30 and asked for opinions in https://groups.google.com/g/jenkinsci-dev/c/11P2B9s67tw/m/buquLnLeAwAJ

Released and oh cool I didn't realise the v1 would get automatically moved, that's nice: https://github.com/jenkins-infra/github-reusable-workflows/blob/main/.github/workflows/self-update-major-tag.yml


direction option

direction option added.

Thanks for adding this valuable options. Have merged and done some necessary changes in the code.


AWS profile region restrictions

AWS creates a default VPC per region. Starcluster creates its instances in this VPC by default so that the cluster instance are not accessible from the outside world. In order to do this Starcluster must be run from a machine that is in the VPC. Starcluster also has the option to assign public ips to all node in the cluster that then removes this restriction although there is potentially a greater security risk. So what does this mean client? We need to expose and check box indicating whether to use public ip on cluster nodes. This check box will have different behavior depending if the HPCCloud stack is deployed on EC2 or not.
EC2 deployment

Check box is checked -
We configure Starcluster to use public IP and the pull list of AWS regions is available to choose from.
Check box is unchecked - We have to restrict the regions that can be used to the region the stack has been deployed in so Starcluster will have access to the default VPC. The region will be configured into a JSON file as part of the deployment process.

Non EC2 deployment

In this case the only option is to use public IP for every node as Starcluster will be running outside EC2.
The checkbox should be checked and disabled and all regions will be availble to the user to create clusters in.

We are going to simplify this further. There will be no public ips check box.
EC2 deployment
We have to restrict the regions that can be used to the region the stack has been deployed in so Starcluster will have access to the default VPC. The region will be configured into a JSON file as part of the deployment process.
Non EC2 deployment
In this case there will be not access to EC2, so traditional cluster should be the only thing a user can configure. This deployment will be indicated by the fact that there will be no region set in the JSON file mentioned above.

+1
On Mon, Sep 28, 2015 at 7:12 AM, Chris Harris<EMAIL_ADDRESS>wrote:

We are going to simplify this further. There will be no public ips check
box.
EC2 deployment
We have to restrict the regions that can be used to the region the stack
has been deployed in so Starcluster will have access to the default VPC.
The region will be configured into a JSON file as part of the deployment
process.
Non EC2 deployment
In this case there will be not access to EC2, so traditional cluster
should be the only thing a user can configure. This deployment will be
indicated by the fact that there will be no region set in the JSON file
mentioned above.
—
Reply to this email directly or view it on GitHub
https://github.com/Kitware/HPCCloud/issues/33#issuecomment-143739550.

@TristanWright Where do you think the configured file should be added to HPCCloud?

How about the configuration gets reached from a service or a factory injected into the user-preferences? The file can be on the root level for simplicity's sake/

Sounds good to me

Starcluster was removed from cumulus, is this issue still pertinent?

Yes, lets leave this open


NixOS build-vm does not know virtualisation.diskSize

Issue description & Steps to reproduce
On current master (bdb8baf) and at least since 0b3e1f8:
$ nixos-rebuild build-vm -I nixpkgs=$HOME/projects/nixpkgs
building Nix...
error: The option `virtualisation.diskSize' defined in `/home/layus/projects/nix_config/inginious-server.nix' does not exist.
(use ‘--show-trace’ to show detailed location information)
error: The option `virtualisation.diskSize' defined in `/home/layus/projects/nix_config/inginious-server.nix' does not exist.
(use ‘--show-trace’ to show detailed location information)
building the system configuration...
# the build proceeds normally from here.

Importing <nixos/modules/virtualisation/qemu-vm.nix> fixes the first part, but breaks the vm build :disappointed:
building Nix...
building the system configuration...
error: The option `virtualisation.writableStore' in `/home/layus/projects/nixpkgs/nixos/modules/virtualisation/qemu-vm.nix' is already declared in `/nix/store/8vs3b5l91pklnczz9rqmmdr5bw32bmnh-nixos-16.09pre82105.7465bcd/nixos/nixos/modules/virtualisation/qemu-vm.nix'.
(use ‘--show-trace’ to show detailed location information)

... which is kind of expected.
Importing <nixpkgs/nixos/modules/virtualisation/qemu-vm.nix> fixes all the warnings.
Is this the expected behavior? What has changed from one month ago where everything went fine without imports?
Technical details

nixos-version: 16.09.git.aa8bc97M (Flounder)
nix-env --version: nix-env (Nix) 1.11.2
nix-instantiate --eval '' -A lib.nixpkgsVersion: "16.09pre82105.7465bcd"

/cc @nbp as you master the module import system :-).

Is this the expected behavior? What has changed from one month ago where everything went fine without imports?

No this is not the expected behaviour.
This is indeed weird, as qemu-vm.nix is the only module to define diskSize and writableStore options.  Also, this module is supposed to be included by default in vmConfig of nixos/default.nix.
@layus Are you able to bisect the config /home/layus/projects/nix_config/inginious-server.nix, and isolate the minimal set which cause the same error?  And then bisect nixpkgs to find which commit cause this change?

I can reproduce it with export NIXOS_CONFIG=/path/to/minibug.nix.
# minibug.nix
{
  virtualisation.diskSize = 1024 * 1024;
}

@nbp, Git bisect points at 05a36304ea812cc891a1d03a497b8ee7ce3729de, which look innocuous, but the commit contains a discussion about it triggering an infinite recursion, so maybe it induces a subtle breakage ?

Lost interest in this one... Let's close it for now.

Yes, the bisect sounds wrong.


VHDX resize tests: Remove code copying files to /root

This is no longer needed after merge of PR #289

@santoshx can you please post test results here?

@santoshx can you please post test results here?

@lizzha  Here is the test results:
Test Results Summary
ICA test run on 10/30/2018 07:34:47
VHD under test D.vhdx
ARM Image under test  :  :  :
Total Executed TestCases        16 (       16 Pass,        0 Fail,        0 Abort)
Total Execution Time(dd:hh:mm) 0:3:4
XML file: TestConfiguration
#Sr. Test Name : Test Result : Test Duration (in minutes)

VHDX-RESIZE-TO-BIGGER512 : PASS : 11.76
VHDX-RESIZE-TO-BIGGER4096 : PASS : 6.05
VHDX-RESIZE-TO-BIGGER512-FIXED-IDE : PASS : 14.86
VHDX-RESIZE-TO-BIGGER512-DYNAMIC-IDE : PASS : 7.96
VHDX-RESIZE-TO-SMALLER512 : PASS : 7.66
VHDX-RESIZE-TO-SMALLER4096 : PASS : 7.24
VHDX-RESIZE-GROWSHRINK-SCSI : PASS : 8.95
VHDX-RESIZE-GROWSHRINK-SCSI-OFFLINE : PASS : 9.93
VHDX-RESIZE-OVER2TB-SCSI : PASS : 13.64
VHDX-RESIZE-OVER2TB-IDE : PASS : 14.44
VHDX-RESIZE-GROWOVER2TB-SHRINK-SCSI-ONLINE : PASS : 12.98
VHDX-RESIZE-GROWOVER2TB-SHRINK-SCSI-OFFLINE : PASS : 16.25
VHDX-RESIZE-GROWSHRINK-IDE : PASS : 10.14
VHDX-RESIZE-GROWOVER2TB-SHRINK-IDE : PASS : 18.5
VHDX-RESIZE-GROW-FILESYSTEM-512 : PASS : 9.41
VHDX-RESIZE-GROW-FILESYSTEM-4096 : PASS : 14.94