Error while importing "wbindgen_placeholder"."__wbindgen_describe": unknown import. Expected Function(FunctionType { params: [I32], results: [] })

Describe the Bug
I am creating a SWC plugin for next js.
I recently started getting an error when running the plugin.
Now this error does not go away. Any recompiled plugin breaks the application. The same plugin compiled a few days ago works.
I reinstalled: cargo, rust, swc_core.
The error text brought me here. What does this error mean? Please help me understand.
In SWC they told me - check if all versions are latest. YES, but that's where their help ended.
Steps to Reproduce
I am completely following the instructions:
https://swc.rs/docs/plugin/ecmascript/getting-started
Run next js and I get an error.
The same plugin that I compiled a few days ago works in the latest version of Next js.
But everything I compile now breaks the application
Expected Behavior
The application must not break
Actual Behavior
thread '<unnamed>' panicked at 'failed to invoke plugin: failed to invoke plugin on 'Some("C:\\Users\\79833\\WebstormProjects\\TestSWC\\nextnew\\node_modules\\next
\\dist\\client\\dev\\amp-dev.js")'

Caused by:
    Error while importing "__wbindgen_placeholder__"."__wbindgen_describe": unknown import. Expected Function(FunctionType { params: [I32], results: [] })', C:\Use
rs\runneradmin\.cargo\registry\src\index.crates.io-6f17d22bba15001f\swc-0.260.41\src\plugin.rs:219:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread '<unnamed>' panicked at 'failed to invoke plugin: failed to invoke plugin on 'Some("C:\\Users\\79833\\WebstormProjects\\TestSWC\\nextnew\\node_modules\\next
\\dist\\client\\next-dev.js")'

Caused by:
    Error while importing "__wbindgen_placeholder__"."__wbindgen_describe": unknown import. Expected Function(FunctionType { params: [I32], results: [] })', C:\Use
rs\runneradmin\.cargo\registry\src\index.crates.io-6f17d22bba15001f\swc-0.260.41\src\plugin.rs:219:14
thread '<unnamed>' panicked at 'failed to invoke plugin: failed to invoke plugin on 'Some("C:\\Users\\79833\\WebstormProjects\\TestSWC\\nextnew\\node_modules\\next
\\dist\\client\\router.js")'

Caused by:
    Error while importing "__wbindgen_placeholder__"."__wbindgen_describe": unknown import. Expected Function(FunctionType { params: [I32], results: [] })', C:\Use
rs\runneradmin\.cargo\registry\src\index.crates.io-6f17d22bba15001f\swc-0.260.41\src\plugin.rs:219:14
thread '<unnamed>' panicked at 'failed to invoke plugin: failed to invoke plugin on 'Some("C:\\Users\\79833\\WebstormProjects\\TestSWC\\nextnew\\node_modules\\next
\\dist\\client\\app-next-dev.js")'

Caused by:
    Error while importing "__wbindgen_placeholder__"."__wbindgen_describe": unknown import. Expected Function(FunctionType { params: [I32], results: [] })', C:\Use
rs\runneradmin\.cargo\registry\src\index.crates.io-6f17d22bba15001f\swc-0.260.41\src\plugin.rs:219:14
thread '<unnamed>' panicked at 'failed to invoke plugin: failed to invoke plugin on 'Some("C:\\Users\\79833\\WebstormProjects\\TestSWC\\nextnew\\node_modules\\next
\\dist\\pages\\_app.js")'

Additional Context
I don't add anything other than the SWC starter kit. This is definitely not my fault.
I reinstalled everything except windows. I am ready to test any theory to solve the problem, and provide any information. Answer, please. I need any advice

SWC uses tracing for logging. By default, SWC testing library configures the log level to debug by default, and this can be controlled by using an environment variable named RUST_LOG.

Could you try setting RUST_LOG=trace and see if there's anything else in the logs?

SWC uses tracing for logging. By default, SWC testing library configures the log level to debug by default, and this can be controlled by using an environment variable named RUST_LOG.

Could you try setting RUST_LOG=trace and see if there's anything else in the logs?
i setting - RUST_BACKTRACE=1, RUST_LOG=trace, SWC_DEBUG=1

Panic: PanicInfo { payload: Any { .. }, message: Some(failed to invoke plugin: failed to invoke plugin on 'Some("C:\\Users\\79833\\WebstormProjects\\TestSWC\\nextn
ew\\node_modules\\next\\dist\\client\\app-next-dev.js")'

Caused by:
    Error while importing "__wbindgen_placeholder__"."__wbindgen_describe": unknown import. Expected Function(FunctionType { params: [I32], results: [] })

Stack backtrace:
   0: napi_register_module_v1
   1: napi_register_module_v1
   2: napi_register_module_v1
   3: napi_register_module_v1
   4: napi_register_module_v1
   5: napi_register_module_v1
   6: napi_register_module_v1
   7: BrotliDecoderVersion
   8: BrotliDecoderVersion
   9: canonical_abi_free
  10: canonical_abi_free
  11: canonical_abi_free
  12: canonical_abi_free
  13: canonical_abi_free
  14: canonical_abi_free
  15: canonical_abi_free
  16: v8::base::TimeDelta::TimeDelta
  17: uv_queue_work
  18: uv_poll_stop
  19: inflateValidate
  20: BaseThreadInitThunk
  21: RtlUserThreadStart), location: Location { file: "C:\\Users\\runneradmin\\.cargo\\registry\\src\\index.crates.io-6f17d22bba15001f\\swc-0.260.41\\src\\plugin.r
s", line: 219, col: 14 }, can_unwind: true }
Backtrace:    0: napi_register_module_v1
   1: napi_register_module_v1
   2: canonical_abi_free
   3: napi_register_module_v1
   4: napi_register_module_v1
   5: napi_register_module_v1
   6: napi_register_module_v1
   7: napi_register_module_v1
   8: napi_register_module_v1
   9: BrotliDecoderVersion
  10: canonical_abi_free
  11: canonical_abi_free
  12: canonical_abi_free
  13: canonical_abi_free
  14: canonical_abi_free
  15: canonical_abi_free
  16: canonical_abi_free
  17: v8::base::TimeDelta::TimeDelta
  18: uv_queue_work
  19: uv_poll_stop
  20: inflateValidate
  21: BaseThreadInitThunk
  22: RtlUserThreadStart

This error is printed to the console many times

I'm not sure this is the place to ask this, probably better to figure it out in SWC, if it is a bug in wasm-bindgen a more minimal example, that doesn't involve tools outside wasm-bindgen, would be really helpful.

I'm not sure this is the place to ask this, probably better to figure it out in SWC, if it is a bug in wasm-bindgen a more minimal example, that doesn't involve tools outside wasm-bindgen, would be really helpful.

I asked this question to the SWC developers. Unfortunately they don't answer.
Why is this problem possible? I found a discussion thread with the same problem. In that case, another version of rust nightly helped. https://github.com/swc-project/swc/discussions/6883
I have tried this version and many others. And I will try all versions of rust. I have no other ideas :(

Looking at https://github.com/swc-project/swc/discussions/6883, the problem is more clear now. The latest release seems to have broken WASI support, which is not actually officially supported by wasm-bindgen.
I encourage you to bring your use-case and point of view to #3421.


Can't create an AudioFrame from_ndarray

Hello,
I'm trying to generate silence in wav format:
silence = np.zeros((2, 1152))
frame = av.AudioFrame.from_ndarray(silence)

But it crashes with:
File "av/audio/frame.pyx", line 120, in av.audio.frame.AudioFrame.from_ndarray
AssertionError

There are a number of asserts in there that ought to be more descriptive.
In the meantime, I'd advise that you specify an audio format (it defaults to s16) and numpy dtype, e.g.:
>>> silence = np.zeros((2, 1152), dtype='int16')
>>> frame = av.AudioFrame.from_ndarray(silence, 's16p')

Thanks for the answer! that was it.
I now seem to have succesfully encoded the frame via out_pack = out_stream.encode(frame) but just discovered that doing that in a loop fails on the second iteration, so I probably lack some background here, why can't I just generate and encode an AudioFrame like so?
        for _ in range(10):
            frame = av.AudioFrame.from_ndarray(silence, 's16p')
            frame.pts = None
            out_pack = out_stream.encode(frame)
            if out_pack:
                out_container.mux(out_pack)
            else:
                break   # It does break on second iteration

Thanks again for your time

If you want to generate silence, you don't even need to use numpy at all.
import av

with av.open('test.wav', 'w') as out_container:
    out_stream = out_container.add_stream('pcm_s16le')

    for _ in range(100):
        frame = av.AudioFrame(samples=1152)
        frame.pts = None
        frame.rate = 48000
        for packet in out_stream.encode(frame):
            out_container.mux(packet)

    for packet in out_stream.encode(None):
        out_container.mux(packet)

This isn't helpful at all. I'm pretty sure that the silence is created only for simplicity purpose and the actual goal is to be able to use it with some real audio data.
The answer, while technically true, doesn't help to figure out the cause of the issues with numpy usage.

Hello everyone, I also faced this problem. Did someone manage to fill in the data array correctly with real sound? share your experience please.

        frame = av.AudioFrame.from_ndarray(audio_chunk, layout='mono', format='s16p')
        frame.sample_rate = ori_sr


Investigate using cloud run module

Cloud run module maybe more succinct to use as we can bundle in the service and iam
module "cloud_run" {
  source  = "GoogleCloudPlatform/cloud-run/google"
  version = "~> 0.3.0"

  service_name           = "cloudrun-srv"
  project_id             = var.projct_id
  location               = var.region
  service_labels         = var.labels
  image                  = "gcr.io/cloudrun/hello"
  members                = "allUsers"
}

which can replace
https://github.com/GoogleCloudPlatform/terraform-google-log-analysis/blob/2dc9c004c779c4c744cd8a8276b812ac620e1aca/main.tf#L64-L99

Replaced the block with Cloud Run module as suggested.


为什么识别不了vert.x 项目？

English only in the community of an Apache project.
Just because the logo for vert.x did not show up? I think it does no harm as long as you got the correct traces, and if you really care, you can open a pull request to add the logo in the UI repo https://github.com/apache/skywalking-rocketbot-ui/tree/master/src/views/components/topology/assets

只在Apache项目社区中使用英语。
只是因为vert.x的徽标没有出现？我认为只要你得到正确的痕迹就没有坏处，如果你真的在乎，你可以打开一个拉取请求，在UI回购中添加徽标https://github.com/apache/skywalking-rocketbot-ui /树/主/ src目录/视图/组件/拓扑/资产

Not just not identifying it,
Why is there no trace of gateway to vert.x?

English only in the community of an Apache project.
Just because the logo for vert.x did not show up? I think it does no harm as long as you got the correct traces, and if you really care, you can open a pull request to add the logo in the UI repo https://github.com/apache/skywalking-rocketbot-ui/tree/master/src/views/components/topology/assets

Not just not identifying it,
Why is there no trace of gateway to vert.x?

As long as you're not using Vert.x with RxJava, https://github.com/apache/skywalking/pull/4840 will likely solve this issue.


drop fps

Once i start loading Xivalexander, my game fps drops from 100 to 30, the only thing i was running is Act and Dolphin vpn https://www.htjsq.com/

Can you post your config.runtime.json?

"E:\Steam\steamapps\common\FINAL FANTASY XIV Online\game\ffxiv_dx11.exe": {
"": false,
"AdditionalGameResourceFileEntryRootDirectories": [],
"AdditionalSqpackRootDirectories": [],
"AdditionalTexToolsModPackSearchDirectories": [],
"AlwaysOnTop_GameMainWindow": false,
"AlwaysOnTop_XivAlexLogWindow": false,
"AlwaysOnTop_XivAlexMainWindow": true,
"ChainLoadPath_d3d11": [],
"ChainLoadPath_d3d9": [],
"ChainLoadPath_dinput8": [],
"ChainLoadPath_dxgi": [],
"CheckForUpdatedOpcodesOnStartup": true,
"CompressModdedFiles": false,
"CompressModsWheneverPossible": true,
"ExcelTransformConfigFiles": [],
"ExpectedAnimationLockDurationUs": 75000,
"FallbackLanguagePriority": [],
"HideOnMinimize_XivAlexMainWindow": false,
"HighLatencyMitigationMode": "SimulateNormalizedRttAndLatency",
"Language": "SystemDefault",
"LockFramerate": 0,
"LockFramerateAutomatic": false,
"LockFramerateGlobalCooldown": 250,
"LockFramerateMaximumRenderIntervalDeviation": 100,
"LockFramerateTargetFramerateRangeFrom": 50.0,
"LockFramerateTargetFramerateRangeTo": 60.0,
"LogAllDataFileRead": false,
"MaximumAnimationLockDurationUs": 150000,
"MusicImportConfig": [],
"MusicImportConfig_Directories": {},
"MusicImportTargetSamplingRate": 0,
"MuteVoice_Battle": false,
"MuteVoice_Cm": false,
"MuteVoice_Emote": false,
"MuteVoice_Line": false,
"OverrideFontConfig": "",
"ReducePacketDelay": true,
"RememberedGameLaunchLanguage": "Unspecified",
"RememberedGameLaunchRegion": "Unspecified",
"ResourceLanguageOverride": "Unspecified",
"ShowControlWindow": false,
"ShowLoggingWindow": false,
"SynchronizeProcessing": false,
"TakeOverAllAddresses": false,
"TakeOverAllPorts": false,
"TakeOverLoopback": false,
"TakeOverPrivateAddresses": false,
"TerminateOnExitProcess": false,
"TtmpFlattenSubdirectoryDisplay": false,
"TtmpShowDedicatedMenu": false,
"UseAllIpcMessageLogger": false,
"UseEarlyPenalty": false,
"UseEffectApplicationDelayLogger": true,
"UseHashTrackerKeyLogging": false,
"UseHighLatencyMitigationLogging": true,
"UseHighLatencyMitigationPreviewMode": false,
"UseMainThreadTimingHandler": false,
"UseModding": false,
"UseMonospaceFont_XivAlexLogWindow": false,
"UseMoreCpuPower": false,
"UseNetworkTimingHandler": true,
"UseOpcodeFinder": false,
"UseWordWrap_XivAlexLogWindow": false,
"VoiceResourceLanguageOverride": "Unspecified"
}
}

it happend a couple patches ago, but it got fixed. However, it happend again recently.

Can you post your config.runtime.json?

This similar issue was reported by me once and got fixed in this patch "v<IP_ADDRESS>"
I was also using Dolphin VPN or should be called proxy at that time.


Why VideoInput operator doesn't exists?

I did rebuild caffe2 with ffmpeg, but It's not solved.
What should I do??

solved myself

it's a bit late to ask, but how did you solve it?


Hot Reloading Rsx

Enable hot reloading for the rsx macro.
How?

If the hot reload feature is enabled, the rsx macro parses the rsx and determines what variables are captured, and any iterators or components that are built.
It then passes that context to a interpreter which looks for the text of the rsx macro within a global context with the code position as a key (using panic's location).
This approach is renderer independent

Why?

Faster iteration times

Limitations

Components, iterators, listeners, and expressions cannot be hot reloaded

Change to what variables are captured cannot be hot reloaded

It requires the text editor or cli to track the line/character of the rsx macro as it moves.

Nested rsx calls cannot be hot reloaded

[x] capture anything that cannot be interpreted

[x] variables

[x] handle formatting options

[x] expressions in attributes

[x] components

[x] iterators

[x] listeners

[x] cx (if supplied)

[x] interpret rsx with the captured context

[x] elements

[x] components

[x] iterators

[x] text

[x] listeners

[x] keys

[x] provide a way to edit the rsx index in different programs

[x] desktop with interprocess

[x] web with WebSockets

[x] better error handling

[x] update elements when the rsx is set

[x] documentation

[x] better error reporting

Demo with https://github.com/DioxusLabs/cli/pull/43:
https://user-images.githubusercontent.com/66571940/174206798-1b73e42a-0b36-4bce-83c4-aa7d875ec800.mp4

Before opening this PR I have some notes/painpoints:

The interpreter assumes that formatted expression will resolve to the same string every time. Eg: in "{x}-{x}" is assumes the first {x} will be the same as the second {x}. This allows adding a new {x} without recompiling.
It also assumes the expressions used in the rsx call do not depend on the order.
I can't think of a reasonable example where either of these would matter, but if it is an issue I can fix it.
It passes/stores code as a String and re-parses it when it is used because syn's representation is not Send.

You put an absolute ton of work into this!!!
There's a lot of code here, but I do have some thoughts. In reality I might end up merging this branch as-is and massaging it once it's in master.
In particular, I think (hope?) we can resolve scopes/rsx calls without needing to probe the user's code directly. I don't really have a great design for this yet, but I think part of it might involve hashing each rsx! body and then lining up the source against the macro once the server is running. As I said, I don't quite have a great design yet, so I can't propose anything better. In theory - before we release hot reloading in the next big release - I want to enable it without any feature flags to be turned on/off.
I'm still reviewing it, but given the size of the PR, it might end up making more sense merging it and then massaging it once it's in. Especially since you started with the jk/rsx-refactor fork and completed that body of work... and I want to implement a few features in the post-rsx-refactor world.
Again - this is so awesome and I'm very excited to build apps with hot reloading working! :)

Thanks for the feedback!

In theory - before we release hot reloading in the next big release - I want to enable it without any feature flags to be turned on/off.

I would argue against removing the feature, but it could be enabled by default in debug mode.

I don't see a way to get hot reloading working without some amount of runtime overhead, but I could be missing something. I haven't benchmarked it but I am assuming pre-compiling the rsx will be faster than interpreting it.
There also could be some security concerns. The desktop implementation has a open ipc port and the web implementation will try to connect to a new WebSocket. Both of them would allow changing the rsx and indirectly the html and js. That could allow any malicious desktop program to watch for user inputs, impersonate the organization that created the program, etc.

I dove into this some more, and I think we might be able to get scopes resolved from rsx! calls using the file!, row!, and col! macros.
https://doc.rust-lang.org/std/macro.file.html

The file!, row!, and col! macros seem similar to panic's location tracker but with better documentation and more well defined behavior! I didn't know they existed. I changed that and also added env!("CARGO_MANIFEST_DIR") to find the absolute path instead of the path relative to the current crate.

The more I think about it, the more I agree with this approach - at least for the near term.
In the future I want to add some sort of internal cache in the VirtualDom for rsx! calls. This metadata doesn't really exist currently - the only metadata we have right now is the name of components. In dev mode, we want all this metadata exposed to provide good tooling, but we want this metadata hidden when the app is built in release mode.
Whenever I add rsx! call caching and static-ify of rsx! call bodies, then we can reconsider how deeply integrated hot reloading is in the core/web/desktop libraries.
In theory, each virtualdom registers itself with a remote interpreter, rsx! calls are cached on the interpreter's side, and the hot reloading system only needs access to the JS-interpreter (via injection from a dev server) since the JS interpreter provides enough information to match up rsx! calls to the corresponding source. There's a slight runtime overhead for this, but the performance gains of caching rsx! calls would outweigh it.
However, this body of work requires a lot of knowledge about the vdom implementation and frankly should be done after this is merged.
Everything in the PR looks good, but I might play with a little bit of the code style after merging it. Is https://github.com/DioxusLabs/cli/pull/43 still in draft or would it be out of draft after we add this?


Updates to metrics.py (still need Brier skill)

New metrics added to metrics.py:
Mean Accuracy Ratio
Median Symmetric Accuracy
Spearman Correlation
Symmetric Extreme Dependency Score
(Issues 48, 54, and 55 resolved).
Still need to update Brier Skill Score

looked over code and looks good. Thanks, Clayton.

Commits are attributed to "Allison".  Clayton, you need to configure your local git to attribute your commits to an email GitHub understands (in your profile).  Right now you are not getting "credit", and this has some implications in the system.  (e.g. right now I can't assign Issues to you.)

@rickyegeland I believe this should now be fixed. Thanks for pointing it out to me


feat: 🎸 add set admin method to multi instance

Description
allow for management of a multiSig admin for v7 chains. Signers can create a proposal to set an admin and an admin can relinquish the privilege
Breaking Changes

JIRA Link

Checklist

[ ] Updated the Readme.md (if required) ?

Needs to be draft for now since this will need to be updated for the approve weight as an option


Default value in get_theme_mod function

Is there a way to get the default values from kirki when making a call to get_theme_mod?  Right now, I have to set the default in kirki, and then I set the same default in my get_theme_mod call, which seems like a duplication of effort.  Just thought I'd ask to make sure I wasn't missing something.

We will be introducing a new get_kirki_option soon that will do that.
For the time being we're using the default WordPress functions and unfortunately that's the downside of it...
It will be improved though soon. :)

@aristath -
Thanks!  I think kirki is really great, and I appreciate all your work on it.

Fixed in https://github.com/aristath/kirki/commit/78e638e8acbeabc1d12305ca85904007c4015518
Not yet merged 'cause I'm still testing that branch, but it will be included in the next version. :smile:

Update:
I tried this and ended up spending a lot of time staring at my screen without understanding why this wouldn't work.
For now I just commented-out this function so it won't be available.
If anyone has any ideas then please let me know...
This is the code we currently have: https://github.com/aristath/kirki/blob/12f8141d838f2178306a836e2fbf59614eaff8bf/kirki.php#L178-L223
For the time being you will simply have to define a default value when using get_theme_mod()

Also looking forward into this feature.

@aristath Do you have any ETA on this feature?
Just realised this breaks my sites when deploying because processing the output values in other functions.

Actually that's the default WordPress functionality...
get_theme_mod needs a default value.
I'm trying to find a workaround though I don't currently have an ETA

Sure, i get that. No stress, going with a workaround for the time being.

Hey there! It took me 31 commits and I had to re-structure the whole plugin, but I got this working. :+1:
You can now use kirki_get_option( 'my_option' ); instead of the get_theme_mod function and it will automatically get the default value.
However, you may want to add the following in the theme you're building:
if ( ! function_exists( 'kirki_get_option' ) ) :
function kirki_get_option( $option ) {
	get_theme_mod( $option, '' );
}
endif;

This way if the plugin is not installed you won't get the right default value for unset controls, but at least the universe will not collapse on its self due to a fatal error.

Going to test this now, i'll let you know if something goes wrong.
Thanks for the all the work.

Any update on adding this utility method?

Any update on adding this utility method?

Which utility method? If you mean adding a method that will allow you to skip defining the default value when you're getting a theme-mod then no, this will not be implemented.
It was part of earlier versions of the plugin years ago, but since then we're trying to instead educate theme authors and teach them to do the right thing: Use the 2nd argument in the get_theme_mod() function to get the default value if a saved one does not exist. 😄

I actually solved it doing a init setup if its detected that some reference value isnt yet loaded into the options, so it only runs once.
if(empty(get_theme_mod("some variable") )){
error_log("init");
foreach (Kirki::$fields as $field ) {
if(isset($field["default"]) && !isset($redux_demo[$field["settings"]])){
set_theme_mod($field["settings"],$field["default"]);
}
}
}


CDI-593 Mention javax.enterprise.inject.spi.Prioritized in spec text and improve its javadoc

Added to Custom bean, interceptor and decoractor

+1


Best practices

Hi, João.
It is good practice to create repositories with the name in lower case and separated by dashes. Example:
my-repository
fast-win
another-repository

Thanks


Support for custom build args

The current plug-in doesn't seem to provide a capability to provide custom build args into the build image task.
I have a scenario where a version parameter is passed into my dockerfile via a buildarg.
As the docker-client already supports passing in a buildparam list (that's how nocache, etc. works) is this something that would be logical to add to the plug-in?
Would a PR supporting this be accepted?

Perhaps I spoke too quickly about assuming docker-client would support this without change.  I made the following local changes:
Add a new configuration parameter:
@Parameter(property = "dockerfile.customBuildArgs")   private Properties customBuildArgs;
Use configuration value to create buildArgs (within buildImage):
   if (customBuildArgs != null && !customBuildArgs.isEmpty()) {       Enumeration<?> buildArgEnum = customBuildArgs.propertyNames();       while (buildArgEnum.hasMoreElements()) {         String name = (String) buildArgEnum.nextElement();          buildParameters.add(new DockerClient.BuildParam(name, customBuildArgs.getProperty(name)));       }     }
Then within my pom file I've tried two approaches:
             		<customBuildArgs>               			<property>               				<name>build-arg</name>               				<value>buildversion=${project.version}</value>               			</property>               		</customBuildArgs>
and
             		<customBuildArgs>               			<property>               				<name>buildversion</name>               				<value>${project.version}</value>               			</property>               		</customBuildArgs>
Confirmed through logs that the parameter is properly read and added to the buildArg collection, but am unable to determine what, if anything, docker-client is doing with them.

+1 I also need this feature, which is present in the older docker-maven-plugin
To facilitate migration from docker-maven-plugin, it would be nice to support the same configuration format, ie :
<configuration>
	<buildArgs>
		<APT_MIRROR>http://my.org/ubuntu</APT_MIRROR>
	</buildArgs>
</configuration>

I need this!

This was added in #41


Updating readme from branch example

Updates
I updated the readme file. Please review and accept.

Thoughts
I probably shouldn't but okay. :+1:


You can send messages to no one - reported by @ahmdshrif

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open any chat on web desktop
change any number on the id from url
Send some messages

Expected Result:
Some error should display that page is invalid
Actual Result:
User can send a message
Workaround:
unknown
Platform:

Where is this issue occurring?

Web
Mobile Web

Version Number: 1.1.39-0
Reproducible in staging?: Y
Reproducible in production?: Y
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/43995119/154624852-84d24977-8fe8-434d-a505-00628728060b.mp4
Expensify/Expensify Issue URL:
Issue reported by: @ahmdshrif
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1643992468617449
View all open jobs on GitHub

I had reported this earlier and the core issue is to fix the invalid URL/report ID page load. Here's an existing issue reported earlier to fix it - https://github.com/Expensify/App/issues/5897

@sonialiap Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

Closing in favor of https://github.com/Expensify/App/issues/5897


Hackathon III - Checklist

Description
This is a simple checklist for some manual steps that should be taken to make sure the hackathon will be a success.

[ ] Test all Loaders/Functions and verify its working
[ ] Test all Sections and verify its working
[ ] Test onboarding - should be possible to edit a component + deploy/ab-testing
[ ] Discord channels for mentors should have been created
[ ] Discord voice channel/text channels for Hackathon
[ ] Verify if the agenda is clear for everyone
[ ] Ensure that we're running on multiple OSs without any issue (windows/linux/darwin)
[ ] Make sure the hackathon rules are clear

[ ] Check documentation and examples


Not installing if project react version >= 17.0.1

I tried to install this package on my project but I got a conflict error for react version. Do you have any plan to upgrade peer dependency version?

I have also an error while installing this library in my latest react-native project.
My project configuration :
"react": "17.0.1",
"react-native": "0.64.2",

This is the error that I am gettings :

You can solve this by running npm install --legacy-peer-deps

Thank @hellotoby
Installing this package with --legacy-peer-deps solved my problem. I have installed with below command and it installed :
npm install react-native-fast-image --legacy-peer-deps --save

Does the package install this way, can create any other issues?

+1

@kishanbharda is it working this way?

@Desintegrator yes this package working this way.

Fix the upstream dependency conflict, or retry
this command with --force, or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.

Running npm install react-native-fast-image --legacy-peer-deps --save will not  solve the potentially broken dependency resolution it will just ignore them.
Do you have any plan to upgrade peer dependency version?

+1

+1

Issue fixed in #790 merge, and the fix is in version 8.3.5 as per https://github.com/DylanVann/react-native-fast-image/pull/790#issuecomment-875101311


Improved contextuality of fresh variable names

Fresh variables are currently expanded to the prefix __tmp_ followed by a number taken from an increasing sequence. For example %foo becomes %__tmp_1234.
When reading the generated macro code, it's hard to match the variable names back to the macro source because there's no common element.
It would be helpful if the name of the fresh variable retained some information from the macro variable.
The name could be retained as part of the new variable name. It could enhance the tmp_ prefix or even replace it.
And it would be possible to scope the number sequence per name instead of a single sequence for the entire program. This would keep the numbers lower and thus easier to handle the names.
So %foo could become something like %__tmp_foo_1234 or %__foo_12.
Expressions (which follow the fresh variable name in curly braces) could be considered as part of the name as well. They must be turned into identifier-safe strings and could be inserted between the name and the sequence number.
For example, {% bar = "baz qux" %} %foo{bar} could become something like __foo_bazqux_12.

This example of an instantiation of JSON::Serizaliable#initialize demonstrates the differences of the proposed approach.
I think the additional information improves the readability a lot, especially when dealing with repeated code segments.
-__temp_879 = uninitialized ::Union(String)
-__temp_880 = false
+__var_foo_1 = uninitialized ::Union(String)
+__found_foo_1 = false

-__temp_881 = uninitialized ::Union(String)
-__temp_882 = false
+__var_bar_1 = uninitialized ::Union(String)
+__found_bar_1 = false

-__temp_883 = pull.location
+__location_1 = pull.location
 begin
   pull.read_begin_object
 rescue exc : ::JSON::ParseException
-  raise ::JSON::SerializableError.new(exc.message, self.class.to_s, nil, *__temp_883, exc)
+  raise ::JSON::SerializableError.new(exc.message, self.class.to_s, nil, *__location_1, exc)
 end
 until pull.kind.end_object?
-  __temp_884 = pull.location
+  __key_location_1 = pull.location
   key = pull.read_object_key
   case key
   when "foo"
     begin
       next if pull.read_null?

-      __temp_879 =
+      __var_foo_1 =
         begin
           ::Union(String).new(pull)
         end
-      __temp_880 = true
+      __found_foo_1 = true
     rescue exc : ::JSON::ParseException
-      raise ::JSON::SerializableError.new(exc.message, self.class.to_s, "foo", *__temp_884, exc)
+      raise ::JSON::SerializableError.new(exc.message, self.class.to_s, "foo", *__key_location_1, exc)
     end
   when "bar"
     begin
       next if pull.read_null?

-      __temp_881 =
+      __var_bar_1 =
         begin
           ::Union(String).new(pull)
         end
-      __temp_882 = true
+      __found_bar_1 = true
     rescue exc : ::JSON::ParseException
-      raise ::JSON::SerializableError.new(exc.message, self.class.to_s, "bar", *__temp_884, exc)
+      raise ::JSON::SerializableError.new(exc.message, self.class.to_s, "bar", *__key_location_1, exc)
     end
   else
-    on_unknown_json_attribute(pull, key, __temp_884)
+    on_unknown_json_attribute(pull, key, __key_location_1)
   end
 end
 pull.read_next

-if __temp_880
-  @foo = __temp_879
+if __found_foo_1
+  @foo = __var_foo_1
 else
 end

-if __temp_882
-  @bar = __temp_881
+if __found_bar_1
+  @bar = __var_bar_1
 else
 end

I'd still vote to keep the prefix for the tools like ameba.

Could you elaborate on that? What does ameba do with the __temp_ prefix?

It detects the usage of auto-expanded variables.

To be precise, ameba detects auto argument expansion, and not fresh variables in macros.
This might might come handy in the future though, once ameba gain semantic analysis.


-- Better form of Readme

Updating the Readme with the Screenshots are better as user may find the relevant image faster and easily

Hello World


Set up bounties for contributors to hunt.

We have a lot of things we would like, i.e., https://roadmap.maplibre.org/tabs/16-overview and many more.
Currently, no resources are allocated for anything to drive development.
With ESRI's recent adoption of MapLibre, it would arguably make a lot of sense to collaborate with that deep expertise on the compatibility with the ArcGIS stack (on our roadmap)

https://github.com/maplibre/maplibre/wiki/Bounty-System

https://twitter.com/rust_foundation/status/1579889452977369089?t=7oeAH4eqc0S3eToN9vvy3g&s=19

Let's track the progress on the bounty system in #125 only.


v1.8.0 crash by panic: runtime error: slice bounds out of range [2:1]

Which version are you using?
v1.8.0
Which operating system are you using?

[ ] Linux amd64 standard
[x] Linux amd64 Docker
[ ] Linux arm64 standard
[ ] Linux arm64 Docker
[ ] Linux arm7 standard
[ ] Linux arm7 Docker
[ ] Linux arm6 standard
[ ] Linux arm6 Docker
[ ] Windows amd64 standard
[ ] Windows amd64 Docker (WSL backend)
[ ] macOS amd64 standard
[ ] macOS amd64 Docker
[ ] Other (please describe)

Describe the issue
Description
Describe how to replicate the issue
I'm using mediamtx on my program for forward RTSP streams. In my using case, the Input video streams are very unstable so FFMPEG process always needs be stoped and restart again frequently.  Mediamtx well worked for 7 hours then it crashed.
I'm sorry the bug is too random to replicate it, so I haven't found more info except server logs traceback.

start the server (I use default configuration):
./mediamtx

publish with ...

ffmpeg -rtsp_transport tcp -buffer_size 10240000 -stimeout 10000000 -i rtsp://<IP_ADDRESS>:1815/ {Camera ID} /livestream -c:v copy -f rtsp rtsp://<IP_ADDRESS>:8554/stream/{Camera ID}

read with ...
A gstreamer-1.0 C++ program with uri_decode_bin() and UDP protocol.

Did you attach the server logs?

Here are some error logs:
2024/09/09 17:55:28 INF [RTSP] [conn <IP_ADDRESS>:45634] opened
2024/09/09 17:55:28 INF [RTSP] [session b39d5739] created by <IP_ADDRESS>:45634
2024/09/09 17:55:29 INF [RTSP] [session eafb44e9] is reading from path 'stream/64069111101322020025', with UDP, 1 track (H265)
2024/09/09 17:55:29 INF [RTSP] [session b39d5739] is reading from path 'stream/46040095001321000124', with UDP, 1 track (H264)
2024/09/09 17:55:57 INF [RTSP] [conn <IP_ADDRESS>:45680] opened
2024/09/09 17:55:57 INF [RTSP] [session 0c7b12b0] created by <IP_ADDRESS>:45680
2024/09/09 17:55:57 INF [RTSP] [session 0c7b12b0] is publishing to path 'stream/46040095001321000164', 1 track (H264)
2024/09/09 17:55:58 INF [RTSP] [session 95434526] destroyed: torn down by <IP_ADDRESS>:45620
2024/09/09 17:55:58 INF [RTSP] [conn <IP_ADDRESS>:45634] closed: terminated
2024/09/09 17:55:58 INF [RTSP] [conn <IP_ADDRESS>:45620] closed: EOF
2024/09/09 17:55:58 INF [RTSP] [session b39d5739] destroyed: terminated
2024/09/09 17:55:58 INF [RTSP] [conn <IP_ADDRESS>:45682] opened
2024/09/09 17:56:07 INF [RTSP] [conn <IP_ADDRESS>:45694] opened
2024/09/09 17:56:07 INF [RTSP] [session 76d8641d] created by <IP_ADDRESS>:45694
2024/09/09 17:56:08 INF [RTSP] [session 76d8641d] is reading from path 'stream/46040095001321000164', with UDP, 1 track (H264)
2024/09/09 17:56:13 INF [RTSP] [session 76d8641d] destroyed: torn down by <IP_ADDRESS>:45694
2024/09/09 17:56:13 INF [RTSP] [conn <IP_ADDRESS>:45694] closed: EOF
2024/09/09 17:56:13 INF [RTSP] [conn <IP_ADDRESS>:45712] opened
2024/09/09 17:56:13 INF [RTSP] [session 8a37a181] created by <IP_ADDRESS>:45712
2024/09/09 17:56:14 INF [RTSP] [session 8a37a181] is reading from path 'stream/46040095001321000164', with TCP, 1 track (H264)
2024/09/09 17:56:14 INF [RTSP] [session 0c7b12b0] destroyed: torn down by <IP_ADDRESS>:45680
2024/09/09 17:56:14 INF [RTSP] [conn <IP_ADDRESS>:45680] closed: EOF
2024/09/09 17:56:14 INF [RTSP] [conn <IP_ADDRESS>:45712] closed: terminated
2024/09/09 17:56:14 INF [RTSP] [session 8a37a181] destroyed: terminated
2024/09/09 17:56:26 INF [RTSP] [conn <IP_ADDRESS>:45682] closed: EOF
panic: runtime error: slice bounds out of range [2:1]
goroutine 23 [running]:
github.com/bluenviron/gortsplib/v4/pkg/format.(*H265).PTSEqualsDTS(0xc00098c8d0?, 0xc0005ec360?)
/go/pkg/mod/github.com/bluenviron/gortsplib/v4@v4.8.2/pkg/format/h265.go:143 +0x186
github.com/bluenviron/gortsplib/v4.(*serverSessionFormat).readRTPUDP(0xc000412200, 0xc00047f1d0?, {0xc0005ec364?, 0x5c1?, 0x1787520?})
/go/pkg/mod/github.com/bluenviron/gortsplib/v4@v4.8.2/server_session_format.go:66 +0xbe
github.com/bluenviron/gortsplib/v4.(*serverSessionMedia).readRTPUDPRecord(0xc00001e200, {0xc0005f1200, 0x0?, 0x5c1})
/go/pkg/mod/github.com/bluenviron/gortsplib/v4@v4.8.2/server_session_media.go:214 +0x125
github.com/bluenviron/gortsplib/v4.(*serverUDPListener).run.func1(0xc000493600, 0xc0005f1200?, {0xc0005f1200, 0x5c1?, 0x5c1}, 0xd)
/go/pkg/mod/github.com/bluenviron/gortsplib/v4@v4.8.2/server_udp_listener.go:146 +0x174
github.com/bluenviron/gortsplib/v4.(*serverUDPListener).run(0xc000493600)
/go/pkg/mod/github.com/bluenviron/gortsplib/v4@v4.8.2/server_udp_listener.go:147 +0x6c
created by github.com/bluenviron/gortsplib/v4.(*serverUDPListener).initialize in goroutine 1
/go/pkg/mod/github.com/bluenviron/gortsplib/v4@v4.8.2/server_udp_listener.go:106 +0x20a
Did you attach a network dump?

no

I have the same issue.
The only difference is that I use gst-python to create and run the gst-pipeline.
You could try the command line GStreamer pipeline (for some reason it works).
But it looks like this issue is related to uridecodebin and origin rtsp source (AXIS camera in my case)
FYI @Titianzi

Thank you very much for reporting the crash, this is fixed by https://github.com/bluenviron/gortsplib/pull/617


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v3.12 to before v5.4.165",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ac22ac466a659f1b2e02a2e2ee23fc5c42da2c95",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=48fcd08fdbe05e35b650a252ec2a2d96057a1c7a"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "ac22ac466a659f1b2e02a2e2ee23fc5c42da2c95",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "48fcd08fdbe05e35b650a252ec2a2d96057a1c7a",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.4.165 by commit 48fcd08fdbe05e35b650a252ec2a2d96057a1c7a, it was introduced in version v3.12 by commit ac22ac466a659f1b2e02a2e2ee23fc5c42da2c95. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2021-1002456


Very good plugin!

I just want to say thank you, this is must to have plugin if you're working with CSS. :+1:

Thank you, but i just ported plugin from sublime


worker/task: add convenience HexDump() and String() methods

Being able to dump the hex/string content of a message is quite useful for debugging/logging.

Looks good other than the one comment 👍

Nice! Thanks for the update, and great to have this merged 👍


What's new in .NET 7 Preview 2 [WIP]

What's new in .NET 7 Preview 2
This issue is for teams to highlight work for the community that will release .NET 7 Preview 1
To add content, use a new conversation entry. The entry should include the team name and feature title as the first line as shown in the template below.
## Team Name: Feature title

[link to the tracking issue or epic item for the work]

Tell the story of the feature and anything the community should pay particular attention
to be successful using the feature.

Preview 1: https://github.com/dotnet/core/issues/7106
Preview 2: https://github.com/dotnet/core/issues/7107
Preview 3: https://github.com/dotnet/core/issues/7108

Note: This feature has been present since Preview 1 but didn't make it to the Preview 1 blog post, so copying the content here again in order to get it into Preview 2 blog.
Introducing the new Regex Source Generator
https://github.com/dotnet/runtime/issues/44676
Ever wished you had all of the great benefits that come from having a specialized Regex engine that is optimized for your particular pattern, without having to pay the costs of building this engine at runtime? We are excited to announce the new Regex Source Generator which is included in Preview 1. It brings all of the performance benefits from our Compiled engine without the startup cost, and it has additional benefits, like providing a great debugging experience as well as being trimming-friendly. If your pattern is known at compile-time, then the new regex source generator is the way to go.
In order to start using it, you only need to turn the containing type into a partial one, and declare a new partial method with the RegexGenerator attribute that will return the optimized Regex object, and that's it! The source generator will fill the implementation of that method for you, and will get updated automatically as you make changes to your pattern or to the additional options that you pass in. Here is an example:
Before:
public class Foo
{
  public Regex regex = new Regex(@"abc|def", RegexOptions.IgnoreCase);

  public bool Bar(string input)
  {
    bool isMatch = regex.IsMatch(input);
    // ..
  }
}

After:
public partial class Foo  // <-- Make the class a partial class
{
  [RegexGenerator(@"abc|def", RegexOptions.IgnoreCase)] // <-- Add the RegexGenerator attribute and pass in your pattern and options
  public static partial Regex MyRegex(); //  <-- Declare the partial method, which will be implemented by the source generator

  public bool Bar(string input)
  {
    bool isMatch = MyRegex().IsMatch(input); // <-- Use the generated engine by invoking the partial method.
    // ..
  }
}

And that's it. Please try it out and let us know if you have any feedback.

CodeGen
Community PRs (Many thanks to JIT community contributors!!)
From @sandreenko

https://github.com/dotnet/runtime/pull/64506

From @SingleAccretion

https://github.com/dotnet/runtime/pull/63100
https://github.com/dotnet/runtime/pull/63251
https://github.com/dotnet/runtime/pull/63268
https://github.com/dotnet/runtime/pull/63447
https://github.com/dotnet/runtime/pull/63462
https://github.com/dotnet/runtime/pull/63539
https://github.com/dotnet/runtime/pull/63903
https://github.com/dotnet/runtime/pull/64498
https://github.com/dotnet/runtime/pull/64501
https://github.com/dotnet/runtime/pull/64701
https://github.com/dotnet/runtime/pull/64826
https://github.com/dotnet/runtime/pull/64855
https://github.com/dotnet/runtime/pull/64882
https://github.com/dotnet/runtime/pull/65079

From @Wraith2

Recognize BLSR in "x & (x-1)" https://github.com/dotnet/runtime/pull/63545
https://github.com/dotnet/runtime/pull/64350

Dynamic PGO

https://github.com/dotnet/runtime/pull/63720

Arm64

https://github.com/dotnet/runtime/pull/64481
https://github.com/dotnet/runtime/pull/64857
https://github.com/dotnet/runtime/pull/64864
https://github.com/dotnet/runtime/pull/62933
https://github.com/dotnet/runtime/pull/65153

General Optimizations

Security: https://github.com/dotnet/runtime/pull/63763
Testing: https://github.com/dotnet/runtime/pull/64119

In preview 2 we fixed the following logging source generator failures with various syntax issues:

[x] https://github.com/dotnet/runtime/issues/64310
[x] https://github.com/dotnet/runtime/issues/62644
[x] https://github.com/dotnet/runtime/issues/60968
[x] https://github.com/dotnet/runtime/issues/61814
[x] https://github.com/dotnet/runtime/issues/58550

Observability

https://github.com/dotnet/runtime/issues/63648

static Meter s_meter = new Meter("MyLibrary.Queues", "1.0.0");
static UpDownCounter<int> s_queueSize = s_meter.CreateUpDownCounter<int>("Queue-Size");
static ObservableUpDownCounter<int> s_pullQueueSize = s_meter.CreateObservableUpDownCounter<int>("Queue-Size", () => s_pullQueueSize);

...

s_queueSize.Add(10);
s_queueSize.Add(-2);

The PR for blog post; will remain open until Monday 3/14 noon (PST)
Create dotnet-7-preview-2.md · Pull Request #784 · microsoft/dotnet-blog (github.com)
The plan is to work on the content in the PR until noon (PST) on Monday 3/14. After that the content will be copied over to the blog and we can make any last minute changes if needed there.

SDK Improvements
dotnet new syntax and tab-completion
https://github.com/dotnet/templating/issues/2191
For 7.0.100-preview2, the dotnet new command has been given a more consistent and intuitive interface for many of the subcommands that users already use. In addition, support for tab-completion of template options and arguments has been massively updated, now giving rapid feedback on valid arguments and options as the user types.
Here's the new help output as an example:
❯ dotnet new --help
Description:
  Template Instantiation Commands for .NET CLI.

Usage:
  dotnet new [<template-short-name> [<template-args>...]] [options]
  dotnet new [command] [options]

Arguments:
  <template-short-name>  A short name of the template to create.
  <template-args>        Template specific options to use.

Options:
  -?, -h, --help  Show command line help.

Commands:
  install <package>       Installs a template package.
  uninstall <package>     Uninstalls a template package.
  update                  Checks the currently installed template packages for update, and install the updates.
  search <template-name>  Searches for the templates on NuGet.org.
  list <template-name>    Lists templates containing the specified template name. If no name is specified, lists all templates.

New Command Names
Specifically, all of the commands in this help output no longer have the -- prefix that they do today. This is more in line with what users expect from subcommands in a CLI application. The old versions (--install, etc) are still available to prevent breaking user scripts, but we hope to add obsoletion warnings to those commands in the future to encourage migration.
Tab Completion
The dotnet CLI has supported tab completion for quite a while on popular shells like PowerShell, bash, zsh, and fish (instructions for enabling that can be found here).  It's up to individual dotnet commands to implement meaningful completions, however. For .NET 7, the new command learned how to provide tab completion for

available template names (in dotnet new <template-short-name>
template options (the list of template options in the web template)
allowed values for those template options (choice values on an choice template argument)

There are certain known gaps in completion (for example, --language doesn't suggest installed language values), but we'd love for you to try the new completion in your templates and let us know how you like it!
Future work
In future previews we plan to continue filling gaps left by this transition, as well as make enabling completions either automatic or as simple as a single command that the user can execute. We hope that this will make improvements in tab-completion across the entire dotnet CLI more broadly used by the community!

Note: This feature has been present since Preview 1 but didn't make it to the Preview 1 blog post, so copying the content here again in order to get it into Preview 2 blog.
Introducing the new Regex Source Generator
dotnet/runtime#44676
Ever wished you had all of the great benefits that come from having a specialized Regex engine that is optimized for your particular pattern, without having to pay the costs of building this engine at runtime? We are excited to announce the new Regex Source Generator which is included in Preview 1. It brings all of the performance benefits from our Compiled engine without the startup cost, and it has additional benefits, like providing a great debugging experience as well as being trimming-friendly. If your pattern is known at compile-time, then the new regex source generator is the way to go.
In order to start using it, you only need to turn the containing type into a partial one, and declare a new partial method with the RegexGenerator attribute that will return the optimized Regex object, and that's it! The source generator will fill the implementation of that method for you, and will get updated automatically as you make changes to your pattern or to the additional options that you pass in. Here is an example:
Before:
public class Foo
{
  public Regex regex = new Regex(@"abc|def", RegexOptions.IgnoreCase);

  public bool Bar(string input)
  {
    bool isMatch = regex.IsMatch(input);
    // ..
  }
}

After:
public partial class Foo  // <-- Make the class a partial class
{
  [RegexGenerator(@"abc|def", RegexOptions.IgnoreCase)] // <-- Add the RegexGenerator attribute and pass in your pattern and options
  public static partial Regex MyRegex(); //  <-- Declare the partial method, which will be implemented by the source generator

  public bool Bar(string input)
  {
    bool isMatch = MyRegex().IsMatch(input); // <-- Use the generated engine by invoking the partial method.
    // ..
  }
}

And that's it. Please try it out and let us know if you have any feedback.

Added it to the draft of the blog post

CodeGen
Community PRs (Many thanks to JIT community contributors!!)
From @sandreenko

[Jit] Delete Statement::m_compilerAdded . runtime#64506

From @SingleAccretion

Delete GT_DYN_BLK runtime#63026
Address-expose locals under complex local addresses in block morphing runtime#63100
Refactor optimizing morph for commutative operations runtime#63251
Preserve OBJ/BLK on the RHS of ASG runtime#63268
Handle embedded assignments in copy propagation runtime#63447
Do not set GTF_NO_CSE for sources of block copies runtime#63462
Exception sets: debug checker & fixes runtime#63539
Stop using CLS_VAR for "boxed statics" runtime#63845
Tune floating-point CSEs live across a call better runtime#63903
Reverse ASG(CLS_VAR, ...) runtime#63957
Fix invalid threading of nodes in rationalization runtime#64012
Add the exception set for ObjGetType runtime#64106
Improve fgValueNumberBlockAssignment runtime#64110
Commutative morph optimizations runtime#64122
Fix unique VNs for ADDRs runtime#64230
Copy propagation tweaking runtime#64378
Introduce GenTreeDebugOperKind runtime#64498
Add support for TYP_BYREF LCL_FLDs to VN runtime#64501
Do not add NRE sets for non-null addresses runtime#64607
Take into account zero-offset field sequences when propagating locals runtime#64701
Another size estimate fix for movs runtime#64826
Mark promoted SIMD locals used by HWIs as DNER runtime#64855
Propagate exception sets for assignments runtime#64882
Account for HWI stores in LIR side effects code runtime#65079

From @Wraith2

Recognize BLSR in "x & (x-1)" Add blsr runtime#63545
Add xarch andn runtime#64350

Dynamic PGO

JIT: simple forward substitution pass runtime#63720

Arm64

Local heap optimizations  on Arm64 runtime#64481
Couple optimization to MultiRegStoreLoc runtime#64857
Implement LoadPairVector64 and LoadPairVector128 runtime#64864
'cmeq' and 'fcmeq' Vector64.Zero/Vector128.Zero ARM64 containment optimizations runtime#62933
Increase arm32/arm64 maximum instruction group size runtime#65153
Prefer "mov reg, wzr" over "mov reg, #0" runtime#64740
Biggen GC Gen0 for Apple M1 Fix LLC cache issue on Apple M1 runtime#64576
Optimize full memory barriers around volatile reads/writes ARM64: Avoid LEA for volatile IND runtime#64354
Optimize Math.Round(x, MidpointRounding.AwayFromZero/ToEven) runtime#64016

General Optimizations

Security: Add JIT support for control-flow guard on x64 and arm64 runtime#63763
Testing: Spmi replay asmdiffs mac os arm64 runtime#64119

Added it to the draft of the blog post

SDK Improvements

Added it to the draft of the blog post

Observability

Added it to the draft of the blog post

Logging Source Generator
Added it to the draft of the blog post

NativeAOT Update
We previously announced that we're moving the NativeAOT project out of experimental status and into mainline development in .NET 7. Over the past few months we've been heads down doing the coding to move NativeAOT out of the experimental dotnet/runtimelab repo and into the dotnet/runtime repo. That work has now been completed, but we have yet to add first-class support in the dotnet SDK for publishing projects with NativeAOT. We hope to have that work done shortly, so you can try out NativeAOT with your apps. In the meantime, please try trimming your app and ensure there are no trim warnings. Trimming is a requirement of NativeAOT. If you own any libraries there are also instructions for preparing libraries for trimming.

Adding NativeAOT update now...

.NET 7 GA is available. Closing these pre-release issues.


Verifiable Document feature

UI rendering: https://www.npmjs.com/package/react-jsonschema-form-material-ui
swc/wasm

Moved to substitutedr project


Add methods for observing dock visibility

This adds an onDidChangeVisible() and observeVisible() method to docks so that other objects can be notified when they're toggled.
Since this functionality covers the didHide() callback use case, I removed that.
One thing I'd like to discuss is the semantics of this. In the original docks PR, I had avoided calling this "visible" because it'll actually be false while the dock is visible but being animated closed. If you're using this API, for example, to show or hide contents of an item, you could wind up with surprising results.

For posterity: the conclusion after talking to @maxbrunsfeld was that this API should behave as-is. A later PR can toggle the display of the dock item containers before and after animation so that IntersectionObserver can be used. (Currently, it's not working with "overflow: hidden" masking.)

:+1:


Update back to ReadCreateModify...

Summary 🎯

Just realised you actually need ReadCreateModify because you are creating and adding powerups :sweat_smile:

Changes 🔁

Update back to ReadCreateModify...

Yeah, I was confused about this one 😄


Bugfix release v1.0.1

Why this PR?
We would like to release some bug fixes.
What to look out for?
Please review the ensure backward compatibility commit carefully.

Going to prepare a PR for releasing v1.1.0 instead.


Update dialect XSD for 'format-true' and 'format-false' to allow literal, predicate and value attributes

'format-true' and 'format-false' are used in two use cases: literals and predicates
Literals: when a boolean is used a value

defaults to x ? 1 : 0
example usage: SELECT 1 as literalBool

Predicates: when a boolean is used as a predicate

defaults to isTrue ? (1=1) : (1=0)
example usage: SELECT something as blah WHERE (1=1)
'value' attribute is used as 'predicate' for backwards compatability

Did you mean to have the samples updated in this pull request as well?

I couldn't decide if it made sense to do them together or not.  I thought if someone was looking in change history the comments might be easier to follow if they're apart.


python.autoComplete.extraPaths does not appear to be working

Environment data

VS Code version: insiders
Extension version (available under the Extensions sidebar): master
OS and version: Windows 10
Python version (& distribution if applicable, e.g. Anaconda): CPython 3.7.0b3
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
Relevant/affected Python packages and their versions: N/A

Actual behavior
No auto-complete for a file only found through python.autoComplete.extraPaths
Expected  behavior
Auto-complete.
Steps to reproduce:

Create a ~/Desktop/extras folder.
Create a file named foobar.py in that folder containing def spam(): pass
Set python.autoComplete.extraPaths to point to the extras folder
import foobar; foobar. should have spam in its completion list.

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
None
Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)
None

Fixed by #1471


Feature: add support for keyless signed release

We should add support for keyless cosign signing in the Signed-Release check.
cc @asraa

I recently added the ossf scorecard to my project (https://github.com/dadrus/heimdall) and unfortunately was hit by the lack of keyless signing support, which obviously provides the required attestation. Without this support, the corresponding score can be considered a false negative without an option to fix it, which also means it is lower as it should be for my project.
Really appreciate if you address this FR.
See also the corresponding discussion in Slack: https://openssf.slack.com/archives/C0235AR8N2C/p1711287556171039?thread_ts=1711287556.171039&cid=C0235AR8N2C

We are currently looking to roll scorecard into ~13k projects, keyless signing is definitely desirable from our point-of-view as we're in the process on going "all-in" on sigstore and ephemeral keys

I think we have support at HEAD looking for .sigstore files, but we have not released yet. /cc @spencerschrock

@laurentsimon: Could you please share a link to the corresponding PR. I would like to understand whether it would solve the issue I'm currently facing. .sigstore file doesn't say anything to me.

@laurentsimon: Could you please share a link to the corresponding PR? I would like to understand whether it would solve the issue I'm currently facing. .sigstore file doesn't say anything to me.

The relevant PR would be #3772, but I don't think it would help in your case
@laurentsimon the repo in question uses this goreleaser config
https://github.com/dadrus/heimdall/blob/f7d4aaab9ab34fa6c0babb9a31a733356ab0f8c2/.goreleaser.yaml#L50-L53 which you can see in the artifacts:
https://github.com/dadrus/heimdall/releases

Actually, there is more. Since goreleaser cannot properly sign sbom and attach it to the container images, there are https://github.com/dadrus/heimdall/blob/4f018677b6e2e6b2b5a2cf30220b6cd90fdc8227/.github/workflows/ci.yaml#L428-L453 (for dev images) and https://github.com/dadrus/heimdall/blob/4f018677b6e2e6b2b5a2cf30220b6cd90fdc8227/.github/workflows/ci.yaml#L529-L562 (for the released images) in place.
Both result in additional packages you can find in GH (heimdall-sbom and heimdall-signatures, with first being the signed SBOM and the second being the signature of the image, with both providing the same provenance as also available for regular binaries) and in DockerHub (with the same capabilities)

@spencerschrock: you're right, #3772 indeed won't help


Eliminate the second type parameter of punctuated::Iter, IterMut, IntoIter

Currently if you iterate over the values of a Punctuated<T, P> the iterator types are Iter<'a, T, P>, IteraMut<'a, T, P>, IntoIter<T, P>. Instead they should be Iter<'a, T>, IterMut<'a, T>, IntoIter<T>.
Relevant paper: http://www.stroustrup.com/SCARY.pdf
For this to be well defined we will need to replace the Vec<(T, Option<P>)> with a Vec<RawPair> with a defined layout:
#[repr(C)]
struct RawPair<T, P> {
    t: T,
    p: Option<P>,
}

And then have the various iterators store mem::size_of::<RawPair<T, P>>() when constructed and use that as a stride when traversing the contents of the vector.

Fixed in 8095c30c073611aebe4151571ce480f8fea1dd75.


Display sidebar when viewing OpenApi docs

Is your feature request related to a problem?
When visiting a page generated by starlight-openapi (e.g. https://starlight-openapi.vercel.app/api/petstore/operations/addpet/) , the sidebar disappears. My only option to view another page is to navigate with the back button first. This behavior does not blend in well with the rest of the Starlight page, where the sidebar is typically present all the time.
Describe the solution you'd like
Ideal solution would be to specify sidebar behavior for starlight-openapi in astro.config.mjs. However, the sidebar always being there would be a reasonable default IMO.
Describe alternatives you've considered
No response
Additional Context
No response

Thanks for jumping in @stefanofa, really appreciate it. :raised_hands:
This is indeed a regression in the latest version as mentioned in the release notes due to some changes in Starlight 0.11.0.
I already opened an issue in the Starlight repository to discuss/think how this could be handled but the goal is definitely to bring back the sidebar as it was before.
I'll make sure to ping this issue when a fix is available.

Would be really helpful for anybody looking this up in the future to see the issue as open until it is resolved. I had not realized it was a known issue until I thought to look at closed issues, and I would like to follow this issue so I'm notified when it is fixed.

Would be really helpful for anybody looking this up in the future to see the issue as open until it is resolved.

Good point, this was closed by the author and I forgot to reopen it. This is now reopened.

Hey @HiDeoo, absolutely not to stress you out, but do you have any idea when this feature might be released?

Hey @HiDeoo, absolutely not to stress you out, but do you have any idea when this feature might be released?

This requires changes into Starlight that I have described in this discussion and I recently posted my ideas for a fix in this post but so far I didn't get any feedack or suggestions yet.
If I don't get any before I get enough time, I'll switch to making a PR with the changes I described.

Hello, I've been following along with the related issues and discussions (this turned out to be more complicated than I thought, and saw the latest PR update in https://github.com/withastro/starlight/pull/1175#issuecomment-1871868017. And I was wondering if that goes in, this issue can be resolved as well?

And I was wondering if that goes in, this issue can be resolved as well?

Yes, definitely. The PR has a pretty broad scope and try to fix various issues related to custom pages and one of them is indeed having custom content in a custom page using the Starlight layout with the default sidebar.
This page from the PR preview is an example of a dynamically injected page with some custom content that could be the content of the starlight-openapi integration (which will be refactored to a Starlight plugin if the PR is merged) while still having the default Starlight sidebar.

Oh wow, the possibilities have been greatly expanded. This is amazing work. 🙇🏻♀🙇🏻♀🙇🏻♀

Thanks everyone for your patience with this issue.
v0.5.0 fixes the issue, e.g. this demo page which now includes the Starlight sidebar.

hey @HiDeoo , from behind the scenes I have been following the immense work you have done to make everything possible over the releases of the past few days, and I simply wanted to thank you ❤


Setting Capabilities and/or Security Context for App?

This is a question & potential feature request, not a bug report.
I was wondering if it's possible to set capabilities for apps deployed via Docker at configuration time?
Is the case? If not, is it possible to extend Workflow to support this functionality?
Desired Outcome
Apps built via Docker would respect Kubernetes Security Context settings; such as adding NET_ADMIN capabilities to the container.

@teamhephy-admin - Just wanted to check in on this as it's been quite some time without a response.

Do you have a good reference document about the subject?  I'm not really familiar with security context, is this the same thing as PodSecurityPolicy?

@kingdonb - It is related to PodSecurityPolicy.
https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-capabilities-for-a-container
https://raw.githubusercontent.com/kubernetes/website/master/content/en/examples/pods/security/security-context-4.yaml
https://kubernetes.io/docs/concepts/policy/pod-security-policy/#capabilities
Basically, what I'm wondering is can the capabilities for an app deployment either at build/deploy time or afterwards via the CLI?

@joshuabuildsthings , this is very interesting feature request and we have already done some reading about security context settings on pods before this. It would be nice to be able to set these security contexts on pods via the CLI. We are open to pull requests and can prioritize this feature at some point as my team will also be interested in these security context settings per pod. :1st_place_medal:
Some more context:
https://kubernetes.io/docs/tasks/configure-pod-container/security-context/


Could our card sign a Partially Signed Bitcoin Transaction ?

Some hardwallets (eg coinkite) implement BIP174
https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki
It seems it's an interesting BTC only feature to facilitate BTC multisig.
One question to look out : if a mobile wallet (handling BTC) implements PSBT, can our card (integrated with this wallet) can sign this PSBT, or is there a need to sign more than a hash and pass the transaction to the card with some other parameters ?

ECDSA signature are always calculated over hashes. The off-card side must perform all needed checks, format the data accordingly and finally generate the hash for actual signing. I am not familiar with this specific BIP but I would tend to say that it is possible without changes to the card. We would however need at least one BTC wallet integrating with our hardwallet to have a proof of concept


Admin > Rewards Distribution: Cannot claim marketplace balance

Cannot claim marketplace balance: button Claim Balance for marketplace seems not working.
Claim balance for Collection & Launchpad work fine.

Re-test: Claim marketplace balance successfully. Close issue.


Invalid CSV: HDX_ACAPS.csv

Describe the bug
The file HDX_ACAPS.csv (https://s3-us-west-1.amazonaws.com/starschema.covid/HDX_ACAPS.csv) is not valid CSV.
To Reproduce
Steps to reproduce the behavior:

Parse CSV-file https://s3-us-west-1.amazonaws.com/starschema.covid/HDX_ACAPS.csv
Parsing fails with "Error parsing CSV line: 3967. [,Not applicable,2020-04-09 00:00:00.000000,Palau MoH,Government,http://www.palauhealth.org/2019nCoV_SitRep/MOH-COVID-19 Daily Update.pdf,2020-04-15 00:00:00.000000,PW,2020-04-17 00:04:23.338183]"

Additional context
Looks like line 3967 misses some columns. Maybe there are more invalid rows following.

OpenCSV says line 3967 is invalid. However, opening the CSV in Excel shows it's actually line 3861 that is invalid. This difference might be because of line-breaks in the lines above.

Update: Until yesterday (~24 hours ago) that CSV-file was valid

I will have a look at it, but we were able to load the same file to our database. Our process uses generic pandas to_csv method to save it, so the expectation is that it should work.
I'll let you what did we find

Thx!
Depending on the parser it might work, but the number of columns is not matching the number of header-columns. At least for the given row

seems there is a non-printable character at the end of a few fields. Excel considers that as a new line character for some reason. I will force double quotes for that column

Thanks a lot! 👍


Should add some additonal env to "setup.sh"

Hi,
Sometimes, we need to keep the container not be destroyed when debuging problems, login to container by ./bin/wsh, after that we can destroy it manually.
But the stop.sh and the destroy.sh can not be run directly, because miss some env like GARDEN_CGROUP_PATH and GARDEN_IPTABLES_NAT_PREROUTING_CHAIN. notes that this two scripte can run directly in Warden.
So, it will be quite good to add all env which stop.sh, destroy.sh, net.sh will use into the setup.sh like iface_name_prefix.
This will make sense for mess around with Garden.
@lyuyun
Thanks

Hey @tsjsdbd - What kind of problems are you looking to debug, and how are you driving Garden?  I'd expect that you could Create() a container, Run() something inside it, and then ssh to the host and debug the issue via wsh before later calling Destroy().  Why would you want to destroy the container via the stop.sh and destroy.sh scripts?
(also, we're going to be rewriting all of the shell scripts in Go, so this probably isn't the right time to add functionality to them)

Because we are behind the proxy (in a internal network), and always face network download problems,  also, in the Garden log, it is difficult to get the command stdout or stderr, it always said command exited code 1. So we need login to container use wsh to verfy if the command execute correct or see what's the real output, when use Diego intergrate with CF.
it's another thing that Garden's log should include the command's stdout and stderr when run command failed. just a exited code is not enough.

@tsjsdbd were you able to work around this in the end? I'd like to close this issue given that we're rewriting those scripts in Go now.

it is very difficult to get the script's error output from Garden's log when call these scripts, like start.sh. it's very useful if we can control Container lifecycle by these script seperately.(like Warden)
so i wonder if you can add this ENV before it become GO code, i believe it is very simple. or I can send a PR if it will be long time before it become GO. but if it already have GO implementation, please omit this, and just colse it. @goonzoid

@glyn Am I correct in thinking that setup.sh is going to be gone when we merge the wshd rewrite branch?

@goonzoid No, setup.sh will survive the wsh/wshd rewrite.

Since we'll soon stop supporting Garden-Linux in favour of Guardian, I think we're unlikely to fix this.
@tsjsdbd please feel free to submit a PR if this is still an issue for you. Thanks.


Upgrade RocksDB to 6.15.2

@bradyoo Thanks for the improvement. Do you mind adding a short description on why we need to upgrade RocksDB?

Added description.

alluxio-bot, merge this please.

Related to https://github.com/Alluxio/alluxio/issues/12999

alluxio-bot, cherry-pick this to branch-2.5 please.


zoekt: 3.7.2-2-unstable-2024-09-10 -> 3.7.2-2-unstable-2024-09-19

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for zoekt is: Fast trigram based code search
meta.homepage for zoekt is: https://github.com/sourcegraph/zoekt
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.7.2-2-unstable-2024-09-19 in filename of file in /nix/store/06qg98m1qfk8rn7hri2fc9ri578axg23-zoekt-3.7.2-2-unstable-2024-09-19

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

zoekt

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/06qg98m1qfk8rn7hri2fc9ri578axg23-zoekt-3.7.2-2-unstable-2024-09-19 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A zoekt https://github.com/r-ryantm/nixpkgs/archive/fb621ed8eeda4e54581ce676458680a2fb9613fb.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/fb621ed8eeda4e54581ce676458680a2fb9613fb#zoekt

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/06qg98m1qfk8rn7hri2fc9ri578axg23-zoekt-3.7.2-2-unstable-2024-09-19
ls -la /nix/store/06qg98m1qfk8rn7hri2fc9ri578axg23-zoekt-3.7.2-2-unstable-2024-09-19/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

zoekt

Maintainer pings
cc @AndersonTorres for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge


Build info error

while running yarn verify, I am getting this error"
[Error: ENOENT: no such file or directory, open 'C:\Users\dev\Desktop\nft-erc721-collection-main\smart-contract\artifacts\build-info\dbb0ed8fef0c7503b97499097ec4a1cc.json'] {
errno: -4058,
code: 'ENOENT',
syscall: 'open',
path: 'C:\Users\dev\Desktop\nft-erc721-collection-main\smart-contract\artifacts\build-info\dbb0ed8fef0c7503b97499097ec4a1cc.json'
}
error Command failed with exit code 1.

Hi,
The bug report template requires some data that is missing here.
I'll give you some time to add the missing information, otherwise I will have to close the issue as invalid. Please keep in mind that if you don't provide us with the steps to reproduce this issue on our side, we won't be able to help you.
If you just have a general question and you don't think this is a bug, you might ask for support from the community in the Discussions section. Thank you.
You can take a look at the issue template below:
https://github.com/hashlips-lab/nft-erc721-collection/blob/ecb19096f3dae6f29505d0d85a9844d7cf07d505/.github/ISSUE_TEMPLATE/bug_report.md?plain=1#L24-L51

General information

error while verifying the smart contract
[Error: ENOENT: no such file or directory, open 'C:\Users\dev\Desktop\nft-erc721-collection-main\smart-contract\artifacts\build-info\dbb0ed8fef0c7503b97499097ec4a1cc.json']

Project version
0.0.0

Operating system and version
windows 10 home

NodeJS version
14.16.1

NPM version
6.14.12

Yarn version
1.22.15

Truffle version
5.5.7

Describe the bug
While running the command "yarn verify 0xbca4FBDe64E4B5e67DA0CFD9bB45c619464820D3 --network truffle" i get this error
[Error: ENOENT: no such file or directory, open 'C:\Users\dev\Desktop\nft-erc721-collection-main\smart-contract\artifacts\build-info\dbb0ed8fef0c7503b97499097ec4a1cc.json'] {
errno: -4058,
code: 'ENOENT',
syscall: 'open',
path: 'C:\Users\dev\Desktop\nft-erc721-collection-main\smart-contract\artifacts\build-info\dbb0ed8fef0c7503b97499097ec4a1cc.json'
}
error Command failed with exit code 1.
How to Reproduce
Steps to reproduce the behavior (please provide a reproducer project for complex bugs):

Go to 'cd smart-contract'
run 'yarn verify (your smart contract address) --network truffle'
Scroll down to 'an unexpected error occured'
See error

Expected behavior
I expected to have the smart contract verified on rinkyby testnet.
Screenshots

Additional context
nothing more just that.

Hi @SharkTankIndia,
I don't think this is a bug, you might have compiled multiple versions of the contract and now the compiler is confused by the multiple "cache" files.
First of all there is no version 0.0.0, did you download the last commit from the main branch instead of a release tag?
The main branch contains the development version. It should be stable enough for testing, but it's not production-ready. I highly recommend sticking with stable releases instead.
To solve the error please try the following:

remove these folders from the /smart-contract path: artifacts, cache, typechain
run yarn compile
try verifying again

Let me know if this works.

hey there,
I tried as you instructed me to but this time I am getting a different error.
HeadersTimeoutError: Headers Timeout Error
at Timeout.onParserTimeout [as _onTimeout] (C:\Users\dev\Desktop\nft-erc721-collection-main\smart-contract\node_modules\undici\lib\client.js:1005:28)
at listOnTimeout (internal/timers.js:556:17)
at processTimers (internal/timers.js:497:7) {
code: 'UND_ERR_HEADERS_TIMEOUT'
}

It seems like the CLI can't connect to the remote API for verifying the contract.
Please make sure that:

your wallet is connected to truffle dashboard
the correct network is selected on metamask

My only way to reproduce this error is by running the command while my wallet is not connected to the dashboard.

Which is the correct network sir?how do I use polygon?
On Wed, 6 Apr, 2022, 6:25 pm Marco Lipparini, @.***>
wrote:

It seems like the CLI can't connect to the remote API for verifying the
contract.
Please make sure that:

your wallet is connected to truffle dashboard
the correct network is selected on metamask

My only way to reproduce this error is by running the command while my
wallet is not connected to the dashboard.
—
Reply to this email directly, view it on GitHub
https://github.com/hashlips-lab/nft-erc721-collection/issues/214#issuecomment-1090235645,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXVJAQSO76DW4XPBFII34PLVDWCSRANCNFSM5SSOMA3Q
.
You are receiving this because you were mentioned.Message ID:
@.***>

I think you are missing some basic concepts here, please follow my tutorials in order to understand the basics.
I have to close this issue since the error you are getting is not a bug, it seems like you have a bad configuration on your wallet or you are not confirming the transaction on metamask before the timeout kicks in. When opening an issue you will be guided about how to ask for support instead of opening a bug report.
Thank you.

@SharkTankIndia I have the same problem when verifying contract on polygon testnet. I deleted artifacts and cache folders and rerun yarn compile. After that, my contract is abled to be verified via yarn verify 0x**** --network truffle.


npm v1.0.13 is missing

Was this unpublished? It seems the only diff between 1.0.13 and 1.0.14 is the package version, but 1.0.13 is not found in npm info. Can this be republished if it's not too much trouble?

It was unpublished because of #141. Please switch to 1.0.14.

This problem seems to have come back.
$ node -v
v6.9.2

npm install<EMAIL_ADDRESS>npm ERR! Darwin 17.3.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"<EMAIL_ADDRESS>npm ERR! node v6.9.2
npm ERR! npm  v3.10.9
npm ERR! code ETARGET

npm ERR! notarget No compatible version found<EMAIL_ADDRESS>npm ERR! notarget Valid install targets:
npm ERR! notarget 1.1.3, 1.1.2, 1.1.1, 1.1.0, 1.0.18-0, 1.0.17, 1.0.15, 1.0.14, 1.0.12, 1.0.11, 1.0.10, 1.0.9, 1.0.8, 1.0.7, 1.0.6, 1.0.5, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0, 0.3.8, 0.3.7, 0.3.6, 0.3.5, 0.3.4, 0.3.3, 0.3.2, 0.3.1, 0.3.0, 0.2.0, 0.1.6, 0.1.5, 0.1.4, 0.1.3, 0.1.1
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR! Please include the following file with any support request:
npm ERR!     /Volumes/Data/Work/Code/vyprvpn-sdk-reference-ui/www/npm-debug.log

@wesleyboar that version had to be unpublished. Update to latest


Can't use *.h extension for file to mock

Describe the bug
I'm not able to mock files with "h" extension
To Reproduce
Steps to reproduce the behavior:
Just change the extension of the mocked file in the tutorial repository
Expected behavior
All extensions should work fine

PR merged https://github.com/FreeYourSoul/FSeam/pull/16 , thank you for the contribution