WIP: Add buffer to log writer

close  #2064
tested with a program that spils out 3000 lines of logfiles.
It took 2min on current v1.0.0./main and 4sec with this.
But the log output is broken and dont live stream anymore the bufio.Writer only consider the buffer when to write.
We alos sould consider linebreaks and time components too.
TODO:

[ ] create own bufio.Writer that:

[ ]  writes if for smal time there is no new content for reader
[ ] write on new lines before buff is full

[ ] make log save infrastructure not reliant on the unwritten promise that each write is it's own line

[ ] e.g. time stamp calculation#

Sponsored by Kithara Software GmbH

I'll just add that you should probably consider \r for programs that print progress bars.

@6543 How far is the progress here? Is this likely to make it into 2.0?

I've added a timer to the buffer so when ever a specific amount of time (currently 1s) or a specific length of data is in the buffer it is being flushed, so we should have live-logs with a maximum of a 1s delay. Added the build_pr_images label so everyone being interested could help testing. Code definitely needs a few improvements and tests, but I guess when everything is working it could be merged for the beginning as a first enhancement.

Have these points been addressed:

But the log output is broken and dont live stream anymore the bufio.Writer only consider the buffer when to write.
We alos sould consider linebreaks and time components too.

For the "live-streaming" the buffer will be flushed after 1 second or if it is full. Got this concept of having a 1s trigger from drone and other CI systems. Left the handling of new-lines untouched for now. Might be sth for a new PR.

Well, that affects all other files also, e.g. agent/logger/buf.go. Not that I really care, but such changes look arbitrary to me.

Did some testing regarding the current logging speed. Tested with a small amount of data (just the timestamps) for now.
Without the changes from this PR (unix-timestamps in ms):

171406337_2206 (log send by docker backend)
171406337_2206 (log send by agent via grpc)
171406337_2207 (log received by server via grpc)
171406337_4813 (log send by server via sse stream)
171406337_4815 (log received by UI)

With the changes from this PR (unix-timestamps in ms):

171406355_4028 (log send by docker backend)
171406355_4028 (log send by agent via grpc)
171406355_4029 (log received by server via grpc)
171406355_6546 (log send by server via sse stream)
171406355_6547 (log received by UI)

While doing some testing I noticed that our streaming logic seems to have some time issues.

Generally improve the log streaming in #3722 (released in 2.6) and therefore these changes shouldn't be needed anymore.


Fix tutorial with Aer#1388

Summary
Fix tutorial errors with the recent change in the main branch of Aer Qiskit/qiskit-aer#1388.
The CI step that runs stable tutorials was disabled for now since the stable tutorials will fail with the new Aer too.
Since the 0.3.0 is imminent, the new stable will be stable/0.3 with the fixed tutorials in this PR.
Once the release happens, the CI step will be re-enabled.
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 82.735%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
714

Relevant Lines:
863

💛  - Coveralls


Scroll Restoration

Whenever I try to read through the docs when I click the next topic when being scrolled at the bottom from sidebar, it automatically scrolls me up with no reason!

Hey @broisnischal 👋  we recently rewrote our docs and I believe this should be fixed now (I couldn't reproduce it in Chrome Version 130.0.6723.92 (Official Build) (x86_64))!
If you still encounter this problem, please feel free to re-open the issue and also share with us which browser you're using 🙏


Update getting-started.md

Updated section on animations to clarify directions on where to import when using Angular Universal

I signed it!


cli/verifier: verify destination for connectivity config

Description:
Adds the destination verifier for connectivity checks.
Also updates the test configs to reflect the name change
made to inbound filter chains in 82492c0b.
Part of #4634

Testing done:
# permissive mode
$ osm verify connectivity --from-pod curl/curl-7bb5845476-8hggq --to-pod httpbin/httpbin-69dc7d545c-z5l6r --service httpbin --app-protocol http
---------------------------------------------
[+] Context: Verify if pod "curl/curl-7bb5845476-8hggq" can access pod "httpbin/httpbin-69dc7d545c-z5l6r" for app protocol "http"
Status: Success

---------------------------------------------

# SMI mode
$ osm verify connectivity --from-pod bookbuyer/bookbuyer-5c6bc7b74d-r7x5g --to-pod bookstore/bookstore-v1-6bc7859dbf-9c7s8 --service bookstore-v1
---------------------------------------------
[+] Context: Verify if pod "bookbuyer/bookbuyer-5c6bc7b74d-r7x5g" can access pod "bookstore/bookstore-v1-6bc7859dbf-9c7s8" for app protocol "http"
Status: Success

---------------------------------------------

# SMI mode
$ osm verify connectivity --from-pod bookbuyer/bookbuyer-5c6bc7b74d-r7x5g --to-pod bookstore/bookstore-v1-6bc7859dbf-9c7s8 --service bookstore-v2
---------------------------------------------
[+] Context: Verify if pod "bookbuyer/bookbuyer-5c6bc7b74d-r7x5g" can access pod "bookstore/bookstore-v1-6bc7859dbf-9c7s8" for app protocol "http"
Status: Failure
Reason: A verification step failed
Suggestion: Please follow the suggestions listed in the failed steps below to resolve the issue

[++] Context: Verify if namespace "bookbuyer" is monitored
Status: Success

[++] Context: Verify if namespace "bookstore" is monitored
Status: Success

[++] Context: Verify Envoy sidecar on pod "bookbuyer/bookbuyer-5c6bc7b74d-r7x5g"
Status: Success

[++] Context: Verify Envoy sidecar on pod "bookstore/bookstore-v1-6bc7859dbf-9c7s8"
Status: Success

[++] Context: Verify Envoy config for traffic:
	source pod: bookbuyer/bookbuyer-5c6bc7b74d-r7x5g
	destination pod: bookstore/bookstore-v1-6bc7859dbf-9c7s8
	destination service: bookstore/bookstore-v2
	destination protocol: http
Status: Failure

[+++] Context: Verify Envoy config on source for traffic:
	source pod: bookbuyer/bookbuyer-5c6bc7b74d-r7x5g
	destination pod: bookstore/bookstore-v1-6bc7859dbf-9c7s8
	destination service: bookstore/bookstore-v2
	destination protocol: http
Status: Success

[+++] Context: Verify Envoy config on destination for traffic [
	source pod: bookbuyer/bookbuyer-5c6bc7b74d-r7x5g
	destination pod: bookstore/bookstore-v1-6bc7859dbf-9c7s8
	destination service: bookstore/bookstore-v2
	destination protocol: http]
Status: Failure
Reason: Did not find matching inbound filter chain for service "bookstore/bookstore-v2": filter chain match inbound_bookstore/bookstore-v2_14001_http not found

---------------------------------------------

Affected area:

Functional Area

CLI Tool
[X]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? no

Did you notify the maintainers and provide attribution?

Is this a breaking change? no

Has documentation corresponding to this change been updated in the osm-docs repo (if applicable)? n/a

Codecov Report

Merging #4672 (ecfe038) into main (82492c0) will decrease coverage by 0.05%.
The diff coverage is 60.21%.

@@            Coverage Diff             @@
##             main    #4672      +/-   ##
==========================================
- Coverage   69.76%   69.71%   -0.06%
==========================================
  Files         217      217
  Lines       15020    15112      +92
==========================================
+ Hits        10479    10535      +56
- Misses       4491     4527      +36
  Partials       50       50

Flag
Coverage Δ

unittests
69.71% <60.21%> (-0.06%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/cli/verifier/envoy_config.go
64.42% <60.21%> (-2.04%)
:arrow_down:

Continue to review full report at Codecov.

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


dropdown menus moving with page scroll

Describe the bug

The dropdown menus seem to scroll with the page. Seems to only be Firefox.
Video + Details:
https://transitmatters.slack.com/archives/GSJ6F35DW/p1693958876191559

confirmed that this issue is no longer happening on any browser, including Firefox


Rewire cmake internals for cmake's target_source()

...instead of delaying the cmake target creating the the fips_end_*() function, an empty target is now created in the fips_begin_*() macros, and adding sources, options, dependencies etc is now directly to the respective cmake target_*() functions instead of first gathering everything in variables. This simplifies the cmake scripts quite a bit and allows to directly use standard cmake commands (like target_sources() or target_compile_options() inside the fips begin/end block.

Yeah it's a weird feature indeed.


SSR

I noticed a ssr.index.js in the ./dist folder but I'm unsure how I could use it for the Gridsome build to work.
Any ideas?
Edit: I tried using the lazy-loaded component approach (described here) but it leads to a window is not defined error and the ssr.index.js doesn't seem to export a Vue component.
And using the following leads to a successfully built page with no chat (using the <ClientOnly>...</ClientOnly> wrapper in the template):
export default {
  name: 'chatbox',
  components: {
    BeautifulChat: () =>
      import('vue-beautiful-chat/dist/ssr.index')
        .then(m => m.default)
        .catch()
  },

Is there a way to get the SSR export to a valid Vue Component?

hi Berkmann18, do you succeed to solve the problem ?
I managed to add vue-beautiful-chat to nuxt throught plugin option. like that 👍
nux.config.js (ssr: false seems to be unnecessary)
  plugins: [     { src: '~plugins/chat', mode: 'client', ssr: false}, }
With that plugin in plugin folder :
`import Vue from 'vue'
import Chat from 'vue-beautiful-chat'
export default () => {
Vue.use(Chat)
}`
The chat works perfectly after that.
But I still have an avertissement error  on chat scrollHeigth event (linked to window event) : 404 NOT FOUND.
Someone to help me supress this error ?
thanks

@sk8killer I didn't really solve it, the only solution I found (in the short timeframe I had) was to have the vue-beautiful-chat source modules placed in my Gridsome's components directory (with the appropriate credits of course).
I'm not that familiar with Nuxt so I'm unsure how I could help on that other than suggesting solutions like the ones above or those others suggested like:

loading the chat in the mounted hook or,
importing it in the component that is wrapped in a <ClientOnly> </ClientOnly> snippet.
...

@Berkmann18 Did you try using this component normally? So importing and registering in main.js file of your Gridsome site, and then using it in one of the pages or components without <ClientOnly> tag.
I just tried that in a clean Gridsome project, and both the develop and build commands work fine, with the chat usable in the generated build (I served it with http-server).
I don't think the lazy-loading approach has any advantages in Gridsome since the component will be rendered and included in the final build regardless.
Also, the build process has been updated in #156, so the ssr.index file will not exist in the next release, with SSR support existing in the regular build.

@a-kriya Yes, obviously but that lead to a window is not defined so the only possible ways were to use the technique recommended by the Gridsome team (all of which failed prior to the creation of this issue).

I just tried that in a clean Gridsome project, and both the develop and build commands work fine, with the chat usable in the generated build (I served it with http-server).

Interesting, the build approach didn't work back then.

Also, the build process has been updated in #156, so the ssr.index file will not exist in the next release, with SSR support existing in the regular build.

That's nice to know.

@Berkmann18 Well, you hadn't mentioned that in the original post, so I thought it best to confirm since I couldn't reproduce the issue with that approach using the currently published NPM version 2.4.1 (without the build changes from that PR).
If you're able reproduce it in a clean Gridsome site, can you please share that?

@a-kriya Ah I see, did you try it with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(that's what I had looking at the PR I referenced)?

If you're able reproduce it in a clean Gridsome site, can you please share that?

Sure, I'm hoping to use that for a more recent project and I'll see if I get this issue.

Hi,
Hi,
Hi, I'm trying to integrate chat with Nuxtjs/Vuetify, the problem is the chat window hiding behind the other components of the page, not overlaying them. Below is a basic component where I want to use the chat. How can I make it overlay, any pointers?
<template>   <v-app id="appRoot">     <v-main>       <beautiful-chat         :participants="participants"         :title-image-url="titleImageUrl"         :on-message-was-sent="onMessageWasSent"         :message-list="messageList"         :new-messages-count="newMessagesCount"         :is-open="isChatOpen"         :close="closeChat"         :open="openChat"         :show-emoji="true"         :show-file="true"         :show-edition="true"         :show-deletion="true"         :show-typing-indicator="showTypingIndicator"         :show-launcher="true"         :show-close-button="true"         :colors="colors"         :always-scroll-to-bottom="alwaysScrollToBottom"         :disable-user-list-toggle="false"         :message-styling="messageStyling"         @onType="handleOnType"         @edit="editMessage"       />       <app-navigation></app-navigation>       <transition mode="out-in">         <nuxt></nuxt>       </transition>       <app-footer></app-footer>     </v-main>   </v-app> </template>

Hi,
Hi,
Hi, I'm trying to integrate chat with Nuxtjs/Vuetify, the problem is the chat window hiding behind the other components of the page, not overlaying them. Below is a basic component where I want to use the chat. How can I make it overlay, any pointers?
<template>   <v-app id="appRoot">     <v-main>       <beautiful-chat         :participants="participants"         :title-image-url="titleImageUrl"         :on-message-was-sent="onMessageWasSent"         :message-list="messageList"         :new-messages-count="newMessagesCount"         :is-open="isChatOpen"         :close="closeChat"         :open="openChat"         :show-emoji="true"         :show-file="true"         :show-edition="true"         :show-deletion="true"         :show-typing-indicator="showTypingIndicator"         :show-launcher="true"         :show-close-button="true"         :colors="colors"         :always-scroll-to-bottom="alwaysScrollToBottom"         :disable-user-list-toggle="false"         :message-styling="messageStyling"         @onType="handleOnType"         @edit="editMessage"       />       <app-navigation></app-navigation>       <transition mode="out-in">         <nuxt></nuxt>       </transition>       <app-footer></app-footer>     </v-main>   </v-app> </template>


Tag releases

Can you please tag your releases (see here), it would be helpful for the F-Droid release. You could also attach the binaries to your releases (see here).
That's pretty easy and very helpful for those of us who aren't using Google services.
#16

In v1.1.0, I added v1.1.0 tag.
Thank you!


[doc] load_results loads all files matching an undocumented pattern and not just a single file as stated in the documentation

Describe the bug
load_results loads all results ending with 'monitor.csv' (and json files) and not just a single file as the documentation states.
Code example
Erroneous comment here
System Info
N/A

Hello,
thanks for the issue. We would appreciate a PR that fixes this issue ;)


[Clinical Module prescription] Remove drug from new prescription is  not working after clicking on refill.

[Actual Results]: The system is not removing the drug from the new prescription list if the user clicks on the remove button
[Expected results]: The system should remove the drug from the new presciption list when the user clicks on remove drug
[Steps to reproduce]: (The patient must have at least one prescribed drug )Clinical module-> Patient dashboard -> Prescription Tab-> Refill drug button-> remove button

The system does remove all the drugs from new prescription. It does not remove the controls (cancel and save button).


⚠ Processors has degraded performance

In 5c52ccc, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 98 ms

Resolved: Processors performance has improved in 1f40adc.


add license parser to trivy scan

Description
Trivy allows for license scan and the report will be provided in json format. The changes are made to parse the license report

Hi @abheeshtan
Please add to the unit tests to run that new sample report. Also base your PR against the dev branch

Hi @abheeshtan
Please add to the unit tests to run that new sample report. Also base your PR against the dev branch

@Maffooch unit tests are added, and the PR is based against the dev branch.

2023-02-15T17:40:15.8633792Z uwsgi_1         | ======================================================================
2023-02-15T17:40:15.8634108Z uwsgi_1         | FAIL: test_license_scheme (unittests.tools.test_trivy_parser.TestTrivyParser.test_license_scheme)
2023-02-15T17:40:15.8634369Z uwsgi_1         | ----------------------------------------------------------------------
2023-02-15T17:40:15.8634555Z uwsgi_1         | Traceback (most recent call last):
2023-02-15T17:40:15.8634825Z uwsgi_1         |   File "/app/unittests/tools/test_trivy_parser.py", line 182, in test_license_scheme
2023-02-15T17:40:15.8635036Z uwsgi_1         |     self.assertEqual("HIGH", finding.severity)
2023-02-15T17:40:15.8635218Z uwsgi_1         | AssertionError: 'HIGH' != 'High'
2023-02-15T17:40:15.8635342Z uwsgi_1         | - HIGH
2023-02-15T17:40:15.8635466Z uwsgi_1         | + High
2023-02-15T17:40:15.8635579Z uwsgi_1         |
2023-02-15T17:40:15.8635690Z uwsgi_1         |
2023-02-15T17:40:15.8635941Z uwsgi_1         | ----------------------------------------------------------------------
2023-02-15T17:40:15.8636102Z uwsgi_1         | Ran 2263 tests in 449.881s
2023-02-15T17:40:15.8636212Z uwsgi_1         |
2023-02-15T17:40:15.8636396Z uwsgi_1         | FAILED (failures=1, skipped=364)

hi @abheeshtan ,
we'd also be interested into this feature. any chances to get that test fixed?


perf(transformer): RegExp transform exit early if nothing to do

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#5486  👈
#5484
#5483
#5482
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite


Fix VSCode draft window on Mac

Switches to using tags for everything and then setting them by listening for app focus switch rather than trying to use matches.  Should be more robust, and also means it should reflect settings changes in real time
Also fixed timing issue on submit

[ ] Test Windows
[ ] Test Linux

Have tested this on VSCode on Linux, it works fine.

this works fine on windows  as well


Code Review Checklist

Do we have a code review checklist? If not, I think we should. Maybe we could just crowdsource this by starting a discussion on astropy-dev asking people what they think should go on the list?
Relevant articles which I skimmed:

http://blog.smartbear.com/code-review/creating-your-code-review-checklist/
https://blog.fogcreek.com/increase-defect-detection-with-our-code-review-checklist-example/

Documentation of how to do code review should go in https://astropy.readthedocs.io/en/latest/development/workflow/maintainer_workflow.html somewhere.

Is this for review or PR? the title of the issue and the discussion is ambiguous.
Also, since the opening of this, we have a PR template, that should have all the pointers for contributors. We still don't have the review checklist, but that's a smaller issue as maintainers are the ones doing the review and they have the gist of it already (having guidelines though useful for onboarding new maintainers)

Looks like a duplicate of https://github.com/astropy/astropy-project/issues/212 . See https://github.com/astropy/astropy-project/issues/212#issuecomment-2253297059


Feat: Ability to add migrations without actually running it

Is your feature request related to a problem? Please describe.
This will add the migration to the migrations table without running it. This is useful for migrations created
after manual changes have already been made to the database or when migrations have been run externally
(e.g. by another tool or application), and you still would like to keep a consistent migration history.
Describe the solution you'd like
Something like
npx mikro-orm migration:up --fake
Describe alternatives you've considered
Right now I am manually adding the migration file to the migrations table
Additional context
Add any other context about the feature request here.

How would you see this working?
You might have more than on migration that needs to be applied.
By adding this you risk “fake applying” migrations you need.
If this is something people need, it might be better to have the CLI interactive, and provide you with a list of migrations it’s going to run, where you can mark some as “already used”.

I don't think we need --fake, that feels weird to me. But we can have a command to log/unlog a single migration by name, that feels quite handy and is very easy to do.

if this is implemented in Umzug instead of in MikroORM

In fact, umzug is not adding much value here, and could be easily removed, most of the stuff that @mikro-orm/migrations are doing is implemented on top of umzug, replacing most of what it does with custom implementations to allow different driver storages and whatnot.

@B4nan did you mean something like this when you said logging https://www.doctrine-project.org/projects/doctrine-migrations/en/3.5/reference/managing-migrations.html#dry-run

No, log and unlog and umzug names to add/remove lines from the migrations table, it has nothing to do with logging as in printing stuff to console.

Though then again, being able to log/unlog multiple at once may also come in handy in more exotic setups... and in that case, I would expect all migration names to be in the sequence that they would be logged/unlogged. Combined with a "--dry-run" like option to see the migrations that are to be migrated, but not migrate them, one could implement log/unlog that behaves like up/down with a --fake flag, if they really need to.

I don't think we need that (or should I say, I am not interested in writing that myself, and I still don't like the idea of --fake flag in the first place). Let's not complicate things, OP asked for a way to add lines to the migrations table, that's what I can add easily, the rest doesn't feel justified for the added complexity.
Also for dry running, I don't see how it could work, as the migration can contain dynamic stuff, e.g. query execution, not just the addSql calls. But I surely see a value in that option, maybe we could just log the code of such migrations, as running them might already bring side effects.

The scenario I am trying to cover is :
Lets say I modified some  columns to a table externally
Later on I wrote a migration to cover the change. Since the change was already applied, I wanted the orm to be able to track this as well(which is why adding it to the migration table without actually running it) .


proposal multi-target

Based on your recent changes regarding test projects to net7.0;
As stated in recent exchanges, I propose to enable multi-target in the test projects, but also in the main projects.
Please review the proposed changes and comment.
Issue describing the changes in this PR
resolves #issue_for_this_pr
Pull request checklist

[x] My changes do not require documentation changes

[ ] Otherwise: Documentation issue linked to PR

[x] My changes should not be added to the release notes for the next release

[ ] Otherwise: I've added my notes to release_notes.md

[x] My changes do not need to be backported to a previous version

[ ] Otherwise: Backport tracked by issue/PR #issue_or_pr

[x] I have added all required tests (Unit tests, E2E tests)

Additional information
Additional PR information

@bobbyangers can you explain what the end customer benefit of this PR is? What scenarios does this unblock? What issues does it address?

@bobbyangers can you explain what the end customer benefit of this PR is? What scenarios does this unblock? What issues does it address?

In a previous exchanged you mentionned the concern about supporting a wide range of customer, and reducing the risk to excisting consumer of the package.  In this proposal, I am summitting a proposal to expand the sdk to natively support netstandard2.0, net6 and net7.0.    Using the method already in place (ie multi-targeting), and expanding this to the test projects, and validating the versions against the same tests.     This in effect, removes the guess work (and assumptions) and validates the core modules and SDK actually works with all supported versions (not simply assume that everything is backward compatible from 'net7.0`).
The problematic I am trying to solve is that when writing a net6.0 function, I want the core module and sdk to use net6.0,  when using net7.0, then I want to use net7.0 at all levels as well.
For example, when the sdk and core module are compile against net5.0 and that I get warning from the compiler and from my static code analyzer that my modules rely on 'unsupported or even 'unsafe modules,  policy required that I use more recent modules and framework.


toggle button for soql builder- not working

Summary
I am unable to use the SOQL builder
Steps To Reproduce:

install salesforce extension pack
create a file- foo.soql
click button on top right corner to toggle to soql builder
error prompt appears: command 'soql.builder.toggle' not found

Expected result
soql builder should open up
Actual result
error prompt appears: command 'soql.builder.toggle' not found
and soql builder does not appear
Additional information

Salesforce Extension Version in VS Code:
v53.0.0
SFDX CLI Version:
v53.0.0
OS and version:
macOS Catalina and 10.15.17

hi @aishanya11 - we haven't been able to repro this.  What happens if you use the Create Query in SOQL Builder command instead to open it?


Files with incompatible licenses must be removed.

These files have incompatible licenses and must be removed.
examples/polkadot/ballot.sol
testdata/solang_import_resolution_tests/01_solang_remap_target/contracts/Contract.sol
testdata/solang_import_resolution_tests/01_solang_remap_target/contracts/Contract2.sol
testdata/solang_import_resolution_tests/02_solang_incorrect_direct_imports/Ambiguous.sol
testdata/solang_import_resolution_tests/02_solang_incorrect_direct_imports/contracts/Ambiguous.sol
testdata/solang_import_resolution_tests/02_solang_incorrect_direct_imports/contracts/Contract.sol
testdata/solang_import_resolution_tests/02_solang_incorrect_direct_imports/resources/node_modules/lib/Ambiguous.sol
testdata/solang_import_resolution_tests/03_ambiguous_imports_should_fail/Ambiguous.sol
testdata/solang_import_resolution_tests/03_ambiguous_imports_should_fail/contracts/Ambiguous.sol
testdata/solang_import_resolution_tests/03_ambiguous_imports_should_fail/contracts/Contract.sol
testdata/solang_import_resolution_tests/03_ambiguous_imports_should_fail/resources/node_modules/lib/Ambiguous.sol
testdata/solang_import_resolution_tests/04_multiple_map_path_segments/contracts/Contract.sol
testdata/solang_import_resolution_tests/05_import_path_order_should_not_matter/contracts/Contract.sol
testdata/solang_import_resolution_tests/06_redundant_remaps/contracts/Contract.sol

The report is here

@xermicus that first file is yours
The other files were added as tests to make sure solang's imports work the same as solc.  We'll have to remove those.


Fix the iproxy

Fixing the iproxy again. 😄
I have tested locally and it works fine. There might be a race condition in rare case. Sometimea the proxy setup can take a little longer. When that happens the user will still have to retry in 300 seconds. Then it will work again.
I found this default waiting is quite long. Not sure if there is a reason behind. This can however be overwritten by adding something like retryBackoffTime=3000 in the desired capabilities. So it is not a big thing if it is documented somewhere.

Fixing the iproxy again.
I have tested locally and it works fine. There might be a race condition in rare case. Sometimea the proxy setup can take a little longer. When that happens the user will still have to retry in 300 seconds. Then it will work again.

Yes, exactly sometimes it will take time to start better we can add some NOTE to increase retrycount  so user can aware. Lets's add it then will publish a beta version to cover wider audience.

Fixing the iproxy again.
I have tested locally and it works fine. There might be a race condition in rare case. Sometimea the proxy setup can take a little longer. When that happens the user will still have to retry in 300 seconds. Then it will work again.

Yes, exactly sometimes it will take time to start better we can add some NOTE to increase retrycount  so user can aware. Lets's add it then will publish a beta version to cover wider audience.

Fixing the iproxy again.
I have tested locally and it works fine. There might be a race condition in rare case. Sometimea the proxy setup can take a little longer. When that happens the user will still have to retry in 300 seconds. Then it will work again.

Yes, exactly sometimes it will take time to start better we can add some NOTE to increase retrycount so user can aware. Lets's add it then will publish a beta version to cover wider audience.

This is actually mentioned in the README.md. Shall I add something else? Where is it supposed to be?

Fixing the iproxy again.
I have tested locally and it works fine. There might be a race condition in rare case. Sometimea the proxy setup can take a little longer. When that happens the user will still have to retry in 300 seconds. Then it will work again.

Yes, exactly sometimes it will take time to start better we can add some NOTE to increase retrycount so user can aware. Lets's add it then will publish a beta version to cover wider audience.

This is actually mentioned in the README.md. Shall I add something else? Where is it supposed to be?

Ah! it actually mentioned and the default is also 10 so fine let me merge and plan for beta.

Ah! it actually mentioned and the default is also 10 so fine let me merge and plan for beta.


Make logo clickable + add ALT text

Current behavior: at pycon.sk, the text "PyCon SK" in the upper left corner in the navigation bar is clickable but the logo right next to it isn't.
Desired behavior: the logo should be clickable and point to the same page as the text "PyCon SK". Also, ALT text should be provided.

What should ALT text state? "Home" or "Index" or something else?

"PyCon SK Home"?

That's fine by me :) I'll get the patch out in a few minutes.

Please, review the code and if it's OK, close the issue and get it out to the production server. Thanks.


Loading Indicator is pixelated

The loading indicator seems to be in the wrong size and therefore appears very pixelated.
Device: iPhone 14 Pro Max

Thanks for the feedback we will improve the quality of the spinner

Loading indicator should be improved


HTTPS Everywhere

Is your feature request related to a problem? Please describe.
Presently to enable such thing, extension is required. However, I prefer if such things are built-in.
Moreover this being a privacy oriented browser, it is important to have such a feature.
Describe the solution you'd like
Something like how Brave has done - "Upgrade connections to HTTPS" setting
Describe alternatives you've considered
NA
Additional context
NA

This feature seem to be advertised on the website of the project, under "Enhancing Features" here:
https://ungoogled-software.github.io/features/#enhancing-features
First one atm is "Use HTTPS by default when a URL scheme is not provided (e.g. Omnibox, bookmarks, command-line)"
But I also don't have it working here, e.g. if you type "e.var.nz/asdfg" into address bar, browser goes to http:// URL instead of https:// (and there's no redirect, so it stays there).
This is a very nice feature, which I believe eliminates a large class of still very relevant security issues, so I'd also love to see it restored here, assuming that patch was maybe dropped by mistake at some point.
Here's one patch implementing this feature, in case it might be useful:
https://github.com/Rob--W/https-by-default/blob/master/chrome/https-by-default.patch


Telegraf seems to have a memory leak

In my cluster running the 2.0 official release I have noticed that telegraf works its way up to 2GB of memory usage before it seemingly gets cleaned up and starts over.

Are you noticing the pod restarting a lot? There was an issue in the 0.13.x version of telegraf that caused the binary to panic when sending data to influx - https://github.com/influxdata/telegraf/issues/1268
Check the pod logs and see if you see a similar erorr message.

Unfortunately I actually killed off the DS, I have my own monitoring stuff in place so I shut down most of the deis-monitor components this morning.
I don't believe that the container is getting restarted though, if that was the case the container ids in the chart above would have changed.

Hello, I think I got the same issue.
I suspect prometheus plugin. It seems it doesn't closing connection :/
Run on you apiservers:  netstat -ntp | grep 8080 | wc -l

So we have seen this happen (especially on larger clusters) so we disabled the prometheus plugin by default in the image (although the chart turns it on). This means you will lose out on k8s metrics and container metrics. I will open an issue with telegraf and see if we can get it fixed.

See here - https://github.com/influxdata/telegraf/issues/1405

PR  influxdata/telegraf#1406 created

So I have rebuilt the image to include latest master changes. It seems to have fixed the memory leak problem but Im not 100% on that. If you want to redeploy telegraf and check it out that would be awesome.

@jchauncey testing today or tomorrow. I let you know when I get results ;)

The issue is fix for me !


Bad parsing of Opensmile output

The parsing of the opensmile output is mostly good, but sometimes, some irregularities in the console output of opensmile are badly parsed and this results in weird onset/offset in the output rttm (in 1 file I had an offset of [1], in one other I had an offset of 159.42(MSG), and sometimes I have a line with, e.g., onset=74.37, offset=-74.37).
When this occurs, diartk seems to be working fine, but the SAD evaluation skips the entire file when one bad line is written in the SAD output. On the ASE+ corpus (ACLEW Starter + SOD), on 18 files it evaluates 14.
Maybe one solution could be to add a "post processing" of the rttm output to remove charaters like '(MSG)' and to delete non-sensical lines (like onset [1], or offset = -onset).

Actually the problem is worse than just some rare artifacts.
In the wrapper, if you remove the " | awk [...]", and look at what awk is parsing, you'll see that sometimes what awk receives is incorrect !
Here is an example (when running opensmile on a small test corpus) of what awk converts to rttm :
  (Start of segment received: 73.25   (End of segment received: 74.11
  (Start of segment received: 74.32   (End of segment received: 79.28
  (Start of segment received: 80.60   (End of segment received: 81.03
  (Start of segment received: 89.03   (Start of segment received: 91.35
  (End of segment received: 93.41   (Start of segment received: 95.81
  (End of segment received: 109.04   (Start of segment received: 111.60
  (End of segment received: 112.22   (Start of segment received: 114.25
  (End of segment received: 117.50   (Start of segment received: 120.05
  (End of segment received: 120.44   (Start of segment received: 121.15

For some reason, it skips one of the "End of segment", so up until the end both "start" and "end" are reversed. That output pipes to awk, and for each line, awk takes the first number as "onset" and the second minus the first as duration.
What this means is that in the output RTTM, sometimes the silences are labeled as speech, instead of the speech !

I just pushed a fix for that, by first writing the timestamps output from opensmile, and then parsing it and forcing the correct order between start/stop using awk.
@riebling could you double check to see if I didn't do any other mistakes (seems to be correct on the small corpus I tested it on)

Would it be possible to share with me some of the 'bad' OpenSmile output,
or a pointer to data that will produce it? It took me a while to follow the thread
to figure out that OpenSmile output is parsed by DiarTK, and then to find the
patched script in tools

Sorry, the issue is misleading, I'm actually refering to the way tools/opensmile.sh deals with the binary SMILExtract output.
The old version of opensmile.sh had this part (where the output of the binary is piped through several things ending in awk that converts it to RTTM):
	$OPENSMILE \
	-C $CONFIG_FILE \
	-I $file \
	-turndebug 1 \
	-logfile opensmile-vad.log 2>&1 | grep "of segment" | cut -d ' ' -f -7 | paste -sd ' \n' | awk -v FN=$id '{print "SPEAKER\t"FN"\t1\t"$5"\t"($10-$5)"\t<NA>\t<NA>\tspeech\t<NA>"}' > $audio_dir/opensmile_sad_$id.rttm

I found at least one example (I'll send you the file via slack) where, if you look at what enters in awk (i.e. by ending the line after the paste -sd '\n' ), you see that the timestamps are reversed (cf my second message).


Automorphisms of affine and projective space

We should write down what we know about those automorphism groups.

Here is an update: By now we expect that $\mathbb P^n$ has the classical automorphism group $\mathrm{PGL}_{n+1}$. David and proved this in for $n=1$, here is a sketch of my parallel, less direct proof attempt (which also works):
We can take a Möbius transformation to turn an automorphism $\mathbb P^1$ into a map fixing 0,1,$\infty$. Then it is an automorphism of $\mathbb A^1$ on each chart, given by polynomials of the form $P=X+\epsilon_2 X^2+\dots \epsilon_n X^n$ and $Q=Y+\delta_2 Y^2+\dots \delta_n Y^n$ (where all the numbers are nilpotent). By pushout-recursion for $\mathbb P^1$ and writing everything down carefully, we get the relation $P(X)\cdot Q(\frac{1}{X})=1$. This implies all the $\epsilon$s and $\delta$s are 0.
This does not directly generalize to all $n$, because we don't know that automorphisms preserve hyperplanes (we used that n=1, points are preserved).

The general case for automorphisms of $\mathbb P^n$ is written down in here


What's the best way to reuse code or define helper methods inside methods!macro?

If I define some_helper_method inside methods! macro and try to call it inside other method defined inside methods! macro I get these errors:
     some_helper_method();
   | ^^^^^^^^^^^^^^^^^^^^^^ expected 3 parameters
src/lib.rs:7:1: 109:3 note: in this expansion of methods! (defined in <ruru macros>)
   |
   = note: the following parameter types were expected: i32, *const ruru::AnyObject, SomeClass

So... What's the best way to declare some helper methods to reuse code?

methods! macro should be used to define only those methods which are exposed to Ruby (those ones which are used in def and def_self). You should move "helper functions" outside the methods! macro.
Long story short, Ruby methods and Rust functions are different and those functions which are declared inside methods! macro are transformed during compile-time to be compatible with MRI.
For example, printing some message to stdout from several Ruby methods:
fn print_message(message: &str) {
    println!("{}", message);
}

class!(Printer);

methods!(
    Printer,
    itself,

    fn print_hello() -> NilClass {
        print_message("Hello!");

        NilClass::new()
    }

    fn print_good_bye() -> NilClass {
        print_message("Good bye!");

        NilClass::new()
    }
}

fn main() {
    Class::new("Printer", None).define(|itself| {
        itself.def("print_hello", print_hello);
        itself.def("print_good_bye", print_good_bye);
    });
}

It may also be a good idea to treat Ruru methods as simple translators:

Use Ruru defined methods to unwrap and convert their arguments to Rust objects.
Pass arguments to outside methods that do all the work.
Convert Rust return value to Ruby.

Will help with reuse and allow you to adapt to future API changes.


Unable to use SAS Token to connect Premium Page Blob account to ASE

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.35.0
Regression From
No response
Architecture
x64
Storage Explorer Build Number
20240810.1
Platform
Windows
OS Version
No response
Bug Description
When trying to use Premium Page Blob account in ASE with SAS URL, authentication failure is received, even though having all the necessary permissions for the SAS token and use a storage account completely free of network configurations.
Steps to Reproduce

Create SAS Token in Portal with all permission:

Launch ASE and connect to Storage Account or service

Use Shared access signature URL (SAS)

The account will be connected but when trying to access it, it will fail.

Actual Experience
I would like to be able to use Premium Page Blob in ASE with SAS Token but I can't.
With account name and key I can access/connect the page account without problems and also with Premium Block Blob works with SAS Token only Premium Page Blob doesn't work.
Expected Experience
No response
Additional Context
This request is not authorized to perform this operation.
This storage account's 'Firewalls & virtual networks' settings may be blocking access to storage services. Try adding your client IP address to the firewall exceptions, or by allowing access from 'all networks' instead of 'selected networks'. To learn more about Azure Storage firewalls and virtual networks, visit http://go.microsoft.com/fwlink/?LinkId=845443.
Error Details:
{
"name": "RestError",
"code": "AuthenticationFailed",
"statusCode": 403,
"request": {
"streamResponseStatusCodes": {},
"url": "https://newpagestgguide.blob.core.windows.net/?sv=2022-11-02&ss=b&srt=sco&sp=rwdlaciyx&se=2024-10-04T16:25:05Z&st=2024-10-04T08:25:05Z&spr=https&sig=AzureSAS Token Redacted&comp=list&include=metadata",
"method": "GET",
"headers": {
"_headersMap": {
"x-ms-version": {
"name": "x-ms-version",
"value": "2023-01-03"
},
"accept": {
"name": "Accept",
"value": "application/xml"
},
"user-agent": {
"name": "User-Agent",
"value": "Microsoft Azure Storage Explorer/1.35.0 (win32) azsdk-js-storageblob/12.15.0 (NODE-VERSION v20.14.0; Windows_NT 10.0.26100)"
},
"x-ms-client-request-id": {
"name": "x-ms-client-request-id",
"value": "bbb8a9b4-2923-4b7b-85d6-171c37deea23"
}
}
},
"withCredentials": false,
"timeout": 0,
"keepAlive": true,
"decompressResponse": false,
"requestId": "bbb8a9b4-2923-4b7b-85d6-171c37deea23"
},
"response": {
"request": {
"streamResponseStatusCodes": {},
"url": "https://newpagestgguide.blob.core.windows.net/?sv=2022-11-02&ss=b&srt=sco&sp=rwdlaciyx&se=2024-10-04T16:25:05Z&st=2024-10-04T08:25:05Z&spr=https&sig=AzureSAS Token Redacted&comp=list&include=metadata",
"method": "GET",
"headers": {
"_headersMap": {
"x-ms-version": {
"name": "x-ms-version",
"value": "2023-01-03"
},
"accept": {
"name": "Accept",
"value": "application/xml"
},
"user-agent": {
"name": "User-Agent",
"value": "Microsoft Azure Storage Explorer/1.35.0 (win32) azsdk-js-storageblob/12.15.0 (NODE-VERSION v20.14.0; Windows_NT 10.0.26100)"
},
"x-ms-client-request-id": {
"name": "x-ms-client-request-id",
"value": "bbb8a9b4-2923-4b7b-85d6-171c37deea23"
}
}
},
"withCredentials": false,
"timeout": 0,
"keepAlive": true,
"decompressResponse": false,
"requestId": "bbb8a9b4-2923-4b7b-85d6-171c37deea23"
},
"status": 403,
"headers": {
"_headersMap": {
"content-length": {
"name": "content-length",
"value": "409"
},
"content-type": {
"name": "content-type",
"value": "application/xml"
},
"date": {
"name": "date",
"value": "Fri, 04 Oct 2024 08:25:55 GMT"
},
"server": {
"name": "server",
"value": "Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0"
},
"x-ms-client-request-id": {
"name": "x-ms-client-request-id",
"value": "bbb8a9b4-2923-4b7b-85d6-171c37deea23"
},
"x-ms-error-code": {
"name": "x-ms-error-code",
"value": "AuthenticationFailed"
},
"x-ms-request-id": {
"name": "x-ms-request-id",
"value": "8962abe8-501c-0033-7237-160747000000"
},
"x-ms-version": {
"name": "x-ms-version",
"value": "2023-01-03"
}
}
},
"bodyAsText": "\nAuthenticationFailedServer failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.\nRequestId:8962abe8-501c-0033-7237-160747000000\nTime:2024-10-04T08:25:55.8167608ZSignature fields not well formed.",
"parsedBody": {
"message": "Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.\nRequestId:8962abe8-501c-0033-7237-160747000000\nTime:2024-10-04T08:25:55.8167608Z",
"code": "AuthenticationFailed",
"AuthenticationErrorDetail": "Signature fields not well formed."
},
"parsedHeaders": {
"errorCode": "AuthenticationFailed",
"content-length": "409",
"content-type": "application/xml",
"date": "Fri, 04 Oct 2024 08:25:55 GMT",
"server": "Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0",
"x-ms-client-request-id": "bbb8a9b4-2923-4b7b-85d6-171c37deea23",
"x-ms-request-id": "8962abe8-501c-0033-7237-160747000000",
"x-ms-version": "2023-01-03"
}
},
"details": {
"errorCode": "AuthenticationFailed",
"content-length": "409",
"content-type": "application/xml",
"date": "Fri, 04 Oct 2024 08:25:55 GMT",
"server": "Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0",
"x-ms-client-request-id": "bbb8a9b4-2923-4b7b-85d6-171c37deea23",
"x-ms-request-id": "8962abe8-501c-0033-7237-160747000000",
"x-ms-version": "2023-01-03",
"message": "Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.\nRequestId:8962abe8-501c-0033-7237-160747000000\nTime:2024-10-04T08:25:55.8167608Z",
"code": "AuthenticationFailed",
"AuthenticationErrorDetail": "Signature fields not well formed."
}
}

@eliaquimbrandao Can you verify that the start and expiry times are reasonable? Can you try a SAS with an expiry time further in the future? Does a SAS generated from Storage Explorer work?

@eliaquimbrandao Can you verify that the start and expiry times are reasonable? Can you try a SAS with an expiry time further in the future? Does a SAS generated from Storage Explorer work?

The SAS I create was for 1 day and always a new SAS couples of time, I can try longs expire times (years) if necessary but don't think would change anything, but the issue is easy to be repro, I will try with a SAS from ASE and update.

@eliaquimbrandao

However, if I don't want to connect my entire subscription to ASE, I need to relay in Azure portal to create my SAS to connect, what only for Premium Page Blob account is not working.

I think you'll find it's the opposite. Azure Portal only lets you create storage account SAS, but Storage Explorer lets you create SAS for containers as well as accounts. You can right-click any storage account or container node in Storage Explorer and select "Generate Shared Access Signature".
The only major difference I can see is the SAS version (sv parameter) used. The Portal is using a much older version. Normally, that shouldn't matter much, but if the problem persists, I suggest opening an Azure service request. If a Storage Explorer SAS is working for you, I suggest continuing to use that.
Let us know if there's anything else, otherwise we can close this issue.

Hi @craxal ,
The Azure Portal offers the capability to create SAS tokens for containers; however, this is not directly relevant to the issue.
The question is: why does Azure Storage Explorer (ASE) not recognize a SAS token created in the Azure Portal for a Premium Page Blob account?
Other storage types utilize the same SAS token version and structure, and connections to ASE work as expected. Nevertheless, ASE rejects the connection only for that kind of account, which suggests the SAS token generated by the Portal is being rejected by the server.
Upon comparing the permissions set by the Portal and ASE, there are discrepancies: Portal [sp=rwdlaciyx] versus ASE [sp=rwdxftlacup]. Despite these differences in permission flags, I believe this is not a issue.
Could you provide insight into why ASE is rejecting a SAS token generated by the Azure Portal?

The error message says, "signature not well formed", which suggests the error was introduced in the creation of the SAS.
I think it's likely the permission differences could be the source of the problem. According to documentation for account SAS, rwdylacuptfi are the only valid permissions, so x shouldn't be in there. The order is also important, according to docs for service SAS. It would seem to me the permissions part of the Portal SAS is not well formed.
Here is, I think, the best way to determine if this is the case:

Confirm whether you have hierarchical namespaces enabled for your premium page blob account.
When creating SAS, match the exact same set of permissions in the Portal and in Storage Explorer. See which ones work.
Reduce the number of permissions in the Portal SAS until they start working in Storage Explorer.

All in all, however, I do believe it's time we take another look at our SAS code. I know for a fact we're missing y and i today, so Storage Explorer can't generate SAS with those permissions (that shouldn't affect whether it works in Storage Explorer).

The error message says, "signature not well formed", which suggests the error was introduced in the creation of the SAS.
I think it's likely the permission differences could be the source of the problem. According to documentation for account SAS, rwdylacuptfi are the only valid permissions, so x shouldn't be in there (I don't even know how you managed it with the Portal UI). The order (at least in the past) is also important, according to docs for service SAS. It would seem to me the permissions part of the Portal SAS is not well formed.
Here is, I think, the best way to determine if permissions is the problem:

Confirm whether you have hierarchical namespaces enabled for your premium page blob account.
When creating SAS, match the exact same set of permissions in the Portal and in Storage Explorer. See which ones work.
Reduce the number of permissions in the Portal SAS until they start working in Storage Explorer.

All in all, however, I do believe it's time we take another look at our SAS code. I know for a fact we're missing y and i today, so Storage Explorer can't generate SAS with those permissions (that shouldn't affect whether it works in Storage Explorer).

I ended up expressing myself wrong, but yes, it suggests the error was introduced in the creation of the SAS.
The "x" is being introduced in the portal by default for this option "Blob versioning permissions" when we access the SAS blade, but in fact it is not described in public articles. From ASE the "x" is introduce for "Delete Version".
ASE Permission

Portal Permission

However, even removing "x" when creating the SAS, ASE does not accept it and fails with the same error.
Responding how best to determine the permission issue:
1 - Confirm whether you have hierarchical namespaces enabled for your premium page blob account.
Hierarchical namespaces are not supported for Page Blob account, so this option is disabled by default.
2 - When creating SAS, match the exact same set of permissions in the Portal and in Storage Explorer. See which ones work.
Unfortunately, through the portal, the maximum I can generate would be "rwdlaciy" by removing "x", as the "update (u)" and "process (p)" options for Premium Page Blob account are blocked, they are only released when I have an account with Hierarchical namespace. But even with that permission "rwdlaciy" still not able to use it on the ASE.
3 - Reduce the number of permissions in the Portal SAS until they start working in Storage Explorer.
I did some tests and with these "rwdlac" permissions I can successfully use the SAS URL in ASE.

I did a test: I created a SAS through ASE with all permissions [rwdxftlacup] and tried to connect with SAS URL  in the ASE, and I also failed, Premium Page Blob account seems to not accept all permissions is clear, but we also do not have a description of which SAS and permissions should work for each type of account, but starting from a principle where more permissions everything would be possible, I believe that for SAS and some types of accounts this does not apply. :)

@eliaquimbrandao Have you been able to resolve your issue?

@craxal I would say that I have a mitigation, however, a SAS review from Portal or at least a article point the correct permission for Page Blob account would be great.

@eliaquimbrandao Can you elaborate? What sort of "review" are you referring to? There's not much we can do there, as this is for Storage Explorer issues. What permissions did you find that you needed, and do they differ from what Storage Explorer documentation specifies?


Amplify Console Host Web App flow not respecting the backend env name provided

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
NEW_APP
AWS Region
us-east-1
Amplify Hosting feature
Backend environments, Console, Deployments
Frontend framework
React
Next.js version
N/A
Next.js router
N/A
Describe the bug
Amplify console let's you provide the name for the new backend environment while hosting the web app. It used to create the backend env with provided name and link with the frontend for CI/CD fullstack deployment.
However, currently it is either using the name of branch when possible or randomly generates a name.
Expected behavior
Backend environment should be created with the name provided and that should get linked to the frontend
Reproduction steps

Fork this repo or setup any fullstack repo without amplify.yml file (so that default behaviour gets kicked in) in github (less likely to be provider dependent).
Open Amplify console => New App => Host Web App.
Select the repo, branch etc.
Select create backend environment option and provide the name which is different from branch name & complete steps.
Wait for deployment to finish.
Check the backend env name

Build Settings
=== Note: this is the auto generated version itself

version: 1
backend:
  phases:
    build:
      commands:
        - '# Execute Amplify CLI with the helper script'
        - amplifyPush --simple
frontend:
  phases:
    preBuild:
      commands:
        - yarn install
    build:
      commands:
        - yarn run build
  artifacts:
    baseDirectory: build
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

Log output

# Put your logs below this line
N/A

Additional information
Repo URL: https://github.com/gorbinphilip/react-amplify-sample
Recording: https://github.com/aws-amplify/amplify-hosting/assets/41995531/39b8e7f9-98fe-4169-af93-5d9519467396
Screenshot: https://github.com/aws-amplify/amplify-hosting/assets/41995531/bfe8b30f-7300-4020-a69e-2da2a4f49864

Feel free to skip if clock is ticking too fast.

At least this was working while amplifyPush helper script was around. Which I still continue using by manually adding to the existing deployments running cli v5.6 out of fear (keeping some magical commands in that script is scary as well, but boy do I have a choice).
Well, the reason for that is because amplify team decided to  remove that out of the blue and backend builds were no longer happening. So we had to hack (apologies for the bragging but that was really unprofessional). From docs, I see that now amplify hosting scans for the presence of amplifyPush command and automatically manages backend deployment for backward compatibility.
Now at present, while I'm scratching head exploring the options to migrate to latest cli and get rid of hacks, there comes this env name trouble. Now I am wondering what would be the effect of getting rid of the helper script from existing deployments and just put the magical word amplifyPush --simple. Well, who knows if amplify would randomly setup a new backend env :fearful: and  connect that with the frontend.
Some might ask, why not just try and see for yourself. Well, for my luck nodejs12.x is no longer supported by AWS lambda which is magically used by cli 5.6 for different categories and that prevents me from spawning new envs to play with. I'll give a shot with the new repo and update later on this one.

Hi @gorbinphilip 👋 , thanks for raising this issue and for sharing detailed reproduction steps.
I was able to reproduce this behavior and I am going to mark this as a bug. Additionally, you've correctly mentioned that the issue seems to be related to the console not setting the USER_BRANCH environment variable with the backend environment name that is passed during the app creation workflow.
The workaround for now is to manually set the USER_BRANCH environment variable to the backend environment name that is being used during the app creation workflow. Kindly refer to the attached screenshot:

Any update of this. Has the website been updated or must we still enter user branch as environment variable?

Fast forwarding to 2024, AWS amplify console has reached to a stage where it doesn't respect any of the build package overrides. Whatever you configure cli version, node version etc.. it just installs whatever it feels like. Currently with when requesting, node 18, amplify cli 12.11 with Amazon Linux 2023, console goes ahead and configures node 14, amplify 12.12.
https://discord.com/channels/705853757799399426/1239554630153670697/1239554630153670697
Have never used a service from AWS that's this unreliable. I do appreciate that most of the components are open source and iterated in fast pace, but that doesn't justify breaking core parts. Not to mention the fact the idea was to set a project up and running without head scratching too much about infra.
Apologies once again for the rant here because AWS doesn't have a provision to report or reach out without a paid developer plan. This probably has nothing do with open source side of amplify but just AWS

Yes, and I think the new design of the new amplify console is much less intuit. And still there is no button for manual build, you must enable CI and push a commit to build.
The new UI also duplicate global build settings as branch environments variables. So if after the first deployment and want change a global build environment variable, you must also change the variable for all build branch.

Are you still experiencing this issue?

I've used the workaround and not tried to deploy without it. If two
deployments/apps use the same backend then corruption will occur. I think
this was a major bug, and shocked that AWS amplify had not fixed it
tor. 27. juni 2024, 18:12 skrev Matt Auerbach @.***>:

Are you still experiencing this issue?
—
Reply to this email directly, view it on GitHub
https://github.com/aws-amplify/amplify-hosting/issues/3745#issuecomment-2195116394,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUXMIROB2IZARERS6HTSPNLZJQ2VLAVCNFSM6AAAAAA5V6JA4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJVGEYTMMZZGQ
.
You are receiving this because you commented.Message ID:
@.***>


Some more information about issue #57097(VS Code 1.26.1 recognizing 'htm' extension as opposed to 'html' extension for html docs)

I have the same problem with recognizing .html extension (VS Code does not recognize html, but recognizes .htm as .html), but in my situation the problem is with extension Django. I have VS Code 1.29.1. When Django is enabled - VS Code doesn't recognise .html extension(recognizes .hml as .html), when Django is disabled - everything works fine.

Well, if you follow Django's setup, it doesn't treat *.html files as html files:
"files.associations": {
    "**/templates/*.html": "django-html",
    "**/templates/*": "django-txt",
    "**/requirements{/**,*}.{txt,in}": "pip-requirements"
},

Open issues for that extension. Thanks.


MKSpinner has no propType for native prop MKSpinnner.scaleXof native type number

Getting this when trying to use it in android.

Seeing the same error too after upgrading react-native to 0.13.1.


Pubstwo 1253

@mbucknell - This is a first working draft which will probably need some UI and code refinement.  Also, no tests yet.  Just wanted to get a version out to get some initial feedback.

Looks good! Looks like you still need to implement the pagination and the Create button. Jim asked if rather than using the select-all, if we could implement the edit feature using another column which will contain the url for the publication's edit page. This would use the backbone UriCell, with some formatting customization. This allows the one click editing, rather than two.

@mbucknell - paginagation is working now. I'll be working on tests but let me know if you want me to merge this now.

@mamcderm-usgs , can you push up what you've done so far? I can take a look and then I would like to push it out. It will allow me to pick up the last pubs ticket for this sprint.

@mbucknell - I've pushed everything I have.

Looks good to merge. Don't worry about updating PublicationModel parse. I will need to merge your changes in with mine and I just notice a logic flaw.


Add Steven Chu to Contributors list

Thank you for creating this primer!! <3

@stevenchu You are welcome to join the community :)


Add Stylelint

Linked issue
none, part of initial setup

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


Ensure that notebooks can run in Binder out of the box

(Follow-up from discussion https://github.com/opendp/opendp/discussions/898)
The first cell of first-look-at-DP.ipynb failed for me on Binder because pandas is not installed. Should fix it by adding pandas to .binder/requirements.txt.
(... but smoke-test.yml seems like it should be testing notebooks with pytest --nbmake source/**/*.ipynb -n=auto, so maybe that test isn't working as intended?)
I'll try starting a PR, and will update here with what I learn.
Ideally, close when all notebooks work in Binder if cells are evaluated in order, and CI tests fail if this is not true.

New plan from https://github.com/opendp/opendp/pull/905#issuecomment-1667075429:

After thinking about it a bit, I think the ideal approach is to:

Don't show a binder link for versions 0.7 or below (their .binder/requirements are broken)
Don't show a binder link for nightly (the images take too long to build and constantly get rebuilt)
-    if you want a nightly build, you're better off setting things up locally
Adjust .binder/requirements to -r install the existing ../docs/requirements_notebooks.txt
-    because .binder is not the source of truth for notebook dependencies

At this point, all Binder links will disappear from the docs site, but when we cut 0.8 (sometime within the next week), stable and 0.8 will have links.

In addition, might add a note to emphasize that the test is not about the current state of the code, but to ensure that the documentation of released versions is consistent

#910 affects this:

Not done. Do we still want to do this?
Fixed the binder link on nightly instead.
Done.


Add ExecStop to integration guide

Fixes #362

LGTM - I had a comment about using NODENAME - but perhaps that should be a separate PR?


Project still maintained?

I see this project hasn't had any commits in several months, but had several PRs and issues opened that haven't had any comments on them. I'm wondering if this is still under active development or is being abandoned?

@brandongregoryscott @jeroenransijn could we get an update on this? If the project is dead it would be nice to know so we can start planning migrations or forks.

Looks dead to me ..

:(

No accordion more than a year after the feature request in #1539. Looks dead to me.

I believe he died :cry: , starting the migrations :rocket:

@DevJoaoLopes
What are you thinking migrating too ?

@iansummerlin Unfortunately, I don't see anyone paying much more attention to this project, there are other options on the market and it's not worth leaving a discontinued library in my projects. :disappointed:

@DevJoaoLopes what options are you considering?

@dandv https://mui.com/

For anybody in a similar boat to me/@DevJoaoLopes, I would like to pitch mantine or shad-cn.

ant design is very good, much better than mui imo

Sad to see that this is (seemingly?) abandoned. It was one of few UI libraries that got it exactly right - clean primitives to compose a UI without a bunch of tedious theming/config. Hopefully they are just rewriting it in TS and are too busy to reply here 😛

I'm not a contributor to this project or affiliated with Twilio/Segment.
However, I thought it may be worth mentioning that Twilio - which is the parent company of Segment - has undergone several rounds of layoffs over the last year.
I suspect those layoffs impacted some (or all) the maintainers of this project (possible they were laid off or at the very least? resources were allocated to other projects).
With that, I think starting a community-led fork or moving to another library are good ideas.


[Feature] Dynamic row height

Hello,
I had opened this feature request a long time ago in the original repo, but it never got implemented.
So I was hoping there is a chance of having it implemented it now with the new maintainers.
My original request was:

Is it possible to have dynamic row height?
Some of my rows use a renderer with a variable widget height.

Kind regards

Hi, @vixez
Could you please open it again on the current repo.
I will try to deploy it ASAP.

Hey @doonfrs,
There was no code written for it, it was only a request if the author could add this functionality.
But this was never implemented.

Hey @doonfrs, There was no code written for it, it was only a request if the author could add this functionality. But this was never implemented.

This is my approach:
double rowHeight = 75;
final _pageLimit = 25;
final columnHeight = 75;
final footerHeight = 75;

if (widget.fixedRowHeight != null) {
  // Row height is fixed
  rowHeight = widget.fixedRowHeight!;
} else {
  // Row height is calculated
  rowHeight = (((constraints.maxHeight) - (widget.columnHeight + widget.footerHeight)) / _pageLimit) - 1.2;

  rowHeight = rowHeight.clamp(40, 75);
}


API testing tab

Crazy idea. I'm posting this to gauge interest since it was suggested by API evangelist. Would anybody be interested in something like a "test tab"?

Code examples in this tab would be replaced by a swagger-like interface for submitting actual API requests and seeing their responses.

+1M... That would make me completely remove all the swagger UI installs... :+1:

+1

+1

This is probably the only reason I have doubts about using Slate :) Nobody seems to like Swagger UI.

+1 I agree with @oytuntez that this is the best thing about swagger and would be excellent in slate.
Is there any way to achieve this currently for a RESTful API that can be accessed with basic-auth and GET/POST requests?

+1

+1

+1

+1 this would be awesome.

I think that although there is demand for this, it'd best be implemented in some sort of extension or add-on to Slate, since it'd be difficult to cover all the cases in which it'd be needed or used, and I'd rather not have Slate become bloated from too many add-on features.


Issue213 gpcp

Fix for https://github.com/E3SM-Project/e3sm_diags/issues/213 for GPCP v2.3 post-processing problem

@chengzhuzhang, thanks for doing this. I'll look into this when I get back soon. In the meantime, you will (maybe?) eventually need to regenerate the obs data in a Python 3 env. Please see #215.

@zshaheen Yes, only a small portion of the scripts are python, so it shouldn't be too bad to convert (to python 3)

@chengzhuzhang, this looks good. Please merge whenever you want to.

Please see the results @chengzhuzhang collected here.


Refresh of notebook - MLOps stage 1 : data management: get started with Dataflow

This tutorial demonstrates how to use Vertex AI for E2E MLOps on Google Cloud in production. This tutorial covers stage 1 : data management: get started with Dataflow.

[x] Use the notebook template as a starting point.
[x] Follow the style and grammar rules outlined in the above notebook template.
[ ] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
[x] Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
[x] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
[x] This notebook has been added to the CODEOWNERS file under # Official Notebooks section, pointing to the author or the author's team.
[x] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

/gcbrun

This script has a dependence with another script (https://github.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/notebooks/community/ml_ops/stage1/get_started_bq_datasets.ipynb) in order to access sample BQ data

/gcbrun

Verified fix and added minor corrections

@manuelamunategui Looks like a pip install is needed. I think you will want to use the gcp version like this: pip install apache-beam[gcp].
----> 1 import apache_beam as beam

ModuleNotFoundError: No module named 'apache_beam'

/gcbrun

error log:
Step #3: === EXECUTION FINISHED ===
Step #3:
Step #3: Please debug the executed notebook by downloading: gs://cloud-build-notebooks-presubmit/executed_notebooks/PR_350/BUILD_de5f95df-b34e-43ef-a9c4-8b20a12923f2/get_started_dataflow.ipynb
Step #3:
Step #3: ======
Step #3:
Step #3:     execute_notebook_helper.execute_notebook(
Step #3:   File "/workspace/.cloud-build/execute_notebook_helper.py", line 91, in execute_notebook
Step #3:     raise execution_exception
Step #3:   File "/workspace/.cloud-build/execute_notebook_helper.py", line 56, in execute_notebook
Step #3:     pm.execute_notebook(
Step #3:   File "/builder/home/.local/lib/python3.9/site-packages/papermill/execute.py", line 122, in execute_notebook
Step #3:     raise_for_execution_errors(nb, output_path)
Step #3:   File "/builder/home/.local/lib/python3.9/site-packages/papermill/execute.py", line 234, in raise_for_execution_errors
Step #3:     raise error
Step #3: papermill.exceptions.PapermillExecutionError:
Step #3: ---------------------------------------------------------------------------
Step #3: Exception encountered at "In [13]":
Step #3: ---------------------------------------------------------------------------
Step #3: AttributeError                            Traceback (most recent call last)
Step #3: File /usr/local/lib/python3.9/site-packages/pkg_resources/init.py:3016, in DistInfoDistribution.dep_map(self)
Step #3:    3015 try:
Step #3: -> 3016     return self.__dep_map
Step #3:    3017 except AttributeError:
Step #3:
Step #3: File /usr/local/lib/python3.9/site-packages/pkg_resources/init.py:2813, in Distribution.getattr(self, attr)
Step #3:    2812 if attr.startswith(''):
Step #3: -> 2813     raise AttributeError(attr)
Step #3:    2814 return getattr(self._provider, attr)
Step #3:
Step #3: AttributeError: _DistInfoDistribution__dep_map
Step #3:
Step #3: During handling of the above exception, another exception occurred:
Step #3:
Step #3: AttributeError                            Traceback (most recent call last)
Step #3: File /usr/local/lib/python3.9/site-packages/pkg_resources/init.py:3007, in DistInfoDistribution._parsed_pkg_info(self)
Step #3:    3006 try:
Step #3: -> 3007     return self.pkg_info
Step #3:    3008 except AttributeError:
Step #3:
Step #3: File /usr/local/lib/python3.9/site-packages/pkg_resources/init.py:2813, in Distribution.getattr(self, attr)
Step #3:    2812 if attr.startswith(''):
Step #3: -> 2813     raise AttributeError(attr)
Step #3:    2814 return getattr(self._provider, attr)
Step #3:
Step #3: AttributeError: _pkg_info
Step #3:
Step #3: During handling of the above exception, another exception occurred:
Step #3:
Step #3: FileNotFoundError                         Traceback (most recent call last)
Step #3: Input In [13], in <cell line: 1>()
Step #3: ----> 1 import google.cloud.aiplatform as aip
Step #3:
Step #3: File ~/.local/lib/python3.9/site-packages/google/cloud/aiplatform/init.py:26, in
Step #3:      21 version = aiplatform_version.version
Step #3:      24 from google.cloud.aiplatform import initializer
Step #3: ---> 26 from google.cloud.aiplatform.datasets import (
Step #3:      27     ImageDataset,
Step #3:      28     TabularDataset,
Step #3:      29     TextDataset,
Step #3:      30     TimeSeriesDataset,
Step #3:      31     VideoDataset,
Step #3:      32 )
Step #3:      33 from google.cloud.aiplatform import explain
Step #3:      34 from google.cloud.aiplatform import gapic
Step #3:
Step #3: File ~/.local/lib/python3.9/site-packages/google/cloud/aiplatform/datasets/init.py:19, in
Step #3:       1 # -- coding: utf-8 --
Step #3:       2
Step #3:       3 # Copyright 2020 Google LLC
Step #3:    (...)
Step #3:      15 # limitations under the License.
Step #3:      16 #
Step #3:      18 from google.cloud.aiplatform.datasets.dataset import _Dataset
Step #3: ---> 19 from google.cloud.aiplatform.datasets.column_names_dataset import _ColumnNamesDataset
Step #3:      20 from google.cloud.aiplatform.datasets.tabular_dataset import TabularDataset
Step #3:      21 from google.cloud.aiplatform.datasets.time_series_dataset import TimeSeriesDataset
Step #3:
Step #3: File ~/.local/lib/python3.9/site-packages/google/cloud/aiplatform/datasets/column_names_dataset.py:24, in
Step #3:      21 from typing import List, Optional, Set
Step #3:      22 from google.auth import credentials as auth_credentials
Step #3: ---> 24 from google.cloud import bigquery
Step #3:      25 from google.cloud import storage
Step #3:      27 from google.cloud.aiplatform import utils
Step #3:
Step #3: File ~/.local/lib/python3.9/site-packages/google/cloud/bigquery/init.py:35, in
Step #3:      31 from google.cloud.bigquery import version as bigquery_version
Step #3:      33 version = bigquery_version.version
Step #3: ---> 35 from google.cloud.bigquery.client import Client
Step #3:      36 from google.cloud.bigquery.dataset import AccessEntry
Step #3:      37 from google.cloud.bigquery.dataset import Dataset
Step #3:
Step #3: File ~/.local/lib/python3.9/site-packages/google/cloud/bigquery/client.py:61, in
Step #3:      58 from google.cloud.client import ClientWithProject  # type: ignore  # pytype: disable=import-error
Step #3:      60 try:
Step #3: ---> 61     from google.cloud.bigquery_storage_v1.services.big_query_read.client import (
Step #3:      62         DEFAULT_CLIENT_INFO as DEFAULT_BQSTORAGE_CLIENT_INFO,
Step #3:      63     )
Step #3:      64 except ImportError:
Step #3:      65     DEFAULT_BQSTORAGE_CLIENT_INFO = None  # type: ignore
Step #3:
Step #3: File /usr/local/lib/python3.9/site-packages/google/cloud/bigquery_storage_v1/init.py:21, in
Step #3:      17 from future import absolute_import
Step #3:      19 import pkg_resources
Step #3: ---> 21 version = pkg_resources.get_distribution(
Step #3:      22     "google-cloud-bigquery-storage"
Step #3:      23 ).version  # noqa
Step #3:      25 from google.cloud.bigquery_storage_v1 import client
Step #3:      26 from google.cloud.bigquery_storage_v1 import types
Step #3:
Step #3: File /usr/local/lib/python3.9/site-packages/pkg_resources/init.py:466, in get_distribution(dist)
Step #3:     464     dist = Requirement.parse(dist)
Step #3:     465 if isinstance(dist, Requirement):
Step #3: --> 466     dist = get_provider(dist)
Step #3:     467 if not isinstance(dist, Distribution):
Step #3:     468     raise TypeError("Expected string, Requirement, or Distribution", dist)
Step #3:
Step #3: File /usr/local/lib/python3.9/site-packages/pkg_resources/init.py:342, in get_provider(moduleOrReq)
Step #3:     340 """Return an IResourceProvider for the named module or requirement"""
Step #3:     341 if isinstance(moduleOrReq, Requirement):
Step #3: --> 342     return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0]
Step #3:     343 try:
Step #3:     344     module = sys.modules[moduleOrReq]
Step #3:
Step #3: File /usr/local/lib/python3.9/site-packages/pkg_resources/init.py:886, in WorkingSet.require(self, *requirements)
Step #3:     877 def require(self, *requirements):
Step #3:     878     """Ensure that distributions matching requirements are activated
Step #3:     879
Step #3:     880     requirements must be a string or a (possibly-nested) sequence
Step #3:    (...)
Step #3:     884     included, even if they were already activated in this working set.
Step #3:     885     """
Step #3: --> 886     needed = self.resolve(parse_requirements(requirements))
Step #3:     888     for dist in needed:
Step #3:     889         self.add(dist)
Step #3:
Step #3: File /usr/local/lib/python3.9/site-packages/pkg_resources/init.py:780, in WorkingSet.resolve(self, requirements, env, installer, replace_conflicting, extras)
Step #3:     777     raise VersionConflict(dist, req).with_context(dependent_req)
Step #3:     779 # push the new requirements onto the stack
Step #3: --> 780 new_requirements = dist.requires(req.extras)[::-1]
Step #3:     781 requirements.extend(new_requirements)
Step #3:     783 # Register the new requirements needed by req
Step #3:
Step #3: File /usr/local/lib/python3.9/site-packages/pkg_resources/init.py:2734, in Distribution.requires(self, extras)
Step #3:    2732 def requires(self, extras=()):
Step #3:    2733     """List of Requirements needed for this distro if extras are used"""
Step #3: -> 2734     dm = self._dep_map
Step #3:    2735     deps = []
Step #3:    2736     deps.extend(dm.get(None, ()))
Step #3:
Step #3: File /usr/local/lib/python3.9/site-packages/pkg_resources/init.py:3018, in DistInfoDistribution._dep_map(self)
Step #3:    3016     return self.__dep_map
Step #3:    3017 except AttributeError:
Step #3: -> 3018     self.__dep_map = self._compute_dependencies()
Step #3:    3019     return self.__dep_map
Step #3:
Step #3: File /usr/local/lib/python3.9/site-packages/pkg_resources/init.py:3027, in DistInfoDistribution._compute_dependencies(self)
Step #3:    3025 reqs = []
Step #3:    3026 # Including any condition expressions
Step #3: -> 3027 for req in self._parsed_pkg_info.get_all('Requires-Dist') or []:
Step #3:    3028     reqs.extend(parse_requirements(req))
Step #3:    3030 def reqs_for_extra(extra):
Step #3:
Step #3: File /usr/local/lib/python3.9/site-packages/pkg_resources/init.py:3009, in DistInfoDistribution._parsed_pkg_info(self)
Step #3:    3007     return self._pkg_info
Step #3:    3008 except AttributeError:
Step #3: -> 3009     metadata = self.get_metadata(self.PKG_INFO)
Step #3:    3010     self._pkg_info = email.parser.Parser().parsestr(metadata)
Step #3:    3011     return self._pkg_info
Step #3:
Step #3: File /usr/local/lib/python3.9/site-packages/pkg_resources/init.py:1407, in NullProvider.get_metadata(self, name)
Step #3:    1405     return ""
Step #3:    1406 path = self._get_metadata_path(name)
Step #3: -> 1407 value = self._get(path)
Step #3:    1408 try:
Step #3:    1409     return value.decode('utf-8')
Step #3:
Step #3: File /usr/local/lib/python3.9/site-packages/pkg_resources/init.py:1611, in DefaultProvider._get(self, path)
Step #3:    1610 def _get(self, path):
Step #3: -> 1611     with open(path, 'rb') as stream:
Step #3:    1612         return stream.read()
Step #3:
Step #3: FileNotFoundError: [Errno 2] No such file or directory: '/builder/home/.local/lib/python3.9/site-packages/google_api_core-2.7.1.dist-info/METADATA'
Step #3:
Finished Step #3
ERROR

/gcbrun

/gcbrun

Step #3: File ~/.local/lib/python3.9/site-packages/pkg_resources/init.py:1622, in DefaultProvider._get(self, path)
Step #3:    1621 def _get(self, path):
Step #3: -> 1622     with open(path, 'rb') as stream:
Step #3:    1623         return stream.read()
Step #3:
Step #3: FileNotFoundError: [Errno 2] No such file or directory: '/builder/home/.local/lib/python3.9/site-packages/google_api_core-2.7.1.dist-info/METADATA'
Step #3:
Finished Step #3
ERROR
ERROR: build step 3 "gcr.io/cloud-devrel-public-resources/python-samples-testing-docker:latest" failed: step exited with non-zero status: 1

Notebook note compatible with Python 3.9 ( tensorflow-data-validation and tensorflow-transform)

/gcbrun

Close this PR as the code has changed and due to incompatibility with Python 3.9


No aarch64 wheel or source distro

Hi,
I'm trying to install ydf on raspberry pi, but cannot find new version compatible

Hi, thank you for reporting - that's true, I'll see if there's a simple way of us to provide these wheels.

We're not ready to provide wheels yet, but I can confirm that compiling for aarch64 is possible. I've added installation instructions to INSTALLATION.md and provided scripts to make it easier. We're working on updating our infra to provide wheels as well.


clusterrole does not have permission to access resources?

k8s version: v1.17.4
kube-prometheus version: v0.3
I’m a bit surprised, kube-state-metrics clusterRole already has permission, why the request is forbidden.
In addition, I am curious, why kube-prometheus needs to install another kube-rbac-proxy container

#kube-system  kube-state-metrics
E1226 05:37:23.125175       1 reflector.go:127] k8s.io/kube-state-metrics/internal/store/builder.go:358: Failed to watch *v1.Lease: failed to list *v1.Lease: leases.coordination.k8s.io is forbidden: User "system:serviceaccount:kube-system:kube-state-metrics" cannot list resource "leases" in API group "coordination.k8s.io" in the namespace "kube-node-lease"
E1226 05:37:28.123076       1 reflector.go:127] k8s.io/kube-state-metrics/internal/store/builder.go:358: Failed to watch *v1.Ingress: failed to list *v1.Ingress: ingresses.networking.k8s.io is forbidden: User "system:serviceaccount:kube-system:kube-state-metrics" cannot list resource "ingresses" in API group "networking.k8s.io" at the cluster scope

#monitoring  kube-state-metrics
E1226 05:49:13.679522       1 reflector.go:127] k8s.io/kube-state-metrics/internal/store/builder.go:358: Failed to watch *v1.Lease: failed to list *v1.Lease: leases.coordination.k8s.io is forbidden: User "system:serviceaccount:kube-system:kube-state-metrics" cannot list resource "leases" in API group "coordination.k8s.io" in the namespace "kube-node-lease"
E1226 05:49:30.179468       1 reflector.go:127] k8s.io/kube-state-metrics/internal/store/builder.go:358: Failed to watch *v1.Ingress: failed to list *v1.Ingress: ingresses.networking.k8s.io is forbidden: User "system:serviceaccount:kube-system:kube-state-metrics" cannot list resource "ingresses" in API group "networking.k8s.io" at the cluster scope

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  labels:
    app.kubernetes.io/name: kube-state-metrics
    app.kubernetes.io/version: 2.0.0-beta
  name: kube-state-metrics
rules:
- apiGroups:
  - ""
  resources:
  - configmaps
  - secrets
  - nodes
  - pods
  - services
  - resourcequotas
  - replicationcontrollers
  - limitranges
  - persistentvolumeclaims
  - persistentvolumes
  - namespaces
  - endpoints
  verbs:
  - list
  - watch
- apiGroups:
  - extensions
  resources:
  - daemonsets
  - deployments
  - replicasets
  verbs:
  - list
  - watch
- apiGroups:
  - apps
  resources:
  - statefulsets
  - daemonsets
  - deployments
  - replicasets
  verbs:
  - list
  - watch
- apiGroups:
  - batch
  resources:
  - cronjobs
  - jobs
  verbs:
  - list
  - watch
- apiGroups:
  - autoscaling
  resources:
  - horizontalpodautoscalers
  verbs:
  - list
  - watch
- apiGroups:
  - authentication.k8s.io
  resources:
  - tokenreviews
  verbs:
  - create
- apiGroups:
  - authorization.k8s.io
  resources:
  - subjectaccessreviews
  verbs:
  - create
- apiGroups:
  - policy
  resources:
  - poddisruptionbudgets
  verbs:
  - list
  - watch
- apiGroups:
  - certificates.k8s.io
  resources:
  - certificatesigningrequests
  verbs:
  - list
  - watch
- apiGroups:
  - storage.k8s.io
  resources:
  - storageclasses
  - volumeattachments
  verbs:
  - list
  - watch
- apiGroups:
  - admissionregistration.k8s.io
  resources:
  - mutatingwebhookconfigurations
  - validatingwebhookconfigurations
  verbs:
  - list
  - watch
- apiGroups:
  - networking.k8s.io
  resources:
  - networkpolicies
  - ingresses
  verbs:
  - list
  - watch
- apiGroups:
  - coordination.k8s.io
  resources:
  - leases
  verbs:
  - list
  - watch

I found that kube-prometheus carries kube-state-metrics, but my cluster has installed kube-state-metrics, and the role permissions of the two conflicts. I deleted kube-state-metrics in the cluster and it worked.


After hours of searching to no avail, I have found that you need to:

  After hours of searching to no avail, I have found that you need to:

do sudo su  (all the commands need to be performed by root user)  ;
delete the symlink in /tmp/.X11-unix  ( just do rm /tmp/.X11-unix) ;
run vncserver (It will now be able to create the server) ;
Run kex and everything should work.

Originally posted by @afonsofrancof in https://github.com/microsoft/WSL/discussions/6675#discussioncomment-1007781

I'm still not able to delete any files or nine of the commands u mentioned worked on me

kindly help with this


Ispn 6405 8.2.x

https://issues.jboss.org/browse/ISPN-6405
https://issues.jboss.org/browse/ISPN-6071

Pushed, thanks


[FR] Setuptools equivalent to distutils.command.build.build

What's the problem this feature will solve?
Before distutils was scheduled for removal, distutils.command.build.build used to be an ideal place to add custom build steps. The pattern usually looks something like this:
from distutils.command.build import build

class CustomBuild(build):
    def run(self):
        some_custom_compile_step()
        super().run()

setup(
    ...,
    cmdclass = {
        "build": CustomBuild,
    },
)

Typically, the custom behaviour can be put in a custom setuptools.Command but in order for that command to be ran automatically by pip wheel . or when installing from an sdist, the build command still needs to be monkeypatched
Describe the solution you'd like
I want some place in the setup process where I can prepend arbitrary build steps to be ran when building wheels or installing from sdists or git. In my case, I want to use this to invoke a C compile using a custom build system. Currently, when distutils disappears, I have no way for the platforms that can't use precompiled wheels to be able to install directly from an sdist on PyPI.
Alternative Solutions
I see that I can accomplish the same thing by overriding build_py instead. This feels like a hack though.
Perhaps a better solution would be the ability to mark custom commands as necessary prerequisite commands to the install or build commands. Setuptool's aliases feature looks tantalisingly close - using the following setup.cfg configuration I can replace build with a custom step + the original build.
[aliases]
build = custom_step build

This does indeed correctly override python setup.py build but does not apply when other commands invoke build so that pip install . or installing from an sdist still calls the original, non-extended build. So either making the above config apply to implicitly called commands or adding some kind of [command-requires] build = custom_step option do the job.
Additional context
No response
Code of Conduct

[X] I agree to follow the PSF Code of Conduct

For now, you can continue to rely on distutils. Even as it goes away from the standard library, Setuptools is adopting it such that if you run with SETUPTOOLS_USE_DISTUTILS=local then import distutils resolves to Setuptools' bundled copy.
But I agree, long-term, there should be a better way to introduce build steps, which is captured in #2591.


Measure validation

Measure evaluation in the CQL Evaluator generally requires measure to conform to the CQF measures profile. Add validation for measure resources and report to use any validation errors.

In particular, we need to ensure that SDEs, Groups, and Stratifiers need Ids.

Resolved by #189


refactor(wc): use clap instead of getopts

I am planning to land this Thursday 5st if no objection!


[refmt] Incorrect indentation when right side of pipe operator (|>) is multi-line

Input:
m
|> StringMap.add("a", 1)
|> StringMap.fold_right(
  (el, m) => StringMap.add(el, 1, m),
  ["someReallyLongString"]
)
|> StringMap.add("h", 1);

Desired output:
m
|> StringMap.add("a", 1)
|> StringMap.fold_right(
    (el, m) => StringMap.add(el, 1, m),
    ["someReallyLongString"]
  )
|> StringMap.add("h", 1);

Actual output:
m
|> StringMap.add("a", 1)
|> StringMap.fold_right(
     (el, m) => StringMap.add(el, 1, m),
     ["someReallyLongString"]
   )
|> StringMap.add("h", 1);

It's bad that the indented lines are not tab-aligned. They have 5, 5, and 3 spaces in front.
Slightly relevant prettier example: https://goo.gl/6eXRLn
(Edit: No longer relevant comment) Less confident in the desired output because now the closing paren aligns with the |> operator. However prettier does support the JavaScript pipeline proposal and does alignment more similar to the desired output above: https://goo.gl/vvfTfb

This one has me torn - I don't like the paren being aligned to the |>, but I don't like when things aren't tab aligned.

@jordwalke I updated the desired output. I think matching the way ternaries break across lines in prettier is similar enough and more desirable. This just means we need to tab align the lines that get indented, but still always increase the indentation at least one level past the pipe operator.

Yeah, that looks better.


Feature Request : Support "force" as a flag to the Airflow Clear Command

I'm building automation around the airflow CLI and would like to clear a DAG for a set of dates. I'd like to call it and just force without needing to programmatically sending "yes" to stdin.
It would be nice to have an optional --force or -c (coerce) flag to just clear state. '-f' is already taken to mean run only failed tasks.

I recall seeing that this was implemented somewhere and I was about to close this but I can't find the pull request.

airflow clear --no_confirm


Serial.print does not work in "Factory" example

Help/advice needed
I am using the T-RGB example "factory" (this app which is commonly installed on a T-RGB at supply), as a framework for creating a new app, but the "Serial.print" debug function does not work, even if "Serial.begin(115200)" is declared in the beginning of "void setup()". normally. This is not an installation fault, as the Serial.print function works with other apps on the same device. Any help is highly appreciated.

CDC must turn on

Hello Lewis,
many thanks, problem solved!
BR,
Thomas


Add logs to inspect error bug from #18

This is for issue #18

Actually, there is no need to merge this. After the investigation is done this would be rolled back.


improvement Avoid reading from left child while hash table is empty(right join)

… empty(right join)
Proposed changes
When the right (build) side is empty in a right outer join, there is no need to read data from the left child.
Problem summary
Describe your changes.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

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

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 33.61 seconds
stream load tsv:          455 seconds loaded<PHONE_NUMBER>9 Bytes, about 156 MB/s
stream load json:         41 seconds loaded<PHONE_NUMBER> Bytes, about 54 MB/s
stream load orc:          73 seconds loaded<PHONE_NUMBER> Bytes, about 14 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230310090208_clickbench_pr_112161.html


Colon In Http route constraint causes failure

Repro:

create an http function with a custom route test/{dt:datetime}
attempt to send a valid url including colons in the datetime value (e.g.http://host/api/test/2017-08-18 20:06:30 ) it will cause a host failure

The same URL will work in ASP.NET, so it looks like something we're doing wrong.

This can be reproed locally using the local host. Use of a colon in the URL results in an error "A potentially dangerous Request.Path value was detected from the client (:).".

I believe this is due to ASP.NET request validation. My understanding is that this validation has changed in .NET core so it will be resolved in the .NET core version of functions.


Protein in explicit water solvent box simulation with torchMD

Is is possible to run MD simulation a large protein (AA>300) in explicit water solvent with torchMD?
Thank you!

in theory yes, in practice it is too slow for that.
You should use ACEMD for fast calculations.
Any reason to use TorchMD?
On Wed, Jun 28, 2023 at 8:12 AM Byun-jinyoung @.***>
wrote:

Is is possible to run MD simulation a large protein (AA>300) in explicit
water solvent with torchMD?
Thank you!
—
Reply to this email directly, view it on GitHub
https://github.com/torchmd/torchmd/issues/48, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB3KUOV7FKABAUVFHPLP6XLXNPDMZANCNFSM6AAAAAAZWRKXAE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I want to run MD simulation by using TorchMD. and later I'd like to add custom NN potential during MD simulation

you can add an external potential using ACEMD as well. We can help in you
find issues to include torchmd-net into it.
The only reason to use TorchMD if you need to play with the MM part of it.
On Wed, Jun 28, 2023 at 9:19 AM Byun-jinyoung @.***>
wrote:

I want to run MD simulation by using TorchMD. and later I'd like to add
custom NN potential during MD simulation
—
Reply to this email directly, view it on GitHub
https://github.com/torchmd/torchmd/issues/48#issuecomment-1610899207,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB3KUOVE22QPXIIL4RV3UBTXNPLI5ANCNFSM6AAAAAAZWRKXAE
.
You are receiving this because you commented.Message ID:
@.***>

Is it better to upload this issue in torchMD-net GitHub repository?
I'd like to simulation protein in explicit solvent with MD + deep learning approach (e.g. roughly such as OpenMM + openmm-pytorch although I've never used openmm-pytorch...)

It's not really an issue yet. Just try with OpenMM or ACEMD and then post
depending of the problems
On Thu, Jun 29, 2023 at 8:43 AM Byun-jinyoung @.***>
wrote:

Is it better to upload this issue in torchMD-net GitHub repository?
I'd like to simulation protein in explicit solvent with MD + deep learning
approach (e.g. roughly such as OpenMM + openmm-pytorch although I've never
used openmm-pytorch...)
—
Reply to this email directly, view it on GitHub
https://github.com/torchmd/torchmd/issues/48#issuecomment-1612507634,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB3KUOTMS36BDJYFJLMKHJLXNUP2DANCNFSM6AAAAAAZWRKXAE
.
You are receiving this because you commented.Message ID:
@.***>

Okay!


feat: add retry API for archived workflows. Fixes #7906

Signed-off-by: Dillen Padhiar<EMAIL_ADDRESS>Fixes #7906
Previously workflows were only able to be retried if they existed in the cluster. If a workflow is GC-ed immediately after completion, you must save the workflow manually as a plain YAML or into workflow archive, then kubectl create before using argo retry. This API allows for archived workflows to be created and retried removing the need for this otherwise hacky method.

@sarabala1979

What happens if you move the Update/Create to the service level?

Functionality is the same if we move the update/create calls to the service level. We can remove the RetryArchiveWorkflow function altogether since RetryWorkflow will only just prepare a workflow for retry and the server will either update or create.

I think that's the right thing to do. The current util finc combines two responsibilies:

Preparing the workflow for retry.
Persisting the workflow.

It if only does the first, the second responsibly can be moved to the service layer.
https://en.wikipedia.org/wiki/Single-responsibility_principle

Great work! I’ll review this soon as well since I originally proposed/requested this feature in https://github.com/argoproj/argo-workflows/issues/5405.

LGTM. Do you also plan to add UI support for this?

Yes the plan is to next implement the Resubmit API then CLI and UI for both.


Update Schema from OCPP 2.0.1

Apparently JSON Schemas from last realease OCPP 2.0.1 are not yet updated

What do you mean exactly? Which version of the schemas do you think we should be used?

Last version of OCPP 2.0.1 has been published in mars 2020 (and replace OCPP 2.0) having modification to json schemas.
See:
https://www.openchargealliance.org/downloads/

We just added support for OCPP 2.0.1, I believe that uses the correct schemas. Can you confirm that?

Yes, I did not have that in local repo. Sorry.

Closed due to question answered